From: kant@have.it   
      
   > Ie, are those actually your hosts entries, literally, or is c k and to   
   > be read as crab kraken and shrimp? If it is literally c k and s then   
   > that is fine, but then you also have to call them as c k and s, not as   
   > crab, kraken and shrimp   
      
   Those are the host names. c, crab, k, kraken, s, and shrimp.  Each host name   
   has   
   a unique IP assigned to it.  Not to be snippy about it...but I retired in 2002   
   as a sysadmin taking care of 40 or 50 machines, a dozen were SUN Sparc servers   
   running Solaris.  They all had two network cards, one to talk to client   
   machines, and one so the servers could talk to each other.  So I've set this up   
   before.  Once upon a time I had a BSD machine at home running two cards (it was   
   a firewall and did NAT [IP masquerading back in the old days, who knows what   
   the   
   latest term is], one to the ISP and the other to several linux machines behind   
   it.   
      
   >> 1.  All the computers work on the wlan0/192.168.1.* network.   
   >   
   > Under what names?   
      
   For that network they are crab, kraken, and shrimp.   
      
   >> 2.  The hosts k and s work fine on the eth0/10.10.13.* network.  So it   
   works.   
   >   
   > Under what name   
      
   For that network c, k, and s.   
      
   > Are you sure that there is not some other machine with IP   
   > 10.10.13.4?   
      
   My networks, I assigned the IP addresses and names.   
      
   > Are you sure that the answers are not sent on the wlan0 line?   
      
   Can't see how.  wlan0 talks to a WiFi router which passes it's traffic on up to   
   the network the cable company runs.  I ran wireshark on c and saw the broadcast   
   traffic from the switch asking who had 10.10.13.4 when I tried to "ssh bill@c"   
   from k, and k ended up with an ARP cache entry for c on eth0.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)