Hi Antonio,
El 06/06/13 02:51, Antonio Quartulli escribió:
Hello Gabriel,
On Wed, Jun 05, 2013 at 12:27:48PM -0300, Gabriel Tolón wrote:
Sorry, I sent the mail incomplete,
So these are the routes:
Equipo1:
root@Equipo 1:~# batctl o [B.A.T.M.A.N. adv 5ffa8f2, MainIF/MAC: wlan0-1/66:70:02:4e:d9:42 (bat0)] Originator last-seen (#/255) Nexthop [outgoingIF]: Potential nexthops ... E3-5GHz 0.680s (251) E3-5GHz [ wlan1-1]: E3-5GHz (251) E3-2GHz 0.430s (255) E3-5GHz [ wlan1-1]: E3-5GHz (255) E3-2GHz (252)
Equipo3:
root@Equipo 3:~# batctl o [B.A.T.M.A.N. adv 5ffa8f2, MainIF/MAC: wlan0-1/66:70:02:4e:d9:d6 (bat0)] Originator last-seen (#/255) Nexthop [outgoingIF]: Potential nexthops ... E1-2GHz 0.310s (255) E1-5GHz [ wlan1-1]: E1-5GHz (255) E1-2GHz (255) E1-5GHz 0.550s (255) E1-5GHz [ wlan1-1]: E1-5GHz (255)
routing tables look good. I am wondering where the problem can be.. Can you try to do a "batctl td wlan0-1" while pinging? this may help to understand where the process is blocking. It would be helpful if you could do that on both the nodes while pinging in only one direction This way we see who receives what.
I did it, but the text files for the logs of the nodes with "batctl td" have a size of about 250 kB each one, with just 1 or 2 seconds logging. Is that too much for sending them to the list?
(commit IDs are ok) Thank you very much for helping us in debugging this :)
No problem! I've asked things to this list many times and I've got useful answers, so I'm pleased to cooperate.
Regards
Gabriel