[FROG] received-routes.. doesn't work?

[Mark Kamichoff]

On Mon, Aug 28, 2017 at 10:20:42PM -0500, Mark Kamichoff wrote:
> Hi - 
> 
> I'm running various 3.1-dev versions of FRR and noticed that the "show
> ip bgp nei <peer> received-routes" doesn't seem to work as expected on
> any of them.
> 
> Here's an example of the relevant parts of the configuration:
> 
> !
> router bgp 395460
>  neighbor 169.254.169.254 remote-as 64515
>  neighbor 169.254.169.254 password <snip>
>  neighbor 169.254.169.254 ebgp-multihop 2
>  address-family ipv4 unicast
>   neighbor 169.254.169.254 soft-reconfiguration inbound
>   neighbor 169.254.169.254 route-map DENY_ALL in
>   neighbor 169.254.169.254 route-map DENY_ALL out
>  exit-address-family
> !
> route-map DENY_ALL deny 65535
> !
> 
> orca# show ip bgp neighbors 169.254.169.254 routes 
> orca# show ip bgp neighbors 169.254.169.254 received-routes 
> BGP table version is 0, local router ID is 10.3.4.36
> Status codes: s suppressed, d damped, h history, * valid, > best, = multipath,
>               i internal, r RIB-failure, S Stale, R Removed
> Origin codes: i - IGP, e - EGP, ? - incomplete
> 
>    Network          Next Hop            Metric LocPrf Weight Path
> orca# 
> 
> From tcpdump and other t-shooting I know that there is an IPv4 DFZ being
> received, but received-routes doesn't show any of the routes that should
> be in the adj-rib-in.
> 
> Oddly, if I remove the inbound route-map I see expected prefixes using
> the "routes" /and/ "received-routes" command.  If I put it back, the
> "received-routes" shows nothing once again.
> 
> It would almost seem like soft-reconfiguration isn't really enabled, but
> received-routes should give me an error if it wasn't and the neighbor
> information confirms that it is:
> 
> orca# show ip bgp neighbors 169.254.169.254
> <snip>
>  For address family: IPv4 Unicast
>   Update group 5, subgroup 5
>   Packet Queue length 0
>   Inbound soft reconfiguration allowed    <-----
> <snip>
> 
> This isn't limited to the IPv4 AF, either.  I've got IPv6 peers that
> echibit the same behavior.
> 
> Have I found a bug or am I doing something wrong?  I'm happy to file a
> bug report.
> 
> More info., if it helps:
> 
> orca# show version 
> FRRouting 3.1-dev ().
> Copyright 1996-2005 Kunihiro Ishiguro, et al.
> configured with:
>      '--build=x86_64-linux-gnu' '--prefix=/usr'
> '--includedir=${prefix}/include' '--mandir=${prefix}/share/man'
> '--infodir=${prefix}/share/info' '--sysconfdir=/etc'
> '--localstatedir=/var' '--disable-silent-rules'
> '--libexecdir=${prefix}/lib/frr' '--disable-maintainer-mode'
> '--disable-dependency-tracking'
> '--enable-exampledir=/usr/share/doc/frr/examples/'
> '--localstatedir=/var/run/frr' '--sbindir=/usr/lib/frr'
> '--sysconfdir=/etc/frr' '--enable-ospfapi=yes' '--enable-vtysh=yes'
> '--enable-isisd=yes' '--enable-multipath=256' '--enable-user=frr'
> '--enable-group=frr' '--enable-vty-group=frrvty'
> '--enable-configfile-mask=0640' '--enable-logfile-mask=0640'
> '--enable-werror' '--enable-gcc-rdynamic' '--with-libpam'
> '--enable-systemd=yes' '--enable-poll=yes' '--enable-cumulus=yes'
> '--enable-pimd=yes' '--enable-dependency-tracking' '--enable-bgp-vnc=no'
> 'build_alias=x86_64-linux-gnu'
> orca# 
> (orca:20:08:PDT)% uname -a
> Linux orca 4.9.0-3-amd64 #1 SMP Debian 4.9.25-1 (2017-05-02) x86_64 GNU/Linux
> 
> (the build is from August 26th)
> 
> Thanks!
> 
> - Mark

FWIW, I'm not sure which version this was fixed in, but the above works
as expected in version 5.0.1.

- Mark

-- 
Mark Kamichoff
prox at prolixium.com
https://www.prolixium.com/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.frrouting.org/pipermail/frog/attachments/20180901/761a9fc9/attachment.sig>