Thank you for your time looking through this. I agree, it should be installed in the routing table :)
I do have the route advertised via eBGP and iBGP, but the eBGP neighbors are just metallb pods in my kubernetes cluster.
I think you accidentally a word here, so I'm not exactly sure what you're asking but I think you want to know if the route arrives at router01 from ebgp and ibgp and the answer is no. The metallb neighbors only advertise LoadBalancerIPs for services available on their nodes.
If I reset all the eBGP connections nothing changes:
I do have the route advertised via eBGP and iBGP, but the eBGP neighbors are just metallb pods in my kubernetes cluster.
QuoteDoes the route 192.168.131.2 from iBGP as well eBGP on router1?
I think you accidentally a word here, so I'm not exactly sure what you're asking but I think you want to know if the route arrives at router01 from ebgp and ibgp and the answer is no. The metallb neighbors only advertise LoadBalancerIPs for services available on their nodes.
Code Select
router01.example.com# show ip bgp neighbors 192.168.128.46 received-routes
BGP table version is 36, local router ID is 192.168.255.3, vrf id 0
Default local pref 100, local AS 64601
Status codes: s suppressed, d damped, h history, u unsorted, * valid, > best, = multipath,
i internal, r RIB-failure, S Stale, R Removed
Nexthop codes: @NNN nexthop's vrf id, < announce-nh-self
Origin codes: i - IGP, e - EGP, ? - incomplete
RPKI validation codes: V valid, I invalid, N Not found
Network Next Hop Metric LocPrf Weight Path
*> 192.168.255.8/32 192.168.128.46 0 0 64641 i
*> 192.168.255.18/32
192.168.128.46 0 0 64641 i
*> 192.168.255.23/32
192.168.128.46 0 0 64641 i
Total number of prefixes 3
If I reset all the eBGP connections nothing changes:
Code Select
router01.example.com# clear ip bgp 192.168.128.41
router01.example.com# clear ip bgp 192.168.128.42
router01.example.com# clear ip bgp 192.168.128.43
router01.example.com# clear ip bgp 192.168.128.44
router01.example.com# clear ip bgp 192.168.128.45
router01.example.com# clear ip bgp 192.168.128.46
router01.example.com# show ip bgp sum
IPv4 Unicast Summary:
BGP router identifier 192.168.255.3, local AS number 64601 VRF default vrf-id 0
BGP table version 85
RIB entries 25, using 3200 bytes of memory
Peers 7, using 116 KiB of memory
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd PfxSnt Desc
192.168.128.41 4 64641 16 40 85 0 0 00:00:20 6 13 N/A
192.168.128.42 4 64641 16 35 85 0 0 00:00:04 4 13 N/A
192.168.128.43 4 64641 16 37 85 0 0 00:00:03 3 13 N/A
192.168.128.44 4 64641 16 34 85 0 0 00:00:02 4 13 N/A
192.168.128.45 4 64641 16 37 85 0 0 00:00:01 6 13 N/A
192.168.128.46 4 64641 14 33 0 0 0 00:00:00 0 0 N/A
192.168.255.4 4 64601 17 26 85 0 0 00:09:00 12 12 FRRouting/10.4.1
Total number of neighbors 7
router01.example.com#
root@router01:~ # netstat -rn -f inet| grep 131
192.168.131.1 link#13 UH lo1
"