[SOLVED] 18.1.5: IPv6 interface tracking does not work for me any more

[gothbert]

Hi,

upgraded from 18.1.3 to 18.1.5 recently. Now my LAN interfaces do not get IPv6 addresses any more as they did previously in the 18.1 series. The LAN interfaces are set to IPv6 Configuration Type: Track Interface (WAN). WAN has IPv6 address.

Rebooted several times, even with suricata turned off, without success. What logs should I have a look into on the search for the cause?

Kind regards
Boris

[franco]

Hi there,

Is this PPPoE on WAN? Did you skip 18.1.4? if yes we have two versions to cover.

You can try:

# opnsense-revert -r 18.1.4 opnsense

Or...

# opnsense-revert -r 18.1.3 opnsense


Cheers,
Franco

[gothbert]

I went from 18.1.3 to 18.1.4 to 18.1.5 in a few minutes without actually having a look at 18.1.4.

I will return to 18.1.3 and then upgrade one by one to see which version first causes the issue.

Thank you for the guidance. Will report back when I am done with the test.

[BeNe]

Just for Info:

Updated from 18.1.4 to 18.1.5 without any IPv6 issues.
Track the IPv6 WAN Interface for 9 LAN´s without any problem on last Update. So it´s not a general issue.

[franco]

Same here. It could be a fix interacting with a certain configuration in a bad way. But all actual IPv6 tracking changes are still on the development branch (but also work in a real work office install).

[gothbert]

Still investigating. Will keep you posted.

Some probability that it is a local problem that occured around the same time as I did the updates and thus got attributed to the update. Rebooted the cable modem in front of the OPNSense box and also had to disable/reenable a NAT rule (transparent proxying) which I received a complaint about by OPNSense after upgrading to 18.1.5 and which prevented me from accessing port 80 anywhere after downgrade to 18.1.3 - curious.

Which log files should I inspect to gain more insight on what might be happening?

- Boris

[gothbert]

Hi,

I confirm that IPv6 interface tracking on OPNSense 18.1.5 works fine for me.

The issue was related to a misconfiguration of the upstream cable modem and not to OPNSense.

I beg your pardon for bothering you with a non-issue.

Best regards
Boris

[franco]

Hi Boris,

Nice to hear, no worries at all... thanks for the quick resolve.


Cheers,
Franco