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

    IPv6 NDP Incomplete

    Scheduled Pinned Locked Moved IPv6
    2 Posts 2 Posters 370 Views 2 Watching
    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.
    • S Offline
      smaxwell2
      last edited by

      Hi All,

      I have a problem with pfSense IPv6 and Windows Clients. Apple Devices appear to be working perfectly. So pretty sure my issue lies within my Windows configuration, though I stand to be corrected.

      My ISP provides me IPv6 on the WAN and delegated me a /56

      I have my LAN configured within pfSense to "Track Interface" (WAN)

      The issue is, when a Windows Client is connected, I have IPv6 connectivity for around 30 seconds then my PING (to the Internet - IPv6) drops out for around 20 seconds then comes back again.

      After banging my head against the wall for hours and trying lots of different options. I think I have found the issue, if I click on Diagnostics > NDP Table I can see my Windows Client IPv6 address with a expiry of around 30 seconds, then it changes to (incomplete), my IPv6 PING to the Internet Drops out and then, the whole process happens again.

      I have taken Packet Captures from both pfSense LAN interface and my Windows LAN interface, however unsure what I need to look for here. Any pointers ?

      My Windows clients are protected with Windows Defender for Endpoint, so un-sure if my client side firewall is being too over-protective, I have created an ICMPv6 allow all rule, but that did not make any difference.

      Any pointers ?

      GertjanG 1 Reply Last reply Reply Quote 0
      • GertjanG Online
        Gertjan @smaxwell2
        last edited by

        @smaxwell2 said in IPv6 NDP Incomplete:

        So pretty sure my issue lies within my Windows configuration, though I stand to be corrected.

        Your 'Windows' devices are like mine : you never changed anything in the 'Network' setup of your devices.
        They came with DHCPv4 and DHCPv6 client activated.
        There is/was never a need to change anything.

        @smaxwell2 said in IPv6 NDP Incomplete:

        My ISP provides me IPv6 on the WAN and delegated me a /56

        I have my LAN configured within pfSense to "Track Interface" (WAN

        Like me.
        I assigned prefix ID '0' ion the LAN interface :

        2754f99d-c6dc-4ac1-9a8d-69be1d3187d6-image.png

        And .... I've set up the DHCPv6 server - like the DHCPv4, for my LAN :

        2207d61e-7010-4f74-b7f2-54116f2f5571-image.png

        and since I did this (years ago), all my LAN device that are IPv6 capable receive a IPv6 Lease in the ::2 to ::86 range.

        Because I'm old and stupid, I also gave most of all my device a DHCPv6 Static DUID Lease. This means that all my device always get the same IPv6 GUA.

        C:\Users\Gauche>nslookup diskstation2
        Serveur :   pfSense.bhf.tld
        Address:  2a01:cb19:907:xxxx:yyyy:77ff:fe29:392c
        
        Nom :    diskstation2.brit-hotel-fumel.net
        Addresses:  2a01:cb19:907:xxxx::c2
                  192.168.1.33
        

        I actually never (had to) looked at the NDP table page

        I can see on the DHCP Logs page that IPv4 and IPv6 are getting renewed :

        a167e7a1-58a5-47ea-85d7-c3179191b4d5-image.png

        Btw : I use ISC, not Kea.

        No "help me" PM's please. Use the forum, the community will thank you.
        Edit : and where are the logs ??

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