- dev - lists.frrouting.org

Debian packages repo not available
by Markus Melicher 13 Jul '19

13 Jul '19

Hello, the host https://deb.frrouting.org/ ,,For Debian/Ubuntu packages" is down. Is there a maintenance from your site? > dig deb.frrouting.org @8.8.8.8 > > ;; ANSWER SECTION: > deb.frrouting.org. 3331 IN A 185.142.180.129 > > ;; Query time: 17 msec > ;; SERVER: 8.8.8.8#53(8.8.8.8) > ;; WHEN: Thu Jul 11 11:04:29 CEST 2019 > ;; MSG SIZE rcvd: 62 > traceroute 185.142.180.129 > traceroute to 185.142.180.129 (185.142.180.129), 30 hops max, 60 byte > packets > 1 31.31.74.174 (31.31.74.174) 0.843 ms 1.166 ms 1.331 ms > 2 r4-b.wedos.net (46.28.104.36) 0.463 ms 0.372 ms 0.272 ms > 3 hu0-1-0-1.ccr21.prg01.atlas.cogentco.com (149.6.25.177) 4.530 ms > 2.888 ms 3.331 ms > 4 gtt.prg01.atlas.cogentco.com (130.117.14.50) 2.583 ms 2.566 ms > 4.295 ms > 5 et-2-1-5.cr1-fra6.ip4.gtt.net (213.200.114.173) 16.824 ms 16.724 > ms 16.621 ms > 6 ip4.gtt.net (46.33.85.226) 32.412 ms 30.450 ms 32.253 ms > 7 SNLEJ-MC04.hlkomm.net (109.104.61.164) 30.132 ms 31.766 ms > 31.978 ms > 8 edge1.lej.westnetz.org (185.142.181.254) 31.637 ms 31.754 ms > 31.617 ms > 9 v1998.ar1.lej.westnetz.org (185.142.181.129) 30.307 ms 30.205 ms > 30.098 ms > 10 v1998.ar1.lej.westnetz.org (185.142.181.129) 1945.897 ms !H > 1945.824 ms !H 1945.722 ms !H > > ping 185.142.180.129 > PING 185.142.180.129 (185.142.180.129) 56(84) bytes of data. > From 185.142.181.129 icmp_seq=2 Destination Host Unreachable > Best Regards, Markus.

3 2

Get router adresses from zebra
by p.issartel64＠gmail.com 12 Jul '19

12 Jul '19

Hello, I am developping my own routing deamon based on the Zebra API included in FR Route ing. My deamon works and I am able to receive routes from zebra. I can get prefix and nexthop adresses (from ospf routers on dockers) but my problem is that I want to get routers IP adresses (or ID) of the routes I got. For the moment, I am basing my work on the ospf deamon. But I don’t understand how (and where in the code) ospf->new_rtrs is set from routes received. How can I get the routers ip adresses sent by ospf/zebra on my deamon ? Thank you for your answers. Pierre I.

2 1

IS-IS and EIGRP md5 authentication not working?
by Michal Ruprich 09 Jul '19

09 Jul '19

I have been trying to run a simple IS-IS configuration between two routers and it seems that the neighborship between the two stays established even when one is configured with md5 authentication and the other is not. Is the message-digest for IS-IS actually working? I did not have enough time to look in the code to see whether it is actually used so I am asking here whether this is a known issue or not? Also, I have a similar question for EIGRP. When configured without authentication, two neighbors are established and some routing information exchanged. When I tried to configure md5 authentication on one side, funny thing happened - the router WITH the authentication still accepted hello packets from the other router and listed this router as neighbor. The router WITHOUT authentication did not list the other one as neighbor but also refused to remove previously received routing information from the routing table. When authentication is enabled on both sides, the neighborship fails and is never established again. This leads me to an assumption that the message-digest does not work with EIGRP. Did anyone else encounter this? EIGRP example here: *Router with authentication:* interface eth0 ip authentication key-chain eigrp 1 eigrp ip authentication mode eigrp 1 md5 key chain eigrp key 1 key-string secure_eigrp router eigrp 1 network 10.0.136.0/22 network 192.168.2.0/24 #dummy interface just for route exchange # sh ip eigrp neighbors H Address Interface Hold Uptime SRTT RTO Q Seq (sec) (ms) Cnt Num 0 10.0.136.125 eth0 14 0 0 2 0 2 *Router without authentication:* router eigrp 1 network 10.0.136.0/22 # sh ip eigrp neighbors H Address Interface Hold Uptime SRTT RTO Q Seq (sec) (ms) Cnt Num <empty> # sh ip route E>* 192.168.2.0/24 [90/30720] via 10.0.136.87, eth0, 00:04:45 Thanks for any info or ideas about this. Regards, Michal

