December 2018 - frog - lists.frrouting.org

v6 Route Replace semantics
by Donald Sharp 08 Apr '20

08 Apr '20

All - We recently introduced, into master, a new cli switch for zebra on linux `--v6-rr-semantics`. This was allow zebra to take advantage of the linux kernel getting v6 route replace semantics that is coming soon in the 4.18 linux kernel. So if you are on the bleeding edge of linux kernels and FRR you can start to take advantage of this new feature. What are Route Replace semantics you ask? Suppose we have a v6 route with 2 nexthops: S>* 4:6:7::/64 [1/0] via 1:2:3::4, enp0s3, 00:00:02 via 1:2:8::8, enp0s8, 00:00:02 Now suppose we remove a nexthop: robot# conf t robot(config)# no ipv6 route 5:7:9::/78 1:2:8::9 robot(config)# end robot# show ipv6 route [snip] S>* 5:7:9::/78 [1/0] via 1:2:3::4, enp0s3, 00:01:04 Let's look at the netlink notifications for this event: [ROUTE]5:7:9::/78 proto static metric 20 <----------- From creation of the 2x ecmp for 5:7:9::/78 nexthop via 1:2:3::4 dev enp0s3 weight 1 nexthop via 1:2:8::9 dev enp0s8 weight 1 [ROUTE]Deleted 5:7:9::/78 proto static metric 20 <---- We delete the route nexthop via 1:2:3::4 dev enp0s3 weight 1 nexthop via 1:2:8::9 dev enp0s8 weight 1 [ROUTE]5:7:9::/78 via 1:2:3::4 dev enp0s3 proto static metric 20 pref medium <----- We add it back in. In order to get the routes right in the kernel we had to delete the route first and then add it back in. Exposing a small window of packets being dropped while the route is fixed in the fib. Route Replace semantics tells the linux kernel to just replace the nexthops for the route. New packets coming in would immediately start using the new ecmp nexthop group path: [ROUTE]5:7:9::/78 proto static metric 20 nexthop via 1:2:3::4 dev enp0s3 weight 1 nexthop via 1:2:8::9 dev enp0s8 weight 1 [ROUTE]5:7:9::/78 via 1:2:3::4 dev enp0s3 proto static metric 20 pref medium thanks! donald

2 1

FRR on NRL CORE (fyi)
by Phil Wiggins 10 Apr '19

10 Apr '19

If anyone is interested in running FRR in the NRL CORE emulation environment, I have some build scripts for FRR on CORE that I posted at the first link below. Normally CORE runs Quagga, so this script was a hack to shoehorn FRR as a Quagga replacement. These scripts are not part of CORE yet, so are unsupported. People on this list may want to use CORE for FRR experimentation and testing, so you can customize these scripts to suit your own needs. It's best to run this stuff in a VM with no internet connection (after installation) since CORE runs lots of processes as root - a well-known security issue. https://github.com/coreemu/core/issues/170 ( install_frr_for_core.sh) FRR on NRL CORE build script - assumes Ubuntu 16.04.4 clean installation in a VM or physical host: https://gist.github.com/apwiggins/44f3592a61965783372aea5881ed9f7a (core_misc_frr.py ) used by the install script above to install at ./core/misc/frr.py https://gist.github.com/apwiggins/d610c2794c8c0a12a45bfc093fd2e949 (core_services_frr.py) used by the install script above to install at ./core/services/frr.py https://gist.github.com/apwiggins/747a9a14feff2ce3a3b8760406b825a7 https://www.nrl.navy.mil/itd/ncs/products/core The Common Open Research Emulator (CORE) is a tool for emulating networks on one or more machines. You can connect these emulated networks to live networks. CORE consists of a GUI for drawing topologies of lightweight virtual machines, and Python modules for scripting network emulation. Cheers, Phil

2 3

Question
by o1bigtenor 03 Jan '19

03 Jan '19

Greetings I cannot find the question in the 'frog' environment and the web isn't very useful so far - - - - so I'm going to those that live this networking stuff. Cheap routers seem to not work very well. Decent routers aren't cheap? What are the system requirements to use the 'frrouting' universe in the creating of a good quality but still home brew router? (Will something like a 64 bit Raspberry Pi work? How could I achieve 1000 MB network speeds on such a system? Likely more questions later.) If this is not an appropriate place to ask this - - - please do advise! Dee

5 11

setup and configuration
by o1bigtenor 01 Jan '19

01 Jan '19

