December 2020 - frog - lists.frrouting.org

Yocto Recipe for FRR
by Amol Lad 10 Aug '21

10 Aug '21

Hi, Please advise if there is any Yocto recipe for FRRouting? If not, how to go about creating one for FRR? Yocto Recipe for FRR will hugely simplify integrating FRR in Yocto based embedded linux distributions. So please advise if there are any plans to develop this recipe? Thanks Amol ________________________________ The information in this email communication (inclusive of attachments) is confidential to 4RF Limited and the intended recipient(s). If you are not the intended recipient(s), please note that any use, disclosure, distribution or copying of this information or any part thereof is strictly prohibited and that the author accepts no liability for the consequences of any action taken on the basis of the information provided. If you have received this email in error, please notify the sender immediately by return email and then delete all instances of this email from your system. 4RF Limited will not accept responsibility for any consequences associated with the use of this email (including, but not limited to, damages sustained as a result of any viruses and/or any action or lack of action taken in reliance on it).

4 10

Binding two IP addresses to bgpd
by Matt Riffle 04 Mar '21

04 Mar '21

Apologies if I’m missing something easy here — I think I’ve looked at this for too long. I want my bgpd process to listen to 2 IP addresses — one IPv4 and one IPv6. I cannot find a syntax that allows this to happen. I can listen to one or the other. I really don’t want to run two bgpd processes to accomplish it. (I could let it bind to the default 0.0.0.0 / :: and use a firewall, but, again, I’d rather just bind to the two addresses I need it on, if possible.) Thanks, -Matt

6 6

nhrpd event manager
by Joe Maimon 01 Mar '21

01 Mar '21

I have successfully gotten frr,nhrpd,strongswan,charon all running on another system for a dmvpn application. I am currently trying to do another setup, but without vpn/ipsec, just nhrp/gre. Its not working out well, debug logs show Netlink: Received msg_type 28 which if I recall correctly suggests that the neighbor entry isnt being installed correctly, trying it as root worked even less. So while poking around, I see there is an entire event manager unix sock structure. Perhaps I can parse that and do it myself? However, this is as far as I got. I am interacting with it via shell script. Mar 15 08:11:35 debian67 nhrpd[20977]: evmgr: sending event authorize-binding Mar 15 08:11:35 debian67 nhrpd[20977]: Send Registration-Reply(4) 192.168.241.129 -> 192.168.241.130 Mar 15 08:11:35 debian67 nhrpd[20977]: PACKET: Send 45.77.146.76 -> 209.51.164.27 Mar 15 08:11:35 debian67 nhrpd[20977]: evmgr: msg: eventid=214 Mar 15 08:11:35 debian67 nhrpd[20977]: evmgr: msg: result=accept Mar 15 08:11:35 debian67 nhrpd[20977]: evmgr: msg: Mar 15 08:11:35 debian67 nhrpd[20977]: evmgr: received: eventid=214 result= Mar 15 08:11:45 debian67 nhrpd[20977]: cache: t67 192.168.241.130: timeout Mar 15 08:11:46 debian67 nhrpd[20977]: Netlink: Received msg_type 28, msg_flags 0 I have looked at the source and I cant seem to convince the function to recognize that result should be "accept". Any advice appreciated. Joe For the interested, the below is the fledgling script #!/bin/bash PROGNAME=`basename $0` VERSION="0.0.1" usage() { echo "Usage: $PROGNAME -s nhrp-sock [-i interface-name] [-u user] [-g group] " echo "" echo "-s nhrp-sock file" echo "-i interface-name to execute on, may be repeated multiple times" echo "-u user to own the sock" echo "-g group to own the sock" exit 1 } SOCK="/var/run/frr/nhrp.sock" USER="frr" GROUP="frr" j=0 while getopts s:i:u:g: opt; do case "$opt" in s) SOCK="$OPTARG" ;; i) INTARR[((j++))]="$OPTARG" ;; u) USER="$OPTARG" ;; g) GROUP="$OPTARG" ;; esac; done coproc socat - UNIX-LISTEN:$SOCK,unlink-early,setuid-early=$USER || exit 1 OLDIFS="$IFS" while read -r S; do if [[ "$S" == "" ]]; then if [[ "$EVID" != "" ]]; then echo -e "eventid=$EVID\nresult=accept\n"; fi unset EVID unset EVINT continue; fi IFS="${IFS}=" SA=($S) IFS="$OLDIFS" case "${SA[0]}" in eventid) EVID="${SA[1]}" ;; interface) EVINT="${SA[1]}" esac done <&"${COPROC[0]}" >&"${COPROC[1]}" kill "$COPROC_PID"

