Seems like on my node2 the TQ value keeps ramping up and down (120-230) along with my internet usage...
Batman does consider and average TQ value rite?
Philippe...seems your problem and mine are similar hence continuing posting in
this thread,if you feel its different please tell me ill repost as a new thread.
My network setup is as shown
Gateway 10.24.249.96
-------------------------------------
|
50ft |
|
|
|
Node 1 (10.1.125.158)
-------------------------------------
|
25ft |
|
Node 2 (10.1.52.)236
-------------------------------------
The wifi signal strength between Gateway and Node 1 is good and so is between Node 1 and Node 2 .In general the average signal strength between Node 2 and gateway is bad.
But momentarily there seems to be an improvement in direct link between the Gateway and Node 2 and at this point of time the the tunnel formed from Node 2 to gateway via Node 1 is deleted and the a new direct tunnel is formed which again looses link as its average signal strength is bad.
This is what batmand -cd3 on the Node 2 shows
/ # batmand -cd3
WARNING: You are using the unstable batman branch. If you are interested in *using* batman get the latest stable release !
Gateway client - successfully refreshed IP lease: 10.24.249.96
Deleting route to 10.24.249.96 via 0.0.0.0 (table 66 - ath0)
Adding route to 10.24.249.96/32 via 10.1.125.158 (table 66 - ath0)
Deleting route to 10.24.249.96/32 via 10.1.125.158 (table 66 - ath0)
Adding route to 10.24.249.96 via 0.0.0.0 (table 66 - ath0)
Deleting route to 10.24.249.96 via 0.0.0.0 (table 66 - ath0)
Adding route to 10.24.249.96/32 via 10.1.125.158 (table 66 - ath0)
Gateway client - disconnecting from unresponsive gateway (10.24.249.96): could not refresh IP lease
Deleting default route via gate0 (table 68)
Adding default route to 10.24.249.96 (gw_flags: 41, tq: 178, gw_product: 0)
Adding default route to 10.24.249.96 (gw_flags: 41, tq: 171, gw_product: 0)
Gateway client - got IP (169.254.0.2) from gateway: 10.24.249.96
Adding default route via gate0 (table 68)
Gateway client - gateway (10.24.249.96) says: IP (169.254.0.2) is expired
Deleting default route via gate0 (table 68)
Adding default route to 10.24.249.96 (gw_flags: 41, tq: 46, gw_product: 0)
Gateway client - got IP (169.254.0.2) from gateway: 10.24.249.96
Adding default route via gate0 (table 68)
Deleting route to 10.24.249.96/32 via 10.1.125.158 (table 66 - ath0)
Adding route to 10.24.249.96 via 0.0.0.0 (table 66 - ath0)
Deleting route to 10.24.249.96 via 0.0.0.0 (table 66 - ath0)
Adding route to 10.24.249.96/32 via 10.1.125.158 (table 66 - ath0)
Deleting route to 10.24.249.96/32 via 10.1.125.158 (table 66 - ath0)
Adding route to 10.24.249.96 via 0.0.0.0 (table 66 - ath0)
Deleting route to 10.24.249.96 via 0.0.0.0 (table 66 - ath0)
Adding route to 10.24.249.96/32 via 10.1.125.158 (table 66 - ath0)
Deleting route to 10.24.249.96/32 via 10.1.125.158 (table 66 - ath0)
--CUT--
The above keeps happening very frequently (at times even every 5-10 secs)
and in my case eventually the gateway crashed (which is my second problem i had posted separately yesterday).
I have noticed that while i am connected to Node 2 and am downloading or transfering data from internet the link keeps chopping up and in most cases times out....however as my wan ip is constant the downloads don't get disconnected.
--
Vinay Menon