<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.28.3">
</HEAD>
<BODY>
Hello Ondrej, bird-users<BR>
<BR>
correct no multihop defined, as there is/was no need to.<BR>
i'd only enabled the link when needing it.<BR>
<BR>
Regards,<BR>
<BR>
On Fri, 2010-07-02 at 10:44 +0200, Ondrej Zajicek wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
On Mon, Jun 28, 2010 at 02:02:16PM +0200, Arjan Filius wrote:
> Hello Bird-users,
>
>
> Currently making some monitor scripts, and working on that i noticed a
> little difference with 2 (ipv4 and ipv6) export-only bgp protocols.
...
> Both the protocol definitions are exactly the same, apart from the
> neighbor definition.
>
> The only difference is the ipv4 neigbor is in a direct connected subnet,
> where the ipv6 isn't.
>
> After "fixing" the ipv6 passive neigbor to a direct connected ip i got
> the "Passive" in the info field.
>
> I'm not sure what is the correct behaviour, but displaying passive when
> actually passive eases my monitoring scripts.
I think that if you don't have multihop option and your neighbor address
is not from a direct connected subnet, that such configuration is unusable
and that is a reason why there is Idle state and not Passive state.
</PRE>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>