April 2019 - dev - lists.frrouting.org

Regarding support for rsvp-te support in free routing
by Rhene Kavi 20 Feb '20

20 Feb '20

Hi All, Do we have any plans to support rsvp-te Thanks in advance KaviRhene

4 3

FRR on NRL CORE (fyi)
by Phil Wiggins 22 Aug '19

22 Aug '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

3 6

FRR coming to Fedora
by Michal Ruprich 24 Jun '19

24 Jun '19

Hi all, I am happy to announce that I have started a review process for FRR to be added to Fedora[1]. After we figure out all the packaging details, FRR will be available in F29 and higher. I need to mention one important thing. I have added the latest version of FRR but *without* *babeld* and *ldpd* modules. These two modules are still having licensing issues and I will not include them in the distro unless all these issues are resolved. Regards, Michal Ruprich -------------------------------- [1] https://bugzilla.redhat.com/show_bug.cgi?id=1702720

3 5

FRR build system "workshop"
by David Lamparter 28 May '19

28 May '19

Hi FRR-dev, I'll be doing a session on FRR's build system, workshop-style-ish. If you're interested, please check https://xoyondo.com/dp/IBeddxPPB3cFIZG for date/time coordination. Cheers, -David

4 7

ask for Ubuntu 19.04 (disco) support.
by xiaoyu.net 30 Apr '19

30 Apr '19

Hello, I am using ubuntu 19.04, i want to ask for get this support, how i do it? Ign:7 https://deb.frrouting.org/frr disco InRelease Err:8 https://deb.frrouting.org/frr disco Release 404 Not Found [IP: 185.142.180.129 443] Reading package lists... Done E: The repository 'https://deb.frrouting.org/frr disco Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. ***************************************************** Best Service and Trustworthy From Us Our Mail Server Support IPv6 & IPv4 Mail ======================================================

1 0

discard interface warnings on FreeBSD
by Mike Tancsa 29 Apr '19

29 Apr '19

