Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: The Natural Philosopher <tnp@invalid.invalid>
Newsgroups: comp.sys.raspberry-pi
Subject: Re: Dual wifi connections in Bookworm
Date: Wed, 27 Nov 2024 16:53:19 +0000
Organization: A little, after lunch
Lines: 40
Message-ID: <vi7ipv$3793$2@dont-email.me>
References: <vhvsif$2bgld$1@dont-email.me> <vi2pvm$30hu1$1@dont-email.me>
 <slrnvkduch.5ca.news-1513678000@a-tuin.ms.intern>
 <vi70pa$3vogk$9@dont-email.me>
 <slrnvkecka.5ca.news-1513678000@a-tuin.ms.intern>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Wed, 27 Nov 2024 17:53:19 +0100 (CET)
Injection-Info: dont-email.me; posting-host="d3a623bf95e4349e30bbb37a7e6182dd";
	logging-data="105763"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19yb+bMUy3cWKnCicX4ieiQxC18+GyxLco="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:ZRZ8EiTVlxj4VstD+0I+/UIbWb4=
Content-Language: en-GB
In-Reply-To: <slrnvkecka.5ca.news-1513678000@a-tuin.ms.intern>
Bytes: 2710

On 27/11/2024 14:54, Michael Schwingen wrote:
> On 2024-11-27, The Natural Philosopher <tnp@invalid.invalid> wrote:
>> However the ability under windows to make BOTH of them the default
>> route, led to the TCP/IP stack using them in round robin to send TCP/IP
>> packets.
> 
> I just checked on my laptop, which has (sometimes) ethernet and wireless
> connections to the same network, with separate IP addresses. This works just
> fine without any packet losses.
> 
Oh. I wasn't meaning that that was the *exact* issue in this case. It 
was merely a nice swipe at Micro$oft.

Linux doesn't allow of more than one default route.

*However* routing with more than one interface active is complex, 
especially if they connect to the *same* network.

If you have two interfaces active on the same network, which one is 
going to be used to access that network?

I am not claiming this is the answer, just that it may be due some 
consideration.

> This is while running Debian, not raspbian, but at least it shows that this
> scenario can work on Linux - I am at a loss what happens on the problem
> machine.  Probably some tcpdump/wireshark tracing, maybe even on both sides
> of the access point, is required to get at the cause of the problem.
> 
I think some careful thought and experimentation may get you there quicker.



-- 
“Some people like to travel by train because it combines the slowness of 
a car with the cramped public exposure of 
an airplane.”

Dennis Miller