Greetings I'm looking way beyond anything I've ever done before with this so please - - - if its stupid - - - I need to know (just don't hit me too hard - - - grin!) FRRouting looks like a very complete environment (what do I know but its got lots of things to set anyway!). If I purchase something like a sbc set up with say 2 GB of RAM and a 15 GB SDD I'm not sure how I would set things up. Is there a recipe for the noob crowd for what to do? (I'm seeing lots of options for things to ssetup and parameters to set but no having any idea on what to do makes the process more than somewhat intimidating. I'm thinking something like a router set up so that there are vlans separating a couple wired networks, one wireless network and possible another mesh network. I am wanting to be quite tough re: my security and privacy so want to very much reduce crosstalk between the lans.) TIA Dee

2 1

FRR (5.0) on latest pfSense 2.4.4p1 doesn't insert BGP routes into the kernel
by John Antypas 31 Dec '18

31 Dec '18

The subject basically says it all..... I have two sites connected over an IPSEC tunnel. Each site has its own internal routes managed by OSPF, and I am trying to exchange them by BGP. * We know the traffic is being passed over the IPSEC tunnel, and we can see that each side does get the other's BGP routes. We did have to install directives to allow multihop and disable-connection-checks.... * We do not see the routes being installed into the local kernel routing tables but for the life us, we can't understand why. We see the routes come across in the BGP debug info, but it never makes it into the FIB. Here's our BGPD.conf albeit for one side -- the other just has the AS numbers changed. # BGP Config router bgp 3000000 bgp router-id 10.0.0.5 redistribute connected redistribute static redistribute kernel redistribute ospf # BGP Neighbors neighbor 192.168.101.39 remote-as 2510000 neighbor 192.168.101.39 description Aaron Martin neighbor 192.168.101.39 update-source 10.0.0.5 address-family ipv4 unicast neighbor 192.168.101.39 activate neighbor 192.168.101.39 disable-connected-checks no neighbor 192.168.101.39 send-community neighbor 192.168.101.39 addpath-tx-bestpath-per-AS neighbor 192.168.101.39 allowas-in exit-address-family And here's what we see BGP table version is 208559, local router ID is 10.0.0.5, vrf id 0 Status codes: s suppressed, d damped, h history, * valid, > best, = multipath, i internal, r RIB-failure, S Stale, R Removed Nexthop codes: @NNN nexthop's vrf id, < announce-nh-self Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path 0.0.0.0 192.168.101.39 0 2510000 3000000 ? 192.168.101.39 0 0 2510000 ? *> 50.247.114.30 0 32768 ? 10.0.0.0 192.168.101.39 0 2510000 ? 10.0.0.0/16 192.168.101.39 0 2510000 3000000 ? *> 0.0.0.0 1 32768 ? 10.1.6.0/24 192.168.101.39 0 2510000 3000000 ? *> 0.0.0.0 1 32768 ? 10.10.10.1/32 192.168.101.39 1 0 2510000 ? 10.147.20.0/24 192.168.101.39 0 2510000 3000000 ? *> 10.0.1.5 110 32768 ? 50.247.114.16/28 192.168.101.39 0 2510000 3000000 ? *> 0.0.0.0 1 32768 ? 50.247.114.18/32 192.168.101.39 0 0 2510000 ? 64.62.134.130/32 192.168.101.39 0 2510000 3000000 ? *> 50.247.114.30 0 32768 ? 68.115.209.232/29 192.168.101.39 1 0 2510000 ? 68.115.209.237/32 192.168.101.39 0 2510000 3000000 ? *> 50.247.114.30 0 32768 ? 72.52.104.74/32 192.168.101.39 0 2510000 3000000 ? *> 50.247.114.30 0 32768 ? 172.16.0.0 192.168.101.39 0 2510000 ? 172.16.184.0/24 192.168.101.39 0 0 2510000 ? 172.16.231.0/24 192.168.101.39 1 0 2510000 ? 172.16.232.0/24 192.168.101.39 0 0 2510000 ? 172.16.238.0/24 192.168.101.39 1 0 2510000 ? 172.17.0.0 192.168.101.39 0 2510000 3000000 ? *> 10.0.1.5 110 32768 ? 172.21.0.0 192.168.101.39 0 2510000 ? 192.168.1.0 192.168.101.39 0 2510000 ? 192.168.101.39 0 0 2510000 ? 192.168.101.0 192.168.101.39 1 0 2510000 ? 192.168.101.39 0 2510000 ? 192.168.106.0 192.168.101.39 1 0 2510000 ? 192.168.101.39 0 2510000 ? 192.168.108.0 192.168.101.39 0 2510000 ? 192.168.121.0 192.168.101.39 0 2510000 ? 192.168.128.0 192.168.101.39 1 0 2510000 ? 192.168.101.39 0 2510000 ? 192.168.131.0 192.168.101.39 0 2510000 ? 192.168.132.0 192.168.101.39 0 2510000 ? 192.168.101.39 0 0 2510000 ? 192.168.148.0 192.168.101.39 1 0 2510000 ? 192.168.150.0 192.168.101.39 0 2510000 ? 192.168.228.0 192.168.101.39 0 2510000 3000000 ? *> 0.0.0.0 1 32768 ? 192.168.229.0 192.168.101.39 0 2510000 3000000 ? *> 0.0.0.0 1 32768 ? 196.101.2.0 192.168.101.39 0 2510000 ? 209.51.161.14/32 192.168.101.39 0 0 2510000 ? Displayed 33 routes and 50 total paths Everything's there, but it never makes it into the kernel. I'm sure we've done something wrong, because I tried a different BGP-based router at the other end, and I see the connection, but again, the routes don't seem to make it into the kernel -- clearly I've broken something basic :-)

