From: grinch@somewhere.com   
      
   > If I change the configuration, via yast, to bring up the eth0 device it   
   > shuts down the wlan0 (even though both are defined).   
   >   
   > Seems like I can get either one or the other, but not both.   
      
   If they are in the same subnet that is correct behaviour,Ethernet is   
   preferred over wlan. I don't know how is made to work in Linux but it does.   
      
   My personal laptop is setup like that, when it is on its docking station   
   the traffic goes via the Ethernet even though both eth0 and wlan0 have a   
   LAN IP address in the same subnet.   
      
   >   
   > Is there a place where I can look to see how this should be configured?   
   >   
   > 20 years ago I used to run a smallish network like this at   
   > work...servers had their own network via a switch and another card (no   
   > WiFi, not secure enough for the environment, we used fiber) to the   
   > network where all the desktop machines lived.  Even before that I had a   
   > BSD machine with 2 NIC's in it at home.   
      
   Try adding a second different subnet on the eth0 .   
      
   or   
      
   You could try static routes via eth0 to each box  from each box if you   
   need to keep the same subnet.   
      
   i.e. IP route 192.168.1.100 /24 via eth0's IP address the repeat for   
   each separate box   
      
   The static routes should take precedence due to the longest match rule,   
   well they would in a cisco router which is what I am used to.   
      
   This can cause weird routing problems though ,I would not recommend it.   
      
      
   or   
      
   A more elegant solution would be to make the subnet on your router   
   larger so say a /23 then have 2 separate /24 subnets   
      
   /23 255.255.252.0   
      
   So wlan 192.168.0.0/24   
   eth0 192.168.1.0/24   
   Default gateway 192.168.0.x /23   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)