Dhcp6c: prefix renewal fails - does pfsense create pd's with wrong pl/vl times?
-
Sorry, forgot to mention:
2.3.4-RELEASE-p1 (amd64)
built on Fri Jul 14 14:52:43 CDT 2017
FreeBSD 10.3-RELEASE-p19I also had the issue with all 2.3.x versions. I activated ia-pd 0 only a few moths back. Currently, I am testing pltime => 14400. Seems to hold atm.
<adv_dhcp6_interface_statement_send_options>ia-pd 0</adv_dhcp6_interface_statement_send_options> <adv_dhcp6_id_assoc_statement_prefix_enable>Selected</adv_dhcp6_id_assoc_statement_prefix_enable> <adv_dhcp6_id_assoc_statement_prefix_pltime>14400</adv_dhcp6_id_assoc_statement_prefix_pltime>
Live - status can be seen here: https://status.m-box.de/ - if the interface (GatewayB) is up and all the IPv6 stuff is down, the prefix is lost.
-
OK, there are a lot of changes around dhcp6c in version 2.4b, some of them are back ported but there have also been changes to dhcp6c itself which have not been backported.
If you can, you might wish to try 2.4b, it is very stable.
-
Ok, thanks for the info! I'll give it a try if my current setup fails again. I'll keep this thread updated!
-
As a note, most ISP's will ignore your lease time request. :)
-
As a note, most ISP's will ignore your lease time request.
Figured that much as I would do the same. My hope is dhcpv6c might get to know the lease time that way. So far, it works as the prefix is renewed correctly (knock on wood).
-
A noob question, how do I get 2.4b? When I switch over to devel snapshots, I would update to 2.3.5.a.20170726.1256
-
It's so long since I changed to 2.4b I cannot remember… Sad or what :D
Have a look under advanced config, I think there may be something there. I only remember doing what you have done when I was on 2.3, but that's over a year ago now.
-
Hi!
Export config, install 2.4 with ZFS and then simple restore config. It will restore everything.
Did it this way and it took me exactly 7.87 minutes :) -
And THAT is the best way to do it!
No junk left around either.
-
Export config, install 2.4 with ZFS and then simple restore config
Thanks, I read about ZFS and was also thinking doing it this way.
BTW, you can directly upgrade to 2.4b when selecting NEXT MAJOR in update settings.
-
I'll remember that, or try to. :)
-
Export config, install 2.4 with ZFS and then simple restore config
Thanks, I read about ZFS and was also thinking doing it this way.
BTW, you can directly upgrade to 2.4b when selecting NEXT MAJOR in update settings.
You can, but then you het NO ZFS :)
-
Don't use ZFS as I run pfSense on an APU2 with a 32Gb SSD. There would not much benefit as I also use a RAM disk and set low levels of logging.
-
There would not much benefit as I also use a RAM disk and set low levels of logging.
Truth is you could also benefit from ZFS:
- It is a copy on write FS witch greatly reduces the chance of failures due to power cuts etc.
- By using ZIL/log you basically get the benefits from aync IO with the reliability of synced I/O operations (though this does not need to make a big performance dent with SSD's nowadays, it is very true for HDD's in RAIDZ).
- Upgrading to new releases will benefit as can basically create a snapshot from your root volume and boot from that if something goes wrong greatly reducing upgrade downtime in case of issues (this is indeed the main reason for me to switch)
-
Indeed, but as was pointed out, it tales 10 or minutes or less to install pfSense from scratch and reload the config - which is backed up in a couple of locations just in case, Plus I have a spare APU which I do my testing and developing on, so if needed that swings into action.
I might use ZFS on my FreeBSD PC, but at present the stuff on it that needs to be backed up goes to a NAS Raid device.
Maybe one day….
-
For what it's worth, I opened a redmine ticket for it: https://redmine.pfsense.org/issues/7734
@marjohn56,
OK, there are a lot of changes around dhcp6c in version 2.4b
I think you where referring to your https://github.com/pfsense/pfsense/pull/3515; and this got merged in 2.4b?