From: kant@have.it   
      
   On 8/6/21 4:11 PM, William Unruh wrote:   
      
   Thanks for the reply.  Let me see if I can clear up some confusion.   
      
   These are the relevant /etc/hosts entries.   
   >> 192.168.1.2     crab   
   >> 192.168.1.3     kraken   
   >> 192.168.1.5     shrimp   
      
   >> 10.10.13.4      c   
   >> 10.10.13.2      k   
   >> 10.10.13.3      s   
      
   All the 192.168.1.* hosts are on wlan0.  All the 10.10.13.* hosts are on eth0.   
   So crab IS c depending on whether it's wlan0 or eth0.  On wlan0 its IP is   
   192.168.1.2 (and that's how it gets to the internet) and on eth0 it uses   
   10.10.13.4 for an IP address.   
      
   > I really have no idea what it is you are trying to do.   
      
   I live in a building where there are WiFi routers everywhere.  Right now I   
   could, if I had the correct password, use any one of the probably 20+ routers   
   the computers see, if I had to guess I'd say there are about 150 WiFi routers   
   in   
   this building.  All of those routers are fighting to use the same 2.4/5Ghz   
   frequencies.  Heck when I had to get a replacement cable modem the company gave   
   me a new one that has a builtin WiFi router, meaning I have 2 WiFi routers   
   running (ironically they're wired together with a cable, probably on   
   192.168.0.*   
   network).   
   By using the eth0, an old switch, and cables, I can pass traffic between c, k,   
   and s without adding to the WiFi traffic.  I often move large 1Gb to 2Gb files   
   between these 3 computers.  WiFi network throughput is often abysmal.   
      
   > I would suggest that you give them different names on the two networks   
      
   They do have different names, and IP addresses on different interfaces.   
      
   To try and put it succinctly.   
   1.  All the computers work on the wlan0/192.168.1.* network.   
   2.  The hosts k and s work fine on the eth0/10.10.13.* network.  So it works.   
   3.  Neither hosts k or s can initiate a connect to host c on the   
   eth0/10.10.13.*   
   network.  This is the problem.   
   4.  Host c can initiate connects to hosts k and s fine on the eth0/10.10.13.*   
   network.  This is important as it shows the eth0 interface on host c does work.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)