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

    Help needed geting fresh install playing nice with IPV6

    Scheduled Pinned Locked Moved IPv6
    23 Posts 2 Posters 2.3k 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.
    • JKnottJ
      JKnott @ftarz
      last edited by

      @ftarz

      You have several "release XID" packets. I'm not sure yet why that's happening.

      5f6732c7-ea3f-4416-9e82-4e170f9502b4-image.png

      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 @ftarz
        last edited by

        @ftarz

        If you have Do not allow PD/Address release selected, try deselecting it and rebooting.

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

        F 1 Reply Last reply Reply Quote 0
        • F
          ftarz @JKnott
          last edited by

          @jknott
          I do not have "Do not allow PD/Address release" selected.

          Here are my WAN and LAN configurations.

          WAN (re0).zip LAN (em0).zip

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

            @ftarz

            That WAN page isn't readable.

            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
            • F
              ftarz
              last edited by

              WAN (re0).7z

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

                @ftarz

                Same thing. Try doing a screen capture.

                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 @ftarz
                  last edited by

                  @ftarz

                  In packet 5 of your capture I see a release of 2606:a000:bfc0:b6:719c:fa6f:6408:8118.

                  Does that appear on your WAN interface? It's not 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
                  • F
                    ftarz
                    last edited by

                    screenshot.zip

                    So you noticed that the WAN IPV6 address I get from my ISP (Spectrum) starts with 2606, while the IPV6 address that pfSense gives me by "tracking" WAN is a 2603.

                    This is one of the problems I'm having.

                    I don't know why this happening, but you can clearly see it in the screenshot.

                    Frank

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

                      @ftarz

                      That's entirely normal. The WAN address has nothing to do with the LAN prefix, other than they're from a pool that belongs to the ISP. In fact, all you need on the WAN side is a link local address.

                      Recapping some of the earlier stuff, I also see that v6/t6 on my LAN and don't know what it means.

                      In that screen capture, I see you have valid WAN and LAN IPv6 addresses. You say the gateway is down. Is gateway monitoring enabled? If so, you can disable it, as you don't need it. However, if you do use it, you need a valid IPv6 address to ping. I used traceroute to google and picked the first valid global address along the path for my monitor address. You can't use your gateway address, as it's link local, which pfSense doesn't like.

                      BTW, you don't have to keep zipping everything. You can paste an image directly on this site. Also, it appears you took a photo of a serial console. You could also have used ssh to connect over the LAN and then taken a screen capture of the ssh session or even copy 'n paste, like this:

                      pfSense - Netgate Device ID: f6ff265a45c6b06c28b6

                      *** Welcome to pfSense 2.6.0-RELEASE (amd64) on firewall ***

                      WAN (wan) -> igb0 -> v4/DHCP4: 99.246.abc.def/23
                      v6/DHCP6: 2607:f798:804:90:3899:8d05:1234.abcd/128
                      LAN (lan) -> igb1 -> v4: 172.16.0.1/24
                      v6/t6: 2607:fea8:4c82:5900:4262:31ff:1234.abc1/64
                      VLAN3_GUEST_WIFI (opt1) -> igb1.3 -> v4: 172.16.3.1/24
                      v6/t6: 2607:fea8:4c82:5903:4262:31ff:1234.abc2/64
                      TEST (opt2) -> igb2 -> v4: 172.16.4.1/24
                      v6/t6: 2607:fea8:4c82:5904:4262:31ff:1234.abc3/64
                      CISCO (opt3) -> igb3 -> v4: 192.168.37.0/31
                      v6/t6: 2607:fea8:4c82:5907:4262:31ff:1234.abc4/64
                      OPENVPN (opt4) -> ovpns1 -> v4: 172.16.255.1/24
                      v6: 2607:fea8:4c82:59ff::1/64

                      1. Logout (SSH only) 9) pfTop
                      2. Assign Interfaces 10) Filter Logs
                      3. Set interface(s) IP address 11) Restart webConfigurator
                      4. Reset webConfigurator password 12) PHP shell + pfSense tools
                      5. Reset to factory defaults 13) Update from console
                      6. Reboot system 14) Disable Secure Shell (sshd)
                      7. Halt system 15) Restore recent configuration
                      8. Ping host 16) Restart PHP-FPM
                      9. Shell

                      Enter an option:

                      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
                      • F
                        ftarz
                        last edited by

                        2c9312f5-1be0-42f0-82b9-37c99c93416b-image.png

                        I only keep zipping files since this webpage doesn't accept my native uploads. The screenshots have to be less than 2MB or they get rejected. The only way I could get the screenshot that small was to make it a PDF file which isn't accepted. Saving it as a .BMP or .JPG the file was just over 2MB and wasn't accepted.

                        Frank

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