Path: ...!weretis.net!feeder9.news.weretis.net!2.eu.feeder.erje.net!feeder.erje.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Michael Schwingen <news-1513678000@discworld.dascon.de>
Newsgroups: comp.sys.raspberry-pi
Subject: Re: Dual wifi connections in Bookworm
Date: 27 Nov 2024 14:54:02 GMT
Lines: 18
Message-ID: <slrnvkecka.5ca.news-1513678000@a-tuin.ms.intern>
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>
X-Trace: individual.net zwNB8xV/G4p1wSsjXN8iaQD3+8VwbXQDuu5HSETgoS7POSmD7V
Cancel-Lock: sha1:I3KpS3jtsSNLECIF7xh+UvbzP+g= sha256:8QIYjTP214zp+YcwREvUGB7IM7DQmi3MgtzOcKxV98Y=
User-Agent: slrn/1.0.3 (Linux)
Bytes: 1597

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.

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.

cu
Michael
-- 
Some people have no respect of age unless it is bottled.