2 3

IPv6 /128 peers, VRF import issues.
by Brandon Jackson 31 Dec '20

31 Dec '20

Hey peeps hoping someone here has a solution or some idea on this, and maybe this just isn't possible but I figured id let people with much more FRR skill than me let me know.. So, I am trying to solve an issue with IPv6 /128 peers and VRF importing. This is on Ubuntu 20.04.1 with FRR 7.5-0~ubuntu20.04 I have 2 VRFs, the default and dn42 (table 42), currently I import both VRFs into each other for IPv4 and IPv6. In my default VRF I only have 1 downstream peer that is my own, all of my other peers are in the dn42 VRF. I have no issues when my BGP peers are in the same subnet as me, such as links using /64s to /127s etc. All routes import and get installed on this host in both VRFs But I do have an issue when usings links with /128s, peering comes up routes are exchanged and no issues using any of the received routes on the dn42 VRF, they are installed and work perfectly in the dn42 VRF. However the routes are never installed in the default VRF table of the host, but they are announced to my downstream peer by FRR, but when a packet comes in for the affected route it follows the default route instead of getting routed into the VRF and beyond because there is no route in the default table for it. I will note these are Multiprotocol peering sessions and IPv4 is working fine, this only affects IPv6. And static routes for the /128 are installed via "ip route add..", also tried adding via FRR as a test, no change of course. Also note, I have 3 peers with /128 links, this affects them all, just including one example. I have included a broken peer using the /128s, and a working peer using a /127, though again peers/links using /64 - /127s are fine. Broken Peer Peer AS: 4242421080 Interface: wg1080 My IPv6: fda9:26a9:1c47:d42:42:42:1080:1050/128 Peer Ipv6: fd86:bad:11b7:9::1/128 Working Peer Peer AS: 4242422601 Interface: wg2601 My IPv6: fda9:26a9:1c47:d42:42:42:2601:1050/127 Peer Ipv6: fda9:26a9:1c47:d42:42:42:2601:1051/127 ***********Snipped relevant peers*********** ATL1-US.napshome.dn42# show ipv6 nht vrf dn42 fd86:bad:11b7:9::1 resolved via static is directly connected, wg1080 Client list: bgp(fd 16) fda9:26a9:1c47:d42:42:42:2601:1051(Connected) resolved via connected is directly connected, wg2601 Client list: bgp(fd 16) ************************************* *********Broken Route**************** ATL1-US.napshome.dn42# show ipv6 route vrf dn42 fd86:bad:11b7::/48 Routing entry for fd86:bad:11b7::/48 Known via "bgp", distance 20, metric 0, vrf dn42, best Last update 02:04:19 ago fd86:bad:11b7:9::1 (recursive), weight 1 * fd86:bad:11b7:9::1, via wg1080 onlink, weight 1 ATL1-US.napshome.dn42# show ipv6 route fd86:bad:11b7::/48 Routing entry for fd86:bad:11b7::/48 Known via "bgp", distance 200, metric 0 Last update 2d00h44m ago fd86:bad:11b7:9::1(vrf dn42) inactive, weight 1 ************************************* Note: inactive in default VRF *********Broken Route**************** ip -6 route list fd86:bad:11b7::/48 <Blank/Nothing> ip -6 route list table 42 fd86:bad:11b7::/48 fd86:bad:11b7::/48 nhid 2095953 via fd86:bad:11b7:9::1 dev wg1080 proto bgp metric 20 onlink pref medium ************************************* *********Working Route*************** ATL1-US.napshome.dn42# show ipv6 route vrf dn42 fd42:4242:2601::/48 Routing entry for fd42:4242:2601::/48 Known via "bgp", distance 20, metric 0, vrf dn42, best Last update 02:07:13 ago * fe80::42:2601:2e:1, via wg2601, weight 1 ATL1-US.napshome.dn42# show ipv6 route fd42:4242:2601::/48 Routing entry for fd42:4242:2601::/48 Known via "bgp", distance 200, metric 0, best Last update 2d00h47m ago * fe80::42:2601:2e:1, via wg2601(vrf dn42), weight 1 ************************************* *********Working Route*************** ip -6 route list fd42:4242:2601::/48 fd42:4242:2601::/48 nhid 2094697 via fe80::42:2601:2e:1 dev wg2601 proto bgp metric 20 pref medium ip -6 route list table 42 fd42:4242:2601::/48 fd42:4242:2601::/48 nhid 2094697 via fe80::42:2601:2e:1 dev wg2601 proto bgp metric 20 pref medium ************************************* *********Broken Peer*************** ATL1-US.napshome.dn42# show bgp vrf dn42 neighbors fd86:bad:11b7:9::1 BGP neighbor is fd86:bad:11b7:9::1, remote AS 4242421080, local AS 4242421050, external link Description: jlu5-dn42-ATL Member of peer-group DN42fullpeer for session parameters BGP version 4, remote router ID 172.20.229.119, local router ID 172.22.169.128 BGP state = Established, up for 2d00h48m Last read 00:00:19, Last write 00:00:02 Hold time is 180, keepalive interval is 60 seconds Neighbor capabilities: 4 Byte AS: advertised and received AddPath: IPv4 Unicast: RX advertised IPv4 Unicast IPv6 Unicast: RX advertised IPv6 Unicast Route refresh: advertised and received(new) Address Family IPv4 Unicast: advertised and received Address Family IPv6 Unicast: advertised and received Hostname Capability: advertised (name: ATL1-US.napshome.dn42,domain name: n/a) not received Graceful Restart Capability: advertised and received Remote Restart timer is 120 seconds Address families by peer: none Graceful restart information: End-of-RIB send: IPv4 Unicast, IPv6 Unicast End-of-RIB received: IPv4 Unicast, IPv6 Unicast Local GR Mode: Helper* Remote GR Mode: Helper R bit: False Timers: Configured Restart Time(sec): 120 Received Restart Time(sec): 120 IPv4 Unicast: F bit: False End-of-RIB sent: Yes End-of-RIB sent after update: No End-of-RIB received: Yes Timers: Configured Stale Path Time(sec): 360 IPv6 Unicast: F bit: False End-of-RIB sent: Yes End-of-RIB sent after update: No End-of-RIB received: Yes Timers: Configured Stale Path Time(sec): 360 Message statistics: Inq depth is 0 Outq depth is 0 Sent Rcvd Opens: 3 3 Notifications: 2 0 Updates: 1697133 320409 Keepalives: 5638 6440 Route Refresh: 1 6 Capability: 0 0 Total: 1702777 326858 Minimum time between advertisement runs is 0 seconds Update source is wg1080 For address family: IPv4 Unicast DN42fullpeer peer-group member Update group 3, subgroup 57 Packet Queue length 0 MED is propagated unchanged to this neighbor Community attribute sent to this neighbor(all) Inbound path policy configured Outbound path policy configured Route map for incoming advertisements is *rm-fullpeer-in Route map for outgoing advertisements is *rm-fullpeer-out 444 accepted prefixes For address family: IPv6 Unicast DN42fullpeer peer-group member Update group 4, subgroup 58 Packet Queue length 0 Inbound soft reconfiguration allowed MED is propagated unchanged to this neighbor Community attribute sent to this neighbor(all) Inbound path policy configured Outbound path policy configured Route map for incoming advertisements is *rm-fullpeer-in Route map for outgoing advertisements is *rm-fullpeer-out 335 accepted prefixes Connections established 3; dropped 2 Last reset 2d00h48m, Peer closed the session Local host: fda9:26a9:1c47:d42:42:42:1080:1050, Local port: 40287 Foreign host: fd86:bad:11b7:9::1, Foreign port: 179 Nexthop: 172.22.169.128 Nexthop global: fda9:26a9:1c47:d42:42:42:1080:1050 Nexthop local: :: BGP connection: non shared network BGP Connect Retry Timer in Seconds: 30 Estimated round trip time: 8 ms Read thread: on Write thread: on FD used: 49 ************************************* *********Working Peer*************** ATL1-US.napshome.dn42# show bgp vrf dn42 neighbors fda9:26a9:1c47:d42:42:42:2601:1051 BGP neighbor is fda9:26a9:1c47:d42:42:42:2601:1051, remote AS 4242422601, local AS 4242421050, external link Description: Burble-dn42-us-CHI1 Member of peer-group DN42fullpeer for session parameters BGP version 4, remote router ID 193.29.63.150, local router ID 172.22.169.128 BGP state = Established, up for 2d00h48m Last read 00:00:29, Last write 00:00:10 Hold time is 180, keepalive interval is 60 seconds Neighbor capabilities: 4 Byte AS: advertised and received AddPath: IPv4 Unicast: RX advertised IPv4 Unicast IPv6 Unicast: RX advertised IPv6 Unicast Route refresh: advertised and received(new) Address Family IPv4 Unicast: advertised and received Address Family IPv6 Unicast: advertised and received Hostname Capability: advertised (name: ATL1-US.napshome.dn42,domain name: n/a) not received Graceful Restart Capability: advertised and received Remote Restart timer is 120 seconds Address families by peer: none Graceful restart information: End-of-RIB send: IPv4 Unicast, IPv6 Unicast End-of-RIB received: IPv4 Unicast, IPv6 Unicast Local GR Mode: Helper* Remote GR Mode: Helper R bit: False Timers: Configured Restart Time(sec): 120 Received Restart Time(sec): 120 IPv4 Unicast: F bit: False End-of-RIB sent: Yes End-of-RIB sent after update: No End-of-RIB received: Yes Timers: Configured Stale Path Time(sec): 360 IPv6 Unicast: F bit: False End-of-RIB sent: Yes End-of-RIB sent after update: No End-of-RIB received: Yes Timers: Configured Stale Path Time(sec): 360 Message statistics: Inq depth is 0 Outq depth is 0 Sent Rcvd Opens: 3 2 Notifications: 0 2 Updates: 1702783 136850 Keepalives: 5637 6445 Route Refresh: 0 10 Capability: 0 0 Total: 1708423 143309 Minimum time between advertisement runs is 0 seconds Update source is wg2601 For address family: IPv4 Unicast DN42fullpeer peer-group member Update group 3, subgroup 57 Packet Queue length 0 MED is propagated unchanged to this neighbor Community attribute sent to this neighbor(all) Inbound path policy configured Outbound path policy configured Route map for incoming advertisements is *rm-fullpeer-in Route map for outgoing advertisements is *rm-fullpeer-out 454 accepted prefixes For address family: IPv6 Unicast DN42fullpeer peer-group member Update group 7, subgroup 56 Packet Queue length 0 Inbound soft reconfiguration allowed MED is propagated unchanged to this neighbor Community attribute sent to this neighbor(all) Inbound path policy configured Outbound path policy configured Route map for incoming advertisements is *rm-fullpeer-in Route map for outgoing advertisements is *rm-fullpeer-out 339 accepted prefixes Connections established 2; dropped 1 Last reset 2d00h48m, No AFI/SAFI activated for peer Local host: fda9:26a9:1c47:d42:42:42:2601:1050, Local port: 179 Foreign host: fda9:26a9:1c47:d42:42:42:2601:1051, Foreign port: 54219 Nexthop: 172.22.169.128 Nexthop global: fda9:26a9:1c47:d42:42:42:2601:1050 Nexthop local: fe80::1050 BGP connection: shared network BGP Connect Retry Timer in Seconds: 30 Estimated round trip time: 20 ms Read thread: on Write thread: on FD used: 38 ************************************* ---------------------------------- Brandon Jackson bjackson(a)napshome.net

