On two machines running 2.2.17 and one running 2.4-pre9-rest9 I have observed
that it is possible to ping an interface after it has been brought down.
On 2.0.38 I get "Network is unreachable"
Is this a bug or a feature?
Tomorrow we are going to take a new Compaq server into operation so I configured
eth0 with the same ip address as the old server and configured eth1 to be on
another network in order to do the final rsync tonight:
eth0: 172.16.52.32/255.255.255.0
eth1: 172.17.136.1/255.255.0.0 gw 172.17.0.254
I then took eth0 down connected the cables and could ping 172.16.52.32 thinking
that is was the old server I was pinging via eth1. When I telnetted to the
address I got the login prompt from the new server. arp -a showed nothing
interesting. I could reproduce this on another 2.2.17 machine.
pinging 172.16.52.31 (or any different from .32) gives "Network is unreachable".
The ip address of eth1 was also "pingable" after it was downed.
If I also took lo down the ping's for 127.0.0.1, 172.16.52.32 or 172.17.136.1
just hangs.
Occasionally I see something along "error fetching interface information" from
ifconfig on 2.2.17.
Most devices are eepro100.
Many regards
Peter
--
Peter L. Hansen
LASAT Networks A/S
pha@xxxxxxxxx / peter@xxxxxxxxxxxx
|