not seeing statics being advertised to bgp neighbors
Hi, I have the following setup and am not seeing what I expect. I had this working before, so I am sure it is something I have changed in the configurations when automating them. I just can't see what it is. Situation is that that have a bunch of host aliases (/32) defined on the lo interface. For each of these, I create a static in bird so there is a route. Then I filter and forward those via BGP to the edge routers that talk to ISPs. A single machine is presenting a number of addresses in different routing blocks and addresses. I have attached the bird config for this machine. here is the list of loopback aliases [root@pnpborder1 bird]# ip addr show lo 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1 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 inet 198.49.100.18/32 brd 198.49.100.18 scope global lo valid_lft forever preferred_lft forever inet 8.25.217.45/32 brd 8.25.217.45 scope global lo valid_lft forever preferred_lft forever inet 8.6.161.18/32 brd 8.6.161.18 scope global lo valid_lft forever preferred_lft forever inet 8.5.161.45/32 brd 8.5.161.45 scope global lo valid_lft forever preferred_lft forever inet 198.49.100.45/32 brd 198.49.100.45 scope global lo valid_lft forever preferred_lft forever inet 8.25.217.18/32 brd 8.25.217.18 scope global lo valid_lft forever preferred_lft forever inet 4.7.20.4/32 brd 4.7.20.4 scope global lo valid_lft forever preferred_lft forever inet 4.7.20.5/32 brd 4.7.20.5 scope global lo valid_lft forever preferred_lft forever inet 173.1.2.36/32 brd 173.1.2.36 scope global lo valid_lft forever preferred_lft forever inet 173.1.2.37/32 brd 173.1.2.37 scope global lo valid_lft forever preferred_lft forever inet6 dead:beef::1/32 scope global valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever the routing table doesn't show the routes and the neighbors don't get them (did a tcpdump to make sure it wasn't filtering on the far side.) [root@pnpborder1 bird]# netstat -nr Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 - 0.0.0.0 ! - - - - 4.7.20.0 0.0.0.0 255.255.255.240 U 0 0 0 edge10Bvl801 4.7.20.0 0.0.0.0 255.255.255.240 U 0 0 0 edge10Avl801 10.100.16.0 0.0.0.0 255.255.240.0 U 0 0 0 eth4 10.100.32.0 0.0.0.0 255.255.240.0 U 0 0 0 eth5 10.201.0.0 0.0.0.0 255.255.240.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 172.18.10.0 0.0.0.0 255.255.255.0 U 0 0 0 edge10Bvl800 172.18.10.0 0.0.0.0 255.255.255.0 U 0 0 0 edge10Avl800 173.1.2.32 0.0.0.0 255.255.255.240 U 0 0 0 edge10Bvl803 173.1.2.32 0.0.0.0 255.255.255.240 U 0 0 0 edge10Avl803 can anyone spot what I did wrong? thanks, jerry -- Jerry Scharf, Soundhound DevOps "What could possibly go wrong?"
Sorry, forgot to say this is bird 1.4.5 install from centos epel. On 05/15/2017 06:38 PM, Jerry Scharf wrote:
Hi,
I have the following setup and am not seeing what I expect. I had this working before, so I am sure it is something I have changed in the configurations when automating them. I just can't see what it is.
Situation is that that have a bunch of host aliases (/32) defined on the lo interface. For each of these, I create a static in bird so there is a route. Then I filter and forward those via BGP to the edge routers that talk to ISPs. A single machine is presenting a number of addresses in different routing blocks and addresses.
I have attached the bird config for this machine.
here is the list of loopback aliases [root@pnpborder1 bird]# ip addr show lo 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1 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 inet 198.49.100.18/32 brd 198.49.100.18 scope global lo valid_lft forever preferred_lft forever inet 8.25.217.45/32 brd 8.25.217.45 scope global lo valid_lft forever preferred_lft forever inet 8.6.161.18/32 brd 8.6.161.18 scope global lo valid_lft forever preferred_lft forever inet 8.5.161.45/32 brd 8.5.161.45 scope global lo valid_lft forever preferred_lft forever inet 198.49.100.45/32 brd 198.49.100.45 scope global lo valid_lft forever preferred_lft forever inet 8.25.217.18/32 brd 8.25.217.18 scope global lo valid_lft forever preferred_lft forever inet 4.7.20.4/32 brd 4.7.20.4 scope global lo valid_lft forever preferred_lft forever inet 4.7.20.5/32 brd 4.7.20.5 scope global lo valid_lft forever preferred_lft forever inet 173.1.2.36/32 brd 173.1.2.36 scope global lo valid_lft forever preferred_lft forever inet 173.1.2.37/32 brd 173.1.2.37 scope global lo valid_lft forever preferred_lft forever inet6 dead:beef::1/32 scope global valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever
the routing table doesn't show the routes and the neighbors don't get them (did a tcpdump to make sure it wasn't filtering on the far side.) [root@pnpborder1 bird]# netstat -nr Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 - 0.0.0.0 ! - - - - 4.7.20.0 0.0.0.0 255.255.255.240 U 0 0 0 edge10Bvl801 4.7.20.0 0.0.0.0 255.255.255.240 U 0 0 0 edge10Avl801 10.100.16.0 0.0.0.0 255.255.240.0 U 0 0 0 eth4 10.100.32.0 0.0.0.0 255.255.240.0 U 0 0 0 eth5 10.201.0.0 0.0.0.0 255.255.240.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 172.18.10.0 0.0.0.0 255.255.255.0 U 0 0 0 edge10Bvl800 172.18.10.0 0.0.0.0 255.255.255.0 U 0 0 0 edge10Avl800 173.1.2.32 0.0.0.0 255.255.255.240 U 0 0 0 edge10Bvl803 173.1.2.32 0.0.0.0 255.255.255.240 U 0 0 0 edge10Avl803
can anyone spot what I did wrong?
thanks, jerry
-- Jerry Scharf, Soundhound DevOps "What could possibly go wrong?"
participants (1)
-
Jerry Scharf