- frog - lists.frrouting.org

BUG: Frrouting ospfd crashes
by Алексей 25 Aug '20

25 Aug '20

OSPFD crashing, after exec: sh ip ospf interface <if> arch# show ip ospf interface archkde0 vtysh: error reading from ospfd: Success (0)Warning: closing connection to ospfd because of an I/O error! arch# arch# Systemd log: авг 20 04:35:21 arch systemd[1]: frr.service: Killing process 29450 (zebra) with signal SIGABRT. авг 20 04:35:21 arch systemd[1]: frr.service: Killing process 29456 (staticd) with signal SIGABRT. авг 20 04:35:21 arch systemd[1]: frr.service: Killing process 29464 (bgpd) with signal SIGABRT. авг 20 04:35:21 arch systemd[1]: frr.service: Killing process 29476 (ripd) with signal SIGABRT. авг 20 04:35:21 arch systemd[1]: frr.service: Killing process 29484 (ripngd) with signal SIGABRT. авг 20 04:35:21 arch systemd[1]: frr.service: Killing process 29492 (ospfd) with signal SIGABRT. авг 20 04:35:21 arch systemd[1]: frr.service: Killing process 29500 (ospf6d) with signal SIGABRT. авг 20 04:35:21 arch systemd[1]: frr.service: Killing process 29508 (isisd) with signal SIGABRT. авг 20 04:35:21 arch systemd[1]: frr.service: Killing process 29516 (babeld) with signal SIGABRT. авг 20 04:35:21 arch systemd[1]: frr.service: Killing process 29524 (pimd) with signal SIGABRT. авг 20 04:35:21 arch systemd[1]: frr.service: Killing process 29533 (ldpd) with signal SIGABRT. авг 20 04:35:21 arch systemd[1]: frr.service: Killing process 29534 (ldpd) with signal SIGABRT. авг 20 04:35:21 arch systemd[1]: frr.service: Killing process 29535 (ldpd) with signal SIGABRT. авг 20 04:35:21 arch systemd[1]: frr.service: Killing process 29544 (nhrpd) with signal SIGABRT. авг 20 04:35:21 arch systemd[1]: frr.service: Killing process 29552 (eigrpd) with signal SIGABRT. авг 20 04:35:21 arch systemd[1]: frr.service: Killing process 29563 (pbrd) with signal SIGABRT. авг 20 04:35:21 arch systemd[1]: frr.service: Killing process 29571 (bfdd) with signal SIGABRT. авг 20 04:35:21 arch systemd[1]: frr.service: Killing process 29579 (fabricd) with signal SIGABRT. авг 20 04:35:21 arch systemd[1]: frr.service: Killing process 29587 (vrrpd) with signal SIGABRT. авг 20 04:35:21 arch systemd[1]: frr.service: Failed with result 'watchdog'. авг 20 04:35:26 arch systemd[1]: frr.service: Scheduled restart job, restart counter is at 2. авг 20 04:35:26 arch systemd[1]: Stopped FRRouting. авг 20 04:35:26 arch systemd[1]: Starting FRRouting... авг 20 04:35:26 arch frr[29603]: Loading capability module if not yet done. авг 20 04:35:26 arch frr[29632]: 2020/08/20 04:35:26 ZEBRA: [EC 4043309110] Disabling MPLS support (no kernel support) авг 20 04:35:27 arch frr[29603]: starting staticd since zebra is running (binary does not exist)Exiting from the script авг 20 04:35:27 arch systemd[1]: Started FRRouting. авг 20 04:36:27 arch systemd[1]: frr.service: Watchdog timeout (limit 1min)! авг 20 04:36:27 arch systemd[1]: frr.service: Killing process 29633 (zebra) with signal SIGABRT. авг 20 04:36:27 arch systemd[1]: frr.service: Killing process 29639 (staticd) with signal SIGABRT. авг 20 04:36:27 arch systemd[1]: frr.service: Killing process 29647 (bgpd) with signal SIGABRT. авг 20 04:36:27 arch systemd[1]: frr.service: Killing process 29659 (ripd) with signal SIGABRT. авг 20 04:36:27 arch systemd[1]: frr.service: Killing process 29667 (ripngd) with signal SIGABRT. авг 20 04:36:27 arch systemd[1]: frr.service: Killing process 29675 (ospfd) with signal SIGABRT. авг 20 04:36:27 arch systemd[1]: frr.service: Killing process 29683 (ospf6d) with signal SIGABRT. авг 20 04:36:27 arch systemd[1]: frr.service: Killing process 29691 (isisd) with signal SIGABRT. авг 20 04:36:27 arch systemd[1]: frr.service: Killing process 29699 (babeld) with signal SIGABRT. авг 20 04:36:27 arch systemd[1]: frr.service: Killing process 29707 (pimd) with signal SIGABRT. авг 20 04:36:27 arch systemd[1]: frr.service: Killing process 29716 (ldpd) with signal SIGABRT. авг 20 04:36:27 arch systemd[1]: frr.service: Killing process 29717 (ldpd) with signal SIGABRT. авг 20 04:36:27 arch systemd[1]: frr.service: Killing process 29718 (ldpd) with signal SIGABRT. авг 20 04:36:27 arch systemd[1]: frr.service: Killing process 29727 (nhrpd) with signal SIGABRT. авг 20 04:36:27 arch systemd[1]: frr.service: Killing process 29735 (eigrpd) with signal SIGABRT.

