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

    IPv6 not working - WAN and LAN Interface getting an IP Adress, not any Client

    Scheduled Pinned Locked Moved IPv6
    17 Posts 2 Posters 1.4k 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.
    • Gamienator 0G
      Gamienator 0 @JKnott
      last edited by Gamienator 0

      @jknott So I tried this one:

      WAN Interface:
      IPv6
      Port Number 546

      got this small package capture. Does this help?

      WAN_2.zip

      But since this is in an Proxmox with OVS Switch configured, could I capture from that?

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

        One thing I see right off is in the solicit, you're asking for a /60, but being offered a /59. We saw this recently with someone on Comcast, IIRC. On my system, I request and get a /56. I have no idea why you're getting that.

        IA Prefix
        Option: IA Prefix (26)
        Length: 25
        Value: ffffffffffffffff3c000000000000000000000000000000…
        Preferred lifetime: infinity
        Valid lifetime: infinity
        Prefix length: 60
        Prefix address: ::

        IA Prefix
        Option: IA Prefix (26)
        Length: 25
        Value: 000934d100126f513b2a0209084c1239a000000000000000…
        Preferred lifetime: 603345
        Valid lifetime: 1208145
        Prefix length: 59
        Prefix address: 2a02:908:4c12:39a0::

        On the LAN side, I see your RAs are saying to use a /63, when it should always be a /64. This also happened with that guy on Comcast.

        ICMPv6 Option (Prefix information : 2a02:908:4c12:39a0::/63)

        Given the same thing is happening with 2 different ISPs, I wonder if there's a bug somewhere.

        BTW, you don't have to ZIP the captures. Just download and paste the file is good enough.

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

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

          @jknott

          Here's the Comcast thread, with a similar problem to yours.

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

          Gamienator 0G 1 Reply Last reply Reply Quote 1
          • Gamienator 0G
            Gamienator 0 @JKnott
            last edited by

            @jknott Wow ... that is really interesting, especially now, that comcast is not an german based ISP and I got the same issues.

            Which now makes me think: Is there a work around that I can reach out via IPv6, is should I even disable it? I'm even fine using NAT until it's sorted out 😲

            Gamienator 0G 1 Reply Last reply Reply Quote 0
            • Gamienator 0G
              Gamienator 0 @Gamienator 0
              last edited by Gamienator 0

              Aehm ... Wow, not I'm just blown away ...

              I got now an IPv6 Connection 😲

              e7fcec5e-4341-415f-9f38-88d8a41becfc-image.png

              4c9b2632-c826-4748-833d-51a828f40d3a-image.png

              The "only" thing I changed in pfsense: Set WAN to /59 prefix, DHCPv6-PD to /63 prefix. That is ... Wow ...

              Now my last question is: Do I need to setup my pihole with IPv6 too or is it enough to be reachable via IPv4?

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

                @gamienator-0

                The /59 & /63 prefixes indicate there's still a problem somewhere.

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

                Gamienator 0G 1 Reply Last reply Reply Quote 0
                • Gamienator 0G
                  Gamienator 0 @JKnott
                  last edited by

                  @jknott That's true ... Still suprised that I'm now connectable 😬

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

                    @gamienator-0

                    My concern is that /63. The LAN side prefix is supposed to be /64 for SLAAC to work properly. I don't know what will happen with the wrong 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...

                    Gamienator 0G 1 Reply Last reply Reply Quote 0
                    • Gamienator 0G
                      Gamienator 0 @JKnott
                      last edited by

                      @jknott Hmm, okay. Well every VM in my network is configured to use SLAAC and working atm

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

                        @gamienator-0

                        At the moment, you're using an even number prefix. What happens if you pick an odd one? That /63 moves the boundary between the prefix and suffix over by one to the left. Will a prefix ID 1 now be the same as 0?

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