Dear diary, on Sat, Mar 23, 2002 at 06:08:26PM CET, I got a letter, where Pekka
Savola <pekkas@xxxxxxxxxx> told me, that...
> On Sat, 23 Mar 2002, Petr Baudis wrote:
> > > I think I've seen something similar to this before, and IIRC it was
> > > caused by the fact that loopback interface had been brought down.
> > >
> > > If loopback has been taken down and is back up, IIRC the addresses of the
> > > interfaces must be "refreshed" (e.g. by also taking the interfaces down
> > > and up).
> >
> > First, sorry for the late reply.
> >
> > The problem is, that we don't do anything with loopback interface at all.
> > Please ask us for any additional informations you need, we'll gladly
> > provide you them.
>
> Perhaps zebra does. You could try stracing the appropriate processes to see
> whether they're doing something nasty; 'tcpdump -n -i lo' might also die if
> loopback is taken down and back up.
I started the tcpdump there, and we'll see. However, by looking into code, we
found no possibility how would zebra want to mess with loopback.
Also, we discovered that just taking down and back up any ONE interface will
fix this for ALL other interfaces as well.
--
Petr "Pasky" Baudis
* elinks maintainer * IPv6 guy (XS26 co-coordinator)
* IRCnet operator * FreeCiv AI hacker
.
Teamwork is essential -- it allows you to blame someone else.
.
Public PGP key && geekcode && homepage: http://pasky.ji.cz/~pasky/
|