2013.4.0
On 1 December 2013 11:18, tjhowse tjhowse@gmail.com wrote:
I can't say which version for certain right now - I'll check when I'm back at work on Monday - but it was the latest available from the barrier_breaker sources as of approximately two weeks ago.
On 1 December 2013 09:19, tjhowse tjhowse@gmail.com wrote:
I can't say which version for certain right now - I'll check when I'm back at work on Monday - but it was the latest available from the barrier_breaker sources as of approximately two weeks ago.
On 30 November 2013 13:35, Gui Iribarren gui@altermundi.net wrote:
On 11/24/2013 08:36 PM, tjhowse wrote:
In my test system I have 11 dual-channel nodes. The 5GHz link is used for interconnect between the nodes and the 2.4GHz link is for clients. One of the nodes is distant. My laptop is connected to a common-SSID AP link from one of the local nodes. I can always ping the distant node from one of the local nodes, but the link from my laptop is less reliable. I can have an SSH session open to the distant node and a local node, pinging the distant node from both the local node and my laptop. At no particular point the distant node will stop pinging from my laptop and its SSH session will drop, while the ping continues just fine from the local node.
The connection can restore equally mysteriously.
Can anyone explain this behavior? No manual network configuration changes are being made at the point at which the connection drops or is restored, though I suppose my laptop could be hopping between one of the local APs. I am pinging an IP attached to the bridge joining bat0, the copper node LAN and the 2.4GHz client LAN.
Which batman-adv version are you using?
i've seen a similar behaviour on 2013.1.0 and 2013.2.0, related to TTVN, but never collected data clean enough to report it, and then 2013.4.0 came out. i'll test this week 2013.4.0 to see if it's still an issue.