- frog - lists.frrouting.org

Re: [FROG] [dev] Ubuntu 20.04 LTS File..
by Chriztoffer Hansen 12 Jun '20

12 Jun '20

On Sun, 7 Jun 2020 at 20:39, Kevin Morales wrote: > when do you are to add the file for Ubuntu 20.04 LTS (focal) on your repository? 💌 "Ubuntu 20.04 LTS (focal) - will be added shortly" - deb.frrouting.org 😃

1 0

Why no ecmp route?
by Simon Jones 12 Jun '20

12 Jun '20

Hi all, Now I use quagga-0.99 as BGP stack in testbed, TOPO as bellow: ``` routerA |--- | ------- DUT | routerB |--- ``` routerA and routerB is aristaOS, its config is: ``` some static route and route-map router bgp 64600 router-id 100.1.0.29 neighbor 10.0.0.56 remote-as 65100 neighbor 10.0.0.56 description 65100 neighbor 10.0.0.56 default-originate route-map DEFAULT_ROUTES neighbor 10.0.0.56 maximum-routes 12000 neighbor fc00::71 remote-as 65100 neighbor fc00::71 description 65100 neighbor fc00::71 default-originate route-map DEFAULT_ROUTES neighbor fc00::71 maximum-routes 12000 redistribute static route-map PREPENDAS # this is used for redistribute local static route into bgp.rib and zebr.rib address-family ipv4 network 100.1.0.29/32 ! address-family ipv6 neighbor fc00::71 activate network 2064:100::1d/128 ! ``` DUT is out router, use quagga-0.99, its config is: ``` router bgp 65100 bgp router-id 10.1.0.32 bgp log-neighbor-changes no bgp default ipv4-unicast bgp bestpath as-path multipath-relax # use this for ECMP network 10.1.0.32/32 network 192.168.0.0/21 neighbor 10.0.0.57 remote-as 64600 neighbor 10.0.0.57 description ARISTA01T1 neighbor 10.0.0.57 timers 3 10 neighbor 10.0.0.57 activate neighbor 10.0.0.59 remote-as 64600 neighbor 10.0.0.59 description ARISTA02T1 neighbor 10.0.0.59 timers 3 10 neighbor 10.0.0.59 activate neighbor 10.0.0.61 remote-as 64600 neighbor 10.0.0.61 description ARISTA03T1 neighbor 10.0.0.61 timers 3 10 neighbor 10.0.0.61 activate neighbor 10.0.0.63 remote-as 64600 neighbor 10.0.0.63 description ARISTA04T1 neighbor 10.0.0.63 timers 3 10 neighbor 10.0.0.63 activate neighbor fc00::72 remote-as 64600 neighbor fc00::72 description ARISTA01T1 neighbor fc00::72 timers 3 10 neighbor fc00::76 remote-as 64600 neighbor fc00::76 description ARISTA02T1 neighbor fc00::76 timers 3 10 neighbor fc00::7a remote-as 64600 neighbor fc00::7a description ARISTA03T1 neighbor fc00::7a timers 3 10 neighbor fc00::7e remote-as 64600 neighbor fc00::7e description ARISTA04T1 neighbor fc00::7e timers 3 10 ! address-family ipv6 network fc00:1::32/128 neighbor fc00::72 activate neighbor fc00::76 activate neighbor fc00::7a activate neighbor fc00::7e activate exit-address-family ! ip forwarding ipv6 forwarding ! line vty ! end ``` But when run this testbed, I found there is no ECMP route on DUT, as bellow: ``` test-hostname(config-router)# do show ip bgp 193.7.248.128/25 BGP routing table entry for 193.7.248.128/25 Paths: (4 available, best #4, table Default-IP-Routing-Table) Advertised to non peer-group peers: 10.0.0.57 10.0.0.61 10.0.0.63 64600 65534 64791 65115 10.0.0.57 from 10.0.0.57 (100.1.0.29) Origin incomplete, localpref 100, valid, external Last update: Wed Jun 10 09:47:27 2020 64600 65534 64791 65115 10.0.0.63 from 10.0.0.63 (100.1.0.32) Origin incomplete, localpref 100, valid, external Last update: Wed Jun 10 06:33:03 2020 64600 65534 64791 65115 10.0.0.61 from 10.0.0.61 (100.1.0.31) Origin incomplete, localpref 100, valid, external Last update: Wed Jun 10 06:32:58 2020 64600 65534 64791 65115 10.0.0.59 from 10.0.0.59 (100.1.0.30) Origin incomplete, localpref 100, valid, external, best Last update: Wed Jun 10 06:32:56 2020 test-hostname(config-router)# do show ip route 193.7.248.128/25 Routing entry for 193.7.248.128/25 Known via "bgp", distance 20, metric 0, best Last update 03:15:00 ago * 10.0.0.59, via PortChannel0002 ``` Why??? Compare with another environment: ``` BJ-GH-M1F203-B02-TEST-12# show ip bgp 1.1.1.224/32 BGP routing table entry for 1.1.1.224/32 Paths: (2 available, best #1, table Default-IP-Routing-Table) Advertised to non peer-group peers: 100.0.34.222 235 224 100.0.56.223 from 100.0.56.223 (100.0.3.223) Origin IGP, localpref 100, valid, external, multipath, best Last update: Tue Jun 9 06:08:59 2020 235 224 100.0.34.222 from 100.0.34.222 (100.0.55.222) Origin IGP, localpref 100, valid, external, multipath Last update: Tue Jun 9 06:08:59 2020 BJ-GH-M1F203-B02-TEST-12# show ip route 1.1.1.224/32 Routing entry for 1.1.1.224/32 Known via "bgp", distance 20, metric 0, best Last update 1d02h19m ago * 100.0.56.223, via Ethernet53 * 100.0.34.222, via Ethernet50 ``` Why does this have ECMP??? For detail, I found there is only one difference, which is `Origin IGP` and `Origin imcomplete`. But I check code, in `bgp_path_info_cmp` function, in step 11, the `paths_eq` only depends on `BGP_FLAG_ASPATH_MULTIPATH_RELAX` and something, nothing with `Origin`. So why there is no ECMP in my testbed??? ---- Simon Jones

2 1

BGPd logging BGP updates
by Niklas Hoglund 05 Jun '20

05 Jun '20

Hi, Can I make BGPd just put all (EVPN) BGP updates into a log file? As they come and go, not just a snapshot (" dump bgp all ") in certain intervals. //Niklas

3 2

How to evaluate ospfv3 shortest path first running time for large networks?
by yanhc519 24 May '20

24 May '20

Hi all. I am using ospfv3 routing in an embeded processor. The most time consuming part is the shortest path first(spf, Dijkstra) calculation in ospf6_spf.c. Since the spf calculation uses a priority queue, so the computational complexity is O(E*log2(V)) where E is the number of edges and V is the number of vertices. I have measured the running time of spf calculation in the embeded processor with small E and V, i.e. E=1 and V=2. The measured spf running time is 10 milliseconds. My goal is to evaluate the spf running time in a large network e.g. V=800 and E=1600. Since deploy such a large network in conceptual design phase is not practical, so is there an estimation method using the computational complexity O(E*log2(V)) and measurement in small network? Thanks in advance. yan

