hans privat wrote:
The situation is certainly unsatisfactory, and the solution I use involves making all the NICs the same speed, so that they are interchangeable and you don't care which one the kernel decides is eth0.if I change the two cards, so that I have eth0 as IP 10.0.0.10 and eth1 has the IP 192.168.10.8, then I'm running into problems with ssh-login from local or remote.Now my very interesting question : Is this behavior predesigned on linux, or do I have a possibility to make a change in a script anywhere on the linux-system, so that eth0 can have also an IP 10.0.0.10 or any other IP, and the eth1 is having the "local-network" adress of 192.168.10.1 (or any other IP) and a login with ssh root@jojo will be successfully.
man arp is a hot clue. The arp command probably sets up which is eth0, 1, etc based not on your assigned IP address but based on the NIC's MAC address, which is really what you want. The problem here is that arp seems to be using the MAC of whatever is at the other end of the link.
Anybody have an answer to this riddle?
--
Ron. [Melbourne, Australia]
troels... now updated to use sunet.se server.
See: http://members.optusnet.com.au/ronst/
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
