---

@Tux0ne wrote:

Try using the init7 setting for the IPv6 tab, just use native IPv4.

🌈🐰7️⃣

---

@Tux0ne: Thanks for the tip. Didn’t do anything. 😕 But I can’t set everything on my “old” 7490. VLAN can’t do that. Don’t think that matters, do you?

The error messages in Event Viewer are still:

“DHCPv6 error with error reason 8 (UnspecFail)”

and

“Internet connection IPv6 could not be established: No response from DHCPv6 server (SOL)”

@MichelB: No news from the insiders? 😉

@5018 wrote:
Fritzbox = help yourself

Thank you for this extremely valuable contribution! <Irony off> Next time leave it on your keyboard. If I could help myself, I wouldn’t ask for help here.

😶

---

@Tux0ne wrote:

Those affected are welcome to contact our support: avm.de/service/support

Are you sure you don’t want a referral code too? 😉

---

@Tux0ne: Thanks, I did that without a referral code. 😉 I generated the support data for the Büxe for the request. The information in there already suggests that I won’t get a prefix. Everything is somehow logical if the box does not receive a DHCPv6 server…:

0: IPv6: native (none)
0: IPv6: connecting
0: IPv6: no address
0: IPv6: no prefix (0)
0: IPv6: mtu 1500
0: IPv6: error 4/0×2/8 2022-12-12 21:43:55 UnspecFail (DHCPv6/unknown)
0: IPv4: native
0: IPv4: connected since 2022-12-12 21:43:55 (setup time 0 secs) (connect cnt 3)
0: IPv4: disconnect prevention disabled
0: IPv4: ip ww.xx.yy.zz mask 255.255.252.0 gw ww.xx.yy.zz dhcp mtu 1500
0: IPv4: masqaddr ww.xx.yy.zz
0: IPv4: dns 195.186.4.162 195.186.1.162

Where ww.xx.yy.zz is my WAN IP. Let’s see what the Berliners will answer. Keep you posted.

🙋‍♂️

---

@5018 wrote:

@andiroid You probably didn’t understand the referral code.

But I’m afraid that the instructions are rather inadequate.

---

@5018: Thanks, I actually didn’t understand that. 😶‍🌫️ I actually came across the link from several sites and it actually didn’t help. I’m excited to see what AVM does with my support request… 😐

@Tux0ne: The fiber arrived in the technical room last Monday. I will probably set out to convert my local infrastructure to fiber in 2023. And if things are going well, I’ll do the accounting. It may well be that I have to think about the code again. 👍

---

@5018 wrote:

Maybe connect a real router. It will then probably get native IPv6. Then you can always go back to a FB. Maybe it will work then.

---

I studied your sentences for a long time and at first I thought you were trolling again. And I almost shouted “no router requirement”. Regression is a bit harsh. My third-party router is not a step backwards. It hits with Mesh, Google address book, regular free feature release, re-use of ‘old’ routers as AP… I digress. 🤪 But you suspect that the Swisscom router activated IPv6 on the Anschluss and then the FB finally found a DHCPv6? 🤔 I’m hardly a proven expert in IPv6, but I heard it differently here (a classic!) and remembered it differently: IPv6 configures itself. All changes are flushed through the network. Be it a new prefix or an initial DHCPv6. I think that the systems at either Swisscom or AVM need to be dewormed. 🪲

Other hypotheses are welcome to read here. I’ll stay tuned. 👀

---

@Scheufreveu69 wrote:

According to this thread, this was tried earlier, but the dual stack migration may not have been completed at this point.

Maybe someone “affected” can try this again, I’m holding back, the “step back” from Swisscom CPE to “third-party router” is always tedious.

---

I disposed of my Swisscom router. 😁 I will only do this if I have the glass in the house and no other solution at hand. And no, it’s not a step backwards if I can then disconnect the IB from the power again. I know the drama with IP telephony, router behind router… and it’s just plain scary. I will probably have to evaluate the AVM alternative soon. 😉

---

@Tux0ne wrote:

---

The same situation occurs for me (Fritz 758x) - “Internet connection IPv6 could not be established: No response from the DHCPv6 server (SOL)”

I did a packet dump over an IPv6 connection attempt and found the following:
- There are no RAs on the WAN side, so the FB cannot obtain a prefix and sends a “SOLICIT XID” request (DHCPv6)
- the SOLICIT

It looks to me that no IPv6 is active on the Anschluss, i.e. Swisscom has not switched on a dual stack.

---

Let’s ask around. No IP fan has a RES Anschluss. But there will be someone who can figure it out ☺️

---

@Tux0ne: Cool Thanks for the additional info. It confirms my half-knowledge with a few interesting facts. I’ll have to try the packet dump thing too, just the right activity for dark winter nights. 😉

@Swisscom: Does anyone know why the 6RD server is switched off and dual stack is not activated? Or asked specifically: What needs to be done to activate dual stack? Can I find the setting in Kundencenter? Or is the assumption correct that you first have to connect an IB to activate the feature? Questions after questions… 😕 It would be nice to hear something relevant from the operator, I’m hardly the only one with a third-party router in the network!? I’ll also do a nice know-how article - as a return / win-win situation. 😀