3 4

Configure BGP multicast peering and pim
by Алексей 25 Aug '20

25 Aug '20

Haw to configure MBGP to multicast peering and redistribute the multicast from PIM RP?

2 2

FRR is not announce route if non exsist the RIB
by Алексей 23 Aug '20

23 Aug '20

Hello, FRR 7.4 who is not announced network, if network is none from kernel or static route is exist? Old versions is announce normal non exist networking. The example is no announced network 192.168.100.0/24 conf t router bgp 1 network 192.168.100.0/24 neighbor test0 interface remote-as 2 Announce is normally: conf t ip route 192.168.100.0/24 null0 router bgp 1 network 192.168.100.0/24 neighbor test0 interface remote-as 2

2 1

simple frr ospf example setup
by Moritz Warning 23 Aug '20

23 Aug '20

Hi, I am a newbie with frr/ospf. My aim is to run two ospfd instances in a Linux network namesspace each and let them talk to each other via a virtual link (interface called uplink). My test setup is attached. But I do not see any traffic. This is probably some basic configuration error. I did have a look at the documentation, but it did not seem to cover such simple setups. A few pointer in the right direction would be helpful. thanks, mwarning $ ip netns add ns-0 $ ip netns add ns-1 # Node 0: $ sudo ip netns exec ns-0 ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 4: uplink@if3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether ce:e6:b3:5d:d3:70 brd ff:ff:ff:ff:ff:ff link-netns switch inet 192.168.1.0/24 scope global uplink valid_lft forever preferred_lft forever inet6 fe80::cce6:b3ff:fe5d:d370/64 scope link valid_lft forever preferred_lft forever $ cat ospf0.conf router ospf ospf router-id 192.168.1.0 network 192.168.1.0/24 area 1 $ sudo ip netns exec ns-0 ospfd --terminal -f ./ospf0.conf -i /run/frr/ospfd0.pid # Node 1: $ sudo ip netns exec ns-1 ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 7: uplink@if6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 12:45:ca:46:19:52 brd ff:ff:ff:ff:ff:ff link-netns switch inet 192.168.1.1/24 scope global uplink valid_lft forever preferred_lft forever inet6 fe80::1045:caff:fe46:1952/64 scope link valid_lft forever preferred_lft forever $ cat ospf1.conf router ospf ospf router-id 192.168.1.1 network 192.168.1.0/24 area $ sudo ip netns exec ns-1 ospfd --terminal -f ./ospf1.conf -i /run/frr/ospfd1.pid

4 5

PIM is now visible the RP, else address is an loopback
by Алексей 20 Aug '20

20 Aug '20

PIM is now visible the rp, else address is an loopback: arch(config)# ip pim rp 192.168.7.1 224.1.0.0/24 % No Path to RP address specified: 192.168.7.1 Interface lo is up, line protocol is up Link ups: 0 last: (never) Link downs: 0 last: (never) vrf: default index 1 metric 0 mtu 65536 speed 0 flags: <UP,LOOPBACK,RUNNING> Type: Loopback inet 192.168.6.5/32 inet 192.168.7.1/32 inet 192.168.9.2/32 Interface Type Other

2 1

Unable to save config
by Heikki Lavaste 11 Aug '20

11 Aug '20

