[kea-dev] kea 0.9.2 and tunl0 interfaces

[Marcin Siodelski]

On 18.11.2015 15:49, Angelo Failla wrote:
> 
>> ISC DHCP has a PREINIT script to solve this situation but I don't understand
>> how you can get an interface down on a server (PREINIT scripts are for
>> clients). 
> 
> One word: containers. :P
> 
> 
>> IMHO you should launch Kea only when the interface is UP,
>> RUNNING and has an IPv4 address (it seems it doesn't matter this address
>> is 0.0.0.0).
> 
> Yeah see my last message, was my fault I forgot to up the interface, now that the interface is up the server doesn’t complain about tunl0.
> 
> However it’s still not responding to DISCOVER packets:
> 
> This is a tshark dump on the dhcp server side:
> 
> 110.641303 10.88.105.10 -> 10.127.255.68 DHCP DHCP Discover - Transaction ID 0xc9cc2bea
> 110.641303 10.88.105.10 -> 10.127.255.68 DHCP DHCP Discover - Transaction ID 0xc9cc2bea
> 112.618545 10.88.105.10 -> 10.127.255.68 DHCP DHCP Discover - Transaction ID 0xc9cc2bea
> 112.618545 10.88.105.10 -> 10.127.255.68 DHCP DHCP Discover - Transaction ID 0xc9cc2bea
> 116.573179 10.88.105.10 -> 10.127.255.68 DHCP DHCP Discover - Transaction ID 0xc9cc2bea
> 116.573179 10.88.105.10 -> 10.127.255.68 DHCP DHCP Discover - Transaction ID 0xc9cc2bea
> 124.482385 10.88.105.10 -> 10.127.255.68 DHCP DHCP Discover - Transaction ID 0xc9cc2bea
> 124.482385 10.88.105.10 -> 10.127.255.68 DHCP DHCP Discover - Transaction ID 0xc9cc2bea
> 140.300951 10.88.105.10 -> 10.127.255.68 DHCP DHCP Discover - Transaction ID 0xc9cc2bea
> 140.300951 10.88.105.10 -> 10.127.255.68 DHCP DHCP Discover - Transaction ID 0xc9cc2bea
> 180.670604 10.88.105.10 -> 10.127.255.68 DHCP DHCP Discover - Transaction ID 0x150ab12
> 180.670604 10.88.105.10 -> 10.127.255.68 DHCP DHCP Discover - Transaction ID 0x150ab12
> 184.680157 10.88.105.10 -> 10.127.255.68 DHCP DHCP Discover - Transaction ID 0x150ab12
> 184.680157 10.88.105.10 -> 10.127.255.68 DHCP DHCP Discover - Transaction ID 0x150ab12
> 192.699151 10.88.105.10 -> 10.127.255.68 DHCP DHCP Discover - Transaction ID 0x150ab12
> 192.699151 10.88.105.10 -> 10.127.255.68 DHCP DHCP Discover - Transaction ID 0x150ab12
> 
> 
> 
> 10.127.255.68 is the IP of the tunl0 interface
> 
> 
> 10.88.105.10 is the IP of the RSW dhcp relayer
> 
> 
> Something is wrong there, I see the packets hitting my machine but the server isn’t picking them up
> 
> I see nothing in the server logs.
> 
> Ip addr output on the dhcp server side:
> 
> 6: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
>     link/ether 00:02:c9:dd:0d:5e brd ff:ff:ff:ff:ff:ff
>     inet 10.35.139.79/24 brd 10.35.139.255 scope global br0
>        valid_lft forever preferred_lft forever
>     inet6 2401:db00:3011:b:face:0:3b:0/64 scope global
>        valid_lft forever preferred_lft forever
>     inet6 fe80::202:c9ff:fedd:d5e/64 scope link
>        valid_lft forever preferred_lft forever
> 
> 9: tunl0: <NOARP,UP,LOWER_UP> mtu 0 qdisc noqueue state UNKNOWN
>     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
> 
> Rack switch configuration:
> 
> 
> interface Vlan2105
>   no ip redirects
>   ip address 10.88.105.10/24
>   ip directed-broadcast
>   ipv6 address 2401:db00:3010:4069::000a/64
>   ipv6 nd ra-interval 4
>   ipv6 nd prefix 2401:db00:3010:4069::/64
>   no ipv6 redirects
>   ip dhcp relay address 10.127.255.68 <————————— this is the same ip as in tunl0 on the server side
>   no shutdown
>   mtu 9000
>   no autostate
>   description SERVERS
>   vrrp 1
>     priority 30
>     address 10.88.105.1
>     no shutdown
>   vrrp 2
>     priority 30
>     address 10.88.105.2
>     no shutdown
> 
> _______________________________________________
> kea-dev mailing list
> kea-dev at lists.isc.org
> https://lists.isc.org/mailman/listinfo/kea-dev
> 

Is this something that used to work but stopped working after upgrade of
Kea?

Could you enable logging at the debug severity with debug level at 99
and provide some log output from your tests?

Marcin