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.
Pekka Savola "Tell me of difficulties surmounted,
Netcore Oy not those you stumble over and fall"
Systems. Networks. Security. -- Robert Jordan: A Crown of Swords