Way to use Bird as route server
Hi there, just doing some tests with Bird as route server, but the result was not the desired. Other staff like RTBH is running fine. The situation is that next-hop is not modified (used only RS CLIENT option). All are eBGP sessions. Checked some examples around and found no way to deploy correctly. Any advise or template to achieve this function? Thanks in advance. Regards, Jorge.
NEXT_HOP is not supposed to be modified. http://tools.ietf.org/html/draft-jasinska-ix-bgp-route-server-03 -JJ
On Oct 22, 2014, at 8:56 AM, Osmos <osmoscity@gmail.com> wrote:
Hi there,
just doing some tests with Bird as route server, but the result was not the desired. Other staff like RTBH is running fine.
The situation is that next-hop is not modified (used only RS CLIENT option). All are eBGP sessions.
Checked some examples around and found no way to deploy correctly. Any advise or template to achieve this function?
Thanks in advance. Regards, Jorge.
Hi John, right, it makes sense. After playing on lab, what I checked is that AS_PATH is not modified but next-hop is pointing to route server itself. Reading this draft, next-hop should be one of the rs client (depending on prefix). Configuration tested is based on eBGP session (in, out route maps) and RSCLIENT option active. Route servers clients are Juniper and Vyatta devices. Ospf is running for loopbacks. If it helps, will paste some cli output. Thanks in advance. Jorge.
El 22/10/2014, a las 15:19, John Jensen <jensenja@gmail.com> escribió:
NEXT_HOP is not supposed to be modified.
http://tools.ietf.org/html/draft-jasinska-ix-bgp-route-server-03
-JJ
On Oct 22, 2014, at 8:56 AM, Osmos <osmoscity@gmail.com> wrote:
Hi there,
just doing some tests with Bird as route server, but the result was not the desired. Other staff like RTBH is running fine.
The situation is that next-hop is not modified (used only RS CLIENT option). All are eBGP sessions.
Checked some examples around and found no way to deploy correctly. Any advise or template to achieve this function?
Thanks in advance. Regards, Jorge.
On Wed, Oct 22, 2014 at 2:56 PM, Osmos <osmoscity@gmail.com> wrote:
Hi there,
just doing some tests with Bird as route server, but the result was not the desired. Other staff like RTBH is running fine.
The situation is that next-hop is not modified (used only RS CLIENT option). All are eBGP sessions.
Usually that's the intended behavior of a route server. If you need something else have a look at the "next hop self" option, besides that you can set the next hop in filters using bgp_next_hop.
Thanks Frederik, is the intended behavior the one wanted to deploy. Found that AS_PATH is not modified but next-hop is modified to RS itself. Regards, Jorge.
El 22/10/2014, a las 15:20, Frederik Kriewitz <frederik@kriewitz.eu> escribió:
On Wed, Oct 22, 2014 at 2:56 PM, Osmos <osmoscity@gmail.com> wrote: Hi there,
just doing some tests with Bird as route server, but the result was not the desired. Other staff like RTBH is running fine.
The situation is that next-hop is not modified (used only RS CLIENT option). All are eBGP sessions.
Usually that's the intended behavior of a route server. If you need something else have a look at the "next hop self" option, besides that you can set the next hop in filters using bgp_next_hop.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 22.10.2014 14:56, Osmos wrote:
Hi there,
just doing some tests with Bird as route server, but the result was not the desired. Other staff like RTBH is running fine.
The situation is that next-hop is not modified (used only RS CLIENT option). All are eBGP sessions.
Hi Jorge! The next-hop shouldn't be modified. I was personally involved in many route servers deployments in many IXPs and I can assure you that nobody does that. Why do you need that? Ondrej
Checked some examples around and found no way to deploy correctly. Any advise or template to achieve this function?
Thanks in advance. Regards, Jorge.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJUR9QuAAoJED82D4RIDoWP71sQAJMqsupMCsMgJ/TFCsB2Giza YlNFCJWyMVe/4Mb2aSppARTOlOKvfXEqGu4CSQIFnf8TfjQWyMTGVoBkPu3+76vw sotJVNL4B2oDRn3dRZD/GFbbUf6acU0mmgVhyfCJfJRzJyLoZ4pEhkUESYNEqyKh akcAbLbnQ0XNqTCDIJNF4LjLaDOEsu6xno6YFgOx1kgnO80FLfBFfJ6Q4oSLYgSZ onSqjQjLQ9Ouw2ZocYd6eqvSz+vh9WQtF9x4sxyzpJMs51PVex/lLxoozUXeMxio Zcp6srAIBdGsm4BETNUlnGUZkAvXlWCbJuDaFuKtObSaGc8DMmQ7z7qYaCUUsp7t 7RCQt8x8NDqeD274c4p3leFzlg4y6+jXKAHFg/4Z8A9VVlumIvlhmt5pjvJD2xM+ jKDMmkHQzpR19d4CtELHmioKT8QT9hTwWMX3BJn7Q2BmL+lIv7+GlbXMn5W3lsfs CCCJv0UMZHupq0e51IMFftG/KfDlvtnb4sosft3Gy0wP/AKtlWa3Os9TBBUREGHW YkPzvdUYEMf4LnN+uXHu2PeIgtW9RRunCBUmXvR6XZlZz03n0a0SiQe5RZLWhskR TyYhoexbH2oXMxDxt9hiObp/hgnipu7ubFBv1EeD6aMgpFjVdZ+QNzgMw0ZJLiL8 Evo7uPoW9u91vKTeVrLD =1jht -----END PGP SIGNATURE-----
Hi Ondrej, will need to join the way that IXPs do. What I get is AS_PATH not modified and next-hop modified. RS clients get next-hop attribute of route sever itself. Regards, Jorge.
El 22/10/2014, a las 17:58, Ondrej Filip <feela@network.cz> escribió:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 22.10.2014 14:56, Osmos wrote: Hi there,
just doing some tests with Bird as route server, but the result was not the desired. Other staff like RTBH is running fine.
The situation is that next-hop is not modified (used only RS CLIENT option). All are eBGP sessions.
Hi Jorge! The next-hop shouldn't be modified. I was personally involved in many route servers deployments in many IXPs and I can assure you that nobody does that. Why do you need that?
Ondrej
Checked some examples around and found no way to deploy correctly. Any advise or template to achieve this function?
Thanks in advance. Regards, Jorge.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1
iQIcBAEBAgAGBQJUR9QuAAoJED82D4RIDoWP71sQAJMqsupMCsMgJ/TFCsB2Giza YlNFCJWyMVe/4Mb2aSppARTOlOKvfXEqGu4CSQIFnf8TfjQWyMTGVoBkPu3+76vw sotJVNL4B2oDRn3dRZD/GFbbUf6acU0mmgVhyfCJfJRzJyLoZ4pEhkUESYNEqyKh akcAbLbnQ0XNqTCDIJNF4LjLaDOEsu6xno6YFgOx1kgnO80FLfBFfJ6Q4oSLYgSZ onSqjQjLQ9Ouw2ZocYd6eqvSz+vh9WQtF9x4sxyzpJMs51PVex/lLxoozUXeMxio Zcp6srAIBdGsm4BETNUlnGUZkAvXlWCbJuDaFuKtObSaGc8DMmQ7z7qYaCUUsp7t 7RCQt8x8NDqeD274c4p3leFzlg4y6+jXKAHFg/4Z8A9VVlumIvlhmt5pjvJD2xM+ jKDMmkHQzpR19d4CtELHmioKT8QT9hTwWMX3BJn7Q2BmL+lIv7+GlbXMn5W3lsfs CCCJv0UMZHupq0e51IMFftG/KfDlvtnb4sosft3Gy0wP/AKtlWa3Os9TBBUREGHW YkPzvdUYEMf4LnN+uXHu2PeIgtW9RRunCBUmXvR6XZlZz03n0a0SiQe5RZLWhskR TyYhoexbH2oXMxDxt9hiObp/hgnipu7ubFBv1EeD6aMgpFjVdZ+QNzgMw0ZJLiL8 Evo7uPoW9u91vKTeVrLD =1jht -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 23.10.2014 14:06, Osmos wrote:
Hi Ondrej,
will need to join the way that IXPs do. What I get is AS_PATH not modified and next-hop modified.
RS clients get next-hop attribute of route sever itself.
I see. That's wrong. Can you send me you configuration? Ondrej
Regards, Jorge.
El 22/10/2014, a las 17:58, Ondrej Filip <feela@network.cz> escribió:
On 22.10.2014 14:56, Osmos wrote: Hi there,
just doing some tests with Bird as route server, but the result was not the desired. Other staff like RTBH is running fine.
The situation is that next-hop is not modified (used only RS CLIENT option). All are eBGP sessions.
Hi Jorge! The next-hop shouldn't be modified. I was personally involved in many route servers deployments in many IXPs and I can assure you that nobody does that. Why do you need that?
Ondrej
Checked some examples around and found no way to deploy correctly. Any advise or template to achieve this function?
Thanks in advance. Regards, Jorge.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJUSSmvAAoJED82D4RIDoWPRPsP/jAaqUsvUEkAXlJAjSGjn9zs ePysSQElFiIqNNcj67nKBTNc1HOUzCPdYdpLiDIJ/0mXBKP43EtOUhyC3bR7B6yy Kx68LkgRG1Xz23UmCzhVb3rhhAcGaadaeFZCzkoObPsHXwZyCI2MDbZPMP48HxXl w4/Dkn2916Kb7RIHZ1VN+UWTdb8rKTA3K9k6auTyWo5RS9FsAUUGN/XTlJWLEEeG LbrCYdeOXxP371NjtVGzwte5raB+AwcThlDsbUEhtBpQxJPYCo+S8ZKbwzqbvYXT fwEprUKdsc1cckOeJEdvYhUyEQERPeK1HXAJviIkyylVyRw4x6BBPSgO8+VmMbG8 yXCNDI9NgGleS8hy2ruBw7jWOge9A3I9F5pZjl5Y+VcAP/LxAVI8RqiXBl64hjPb gLoQEzDoBCU/0NIG+qkyNTiccEg0zaxRFZql3uk8XkFSWRg0Z8i6h3yBJXH154uj BPlSM7dsAjGSsn5aU0rodQeGHoZIBLlvpGx50YOdteAV3N43p2J75soksfge9Ii+ 7GoQs8PXvzIIGOKjCFJGkNFL0bSCXt5ZQH/GiQ4C6qWc78LkCY3EyAtUOt8/W688 8LxgFwZ6grjf6GrjIKOexMf66arZ+oPokCYmi+rRjRGeToZyksSSQqNtudqMiBZb +CpRRSlEn5AOcChHXVVG =+22l -----END PGP SIGNATURE-----
participants (4)
-
Frederik Kriewitz -
John Jensen -
Ondrej Filip -
Osmos