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

    IPv6 Delegated Prefix Not Routing

    Scheduled Pinned Locked Moved IPv6
    4 Posts 2 Posters 456 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
      matthewgcampbell
      last edited by matthewgcampbell

      Hello,
      I've got a delegated IPv6 Prefix to a secondary router and I'm having trouble getting my clients to have internet access through that router with the delegated prefix:
      Screenshot 2023-07-21 at 3.12.49 PM.png I've got a firewall rule that allows this prefix to go to any address using any protocol and I enabled logging so I can clearly see that isn't the issue. I only get a /60 from my ISP (AT&T) so I'm delegating a /62 to my other router.Screenshot 2023-07-21 at 3.38.09 PM.png but pings from clients fail:
      Screenshot 2023-07-21 at 3.40.24 PM.png
      basically I'm asking what the best way to trouble shoot this further is because what has me really confused is that pings from the firewall are fine so it clearly has a valid addressScreenshot 2023-07-21 at 3.41.51 PM.png

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

        @matthewgcampbell

        That other router would have a different subnet. Is there a route from pfSense to 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...

        M 1 Reply Last reply Reply Quote 0
        • M
          matthewgcampbell @JKnott
          last edited by

          @JKnott the other router has ipv6 connectivity (can ping) it’s just the clients from that router that don’t as they are using the prefix I have delegated

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

            @matthewgcampbell

            Again, pfSense has to know the route to that subnet. It knows where that interface is, but not what's beyond it.

            Here's an example, though it's for IPv4 only.

            67e12ab2-1f09-4074-ab90-d157cad78d48-image.png

            In order to access that 172.16.2.0 network, I had to tell pfSense where to find it. You may see your pings go out, but how far do you see the replies coming pack? You can use Packet Capture to watch for them. I bet you see them come into pfSense, but then what??? Without a route, pfSense cannot send them where they're supposed to go.

            I assume that delegated prefix is provided by your ISP.

            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 1
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.