On 12/04/06, Sylvain Coutant <[EMAIL PROTECTED]> wrote:
>
> > What was the state of the parent interface and what kind of interface is
> > it?
>
> Bge driver. It was up and running : BGP sessions were established through
> the vlans reported as invalid by OpenBGP.
>
>
> > ifconfig down should not crash the box. Panic message and trace would be
> > interesting.
>
> It was remote and we did a hard reboot without console access. Log files
> were empty.
>
>
> > No, the session and the nexthop are two different things.
>
> I agree. My point is : how to prevent routing loops in such cases ?
> Whatever triggered the case (a link down for any reason or a bug) is not so
> important. Announcing routes over the Internet and creating a routing loop
> for those routes is important.
>
> It could be one more setting that, if set to yes, would drop the session
> if it receives an unreachable nexthop ... just an idea. It could default to
> yes for eBGP session and no for iBGP sessions. Would that fit most of
> "usual" cases ?
That sounds like fixing a bug with an option.
In your case the problem is that a connected next-hop is considered invalid,
right ?
--
Tony Sarendal - [EMAIL PROTECTED]
IP/Unix
-= The scorpion replied,
"I couldn't help it, it's my nature" =-
