To enable full core dumps edit /etc/pfSense-ddb.conf set the kdb.enter.default script line to:
script kdb.enter.default=bt ; show registers ; dump ; reset
Reboot.
Check: sysctl debug.ddb.scripting.scripts make sure it shows the above line.
If you can test a panic: sysctl debug.kdb.panic=1
That will immediately panic the kernel and should generate a full core file.
SWAP is usually double the RAM size so you might not have enough space depending on the usage.
You need to policy route clients via the VPN gateway. So first add static leases for the clients so they always have the same IP addresses. Or if you have different subnets for those clients just policy route all traffic from the subnet.
While this is an old topic, for anyone struggling to get Huawei modem to connect in CDC ECM mode using NDISUP command, the problem is it will ignore those commands sent to cuX serial devices. They need to be sent using the WDM interface, which Linux exposes as cdc-wdmX, but FreeBSD does not.
A workaround is to use a usbconfig command and send that command directly to the device. I explained my findings here: https://dawidwrobel.com/journal/initializing-lte-modem-using-raw-usb-communication/
But for regular home use, or even small business use, why pay that money? Unless it would otherwise change frequently and create regular interruptions, it really doesn't matter.
@borjaevo Perhaps a long shot, but which port is pfsense connected to on the modem? Sometimes in Bridge Mode it's only one of the ports that provide internet, likely port 1.
You can speed up mounting root by changing the value of kern.cam.boot_delay in a custom loader value. But some systems require that delay to allow the root device to become active.
The WAN setup should be quick unless it's waiting for something. Usually that's DHCP but not if it's set static. Do you have it set to dhcpv6 with no v6 server present perhaps?
You can try to resolve those fqdns as an alias and use that in policy routing. However there's a good chance they resolve to numerous IP addresses. Especially for something like that where anonymising the traffic may be important. They may6 not respond to ping but they do resolve. YMMV!
@stephenw10 just saw that thx,
"By default, the M.2 SATA drive will then be the first drive recognized by pfSense" that's good :)
Thanks for your help!
@stephenw10
Thanks for looking at this and helping me out, when i restarted the states, and toggled some firewall rules after testing with packet capture, it just randomly started working.
ive rebooted a couple times and changed things around and it seems to be good for now, not sure what caused the issue however, but i think i should be good now.
Okay, thanks for the idea. initially, I tried to add a path to the router itself, but I did not find such an opportunity. I'll try your idea tomorrow. Thanks for the quick replies, have a nice evening!)
It is an interesting problem sure - but its not pfsesnse manipulating your location info ;) I wish it was that simple - then I could easy use my pc for making bets vs having to do it on my phone ;)
Given I do not really mess with my firewall much, this should be stable for a while as long as I do not change any hardware. It would be neat if the NDI did not change with simple hardware changes. I get it, but man alive, I hope I never have to change anything. Time will tell.
Cheers,
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.