I have been using the discard interface - DISC(4) - on FreeBSD for some time to tie down supernets. On frr7, I am getting a warning message at startup I am not sure what to make of The nic is configured as # ifconfig disc0 disc0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 65532 inet 10.128.128.144 netmask 0xfffffff8 inet 10.129.129.1 netmask 0xfffffff0 inet6 2001:db8::1 prefixlen 64 inet6 fe80::1%disc0 prefixlen 64 scopeid 0x7 groups: disc nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> And at startup, I get /usr/local/etc/rc.d/frr start Checking zebra.conf 2019/04/26 15:58:44 warnings: ZEBRA: [EC 4043309141] warning: interface disc0 broadcast addr 10.128.128.144/29 != calculated 10.128.128.151, routing protocols may malfunction 2019/04/26 15:58:44 warnings: ZEBRA: [EC 4043309141] warning: interface disc0 broadcast addr 10.129.129.1/28 != calculated 10.129.129.15, routing protocols may malfunction 2019/04/26 15:58:44 warnings: ZEBRA: [EC 4043309105] Disabling MPLS support (no kernel support) OK Starting zebra. 2019/04/26 15:58:44 warnings: ZEBRA: [EC 4043309141] warning: interface disc0 broadcast addr 10.128.128.144/29 != calculated 10.128.128.151, routing protocols may malfunction 2019/04/26 15:58:44 warnings: ZEBRA: [EC 4043309141] warning: interface disc0 broadcast addr 10.129.129.1/28 != calculated 10.129.129.15, routing protocols may malfunction 2019/04/26 15:58:44 warnings: ZEBRA: [EC 4043309105] Disabling MPLS support (no kernel support) If I use the same IP info on another non discard interface it works / doesnt complain. Also, when starting staticd, I get these warnings as well. Checking staticd.conf 2019/04/26 15:58:44 warnings: STATIC: void static_zebra_nht_register(struct static_route *, _Bool): Failure to send nexthop to zebra 2019/04/26 15:58:44 warnings: STATIC: void static_zebra_nht_register(struct static_route *, _Bool): Failure to send nexthop to zebra 2019/04/26 15:58:44 warnings: STATIC: void static_zebra_nht_register(struct static_route *, _Bool): Failure to send nexthop to zebra 2019/04/26 15:58:44 warnings: STATIC: void static_zebra_nht_register(struct static_route *, _Bool): Failure to send nexthop to zebra 2019/04/26 15:58:44 warnings: STATIC: void static_zebra_nht_register(struct static_route *, _Bool): Failure to send nexthop to zebra 2019/04/26 15:58:44 warnings: STATIC: void static_zebra_nht_register(struct static_route *, _Bool): Failure to send nexthop to zebra 2019/04/26 15:58:44 warnings: STATIC: void static_zebra_nht_register(struct static_route *, _Bool): Failure to send nexthop to zebra 2019/04/26 15:58:44 warnings: STATIC: void static_zebra_nht_register(struct static_route *, _Bool): Failure to send nexthop to zebra 2019/04/26 15:58:44 warnings: STATIC: void static_zebra_nht_register(struct static_route *, _Bool): Failure to send nexthop to zebra 2019/04/26 15:58:44 warnings: STATIC: void static_zebra_nht_register(struct static_route *, _Bool): Failure to send nexthop to zebra 2019/04/26 15:58:44 warnings: STATIC: void static_zebra_nht_register(struct static_route *, _Bool): Failure to send nexthop to zebra 2019/04/26 15:58:44 warnings: STATIC: void static_zebra_nht_register(struct static_route *, _Bool): Failure to send nexthop to zebra 2019/04/26 15:58:44 warnings: STATIC: void static_zebra_nht_register(struct static_route *, _Bool): Failure to send nexthop to zebra 2019/04/26 15:58:44 warnings: STATIC: void static_zebra_nht_register(struct static_route *, _Bool): Failure to send nexthop to zebra 2019/04/26 15:58:44 warnings: STATIC: void static_zebra_nht_register(struct static_route *, _Bool): Failure to send nexthop to zebra 2019/04/26 15:58:44 warnings: STATIC: void static_zebra_nht_register(struct static_route *, _Bool): Failure to send nexthop to zebra 2019/04/26 15:58:44 warnings: STATIC: void static_zebra_nht_register(struct static_route *, _Bool): Failure to send nexthop to zebra 2019/04/26 15:58:44 warnings: STATIC: void static_zebra_nht_register(struct static_route *, _Bool): Failure to send nexthop to zebra 2019/04/26 15:58:44 warnings: STATIC: void static_zebra_nht_register(struct static_route *, _Bool): Failure to send nexthop to zebra OK Starting staticd. Looking at the installed routes, it looks ok, except for one which I must be missing something obvious, but its ok on quagga and frr6 I have interface igb1.6: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=600703<RXCSUM,TXCSUM,TSO4,TSO6,LRO,RXCSUM_IPV6,TXCSUM_IPV6> ether 90:e2:ba:01:37:81 inet6 fe80::92e2:baff:fe01:3781%igb1.6 prefixlen 64 scopeid 0xe inet 64.7.149.177 netmask 0xfffffffc broadcast 64.7.149.179 and a static route of ip route 10.87.1.0/30 64.7.149.178 It ends up installing this static route on the discard interface for some reason on frr7. On frr6, it works. next hop is 64.7.149.178. I do get the same warning messages however at startup. On frr5, its the same as frr7. # vtysh -c "show ip route 10.87.1.0/30" Routing entry for 10.87.1.0/30 Known via "static", distance 1, metric 0, best Last update 00:00:14 ago 64.7.149.178 (recursive) * 10.129.129.1, via disc0 kernel confirms # netstat -nr | grep ^10.87.1. 10.87.1.0/30 10.129.129.1 UG1 disc0 # Any ideas what up ? As this is just a test box, there is no MAC addr for the next hop, but would it not mark the route as inactive rather than change the next hop to the discard interface ? ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 x203 Sentex Communications, mike(a)sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada

3 2

some questions about zebra in frr
by sudhanshu kumar 29 Apr '19

29 Apr '19

