BGP routes not being inserted into route table.

General questions
1

Simple question hopefully. Trying to work up a solution with VYOS as an NFV service chained router on an SD-WAN appliance to replace all my Cisco WAN edge devices.

Everything is working perfetly and I have eBGP up and peered with my BGP Core and I am receiving routes as expected(See below)

user@vyos:~$ sh ip bgp neighbors 172.16.100.14 received-routes

BGP table version is 0, local router ID is 172.16.100.13
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale, R Removed
Origin codes: i - IGP, e - EGP, ? - incomplete

Network Next Hop Metric LocPrf Weight Path
*> 10.111.10.0/24 172.16.100.14 0 65100 42 65100 65042 i
*> 10.111.20.0/24 172.16.100.14 0 65100 42 65100 65042 i
*> 10.111.30.0/24 172.16.100.14 0 65100 42 65100 65042 i
*> 10.114.0.0/16 172.16.100.14 0 65100 42 65100 65042 i
*> 172.16.100.0/30 172.16.100.14 0 65100 42 65100 65042 i
*> 172.16.200.0/30 172.16.100.14 0 65100 42 65100 65042 i

HOWEVER these routes are not making it into the route table(See Below)
user@vyos:~$ sh ip route

Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF,
I - ISIS, B - BGP, > - selected route, * - FIB route

S>* 10.114.0.0/16 [1/0] is directly connected, Null0, bh
C>* 10.114.0.0/29 is directly connected, eth3
C>* 127.0.0.0/8 is directly connected, lo
C>* 172.16.100.12/30 is directly connected, eth5
C>* 192.168.100.0/24 is directly connected, eth4

I have tried several iterations of inbound route-maps / prefix-lists etc to no avail.

Any help would be greatly appreciated.

Thanks,
Dave

2

Post your config

3

Config Attached

interfaces {
ethernet eth3 {
address 10.114.0.3/29
duplex auto
hw-id 52:54:00:b2:e7:c6
smp_affinity auto
speed auto
}
ethernet eth4 {
address 192.168.100.15/24
duplex auto
hw-id 52:54:00:32:f4:65
smp_affinity auto
speed auto
}
ethernet eth5 {
address 172.16.100.13/30
duplex auto
hw-id 52:54:00:56:7c:31
smp_affinity auto
speed auto
}
loopback lo {
}
}
policy {
prefix-list AS65042 {
rule 10 {
action permit
prefix 10.111.10.0/24
}
rule 20 {
action permit
prefix 10.111.20.0/24
}
}
}
protocols {
bgp 65042 {
neighbor 172.16.100.14 {
prefix-list {
import AS65042
}
remote-as 65100
route-map {
import AS65042-IN
}
soft-reconfiguration {
inbound
}
update-source 172.16.100.13
}
network 10.114.0.0/16 {
}
parameters {
}
}
static {
route 10.114.0.0/16 {
blackhole {
}
}
}
}
service {
ssh {
port 22
}
}
system {
config-management {
commit-revisions 20
}
console {
device ttyS0 {
speed 9600
}
}
host-name vyos
}
ntp {
server 0.pool.ntp.org {
}
server 1.pool.ntp.org {
}
server 2.pool.ntp.org {
}
}
package {
auto-sync 1
repository community {
components main
distribution helium
password ****************
url http://packages.vyos.net/vyos
username “”
}
}
syslog {
global {
facility all {
level notice
}
facility protocols {
level debug
}
}
}
time-zone UTC
}

4

sh ip bgp neighbors 172.16.100.14 received-routes
Network Next Hop Metric LocPrf Weight Path
*> 10.111.10.0/24 172.16.100.14 0 65100 42 65100 65042 I

Those routes originates from your own AS! (65042)
As loop prevention, these route won’t make it to forwarding database

5

Correct however that is the only route that is local.

*> 10.111.10.0/24 172.16.100.14 0 65100 42 65100 65042 i <-- learned via BGP Core Not sure why VYOS is picking it up as originated from himself
*> 10.111.20.0/24 172.16.100.14 0 65100 42 65100 65042 i <-- learned via BGP Core Not sure why VYOS is picking it up as originated from himself
*> 10.111.30.0/24 172.16.100.14 0 65100 42 65100 65042 i <-- learned via BGP Core Not sure why VYOS is picking it up as originated from himself
*> 10.114.0.0/16 172.16.100.14 0 65100 42 65100 65042 i <-- This is the only local route
*> 172.16.100.0/30 172.16.100.14 0 65100 42 65100 65042 i <-- learned via BGP Core Not sure why VYOS is picking it up as originated from himself
*> 172.16.200.0/30 172.16.100.14 0 65100 42 65100 65042 i <-- learned via BGP Core Not sure why VYOS is picking it up as originated from himself

6

DAMMMIT! I inadvertently created an iBGP mesh over my eBGP core :slight_smile: Too many late nites