Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I ask because the server is handling DHCPv6 for two VLANs and I can see some requests both via DHCPv6-relay from our ProCurve switch and via the ff02::0:2 anycast address and responds to both requests.

The logs look like this:

Sep 23 00:40:05 fry dhcpd: Request message from fe80::2c0:b7ff:fe53:32e7 port 546, transaction ID 0x7C08E400
Sep 23 00:40:05 fry dhcpd: Sending Reply to fe80::2c0:b7ff:fe53:32e7 port 546
Sep 23 00:40:05 fry dhcpd: Relay-forward message from 2001:1900:221c:800::1 port 547, link address 2001:1900:221c:800::1, peer address fe80::2c0:b7ff:fe53:32e7
Sep 23 00:40:05 fry dhcpd: Sending Relay-reply to 2001:1900:221c:800::1 port 547

I suppose it might be possible to enable DHCPv6 relay only for one of the VLANs and use anycast for the other, but it seems cleaner to me to have them both serviced in the same way.

This is on Ubuntu 11.04 with a 4.2.2 dhcpd I compiled myself (without changing anything). The same behavior happens with the regular 4.1 Ubuntu package, however.

share|improve this question
up vote 0 down vote accepted

I decided that not using DHCPv6 relay for the VLAN that the DHCP server was in was the sane choice.

Now clients in that VLAN get leases via their link-local addresses and a request to ff02::1:2 and clients outside that VLAN get leases via DHCPv6 relay on the switch.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.