Hi, I have the following problem: I'm not able save the router config.If I exit out of vtysh and jump back in, the config is reset back to defaults. [root@frr frr]# vtysh Hello, this is FRRouting (version 7.3.1). Copyright 1996-2005 Kunihiro Ishiguro, et al. frr# conf t frr(config)# hostname Heikki Heikki(config)# do write Note: this version of vtysh never writes vtysh.conf Building Configuration... Integrated configuration saved to /etc/frr/frr.conf [OK] Heikki(config)# do sh running-config Building configuration... Current configuration: ! frr version 7.3.1 frr defaults traditional hostname frr hostname Heikki service integrated-vtysh-config ! line vty ! end Heikki(config)# do sh startup-config Heikki(config)# exit Heikki# exit [root@frr frr]# vtysh Hello, this is FRRouting (version 7.3.1). Copyright 1996-2005 Kunihiro Ishiguro, et al. frr# According to systemctl, the config save runs with code 0. Aug 11 12:23:38 frr watchfrr[1514]: configuration write completed with exit cod0 I'm pretty sure I'm missing something very simple here, but just can't figure out what it is. Any suggestions for troubleshooting steps? Br Heikki

2 2

EIGRP not working in 7.3/7.4 releases
by Amol Lad 10 Aug '20

10 Aug '20

Hi, First, thank you for integrating FRR in OpenWrt. I used the latest FRR package in OpenWrt (which is FRR 7.4 release). I'm trying to configure EIGRP but it seems the "network" command is not configuring the correct network. For example, see below steps. I'm configuring "network 172.16.1.0/24" under eigrp but the running config shows "network 255.255.255.0/24" I'm not sure if this is OpenWrt specific issue or a general issue and I'll try release 7.3/7.4 on Ubuntu tomorrow. But please let me know if you latest FRR release and can successfully configure EIGRP. Thanks Amol root@arm-linux:/# vtysh Hello, this is FRRouting (version 7.4). Copyright 1996-2005 Kunihiro Ishiguro, et al. arm-linux# do show running-config Building configuration... Current configuration: ! frr version 7.4 frr defaults traditional hostname arm-linux log syslog ! password zebra ! access-list vty seq 5 permit 127.0.0.0/8 access-list vty seq 10 deny any ! line vty access-class vty ! end arm-linux# configure terminal arm-linux(config)# router eigrp 1 arm-linux(config-router)# network 172.16.1.0/24 arm-linux(config-router)# do show running-config Building configuration... Current configuration: ! frr version 7.4 frr defaults traditional hostname arm-linux log syslog ! password zebra ! router eigrp 1 network 255.255.255.0/24 ! access-list vty seq 5 permit 127.0.0.0/8 access-list vty seq 10 deny any ! line vty access-class vty ! end

2 2

[BUG] [BGP] command of `show ip bgp sum` shows ipv6 neighbors in ipv4 address-family
by Simon Jones 06 Aug '20

06 Aug '20

Hi all, I'm using frr-7.2.1-s3, I found command of `show ip bgp sum` shows ipv6 neighbors in ipv4 address-family, like this. Is this a bug? ``` dut-testbed(config-router)# do show ip bgp ipv6 summary IPv6 Unicast Summary: BGP router identifier 10.1.0.32, local AS number 65100 vrf-id 0 BGP table version 13313 RIB entries 12007, using 2158 KiB of memory Peers 3, using 61 KiB of memory Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd fc00::76 4 64600 3606 6686 0 0 0 00:20:06 6002 fc00::7a 4 64600 3605 6686 0 0 0 00:20:06 6002 fc00::7e 4 64600 3605 6686 0 0 0 00:20:05 6002 Total number of neighbors 3 dut-testbed(config-router)# do show ip bgp ipv4 summary IPv4 Unicast Summary: BGP router identifier 10.1.0.32, local AS number 65100 vrf-id 0 BGP table version 12008 RIB entries 12011, using 2158 KiB of memory Peers 8, using 163 KiB of memory Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd 10.0.0.57 4 64600 3610 3414 0 0 0 00:20:17 6002 10.0.0.59 4 64600 3610 3417 0 0 0 00:20:17 6002 10.0.0.61 4 64600 3610 3417 0 0 0 00:20:17 6002 10.0.0.63 4 64600 3610 3414 0 0 0 00:20:17 6002 fc00::72 4 64600 6 18 0 0 0 never Idle fc00::76 4 64600 3609 6690 0 0 0 00:20:15 NoNeg fc00::7a 4 64600 3609 6690 0 0 0 00:20:15 NoNeg fc00::7e 4 64600 3608 6689 0 0 0 00:20:14 NoNeg Total number of neighbors 8 dut-testbed(config-router)# address-family ipv6 dut-testbed(config-router-af)# neighbor fc00::72 activate dut-testbed(config-router-af)# do show ip bgp ipv4 summary IPv4 Unicast Summary: BGP router identifier 10.1.0.32, local AS number 65100 vrf-id 0 BGP table version 12008 RIB entries 12011, using 2158 KiB of memory Peers 8, using 163 KiB of memory Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd 10.0.0.57 4 64600 3617 3421 0 0 0 00:20:39 6002 10.0.0.59 4 64600 3617 3424 0 0 0 00:20:39 6002 10.0.0.61 4 64600 3617 3424 0 0 0 00:20:39 6002 10.0.0.63 4 64600 3617 3421 0 0 0 00:20:39 6002 fc00::72 4 64600 6 18 0 0 0 never Idle fc00::76 4 64600 3616 6697 0 0 0 00:20:37 NoNeg fc00::7a 4 64600 3616 6697 0 0 0 00:20:37 NoNeg fc00::7e 4 64600 3616 6697 0 0 0 00:20:36 NoNeg Total number of neighbors 8 dut-testbed(config-router-af)# do show ip bgp ipv4 summary IPv4 Unicast Summary: BGP router identifier 10.1.0.32, local AS number 65100 vrf-id 0 BGP table version 12008 RIB entries 12011, using 2158 KiB of memory Peers 8, using 163 KiB of memory Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd 10.0.0.57 4 64600 3618 3422 0 0 0 00:20:41 6002 10.0.0.59 4 64600 3618 3425 0 0 0 00:20:41 6002 10.0.0.61 4 64600 3618 3425 0 0 0 00:20:41 6002 10.0.0.63 4 64600 3618 3422 0 0 0 00:20:41 6002 fc00::72 4 64600 3212 20 0 0 0 00:00:01 NoNeg fc00::76 4 64600 3617 6698 0 0 0 00:20:39 NoNeg fc00::7a 4 64600 3616 6698 0 0 0 00:20:39 NoNeg fc00::7e 4 64600 3616 6698 0 0 0 00:20:38 NoNeg ``` ---- Simon Jones

