Dhcp6c client no release option and user configurable DUID.
-
I have compiled a new WIDE-DHCP6 suite which, with an option selected in WAN configuration prevents the dhcp6c client from sending a release signal to the ISPs dhpc6 server. In some cases it appears that when the server receives the release signal it does exactly that and releases the allocation and on the next request a new allocation is given, even if the DUID is the same. Seeing this is the default behavior of dhcp6c as it closes down there is no way to prevent it without modification to not send the release signal. I have now done this by adding a new 'n' option as one of the parameters; this parameter is passed in the start-up command(s) in interfaces.inc. I have also taken the opportunity to add some extra 'useful logging' and removed ctrl error logging.
I and a few others have now tested this thoroughly and it is working flawlessly with our ISP. My problem is that I cannot get pfSense/FreeBSD-ports to accept a PR, would a member of the dev team be prepared to assist with this?
Apart from the changes to the client suite I have modified util.inc, interfaces.inc and interfacers.php files ready to go, but I can't issue a PR on these until the dhcp client has been pulled into the main line as the addition of the new flag would cause the existing dhcp6c to error and exit.
Finally, I have also included routines that allow the user to enter and store the DUID in the configuration, a dhcp6_duid is then created and stored in the /conf folder ( this is safe from deletion - I hope ) and on WAN UP - dhcp6 configure the file is copied to the /var/db folder, this also gets around the problem of users using RAM disks losing thier DUID on reboot; at the moment the work around is an early shell command to copy the duid file in the same way.
If a dev would like to PM me I would be more than happy to send the WIDE-DHCP6 files folder for compilation and testing.
-
I am also on sky uk, is it possible for me to test the DUID user configurable option?
I am on the 2.4 beta and the other stuff seems to be already implemented (both no release and dont wait for RA).
-
The PR was accepted and pulled yesterday, should be appearing in a snapshot near you shortly.
Look in System->Advanced->Networking for the DUID entry. It will display your existing DUID by default. It is not stored though. You need to enter and save it, then it is stored.
-
I updated to the latest snapshot today and it's there.
-
yep I seen the commit's when checking earlier today, thanks for your work on this marjohn56.
-
is there lag between commit and code on updates?
I updated this morning but no DUID box in WAN settings.
Apologies I just read marjohn's post and it is there, I was looking in wrong place.