1 0

import vrf works in running config, but not after write mem and frr restart
by 0xbabaf00l 26 Dec '20

26 Dec '20

Hi list, I'm trying to import routes from one VRF into my default VRF. This is my sample config: debian# show running-config Building configuration... Current configuration: ! frr version 7.4 frr defaults traditional hostname debian log syslog informational no ip forwarding no ipv6 forwarding service integrated-vtysh-config ! router bgp 11111 ! address-family ipv4 unicast network 1.1.1.0/24 exit-address-family ! router bgp 22222 vrf red ! address-family ipv4 unicast network 2.2.2.0/24 exit-address-family ! line vty ! end Now I add the import: debian# conf t debian(config)# router bgp 11111 debian(config-router)# address-family ipv4 unicast debian(config-router-af)# import vrf red debian(config-router-af)# end Everything works fine. ‘show running-configuration’ shows the correct config. Then I save the config and restart frr: debian# write mem Note: this version of vtysh never writes vtysh.conf Building Configuration... Integrated configuration saved to /etc/frr/frr.conf [OK] debian# exit root@debian:~# systemctl restart frr root@debian:~# vtysh Hello, this is FRRouting (version 7.4). Copyright 1996-2005 Kunihiro Ishiguro, et al. debian# sh ru Building configuration... Current configuration: ! frr version 7.4 frr defaults traditional hostname debian log syslog informational no ip forwarding no ipv6 forwarding service integrated-vtysh-config ! router bgp 11111 ! address-family ipv4 unicast network 1.1.1.0/24 import vrf red exit-address-family ! router bgp 11111 vrf red ! line vty ! end Why is the router bgp 22222 vrf red block now missing? As I said, this configuration worked fine until I saved it and restarted frr. Cheers, Sascha