5 5

BFD question
by Operations 05 Aug '20

05 Aug '20

Hi, We are new to this mailing list and to FRR. Currently we are looking into enabling and configuring BFD. We've run into an issue and can not start the BFD daemon; when running manually we get the error: # /usr/lib/frr/bfdd -F traditional -A 127.0.0.1 --log-level debug 2020/08/05 16:36:14 emergencies: BFD: udp6-shop: socket: Address family not supported by protocol IPv6 support is explicitly disabled via kernel boot parameter. Is there a way (that I missed in the documentation) to disable IPv6 altogether in bfdd? We are running FRRouting v7.3.1 from the official repo. Any help is much appreciated! Best regards, -- Zsolt Gurmai NOC Red Matter Ltd. Operations Team +44 333 150 2890 +1 646 586 2159 +61 282 443 020 +852 5808 0256 +65 3163 4091 Emergency Number +44 134 423 1535 E-mail operations(a)redmatter.com

2 1

Pottential bugs RPKI States at FRR 7.3.1 (debian packages)
by Dewangga Alam 02 Aug '20

02 Aug '20

Hello! I am new at FRR, and trying to found a reference that indicated (bugs?) or miss configuration at version 7.3.1 using debian buster packages from http://deb.frrouting.org (%3Ca) class="" style="text-decoration:none !important;border-bottom: 1px dotted #3A9AFC !important">deb.frrouting.org (http://http://deb.frrouting.org (%3Ca) class="" style="text-decoration:none !important;border-bottom: 1px dotted #3A9AFC !important">deb.frrouting.org) Here’s our configuration: https://pastebin.com/xKE3AJij Already adjusted bgpd using rpki options, and when I restart frr service, the tagging was not working. > vtysh > sh bgp ipv4 103.241.24.0 BGP routing table entry for 103.241.24.0/24 Paths: (3 available, best #3, table default) Not advertised to any peer 38515 58820 ((null)) 103.28.75.36 from 103.28.75.0 (103.28.75.0) Origin IGP, localpref 5100, valid, internal Last update: Sat Aug 1 10:54:34 (canary:event?ts=617946879.00) 2020 38515 58820 ((null)) 103.28.75.36 from 103.28.74.255 (103.28.74.255) Origin IGP, localpref 5100, valid, internal Last update: Sat Aug 1 10:54:34 (canary:event?ts=617946879.00) 2020 38515 58820 ((null)) 103.28.75.36 from 103.28.74.129 (103.28.74.127) Origin IGP, localpref 5100, valid, internal, best (Router ID) Community: 38515:58820 Last update: Sat Aug 1 10:54:34 (canary:event?ts=617946879.00) 2020 The rpki states aren’t show, and when I paste the route-map configuration into vtysh, the loc-pref tag are valids and working. The full command pasted here: https://pastebin.com/n3VY4gNm Any hints to fix this issue ? Any helps are appreciated. Thanks in advance! Many thanks. -- Sent from Canary (https://canarymail.io)

1 0