Hi Jeremy, i'm pretty sure I've also ran into this behaviour, but just assigning another (non-used, private) ip to the same device (like eth0:1) would stop it listening on that ip.
I can not remember with what kernel this happened. On kernel 2.2.19, debian 2.2 (kinda) and ifconfig version 1.39 (1999-03-18) it is not reproducable. Regards, Robert Davidson. On Thu, Apr 19, 2001 at 06:12:20PM -0700, Jeremy C. Reed wrote: > I added an IP (IPs changed for this example): > > ifconfig eth0:1 192.168.197.179 netmask 255.255.255.128 up > > It was listed with "ifconfig -a". > > Then I removed it with: > > ifconfig eth0:1 192.168.197.179 down > > And it was gone (not listed) from "ifconfig -a". > > But I can still ping it from a remote machine and logon to it. > > Then I tried to reset eth0:1 by giving it a different IP, but the old IP > still worked. > > And I tried (as documented in linux/Documentation/networking/alias.txt): > ifconfig eth0:1 down > > Any ideas on how I get it to stop listening to that IP ... > > I found a way: I assigned the IP to eth0:4, then I assigned a > different IP to eth0:4 and then it was gone (and I couldn't connect to > it). > > Any ideas why I could connect to an IP that wasn't listed by ifconfig? > > Can anyone reproduce this? > > This is Debian 2.2 Linux 2.2.14. > > Jeremy C. Reed > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] >
