ISP ipv6 request is accepted via dhcp6c but not applied to my interface???
-
@sloopbun said in ISP ipv6 request is accepted via dhcp6c but not applied to my interface???:
At 15:10:54 yo got a /56 prefix : I would say you got 64 block of /64 ! nice !
Jan 1 15:10:54 pfSense dhcp6c[6746]: IA_PD prefix: 2a01:cbxx:51:4d00::/56 pltime=604800 vltime=34360343168
Two seconds later seconds later :
... Jan 1 15:10:56 pfSense dhcp6c[6746]: IA_PD prefix: 2a01:cbxx:51:4d00::/56 pltime=604800 vltime=34360343168 ....
Less then a second later :
... Jan 1 15:10:56 pfSense dhcp6c[6746]: create a prefix 2a01:cbxx:51:4d00::/56 pltime=604800, vltime=604800
Right after this line, 8 seconds later, it looks like 'everything' starts all over again :
A lot of clean up is done ... and that includes this :Jan 1 15:11:09 pfSense dhcp6c[6746]: remove a site prefix 2a01:cbxx:51:4d00::/56
Dono what goes wrong.
Btw : I' still using my 'Livebox' (6) so no /56 for me (the box annouces it has a /56 for me), the DHCPv6 livebox server can just allocate one /64 for my LAN, that it - but that works.edit :
This :
looks strange. -
Thanks for your message. The "OPTION90" chain is the authentication credentials I removed for privacy. Option-90 is the DHCP4 spec and Option 11 is the DHCP6.
It is really odd. The above log is with Debug DHCP6 logging on. I guess there must be another relevant log message but I can't find anything.
I do find it strange that pfsense seems to be lacking in ipv6 compared to opnsense, but I have no idea about much of anything, evidently...
-
@keyser I saw in another thread that you had success using the dhcp6c from opnsense for Orange France DHCP6.
I have tested with a fresh pfsense and same result. As mentioned above, opnsense works perfectly for ipv6.
Do you have any idea why this is not working for me? Thanks!
-
@sloopbun I gave up IPv6 on pfSense all together quite a while ago. It’s just too buggy and temperamental to be used in any on of my sites (including Orange in France).
I did have a breifly working test in France using the OPNSense binary, but hacked installs like that is not really desireable, so I gave it up.
I have similar issues both in Denmark and gernamy where the ISP has no real special requirements - yet IPv6 cannot be brought to a working state (but can with OPNsense).My main gripe with DHCP6c on pfSense is that as soon as you start doing additional config it seems to restart/run the scripts several times on every action - regardless of what I do. Sometimes it will do the discover/renew process up to 4 times in a row whenever it should be only one run. None of my IPS’s plays nice with a misbehaving dhcp6c like that, so the delegation is recieved, but then dropped on the next run (a second or two later), and then it’s game over.
For now I can live without IPv6 so I’m fine, but when the time comes my plan is to switch to OPNsense - I have given up on hoping that pfSense will get a coherent working and configurable IPv6 DHCP6c client. It seems to be a bunch of scripts cobbled together that no-one really understands when you start using “non-default” settings. And given there is no forum support or developer interest in the problems, I have concluded the very few actually uses IPv6 on pfSense.
-
@keyser said in ISP ipv6 request is accepted via dhcp6c but not applied to my interface???:
I gave up IPv6 on pfSense all together quite a while ago.
It's been rock solid for me for almost 8 years and I've had the same prefix for about 5 years. It just works.
-
@JKnott I know there are people with that experience. But so far they all share the fact that “it just works” because they did not have to use any special settings/advanced settings. I assume your setup is also using completely default IPv6 settings?
Apart from this, I’m fully aware that this is also very much an ISP issue. They all go out of their way - deliberate obstruction - to make it difficult to use your own equipment/devices. Because of support they prefer that all customers use their CPE - or don’t use their services at all.
-
I'm using IPv6 for a decade now.
First : by using the free services of tunnel.he.net.
These days, I'm still using Orange (France) and a Livebox 6, and left the ADSL for a fibre router, and this works (somewhat) fine.
Both on pfSense and a pfsense LAN I can use IPv6.These are my WAN DHCP6C settings :
On the LAN I use "Tracking", and the I set up the DHCP6 server on LAN, and done.
The LAN prefix stayed the same since I'm using the livebox 6, since I have fibre, January 2023.
There is one issue : the box's DHCP6 server hand out just one /64 for one LAN.
-
@Gertjan Yeah I know it works behind the Orange Livebox (CPE) with default settings. But like we discussed before, I don’t want to use the Livebox and have doubleNAT on IPv4, two boxes that can fail/use electricity and so on.
My pfSense terminates the Orange Fiber directly in an ONT SFP, and gives me the pulic IPv4 address directly in pfSense.Orange is a particularly good example of my statement about “deliberate obstruction” from the ISP if you want to drop their CPE. They REALLY go out of their way to make it difficult to use your own equipment by using a VERY VERY special DHCP client setup (ipv4 and 6).
It can be made to work flawlessly in pfSense on IPv4, but not IPv6. To make it work with IPv6 I need to use OPNsense as their IPv6 client works normally with lots of advanced configuration. PfSense’s does not - it runs 2 - 4 times on every discover/renew, and it does not support RAW options - which makes Orange deny DHCP leases and shut down the connection. -
@keyser said in ISP ipv6 request is accepted via dhcp6c but not applied to my interface???:
But like we discussed before,
I remember, sorry for making you repeating what was already said (elsewhere).
-
@Gertjan said in ISP ipv6 request is accepted via dhcp6c but not applied to my interface???:
I'm using IPv6 for a decade now.
First : by using the free services of tunnel.he.net.You're a newcomer. I'm coming up on 14 years. Initially with a 6in4 tunnel for almost 6 years, but since then native IPv6 on Rogers.
-
@keyser said in ISP ipv6 request is accepted via dhcp6c but not applied to my interface???:
the delegation is recieved, but then dropped on the next run (a second or two later), and then it’s game over.
This is what seems to happen for me too. I guess I will just forget ipv6 for now. It is a relatively minor thing. Would love to tinker more if devs or anyone has suggestions in the future. Cheers!
-
@sloopbun Me to :-)