3 Oct
2018
3 Oct
'18
11:40 p.m.
Does the ampr gateway know about the networks routed via BGP?
Maybe the mistake is that it consults the route tables in some order (first check if there
is a BGP route, if so
then route that way, then check if there is a tunnel route, if so route via tunnel).
This will fail on my test system because it has a /32 route via IPIP but the address is
within 44.137.0.0/16 routed using BGP.
The routing tables should be all merged into one so that it recognizes this /32 as more
specific than the /16 and it routes
via the tunnel not via BGP.
Part of our routing table:
default via 213.222.29.193 dev eth0
44.0.0.0/8 via 213.222.29.193 dev eth0 src 44.137.0.1
44.0.0.1 via 169.228.34.84 dev tunl0 proto ampr-ripd metric 4 onlink
44.2.0.1 via 191.183.136.1 dev tunl0 proto ampr-ripd metric 4 onlink
(213.222.29.193 is the router of our ISP)
Rob