Deutsche Telekom VDSL IPv6 having issues after upgrade to 24.7

[beisser]

i had a cronjob configured that did a periodic interface reset at 03:00 at night, but i have disable that some time ago.

i compared a RA in wireshark before the restart and after the restart of the RA service and they are identical.
it seems to be advertising correctly even before restart, but for some reason traffic just doesnt pass.

i have attached 2 screenshots of the packets in wireshark. im not able to make out any differences

[meyergru]

I do not get why a radvd restart can help if the RA content does not change and there are RAs sent before the restart.

[tokade]

Perhaps there are scripts that also restart other components depending on the radvd restart?

[beisser]

Perhaps there are scripts that also restart other components depending on the radvd restart?

that would be interesting to know.
would make sense because as far as my limited understanding goes radvd does basically nothing but advertise things.
maybe someone with deeper knowledge of opnsense could comment on this.
is there anything that gets restarted whenever you restart radvd that might explain why ipv6 forwarding resumes immediately when radvd is restarted?

for now i am going to test if the intervals make a difference.
last night i had them at default 200/600, tonight i will leave them at 3/4 and see how the firewall behaves tomorrow morning.

[riverchu2023]

Hi,

Can you try this patch?

https://github.com/opnsense/core/commit/287c13beb

# opnsense-patch 287c13beb


Cheers,
Franco

This worked for me.

[beisser]

latest update for me.
the firewall didnt have any issues forwarding ipv6 in the morning after setting the intervals to 3/4 in the evening before.
when set to 200/600 it had issues in the morning.

i am still not sure why or how this is and why noone else is seeing this.

[PhoenixRider]

I'am using Deutsche Telekom, too. On WAN side, you have to choose DHCPv6 with IPv6 Prefix Delegation 56. On LAN-Interfaces you should use Track Interface with an Prefix-ID.

[Patrick M. Hausen]

I'am using Deutsche Telekom, too. On WAN side, you have to choose DHCPv6 with IPv6 Prefix Delegation 56. On LAN-Interfaces you should use Track Interface with an Prefix-ID.

Or - in case of a business contract with a fixed /56 - just configure all internal interfaces statically.

[beisser]

I'am using Deutsche Telekom, too. On WAN side, you have to choose DHCPv6 with IPv6 Prefix Delegation 56. On LAN-Interfaces you should use Track Interface with an Prefix-ID.

this is the case.
see attached screenshots.

[beisser]

and another screenshot

[Patrick M. Hausen]

Don't enable "use IPv4 connectivity".

If it is a business line, why don't you configure LAN statically? Enable Router Advertisments, done.

[beisser]

Don't enable "use IPv4 connectivity".

If it is a business line, why don't you configure LAN statically? Enable Router Advertisments, done.

its not business. its a completely normal home vdsl with changing prefixes.
nothing to configure statically there.
and any guide i have ever found anywhere says you have to use "use ipv4 connectivity" to get a prefix.
if you dont, you dont get one.

but i can try that, no problem. give me a few minutes

[Patrick M. Hausen]

Sorry, you are right. I got confused.

[beisser]

yup ipv6 broke, when i didnt use ipv4 connectivity. reenabled that.

[PhoenixRider]

I'am using Deutsche Telekom, too. On WAN side, you have to choose DHCPv6 with IPv6 Prefix Delegation 56. On LAN-Interfaces you should use Track Interface with an Prefix-ID.

this is the case.
see attached screenshots.

Request Prefix only have to be enabled! ;)