DHCPDv6 and fixed hosts, not appearing in logs

[sillysausage]

On Mon, 16 Nov 2015 18:53:45 +0000
Alan Buxey <A.L.M.Buxey at lboro.ac.uk> 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 <sillysausage at privatedemail.net> wrote:

> user at 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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: network_diagram_ipv6_tunnel_second_switch.svg
Type: image/svg+xml
Size: 642494 bytes
Desc: not available
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20151117/ff918075/attachment-0001.bin>