From: tnp@invalid.invalid   
      
   On 27/11/2024 14:54, Michael Schwingen wrote:   
   > On 2024-11-27, The Natural Philosopher  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   
      
   --- SoupGate-DOS v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)