Re: Problems with Multiple Interfaces
Linus and Simon, Thank you for your responses. I did try "batctl ping" and the adjacent device was unreachable. I could see it with "batctl n". I did not try a simple IPv6 link local ping. However, I could see it using "iw dev mesh_5g station dump" I agree that it feels like a problem with ath10k reporting the data rate incorrectly (or not at all). I am going to try upgrading to the latest release, but it will be a few days. I'll let you know how it goes. Thanks again, --Joe
Re: How to mesh over ethernet VLAN?
> The MTU of eth0.2 or bat0? It doesn't matter, I cannot set the MTU of eth0.2, eth0 or eth1 to something higher than 1500 > One of the performance penalties might occur when batman-adv needs > to use fragmentation. batman-adv is going to add its own header > on top of the 1500 byte frames received on bat0. That's why I'm trying to increase the MTU > 1536 on eth0.2 looks good though. Then 1500 bytes should fit > without fragmentation on bat0. You can check with "batctl > td" or Wireshark if you see batman-adv fragments on eth0.2. That's only the config. IP LINK still showing 1500. > If 1536 is somehow not applied to eth0.2, might be a driver issue > then. You can check wether you can manually alter an interface MTU > with "ip link dev eth0.2 set mtu 1536", for instance. Actual OpenWRT trunk on TP-Link C7 / C2600 devices. Can decrease to anything lower than 1500 but cannot raise above 1500. Thanks, Andi
Re: How to mesh over ethernet VLAN?
On Tue, Apr 06, 2021 at 11:33:26PM +0200, Andi Depressivum wrote: > That was my very first configuration approach but it's rather slow > (about 200mbit/s over a gigabit link) compared to native VLANs. I've > tried to set the MTU size to 1536 for the mesh interface but for some > reason the MTU of the interface stays at 1500?! The MTU of eth0.2 or bat0? One of the performance penalties might occur when batman-adv needs to use fragmentation. batman-adv is going to add its own header on top of the 1500 byte frames received on bat0. 1536 on eth0.2 looks good though. Then 1500 bytes should fit without fragmentation on bat0. You can check with "batctl td" or Wireshark if you see batman-adv fragments on eth0.2. If 1536 is somehow not applied to eth0.2, might be a driver issue then. You can check wether you can manually alter an interface MTU with "ip link dev eth0.2 set mtu 1536", for instance. Regards, Linus
Re: Problems with Multiple Interfaces
On Fri, Apr 09, 2021 at 12:17:36PM +0200, Simon Wunderlich wrote: > On Thursday, April 8, 2021 7:56:29 AM CEST j...@careyhome.org wrote: > > Hi Everybody, > > > > I'm running BATMAN v 2019.2 with ath10k on OpenWRT. The particular router > > I'm using has two interfaces, 2.4 GHz and 5GHz. With each router using > > single interface (e.g. 2.4 GHz), it works fine. When I add a second > > interface (e.g. 5GHz), it sometimes hangs. One more note: ath10k firmware refuses to provide an expected throughput for the wifi link. The fallback to an estimate which uses the raw tx bitrate was added not that long ago in batman-adv v2020.0: https://www.open-mesh.org/news/95 I'm wondering if you might have very low throughput values in batman-adv and if that might lead to issues with interface alternating. Also, would be interesting to know if you have the same issues when using BATMAN IV, which mainly uses a packetloss based metric. Regards, Linus
Re: Problems with Multiple Interfaces
On Thursday, April 8, 2021 7:56:29 AM CEST j...@careyhome.org wrote: > Hi Everybody, > > I'm running BATMAN v 2019.2 with ath10k on OpenWRT. The particular router > I'm using has two interfaces, 2.4 GHz and 5GHz. With each router using > single interface (e.g. 2.4 GHz), it works fine. When I add a second > interface (e.g. 5GHz), it sometimes hangs. > > I know that BATMAN is expected to alternate between the two interfaces, but > that doesn't seem to be working. As you probably know, using two > interfaces should dramatically improve throughput if you need to make a hop > through another mesh node. > > To verify this is the problem, I did a test where I ran three routers, 2.4G > <> Dual (2.4G & 5G) <> 5G. I would try to ping between the two routers > that were using just a single interface. Obviously, that must hop through > the dual radio router. The dual radio router has both interfaces on the > bat0 master, and batctl reports they're both active. > > The system would sometimes lose link, although batctl would report getting > neighbor messages. Even using the batctl ping function doesn't get > through. I can see traffic flowing on both the 2.4 GHz and 5GHz > interfaces. > > I'm happy to provide lots of configuration detail, but I thought I'd start > with a high level description in case this is a known problem. > > Any assistance is appreciated. Thank you, > > --Joe Hi Joe, I'd expect your setup to work. Could you try to run "batctl ping" between the nodes, maybe also on the intermediate links? If you see that it's failing too, could you set up some IPv4 addresses (or use IPv6 link local addresses) on your ad-hoc/mesh interfaces, and try to ping to the next hop? I suspect that something is off with the wifi driver, i.e. broadcasts are still working but unicast pings are dropped. Cheers, Simon signature.asc Description: This is a digitally signed message part.
