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

    Migrating to IPv6

    Scheduled Pinned Locked Moved IPv6
    28 Posts 7 Posters 4.9k 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.
    • C
      creiss
      last edited by

      Jeesh,

      So I have my transfer net:

      2a01:xyxy:5000:3::1/64 Their End
      2a01:xyxy:5000:3::2/64 My End

      I upped 2a01:xyxy:5000:3::2/64 as the WAN ip for pfsense. Ping6 form somewhere on the planet to 2a01:xyxy:5000:3::2 yields success. I added the default route to 2a01:xyxy:5000:3::1. Beyond that I have no clue on how to proceed.

      If I take the first /64 of my /47 (2a01:xyxy:6000::1/47)

      Yields me with 2a01:xyxy:6000::1/64…

      Okay I admin I am at a total and utter loss here. My brain, after weeks of bashing against IPv6 can not connect the dots, or any dots here. In my 20 years in meddling with the Internet I never asked this: But can anyone tell me what IP goes hwere to get a single ping from a server to the outside? How to I do the transfer net pfsense style?

      Thanks,
      Christian.

      1 Reply Last reply Reply Quote 0
      • DerelictD
        Derelict LAYER 8 Netgate
        last edited by

        You keep saying /47. Is it really /47?

        Chattanooga, Tennessee, USA
        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
        Do Not Chat For Help! NO_WAN_EGRESS(TM)

        1 Reply Last reply Reply Quote 0
        • C
          creiss
          last edited by

          Hey,

          yes, confirmed: /47. It's either /64 or /47. /64 was too small for people here so I went for /47.

          1 Reply Last reply Reply Quote 0
          • JKnottJ
            JKnott
            last edited by

            You keep saying /47. Is it really /47?

            Nothing wrong with a /47.  While not common, it's twice the size of a /48.

            PfSense running on Qotom mini PC
            i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
            UniFi AC-Lite access point

            I haven't lost my mind. It's around here...somewhere...

            1 Reply Last reply Reply Quote 0
            • johnpozJ
              johnpoz LAYER 8 Global Moderator
              last edited by

              So you go from a /64 to a /47 which is 128K /64's - wtf is this DC thinking??

              Well put ::1 on pfsense lan side interface - then on box on this lan use ::2 in your /64 set its gateway to ::1

              Allow ipv6 on that interface and your ready to rock..  You can get fancy with auto handing out IPs, etc. etc. after you get your pinging working.

              Then to allow internet to get to that box - just put the rules on your wan to allow the IPv6 to where you want to allow it an what protocol, etc.

              An intelligent man is sometimes forced to be drunk to spend time with his fools
              If you get confused: Listen to the Music Play
              Please don't Chat/PM me for help, unless mod related
              SG-4860 24.11 | Lab VMs 2.8, 24.11

              1 Reply Last reply Reply Quote 0
              • DerelictD
                Derelict LAYER 8 Netgate
                last edited by

                Zero reason to stray from the expected /48, which lies not only on a hex digit boundary but a : group boundary as well.

                If it is going to be split into multiple /48s it should probably be a routed /40 or /44 instead.

                But whatever. Like you said it's not against any rules. Just unexpected.

                Chattanooga, Tennessee, USA
                A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                Do Not Chat For Help! NO_WAN_EGRESS(TM)

                1 Reply Last reply Reply Quote 0
                • C
                  creiss
                  last edited by

                  @johnpoz:

                  Well put ::1 on pfsense lan side interface - then on box on this lan use ::2 in your /64 set its gateway to ::1

                  Hey,

                  Thanks <3
                  And 2a01:xyxy:5000:3::2/64 in WAN with 2a01:xyxy:5000:3::1/64 as default GW, right?

                  -Chris

                  1 Reply Last reply Reply Quote 0
                  • C
                    creiss
                    last edited by

                    HOLY JEBUS!

                    After whacking my head against this and doubting my networking skills… I got it running. Turns out: A rogue IPMI from (older) testing times was also using the same IP used for the transfer net. This resulted in some kind of wierdness.

                    Deactivated ipv6 on said ipmi, everything is working.

                    Thanks all you rock!
                    I can rest easy tonight.

                    \o/
                    -Chris.

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