3 2

how time support trll
by ak_birdofprey 24 Dec '20

24 Dec '20

很感谢自由社区得FRR，能够通过提供一个很好得全功能路由组件实现来让Gnu/Linux变得更了不起。希望FRR能支持IETF定义的各类路由协议和ACTION/ACTION MODE 的具体实现，通过自由社区让网络变得更加自由，让Gnu/Linux变得更加好玩和具有魅力。也同时让FRR变得更加完善，成为IETF得最好具体实现之一

1 0

Re: [FROG] VRRP BSD support
by Donald Sharp 22 Dec '20

22 Dec '20

We would need someone to implement the kernel features needed then it becomes fairly straightforward to get vrrp going on a bsd system Nothing insurmountable we just need a bsd kernel developer to do the work Donald On Tue, Dec 22, 2020, 10:18 AM David Bader via frog < frog(a)lists.frrouting.org> wrote: > > > > ---------- Forwarded message ---------- > From: David Bader <David.Bader(a)mailbox.org> > To: frog(a)lists.frrouting.org > Cc: > Bcc: > Date: Tue, 22 Dec 2020 16:16:41 +0100 > Subject: VRRP BSD support > Hello, > > the documentation [1] states: > > VRRP is supported on Linux 5.1+ > > Are there any plans to support VRRP also on FreeBSD? > > > thanks, > David > > > > [1] https://docs.frrouting.org/en/latest/vrrp.html > > > > > ---------- Forwarded message ---------- > From: David Bader via frog <frog(a)lists.frrouting.org> > To: frog(a)lists.frrouting.org > Cc: > Bcc: > Date: Tue, 22 Dec 2020 16:16:41 +0100 > Subject: [FROG] VRRP BSD support > _______________________________________________ > frog mailing list > frog(a)lists.frrouting.org > https://lists.frrouting.org/listinfo/frog >

