On 2012-11-15, Daniel Ouellet <dan...@presscom.net> wrote: > A more complete answer provided in private, but here is an extract and > as you can see, I have peers that I have the session where I advertise > supporting the 4 bytes, and they do not support it as shown, so I do not > advertise to them as such and others that I do both as shown.
>From the private mail the important part is that the route server is *not* announcing 4-byte ASN support, but your router does. > Neighbor capabilities: > Route refresh: advertised and received(new) > Four-octets ASN Capability: advertised i.e. "advertised" not "advertised and received". So as far as your router is concerned, this session is *not* using 4-byte ASN, but it would appear that their side thinks it is. I don't see any problems with the code in -current for this negotiation, the relevant code was changed in rde.c 1.276 but the old code also looks correct. It would be interesting to know what version of bgpd code they are running (and whether they have made any changes to it)...
