Hi, I figured out a problem with the BIRD routing daemon. It is not possible to route BGP via IPIP tunnels. As you can see below the packets will be routed through the wrong device. Normally it should choose "ASIX" as right device, but it does not. root@cr01:/etc/bird# ip -6 route | grep 2a06:8187:fe48::/48 2a06:8187:fe48::/48 via 2a06:8187:fe01:100::2 dev vlan1000 proto bird src 2a06:8187:fe01::2 metric 1024 pref medium The interface configuration is the following: iface ASIX inet manual pre-up ip -6 tunnel add ASIX mode any local 2a07:59c6:d007::1 remote 2a00:1ca8:2a::730 ttl 255 pre-up ip link set dev ASIX mtu 1476 pre-up ip link set dev ASIX up pre-up ip address add 89.46.125.149/30 dev ASIX pre-up ip address add 2a06:8187:fe01:100::1/56 dev ASIX post-down ip -6 tunnel del ASIX root@cr01:/etc/bird# birdc6 -v 0001 BIRD 1.6.3 ready. bird> Maybe you can help me here? Kind regards. Joey
On Tue, Sep 12, 2017 at 12:45:25PM +0200, noc@joey-network.de wrote:
Hi,
I figured out a problem with the BIRD routing daemon. It is not possible to route BGP via IPIP tunnels. As you can see below the packets will be routed through the wrong device. Normally it should choose "ASIX" as right device, but it does not.
Hi I guess there could be a problem if the tunnel does not have a link-local address. Is that the case? BGP specification requires secondary link-local IP address on IPv6 BGP_NEXT_HOP attribute when primary (global) next hop is one hop away. BIRD enforces that on TX. See BGP option 'missing lladdr'. It is true that the requirement does not make sense for PTP interfaces, where there is no third party. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
participants (2)
-
noc@joey-network.de -
Ondrej Zajicek