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

    IPv6 LAN to WAN NAT

    IPv6
    2
    11
    930
    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
      chrisjmuk
      last edited by

      Hello All

      We have a public IPv6/32 range and we have split them up, so we are using a ipv6/64 for example.

      The issue is that we have local computers which i have created a local IPv6 address fc00:1:1::/64 and want to nat out to our public ipv6 for example 2b02:2bc8:1:1::/64

      As they are kind of both inernal as they run inside the network it doesnt seem to work when i set the gateway in pfsense 2b02:2bc8:1:1::1/64 which is set in my cisco router i cant ping the range any more but can ping from my cisco router, not sure what is going on.

      Also tried NTP with 0 luck and made no difference.

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

        Given you have a /32, why would you want to use NAT, when you have so much public address space? Just assign another /64 to those computers. The reason for NAT was to get around the IPv4 address shortage and there's no shortage of IPv6 addresses.

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

        C 1 Reply Last reply Reply Quote 1
        • C
          chrisjmuk @JKnott
          last edited by

          @jknott security..

          You don't put public it's on a local secure lan.

          Also want it to connect to other internal networks on ipv6

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

            @chrisjmuk

            That's what firewall rules and routing are for. If you don't enable that network to route to the Internet, it won't. If you do, you use appropriate rules to allow only what you want. Claiming NAT protects you is a false sense of security.

            BTW, you can route between public and unique local addresses just fine. I do it here.

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

            C 1 Reply Last reply Reply Quote 0
            • C
              chrisjmuk @JKnott
              last edited by

              @jknott

              What do you have setup for NAT for configuration?

              C JKnottJ 2 Replies Last reply Reply Quote 0
              • C
                chrisjmuk @chrisjmuk
                last edited by

                @chrisjmuk

                This is my basic setup

                CISCO vLan IP as GW - 2b02:2bc8:1:1::1/64

                pfsense details
                pfsenseIPv6 Gateway - 2b02:2bc8:1:1::1
                WAN IPv6 - 2b02:2bc8:1:1::3/64

                LAN IPv6 - fc00:1:1::/64

                NAT Outbound Settings

                Interface - WANv6
                Source Network - fc00:1:1::/64

                it pings the WANv6 interface IP from fc00:1:1::/64 pc's

                and when i ping from pfsense i can ping fine as well but not on nat.

                So we want the fc00:1:1::/64 to ping the 2b02:2bc8:1:1::/64 range

                When i dont set the WAN IPv6 on the interface i can ping fine, if i set the gateway i cant ping

                Firewall rules are all ok and IPV6 is allowed and icmp enabled

                C 1 Reply Last reply Reply Quote 0
                • C
                  chrisjmuk @chrisjmuk
                  last edited by

                  Have setup a test on a lab server with vm's and i am getting the same issues. i am not sure where this issue.

                  C 1 Reply Last reply Reply Quote 0
                  • C
                    chrisjmuk @chrisjmuk
                    last edited by

                    would i need to create any static routes?

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

                      @chrisjmuk

                      I don't use NAT on IPv6 at all. No need for it.

                      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
                      • JKnottJ
                        JKnott @chrisjmuk
                        last edited by

                        @chrisjmuk said in IPv6 LAN to WAN NAT:

                        would i need to create any static routes?

                        Routing between networks directly connected to pfsense is automatic. Networks beyond that require manually configured routes. The exact method depends on the client. i.e. Linux, Windows, OS/2, etc.

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

                        C 1 Reply Last reply Reply Quote 0
                        • C
                          chrisjmuk @JKnott
                          last edited by

                          @jknott found the issue, was stuck in the state, needed to clear.

                          another issue is that i can cant ping a certain ip on my cisco and it cant ping the pfsense, ::1 but can ping ::20 no idea why.

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