Hi, I have 2 questions about zebra in frr. 1. why do we maintain 2 types (source and destination route type) in zebra. I am not sure what source route type means ? Is it the source of the route (like the packet source or the neighbor from which the route got learnt) ? 2. How does frr routing stack interact with SONIC platform. I see that it has a TCP socket with SONIC which it uses to send messages for all protocols. Is it true ? Thanks, Sudhanshu ---------- Forwarded message --------- From: sudhanshu kumar <sudhanshu22(a)gmail.com> Date: Thu, Apr 25, 2019 at 12:06 PM Subject: help: frr interaction with SONIC To: <dev-request(a)lists.frrouting.org> Hi, I would like to know how does frr routing stack interact with SONIC platform. I see that it has a TCP socket with SONIC which it uses to send messages for all protocols. Is it true ? Thanks & Regards, Sudhanshu

2 3

Request to join Development Mailing List
by Rakesh Garg 29 Apr '19

29 Apr '19

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10 ________________________________ This e-mail message may contain confidential or proprietary information of Mavenir Systems, Inc. or its affiliates and is intended solely for the use of the intended recipient(s). If you are not the intended recipient of this message, you are hereby notified that any review, use or distribution of this information is absolutely prohibited and we request that you delete all copies in your control and contact us by e-mailing to security(a)mavenir.com. This message contains the views of its author and may not necessarily reflect the views of Mavenir Systems, Inc. or its affiliates, who employ systems to monitor email messages, but make no representation that such messages are authorized, secure, uncompromised, or free from computer viruses, malware, or other defects. Thank You

1 0

Anyone using FPM and netlink encoding?
by Donald Sharp 24 Apr '19

24 Apr '19

Hi! I've been asked about netlink encoding that the FPM uses and it's possible expansion to include more data that we have in the rib. If you are using this please respond here and let us know. We would like to talk with you about expanding the api. thanks! donald

1 0

Ubuntu 14.04 LTS (trusty) Packages
by Sullivan (US), Scott C 17 Apr '19

17 Apr '19

Looking for Ubuntu 14.04 LTS (trusty) FRR packages for arm64. When following the install directions for building and installing FRR for Ubuntu 14.04, I can successfully compile/install, however get the following error when trying to start FRR: smc@SHARC16-WG1:~/frr$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.04.5 LTS Release: 14.04 Codename: trusty Architecture = aarch64 smc@SHARC16-WG1:~/frr$ sudo /etc/init.d/frr start Loading capability module if not yet done. 2019/04/11 17:43:58 errors: ZEBRA: libyang: Invalid arguments (ly_ctx_get_node()). 2019/04/11 17:43:58 warnings: ZEBRA: [EC 100663321] nb_load_callbacks: unknown data path: `▒ core_handler: showing active allocations in memory group libfrr core_handler: memstats: Host config : 1 * 12 core_handler: memstats: Command Tokens : 594 * 56 core_handler: memstats: Command Token Text : 483 * (variably sized) core_handler: memstats: Command Token Help : 483 * (variably sized) core_handler: memstats: Command Argument Name : 47 * (variably sized) core_handler: memstats: Graph : 7 * 4 core_handler: memstats: Graph Node : 721 * 16 core_handler: memstats: Hash : 20 * (variably sized) core_handler: memstats: Hash Bucket : 179 * 16 core_handler: memstats: Hash Index : 10 * (variably sized) core_handler: memstats: Hook entry : 2 * 28 core_handler: memstats: Link List : 4 * 20 core_handler: memstats: Link Node : 11 * 12 core_handler: memstats: Logging : 1 * 56 core_handler: memstats: Temporary memory : 1 * 9 core_handler: memstats: Northbound Node : 5 * 320 core_handler: memstats: Priority queue : 1 * 20 core_handler: memstats: Priority queue data : 1 * 128 core_handler: memstats: Privilege information : 2 * (variably sized) core_handler: memstats: Thread master : 3 * (variably sized) core_handler: memstats: Thread Poll Info : 2 * 4096 core_handler: memstats: Vector : 1459 * 12 core_handler: memstats: Vector index : 1459 * (variably sized) core_handler: memstats: YANG module : 1 * 24 core_handler: showing active allocations in memory group Label Manager core_handler: showing active allocations in memory group zebra core_handler: showing active allocations in memory group Table Manager /etc/init.d/frr: line 117: 20327 Aborted ${SSD} --start --pidfile=`pidfile $dmn` --exec "$D_PATH/$dmn" -- `eval echo "$""$dmn""_options"` Thanks, Scott

2 1