Bug #9914


dhcp6c wont work on reboot, only after service restart

Added by Seyfidin Hamraoui over 4 years ago. Updated over 4 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:


The dhcp6c service is not working after a reboot, I have to restart the service to get it working. The log file has the following entry:

/var/etc/dhcp6c_wan.conf:14 invalid interface (lagg0.10): Device not configured

The interface and config file are correct, after a restart of the service, everything works as expected.

Maybe the interface was not created at the time dhcp6c is supposed to start.

Actions #1

Updated by Jim Pingle over 4 years ago

  • Status changed from New to Rejected

This doesn't appear to be a general issue with dhcp6c, but it may be specific to something in your settings or environment. There is a very similar issue at #3965 but it references a bridge, not LAGG. However, I can't reproduce this issue with just a LAGG, so there must be something more to it in your setup.

Until you can narrow down exactly which combination of settings is causing this to happen, there isn't much we can do, so for the moment I'm rejecting it since it can't be reproduced. I suggest starting a thread on the Netgate Forum to discuss the problem and investigate the cause in your environment. You'll need to provide a lot more detail about the specifics of your interface configuration, and more log entries.

Once it can be reproduced, then this can be reopened, assuming it doesn't turn out to be a duplicate of #3965 in which case we already have an issue open for it.

Actions #2

Updated by Seyfidin Hamraoui over 4 years ago

Did you use VLAN on your lagg? I can reproduce the issue when using VLAN on a lagg in a fresh installed pfsense VM.

Actions #3

Updated by Jim Pingle over 4 years ago

Yes. The default installation configuration of some devices such as our XG-7100 includes VLAN on LAGG, and dhcp6c is working on those. If it was broken in general then it wouldn't be working for any of those devices, and it is. There is something else in your setup contributing to the problem. Bring it up on the forum.


Also available in: Atom PDF