2 1

l2vpn evpn, vxlan without bridge.
by Erwan David 18 May '20

18 May '20

Hi, I set up FRR routers as VTEP for a setting where all trafic on the vxlan will originate on the routers. I setup the BGP l2vpn evpn family address, but I cannot get FRR to announce its routes (type 2 or type 3) if the vxlan interface is not in bridge. I end up bridging it with a dummy interface, but for me it is an ugly workaround. Is there a way to avoid this bridge ? -- Erwan David

2 1

Re: [FROG] Unable to get spoke to spoke communication for private networks behind two spoke.
by Gaurav Goyal 15 May '20

15 May '20

Diagram of network attached since it is not getting correctly displayed: [cid:image002.jpg@01D62AB2.42A4F320] From: Gaurav Goyal Sent: Wednesday, 13 May 2020 6:14 pm To: 'frog(a)lists.frrouting.org' <frog(a)lists.frrouting.org<mailto:frog@lists.frrouting.org>> Subject: Unable to get spoke to spoke communication for private networks behind two spoke. Testing on frr version: 7.4 from https://github.com/FRRouting/frr.git The network is following: ------------ ------------ -------------- | | gre1: 22.22.22.2/32 | Switch | 22.22.22.3/32: gre1 | |--- LO: 192.168.6.1/32 192.168.4.1/24:eth0 | SPOKE1|--eth1: 169.254.50.50--------| |------ -- 169.254.50.52 :eth0| SPOKE2 |--- eth1: 192.168.5.1/24 ------------ ------------ ------------ | | | gre1: 22.22.22.1/32 eth0: 169.254.50.51 --------------- | UBUNTU | | HUB | --------------- Issue: Spoke to Spoke communication between spoke1 and spoke2 works for gre interface IPs 22.22.22.2 and 22.22.22.3 respectively. But does not work between 192.168.5.1 (eth1 IP on Spoke2) and 192.168.4.1 (eth0 IP on Spoke1), this communication happens via the HUB. When pinging 192.168.4.1 from Spoke2, the routes which get installed on Spoke2 after this are the following. As you can see the route to reach 192.168.4.0/24 network is via 22.22.22.1. It should have been via 22.22.22.2. show ip route Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF, I - IS-IS, B - BGP, E - EIGRP, N - NHRP, T - Table, v - VNC, V - VNC-Direct, A - Babel, D - SHARP, F - PBR, f - OpenFabric, > - selected route, * - FIB route, q - queued route, r - rejected route K>* 0.0.0.0/0 [0/0] via 192.168.20.1, wlan0, 02:19:32 N>* 22.22.22.1/32 [10/0] is directly connected, gre1, weight 1, 02:19:26 N>* 22.22.22.2/32 [10/0] is directly connected, gre1, weight 1, 00:01:16 B 22.22.22.2/32 [200/0] via 22.22.22.1 (recursive), weight 1, 02:19:25 via 22.22.22.1, gre1 onlink, weight 1, 02:19:25 B 22.22.22.3/32 [200/0] via 22.22.22.1 (recursive), weight 1, 02:19:25 via 22.22.22.1, gre1 onlink, weight 1, 02:19:25 C>* 22.22.22.3/32 is directly connected, gre1, 02:19:32 C>* 169.254.50.0/24 is directly connected, eth0, 02:19:32 B> 192.168.4.0/24 [200/0] via 22.22.22.1 (recursive), weight 1, 02:19:25 * via 22.22.22.1, gre1 onlink, weight 1, 02:19:25 C>* 192.168.5.0/24 is directly connected, eth1, 02:19:32 C>* 192.168.20.0/24 is directly connected, wlan0, 02:19:32 HUB Configuration: ---------------------------------------------------------------------------------------------------------------- sudo ip tunnel add gre1 mode gre key 42 ttl 64 sudo ip addr add 22.22.22.1/32 dev gre1 sudo ip link set gre1 up sudo iptables -A FORWARD -i gre1 -o gre1 -m hashlimit --hashlimit-upto 4/minute --hashlimit-burst 1 --hashlimit-mode srcip,dstip --hashlimit-srcmask 24 --hashlimit-dstmask 24 --hashlimit-name loglimit-0 -j NFLOG --nflog-group 1 --nflog-size 128 sudo iptables -A OUTPUT -o gre1 -m hashlimit --hashlimit-upto 4/minute --hashlimit-burst 1 --hashlimit-mode srcip,dstip --hashlimit-srcmask 24 --hashlimit-dstmask 24 --hashlimit-name loglimit-0 -j NFLOG --nflog-group 1 --nflog-size 128 ThinkPad-T400# show run Building configuration... Current configuration: ! frr version 7.4-dev-MyOwnFRRVersion frr defaults traditional hostname ThinkPad-T400 log syslog informational nhrp nflog-group 1 service integrated-vtysh-config ! interface gre1 ip nhrp network-id 1 ip nhrp redirect tunnel source eth0 ! router bgp 65000 bgp deterministic-med neighbor spokes-ibgp peer-group neighbor spokes-ibgp remote-as 65000 neighbor spokes-ibgp disable-connected-check neighbor spokes-ibgp advertisement-interval 1 neighbor 22.22.22.2 peer-group spokes-ibgp neighbor 22.22.22.3 peer-group spokes-ibgp ! address-family ipv4 unicast network 22.22.22.0/24 redistribute nhrp neighbor spokes-ibgp route-reflector-client neighbor spokes-ibgp next-hop-self force neighbor spokes-ibgp soft-reconfiguration inbound exit-address-family ! line vty ! end SPOKE1 Configuration: ------------------------------------------------------------------------------------------------------------------ ip tunnel add gre1 mode gre key 42 ttl 64 ip addr add 22.22.22.2/32 dev gre1 ip link set gre1 up iptables -A FORWARD -i gre1 -o gre1 -m hashlimit --hashlimit-upto 4/minute --hashlimit-burst 1 --hashlimit-mode srcip,dstip --hashlimit-srcmask 24 --hashlimit-dstmask 24 --hashlimit-name loglimit-0 -j NFLOG --nflog-group 1 --nflog-size 128 iptables -A OUTPUT -o gre1 -m hashlimit --hashlimit-upto 4/minute --hashlimit-burst 1 --hashlimit-mode srcip,dstip --hashlimit-srcmask 24 --hashlimit-dstmask 24 --hashlimit-name loglimit-0 -j NFLOG --nflog-group 1 --nflog-size 128 show running-config Building configuration... Current configuration: ! frr version 7.3 frr defaults traditional hostname AprisaLTE log stdout informational log syslog service integrated-vtysh-config ! debug nhrp all debug zebra events debug zebra kernel debug zebra nexthop debug zebra nht ! password zebra ! interface gre1 ip nhrp holdtime 600 ip nhrp mtu opennhrp ip nhrp network-id 1 ip nhrp nhs dynamic nbma 169.254.50.51 ip nhrp shortcut tunnel source br-lan169 ! router bgp 65000 neighbor spokes-ibgp peer-group neighbor spokes-ibgp remote-as 65000 neighbor spokes-ibgp disable-connected-check neighbor spokes-ibgp advertisement-interval 1 neighbor 22.22.22.1 peer-group spokes-ibgp ! address-family ipv4 unicast network 192.168.4.0/24 neighbor spokes-ibgp next-hop-self neighbor spokes-ibgp soft-reconfiguration inbound exit-address-family ! access-list vty seq 10 deny any access-list vty seq 5 permit 127.0.0.0/8 ! line vty access-class vty ! end SPOKE2 Configuration: ------------------------------------------------------------------------------------------------------------------ ip tunnel add gre1 mode gre key 42 ttl 64 ip addr add 22.22.22.3/32 dev gre1 ip link set gre1 up sudo nft list ruleset table ip filter { chain input { type filter hook input priority 0; policy accept; } chain forward { type filter hook forward priority 0; policy accept; iifname "gre1" oifname "gre1" meter loglimit-1 size 65535 { ip daddr & 255.255.255.0 . ip saddr & 255.255.255.0 timeout 1m limit rate 4/minute burst 1 packets} counter packets 0 bytes 0 log group 1 snaplen 128 } chain output { type filter hook output priority 0; policy accept; oifname "gre1" meter loglimit-0 size 65535 { ip daddr & 255.255.255.0 . ip saddr & 255.255.255.0 timeout 1m limit rate 4/minute burst 1 packets} counter packets 4322 bytes 291697 log group 1 snaplen 128 } } raspberrypi# show run Building configuration... Current configuration: ! frr version 7.4-dev-MyOwnFRRVersion frr defaults traditional hostname raspberrypi log stdout informational log syslog nhrp nflog-group 1 service integrated-vtysh-config ! debug nhrp all debug zebra events debug zebra kernel debug zebra nexthop debug zebra nht ! interface gre1 ip nhrp holdtime 600 ip nhrp mtu opennhrp ip nhrp network-id 1 ip nhrp nhs dynamic nbma 169.254.50.51 ip nhrp shortcut tunnel source eth0 ! router bgp 65000 bgp router-id 192.168.6.1 no bgp network import-check neighbor spokes-ibgp peer-group neighbor spokes-ibgp remote-as 65000 neighbor spokes-ibgp disable-connected-check neighbor spokes-ibgp advertisement-interval 1 neighbor 22.22.22.1 peer-group spokes-ibgp ! address-family ipv4 unicast network 192.168.5.0/24 network 192.168.6.1/32 neighbor spokes-ibgp next-hop-self neighbor spokes-ibgp soft-reconfiguration inbound exit-address-family ! line vty ! end ------------------------------------------------------------------------------------------------------ When pinging 192.168.4.1 from Spoke2 following logs are seen at spoke2: pi@raspberrypi:~ $ tail -f /var/log/syslog | grep -v vici_reconnect May 12 15:59:44 raspberrypi zebra[15602]: netlink_parse_info: netlink-listen (NS 0) type RTM_NEWNEIGH(28), len=76, seq=0, pid=0 May 12 15:59:44 raspberrypi zebra[15602]: #011Neighbor Entry received is not on a VLAN or a BRIDGE, ignoring May 12 16:00:22 raspberrypi nhrpd[15616]: Netlink-log: Received msg_type 1024, msg_flags 0 May 12 16:00:22 raspberrypi nhrpd[15616]: PACKET: Recv 169.254.50.51 -> 169.254.50.52 May 12 16:00:22 raspberrypi nhrpd[15616]: Recv Traffic-Indication(8) 22.22.22.1 -> 22.22.22.3 May 12 16:00:22 raspberrypi nhrpd[15616]: !LOCAL Traffic-Indication(8) 22.22.22.1 -> 22.22.22.3 May 12 16:00:22 raspberrypi nhrpd[15616]: Traffic Indication from 22.22.22.1 about packet to 192.168.4.1: trying shortcut May 12 16:00:22 raspberrypi nhrpd[15616]: Shortcut 192.168.4.1/32 created May 12 16:00:22 raspberrypi nhrpd[15616]: lookup 192.168.4.1/32: zebra route dev (none) May 12 16:00:22 raspberrypi nhrpd[15616]: lookup 22.22.22.1/32: nhrp_if=gre1 May 12 16:00:22 raspberrypi nhrpd[15616]: Shortcut res_req: set cie ht to 600 and mtu to 0. shortcut ht is 0 May 12 16:00:22 raspberrypi nhrpd[15616]: Send Resolution-Request(1) 22.22.22.3 -> 192.168.4.1 May 12 16:00:22 raspberrypi nhrpd[15616]: PACKET: Send 169.254.50.52 -> 169.254.50.51 May 12 16:00:22 raspberrypi nhrpd[15616]: PACKET: Recv 169.254.50.51 -> 169.254.50.52 May 12 16:00:22 raspberrypi nhrpd[15616]: Recv Resolution-Request(1) 22.22.22.2 -> 22.22.22.3 May 12 16:00:22 raspberrypi nhrpd[15616]: !LOCAL Resolution-Request(1) 22.22.22.2 -> 22.22.22.3 May 12 16:00:22 raspberrypi nhrpd[15616]: Parsing and replying to Resolution Req May 12 16:00:22 raspberrypi nhrpd[15616]: lookup 22.22.22.2/32: zebra route dev (none) May 12 16:00:22 raspberrypi nhrpd[15616]: lookup 22.22.22.1/32: nhrp_if=gre1 May 12 16:00:22 raspberrypi nhrpd[15616]: shortcut res_rep: paylen 0 May 12 16:00:22 raspberrypi nhrpd[15616]: Send Resolution-Reply(2) 22.22.22.3 -> 22.22.22.2 May 12 16:00:22 raspberrypi nhrpd[15616]: PACKET: Send 169.254.50.52 -> 169.254.50.51 May 12 16:00:22 raspberrypi zebra[15602]: netlink_parse_info: netlink-listen (NS 0) type RTM_NEWNEIGH(28), len=72, seq=0, pid=15615 May 12 16:00:22 raspberrypi zebra[15602]: #011Neighbor Entry received is not on a VLAN or a BRIDGE, ignoring May 12 16:00:22 raspberrypi nhrpd[15616]: PACKET: Recv 169.254.50.51 -> 169.254.50.52 May 12 16:00:22 raspberrypi nhrpd[15616]: Recv Resolution-Reply(2) 192.168.4.1 -> 22.22.22.3 May 12 16:00:22 raspberrypi nhrpd[15616]: !LOCAL Resolution-Reply(2) 192.168.4.1 -> 22.22.22.3 May 12 16:00:22 raspberrypi nhrpd[15616]: lookup 192.168.4.1/32: zebra route dev (none) May 12 16:00:22 raspberrypi nhrpd[15616]: lookup 22.22.22.1/32: nhrp_if=gre1 May 12 16:00:22 raspberrypi nhrpd[15616]: Shortcut: 192.168.4.1/24 is at proto 22.22.22.2 dst_proto 192.168.4.1 cie-nbma 169.254.50.50 nat-nbma (unspec) cie-holdtime 600 May 12 16:00:22 raspberrypi nhrpd[15616]: Shortcut: cache found, update binding May 12 16:00:22 raspberrypi nhrpd[15616]: cache: new type 0/4, or peer diff, or mtu 0/0, nbma (unspec) --> 169.254.50.50 (map 0) May 12 16:00:22 raspberrypi nhrpd[15616]: cache: gre1 22.22.22.2: accept May 12 16:00:22 raspberrypi nhrpd[15616]: cache: update binding for 22.22.22.2 dev gre1 from (deleted) peer.vc.nbma 169.254.50.50 to 169.254.50.50 May 12 16:00:22 raspberrypi nhrpd[15616]: cache (remote_nbma_natoa set): Update binding for 22.22.22.2 dev gre1 from (deleted) peer.vc.nbma 169.254.50.50 to 169.254.50.50 May 12 16:00:22 raspberrypi nhrpd[15616]: Zebra send: route add 22.22.22.2/32 nexthop <onlink> metric 0 count 1 dev gre1 May 12 16:00:22 raspberrypi nhrpd[15616]: Shortcut 192.168.4.0/24 created May 12 16:00:22 raspberrypi nhrpd[15616]: Shortcut: calling update_binding May 12 16:00:22 raspberrypi nhrpd[15616]: Shortcut: forcing renewal of zebra announce on prefix change peer 22.22.22.2 ht 600 cur nbma 169.254.50.50 dev gre1 May 12 16:00:22 raspberrypi nhrpd[15616]: Shortcut: route install 192.168.4.0/24 nh (unspec) dev gre1 May 12 16:00:22 raspberrypi nhrpd[15616]: Zebra send: route add 192.168.4.0/24 nexthop <onlink> metric 0 count 1 dev gre1 May 12 16:00:22 raspberrypi nhrpd[15616]: Shortcut: Resolution reply handled May 12 16:00:22 raspberrypi nhrpd[15616]: Netlink: Received msg_type 28, msg_flags 0 May 12 16:00:22 raspberrypi nhrpd[15616]: Netlink: new-neigh 22.22.22.2 dev gre1 lladdr 169.254.50.50 nud 0x2 cache used 0 type 4 May 12 16:00:22 raspberrypi zebra[15602]: netlink_route_multipath: RTM_NEWROUTE 22.22.22.2/32 vrf 0(254) May 12 16:00:22 raspberrypi zebra[15602]: _netlink_route_build_singlepath: (single-path): 22.22.22.2/32 nexthop via if 10 vrf default(0) May 12 16:00:22 raspberrypi zebra[15602]: netlink_talk: netlink-dp (NS 0) type RTM_NEWROUTE(24), len=52 seq=23 flags 0x501 May 12 16:00:22 raspberrypi zebra[15602]: netlink_route_multipath: RTM_NEWROUTE 192.168.4.0/24 vrf 0(254) May 12 16:00:22 raspberrypi zebra[15602]: _netlink_route_build_singlepath: (single-path): 192.168.4.0/24 nexthop via if 10 vrf default(0) May 12 16:00:22 raspberrypi zebra[15602]: netlink_talk: netlink-dp (NS 0) type RTM_NEWROUTE(24), len=52 seq=25 flags 0x501 May 12 16:00:22 raspberrypi nhrpd[15616]: if-route-add: 22.22.22.2/32 via 0.0.0.0 dev gre1 May 12 16:00:22 raspberrypi nhrpd[15616]: if-route-add: 192.168.4.0/24 via 0.0.0.0 dev gre1 May 12 16:00:22 raspberrypi nhrpd[15616]: Shortcut 192.168.4.0/24 used and expiring May 12 16:00:22 raspberrypi nhrpd[15616]: lookup 192.168.4.1/32: zebra route dev gre1 May 12 16:00:22 raspberrypi nhrpd[15616]: lookup 0.0.0.0/32: zebra route dev wlan0 May 12 16:00:22 raspberrypi nhrpd[15616]: lookup 192.168.20.1/32: zebra route dev wlan0 May 12 16:00:22 raspberrypi nhrpd[15616]: lookup 0.0.0.0/32: zebra route dev wlan0 May 12 16:00:22 raspberrypi nhrpd[15616]: Shortcut 192.168.4.1/32 purged May 12 16:00:23 raspberrypi zebra[15602]: netlink_parse_info: netlink-listen (NS 0) type RTM_NEWNEIGH(28), len=72, seq=0, pid=0 May 12 16:00:23 raspberrypi nhrpd[15616]: Netlink: Received msg_type 28, msg_flags 0 May 12 16:00:23 raspberrypi nhrpd[15616]: Netlink: new-neigh 22.22.22.1 dev gre1 lladdr 169.254.50.51 nud 0x4 cache used 1 type 5 May 12 16:00:23 raspberrypi zebra[15602]: #011Neighbor Entry received is not on a VLAN or a BRIDGE, ignoring May 12 16:00:23 raspberrypi zebra[15602]: netlink_parse_info: netlink-listen (NS 0) type RTM_GETNEIGH(30), len=64, seq=0, pid=0 May 12 16:00:23 raspberrypi nhrpd[15616]: Netlink: Received msg_type 30, msg_flags 1 May 12 16:00:23 raspberrypi zebra[15602]: Received RTM_GETNEIGH, ignoring May 12 16:00:23 raspberrypi nhrpd[15616]: Netlink: Received msg_type 28, msg_flags 0 May 12 16:00:23 raspberrypi zebra[15602]: netlink_parse_info: netlink-listen (NS 0) type RTM_NEWNEIGH(28), len=76, seq=0, pid=0 May 12 16:00:23 raspberrypi zebra[15602]: #011Neighbor Entry received is not on a VLAN or a BRIDGE, ignoring May 12 16:00:24 raspberrypi zebra[15602]: netlink_parse_info: netlink-listen (NS 0) type RTM_NEWNEIGH(28), len=64, seq=0, pid=0 May 12 16:00:24 raspberrypi nhrpd[15616]: Netlink: Received msg_type 28, msg_flags 0 May 12 16:00:24 raspberrypi zebra[15602]: #011Neighbor Entry received is not on a VLAN or a BRIDGE, ignoring May 12 16:00:24 raspberrypi zebra[15602]: netlink_parse_info: netlink-listen (NS 0) type RTM_GETNEIGH(30), len=64, seq=0, pid=0 May 12 16:00:24 raspberrypi zebra[15602]: Received RTM_GETNEIGH, ignoring May 12 16:00:24 raspberrypi nhrpd[15616]: Netlink: Received msg_type 30, msg_flags 1 May 12 16:00:25 raspberrypi nhrpd[15616]: Shortcut 192.168.4.0/24 purged May 12 16:00:25 raspberrypi nhrpd[15616]: Shortcut: notify cache down because cache?no or ri?n/a May 12 16:00:25 raspberrypi nhrpd[15616]: Zebra send: route del 192.168.4.0/24 nexthop <onlink> metric 0 count 1 dev none May 12 16:00:25 raspberrypi nhrpd[15616]: Netlink: Received msg_type 28, msg_flags 0 May 12 16:00:25 raspberrypi zebra[15602]: netlink_parse_info: netlink-listen (NS 0) type RTM_NEWNEIGH(28), len=64, seq=0, pid=0 May 12 16:00:25 raspberrypi zebra[15602]: #011Neighbor Entry received is not on a VLAN or a BRIDGE, ignoring May 12 16:00:25 raspberrypi nhrpd[15616]: Netlink: Received msg_type 30, msg_flags 1 May 12 16:00:25 raspberrypi zebra[15602]: netlink_parse_info: netlink-listen (NS 0) type RTM_GETNEIGH(30), len=64, seq=0, pid=0 May 12 16:00:25 raspberrypi zebra[15602]: Received RTM_GETNEIGH, ignoring May 12 16:00:25 raspberrypi zebra[15602]: netlink_route_multipath: RTM_NEWROUTE 192.168.4.0/24 vrf 0(254) May 12 16:00:25 raspberrypi zebra[15602]: _netlink_route_build_singlepath: (recursive, single-path): 192.168.4.0/24 nexthop via 22.22.22.1 if 10 vrf default(0) May 12 16:00:25 raspberrypi zebra[15602]: netlink_talk: netlink-dp (NS 0) type RTM_NEWROUTE(24), len=60 seq=27 flags 0x501 May 12 16:00:25 raspberrypi nhrpd[15616]: if-route-add: 192.168.4.0/24 via 22.22.22.1 dev (none) May 12 16:00:26 raspberrypi zebra[15602]: netlink_parse_info: netlink-listen (NS 0) type RTM_NEWNEIGH(28), len=64, seq=0, pid=0 May 12 16:00:26 raspberrypi nhrpd[15616]: Netlink: Received msg_type 28, msg_flags 0 May 12 16:00:26 raspberrypi zebra[15602]: #011Neighbor Entry received is not on a VLAN or a BRIDGE, ignoring May 12 16:00:30 raspberrypi zebra[15602]: netlink_parse_info: netlink-listen (NS 0) type RTM_NEWADDR(20), len=72, seq=0, pid=0 ----------------------------------------------------------------------------------------------------------------------- ________________________________ 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).

