I had a rather strange thing happen yesterday. I created an aliased
interface under 2.0.33. I put it there because I needed a machine to
listen to the IP while I had a request go through the Internic, for
a new machine to be put on that IP. Anyhow, I created the interface:
ifconfig eth0:1 205.1.28.81 broadcast 205.1.28.127 netmask 255.255.255.192
(IP's changed to protect the innocent ;)
I brought the other machine up on the network, a Solaris 2.4 machine, and
tried to connect to 205.1.28.81 via TCP. It failed, then I realized that
I had the interface aliased on my Linux machine. I then did an:
ifconfig eth0:1 down
I tried again, and it didn't work. So, I started TCPdump and watched it
send packets over the Ethernet to 205.1.28.81, but that machine did respond.
I then checked in /proc/net/arp and found only my gateway router's ARP
entry...it hadn't done an ARP request for 205.1.28.81. The route table
was clear, etc.
I had to reboot the machine to get it to talk to that IP again.
So, sound like a bug???
--Perry
-- Perry Harrington Linux rules all OSes. APSoft () email: perry@apsoft.com Think Blue. /\- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu