[kea-dev] kea 0.9.2 and tunl0 interfaces

Angelo Failla pallotron at fb.com
Wed Nov 18 14:32:44 UTC 2015


ok the problem was that I forgot to up the interface. :P
so I did a `ip link set dev tunl0 up` and now I see the server not complaining about it anymore...
--
Angelo Failla
Cluster Infrastructure - Dublin
Pallotron at fb.com

On 11/18/15, 2:16 PM, "Angelo Failla" <pallotron at fb.com<mailto:pallotron at fb.com>> wrote:

Hello everybody,

At Facebook we use BGP anycast technology to balance DHCP traffic. To do so we advertise a global VIP via BGP, VIP that then ends up in the rack switch dhcp relayers.
We then receive UDP datagrams that have the VIP IP as the destination IP, therefore we need to bring up tunl0/ip6tnl0 interfaces onto our machines that have the VIP assigned so that applications can get those datagrams destined to the VIP address.

I’ve been testing kea 0.9.2 in our production environment and I’ve noticed a regression compared to 0.9:

KEA refuses to listen on tunl0 or ip6tnl0 interfaces.

I get an error like this:

2015-11-18 06:09:11.451 WARN [kea-dhcp4.dhcpsrv/650885] DHCPSRV_OPEN_SOCKET_FAIL failed to open socket: the interface tunl0 is down or has no usable IPv4 addresses configured

Even though I assign an IP to the interface, see:

$ ip addr show tunl0
9: tunl0: <NOARP> mtu 0 qdisc noop state DOWN
    link/ipip 0.0.0.0 brd 0.0.0.0
    inet 10.127.255.68/32 scope global tunl0
       valid_lft forever preferred_lft forever

And basically our DICOVERY packets are never seen by the server.
I am currently reading lib/dhcp/iface_mgr.cc but I wanted to give you an heads up...
--
Angelo Failla
Cluster Infrastructure - Dublin
Pallotron at fb.com<mailto:Pallotron at fb.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/kea-dev/attachments/20151118/c7b9a680/attachment.html>


More information about the kea-dev mailing list