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

    IPv6 Track Interface gives /64 from WAN to LAN - was giving out /56

    Plus 23.05 Development Snapshots (Retired)
    4
    6
    457
    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.
    • U
      uniqueusername
      last edited by uniqueusername

      Hi,

      I tried getting IPv6 working on 23.01, and read through that it was not working. Attempting again with 23.05RC is having different, but still unexpected (not working in a different way) results. I'm configuring IPv6 through a 3100 with multiple subnets on the DPORTs (with VLANs).

      I have Spectrum in Austin, TX. Changing the prefix hint fails on /48, but works with /56 and I was able to get the LAN to track the WAN and I could hand out /60 subnets with version 23.01.

      Now I request /56, but track interface on LAN from WAN gives only a /64 subnet - so no subnets to hand out. I don't think Spectrum suddenly gave me a smaller subnet - as the IPv6 address has two zeros 00 in the same network address location. Testing with different prefix hints indicates that /56 is the correct one to request.

      If I ignore the fact that I don't have /60 subnets to hand out, the RA does not appeat to be advertising via DHCPv6 and RA assisted - as I am not getting any IPv6 addresses on my network - and I was before with version 23.01.

      It seemed that with 23.01 the only thing not working was the Gateway/Routing. Now, more things seem broken. I'm clearly no expert, but am trying to learn IPv6.

      Can anyone else trying to get IPv6 working with 23.05 have a look please?

      Thank you,

      Neil

      1 Reply Last reply Reply Quote 0
      • U
        uniqueusername
        last edited by

        One more clue - maybe.

        I have the LAN track the WAN interface.

        The DPORT interface is static - based on the LAN subnets "available" and configured.

        I believe the IPv6 address should have a /60 subnet, but when I configure that, I get an error that it conflicts with a Static Route. I don't have any static routes configured yet.

        U 1 Reply Last reply Reply Quote 0
        • the otherT
          the other
          last edited by

          Hey there,
          Well, i get a /56 from ISP. Edge router gives pfsense a 57.
          Track interface for lan results in64 as well, other interfaces (vlans running on mother if lan) get 64 as well...
          Everything up and running...with 2.6 ce

          Kinda don't understanding the issue...

          the other

          pure amateur home user, no business or professional background
          please excuse poor english skills and typpoz :)

          1 Reply Last reply Reply Quote 0
          • U
            uniqueusername @uniqueusername
            last edited by

            Hi,

            Too late to edit my original post. I figured out one thing I had wrong. So, am continuing:

            If I ignore the fact that I don't have /60 subnets to hand out, the RA service has error: radvd 85376 prefix length should be 64 for mvneta1.

            I am getting addresses on my network devices. I can ping through the firewall from DPORT1 and LAN to WAN, but I cannot ping to an outside address. My default IPv6 gateway is monitoring and showing online.

            So it seems I am still stuck like before with 23.01, and now I think it is something I'm configuring wrong in the static routes. With the posted IPv6 issues on 23.01, I thought it wasn't me...

            Can anyone else trying to get IPv6 working with 23.05RC have a look please?

            Thank you,

            Neil

            Bob.DigB 1 Reply Last reply Reply Quote 0
            • Bob.DigB
              Bob.Dig LAYER 8 @uniqueusername
              last edited by

              @uniqueusername You got some stuff not right. ;)
              So first, having only a /64 on LAN is correct, if you are using Track Interface. And that was always the case, so don't fight it. Why do you think you need more on your LAN?

              IPv6 is working fine with 23.05-RC, there where only a few who had problems.

              1 Reply Last reply Reply Quote 0
              • stephenw10S
                stephenw10 Netgate Administrator
                last edited by

                Mmm, not seeing any issues here. Can you post what you've configured?

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post