1 0

VRRP BSD support
by David Bader 22 Dec '20

22 Dec '20

Hello, the documentation [1] states: > VRRP is supported on Linux 5.1+ Are there any plans to support VRRP also on FreeBSD? thanks, David [1] https://docs.frrouting.org/en/latest/vrrp.html

1 0

IGMP and MLD Proxy for EVPN
by hongal 20 Dec '20

20 Dec '20

Hi Folks, Looking to see, if this ietf draft for EVPN is supported in frr. https://tools.ietf.org/html/draft-ietf-bess-evpn-igmp-mld-proxy-05 Specifically looking for route-types: + 6 - Selective Multicast Ethernet Tag Route + 7 - Multicast Join Synch Route + 8 - Multicast Leave Synch Route Any plans, or there is something equivalent for these route-types?. I do not see any PR requests, or in code these route type are not defined. Thanks Thippanna

2 2

Hostname / ISIS ?
by Olivier CALVANO 18 Dec '20

18 Dec '20

HI I use FRRouting (version 7.0) and I have a small problem, it refuses to change the hostname for me. it forces the use of the full name of the machine. I put: C220-1.PAR4 and systematically it gives me c220-1.par4.mydomain.com including in the ISIS announcements It's normal ? also currently I access via SSH to the server then to FRR via vtyshy, is it possible to directly access FRRouting via telnet or SSH without going through the server access phase? thank you in advance for your help

2 2