On Sun, May 21, 2000 at 08:19:55PM +0200, Peter T. Breuer wrote:
> "A month of sundays ago Peter T. Breuer wrote:"
> > "A month of sundays ago Alan Cox wrote:"
> > > > [not ac]
> > > > Because the this only happens with IPv6, it is an obvious bug. In
> > > > addition, about 99.9% of people are using commands like 'ifconfig eth0:5
> > > So strace your ifconfig eth0:5 down figure out which ioctl is causing the
>
> > It might be the ifconfig version. The most obvious differences in the
>
> It looks like it. I switched kernels on my machine with a 2.2.10 kernel
> exhibiting th ebug downstairs, loaded ipv6 and tried the test (ifconfig
> lo:0 127.0.0.2; ifconfig lo:0 down, does lo disappear too?). It worked
> fine with my version of ifconfig. net-tools 1.432 ifconfig 1.29
> (1997-09-23), linked against libc 5.4.38.
>
> I then took the ifconfig from downstairs and ran it up here. It
> exhibited the bug. net-tools 1.54 ifconfig 1.39 (1999-03-18), linked
> against glibc 2.1.2.
When I use ifconfig 1.39 (1999-03-18) linked against libc5 on 2.3.99-pre6,
and try lo:1 down, both lo and lo:1 are gone too.
I still had serveral version here, compiled them, and this is what I get:
1.432 (1.29 (1997-09-23)) good
1.46 (1.35 (1998-08-29)) good, but doesn't show lo:1 when it's up
1.47 (1.36 (1998-10-31)) bad
1.51 (1.39 (1999-03-18)) bad
Don't have, and cound't find anything between 1.432 and 1.46
1.55 didn't compile
Kurt
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
