IPv6 native with FritzBox

  • Hello community!

    If I understood it correctly here, native IPv6 now works together with the Swisscom routers. The possibility of sending V6 through V4 using 6RD through a tunnel is also possible for some time now with my plastic router.

    @cybi already has the question here. asked, no answer yet. So here again, explicitly, in a new discussion thread:

    Does native IPv6 work in the Swisscom network with third-party routers, especially with my favorite FritzBox!?

    And no, I won’t cascade the FB behind the IB again. Not an option. For me, the power consumption, i.e. costs/benefits, is too high for the instantaneous heater.

    Show original language (German)
    • cybi likes that.
      • Solutionselected by andiroid

      andiroid

      hallo an alle konstruktiv beteiligte!

      wir haben mit Hilfe von @ChristianEb rausgefunden dass die FB eingestellt mit den Settings aus Post #57 ein DHCPv6 “Solicit” generiert, das DHCP Options 3 (IA_NA) und 25 (IA_PD) gleichzeitig enthält:

      wwe_0-1672267688011.png

      aktuell scheint die SCS Infrastruktur das nicht gut zu vertragen.. (an die Trolle: beide Optionen gleichzeitig zu senden ist RFC konform).. SCS möchte aber nur eine der beiden Optionen gleichzeitig..

      Ich habe Tests mit unterschiedlichen Fritzbox Einstellungen durchgeführt und rausgefunden dass FB mit folgenden Einstellungen ein DHCP Request mit Option 25 und ohne Option 3 erzeugen kann:

      wwe_1-1672268065757.png

      das widerspricht der Online-Hilfe von AVM und zeigte zuerst keinen Unterschied - kein IPv6 Prefix.. Ich habe allerdings aufgrund der Intervention des AVM Support meine FB 7583 von 7.29 auf 7.31 upgedatet.. und habe erstaunt festgestellt dass die FB direkt nach dem Reboot einen IPv6 Prefix bezogen hat!

      Das Update ist auf 7.31 ist schon länger verfügbar aber es wurde bei mir noch nicht automatisch gefunden..

      wwe_2-1672268442593.png

      Ich bin sicher dass ein Update auf 7.31 nicht notwendig ist vermute dass die Einstellungen auch mit 7.29 funktionieren. Ich wäre froh, wenn jemand mit FB 7.29 bestätigen kann dass Einstellungen

      - “use native IPv6”
      - derive global address using assigned prefix
      - rapid commit

      funktionieren und der IPv6 Prefix sofort nach Reboot/Reconnect bezogen wird.

      Gegen-Test mit 7.31 und den Einstellungen aus Post #57 resultierte in dem bekannten Fehler “Keine Antwort vom DHCPv6-Server (SOL)”.. das korrekte Verhalten konnte erst nach anwenden der o.g. Settings und DSL Trennung erreicht werden.

      Wichtiger Hinweis: wenn die FB “fehlerhafte” DHCP requests erstellt hat (und das macht sie jede Minute), werden neue Solicit Requests m.E. vom der SCS Backend für bestimmte Zeit blockiert/ignoriert.. und man muss nachdem korrekte Einstellungen konfiguriert sind, die Box für ca 90 Sec vom DSL trennen - danach funktioniert IPv6 sehr schnell sobald die DSL Verbindung aufgebaut oder “Reconnect” gedrückt wurde.. und statt wie bisher nach x Stunden..

    @andiroid

    thanks for the contribution

    There are always bugs that you can’t find without testing.

    It’s a shame on productive devices.

    At Swisscom, most users are in IPv6 Neverland and there are a lot of errors.

    Errors were also reported at Centro Business, which were then corrected.

    At the IB, the firewall settings are adjusted, IPv6 icmp.

    And maybe PD will also work properly…
    Or do you want to go to another ISP where you can get a native IPv6 with /48 prefix?

    Static if desired.

    this discussion can also help

    Native IPv6 and DHCPv6-PD | Swisscom Community

    Show original language (German)

    “On apprend parfois plus d'une défaite que d'une victoire” — José Raúl Capablanca


    @Black Mamba wrote:

    thanks for the contribution

    There are always bugs that you can’t find without testing.

    It’s a shame on productive devices.

    Um, I’ll probably find these… 😂


    At the IB, the firewall settings are adjusted, IPv6 icmp.

    And maybe PD will also work properly…
    Or you want to go to another ISP where you can get a native IPv6 with /48 prefix?

    Static if desired.

    I don’t want to use IB. I had cascaded routers for too long before I was finally able to obtain my SIP credentials. And actually I don’t want to change provider either. I’m far too comfortable there.

    😕

    I’m just wondering whether there are any restrictions that prevent IPv6 from being activated natively on the Fritzbox. And at the same time, of course, shut down the 6RD tunnel.

    Has anyone already gone this route with a third-party router? Or does it only work adequately with the Internet shops?

    Edit:…and of course not for Geschäftskunden. I have a normal private customer connection here.

    Show original language (German)

    @andiroid

    The determination of whether your Anschluss IPv6 is served with 6rd or with the new IPv6 native with dual stack is not made on the router, but in the Swisscom backend.

    Logically speaking, the system treats this as a contract attribute that cannot be influenced by the user themselves.

    I don’t know how Swisscom deals with connections without Swisscom CPE.

    Maybe they will be gradually changed in the background, but maybe not.

    Have you ever tried to have your Anschluss converted to dual stack via the hotline?

    If there was no knowledge about it, perhaps at least contact with the second level could be made.

    By the way, I currently use a dual stack with prefix delegation and get a 58 prefix from an IB3 for my cascaded internal network, which also works very well.

    Unlike you, I don’t want to replace the provider CPE at all, because Swisscom should take care of the proprietary technology changes from VDSL2 to g.Fast to XGS-PON and then to something else in the future…

    Show original language (German)

    Hobby-Nerd ohne wirtschaftliche Abhängigkeiten zur Swisscom

    Thanks, @Werner for your additions!

    The determination of whether your Anschluss IPv6 is served with 6rd or with the new IPv6 native with dual stack is not made on the router, but in the Swisscom backend.

    Logically speaking, the system treats this as a contract attribute that cannot be influenced by the user themselves.


    Really!? Well then I’ll really have to think about changing providers if the router requirement for the latest IP technology were reintroduced.

    😕


    Have you ever tried to have your Anschluss converted to dual stack via the hotline?

    If there was no knowledge about it, perhaps at least contact with the second level could be made.


    Well, that would also be a sign of poverty that I still have to call the hotline to check the config. This could be implemented in Kundencenter with little effort:

    ✅ Enable IPv6

    ✅ Get a new prefix every x weeks

    Maybe I need to think about changing provider.

    😕

    What I would understand even less. The IPv6 traffic would then slide from the basement to the DSLAM to the “headquarters” and only then into the “foreign” network? (At least that’s how I imagine it…)

    🙄


    By the way, I currently use dual stack with prefix delegation and get a 58 prefix from an IB3 for my cascaded internal network, which also works very well.

    Unlike you, I don’t want to replace the provider CPE at all, because Swisscom should take care of the proprietary technology changes from VDSL2 to g.Fast to XGS-PON and then to something else in the future…


    I can understand this argument. But this is exactly where I see significantly more problems than benefits. SIP forwarding in particular was hair-raising back then. Ok, it worked, but subjectively I always had the feeling that I was traveling with a mess.

    😉

    That’s why I would first like to take the step to a proper dual stack and only then plan for a possible change of media.

    How did you get the /58 prefix? I thought retail customers would only get a /60? Did you also call the hotline or the 2nd level!?

    😜

    Show original language (German)

    @andiroid

    I didn’t do anything special about the prefix length, maybe Swisscom was just more generous with it.

    Currently my IB3 receives a 56 prefix from the backbone when prefix delegation is switched on in the dual stack and when I then activate IPv6 native in my cascaded Asus Merlin network, I recognize a DHCPv6 bind to a 58 prefix in the Merlin log.

    Show original language (German)

    Hobby-Nerd ohne wirtschaftliche Abhängigkeiten zur Swisscom

      Werner

      If you have the Fritzbox and are still with this “ISP”, you should probably try it.

      Ultimately, I can’t say how the backend decides. But the Fritzbox can do it natively and if you had it directly on Anschluss, it would be a non-static /56 prefix.

      So something like this (whether rapid commit is needed? try it out)ipv6.jpg

      What Werner says is another story, a topic of its own. This is the prefix delegation in the Internet Box.

      It would be important to know what you can delegate.

      Previous firmware states that a /60 is delegated. In the thread linked to OP it is said that you only get a /62. The same people say here that you get a /58.

      Ok, sounds really Swisscom 😄…

      What can you get from the PD behind the Internet Box?

      /58, /60 or /62?

      These are such small differences as 64/64s, only 16/64s or even just 4/64s that could be made.

      Conversely, this also applies to the possible number of routers (-1).

      As I said, that would be a separate topic. Maybe once you have agreed on what to do 😉

      Show original language (German)

      During normal working hours, Sam initially only arranges contact with the 1st level in the chat. Only if he doesn’t get any further does he suggest that a specialist call you back. Outside of the helpdesk’s normal working hours, Sam sends a link to a support form.

      If you don’t have a Simply Digital option, you can also call 1st level support and persist and request 2nd level.

      In both cases it will be relatively difficult to get to someone who actually knows the problem and knows what IPv6 actually means.

      Show original language (German)
      6 months later

      So I’m continuing this thread here. Thanks @Tux0ne for the tip. I didn’t see it again until later and of course I didn’t remember the discussion from spring.

      🤪

      Then it would of course be important to mention how you want to operate the FRITZ!Box. Directly on the WAN or via PD on the Internet Büx.

      The Fritzbox in question is connected directly to the WAN, no IB in between. I tried to implement your note. But I’m no longer sure whether this is correct for the direct Anschluss on the WAN.

      As already described in the wrong thread, I get it with every attempt Event monitor of the FB the error message: Internet connection IPv6 could not be established: No response from the DHCPv6 server (SOL).

      @MichelB: If you have relevant information like the @Tux0ne [here](https://community.swisscom.ch/t5/Router-Hardware/Migration-zu-Native- IPv6-Dualstack-completed/m-p/738839#M42287) requested would be available would you please place them here or somewhere else? Thank you!

      🙋‍♂️

      Show original language (German)

      Take a screenshot of the settings you can make on the Fritzbox.
      The screenshot with the setting above is wrong when I read Fritzbox instructions.
      The IPv6 setting should be set to native IPv4 even though you are actually using native IPv6 🙂

      The Germans, with their ISPs that are too big, are using DS Lite. And if it is set to native IPv6, dual stack operation with DS Lite is tried…

      And what would also be important is to replace the WAN interface each time. I think this can be done in the Fritzbox with a reboot.

      Show original language (German)

        Tux0ne Thanks! Here are my current settings:

        andiroid_0-1670689616255.png

        I tried different variants with the LAN prefix without success. I didn’t restart because the event viewer showed a new error message about the unreachable DHCPv6 (“No response from DHCPv6 server (SOL)”) with every config change. But I’ll just try that…

        …but there was no change either. 😕

        Show original language (German)

        @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? 😉

        Show original language (German)

        @andiroid wrote:


        @Tux0ne wrote:

        Try using the init7 setting regarding 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 the 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? 😉


        Fritzbox = help yourself

        Show original language (German)

        @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.

        😶

        Show original language (German)