I have applied the patch supplied by Henning, and now get the following in
my bgpctl show neighbor
Neighbor capabilities:
Multiprotocol extensions: IPv4 Unicast (previously was unknown (128))
yes, with my patch, we simply ignore the annoucement and show the default.
Can this pa
* Graeme Lee <[EMAIL PROTECTED]> [2008-08-26 02:59]:
> Reading over RFC3397, section 3 covers the error handling. This is how I
> read it:
>
> If you don't understand capabilities advertisements at all, you should
> terminate, and re-establish with no capabilities options.
that doesn't help - t
Henning Brauer wrote:
* Claudio Jeker <[EMAIL PROTECTED]> [2008-08-25 17:27]:
On Mon, Aug 25, 2008 at 03:54:27PM +0200, Henning Brauer wrote:
* Graeme Lee <[EMAIL PROTECTED]> [2008-08-25 03:28]:
Yes but the safi's are handled during capability negotiation (in function
parse_capa
* Claudio Jeker <[EMAIL PROTECTED]> [2008-08-25 17:27]:
> On Mon, Aug 25, 2008 at 03:54:27PM +0200, Henning Brauer wrote:
> > * Graeme Lee <[EMAIL PROTECTED]> [2008-08-25 03:28]:
> > > Yes but the safi's are handled during capability negotiation (in function
> > > parse_capabilities in session.c)
On Mon, Aug 25, 2008 at 03:54:27PM +0200, Henning Brauer wrote:
> * Graeme Lee <[EMAIL PROTECTED]> [2008-08-25 03:28]:
> > Yes but the safi's are handled during capability negotiation (in function
> > parse_capabilities in session.c)
> > Do I need to do more than just ignore the unknown safi's? C
* Graeme Lee <[EMAIL PROTECTED]> [2008-08-25 03:28]:
> Yes but the safi's are handled during capability negotiation (in function
> parse_capabilities in session.c)
> Do I need to do more than just ignore the unknown safi's? Currently, the
> return (-1) in the mp_safi test never allows the connec
Henning Brauer wrote:
* Graeme Lee <[EMAIL PROTECTED]> [2008-08-21 03:31]:
Henning Brauer wrote:
* Graeme Lee <[EMAIL PROTECTED]> [2008-08-21 01:51]:
I've had to connect to a new upstream peer which is advertising an IPv4
safi of 128 (MPLS-labelled VPN address)
see http://w
* Graeme Lee <[EMAIL PROTECTED]> [2008-08-21 03:31]:
> Henning Brauer wrote:
>> * Graeme Lee <[EMAIL PROTECTED]> [2008-08-21 01:51]:
>>
>>> I've had to connect to a new upstream peer which is advertising an IPv4
>>> safi of 128 (MPLS-labelled VPN address)
>>> see http://www.iana.org/assignment
Henning Brauer wrote:
* Graeme Lee <[EMAIL PROTECTED]> [2008-08-21 01:51]:
I've had to connect to a new upstream peer which is advertising an IPv4
safi of 128 (MPLS-labelled VPN address)
see http://www.iana.org/assignments/safi-namespace
I've modified the source to temporarily ignore this
On 2008-08-20, Graeme Lee <[EMAIL PROTECTED]> wrote:
> I've had to connect to a new upstream peer which is advertising an IPv4
> safi of 128 (MPLS-labelled VPN address)
> see http://www.iana.org/assignments/safi-namespace
>
> I've modified the source to temporarily ignore this (actually anything
* Graeme Lee <[EMAIL PROTECTED]> [2008-08-21 01:51]:
> I've had to connect to a new upstream peer which is advertising an IPv4
> safi of 128 (MPLS-labelled VPN address)
> see http://www.iana.org/assignments/safi-namespace
>
> I've modified the source to temporarily ignore this (actually anything
I've had to connect to a new upstream peer which is advertising an IPv4
safi of 128 (MPLS-labelled VPN address)
see http://www.iana.org/assignments/safi-namespace
I've modified the source to temporarily ignore this (actually anything
over 127) as it currently only accepts 1 thru 3. Once the s
12 matches
Mail list logo
