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

    6rd tunnel setup on Rogers

    Scheduled Pinned Locked Moved IPv6
    6 Posts 4 Posters 6.0k 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.
    • M Offline
      MaxPF
      last edited by

      I'm trying to get a 6rd tunnel working with my home ISP (Rogers). They provide the settings on this page:
      http://ipv6.rogers.com/tunneled-ipv6-access/

      Provider Prefix 2607:F090
      Provider Prefix Sites 32
      Mask Bits 0
      Relay Address 66.185.95.192

      So, on the WAN interface I set the 6rd prefix to 2607:F090::/32, border relay to 66.185.95.192 and leave 0 for the prefix length. For the LAN interface I set it to track WAN.
      I get a IPV6 assigned to the WAN and LAN interfaces as well as the devices on the lan, so the route advertisement is working. In the LAN firewall rules I allow all IPV6 from any to any.

      However pfsense reports the ipv6 gateway as down and none of the ipv6 tests are successful

      apinger: ALARM: WAN_6RD(2607:f090:42b9:5fc0::) *** down ***

      Any suggestion?

      1 Reply Last reply Reply Quote 0
      • M Offline
        MaxPF
        last edited by

        Something I just noticed. The ipv6 on the WAN interface is /32 while the one on the LAN is /64. Is that supposed to be like that?

        WAN v6/6RD: 2607:f090:xxxx:xxxx::/32
        LAN v6/t6: 2607:f090:xxxx:xxxx::1/64

        1 Reply Last reply Reply Quote 0
        • S Offline
          survive
          last edited by

          Hi MaxPF,

          I don't have any solutions for you, but myself & another user seem to be seeing the same thing as you are using Charter's 6RD service.

          You might want to keep an eye on this thread:

          http://forum.pfsense.org/index.php/topic,59461.0.html

          -Will

          1 Reply Last reply Reply Quote 0
          • D Offline
            databeestje
            last edited by

            Use another monitor address, some use <prefix>::1 others also reply on <prefix>:: (0 basically).

            There is no common ground between those brokers</prefix></prefix>

            1 Reply Last reply Reply Quote 0
            • S Offline
              survive
              last edited by

              Hi databeestje,

              I would suspect that the cause of the monitor being down is because the 6RD connection isn't up. I'm not sure any monitor address is going to work until MaxPF has a connection that passes some tests on the ipv6 test sites.

              I'm in a similar situation as described in the thread in my prior post.

              -Will

              1 Reply Last reply Reply Quote 0
              • E Offline
                eri--
                last edited by

                Can you run a ping -S $WAN_STF_ADDRESS $monitoring address and see if that works?

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