Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    6rd support added

    Scheduled Pinned Locked Moved IPv6
    103 Posts 30 Posters 76.2k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • I
      iancote
      last edited by

      I just installed 2.2.6 and am having this exact issue with Centurylink 6rd.  The brgw calculation in /etc/inc/interfaces.inc is the same as is in the patch, but the gateway ip is coming up as cdab:240::  Also, the interface I'm tracking as subnet 43 comes up as 6d00:43::1 which I'm pretty sure is incorrect as well.  No default route is getting created for the same reason as above, I'm sure.

      Any help would be very appreciated, please let me know anything I can do to help.

      Thanks,
      -ian

      1 Reply Last reply Reply Quote 0
      • F
        Fegu
        last edited by

        I just upgraded to 2.3 from the latest on 2.2.x and suddenly my IPv6 support (via 6RD on the WAN side) is gone. From the server console I can ping6 IPv6-only hosts such as ipv6.google.com. But whatever I try for my LAN-setting (I have tried SLAAC and Track Interface), I can't ping -6 anything (Windows client). I used to have SLAAC on the LAN side and everything was ok. When I try ping -6 ipv6.google.com from a client, it does get the IPv6 IP to ping (i.e. not a DNS issue). The results are sometimes Destination host unreachable and sometimes Request timed out. Any ideas on what I should try?

        Edit: also, Status | Gateways shows WAN_6RD as Offline, even though it works from the server console.

        1 Reply Last reply Reply Quote 0
        • I
          ibikingi @databeestje
          last edited by

          @databeestje Confirmed working from Helsinki, Finland with operator Telia, but had to edit WAN-interface's DHCP-client to request option-212 and run a packet capture for relay and prefix details.
          6RD Prefix:2001: 2003:f400::/38
          6RD Border relay: 84.251.255.254
          6RD IPv4 Prefix length: 14

          From what I've heard, in Finland especially Telia is really behind in native IPv6 -deployment and 6RD is extensively in use. Only the first 32 bits of the prefix are static and to add insult to injury the border relay IPs sometimes change.
          Would it be possible to add a checkbox in the 6RD config GUI for the automatic update of the 6RD parameters via option-212?

          Keep up the good work!

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.