1
23.1 Production Series / Re: IPv6 on Deutsche Telekom very unstable, PPPoE reload dyfunctional since 23.1
« on: February 02, 2023, 03:34:23 pm »
Hi there
@sbellon I have exactly the same set up as you have and still the good old description of
https://forum.opnsense.org/index.php?topic=21839.0
fits also for 23.1 in so far. From my view close to the "definitive" way you seem to look for.
However, "Zwangstrennung" due to the many different reasons it is carried out from network side is a somewhat different animal which is hard to be addressed from client side in all its (often unknown and intransparent) cases. Zwangstrennung is done for maintenance, new customers on the same line bundle and after-optimization, incident resolution, construction work, and many more. Btw. also all my fritzboxes lost ipv6 after Zwangstrennung pretty often.
I can confirm that I saw also in several old versions of Opnsense that IPv6 did not come up properly after Zwangstrennung. I could then recover ipv6 by manually storing the WAN config again and ipv6 was back. Other than that, playing around with the settings on the client side did not bring any improvement for the Zwangstrennung case.
I also did not see that I got the same ipv6 prefix after a Zwangstrennung that I had before - was always different.
Br br
@sbellon I have exactly the same set up as you have and still the good old description of
https://forum.opnsense.org/index.php?topic=21839.0
fits also for 23.1 in so far. From my view close to the "definitive" way you seem to look for.
However, "Zwangstrennung" due to the many different reasons it is carried out from network side is a somewhat different animal which is hard to be addressed from client side in all its (often unknown and intransparent) cases. Zwangstrennung is done for maintenance, new customers on the same line bundle and after-optimization, incident resolution, construction work, and many more. Btw. also all my fritzboxes lost ipv6 after Zwangstrennung pretty often.
I can confirm that I saw also in several old versions of Opnsense that IPv6 did not come up properly after Zwangstrennung. I could then recover ipv6 by manually storing the WAN config again and ipv6 was back. Other than that, playing around with the settings on the client side did not bring any improvement for the Zwangstrennung case.
I also did not see that I got the same ipv6 prefix after a Zwangstrennung that I had before - was always different.
Br br