INTL 3:770/1 3:770/3
REPLYADDR bp@www.zefox.net
REPLYTO 3:770/3.0 UUCP
MSGID: cd9e3cef
REPLY: c087c840
PID: SoupGate-Win32 v1.05
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)
SEEN-BY: 19/38 105/81 106/201 128/187 129/305 153/757 7715 218/700
SEEN-BY: 218/840 220/70 226/17 30 100 227/114 229/110 111 114 200
SEEN-BY: 229/206 300 317 400 426 428 470 550 616 664 700 266/512 267/800
SEEN-BY: 282/1038 291/111 292/854 310/31 320/219 322/757 342/200 396/45
SEEN-BY: 460/58 633/280 281 412 418 420 509 2744 712/848 770/1 3 100
SEEN-BY: 770/330 340 772/210 220 230 902/26 5020/400 5075/35
PATH: 770/3 1 633/280 229/426
