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

    WAN_DHCP6 IP on 2.6.0

    Scheduled Pinned Locked Moved IPv6
    6 Posts 3 Posters 1.1k 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
      metebalci
      last edited by

      I think the IP of WAN_DHCP6 was shown correct on routing/gateways on 2.5.2, but now on 2.6 I see it is showing the link-local IP (fe80). There is no problem with IPv6 connectivity. Is this a bug or I have something misconfigured ?

      JKnottJ 1 Reply Last reply Reply Quote 0
      • T
        Tzvia
        last edited by

        I see it with an IPV6 address and don't see a lot of other complaints so I don't think it's a bug affecting many users. And as you can see, it isn't used for IPV6 connectivity between the clients and internet, but would be used for a road warrior ipv6 vpn setup as the WAN IP. If you haven't tried rebooting the PFSense box, that may resolve that. Or you may have to tweak your WAN IPV6 settings if you need it to have an IPV6 IP for VPN access to your network.

        Tzvia

        Current build:
        Hunsn/CWWK Pentium Gold 8505, 6x i226v 'micro firewall'
        16 gigs ram
        500gig WD Blue nvme
        Using modded BIOS (enabled CSTATES)
        PFSense 2.72-RELEASE
        Enabled Intel SpeedShift
        Snort
        PFBlockerNG
        LAN and 5 VLANS

        M 1 Reply Last reply Reply Quote 0
        • M
          metebalci @Tzvia
          last edited by

          @tzvia I do not need VPN at the moment and it does not affect anything like you said but reboot etc. does not change it, I still see the link-local IP. The routing table also shows the default IPv6 gateway IP as the link local IP, so it is not a problem of the widget or UI alone. AFAIK this is not a problem for routing but if this is not a bug then I think there is a need to be able to select what to see on the widget, link-local, public etc. For example, status > interfaces screen shows both of them correct.

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

            @metebalci

            Normally, the link local address is used for routing and you usually have a global address on the WAN port, but it's not necessary.

            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
            • T
              Tzvia @metebalci
              last edited by

              @metebalci said in WAN_DHCP6 IP on 2.6.0:

              @tzvia I do not need VPN at the moment and it does not affect anything like you said but reboot etc. does not change it, I still see the link-local IP. ...

              I stand corrected- I do see under ROUTING/GATEWAYS, the fe80 link local, but on the DASHBOARD/INTERFACES, it displays the IPV6 address of the WAN interface- which I am assuming is a /128 and so has nothing to do with routing. Don't see an issue here, and don't remember what GATEWAYS showed in 2.52...

              Tzvia

              Current build:
              Hunsn/CWWK Pentium Gold 8505, 6x i226v 'micro firewall'
              16 gigs ram
              500gig WD Blue nvme
              Using modded BIOS (enabled CSTATES)
              PFSense 2.72-RELEASE
              Enabled Intel SpeedShift
              Snort
              PFBlockerNG
              LAN and 5 VLANS

              M 1 Reply Last reply Reply Quote 0
              • M
                metebalci @Tzvia
                last edited by

                @tzvia yes Interfaces widget shows the public one. I was using Gateways just as a quick summary for Interfaces -obviously bad idea- because there are many VLANs, much better idea seems to be a second Interfaces widget showing only the WAN interface so that solves my request. I still dont know why I was seeing public IPv6 address as the gateway before but maybe I am confused and remember something else, I dont have 2.5.2 at the moment to check.

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