2 1

FRR crypto in Fedora and RHEL
by Michal Ruprich 01 Jul '19

01 Jul '19

Hi all, now that FRR is making its way to Fedora, perhaps it will eventually make its way to RHEL-8 as well. In both Fedora and RHEL, we are tying to make sure that every package that uses cryptographic algorithms and protocols uses these correctly. Crypto algorithms are not easy to implement and we are trying to encourage developers to use system libraries that have been certified as secure and well implemented. With every crypto algorithm that is implemented from scratch, it brings a potential security risk to the system. In FRR, md5 and sha256 are used as authentication methods for various routing daemons. These are implemented from scratch. This creates an issue for us and it could eventually result in FRR not getting in RHEL-8 at all. I would like to ask you, whether you would be willing to use system libraries to implement these algorithms. I will do all the work and provide patches and pull requests, of course. I believe that getting FRR into RHEL-8 is worth it. Regards, Michal Ruprich

2 3

frr.serive - FFRouting
by Melvin Jude E. Rosario 25 Jun '19

25 Jun '19

Hello, I have been running into the same issue for quite some time now and unsure of how to fix it. Is there any way to fix the problems given below? -------------------------------------------------------------------------------------------------------------------------------- root@ubuntu:/frr/tools# systemctl start frr ? Job for frr.service failed because the control process exited with error code. See "systemctl status frr.service" and "journalctl -xe" for details. root@ubuntu:/frr/tools# systemctl status frr.service ? frr.service - FRRouting Loaded: loaded (/etc/systemd/system/frr.service; enabled; vendor preset: enab Active: failed (Result: exit-code) since Mon 2019-06-24 11:26:24 CST; 45s ago Docs: https://frrouting.readthedocs.io/en/latest/setup.html Process: 22304 ExecStart=/usr/lib/frr/frrinit.sh start (code=exited, status=20 Jun 24 11:26:24 ubuntu systemd[1]: Starting FRRouting... Jun 24 11:26:24 ubuntu systemd[1]: frr.service: Control process exited, code=exi Jun 24 11:26:24 ubuntu systemd[1]: Failed to start FRRouting. Jun 24 11:26:24 ubuntu systemd[1]: frr.service: Unit entered failed state. Jun 24 11:26:24 ubuntu systemd[1]: frr.service: Triggering OnFailure= dependenci Jun 24 11:26:24 ubuntu systemd[1]: frr.service: Failed to enqueue OnFailure= job Jun 24 11:26:24 ubuntu systemd[1]: frr.service: Failed with result 'exit-code'. CONFIDENTIALITY NOTICE: This message (including any attachments) contains information that is confidential and proprietary to GTA and/or TeleGuam Holdings LLC, and that is for the sole use of the intended recipients. If you are not an intended recipient, you may not read, print, retain, use, copy, distribute, forward or disclose to anyone this message or any information contained in this message (including any attachments). If you have received this message in error, please advise the sender of this error by reply e-mail, and please destroy all copies of this message (including any attachments).

2 1

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

slack invite
by amit sardana 20 Jun '19

20 Jun '19

Hi all, can I have a slack invite for the channel? Thanks, Amit

2 1

babeld: minimal updates for compliance with RFC 6126bis
by laure merat 19 Jun '19

19 Jun '19

Hi, I'm a master's student doing an internship with Juliusz Chroboczek. I've updated Babel to the last specification (you can find my work at https://github.com/lmerat46/frr) I would be very grateful if you could review it and tell me if you have any comments before I do the merge request (should be next week, Juliusz still has to check some things)! Best regards, Laure Mérat

2 1

VxLAN and Linux Kernel support
by Rubens 19 Jun '19

19 Jun '19

Hello everyone, We are currently trying to deploy a VxLAN setup on a Linux distribution that is based on the Linux Kernel Version 4.9.161, and FRR version 6.0.2. We have as well confirmed that it is working on kernel version 4.20. It looks like we don't see the ARP request being propagated through the setup. As it stands, trying to backport the patches required for this feature does not seem to be working correctly, and it is currently impossible for us to move forward in the kernel versions. As such, would anyone be able to give a pointer to some kernel patches, or other possible solutions that would be able to get the VxLAN correctly working on this platform by backporting the correct patches? Thank you, Rubens -- Rubens <rubens(a)bisdn.de>

2 1

Nominate people to be maintainers
by Philippe Guibert 19 Jun '19

19 Jun '19

All - I would like to nominate Donatas Abraitis to be maintainer to the FRR project. He has contributed in the FRR code and already made a great job until now. thanks! Philippe

2 1