This has been solved. After calmly yelling at my ISP support for 3 weeks, they finally conceded and admitted that this is their problem and not mine. It will be fixed soon, maybe. Probably not, but hopefully. I’m not hopeful, but maybe it might be.

=========================================

Hello! My pfsense box has seemingly decided to attain sentience and its first action was to spite its master. I had a pending update for 2.7.0-RELEASE but now the system is running 2.7.0 - seemingly having updated itself. The problem is that there seems to be a problem retrieving an IP from my ISPs DHCP6 server on this version. https://u.drkt.eu/zVDJKb.png

My ISP has double-checked for me, and they are handing out an IP that should look like 2a05:f6c7:8321::/48 and this is consistent with what I expect it to look like.

Going through my pfsense settings, nothing seems to have changed from the settings my ISP require for IPv6 to work.

My pfsense box is attached directly to their fiber modem, communicating on vlan 101

This is set up as follows (these links may not work if you use IPv6) redact

If I run tcpdump and then restart the gateway, I get these packets

tcpdump -ni alc0.101 -c 1000 -U -w - '((ip6)) and ((not vlan))'

redact

Any help or guidance is appreciated!

  • AtariDump@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    edit-2
    11 months ago

    Also, it’s not a great answer, but look at switching to OPNSense.

    I did and had a LOT less issues with my firewall when I did.

    • drkt@feddit.dkOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      11 months ago

      I did switch and had way more problems… And still no IPv6, either.