[SOLVED] Upgrade to 19.1.1 - no ipv6 gateway

[bringha]

Hi,

after upgrading to 19.1.1 from 18.7, the ipv6 gateway is shown as offline and cannot be started from GUI anymore. The issue is that there is no rtsold process anymore pickup the prefix from WAN and  also dhcp6d can not be started.

The logs do not show any hint except that they state that there is no ipv6 default route possible to be set;

Code: [Select]

Feb 17 13:53:54 OPNsense opnsense: /interfaces.php: The command '/bin/pkill -'HUP' 'php-cgi'' returned exit code '1', the output was ''
Feb 17 13:53:54 OPNsense opnsense: /interfaces.php: ROUTING: entering configure using defaults
Feb 17 13:53:54 OPNsense opnsense: /interfaces.php: ROUTING: IPv4 default gateway set to wan
Feb 17 13:53:54 OPNsense opnsense: /interfaces.php: ROUTING: IPv6 default gateway set to wan
Feb 17 13:53:54 OPNsense opnsense: /interfaces.php: ROUTING: setting IPv4 default route to 192.168.2.1
Feb 17 13:53:54 OPNsense opnsense: /interfaces.php: ROUTING: keeping current default gateway '192.168.2.1'
Feb 17 13:53:54 OPNsense opnsense: /interfaces.php: ROUTING: skipping IPv6 default route
Feb 17 13:54:51 OPNsense opnsense: /interfaces.php: ROUTING: entering configure using 'wan'
Feb 17 13:54:51 OPNsense opnsense: /interfaces.php: ROUTING: IPv4 default gateway set to wan
Feb 17 13:54:51 OPNsense opnsense: /interfaces.php: ROUTING: IPv6 default gateway set to wan
Feb 17 13:54:51 OPNsense opnsense: /interfaces.php: ROUTING: setting IPv4 default route to 192.168.2.1
Feb 17 13:54:51 OPNsense opnsense: /interfaces.php: ROUTING: removing /tmp/igb1_defaultgw
Feb 17 13:54:51 OPNsense opnsense: /interfaces.php: ROUTING: creating /tmp/igb1_defaultgw using '192.168.2.1'
Feb 17 13:54:51 OPNsense opnsense: /interfaces.php: ROUTING: skipping IPv6 default route
Feb 17 13:54:57 OPNsense opnsense: /interfaces.php: Warning! services_radvd_configure(auto) found no suitable IPv6 address on igb2
Feb 17 13:54:57 OPNsense opnsense: /interfaces.php: Warning! services_radvd_configure(auto) found no suitable IPv6 address on igb0
Feb 17 13:54:57 OPNsense opnsense: /interfaces.php: Warning! services_radvd_configure(auto) found no suitable IPv6 address on igb3

dpinger can not be started as well (clear if there is no ipv6 gateway ....)

Any idea where to look after?

Br br

[marjohn56]

What are your settings in dhcpv6 client in WAN Settings


Should be like this:





Make sure of the following:-


prefix delegation size matches that issued by the ISP.


Use IPv4 connectivity is off UNLESS your using PPPoE or similar in which case it should be on.


Directly send solicit is usually left on, but some ISPs don't like that so try it both ways.


Prevent release should be set to ON unless you want to risk your address changing.


It should work other than that.

[bringha]

Thanks Marjohn - the good thing is that my ipv6 gateway shows now online again

However, my interfaces now don't get any ipv6 address advertised still and the dhcpd6 cannot be started either still - is there any adaption I need to make for the other interfaces too?

Looking forward to your reply

[marjohn56]

Good.. OK. Next we need to look at the dhcp6c & dhcpd6 logs to find out what's happening. Firstly, check the following, we'll leave everything on automatic to start with. In Services:DHCpv6 is there are LAN sub option? If there is, select it and untick 'Enable DHCPv6 server on LAN Interface', if there is no LAN interface listed that's also fine, just go to the next step.


In Interfaces:LAN it should look like this:






Reboot after any changes.


If it does all look like that and you have rebooted and still have no v6 on the LAN, can you post \var\log\dhcpd.log on dropbox and post the link, i'll take a look.

[bringha]

OK ....

After reboot and having the interfaces description as mentioned, the DHCP log contains for dhcp6c

Code: [Select]

