Re: [Kea-users] DHCPv6, shared network, and double-relay Solicit messages

2024-04-24 Thread Marek Hajduczenia
Of Darren Ankney Sent: Wednesday, April 24, 2024 4:00 AM To: Kea user's list Subject: Re: [Kea-users] DHCPv6, shared network, and double-relay Solicit messages This does not seem to be intended behavior: https://kea.readthedocs.io/en/kea-2.4.1/arm/dhcp6-srv.html#interface-configuration

Re: [Kea-users] DHCPv6, shared network, and double-relay Solicit messages

2024-04-24 Thread Darren Ankney
uot;enp0s2/2001:db8::1234:abcd" ] }, On Tue, Apr 23, 2024 at 7:04 PM Marek Hajduczenia wrote: > I have not been able to find a workaround for this problem on IPv6 side > for now. > > > > Marek > > > > *From:* Kea-users *On Behalf Of *Butler, > Glenn via Kea-u

Re: [Kea-users] DHCPv6, shared network, and double-relay Solicit messages

2024-04-23 Thread Marek Greško via Kea-users
Hello Marek, kea listens on UDP socket only for port 546. You should not use -t flag with netstat which shows only TCP. Marek On Tuesday, April 23rd, 2024 at 17:42, mxhajducze...@gmail.com wrote: > I wonder whether it has anything to do with the fact that DHCPv6 process does > not seem to

Re: [Kea-users] DHCPv6, shared network, and double-relay Solicit messages

2024-04-23 Thread Marek Hajduczenia
I have not been able to find a workaround for this problem on IPv6 side for now. Marek From: Kea-users On Behalf Of Butler, Glenn via Kea-users Sent: Tuesday, April 23, 2024 3:58 PM To: Kea user's list Cc: Butler, Glenn Subject: Re: [Kea-users] DHCPv6, shared network, and double

Re: [Kea-users] DHCPv6, shared network, and double-relay Solicit messages

2024-04-23 Thread Butler, Glenn via Kea-users
I need to figure this out also, as I run Kea in a container that can be destroyed and rebuilt anytime. I am thinking I will update the Kea config via a shell script run on boot/init. Would be nice if there was a "listen on all" option like 0.0.0.0 does for IPv4, but all the docs I have read

Re: [Kea-users] DHCPv6, shared network, and double-relay Solicit messages

2024-04-23 Thread Marek Hajduczenia
So I think I found the potential solution, though I am not sure I understand why this happens. I had to specifically configure the unicast IPv6 address in the “interfaces” clause, as follows "interfaces-config": { "interfaces": [ "enp6s18/2600:6ce4:0:42::130" ] },

Re: [Kea-users] DHCPv6, shared network, and double-relay Solicit messages

2024-04-23 Thread mxhajduczenia
I guess netstat is deprecated. “ss” seems to show the binding but … only to a link local address for some reason on the v6 side. root@server-kea-node1:~# ss -tulpn Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port Process

Re: [Kea-users] DHCPv6, shared network, and double-relay Solicit messages

2024-04-23 Thread mxhajduczenia
I wonder whether it has anything to do with the fact that DHCPv6 process does not seem to listen on port 546 root@server-kea-node1:/home/kea # sudo netstat -tulpn | grep LISTEN tcp0 0 127.0.0.1:8000 0.0.0.0:* LISTEN 628/kea-ctrl-agent tcp0 0

[Kea-users] DHCPv6, shared network, and double-relay Solicit messages

2024-04-23 Thread mxhajduczenia
Dear colleagues, I have been attempting to test a setup in the lab with DOCSIS CM operating in IPv6 mode only, where the DHCPv6 messages are relayed across the CMTS and the first-hop router (relay address 2600:6ce4:0:3e::1) towards a Kea server running 2.4 code (address 2600:6ce4:0:42::130).