ISC DHCP Users

DHCPDv6 and fixed hosts, not appearing in logs

Classic

List

Threaded

9 messages Options

sillysausage

DHCPDv6 and fixed hosts, not appearing in logs

Hi,

I'm having trouble with my clients authenticating with my DHCPDv6
server.

For some reason I see no activity on my DHCPv6 logs, I think I might
have not configured it correctly. DHCPv4 works correctly though!

When a user connects on DHCPv4 I see the lease go out in syslog. With
my DHCPv6 instance I see nothing :(

I any case I configured the rc script configurations in /etc/conf.d
correctly as indicated by this:

gateway:~# ps aux |grep dhcpd

1686 dhcp 0:00 /usr/sbin/dhcpd -4 -cf /etc/dhcp/dhcpd.conf
-q -pf /var/run/dhcp/dhcpd.pid
-lf /var/lib/dhcp/dhcpd.leases
-user dhcp -group dhcp eth0

1714 dhcp 0:00 /usr/sbin/dhcpd -6 -cf /etc/dhcp/dhcpdv6.conf
-q -pf /var/run/dhcp/dhcpdv6.pid
-lf /var/lib/dhcp/dhcpdv6.leases
-user dhcp -group dhcp eth0

I'm using Roy Marples's dhcpcd to do prefix delegation, as the ISC
dhcp server doesn't seem to have the PPP patch yet in the main code
base and my distribution (Alpine Linux), hasn't applied it.

More info about that: https://bugs.gentoo.org/show_bug.cgi?id=432652

> gateway:~# cat /etc/dhcpcd.conf
> # Enable extra debugging
> # debug
>
> # Allow users of this group to interact with dhcpcd via the control
> # socket.
> #controlgroup wheel
>
> # Inform the DHCP server of our hostname for DDNS.
> hostname gateway
>
> # Use the hardware address of the interface for the Client ID.
> #clientid
> # or
> # Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as
> # per RFC4361. Some non-RFC compliant DHCP servers do not reply with
> # this set. In this case, comment out duid and enable clientid above.
> duid
>
> # Persist interface configuration when dhcpcd exits.
> persistent
>
> # Rapid commit support.
> # Safe to enable by default because it requires the equivalent option
> # set on the server to actually work.
> option rapid_commit
>
> # A list of options to request from the DHCP server.
> option domain_name_servers, domain_name, domain_search, host_name
> option classless_static_routes
>
> # Most distributions have NTP support.
> option ntp_servers
> # Respect the network MTU.
> # Some interface drivers reset when changing the MTU so disabled by
> # default.
> #option interface_mtu
>
> # A ServerID is required by RFC2131.
> require dhcp_server_identifier
>
> # Generate Stable Private IPv6 Addresses instead of hardware based
> # ones
> # slaac private
>
> # A hook script is provided to lookup the hostname if not set by the
> # DHCP server, but it should not be run by default.
> nohook lookup-hostname
>
> # IPv6 Only
> ipv6only
>
> # Disable solicitations on all interfaces
> noipv6rs
>
> # Wait for IP before forking to background
> waitip 6
>
> # Don't install any default routes.
> # PPP has already set a default route
> nogateway
>
> # Don't touch DNS
> nohook resolv.conf
>
> # Use the interface connected to WAN
> interface ppp0
> ipv6rs # enable routing solicitation get the default IPv6 route
> iaid 1
> ia_pd 1/::/64 eth0/1/64

This seems to be working great. I can statically set my IP address to
the desired fixed address 2001:0db8:1234:0001::20

The intention is to have DHCPv6 issue me this IP address.

Here is my RADVD. I think it's working correctly.

> gateway:~# cat /etc/radvd.conf
> interface eth0 {
>
> # We are sending advertisments (route)
> AdvSendAdvert on;
>
> # When set, host use the administered (stateful) protocol
> # for address autoconfiguration. The use of this flag is
> # described in RFC 4862
> AdvManagedFlag on;
>
> # When set, host use the administered (stateful) protocol
> # for address autoconfiguration. For other (non-address)
> # information.
> # The use of this flag is described in RFC 4862
> AdvOtherConfigFlag on;
>
> # Suggested Maximum Transmission setting for using the
> # Hurricane Electric Tunnel Broker.
> # AdvLinkMTU 1480;
>
> # We have native Dual Stack IPv6 so we can use the regular MTU
> AdvLinkMTU 1500;
>
> prefix 2001:0db8:1234:0001::/64 {
> AdvOnLink on;
> AdvAutonomous on;
> AdvRouterAddr on;
> };
> };

I seem to get routes to the internet working with this.

I do understand with IPv6 I need radvd to push routes as DHCPv6 cannot
do this.

I'm trying to make it not send me an IP address though. I want DHCPv6
to do this. I'm trying to emulate my IPv4 configuration as much as
possible eg:

> authoritative;
> ddns-update-style interim;
>
> shared-network home {
> subnet 192.168.1.0 netmask 255.255.255.0 {
> range 192.168.1.10 192.168.1.240;
> option subnet-mask 255.255.255.0;
> option broadcast-address 192.168.1.255;
> option routers 192.168.1.1;
> option ntp-servers 192.168.1.1;
> option domain-name-servers 192.168.1.1;
> allow unknown-clients;
> }
>
> host my_workstation {
> hardware ethernet 00:53:00:FF:FF:11;
> fixed-address 192.168.1.30;
> option subnet-mask 255.255.255.0;
> option broadcast-address 192.168.1.255;
> option routers 192.168.1.1;
> option host-name "my_workstation";
> }

Finally my DHCPv6 configuration:

> gateway:~# cat /etc/dhcp/dhcpdv6.conf
> authoritative;
> ddns-update-style interim;
>
> shared-network home {
> subnet6 2001:0db8:1234:0001::/64 {
>
> # Range for clients to have an address from
> range6 2001:0db8:1234:0001::10 2001:0db8:1234:0001::254;
>
> # Range for temporary address
> range6 2001:0db8:1234:0001:: temporary;
>
> # Additional options
> allow unknown-clients;
> }
> }
>
> host my_workstation {
> hardware ethernet 00:53:00:FF:FF:22;
> host-identifier option
> dhcp6.client-id <DUID removed>
> fixed-address6 2001:0db8:1234:0001::20;
> fixed-prefix6 2001:0db8:1234:0001::/64;
> option dhcp6.name-servers 2001:0db8:1234:0001::1;
> option dhcp6.sntp-servers 2001:0db8:1234:0001::1;
> }

Now the problem seems to be that my DHCPv6 server isn't getting
when I connect to it.

> info dhcpd: Internet Systems Consortium DHCP Server 4.3.2
> info dhcpd: Copyright 2004-2015 Internet Systems Consortium.
> info dhcpd: All rights reserved.
> info dhcpd: For info, please visit https://www.isc.org/software/dhcp/
> info dhcpd: Config file: /etc/dhcp/dhcpdv6.conf
> info dhcpd: Database file: /var/db/dhcpd6.leases
> info dhcpd: PID file: /var/run/dhcpd6.pid
>
> info dhcpd: Internet Systems Consortium DHCP Server 4.3.2
> info dhcpd: Copyright 2004-2015 Internet Systems Consortium.
> info dhcpd: All rights reserved.
> info dhcpd: For info, please visit https://www.isc.org/software/dhcp/
>
> info dhcpd: Internet Systems Consortium DHCP Server 4.3.2
> info dhcpd: Copyright 2004-2015 Internet Systems Consortium.
> info dhcpd: All rights reserved.
> info dhcpd: For info, please visit https://www.isc.org/software/dhcp/
> info dhcpd: Wrote 0 deleted host decls to leases file.
> info dhcpd: Wrote 0 new dynamic host decls to leases file.
> info dhcpd: Wrote 0 NA, 0 TA, 0 PD leases to lease file.
> info dhcpd: Bound to *:547
> info dhcpd: Server starting service.
>
> debug radvd[1895]: eth0 recvmsg len=16
> debug radvd[1895]: eth0 received a packet
> debug radvd[1895]: eth0 received RS from: fe80::0db8:ffff:ffff:fff5
> debug radvd[1895]: sending RA to ff02::1 on eth0
> debug radvd[1895]: eth0 next scheduled RA in 559.393 second(s)
> debug radvd[1895]: eth0 processed an RS
> debug radvd[1895]: polling for 559.392 second(s), next iface is eth0
> debug radvd[1895]: eth0 recvmsg len=64
> debug radvd[1895]: eth0 received a packet
> debug radvd[1895]: eth0 received RA from: fe80::0db8:ffff:ffff:fff6
> debug radvd[1895]: processed RA on eth0
> debug radvd[1895]: polling for 559.391 second(s), next iface is eth0

> user@my_workstation:~ $ sudo dhcpcd -6
> DUID < DUID REMOVED >
> eth0: IAID < IAID REMOVED >
> eth0: soliciting an IPv6 router
> eth0: Router Advertisement from fe80::ba27:ebff:fe63:46b5
> eth0: adding address 2001:0db8:1234:0001:ffff:ffff:ffff:4444/64
> eth0: adding address 2001:0db8:1234:0001:ffff:ffff:ffff:8888/64
> eth0: adding route to 2001:0db8:1234:0001::/64
> eth0: adding default route via fe80::0db8:ffff:ffff:fff6
> eth0: soliciting a DHCPv6 lease
> timed out
> forked to background, child pid 4873

Patrick Trapp

RE: DHCPDv6 and fixed hosts, not appearing in logs

I have yet to scratch the surface on IPv6 yet, but after reading through your post, I have a question: Have you confirmed that the dhcp request is reaching your server? I have seen reports of network devices that support IPv6, but not until it's turned on. Thought it would be worthwhile to ask if the traffic has been confirmed to be flowing before you try to change the traffic.

Patrick

________________________________________
From: [hidden email] [[hidden email]] on behalf of sillysausage [[hidden email]]
Sent: Sunday, November 15, 2015 12:55 PM
To: [hidden email]
Subject: DHCPDv6 and fixed hosts, not appearing in logs

Hi,

I'm having trouble with my clients authenticating with my DHCPDv6
server.

For some reason I see no activity on my DHCPv6 logs, I think I might
have not configured it correctly. DHCPv4 works correctly though!

When a user connects on DHCPv4 I see the lease go out in syslog. With
my DHCPv6 instance I see nothing :(

I any case I configured the rc script configurations in /etc/conf.d
correctly as indicated by this:

gateway:~# ps aux |grep dhcpd

1686 dhcp 0:00 /usr/sbin/dhcpd -4 -cf /etc/dhcp/dhcpd.conf
-q -pf /var/run/dhcp/dhcpd.pid
-lf /var/lib/dhcp/dhcpd.leases
-user dhcp -group dhcp eth0

1714 dhcp 0:00 /usr/sbin/dhcpd -6 -cf /etc/dhcp/dhcpdv6.conf
-q -pf /var/run/dhcp/dhcpdv6.pid
-lf /var/lib/dhcp/dhcpdv6.leases
-user dhcp -group dhcp eth0

I'm using Roy Marples's dhcpcd to do prefix delegation, as the ISC
dhcp server doesn't seem to have the PPP patch yet in the main code
base and my distribution (Alpine Linux), hasn't applied it.

More info about that: https://bugs.gentoo.org/show_bug.cgi?id=432652

Finally my DHCPv6 configuration:

Now the problem seems to be that my DHCPv6 server isn't getting
when I connect to it.

I know the port is open, because I was able to test it with netcat ie
running nc -6 -u -l 547 on my router and nc -u -v -6
2001:0db8:1234:0001::1 547 on my workstation.

_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

Venkatesh Siddappa

RE: DHCPDv6 and fixed hosts, not appearing in logs

R u nunnig dhcpcd also.

from the below logs it is seen that
ISC DHCP server running in v4 and v6 mode.

gateway:~# ps aux |grep dhcpd

1686 dhcp 0:00 /usr/sbin/dhcpd -4 -cf /etc/dhcp/dhcpd.conf
-q -pf /var/run/dhcp/dhcpd.pid
-lf /var/lib/dhcp/dhcpd.leases
-user dhcp -group dhcp eth0

1714 dhcp 0:00 /usr/sbin/dhcpd -6 -cf /etc/dhcp/dhcpdv6.conf
-q -pf /var/run/dhcp/dhcpdv6.pid
-lf /var/lib/dhcp/dhcpdv6.leases
-user dhcp -group dhcp eth0

Thanks,
Venkatesh.

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Patrick Trapp
Sent: Monday, November 16, 2015 8:10 PM
To: Users of ISC DHCP
Subject: RE: DHCPDv6 and fixed hosts, not appearing in logs

I have yet to scratch the surface on IPv6 yet, but after reading through your post, I have a question: Have you confirmed that the dhcp request is reaching your server? I have seen reports of network devices that support IPv6, but not until it's turned on. Thought it would be worthwhile to ask if the traffic has been confirmed to be flowing before you try to change the traffic.

Patrick

________________________________________
From: [hidden email] [[hidden email]] on behalf of sillysausage [[hidden email]]
Sent: Sunday, November 15, 2015 12:55 PM
To: [hidden email]
Subject: DHCPDv6 and fixed hosts, not appearing in logs

Hi,

I'm having trouble with my clients authenticating with my DHCPDv6 server.

For some reason I see no activity on my DHCPv6 logs, I think I might have not configured it correctly. DHCPv4 works correctly though!

When a user connects on DHCPv4 I see the lease go out in syslog. With my DHCPv6 instance I see nothing :(

I any case I configured the rc script configurations in /etc/conf.d correctly as indicated by this:

gateway:~# ps aux |grep dhcpd

1686 dhcp 0:00 /usr/sbin/dhcpd -4 -cf /etc/dhcp/dhcpd.conf
-q -pf /var/run/dhcp/dhcpd.pid
-lf /var/lib/dhcp/dhcpd.leases
-user dhcp -group dhcp eth0

1714 dhcp 0:00 /usr/sbin/dhcpd -6 -cf /etc/dhcp/dhcpdv6.conf
-q -pf /var/run/dhcp/dhcpdv6.pid
-lf /var/lib/dhcp/dhcpdv6.leases
-user dhcp -group dhcp eth0

I'm using Roy Marples's dhcpcd to do prefix delegation, as the ISC dhcp server doesn't seem to have the PPP patch yet in the main code base and my distribution (Alpine Linux), hasn't applied it.

More info about that: https://bugs.gentoo.org/show_bug.cgi?id=432652

> gateway:~# cat /etc/dhcpcd.conf
> # Enable extra debugging
> # debug
>
> # Allow users of this group to interact with dhcpcd via the control #
> socket.
> #controlgroup wheel
>
> # Inform the DHCP server of our hostname for DDNS.
> hostname gateway
>
> # Use the hardware address of the interface for the Client ID.
> #clientid
> # or
> # Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as #
> per RFC4361. Some non-RFC compliant DHCP servers do not reply with #
> this set. In this case, comment out duid and enable clientid above.
> duid
>
> # Persist interface configuration when dhcpcd exits.
> persistent
>
> # Rapid commit support.
> # Safe to enable by default because it requires the equivalent option
> # set on the server to actually work.
> option rapid_commit
>
> # A list of options to request from the DHCP server.
> option domain_name_servers, domain_name, domain_search, host_name
> option classless_static_routes
>
> # Most distributions have NTP support.
> option ntp_servers
> # Respect the network MTU.
> # Some interface drivers reset when changing the MTU so disabled by #
> default.
> #option interface_mtu
>
> # A ServerID is required by RFC2131.
> require dhcp_server_identifier
>
> # Generate Stable Private IPv6 Addresses instead of hardware based #
> ones # slaac private
>
> # A hook script is provided to lookup the hostname if not set by the #
> DHCP server, but it should not be run by default.
> nohook lookup-hostname
>
> # IPv6 Only
> ipv6only
>
> # Disable solicitations on all interfaces noipv6rs
>
> # Wait for IP before forking to background waitip 6
>
> # Don't install any default routes.
> # PPP has already set a default route
> nogateway
>
> # Don't touch DNS
> nohook resolv.conf
>
> # Use the interface connected to WAN
> interface ppp0
> ipv6rs # enable routing solicitation get the default IPv6 route
> iaid 1
> ia_pd 1/::/64 eth0/1/64

This seems to be working great. I can statically set my IP address to the desired fixed address 2001:0db8:1234:0001::20

The intention is to have DHCPv6 issue me this IP address.

Here is my RADVD. I think it's working correctly.

I seem to get routes to the internet working with this.

I do understand with IPv6 I need radvd to push routes as DHCPv6 cannot do this.

I'm trying to make it not send me an IP address though. I want DHCPv6 to do this. I'm trying to emulate my IPv4 configuration as much as possible eg:

Finally my DHCPv6 configuration:

Now the problem seems to be that my DHCPv6 server isn't getting when I connect to it.

> info dhcpd: Internet Systems Consortium DHCP Server 4.3.2 info dhcpd:
> Copyright 2004-2015 Internet Systems Consortium.
> info dhcpd: All rights reserved.
> info dhcpd: For info, please visit https://www.isc.org/software/dhcp/
> info dhcpd: Config file: /etc/dhcp/dhcpdv6.conf info dhcpd: Database
> file: /var/db/dhcpd6.leases info dhcpd: PID file: /var/run/dhcpd6.pid
>
> info dhcpd: Internet Systems Consortium DHCP Server 4.3.2 info dhcpd:
> Copyright 2004-2015 Internet Systems Consortium.
> info dhcpd: All rights reserved.
> info dhcpd: For info, please visit https://www.isc.org/software/dhcp/
>
> info dhcpd: Internet Systems Consortium DHCP Server 4.3.2 info dhcpd:
> Copyright 2004-2015 Internet Systems Consortium.
> info dhcpd: All rights reserved.
> info dhcpd: For info, please visit https://www.isc.org/software/dhcp/
> info dhcpd: Wrote 0 deleted host decls to leases file.
> info dhcpd: Wrote 0 new dynamic host decls to leases file.
> info dhcpd: Wrote 0 NA, 0 TA, 0 PD leases to lease file.
> info dhcpd: Bound to *:547
> info dhcpd: Server starting service.
>
> debug radvd[1895]: eth0 recvmsg len=16 debug radvd[1895]: eth0
> received a packet debug radvd[1895]: eth0 received RS from:
> fe80::0db8:ffff:ffff:fff5 debug radvd[1895]: sending RA to ff02::1 on
> eth0 debug radvd[1895]: eth0 next scheduled RA in 559.393 second(s)
> debug radvd[1895]: eth0 processed an RS debug radvd[1895]: polling for
> 559.392 second(s), next iface is eth0 debug radvd[1895]: eth0 recvmsg
> len=64 debug radvd[1895]: eth0 received a packet debug radvd[1895]:
> eth0 received RA from: fe80::0db8:ffff:ffff:fff6 debug radvd[1895]:
> processed RA on eth0 debug radvd[1895]: polling for 559.391 second(s),
> next iface is eth0

> user@my_workstation:~ $ sudo dhcpcd -6 DUID < DUID REMOVED >
> eth0: IAID < IAID REMOVED >
> eth0: soliciting an IPv6 router
> eth0: Router Advertisement from fe80::ba27:ebff:fe63:46b5
> eth0: adding address 2001:0db8:1234:0001:ffff:ffff:ffff:4444/64
> eth0: adding address 2001:0db8:1234:0001:ffff:ffff:ffff:8888/64
> eth0: adding route to 2001:0db8:1234:0001::/64
> eth0: adding default route via fe80::0db8:ffff:ffff:fff6
> eth0: soliciting a DHCPv6 lease
> timed out
> forked to background, child pid 4873

I know the port is open, because I was able to test it with netcat ie running nc -6 -u -l 547 on my router and nc -u -v -6
2001:0db8:1234:0001::1 547 on my workstation.

_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

sillysausage

Re: DHCPDv6 and fixed hosts, not appearing in logs

On Mon, 16 Nov 2015 14:40:16 +0000
Patrick Trapp <[hidden email]> wrote:

> I have yet to scratch the surface on IPv6 yet, but after reading
> through your post, I have a question: Have you confirmed that the
> dhcp request is reaching your server? I have seen reports of network
> devices that support IPv6, but not until it's turned on. Thought it
> would be worthwhile to ask if the traffic has been confirmed to be
> flowing before you try to change the traffic.
>
> Patrick
>

Yes, it most certainly works if I use SLAAC generated addresses or
statically set my interface on my workstation. I have full connectivity
when I do that.

I let my workstation get an IP through SLAAC, and then attempted to
run:

user@my_workstation:~ $ sudo dhcpcd -6
[sudo] password for user:
DUID < DUID REMOVED >
eth0: IAID ff:ff:ff:ff
eth0: soliciting an IPv6 router
eth0: Router Advertisement from fe80::0db8:ffff:ffff:fff6
eth0: adding address 2001:0db8:1234:0001:ffff:ffff:ffff:2222/64
eth0: adding route to 2001:0db8:1234:0001::/64
eth0: adding default route via fe80::0db8:ffff:ffff:fff6
eth0: soliciting a DHCPv6 lease
timed out
forked to background, child pid 3086

gateway:~# tcpdump -i eth0 ip6 and udp

tcpdump: verbose output suppressed, use -v or -vv for full protocol
decode listening on eth0, link-type EN10MB (Ethernet), capture size
262144 bytes

IP6 fe80::ffff:ffff:ffff.546 > ff02::1:2.547: dhcp6 solicit
IP6 fe80::ffff:ffff:ffff.546 > ff02::1:2.547: dhcp6 solicit
IP6 fe80::ffff:ffff:ffff.546 > ff02::1:2.547: dhcp6 solicit
IP6 fe80::ffff:ffff:ffff.546 > ff02::1:2.547: dhcp6 solicit
IP6 fe80::ffff:ffff:ffff.546 > ff02::1:2.547: dhcp6 solicit
IP6 fe80::ffff:ffff:ffff.546 > ff02::1:2.547: dhcp6 solicit

the problem seems to be nothing going out from the DHCPDv6 server. The
DHCPDv6 server just isn't responding to the solicits from my
workstation. There is no firewall on my workstation, or otherwise
in between.

On Mon, 16 Nov 2015 15:37:06 +0000
Venkatesh Siddappa <[hidden email]> wrote:

> R u nunnig dhcpcd also.
>
> from the below logs it is seen that
> ISC DHCP server running in v4 and v6 mode.
>
> gateway:~# ps aux |grep dhcpd
>
> 1686 dhcp 0:00 /usr/sbin/dhcpd -4 -cf /etc/dhcp/dhcpd.conf
> -q -pf /var/run/dhcp/dhcpd.pid
> -lf /var/lib/dhcp/dhcpd.leases
> -user dhcp -group dhcp eth0
>
> 1714 dhcp 0:00 /usr/sbin/dhcpd -6 -cf /etc/dhcp/dhcpdv6.conf
> -q -pf /var/run/dhcp/dhcpdv6.pid
> -lf /var/lib/dhcp/dhcpdv6.leases
> -user dhcp -group dhcp eth0
>

This is just from ps aux. I am running two instances of dhcpd because
one gives out IPv4 addresses, and the other gives out... or is supposed
to give out IPv6 addresses.

dhcpcd is also running on the router, as this is what gets the prefix
from my ISP.

I edited my /etc/radvd.conf and disabled AdvAutonomous, because I don't
want SLAAC generated IPs.

As to be expected then I get no IPv6 addresses, because DHCPDv6 isn't
sending anything back to my clients :(.
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

A.L.M.Buxey

Re: DHCPDv6 and fixed hosts, not appearing in logs

Have you done tcpdump on the server to see if it's receiving these dhcpv6 requests? Is the server running a firewall? Are appropriate holes open?
If on different subnets do you have the required ipv6 helper on and pointing to your server?

alan
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

sillysausage

Re: DHCPDv6 and fixed hosts, not appearing in logs

On Mon, 16 Nov 2015 18:53:45 +0000
Alan Buxey <[hidden email]> wrote:

> Have you done tcpdump on the server to see if it's receiving these
> dhcpv6 requests? Is the server running a firewall? Are appropriate
> holes open? If on different subnets do you have the required ipv6
> helper on and pointing to your server?
>
> alan

Yes, the DHCP server is running on the router. I didn't make that all
that clear.

It's certainly getting the DHCPv6 SOLICIT requests:

On Tue, 17 Nov 2015 04:17:38 +1030
sillysausage <[hidden email]> wrote:

> user@my_workstation:~ $ sudo dhcpcd -6
> [sudo] password for user:
> DUID < DUID REMOVED >
> eth0: IAID ff:ff:ff:ff
> eth0: soliciting an IPv6 router
> eth0: Router Advertisement from fe80::0db8:ffff:ffff:fff6
> eth0: adding address 2001:0db8:1234:0001:ffff:ffff:ffff:2222/64
> eth0: adding route to 2001:0db8:1234:0001::/64
> eth0: adding default route via fe80::0db8:ffff:ffff:fff6
> eth0: soliciting a DHCPv6 lease
> timed out
> forked to background, child pid 3086
>
>
> gateway:~# tcpdump -i eth0 ip6 and udp
>
> tcpdump: verbose output suppressed, use -v or -vv for full protocol
> decode listening on eth0, link-type EN10MB (Ethernet), capture size
> 262144 bytes
>
> IP6 fe80::ffff:ffff:ffff.546 > ff02::1:2.547: dhcp6 solicit
> IP6 fe80::ffff:ffff:ffff.546 > ff02::1:2.547: dhcp6 solicit
> IP6 fe80::ffff:ffff:ffff.546 > ff02::1:2.547: dhcp6 solicit
> IP6 fe80::ffff:ffff:ffff.546 > ff02::1:2.547: dhcp6 solicit
> IP6 fe80::ffff:ffff:ffff.546 > ff02::1:2.547: dhcp6 solicit
> IP6 fe80::ffff:ffff:ffff.546 > ff02::1:2.547: dhcp6 solicit
>
> the problem seems to be nothing going out from the DHCPDv6 server. The
> DHCPDv6 server just isn't responding to the solicits from my
> workstation. There is no firewall on my workstation, or otherwise
> in between.

If the firewall was blocking it then I shouldn't see these dhcp6
solicits should I?

The gateway is the router, which also is running the DHCP server.

It's basically a generic Linux machine (Alpine Linux). I have fully
documented the project here:

http://wiki.alpinelinux.org/wiki/Linux_Router_with_VPN_on_a_Raspberry_Pi

The build has followed these steps of implementation:
http://wiki.alpinelinux.org/wiki/Linux_Router_with_VPN_on_a_Raspberry_Pi#Rationale
http://wiki.alpinelinux.org/wiki/Linux_Router_with_VPN_on_a_Raspberry_Pi#VPN_Tunnel_on_specific_subnet
http://wiki.alpinelinux.org/wiki/Linux_Router_with_VPN_on_a_Raspberry_Pi#Creating_a_LAN_only_Subnet
http://wiki.alpinelinux.org/wiki/Linux_Router_with_VPN_on_a_Raspberry_Pi#IPv6_2

Eventually the plan is to end up with a network that looks like the one
attached. :)

I'll be substituting that yellow managed switch with a managed one. I'm
thinking that new Ubiquiti ES-16-150W might be a nice choice there.

Might even throw in an few UniFi 720p PoE cameras to improve home
security.

_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

network_diagram_ipv6_tunnel_second_switch.svg (859K) Download Attachment

sillysausage

Re: DHCPDv6 and fixed hosts, not appearing in logs

I fixed the problem!

It seems DHCPv6 was only sending RA packets not any DHCPv6 type.

The trick was to upgrade to dhcpcd 6.9.3 or use ipv6ra_accept_nopublic
in dhcpcd.conf.

I used this configuration /etc/dhcpcd.conf

authoritative;
ddns-update-style interim;

shared-network home {
subnet6 2001:0db8:1234:0001::/64 {
range6 2001:0db8:1234:0001::10 2001:0db8:1234:0001::240;
range6 2001:0db8:1234:0001:: temporary;
option dhcp6.name-servers 2001:0db8:1234:0001::1;
option dhcp6.sntp-servers 2001:0db8:1234:0001::1;
allow unknown-clients;
}

subnet6 fde4:8dba:82e1:ffff::/64 {
range6 fde4:8dba:82e1:ffff::10 fde4:8dba:82e1:ffff::240;
range6 fde4:8dba:82e1:ffff:: temporary;
option dhcp6.name-servers 2001:0db8:1234:0001::1;
option dhcp6.sntp-servers 2001:0db8:1234:0001::1;
ignore unknown-clients;
}
}

host Gaming_Computer {
hardware ethernet 00:53:00:FF:FF:11;;
host-identifier option dhcp6.client-id <YOUR_DUID>;
fixed-address6 2001:0db8:1234:0001::20;
fixed-prefix6 2001:0db8:1234:0001::/64;
option dhcp6.name-servers 2001:0db8:1234:0001::1;
option dhcp6.sntp-servers 2001:0db8:1234:0001::1;
}

host Linux Workstation {
hardware ethernet 00:53:00:FF:FF:22;;
host-identifier option dhcp6.client-id <YOUR_DUID>;
fixed-address6 fde4:8dba:82e1:ffff::21;
fixed-prefix6 2001:0db8:1234:0001::/64;
option dhcp6.name-servers 2001:0db8:1234:0001::1;
option dhcp6.sntp-servers 2001:0db8:1234:0001::1;
}

/etc/radvd.conf

interface eth0 {

# We are sending advertisements (route)
AdvSendAdvert on;

# When set, host use the administered (stateful) protocol
# for address autoconfiguration. The use of this flag is
# described in RFC 4862
AdvManagedFlag on;

# When set, host use the administered (stateful) protocol
# for address autoconfiguration. For other (non-address)
# information.
# The use of this flag is described in RFC 4862
AdvOtherConfigFlag on;

# Suggested Maximum Transmission setting for using the
# Hurricane Electric Tunnel Broker.
# AdvLinkMTU 1480;

# We have native Dual Stack IPv6 so we can use the regular MTU
AdvLinkMTU 1500;

prefix 2001:0db8:1234:0001::/64 {
AdvOnLink on;
AdvAutonomous off;
AdvRouterAddr on;
};

# RDNSS 2001:0db8:1234:0001::1 {
# };
# DNSSL example.id {
# };
};
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

sthaug

Re: DHCPDv6 and fixed hosts, not appearing in logs

> I fixed the problem!
>
> It seems DHCPv6 was only sending RA packets not any DHCPv6 type.

I strongly doubt that ISC dhcp is sending RA packets. RA is supposed
to be sent by routers.

> The trick was to upgrade to dhcpcd 6.9.3 or use ipv6ra_accept_nopublic
> in dhcpcd.conf.

dhcpcd != ISC dhcp

I'm glad to see you've solved your problem. However, It doesn't seem
to be related to ISC dhcp.

Steinar Haug, Nethelp consulting, [hidden email]
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

sillysausage

Re: DHCPDv6 and fixed hosts, not appearing in logs

On Wed, 18 Nov 2015 06:42:17 +0100 (CET)
[hidden email] wrote:

> > I fixed the problem!
> >
> > It seems DHCPv6 was only sending RA packets not any DHCPv6 type.
>
> I strongly doubt that ISC dhcp is sending RA packets. RA is supposed
> to be sent by routers.
>

That was miss-wording on my part. radvd was sending the RA. There
wasn't any DHCPv6 traffic. Though I did notice some with udhcpc and
dhclient.

> > The trick was to upgrade to dhcpcd 6.9.3 or use
> > ipv6ra_accept_nopublic in dhcpcd.conf.
>
> dhcpcd != ISC dhcp
>

Yeah I'm aware of that. I just find that dhcpcd is better for debugging
what is going on, assuming it is working :)

> I'm glad to see you've solved your problem. However, It doesn't seem
> to be related to ISC dhcp.
>

Indeed.
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users