Feb 17 15:15:05 OPNsense dhcp6c[78038]: Sending Solicit
Feb 17 15:15:05 OPNsense dhcp6c[78038]: advertise contains NoAddrsAvail status
Feb 17 15:15:13 OPNsense dhcp6c[78038]: Sending Solicit
Feb 17 15:15:13 OPNsense dhcp6c[78038]: advertise contains NoAddrsAvail status
Feb 17 15:15:24 OPNsense dhcpd: DHCPREQUEST for 192.168.1.10 from 00:25:XX:XX:XX via igb0
Feb 17 15:15:24 OPNsense dhcpd: DHCPACK on 192.168.1.10 to 00:25:XX:XX:XX via igb0
Feb 17 15:15:29 OPNsense dhcp6c[78038]: Sending Solicit
Feb 17 15:15:29 OPNsense dhcp6c[78038]: advertise contains NoAddrsAvail status



[marjohn56]

The ISP says no addresses available. OK, in that case you'll need to do the following:-


1. Go to Interfaces:Setting and select 'Insert a new LLT DUID' in the DHCP Unique identifier setting. Save and reboot.


If you still have no v6 LAN addresses after that then you'll need to wait for the ISPs BNG Lease time to expire, usually around an hour ( 7200 seconds ).


Disconnect from the Internet, modem too and go and play football/Cricket/Tennis whatever or talk to the wife/girlfriend/pet/husband/alien for an hour then restart everything and you should have a v6 address back.

[bringha]

Hmmmmm ... Not sure whether this will reflect my configuration: I connect to my ISP via a Fritzbox. This Fritzbox I have configured with

DNS-Server und IPv6-Präfix (IA_PD) zuweisen

After the reboot of all Fritzbox and sense, I have a new error message:

Code: [Select]

Feb 17 15:50:08 OPNsense dhcpd: RTSOLD script - Starting dhcp6 client for interface wan(igb1)
Feb 17 15:50:08 OPNsense dhcpd: RTSOLD script - Sending SIGHUP to dhcp6c for interface wan(igb1)
Feb 17 15:50:08 OPNsense dhcp6c[28493]: restarting
Feb 17 15:50:09 OPNsense dhcp6c[28493]: Sending Solicit
Feb 17 15:50:09 OPNsense dhcp6c[28493]: unknown or unexpected DHCP6 option opt_86, len 16
Feb 17 15:50:10 OPNsense dhcp6c[28493]: Sending Request
Feb 17 15:50:10 OPNsense dhcp6c[28493]: unknown or unexpected DHCP6 option opt_86, len 16
Feb 17 15:50:10 OPNsense dhcp6c[28493]: Received REPLY for REQUEST
Feb 17 15:50:10 OPNsense dhcp6c[28493]: invalid prefix length 62 + 8 + 64
Feb 17 15:50:10 OPNsense dhcp6c[28493]: invalid prefix length 62 + 8 + 64
Feb 17 15:50:10 OPNsense dhcp6c[28493]: invalid prefix length 62 + 8 + 64
Feb 17 15:50:10 OPNsense dhcp6c: dhcp6c REQUEST on igb1 - running newipv6

Would this fit to your recommendation? I had never before to deal with DUID stuff et al with a Fritzbox before ...

Thanks again for your support ....

Br Br

[marjohn56]

You need to change the prefix delegation size in WAN dhcp6c settings. Try changing it to 60

[bringha]

Changed it and rebooted but no success, still:

Code: [Select]

Feb 17 16:44:37 OPNsense dhcp6c[88324]: restarting
Feb 17 16:44:37 OPNsense dhcp6c[88324]: Start address release
Feb 17 16:44:37 OPNsense dhcp6c[88324]: Sending Release
Feb 17 16:44:37 OPNsense dhcp6c[88324]: Received REPLY for RELEASE
Feb 17 16:44:37 OPNsense dhcp6c[88324]: status code: success
Feb 17 16:44:37 OPNsense dhcp6c: dhcp6c RELEASE on igb1 - running newipv6
Feb 17 16:44:37 OPNsense dhcp6c[88324]: Sending Solicit
Feb 17 16:44:37 OPNsense dhcp6c[88324]: unknown or unexpected DHCP6 option opt_86, len 16
Feb 17 16:44:38 OPNsense dhcp6c[88324]: Sending Request
Feb 17 16:44:38 OPNsense dhcp6c[88324]: unknown or unexpected DHCP6 option opt_86, len 16
Feb 17 16:44:38 OPNsense dhcp6c[88324]: Received REPLY for REQUEST
Feb 17 16:44:38 OPNsense dhcp6c[88324]: invalid prefix length 62 + 4 + 64
Feb 17 16:44:38 OPNsense dhcp6c[88324]: invalid prefix length 62 + 4 + 64
Feb 17 16:44:38 OPNsense dhcp6c[88324]: invalid prefix length 62 + 4 + 64
Feb 17 16:44:38 OPNsense dhcp6c: dhcp6c REQUEST on igb1 - running newipv6

 

