DHCPv6 Server not starting following most recent firmware update

[RobLatour]

There is an entry for the lan, and for wan here is what I see:
https://ibb.co/tXX0SbZ

I notice there is yet another update available for opnsense ; should I apply it?

[opnfwb]

Hmm, it seems odd that there is a /128 and a /64 assigned to WAN.

Can you post a screenshot of the Interfaces/WAN configuration page? Specifically the Generic Configuration section and the DHCPv6 Client Config section on that page.

[RobLatour]

here is the whole thing:
https://ibb.co/QNmgQy3

[RobLatour]

also I just applied the latest update and rebooted.  It was of no help, the same problem remains.

[opnfwb]

Within the UI, if you screenshot the output of Interfaces/Overview/LAN, does the LAN interface also show an ipv6 address?

[RobLatour]

Yes, it does.

https://ibb.co/Fs9xW5B

also, for ipv6 on this window I just tried a 'release' followed by a 'renew', but that did not help either.

Addtionally, I applied another set of updates from opnsense this morning, again with no change.

Is there a log someplace that would describe why the lobby's dashboard would be reporting red for the DHCPv6 Server even after I try to start it?

[opnfwb]

That last screenshot actually doesn't show a prefix being delegated to the LAN interface. That interface is only showing a link-local address space.

At this point I would enable ipv6 debug logging and see if that gives any clues. However, I think the main source is the use of the Rogers supplied router.

To enable ipv6 debug logging: Interfaces/Settings/IPv6DHCP and change the log level drop down menu to 'debug'

You could also try some of the settings listed here, use the pfSense recommended settings. It appears that quite a few Rogers customers had issues with IPv6 stability. https://communityforums.rogers.com/t5/Internet/Rogers-IPv6-Status/m-p/373238/highlight/true#M36710

[franco]

Quoting https://communityforums.rogers.com/t5/Internet/Rogers-IPv6-Status/m-p/373238/highlight/true#M36710

> DHCPv6 Prefix Delegation Size: 64

WTF?

Apparently they messed with the prefix delegation and the coincidental reboot caused the prefix to disappear. There's nothing in the update(s) that would cause this.


Cheers,
Franco

[RobLatour]

I enabled the debug logging, tried another restart, and even boot, and looked for the results in system - logfiles - general (which I assume is the correct place) but didn't see any errors or warnings.

While I am not fully discounting the fact the issue could be with the Rogers, the DHCPv6 Server had been working fine up until I applied the most recent upgrade four or five days ago.

Is there a way to roll back to the prior version?

[RobLatour]

(Franko) if by 'they' you mean me, I didn't mess with anything - the service just stopped working when I applied the update.

Is there something I can manually do to fix this up - its all well over my level of expertise :-)

[franco]

No, sorry, I meant the ISP as per that link. Take a look at the pfSense settings at the bottom and try them out on your install:

Use IPv4 connectivity as parent interface: yes
Request only a IPv6 prefix: no
DHCPv6 Prefix Delegation Size: 64
Send IPv6 prefix hint: yes


It supposedly sounds like they use PPPoE on IPv4? These settings are weird... I know that "Request only a IPv6 prefix: no" can cause a lot of issues with tight delegation where you end up with the same network on WAN and LAN and that can't possibly route correctly.


Cheers,
Franco

[RobLatour]

Thanks.

On the Interfaces - [WAN_Rogers] window

I checked 'Use IPv4 connectivity" (it was previously unchecked)
I left "Request only a IPv6 prefix" unchecked
I left "DHCPv6 Prefix Delegation Size" set at 64
I checked 'Send IPv6 prefix hint" (it was previously unchecked)

saved and applied the changes.

However, sadly, the DHCPv6 Server will still not start.

[opnfwb]

At this point you'll need to check the logs and see if there are more details.

To enable ipv6 debug logging: Interfaces/Settings/IPv6DHCP and change the log level drop down menu to 'debug'

[RobLatour]

Here is what is in the log after I click the start service button on the lobby/dashboard screen:

https://ibb.co/8rw1dx0

[RobLatour]

It's working!

There is a setting on my Rogers router that says "Residential Gateway Function" which I changed from Enabled to Disabled.

After that, and a reboot of the router, the opnsense DHCPv6 Server was able to start.

Unfortunately, now I can't seem to sign on to my Rogers Router any more - so I will have to figure that one out.

I will also now try and revert back the new settings I had made to the opnsense box, and will post back here to confirm if they were needed or not - not that the "Residential Gateway Function" is disabled.

Thank you so much for your time and help opnfwb and franco!