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

    pfSense 2.5.0 not picking up default gateway via SLAAC ?

    Scheduled Pinned Locked Moved IPv6
    7 Posts 3 Posters 816 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.
    • D
      dr_tech
      last edited by dr_tech

      I use 4G as my uplink to the internet. My ISP's CPE hands out a single IPv6 address (/64 subnet) for all the devices downstream via SLAAC (no support for DHCPv6 and hence no PD).

      I need IPv6 connectivity for VPN and some other services I have hosted elsewhere (CGNATv4 + IPv6, hence using IPv6 for public addresses).

      I have setup my WAN interface to obtain IPv6 via SLAAC, and the interface does take up an IPv6 address, however I cannot ping anything else than the devices in the same IPv6 subnet (WAN side).

      Under Diagnostics > Routes, I do not see a valid IPv6 route, hence I believe that there's the problem.

      What else do I need to do to enable pfSense to pick up the IPv6 gateway via SLAAC itself ?

      (Trying to use IPv6 NAT for IPv6 connectivity on LAN).

      JKnottJ S 2 Replies Last reply Reply Quote 0
      • JKnottJ
        JKnott @dr_tech
        last edited by

        @dr_tech

        SLAAC will provide info for a single interface only, not a gateway. Also, you can't split a single /64 into multiple networks without breaking things.

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

        D 1 Reply Last reply Reply Quote 0
        • D
          dr_tech @JKnott
          last edited by dr_tech

          @jknott said in pfSense 2.50 not picking up default gateway via SLAAC ?:

          @dr_tech

          SLAAC will provide info for a single interface only, not a gateway. Also, you can't split a single /64 into multiple networks without breaking things.

          But SLAAC should provide the default gateway for pfSense itself, right ? I can't ping anything using the WAN interface on pfSense itself.
          a2b1aeed-fc62-4736-8c92-9660f637af83-image.png

          I am not trying to split the SLAAC assigned IP into multiple subnets, infact :

          WAN (SLAAC:2002:aa:bb:cc::abcd) <NATv6> LAN (fd00::1/64)

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

            @dr_tech

            It provides the info for devices, such as computers, tablets, phones, etc. to connect to a network, including gateway. It does not provide info for routers to use on their LAN side.

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

            D 1 Reply Last reply Reply Quote 0
            • D
              dr_tech @JKnott
              last edited by

              @jknott

              pfSense should atleast be able to ping a public IPv6 through it's WAN interface ?

              9da9a362-0118-4664-93fe-f84f4b99b784-image.png

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

                @dr_tech said in pfSense 2.5.0 not picking up default gateway via SLAAC ?:

                pfSense should atleast be able to ping a public IPv6 through it's WAN interface ?

                Yep, assuming it's a routeable address. However the WAN address will likely not be from within your prefix.

                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
                • S
                  SteveITS Galactic Empire @dr_tech
                  last edited by

                  @dr_tech If you're actually on 2.5.0 there was this IPv6 fix in 2.5.1: Gateway value for DHCP6 interfaces missing after RA events triggered script without gateway information

                  Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                  When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
                  Upvote 👍 helpful posts!

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