4 4

configure: error: "you must use json-c library to use bfdd"
by Ron Hermsen 28 Dec '18

28 Dec '18

Hello, I'm trying to compile frr-6.0, but get the configure error "configure: error: "you must use json-c library to use bfdd"" I have json-c/json-c-dev 0.9 installed. What is the version requirement for json-c for compiling frr-6.0 with bfd support? More details: from configure: <snip> checking json-c/json.h usability... no checking json-c/json.h presence... no checking for json-c/json.h... no checking for json_object_get in -ljson-c... no checking for json_object_get in -ljson... yes <snip> configure: error: "you must use json-c library to use bfdd" JSON-C 0.9 details: json-c: /usr/local/lib/libjson.so /usr/local/lib/libjson.so.0 /usr/local/lib/libjson.so.0.0.1 json-c-dev: usr/local/include/json/json_tokener.h usr/local/include/json/json_object_private.h usr/local/include/json/json_object.h usr/local/include/json/json_util.h usr/local/include/json/printbuf.h usr/local/include/json/arraylist.h usr/local/include/json/linkhash.h usr/local/include/json/debug.h usr/local/include/json/bits.h usr/local/include/json/json.h usr/local/lib/pkgconfig/json.pc usr/local/lib/libjson.a usr/local/lib/libjson.la

1 0

Slack Access Request
by Shawn Olson 21 Dec '18

21 Dec '18

Hi there, I'd like to request access to your Slack Channel. We're an ISP in the northwestern region of the US and are beginning to implement FRR into our network. Love it so far - and would like to be more involved. Slack Username is shawn(a)fencepencil.com Thanks! Shawn Olson | Network Engineer Direct: (208) 286-4759 | Cell: (208) 985-6523 24-hour Customer Support: (800) 454-7214 Our Fiber Network Just Got Bigger Syringa Networks has completed the purchase of former Level 3 Metro Network Assets in the Treasure V<http://www.syringanetworks.net/>alley Syringa Networks | SyringaNetworks.net<http://www.syringanetworks.net/> _________________________ Privilege and Confidentiality Notice The information in this message is intended for the named recipients only. It may contain information that is privileged, confidential or otherwise protected from disclosure. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of this message is strictly prohibited. If you have received this e-mail in error, do not print it or disseminate it or its contents. In such event, please notify the sender by return e-mail and delete the e-mail file immediately thereafter. Thank you.

1 0

Create a BGP topology to run using SDN Controller?
by Kallol Karmakar 19 Dec '18

19 Dec '18

Hi, I want to create a simple BGP topology with SDN. Previously QUAGGA was used to create such topologies ( example: https://github.com/sdnds-tw/SDN-IP-Example-VM) Can you please guide me to create one. Simple network: Peer1(AS1)----R1(SDN Controller)-----Peer2(AS2) Thanks

2 1

Slack invite
by Soma Kelemen 11 Dec '18

11 Dec '18

Hi, Cloud I get an invite to slack? Thanks

2 1

Slack invite
by Craig Smith 11 Dec '18

11 Dec '18

Hello, Can I please get a Slack invite? Thanks, Craig

2 1