1 0

Unable to get spoke to spoke communication for private networks behind two spoke.
by Gaurav Goyal 13 May '20

13 May '20

Testing on frr version: 7.4 from https://github.com/FRRouting/frr.git The network is following: ------------ ------------ -------------- | | gre1: 22.22.22.2/32 | Switch | 22.22.22.3/32: gre1 | |--- LO: 192.168.6.1/32 192.168.4.1/24:eth0 | SPOKE1|--eth1: 169.254.50.50--------| |------ -- 169.254.50.52 :eth0| SPOKE2 |--- eth1: 192.168.5.1/24 ------------ ------------ ------------ | | | gre1: 22.22.22.1/32 eth0: 169.254.50.51 --------------- | UBUNTU | | HUB | --------------- Issue: Spoke to Spoke communication between spoke1 and spoke2 works for gre interface IPs 22.22.22.2 and 22.22.22.3 respectively. But does not work between 192.168.5.1 (eth1 IP on Spoke2) and 192.168.4.1 (eth0 IP on Spoke1), this communication happens via the HUB. When pinging 192.168.4.1 from Spoke2, the routes which get installed on Spoke2 after this are the following. As you can see the route to reach 192.168.4.0/24 network is via 22.22.22.1. It should have been via 22.22.22.2. show ip route Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF, I - IS-IS, B - BGP, E - EIGRP, N - NHRP, T - Table, v - VNC, V - VNC-Direct, A - Babel, D - SHARP, F - PBR, f - OpenFabric, > - selected route, * - FIB route, q - queued route, r - rejected route K>* 0.0.0.0/0 [0/0] via 192.168.20.1, wlan0, 02:19:32 N>* 22.22.22.1/32 [10/0] is directly connected, gre1, weight 1, 02:19:26 N>* 22.22.22.2/32 [10/0] is directly connected, gre1, weight 1, 00:01:16 B 22.22.22.2/32 [200/0] via 22.22.22.1 (recursive), weight 1, 02:19:25 via 22.22.22.1, gre1 onlink, weight 1, 02:19:25 B 22.22.22.3/32 [200/0] via 22.22.22.1 (recursive), weight 1, 02:19:25 via 22.22.22.1, gre1 onlink, weight 1, 02:19:25 C>* 22.22.22.3/32 is directly connected, gre1, 02:19:32 C>* 169.254.50.0/24 is directly connected, eth0, 02:19:32 B> 192.168.4.0/24 [200/0] via 22.22.22.1 (recursive), weight 1, 02:19:25 * via 22.22.22.1, gre1 onlink, weight 1, 02:19:25 C>* 192.168.5.0/24 is directly connected, eth1, 02:19:32 C>* 192.168.20.0/24 is directly connected, wlan0, 02:19:32 HUB Configuration: ---------------------------------------------------------------------------------------------------------------- sudo ip tunnel add gre1 mode gre key 42 ttl 64 sudo ip addr add 22.22.22.1/32 dev gre1 sudo ip link set gre1 up sudo iptables -A FORWARD -i gre1 -o gre1 -m hashlimit --hashlimit-upto 4/minute --hashlimit-burst 1 --hashlimit-mode srcip,dstip --hashlimit-srcmask 24 --hashlimit-dstmask 24 --hashlimit-name loglimit-0 -j NFLOG --nflog-group 1 --nflog-size 128 sudo iptables -A OUTPUT -o gre1 -m hashlimit --hashlimit-upto 4/minute --hashlimit-burst 1 --hashlimit-mode srcip,dstip --hashlimit-srcmask 24 --hashlimit-dstmask 24 --hashlimit-name loglimit-0 -j NFLOG --nflog-group 1 --nflog-size 128 ThinkPad-T400# show run Building configuration... Current configuration: ! frr version 7.4-dev-MyOwnFRRVersion frr defaults traditional hostname ThinkPad-T400 log syslog informational nhrp nflog-group 1 service integrated-vtysh-config ! interface gre1 ip nhrp network-id 1 ip nhrp redirect tunnel source eth0 ! router bgp 65000 bgp deterministic-med neighbor spokes-ibgp peer-group neighbor spokes-ibgp remote-as 65000 neighbor spokes-ibgp disable-connected-check neighbor spokes-ibgp advertisement-interval 1 neighbor 22.22.22.2 peer-group spokes-ibgp neighbor 22.22.22.3 peer-group spokes-ibgp ! address-family ipv4 unicast network 22.22.22.0/24 redistribute nhrp neighbor spokes-ibgp route-reflector-client neighbor spokes-ibgp next-hop-self force neighbor spokes-ibgp soft-reconfiguration inbound exit-address-family ! line vty ! end SPOKE1 Configuration: ------------------------------------------------------------------------------------------------------------------ ip tunnel add gre1 mode gre key 42 ttl 64 ip addr add 22.22.22.2/32 dev gre1 ip link set gre1 up iptables -A FORWARD -i gre1 -o gre1 -m hashlimit --hashlimit-upto 4/minute --hashlimit-burst 1 --hashlimit-mode srcip,dstip --hashlimit-srcmask 24 --hashlimit-dstmask 24 --hashlimit-name loglimit-0 -j NFLOG --nflog-group 1 --nflog-size 128 iptables -A OUTPUT -o gre1 -m hashlimit --hashlimit-upto 4/minute --hashlimit-burst 1 --hashlimit-mode srcip,dstip --hashlimit-srcmask 24 --hashlimit-dstmask 24 --hashlimit-name loglimit-0 -j NFLOG --nflog-group 1 --nflog-size 128 show running-config Building configuration... Current configuration: ! frr version 7.3 frr defaults traditional hostname AprisaLTE log stdout informational log syslog service integrated-vtysh-config ! debug nhrp all debug zebra events debug zebra kernel debug zebra nexthop debug zebra nht ! password zebra ! interface gre1 ip nhrp holdtime 600 ip nhrp mtu opennhrp ip nhrp network-id 1 ip nhrp nhs dynamic nbma 169.254.50.51 ip nhrp shortcut tunnel source br-lan169 ! router bgp 65000 neighbor spokes-ibgp peer-group neighbor spokes-ibgp remote-as 65000 neighbor spokes-ibgp disable-connected-check neighbor spokes-ibgp advertisement-interval 1 neighbor 22.22.22.1 peer-group spokes-ibgp ! address-family ipv4 unicast network 192.168.4.0/24 neighbor spokes-ibgp next-hop-self neighbor spokes-ibgp soft-reconfiguration inbound exit-address-family ! access-list vty seq 10 deny any access-list vty seq 5 permit 127.0.0.0/8 ! line vty access-class vty ! end SPOKE2 Configuration: ------------------------------------------------------------------------------------------------------------------ ip tunnel add gre1 mode gre key 42 ttl 64 ip addr add 22.22.22.3/32 dev gre1 ip link set gre1 up sudo nft list ruleset table ip filter { chain input { type filter hook input priority 0; policy accept; } chain forward { type filter hook forward priority 0; policy accept; iifname "gre1" oifname "gre1" meter loglimit-1 size 65535 { ip daddr & 255.255.255.0 . ip saddr & 255.255.255.0 timeout 1m limit rate 4/minute burst 1 packets} counter packets 0 bytes 0 log group 1 snaplen 128 } chain output { type filter hook output priority 0; policy accept; oifname "gre1" meter loglimit-0 size 65535 { ip daddr & 255.255.255.0 . ip saddr & 255.255.255.0 timeout 1m limit rate 4/minute burst 1 packets} counter packets 4322 bytes 291697 log group 1 snaplen 128 } } raspberrypi# show run Building configuration... Current configuration: ! frr version 7.4-dev-MyOwnFRRVersion frr defaults traditional hostname raspberrypi log stdout informational log syslog nhrp nflog-group 1 service integrated-vtysh-config ! debug nhrp all debug zebra events debug zebra kernel debug zebra nexthop debug zebra nht ! interface gre1 ip nhrp holdtime 600 ip nhrp mtu opennhrp ip nhrp network-id 1 ip nhrp nhs dynamic nbma 169.254.50.51 ip nhrp shortcut tunnel source eth0 ! router bgp 65000 bgp router-id 192.168.6.1 no bgp network import-check neighbor spokes-ibgp peer-group neighbor spokes-ibgp remote-as 65000 neighbor spokes-ibgp disable-connected-check neighbor spokes-ibgp advertisement-interval 1 neighbor 22.22.22.1 peer-group spokes-ibgp ! address-family ipv4 unicast network 192.168.5.0/24 network 192.168.6.1/32 neighbor spokes-ibgp next-hop-self neighbor spokes-ibgp soft-reconfiguration inbound exit-address-family ! line vty ! end ------------------------------------------------------------------------------------------------------ When pinging 192.168.4.1 from Spoke2 following logs are seen at spoke2: pi@raspberrypi:~ $ tail -f /var/log/syslog | grep -v vici_reconnect May 12 15:59:44 raspberrypi zebra[15602]: netlink_parse_info: netlink-listen (NS 0) type RTM_NEWNEIGH(28), len=76, seq=0, pid=0 May 12 15:59:44 raspberrypi zebra[15602]: #011Neighbor Entry received is not on a VLAN or a BRIDGE, ignoring May 12 16:00:22 raspberrypi nhrpd[15616]: Netlink-log: Received msg_type 1024, msg_flags 0 May 12 16:00:22 raspberrypi nhrpd[15616]: PACKET: Recv 169.254.50.51 -> 169.254.50.52 May 12 16:00:22 raspberrypi nhrpd[15616]: Recv Traffic-Indication(8) 22.22.22.1 -> 22.22.22.3 May 12 16:00:22 raspberrypi nhrpd[15616]: !LOCAL Traffic-Indication(8) 22.22.22.1 -> 22.22.22.3 May 12 16:00:22 raspberrypi nhrpd[15616]: Traffic Indication from 22.22.22.1 about packet to 192.168.4.1: trying shortcut May 12 16:00:22 raspberrypi nhrpd[15616]: Shortcut 192.168.4.1/32 created May 12 16:00:22 raspberrypi nhrpd[15616]: lookup 192.168.4.1/32: zebra route dev (none) May 12 16:00:22 raspberrypi nhrpd[15616]: lookup 22.22.22.1/32: nhrp_if=gre1 May 12 16:00:22 raspberrypi nhrpd[15616]: Shortcut res_req: set cie ht to 600 and mtu to 0. shortcut ht is 0 May 12 16:00:22 raspberrypi nhrpd[15616]: Send Resolution-Request(1) 22.22.22.3 -> 192.168.4.1 May 12 16:00:22 raspberrypi nhrpd[15616]: PACKET: Send 169.254.50.52 -> 169.254.50.51 May 12 16:00:22 raspberrypi nhrpd[15616]: PACKET: Recv 169.254.50.51 -> 169.254.50.52 May 12 16:00:22 raspberrypi nhrpd[15616]: Recv Resolution-Request(1) 22.22.22.2 -> 22.22.22.3 May 12 16:00:22 raspberrypi nhrpd[15616]: !LOCAL Resolution-Request(1) 22.22.22.2 -> 22.22.22.3 May 12 16:00:22 raspberrypi nhrpd[15616]: Parsing and replying to Resolution Req May 12 16:00:22 raspberrypi nhrpd[15616]: lookup 22.22.22.2/32: zebra route dev (none) May 12 16:00:22 raspberrypi nhrpd[15616]: lookup 22.22.22.1/32: nhrp_if=gre1 May 12 16:00:22 raspberrypi nhrpd[15616]: shortcut res_rep: paylen 0 May 12 16:00:22 raspberrypi nhrpd[15616]: Send Resolution-Reply(2) 22.22.22.3 -> 22.22.22.2 May 12 16:00:22 raspberrypi nhrpd[15616]: PACKET: Send 169.254.50.52 -> 169.254.50.51 May 12 16:00:22 raspberrypi zebra[15602]: netlink_parse_info: netlink-listen (NS 0) type RTM_NEWNEIGH(28), len=72, seq=0, pid=15615 May 12 16:00:22 raspberrypi zebra[15602]: #011Neighbor Entry received is not on a VLAN or a BRIDGE, ignoring May 12 16:00:22 raspberrypi nhrpd[15616]: PACKET: Recv 169.254.50.51 -> 169.254.50.52 May 12 16:00:22 raspberrypi nhrpd[15616]: Recv Resolution-Reply(2) 192.168.4.1 -> 22.22.22.3 May 12 16:00:22 raspberrypi nhrpd[15616]: !LOCAL Resolution-Reply(2) 192.168.4.1 -> 22.22.22.3 May 12 16:00:22 raspberrypi nhrpd[15616]: lookup 192.168.4.1/32: zebra route dev (none) May 12 16:00:22 raspberrypi nhrpd[15616]: lookup 22.22.22.1/32: nhrp_if=gre1 May 12 16:00:22 raspberrypi nhrpd[15616]: Shortcut: 192.168.4.1/24 is at proto 22.22.22.2 dst_proto 192.168.4.1 cie-nbma 169.254.50.50 nat-nbma (unspec) cie-holdtime 600 May 12 16:00:22 raspberrypi nhrpd[15616]: Shortcut: cache found, update binding May 12 16:00:22 raspberrypi nhrpd[15616]: cache: new type 0/4, or peer diff, or mtu 0/0, nbma (unspec) --> 169.254.50.50 (map 0) May 12 16:00:22 raspberrypi nhrpd[15616]: cache: gre1 22.22.22.2: accept May 12 16:00:22 raspberrypi nhrpd[15616]: cache: update binding for 22.22.22.2 dev gre1 from (deleted) peer.vc.nbma 169.254.50.50 to 169.254.50.50 May 12 16:00:22 raspberrypi nhrpd[15616]: cache (remote_nbma_natoa set): Update binding for 22.22.22.2 dev gre1 from (deleted) peer.vc.nbma 169.254.50.50 to 169.254.50.50 May 12 16:00:22 raspberrypi nhrpd[15616]: Zebra send: route add 22.22.22.2/32 nexthop <onlink> metric 0 count 1 dev gre1 May 12 16:00:22 raspberrypi nhrpd[15616]: Shortcut 192.168.4.0/24 created May 12 16:00:22 raspberrypi nhrpd[15616]: Shortcut: calling update_binding May 12 16:00:22 raspberrypi nhrpd[15616]: Shortcut: forcing renewal of zebra announce on prefix change peer 22.22.22.2 ht 600 cur nbma 169.254.50.50 dev gre1 May 12 16:00:22 raspberrypi nhrpd[15616]: Shortcut: route install 192.168.4.0/24 nh (unspec) dev gre1 May 12 16:00:22 raspberrypi nhrpd[15616]: Zebra send: route add 192.168.4.0/24 nexthop <onlink> metric 0 count 1 dev gre1 May 12 16:00:22 raspberrypi nhrpd[15616]: Shortcut: Resolution reply handled May 12 16:00:22 raspberrypi nhrpd[15616]: Netlink: Received msg_type 28, msg_flags 0 May 12 16:00:22 raspberrypi nhrpd[15616]: Netlink: new-neigh 22.22.22.2 dev gre1 lladdr 169.254.50.50 nud 0x2 cache used 0 type 4 May 12 16:00:22 raspberrypi zebra[15602]: netlink_route_multipath: RTM_NEWROUTE 22.22.22.2/32 vrf 0(254) May 12 16:00:22 raspberrypi zebra[15602]: _netlink_route_build_singlepath: (single-path): 22.22.22.2/32 nexthop via if 10 vrf default(0) May 12 16:00:22 raspberrypi zebra[15602]: netlink_talk: netlink-dp (NS 0) type RTM_NEWROUTE(24), len=52 seq=23 flags 0x501 May 12 16:00:22 raspberrypi zebra[15602]: netlink_route_multipath: RTM_NEWROUTE 192.168.4.0/24 vrf 0(254) May 12 16:00:22 raspberrypi zebra[15602]: _netlink_route_build_singlepath: (single-path): 192.168.4.0/24 nexthop via if 10 vrf default(0) May 12 16:00:22 raspberrypi zebra[15602]: netlink_talk: netlink-dp (NS 0) type RTM_NEWROUTE(24), len=52 seq=25 flags 0x501 May 12 16:00:22 raspberrypi nhrpd[15616]: if-route-add: 22.22.22.2/32 via 0.0.0.0 dev gre1 May 12 16:00:22 raspberrypi nhrpd[15616]: if-route-add: 192.168.4.0/24 via 0.0.0.0 dev gre1 May 12 16:00:22 raspberrypi nhrpd[15616]: Shortcut 192.168.4.0/24 used and expiring May 12 16:00:22 raspberrypi nhrpd[15616]: lookup 192.168.4.1/32: zebra route dev gre1 May 12 16:00:22 raspberrypi nhrpd[15616]: lookup 0.0.0.0/32: zebra route dev wlan0 May 12 16:00:22 raspberrypi nhrpd[15616]: lookup 192.168.20.1/32: zebra route dev wlan0 May 12 16:00:22 raspberrypi nhrpd[15616]: lookup 0.0.0.0/32: zebra route dev wlan0 May 12 16:00:22 raspberrypi nhrpd[15616]: Shortcut 192.168.4.1/32 purged May 12 16:00:23 raspberrypi zebra[15602]: netlink_parse_info: netlink-listen (NS 0) type RTM_NEWNEIGH(28), len=72, seq=0, pid=0 May 12 16:00:23 raspberrypi nhrpd[15616]: Netlink: Received msg_type 28, msg_flags 0 May 12 16:00:23 raspberrypi nhrpd[15616]: Netlink: new-neigh 22.22.22.1 dev gre1 lladdr 169.254.50.51 nud 0x4 cache used 1 type 5 May 12 16:00:23 raspberrypi zebra[15602]: #011Neighbor Entry received is not on a VLAN or a BRIDGE, ignoring May 12 16:00:23 raspberrypi zebra[15602]: netlink_parse_info: netlink-listen (NS 0) type RTM_GETNEIGH(30), len=64, seq=0, pid=0 May 12 16:00:23 raspberrypi nhrpd[15616]: Netlink: Received msg_type 30, msg_flags 1 May 12 16:00:23 raspberrypi zebra[15602]: Received RTM_GETNEIGH, ignoring May 12 16:00:23 raspberrypi nhrpd[15616]: Netlink: Received msg_type 28, msg_flags 0 May 12 16:00:23 raspberrypi zebra[15602]: netlink_parse_info: netlink-listen (NS 0) type RTM_NEWNEIGH(28), len=76, seq=0, pid=0 May 12 16:00:23 raspberrypi zebra[15602]: #011Neighbor Entry received is not on a VLAN or a BRIDGE, ignoring May 12 16:00:24 raspberrypi zebra[15602]: netlink_parse_info: netlink-listen (NS 0) type RTM_NEWNEIGH(28), len=64, seq=0, pid=0 May 12 16:00:24 raspberrypi nhrpd[15616]: Netlink: Received msg_type 28, msg_flags 0 May 12 16:00:24 raspberrypi zebra[15602]: #011Neighbor Entry received is not on a VLAN or a BRIDGE, ignoring May 12 16:00:24 raspberrypi zebra[15602]: netlink_parse_info: netlink-listen (NS 0) type RTM_GETNEIGH(30), len=64, seq=0, pid=0 May 12 16:00:24 raspberrypi zebra[15602]: Received RTM_GETNEIGH, ignoring May 12 16:00:24 raspberrypi nhrpd[15616]: Netlink: Received msg_type 30, msg_flags 1 May 12 16:00:25 raspberrypi nhrpd[15616]: Shortcut 192.168.4.0/24 purged May 12 16:00:25 raspberrypi nhrpd[15616]: Shortcut: notify cache down because cache?no or ri?n/a May 12 16:00:25 raspberrypi nhrpd[15616]: Zebra send: route del 192.168.4.0/24 nexthop <onlink> metric 0 count 1 dev none May 12 16:00:25 raspberrypi nhrpd[15616]: Netlink: Received msg_type 28, msg_flags 0 May 12 16:00:25 raspberrypi zebra[15602]: netlink_parse_info: netlink-listen (NS 0) type RTM_NEWNEIGH(28), len=64, seq=0, pid=0 May 12 16:00:25 raspberrypi zebra[15602]: #011Neighbor Entry received is not on a VLAN or a BRIDGE, ignoring May 12 16:00:25 raspberrypi nhrpd[15616]: Netlink: Received msg_type 30, msg_flags 1 May 12 16:00:25 raspberrypi zebra[15602]: netlink_parse_info: netlink-listen (NS 0) type RTM_GETNEIGH(30), len=64, seq=0, pid=0 May 12 16:00:25 raspberrypi zebra[15602]: Received RTM_GETNEIGH, ignoring May 12 16:00:25 raspberrypi zebra[15602]: netlink_route_multipath: RTM_NEWROUTE 192.168.4.0/24 vrf 0(254) May 12 16:00:25 raspberrypi zebra[15602]: _netlink_route_build_singlepath: (recursive, single-path): 192.168.4.0/24 nexthop via 22.22.22.1 if 10 vrf default(0) May 12 16:00:25 raspberrypi zebra[15602]: netlink_talk: netlink-dp (NS 0) type RTM_NEWROUTE(24), len=60 seq=27 flags 0x501 May 12 16:00:25 raspberrypi nhrpd[15616]: if-route-add: 192.168.4.0/24 via 22.22.22.1 dev (none) May 12 16:00:26 raspberrypi zebra[15602]: netlink_parse_info: netlink-listen (NS 0) type RTM_NEWNEIGH(28), len=64, seq=0, pid=0 May 12 16:00:26 raspberrypi nhrpd[15616]: Netlink: Received msg_type 28, msg_flags 0 May 12 16:00:26 raspberrypi zebra[15602]: #011Neighbor Entry received is not on a VLAN or a BRIDGE, ignoring May 12 16:00:30 raspberrypi zebra[15602]: netlink_parse_info: netlink-listen (NS 0) type RTM_NEWADDR(20), len=72, seq=0, pid=0 ----------------------------------------------------------------------------------------------------------------------- ________________________________ 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).

