Send kea-dev mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/kea-dev
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of kea-dev digest..."
Today's Topics:
1. Re: kea 0.9.2 and tunl0 interfaces (Marcin Siodelski)
2. Re: kea 0.9.2 and tunl0 interfaces (Angelo Failla)
3. Re: kea 0.9.2 and tunl0 interfaces (Francis Dupont)
4. Re: kea 0.9.2 and tunl0 interfaces (Francis Dupont)
5. Re: kea 0.9.2 and tunl0 interfaces (Angelo Failla)
6. Re: kea 0.9.2 and tunl0 interfaces (Marcin Siodelski)
7. Re: kea 0.9.2 and tunl0 interfaces (Templin, Fred L)
----------------------------------------------------------------------
Message: 1
Date: Wed, 18 Nov 2015 16:05:37 +0100
From: Marcin Siodelski <[email protected]>
To: Angelo Failla <[email protected]>, Francis Dupont <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [kea-dev] kea 0.9.2 and tunl0 interfaces
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
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
> [email protected]
> 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
------------------------------
Message: 2
Date: Wed, 18 Nov 2015 15:09:16 +0000
From: Angelo Failla <[email protected]>
To: Marcin Siodelski <[email protected]>, Francis Dupont
<[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [kea-dev] kea 0.9.2 and tunl0 interfaces
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
>
>Is this something that used to work but stopped working after upgrade of
>Kea?
Yes
>Could you enable logging at the debug severity with debug level at 99
>and provide some log output from your tests?
I think you don?t need to worry anymore, I just fixed it. \o/
I setup the VIP as an alias of the eth0 interface and it started working again
:)
What I did:
# ip addr add "${VIP_IP}/32" dev eth0
Then changed json config:
"interfaces-config": {
"interfaces": [
?*"
]
}
Before I had interface_name/IP in them.
------------------------------
Message: 3
Date: Wed, 18 Nov 2015 17:00:53 +0000
From: Francis Dupont <[email protected]>
To: Angelo Failla <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [kea-dev] kea 0.9.2 and tunl0 interfaces
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
Usually when tshark & co can see the packet but not the application
the culprit is the firewall.
Regards
Francis Dupont <[email protected]>
------------------------------
Message: 4
Date: Wed, 18 Nov 2015 17:06:17 +0000
From: Francis Dupont <[email protected]>
To: Angelo Failla <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [kea-dev] kea 0.9.2 and tunl0 interfaces
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
interface_name/IP is special so IMHO you should keep it.
Regards
Francis Dupont <[email protected]>
PS: I know my DHCPv4-over-DHCPv6 requires this special config
(the problem was obvious but I had to dig into the doc for the solution
which was this special config).
------------------------------
Message: 5
Date: Wed, 18 Nov 2015 17:09:12 +0000
From: Angelo Failla <[email protected]>
To: Francis Dupont <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [kea-dev] kea 0.9.2 and tunl0 interfaces
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
Nah it wasn?t a firewall issue for me, KEA 0.9.2 just doesn't like receiving
packets on tunl0 for some reason, while 0.9 did.
Adding the IP of our VIP to eth0 fixed the problem for me.
I am not sure why, maybe something has changed in the way you deal with
interfaces/sockets?
I don?t think it?s something you should put effort into. I am happy with the
way it works now :-)
Thanks for the swift replies to this thread!
--
Angelo Failla
Cluster Infrastructure - Dublin
[email protected]
On 11/18/15, 5:00 PM, "Francis Dupont" <[email protected]> wrote:
>Usually when tshark & co can see the packet but not the application
>the culprit is the firewall.
>
>Regards
>
>Francis Dupont <[email protected]>
------------------------------
Message: 6
Date: Wed, 18 Nov 2015 18:35:25 +0100
From: Marcin Siodelski <[email protected]>
To: Angelo Failla <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [kea-dev] kea 0.9.2 and tunl0 interfaces
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
On 18.11.2015 18:09, Angelo Failla wrote:
> Nah it wasn?t a firewall issue for me, KEA 0.9.2 just doesn't like
> receiving packets on tunl0 for some reason, while 0.9 did.
> Adding the IP of our VIP to eth0 fixed the problem for me.
> I am not sure why, maybe something has changed in the way you deal
> with interfaces/sockets?
> I don?t think it?s something you should put effort into. I am happy
> with the way it works now :-)
> Thanks for the swift replies to this thread!
>
We probably won't look into this immediately, but it will be good to
have a look into this in the future. I'll give it a try when I have time.
Marcin
------------------------------
Message: 7
Date: Wed, 18 Nov 2015 17:42:24 +0000
From: "Templin, Fred L" <[email protected]>
To: Marcin Siodelski <[email protected]>, Angelo Failla
<[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [kea-dev] kea 0.9.2 and tunl0 interfaces
Message-ID:
<2134f8430051b64f815c691a62d9831832f50...@xch-blv-504.nw.nos.boeing.com>
Content-Type: text/plain; charset="utf-8"
I know that kea 0.9.2 works over TUN/TAP interfaces, which I realize is a
different beast than tunl0. However, the two are alike in that some form
of multicast mapping is needed and the MTU is reduced due to encaps
overhead. Apart from that, I did not need to do anything special in the
kea config to make it work.
Thanks - Fred
[email protected]
> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On
> Behalf Of Marcin Siodelski
> Sent: Wednesday, November 18, 2015 9:35 AM
> To: Angelo Failla
> Cc: [email protected]
> Subject: Re: [kea-dev] kea 0.9.2 and tunl0 interfaces
>
>
> On 18.11.2015 18:09, Angelo Failla wrote:
> > Nah it wasn?t a firewall issue for me, KEA 0.9.2 just doesn't like
> > receiving packets on tunl0 for some reason, while 0.9 did.
> > Adding the IP of our VIP to eth0 fixed the problem for me.
> > I am not sure why, maybe something has changed in the way you deal
> > with interfaces/sockets?
> > I don?t think it?s something you should put effort into. I am happy
> > with the way it works now :-)
> > Thanks for the swift replies to this thread!
> >
>
> We probably won't look into this immediately, but it will be good to
> have a look into this in the future. I'll give it a try when I have time.
>
> Marcin
> _______________________________________________
> kea-dev mailing list
> [email protected]
> https://lists.isc.org/mailman/listinfo/kea-dev
------------------------------
_______________________________________________
kea-dev mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-dev
End of kea-dev Digest, Vol 20, Issue 9
**************************************
