From: kant@have.it   
      
   > I would suggest that there is some difference in the routing table of c.   
   > We tend to see what should be there instead of what is actually there.   
      
   To paraphrase Simon & Garfunkel from The Boxer...   
   "Still, a man sees what he wants to see and disregards the rest."   
   The real lyrics say "hear" instead of "see".   
      
   I looked at the output from all 3 computers for the ip a and route commands.   
   The only differences, aside from the expected, are kraken using wlan1 and the   
   altname being missing from kraken.  Recall that kraken is running on 15.1 and   
   several years ago you helped me get this interface working on what was then   
   fairly new hardware.  Seems like someone had to patch the module in order to   
   get   
   it to load under openSUSE, I spent quite a bit of time loading openSUSE and   
   then   
   Ubuntu (maybe it was Debian or RedHat) and comparing the results of the various   
   commands.   
      
   Now, having said the above, I've fixed it temporarily.  It's working.  But as   
   soon as I reboot crab it stops working.   
      
   The, not so very good, fix is:   
   Yast --> Services Manager --> firewalld   
   After boot it's "Inacive(dead)" for some reason.  It's defined to start "On   
   Boot".  The computer crab is the only one not having a firewalld running, it's   
   also the only one which will not accept an inbound connect.   
   After manually starting it the eth0 connects work, until a reboot.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)