[bringha]

OK - though ....

I am not sure whether this is intended or a somewhat collateral effect:

When I set on WAN interface the prefix delegation size to 62, all is fine:

Code: [Select]

Feb 17 18:19:24 OPNsense dhcpd: Copyright 2004-2018 Internet Systems Consortium.
Feb 17 18:19:24 OPNsense dhcpd: All rights reserved.
Feb 17 18:19:24 OPNsense dhcpd: For info, please visit https://www.isc.org/software/dhcp/
Feb 17 18:19:24 OPNsense dhcpd: Wrote 0 NA, 0 TA, 0 PD leases to lease file.
Feb 17 18:19:24 OPNsense dhcpd: Bound to *:547
Feb 17 18:19:24 OPNsense dhcpd: Listening on Socket/9/igb3/2003:e2:XXXX:XXXX::/64
Feb 17 18:19:24 OPNsense dhcpd: Sending on   Socket/9/igb3/2003:e2:XXXX:XXXX::/64
Feb 17 18:19:24 OPNsense dhcpd: Listening on Socket/9/igb0/2003:e2:XXXX:XXXX::/64
Feb 17 18:19:24 OPNsense dhcpd: Sending on   Socket/9/igb0/2003:e2:XXXX:XXXX::/64
Feb 17 18:19:24 OPNsense dhcpd: Listening on Socket/9/igb2/2003:e2:XXXX:XXXX::/64
Feb 17 18:19:24 OPNsense dhcpd: Sending on   Socket/9/igb2/2003:e2:XXXX:XXXX::/64
Feb 17 18:19:24 OPNsense dhcpd: Server starting service.

However, I would assume that this can not be wanted necessarily: Is this size of 62 either hardcoded or calculated out of the number of interfaces?

If not, where can I configure it?
If yes, is my assumption right that Opnsense would not possible to be used as cascaded router with SLACC anymore ...
At least for some of my use cases, this would be very sad ....

Looking forward to any comment

Br br

PS: Not sure whether I missed something but where could I have found the information, that and how the RADV logic has been changed so that the old configs of <= 18.7 can not be obtained 1:1 anymore?

[marjohn56]

You're only getting a /62 prefix from your Fritzbox.

[bringha]

I am pretty sure.  - I am getting a 56 prefix - and this worked in 18.7 ....

Will double check once again

Br br

[Edit]: Ok: here is what we found.

The fritz box gets an /56 prefix from my ISP
If the tickbox 'Send ipv6 prefix hint' is NOT ticked, the Fritzbox sends an /62 prefix to the Opnsense; this seems to be the default behavior. When the tickbox 'Send ipv6 prefix hint' is ticked, this value can be set  in 'the prefix delegation size' field to something different fitting between /56 and /64 accordingly. In my old config, I had this ticked in 18.7 ....

What remains is the changed behavior of the offline ipv6 gateway. The only difference to my old config is now that the 'use IPv4 connectivity' tick box is not active anymore ....

Thanks again marjohn for your real time help - appreciated

[marjohn56]

The reason that 'send prefix hint' is normally unset is that most ISPs ignore it anyway. In your case you are using the Fritzbox as the BNG so it behaves differently.


So all that is not behaving is the gateway says it's offline, when in fact it's working?

[bringha]

Hi Marjohn,

I had a 18.7 system properly working with the setting I mentioned (IPv4 and IPv6), I made an Upgrade to 19.1.1 via GUI. When the system comes back, the ipv6 gateway shows offline and all Interfaces have no ipv6 address. Rtsold is not running, dpinger and dhcpv6d are not running and cannot be started. Simple WAN activation/deactivation and/or. reboot of the system did not bring any change. The ipv6 gateway cannot be started manually either.

At this point our conversation started ...

BR br