1 0

Log rotation - newsyslog
by Rudy Rucker 12 May '20

12 May '20

Hi, I zebra.log gets big. I set up rotation: #grep zeb /etc/newsyslog.conf /var/log/frr/zebra.log frr:network 644 5 5000 * N but zebra keeps keeps the file handle open and continues to write to the rotated log - zebra.0 [1] is there a signal I can send to zebra (and other daemons) without stopping routing? [2] feature request: have daemons check if inode file name has changed and automatically close/open handle on change. PS: zebra.0 is full of mostly this crud: 2020/05/05 14:38:41 ZEBRA: [EC 100663303] kernel_rtm: 2600:1419:e::/48: rtm_write() unexpectedly returned -4 for command RTM_DELETE 2020/05/05 14:38:41 ZEBRA: [EC 100663303] kernel_rtm: 2804:2e40::/32: rtm_write() unexpectedly returned -4 for command RTM_DELETE 2020/05/05 14:38:41 ZEBRA: [EC 100663303] kernel_rtm: 2804:1768::/33: rtm_write() unexpectedly returned -4 for command RTM_DELETE 2020/05/05 14:38:43 ZEBRA: [EC 100663303] kernel_rtm: 2a0b:21c0:4000::/36: rtm_write() unexpectedly returned -4 for command RTM_DELETE 2020/05/05 14:38:47 ZEBRA: [EC 100663303] kernel_rtm: 2a0b:21c0:4000::/36: rtm_write() unexpectedly returned -4 for command RTM_DELETE running 7.2.1. I couldn't figure out log filter to get rid of RTM_DELETEs. Advice? # zebra.conf: log file /var/log/frr/zebra.log errors Thanks, Rudy

3 4

vtysh line length
by Jens Link 28 Apr '20

28 Apr '20

Hi, as I can't find anything in the documentation and on google, but maybe I just search wrong. Can the line length of vtysh be changes? It looks like its wrapping lines at 80 columns which makes it harder to parse the output in shell script. Jens -- ---------------------------------------------------------------------------- | Delbrueckstr. 41 | 12051 Berlin, Germany | +49-151-18721264 | | http://blog.quux.de | jabber: jenslink(a)quux.de | --------------- | ----------------------------------------------------------------------------

4 5

Is there some performance report and bugfix list about FRR and QUAGGA ?
by Simon Jones 26 Apr '20

26 Apr '20

Hi all, Now we need to compare QUAGGA and FRR, used for BGP stack, with lots of routes and large QPS. So, 1) Is there some performance report about FRR and QUAGGA? Like RIB size, FIB size, speed of FIB route instoring, speed of route withdraw, etc. 2) Is there some bugfix list which FRR fixed and QUAGGA not fixed. Thank you !!! ---- Simon Jones

2 1