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.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.
    • Gamienator 0G
      Gamienator 0
      last edited by

      Hello everyone,
      first I want to apologize: Not only that I'm not an native english speaker, but second: I still can't unterstand IPv6 completly. Now watching for hours different teaching videos about v6, it's not 100% clear how v6 should be probaly setup.

      For my setup: I'm here in Germany and use a Docsis Vodafone connection. The hardware from my provider supports bridge mode and is activated. Now with different Dual-Stack tutorials (which I booked and before applying pfsense worked) I have not the situation, that my WAN and LAN adapter received an v6 Adress, but none of my clients. I'll share you my current settings. It would be really great if some one could help me figure out how to set it up and still use only my internal PiHole as DNS resolver.

      In addition, WAN and LAN prefix is different:

      8cc292be-29f0-4f6b-b304-ed3002228ab8-image.png

      8ecc405c-499f-4389-a65d-f15c3cf55ca9-image.png

      47f29537-dae3-4963-929a-d7203fea4ac9-image.png

      cea28339-12d7-4379-8da5-37bae7e2e612-image.png

      a7107a42-5094-4a26-ac5b-15ffa7c5ec53-image.png

      Thanks in advance for your help!

      Cheers
      Gamie

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

        The configuration seems OK, but I don't have Do not wait for a RA selected and you might want to select Do not allow PD/Address release, though that wouldn't affect your problem..

        Can you do a packet capture on your LAN, filtering on ICMP6 and on WAN for DHCPv6. The WAN side may be tricky, if you don't have a managed switch configured for port monitoring. You'll want to capture the DHCPv6 sequence. What you could try is to disconnect the WAN cable, boot up pfsense and then plug the cable in, with Packet Capture running. On the LAN side, you're looking for the Router Advertisements and Solicitations. However, those happen frequently and are easy to 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...

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

          @jknott Alright :) Thanks for the answer. Here are the capture of WAN:

          15:51:40.034723 IP6 2a02:1234:5678:1::1 > ff02::1:ffc8:7d9a: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:651d:770:97c8:7d9a, length 32
          15:51:40.241735 IP6 2a02:1234:5678:1::1 > ff02::1:ffc8:6aca: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:7d16:33bb:c8:6aca, length 32
          15:51:40.281949 IP6 2a02:1234:5678:1::1 > ff02::1:ffc8:f5ca: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:7d16:33bb:c8:f5ca, length 32
          15:51:40.298460 IP6 2a02:1234:5678:1::1 > ff02::1:ff09:f84b: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:101:9000:f809:f84b, length 32
          15:51:40.332949 IP6 2a02:1234:5678:1::1 > ff02::1:ffe4:5aaf: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:5990:d2a8:dde4:5aaf, length 32
          15:51:40.532858 IP6 2a02:1234:5678:1::1 > ff02::1:ff19:f888: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:b462:4710:3f19:f888, length 32
          15:51:40.582739 IP6 2a02:1234:5678:1::1 > ff02::1:ffe2:288: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:c5db:7e8b:f9e2:288, length 32
          15:51:40.609196 IP6 2a02:1234:5678:1::1 > ff02::1:ffde:fbe5: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:70e0:433f:bbde:fbe5, length 32
          15:51:40.760668 IP6 2a02:1234:5678:1::1 > ff02::1:ffc3:42fe: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:155b:48cf:a6c3:42fe, length 32
          15:51:41.155847 IP6 2a02:1234:5678:1::1 > ff02::1:ff9a:ffed: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:39e7:ad74:a39a:ffed, length 32
          15:51:41.252784 IP6 2a02:1234:5678:1::1 > ff02::1:ffe4:4238: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:5990:d2a8:dde4:4238, length 32
          15:51:41.338605 IP6 2a02:1234:5678:1::1 > ff02::1:fff1:ca2c: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:65f7:ce31:fdf1:ca2c, length 32
          15:51:41.378617 IP6 2a02:1234:5678:1::1 > ff02::1:ff85:40e: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:6962:8c8a:9e85:40e, length 32
          15:51:41.390682 IP6 2a02:1234:5678:1::1 > ff02::1:ff85:1306: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:6962:8c8a:9e85:1306, length 32
          15:51:41.397276 IP6 2a02:1234:5678:1::1 > ff02::1:ff09:f84b: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:101:9000:f809:f84b, length 32
          15:51:41.408277 IP6 2a02:1234:5678:1::1 > ff02::1:ff5a:4351: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:e0f2:c141:8f5a:4351, length 32
          15:51:41.409508 IP6 2a02:1234:5678:1::1 > ff02::1:ff5a:5751: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:e0f2:c141:8f5a:5751, length 32
          15:51:41.416202 IP6 2a02:1234:5678:1::1 > ff02::1:ff85:7406: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:6962:8c8a:9e85:7406, length 32
          15:51:41.595981 IP6 2a02:1234:5678:1::1 > ff02::1:ff09:f84b: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:101:9000:f809:f84b, length 32
          15:51:41.717632 IP6 2a02:1234:5678:1::1 > ff02::1:ff52:c13f: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:15de:b8d6:c952:c13f, length 32
          15:51:41.720936 IP6 2a02:1234:5678:1::1 > ff02::1:ffd9:b31d: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:6db6:6697:3dd9:b31d, length 32
          15:51:41.738577 IP6 2a02:1234:5678:1::1 > ff02::1:ff91:299a: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:710c:8e18:f91:299a, length 32
          15:51:42.086933 IP6 2a02:1234:5678:1::1 > ff02::1:ffe4:eaec: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:5990:d2a8:dde4:eaec, length 32
          15:51:42.148337 IP6 2a02:1234:5678:1::1 > ff02::1:ff87:d857: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:680f:d10d:c887:d857, length 32
          15:51:42.355096 IP6 2a02:1234:5678:1::1 > ff02::1:ffc4:431f: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:593:7039:d0c4:431f, length 32
          15:51:42.394007 IP6 2a02:1234:5678:1::1 > ff02::1:ff54:7db5: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:f5fc:5d3f:5c54:7db5, length 32
          15:51:42.395608 IP6 2a02:1234:5678:1::1 > ff02::1:ff54:7e01: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:f5fc:5d3f:5c54:7e01, length 32
          15:51:42.397135 IP6 2a02:1234:5678:1::1 > ff02::1:ff54:7e28: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:f5fc:5d3f:5c54:7e28, length 32
          15:51:42.420852 IP6 2a02:1234:5678:1::1 > ff02::1:ff54:f228: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:f5fc:5d3f:5c54:f228, length 32
          15:51:42.422641 IP6 2a02:1234:5678:1::1 > ff02::1:ff54:f1b5: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:f5fc:5d3f:5c54:f1b5, length 32
          15:51:42.448187 IP6 2a02:1234:5678:1::1 > ff02::1:ff54:f201: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:f5fc:5d3f:5c54:f201, length 32
          15:51:42.561520 IP6 fe80::217:10ff:fe9a:7725 > ff02::1: ICMP6, router advertisement, length 160
          15:51:42.579513 IP6 2a02:1234:5678:1::1 > ff02::1:ff04:9b25: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:1ddd:7a10:f304:9b25, length 32
          15:51:42.751577 IP6 2a02:1234:5678:1::1 > ff02::1:ff5b:d9fe: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:3d32:9cf4:335b:d9fe, length 32
          15:51:42.854233 IP6 2a02:1234:5678:1::1 > ff02::1:fff7:5241: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:6427:ca77:36f7:5241, length 32
          15:51:43.051311 IP6 2a02:1234:5678:1::1 > ff02::1:ff92:12fe: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:5d7d:1765:6092:12fe, length 32
          15:51:43.325738 IP6 2a02:1234:5678:1::1 > ff02::1:ffc8:b6c2: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:7d16:33bb:c8:b6c2, length 32
          15:51:43.329316 IP6 2a02:1234:5678:1::1 > ff02::1:ffc8:9dc2: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:7d16:33bb:c8:9dc2, length 32
          15:51:43.394090 IP6 2a02:1234:5678:1::1 > ff02::1:ff82:286c: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:e019:da63:c382:286c, length 32
          15:51:43.630158 IP6 2a02:1234:5678:1::1 > ff02::1:ffe4:e639: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:5990:d2a8:dde4:e639, length 32
          15:51:43.643076 IP6 2a02:1234:5678:1::1 > ff02::1:ff1e:42c8: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:59aa:9df3:d61e:42c8, length 32
          15:51:43.656546 IP6 2a02:1234:5678:1::1 > ff02::1:ff04:9261: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:1ddd:7a10:f304:9261, length 32
          15:51:43.658551 IP6 2a02:1234:5678:1::1 > ff02::1:ff1e:42d0: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:59aa:9df3:d61e:42d0, length 32
          15:51:43.660665 IP6 2a02:1234:5678:1::1 > ff02::1:ff55:f419: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:615e:efb3:6e55:f419, length 32
          15:51:43.666333 IP6 2a02:1234:5678:1::1 > ff02::1:ff09:f84b: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:101:9000:f809:f84b, length 32
          15:51:43.694301 IP6 2a02:1234:5678:1::1 > ff02::1:ff2b:fac8: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:3939:26ea:e02b:fac8, length 32
          15:51:43.789684 IP6 2a02:1234:5678:1::1 > ff02::1:ffa2:9389: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:30d2:f91b:36a2:9389, length 32
          15:51:43.865314 IP6 2a02:1234:5678:1::1 > ff02::1:ffef:2bcb: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:283c:3037:a2ef:2bcb, length 32
          15:51:43.906078 IP6 2a02:1234:5678:1::1 > ff02::1:ff20:6563: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:adc8:f5af:b820:6563, length 32
          15:51:43.967339 IP6 2a02:1234:5678:1::1 > ff02::1:ffa2:fd5e: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:30d2:f91b:36a2:fd5e, length 32
          15:51:44.009279 IP6 2a02:1234:5678:1::1 > ff02::1:ffdc:fa30: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:493f:332b:b1dc:fa30, length 32
          15:51:44.071467 IP6 2a02:1234:5678:1::1 > ff02::1:ff1e:1d81: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:59aa:9df3:d61e:1d81, length 32
          15:51:44.121241 IP6 2a02:1234:5678:1::1 > ff02::1:ff18:6a06: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:2dbe:c345:bb18:6a06, length 32
          15:51:44.167518 IP6 2a02:1234:5678:1::1 > ff02::1:ffe2:a408: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:c5db:7e8b:f9e2:a408, length 32
          15:51:44.209147 IP6 2a02:1234:5678:1::1 > ff02::1:ff5a:5aac: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:e0f2:c141:8f5a:5aac, length 32
          15:51:44.331446 IP6 2a02:1234:5678:1::1 > ff02::1:ff8b:83cd: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:74f0:1a07:e8b:83cd, length 32
          15:51:44.418538 IP6 2a02:1234:5678:1::1 > ff02::1:ff04:791a: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:1ddd:7a10:f304:791a, length 32
          15:51:44.464565 IP6 2a02:1234:5678:1::1 > ff02::1:ff4f:f3e0: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:5f5:9fc0:194f:f3e0, length 32
          15:51:44.692042 IP6 2a02:1234:5678:1::1 > ff02::1:ff92:72bb: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:5d7d:1765:6092:72bb, length 32
          15:51:44.693401 IP6 2a02:1234:5678:1::1 > ff02::1:ff92:4bbb: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:5d7d:1765:6092:4bbb, length 32
          15:51:44.710886 IP6 2a02:1234:5678:1::1 > ff02::1:ff92:66bb: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:5d7d:1765:6092:66bb, length 32
          15:51:44.897112 IP6 2a02:1234:5678:1::1 > ff02::1:ff92:7643: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:5d7d:1765:6092:7643, length 32
          15:51:45.289768 IP6 2a02:1234:5678:1::1 > ff02::1:ff81:42af: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:54d1:ef54:e681:42af, length 32
          15:51:45.414630 IP6 2a02:1234:5678:1::1 > ff02::1:ff98:43ed: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:1c18:3f12:8798:43ed, length 32
          15:51:45.468756 IP6 2a02:1234:5678:1::1 > ff02::1:ff52:e9ed: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:15de:b8d6:c952:e9ed, length 32
          15:51:45.601518 IP6 2a02:1234:5678:1::1 > ff02::1:ff37:7a75: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:7c7a:a9e4:9437:7a75, length 32
          15:51:45.609637 IP6 2a02:1234:5678:1::1 > ff02::1:ff37:79b5: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:7c7a:a9e4:9437:79b5, length 32
          15:51:45.682870 IP6 2a02:1234:5678:1::1 > ff02::1:ff5a:87c6: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:e0f2:c141:8f5a:87c6, length 32
          15:51:45.725487 IP6 2a02:1234:5678:1::1 > ff02::1:ff5a:95c6: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:e0f2:c141:8f5a:95c6, length 32
          15:51:45.739616 IP6 2a02:1234:5678:1::1 > ff02::1:ffde:ce: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:35bb:aa88:e7de:ce, length 32
          15:51:45.849996 IP6 fe80::217:10ff:fe9a:7725 > ff02::1: ICMP6, router advertisement, length 160
          15:51:45.920837 IP6 2a02:1234:5678:1::1 > ff02::1:ff81:d721: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:54d1:ef54:e681:d721, length 32
          15:51:45.944443 IP6 2a02:1234:5678:1::1 > ff02::1:ff08:7347: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:6d55:81fa:108:7347, length 32
          15:51:45.948408 IP6 2a02:1234:5678:1::1 > ff02::1:ff08:73bf: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:6d55:81fa:108:73bf, length 32
          15:51:46.012413 IP6 fe80::249d:e9ff:fe4d:f771.60502 > 2001:500:9f::42.53: UDP, length 32
          15:51:46.012469 IP6 fe80::249d:e9ff:fe4d:f771.44287 > 2001:500:1::53.53: UDP, length 32
          15:51:46.082700 IP6 fe80::249d:e9ff:fe4d:f771.34125 > 2001:503:d414::30.53: UDP, length 40
          15:51:46.191341 IP6 2a02:1234:5678:1::1 > ff02::1:ff5b:21aa: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:a4ca:9a92:5f5b:21aa, length 32
          15:51:46.191360 IP6 2a02:1234:5678:1::1 > ff02::1:ff06:3d78: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:9ccd:758a:2806:3d78, length 32
          15:51:46.278844 IP6 2a02:1234:5678:1::1 > ff02::1:fff1:3fc2: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:65f7:ce31:fdf1:3fc2, length 32
          15:51:46.324881 IP6 2a02:1234:5678:1::1 > ff02::1:ff09:f84b: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:101:9000:f809:f84b, length 32
          15:51:46.401840 IP6 fe80::249d:e9ff:fe4d:f771.62289 > 2001:500:1::53.53: UDP, length 32
          15:51:46.401887 IP6 fe80::249d:e9ff:fe4d:f771.39923 > 2001:500:9f::42.53: UDP, length 32
          15:51:46.461757 IP6 fe80::249d:e9ff:fe4d:f771.64869 > 2001:503:d414::30.53: UDP, length 40
          15:51:46.544716 IP6 fe80::249d:e9ff:fe4d:f771.53638 > 2610:160:11:11::80.53: UDP, length 44
          15:51:46.589367 IP6 2a02:1234:5678:1::1 > ff02::1:ff9a:d5e6: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:39e7:ad74:a39a:d5e6, length 32
          15:51:46.721404 IP6 2a02:1234:5678:1::1 > ff02::1:ffef:9ae2: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:283c:3037:a2ef:9ae2, length 32
          15:51:46.759009 IP6 2a02:1234:5678:1::1 > ff02::1:ff9a:bccc: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:39e7:ad74:a39a:bccc, length 32
          15:51:46.770578 IP6 2a02:1234:5678:1::1 > ff02::1:ff54:72bb: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:f5fc:5d3f:5c54:72bb, length 32
          15:51:46.773737 IP6 2a02:1234:5678:1::1 > ff02::1:ff54:4bbb: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:f5fc:5d3f:5c54:4bbb, length 32
          15:51:46.786103 IP6 2a02:1234:5678:1::1 > ff02::1:ff9a:2202: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:39e7:ad74:a39a:2202, length 32
          15:51:46.789313 IP6 2a02:1234:5678:1::1 > ff02::1:ff2b:b921: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:3939:26ea:e02b:b921, length 32
          15:51:46.792723 IP6 2a02:1234:5678:1::1 > ff02::1:ff54:66bb: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:f5fc:5d3f:5c54:66bb, length 32
          15:51:46.800778 IP6 fe80::249d:e9ff:fe4d:f771.50289 > 2001:503:c27::2:30.53: UDP, length 32
          15:51:46.813754 IP6 2a02:1234:5678:1::1 > ff02::1:ff54:7643: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:f5fc:5d3f:5c54:7643, length 32
          15:51:46.825954 IP6 2a02:1234:5678:1::1 > ff02::1:ff9a:8dc6: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:39e7:ad74:a39a:8dc6, length 32
          15:51:46.921201 IP6 fe80::249d:e9ff:fe4d:f771.28492 > 2610:160:11:11::80.53: UDP, length 44
          15:51:47.037234 IP6 2a02:1234:5678:1::1 > ff02::1:ff9a:496f: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:39e7:ad74:a39a:496f, length 32
          15:51:47.179449 IP6 fe80::249d:e9ff:fe4d:f771.29090 > 2001:503:c27::2:30.53: UDP, length 32
          15:51:47.189308 IP6 2a02:1234:5678:1::1 > ff02::1:ff55:9602: ICMP6, neighbor solicitation, who has 2a02:1234:5678:1:615e:efb3:6e55:9602, length 32
          

          and here for LAN

          15:53:12.632791 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 28
          15:53:12.633626 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 28
          15:53:12.633980 IP6 fe80::c00:d56:4e09:558e.49742 > ff02::1:3.5355: UDP, length 22
          15:53:13.043970 IP6 fe80::c00:d56:4e09:558e.49742 > ff02::1:3.5355: UDP, length 22
          15:53:13.632752 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 28
          15:53:13.633548 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 28
          15:53:14.651074 IP6 fe80::bfac:710d:5b49:72b1.49254 > 2a02:908:4c12:39a0:78b7:d2ff:fe27:9e86.853: tcp 0
          15:53:16.267258 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 39
          15:53:16.267424 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 39
          15:53:16.267939 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 39
          15:53:16.268155 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 39
          15:53:16.268399 IP6 fe80::c00:d56:4e09:558e.50935 > ff02::1:3.5355: UDP, length 33
          15:53:16.268458 IP6 fe80::c00:d56:4e09:558e.61918 > ff02::1:3.5355: UDP, length 33
          15:53:16.679316 IP6 fe80::c00:d56:4e09:558e.61918 > ff02::1:3.5355: UDP, length 33
          15:53:16.679344 IP6 fe80::c00:d56:4e09:558e.50935 > ff02::1:3.5355: UDP, length 33
          15:53:17.267398 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 39
          15:53:17.267431 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 39
          15:53:17.268239 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 39
          15:53:17.268342 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 39
          15:53:17.477970 IP6 :: > ff02::2: ICMP6, router solicitation, length 8
          15:53:17.478304 IP6 fe80::1:1 > ff02::1: ICMP6, router advertisement, length 136
          15:53:17.486572 IP6 fe80::9a06:3cff:fe2a:e642 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
          15:53:17.488238 IP6 fe80::4c39:8ff:fe1f:4f6d > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
          15:53:18.038370 IP6 fe80::9a06:3cff:fe2a:e642 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
          15:53:18.296253 IP6 fe80::4c39:8ff:fe1f:4f6d > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
          15:53:23.040214 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 39
          15:53:23.040587 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 39
          15:53:23.040890 IP6 fe80::c00:d56:4e09:558e.50167 > ff02::1:3.5355: UDP, length 33
          15:53:23.040929 IP6 fe80::c00:d56:4e09:558e.61253 > ff02::1:3.5355: UDP, length 33
          15:53:23.041243 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 39
          15:53:23.041437 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 39
          15:53:23.450606 IP6 fe80::c00:d56:4e09:558e.50167 > ff02::1:3.5355: UDP, length 33
          15:53:23.450628 IP6 fe80::c00:d56:4e09:558e.61253 > ff02::1:3.5355: UDP, length 33
          15:53:24.039632 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 39
          15:53:24.040487 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 39
          15:53:24.040767 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 39
          15:53:24.041441 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 39
          15:53:25.291922 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 39
          15:53:25.292214 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 39
          15:53:25.292480 IP6 fe80::c00:d56:4e09:558e.65426 > ff02::1:3.5355: UDP, length 33
          15:53:25.292655 IP6 fe80::c00:d56:4e09:558e.51755 > ff02::1:3.5355: UDP, length 33
          15:53:25.292803 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 39
          15:53:25.293006 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 39
          15:53:25.702939 IP6 fe80::c00:d56:4e09:558e.51755 > ff02::1:3.5355: UDP, length 33
          15:53:25.702966 IP6 fe80::c00:d56:4e09:558e.65426 > ff02::1:3.5355: UDP, length 33
          15:53:26.291739 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 39
          15:53:26.291944 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 39
          15:53:26.292582 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 39
          15:53:26.292752 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 39
          15:53:26.641481 IP6 fe80::e2dc:ffff:fef7:32ef.42282 > 2a03:2880:f218:c5:face:b00c:0:7260.80: tcp 0
          15:53:27.675435 IP6 fe80::e2dc:ffff:fef7:32ef.42282 > 2a03:2880:f218:c5:face:b00c:0:7260.80: tcp 0
          15:53:27.915628 IP6 fe80::e2dc:ffff:fef7:32ef > 2a02:908:4c12:39a0:78b7:d2ff:fe27:9e86: ICMP6, neighbor solicitation, who has 2a02:908:4c12:39a0:78b7:d2ff:fe27:9e86, length 32
          15:53:27.915662 IP6 fe80::1:1 > fe80::e2dc:ffff:fef7:32ef: ICMP6, neighbor advertisement, tgt is 2a02:908:4c12:39a0:78b7:d2ff:fe27:9e86, length 24
          15:53:28.892543 IP6 fe80::e2dc:ffff:fef7:32ef.8647 > 2a02:908:4c12:39a0:78b7:d2ff:fe27:9e86.53: UDP, length 40
          15:53:29.464732 IP6 fe80::e2dc:ffff:fef7:32ef.17852 > 2a02:908:4c12:39a0:78b7:d2ff:fe27:9e86.53: UDP, length 43
          15:53:29.705859 IP6 fe80::e2dc:ffff:fef7:32ef.42282 > 2a03:2880:f218:c5:face:b00c:0:7260.80: tcp 0
          15:53:31.718296 IP6 fe80::e2dc:ffff:fef7:32ef > fe80::1:1: ICMP6, neighbor solicitation, who has fe80::1:1, length 32
          15:53:31.718331 IP6 fe80::1:1 > fe80::e2dc:ffff:fef7:32ef: ICMP6, neighbor advertisement, tgt is fe80::1:1, length 24
          15:53:32.968009 IP6 fe80::1:1 > fe80::e2dc:ffff:fef7:32ef: ICMP6, neighbor solicitation, who has fe80::e2dc:ffff:fef7:32ef, length 32
          15:53:33.117647 IP6 fe80::e2dc:ffff:fef7:32ef > fe80::1:1: ICMP6, neighbor advertisement, tgt is fe80::e2dc:ffff:fef7:32ef, length 32
          15:53:41.342891 IP6 fe80::1:1 > ff02::1: ICMP6, router advertisement, length 136
          15:53:41.352374 IP6 fe80::4c39:8ff:fe1f:4f6d > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
          15:53:41.412335 IP6 fe80::4c39:8ff:fe1f:4f6d > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
          15:53:41.467956 IP6 fe80::1:1 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
          15:53:42.267978 IP6 fe80::1:1 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
          15:53:48.636571 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 28
          15:53:48.636863 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 28
          15:53:48.636981 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 28
          15:53:48.637298 IP6 fe80::c00:d56:4e09:558e.62487 > ff02::1:3.5355: UDP, length 22
          15:53:48.637467 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 28
          15:53:48.637645 IP6 fe80::c00:d56:4e09:558e.58898 > ff02::1:3.5355: UDP, length 22
          15:53:49.047384 IP6 fe80::c00:d56:4e09:558e.62487 > ff02::1:3.5355: UDP, length 22
          15:53:49.048272 IP6 fe80::c00:d56:4e09:558e.58898 > ff02::1:3.5355: UDP, length 22
          15:53:49.635921 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 28
          15:53:49.636090 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 28
          15:53:49.637131 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 28
          15:53:49.637332 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 28
          15:53:49.695467 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 28
          15:53:49.695673 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 28
          15:53:49.696206 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 28
          15:53:49.696347 IP6 fe80::c00:d56:4e09:558e.61716 > ff02::1:3.5355: UDP, length 22
          15:53:49.696578 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 28
          15:53:49.696810 IP6 fe80::c00:d56:4e09:558e.63068 > ff02::1:3.5355: UDP, length 22
          15:53:50.106878 IP6 fe80::c00:d56:4e09:558e.61716 > ff02::1:3.5355: UDP, length 22
          15:53:50.106905 IP6 fe80::c00:d56:4e09:558e.63068 > ff02::1:3.5355: UDP, length 22
          15:53:50.695529 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 28
          15:53:50.695855 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 28
          15:53:50.696018 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 28
          15:53:50.696446 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 28
          15:53:57.639865 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 28
          15:53:57.639989 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 28
          15:53:57.640005 IP6 fe80::c00:d56:4e09:558e.61518 > ff02::1:3.5355: UDP, length 22
          15:53:57.640217 IP6 fe80::c00:d56:4e09:558e.59090 > ff02::1:3.5355: UDP, length 22
          15:53:57.640407 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 28
          15:53:57.640581 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 28
          15:53:58.050233 IP6 fe80::c00:d56:4e09:558e.59090 > ff02::1:3.5355: UDP, length 22
          15:53:58.050259 IP6 fe80::c00:d56:4e09:558e.61518 > ff02::1:3.5355: UDP, length 22
          15:53:58.639805 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 28
          15:53:58.640050 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 28
          15:53:58.640319 IP6 fe80::c00:d56:4e09:558e.5353 > ff02::fb.5353: UDP, length 28
          
          
          JKnottJ 1 Reply Last reply Reply Quote 0
          • JKnottJ
            JKnott @Gamienator 0
            last edited by

            @gamienator-0

            Sorry, I guess I wasn't clear enough. I was looking for the capture files, as produced by Packet Capture or Wireshark. I then download and examine them in Wireshark. For example, I can see a router solicitation and advertisement, but I can't see what's actually in the packet. Wireshark will allow me to do that.

            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

              Oh sorry, I really thought you need the text only. The Files can be found here: Downloads.zip

              Cheers,
              Gamie

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

                @gamienator-0

                I guess you don't have much experience with packet captures. When you do that, you generally specify what you're looking for. For example, I mentioned DHCPv6 on the WAN and ICMP6 on the LAN side. When you use Packet Capture, there are boxes where you say, for example, whether IPv4 or IPv6, protocol and more. Use those to provide only the needed info. For example, most of those 2 captures were IPv4, which is irrelevant to what your problem is. Here's a screen capture of the LAN side, which will capture only ICMP6:

                ddbc7ed8-bf95-4805-af44-5fac9065603a-image.png

                And here is the WAN side. Notice I specified both IPv6 and the port number, though I probably didn't have to specify IPv6, as that port shouldn't be used for anything on IPv4:

                37d98777-fa4b-4103-8630-8fc87ab3b274-image.png

                It wasn't necessary to specify the addresses in either.

                Once you have the capture, you can download it to your computer and post here.

                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 2 Replies Last reply Reply Quote 0
                • Gamienator 0G
                  Gamienator 0 @JKnott
                  last edited by

                  @jknott Heyho,
                  like you mentioned, WAN can be tricky, the first try was without any captured Packages :(

                  Here is the LAN Capture: I'll try the WAN capture ASAP

                  LANCapture.zip

                  1 Reply Last reply Reply Quote 0
                  • 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.