[solved] No IPv6 after upgrading

[iam]

Hello,

after upgrading to 19.1 the OPNsense has no IPv6 on the WAN interface anymore. On the WAN side the OPNsense is connected to a FritzBox.

There is no dhcp6c running. Also changing the configuration in the web interface don't cause changes to the file /var/etc/dhcp6c_wan.conf.

Has someone else observed something similar?

Cheers,
iam

[marjohn56]

Check the system & dhcpd log for any dhcp6c entries, is there anything there?

[iam]

The last entry in /var/log/dhcpd.log was written before the upgrade.

Here are the maybe relevant entries in system.log:

Code Select Expand


Feb  3 14:18:50 opnsense opnsense: /interfaces.php: ROUTING: IPv4 default gateway set to wan
Feb  3 14:18:50 opnsense opnsense: /interfaces.php: ROUTING: no IPv6 default gateway set, assuming wan
Feb  3 14:18:50 opnsense opnsense: /interfaces.php: ROUTING: setting IPv4 default route to 192.168.XY.1
Feb  3 14:18:50 opnsense opnsense: /interfaces.php: ROUTING: removing /tmp/re0_defaultgw
Feb  3 14:18:50 opnsense opnsense: /interfaces.php: ROUTING: creating /tmp/re0_defaultgw using '192.168.XY.1'
Feb  3 14:18:50 opnsense opnsense: /interfaces.php: ROUTING: skipping IPv6 default route
Feb  3 14:18:51 opnsense opnsense: /usr/local/etc/rc.dyndns: Aborted IPv6 detection: no address for re0


[marjohn56]

No, we are looking to see if there are any entries from dhcp6c. If it's not starting ( or exiting ) there should be a log entry.

[iam]

Maybe this is more helpful:

Code Select Expand


Feb  1 07:46:41 opnsense opnsense: /usr/local/etc/rc.newwanipv6: The command '/sbin/ifconfig re0 inet6 $ipv6address delete' returned exit code '1', the output was 'ifconfig: ioctl (SIOCDIFADDR): Can't assign requested address'


EDIT: Of course not. That was before the upgrade

[iam]

I can start the dhcp6c manually:

Code Select Expand


/usr/local/sbin/dhcp6c -f -d -D -c /var/etc/dhcp6c_wan.conf -p /var/run/dhcp6c_re0.pid re0


It's no crashing and binds an IPv6 address to the interface. But the routing table seems not to be correct afterwards.

Is there a config file like /etc/network/interfaces in Debian?

[marjohn56]

Have you tried enabling Direct!y send solicit in dhcp6c settings?

[iam]

Yes I've enabled this option in the web interface. But I'm not sure that is synced to the configuration files. Changing the prefix size doesn't change /var/etc/dhcp6c_wan.conf. It's still:

Code Select Expand


interface re0 {
  send ia-na 0; # request stateful address
  send ia-pd 0; # request prefix delegation
  request domain-name-servers;
  request domain-name;
  script "/var/etc/dhcp6c_wan_script.sh"; # we'd like some nameservers please
};
id-assoc na 0 { };
id-assoc pd 0 {
  prefix ::/60 infinity;
};


[marjohn56]

Even so, dhcp6c should be starting, you will see that in the logs. Have you set dhcp6c debug on and the rebooted. Then take a look at the dhcpd logs and filter on dhcp6c.

[iam]

As expected, there is still no log entries regarding DHCPv6 (only after starting dhcpv6 manually).

By the way, it's also a RealtekChip, but with static IPv4. The MTU is 1500.

[marjohn56]

Something is very wrong here. Can you scp into opnsense and copy the system, configd and dhcpd logs. zip them up and attache them your reply.


I've just tried my test unit with a static v4 and dhcp6 on the wan, works perfectly.

[iam]

Here are the requested logs.

[marjohn56]

Your ISP is not responding in the expected way. There's loads of entries from dhcp6, here's just a sample.



Can you turn on the debugging option in dhcp6c settings on the WAN page. Save and reboot, let it run for an hour then send me the dhcpd log again.

[iam]

You mean this entries?

Code Select Expand


Feb  2 09:16:45 opnsense dhcp6c[30652]: Received REPLY for RENEW
Feb  2 09:46:45 opnsense dhcp6c[30652]: Sending Renew
Feb  2 09:46:45 opnsense dhcp6c[30652]: unknown or unexpected DHCP6 option opt_86, len 16
Feb  2 09:46:45 opnsense dhcp6c[30652]: Received REPLY for RENEW


There were written before the upgrade. By the way, the ISP is a FritzBox.

[marjohn56]

O.K. I see now.


The last four entries are actually created by dhcp6c*.script, but I know you said you manually ran it, so it might be from those. That being the case then dhcp6c is not being started but can run manually which rules out a corrupt dhcp6c client itself. It may be something as simple as a stuck pid. So we'll check that first.


Go and have a look in /var/run and and see if there is a dhcp6*.pid file there, if there is delete it and reboot.