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!

@drkt@feddit.dk
creator
link
fedilink
English
410M

I honestly thought only paid users could use the official forums…

I’ll post it there, too! Thank you

@AtariDump@lemmy.world
link
fedilink
English
0
edit-2
10M

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.dk
creator
link
fedilink
English
110M

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

Create a post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

  • 1 user online
  • 126 users / day
  • 421 users / week
  • 1.16K users / month
  • 3.85K users / 6 months
  • 1 subscriber
  • 3.68K Posts
  • 74.2K Comments
  • Modlog