Does Bird supports AS_Trans 23456
Hello everyone, Does anyone know or test the AS_Trans 23456 with Bird? We are using Bird and our ASN is 4 byte, but the peer supports only 2bytes ASN. I told them to use the AS23456 to peer with me, but it seems Bird doesnt establish session with the peer and Im showing "bad asn" So does Bird support this feature? Should I configure anything in Bird so it can send the open bgp message with ASN23456 instead my real ASN? thank you, Gerta
Hi, Have you tried "local as 23456"? On Tue, Aug 28, 2018 at 9:57 AM, gerta toli <gertatoli@yahoo.com> wrote:
Hello everyone,
Does anyone know or test the AS_Trans 23456 with Bird? We are using Bird and our ASN is 4 byte, but the peer supports only 2bytes ASN. I told them to use the AS23456 to peer with me, but it seems Bird doesnt establish session with the peer and Im showing "bad asn"
So does Bird support this feature? Should I configure anything in Bird so it can send the open bgp message with ASN23456 instead my real ASN?
thank you, Gerta
Thank you Alexander for your response. My main point is to use my real 4byte ASN as local as. Then Bird has to translate it to AS_Trans when talking with my 2byte ASN peer.But it seems Bird is not doing this and instead is sending my real ASN number. gerta On Tuesday, August 28, 2018, 12:30:41 PM GMT+2, Alexander Zubkov <green@qrator.net> wrote: Hi, Have you tried "local as 23456"? On Tue, Aug 28, 2018 at 9:57 AM, gerta toli <gertatoli@yahoo.com> wrote: Hello everyone, Does anyone know or test the AS_Trans 23456 with Bird? We are using Bird and our ASN is 4 byte, but the peer supports only 2bytes ASN. I told them to use the AS23456 to peer with me, but it seems Bird doesnt establish session with the peer and Im showing "bad asn" So does Bird support this feature? Should I configure anything in Bird so it can send the open bgp message with ASN23456 instead my real ASN? thank you, Gerta
On Tue, Aug 28, 2018 at 07:57:43AM +0000, gerta toli wrote:
Hello everyone,
Does anyone know or test the AS_Trans 23456 with Bird? We are using Bird and our ASN is 4 byte, but the peer supports only 2bytes ASN. I told them to use the AS23456 to peer with me, but it seems Bird doesnt establish session with the peer and Im showing "bad asn"
Hello What exactly is your configuration and what exact error message you get in log and/or in 'show protocols'? -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
HI Ondrej, This is my configuration protocol bgp eBGP4byteASN { debug all; import all; export filter out; local as "my-4byteASN"; neighbor 192.168.0.1 as 65535; source address 192.168.0.2; } So my peer 192.168.0.1 understands only 2byte ASN , but I have 4byte ASN. ASN_Trans is used in case of such scenario by the 4byte ASN routers. So supposedly, Bird should send open message using the ASN 23456, since it knows that it is peering with an old 2byteASN router. The error im showing is below: 2018-08-27 15:19:03 <TRACE> eBGP4byteASN: Started 2018-08-27 15:19:03 <TRACE> eBGP4byteASN: Connect delayed by 5 seconds 2018-08-27 15:19:03 <TRACE> eBGP4byteASN: Incoming connection from 192.168.0.1 (port 62762) accepted 2018-08-27 15:19:03 <TRACE> eBGP4byteASN: Sending OPEN(ver=4,as=my_4byteASN,hold=240,id=0a858502) 2018-08-27 15:19:03 <TRACE> eBGP4byteASN: Got OPEN(as=65535,hold=180,id=c6207d28) 2018-08-27 15:19:03 <TRACE> eBGP4byteASN: Sending KEEPALIVE 2018-08-27 15:19:03 <RMT> eBGP4byteASN: Received: Bad peer AS: my_4byteASN 2018-08-27 15:19:03 <TRACE> eBGP4byteASN: State changed to stop 2018-08-27 15:19:03 <TRACE> eBGP4byteASN: Down 2018-08-27 15:19:03 <TRACE> eBGP4byteASN State changed to down 2018-08-27 15:19:03 <TRACE> eBGP4byteASN: Starting 2018-08-27 15:19:03 <TRACE> eBGP4byteASN: State changed to start 2018-08-27 15:19:03 <TRACE> eBGP4byteASN: Startup delayed by 300 seconds So my question is, does Bird supports using this ASN_Trans? How can a 4byte ASN bird router establish a session with a 2byte ASN router? Thanks, Gerta On Tuesday, August 28, 2018, 1:08:32 PM GMT+2, Ondrej Zajicek <santiago@crfreenet.org> wrote: On Tue, Aug 28, 2018 at 07:57:43AM +0000, gerta toli wrote:
Hello everyone,
Does anyone know or test the AS_Trans 23456 with Bird? We are using Bird and our ASN is 4 byte, but the peer supports only 2bytes ASN. I told them to use the AS23456 to peer with me, but it seems Bird doesnt establish session with the peer and Im showing "bad asn"
Hello What exactly is your configuration and what exact error message you get in log and/or in 'show protocols'? -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
On Tue, Aug 28, 2018 at 11:48:31AM +0000, gerta toli wrote:
HI Ondrej,
This is my configuration
protocol bgp eBGP4byteASN { debug all; import all; export filter out; local as "my-4byteASN"; neighbor 192.168.0.1 as 65535; source address 192.168.0.2; }
So my peer 192.168.0.1 understands only 2byte ASN , but I have 4byte ASN. ASN_Trans is used in case of such scenario by the 4byte ASN routers. So supposedly, Bird should send open message using the ASN 23456, since it knows that it is peering with an old 2byteASN router. The error im showing is below:
That is how it works: OPEN message itself contains always 2byte ASN or ASN 23456 in the main ASN field and 4B ASN is stored in optional field, so it is ignored by the peer that does not understand the optional field. If the peer reports Bad peer AS: my_4byteASN, then the peer most likely understands 4byte ASNs, because it can read the optional field. Therefore, it should be configured with your 4B ASN as peer ASN. The fact that the peer itself uses 2B ASN is irrelevant. The important distinction is whether the peer understands 4B ASN capability, which likely is supported by most BGP software/firmware that is not older than ~10 years. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
I understand what you are saying but they are insisting that they router doesnt support 4byte ASN. Im not sure what the router and the version they are using. So Bird can interoperate with a router that supports 2byte ASN only? Gerta On Tuesday, August 28, 2018, 2:25:52 PM GMT+2, Ondrej Zajicek <santiago@crfreenet.org> wrote: On Tue, Aug 28, 2018 at 11:48:31AM +0000, gerta toli wrote:
HI Ondrej,
This is my configuration
protocol bgp eBGP4byteASN { debug all; import all; export filter out; local as "my-4byteASN"; neighbor 192.168.0.1 as 65535; source address 192.168.0.2; }
So my peer 192.168.0.1 understands only 2byte ASN , but I have 4byte ASN. ASN_Trans is used in case of such scenario by the 4byte ASN routers. So supposedly, Bird should send open message using the ASN 23456, since it knows that it is peering with an old 2byteASN router. The error im showing is below:
That is how it works: OPEN message itself contains always 2byte ASN or ASN 23456 in the main ASN field and 4B ASN is stored in optional field, so it is ignored by the peer that does not understand the optional field. If the peer reports Bad peer AS: my_4byteASN, then the peer most likely understands 4byte ASNs, because it can read the optional field. Therefore, it should be configured with your 4B ASN as peer ASN. The fact that the peer itself uses 2B ASN is irrelevant. The important distinction is whether the peer understands 4B ASN capability, which likely is supported by most BGP software/firmware that is not older than ~10 years. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
Im using this version of bird BIRD 1.6.4 ready. Thank you, Gerta On Tuesday, August 28, 2018, 2:33:38 PM GMT+2, gerta toli <gertatoli@yahoo.com> wrote: I understand what you are saying but they are insisting that they router doesnt support 4byte ASN. Im not sure what the router and the version they are using. So Bird can interoperate with a router that supports 2byte ASN only? Gerta On Tuesday, August 28, 2018, 2:25:52 PM GMT+2, Ondrej Zajicek <santiago@crfreenet.org> wrote: On Tue, Aug 28, 2018 at 11:48:31AM +0000, gerta toli wrote:
HI Ondrej,
This is my configuration
protocol bgp eBGP4byteASN { debug all; import all; export filter out; local as "my-4byteASN"; neighbor 192.168.0.1 as 65535; source address 192.168.0.2; }
So my peer 192.168.0.1 understands only 2byte ASN , but I have 4byte ASN. ASN_Trans is used in case of such scenario by the 4byte ASN routers. So supposedly, Bird should send open message using the ASN 23456, since it knows that it is peering with an old 2byteASN router. The error im showing is below:
That is how it works: OPEN message itself contains always 2byte ASN or ASN 23456 in the main ASN field and 4B ASN is stored in optional field, so it is ignored by the peer that does not understand the optional field. If the peer reports Bad peer AS: my_4byteASN, then the peer most likely understands 4byte ASNs, because it can read the optional field. Therefore, it should be configured with your 4B ASN as peer ASN. The fact that the peer itself uses 2B ASN is irrelevant. The important distinction is whether the peer understands 4B ASN capability, which likely is supported by most BGP software/firmware that is not older than ~10 years. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
On Tue, Aug 28, 2018 at 12:33:38PM +0000, gerta toli wrote:
I understand what you are saying but they are insisting that they router doesnt support 4byte ASN. Im not sure what the router and the version they are using.
You can catch the session establishment attempt using tcpdump tool to see what the other side sends in the HELLO message.
So Bird can interoperate with a router that supports 2byte ASN only?
Yes, it should. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
participants (3)
-
Alexander Zubkov -
gerta toli -
Ondrej Zajicek