Subj : Re: Dual wifi connections in Bookworm To : bp@www.zefox.net From : bp@www.zefox.net Date : Wed Nov 27 2024 20:22:28 bp@www.zefox.net wrote: > The Natural Philosopher wrote: >> >> Bob.. I dont *know* how linux routing copes with two interfaces to the >> same network. >> >> Ideally it should open either at random, and since they have unique >> source addresses pings should always get back. Nothing outside the >> machine itself knows whether it has two interfaces or is in fact two >> separate machines. >> >> I just know that my gut feeling is not to do that, at all. >> When you have all these interfaces up, what does ifconfig show? and route? > > To start with, ifconfig reports > wlan1: flags=4163 mtu 1500 > inet 192.168.1.18 netmask 255.255.255.0 broadcast 192.168.1.255 > inet6 fe80::26ee:3368:6e6c:aa6e prefixlen 64 scopeid 0x20 > ether 24:2f:d0:b9:54:f7 txqueuelen 1000 (Ethernet) > RX packets 6896208 bytes 8657581257 (8.0 GiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 1647035 bytes 215681086 (205.6 MiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > and route reports > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use Iface > default 192.168.1.254 0.0.0.0 UG 601 0 0 wlan1 > 192.168.1.0 0.0.0.0 255.255.255.0 U 601 0 0 wlan1 > > If I bring up wlan0 (the internal wifi interface then ifconfig reports > wlan0: flags=4163 mtu 1500 > inet 192.168.1.11 netmask 255.255.255.0 broadcast 192.168.1.255 > inet6 fe80::98a0:b51e:4f4:236a prefixlen 64 scopeid 0x20 > ether 2c:cf:67:0f:10:64 txqueuelen 1000 (Ethernet) > RX packets 108 bytes 15818 (15.4 KiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 1120 bytes 200215 (195.5 KiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > wlan1: flags=4163 mtu 1500 > inet 192.168.1.18 netmask 255.255.255.0 broadcast 192.168.1.255 > inet6 fe80::26ee:3368:6e6c:aa6e prefixlen 64 scopeid 0x20 > ether 24:2f:d0:b9:54:f7 txqueuelen 1000 (Ethernet) > RX packets 6897155 bytes 8657817041 (8.0 GiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 1648196 bytes 215824139 (205.8 MiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > and route reports > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use Iface > default 192.168.1.254 0.0.0.0 UG 601 0 0 wlan1 > default 192.168.1.254 0.0.0.0 UG 602 0 0 wlan0 > 192.168.1.0 0.0.0.0 255.255.255.0 U 601 0 0 wlan1 > 192.168.1.0 0.0.0.0 255.255.255.0 U 602 0 0 wlan0 > > At the moment, there's a ping session running to the gateway continuously. > Times are sub-2ms unloaded, until I start loading a big page under chromium, > whereupon ping times go.....dammit, everthing works just fine 8-( > > At the moment I'm baffled. It turns out that letting the system stand for ~4 hrs reproduced some of the problems. Ping times with both interfaces up eventually rose to 7-10 ms but didn't fail completely. Several of the ssh connections open from the Pi5 to other hosts either froze or disconnected. bob prohaska --- SoupGate-Win32 v1.05 * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3) .