Netgate units use the "factory" image, VMs use the "Community" image. Those images are built sequentially, so you just caught it in-between I imagine.

Ok I'll see if I can recreate something in native FreeBSD, although I'm not familiar with FreeBSD outside of pfSense

More information; 2.4 / FreeBSD 11.0 reliably crashes when more than 3 virtual network interfaces are added.

Configuration used:

name = 'firewall' bios = "ovmf" uuid="11d1366c-40e2-43b2-83be-52cfe0c6542d" builder = 'hvm' memory = '2024' vcpus = 4 disk = ['file:/dev/hypervisor-local/firewall-system,xvda,w'] vif = [ 'mac=00:16:3e:e5:68:fd, bridge=wan0, script=vif-openvswitch-no-offload, type=vif', 'mac=00:16:3e:e8:20:db, bridge=lan10, script=vif-openvswitch-no-offload, type=vif', #'mac=00:16:3e:ee:02:44, bridge=lan20, script=vif-openvswitch-no-offload, type=vif', #'mac=00:16:3e:e1:03:f1, bridge=lan30, script=vif-openvswitch-no-offload, type=vif', 'mac=00:16:3e:e2:30:44, bridge=lan40, script=vif-openvswitch-no-offload, type=vif' ] boot = 'c' serial='pty'

The VIF lines define network interfaces, when using the 3 as described in this configuration pfSense works, when adding one or more beyond that, it always crashes. With 4 it generates a panic and dump, with 5 it just panics and hangs in kdb with db>.

FIXED but not really..

On every reboot and daily update we lose ipv6… I just follow steps below.. Its fixed in like 20 secs.. (bug)

on wan set to NONE for dhcpv6.. apply then exit

then go back on wan set to dhcp6

fixed 10/10 score

Looks to be the NUT widget (from the forum) - removed, and stable now for ~ 18 hours (before 2-3 hours was a stretch).

Thanks!

Yes, that is the offending options/checkbox.

I thinks I've found the reason. It was faulty flash drive, it was returning read/write operations.

thanks
. that thread was helpful. i will see what my isp can do for me. two redundant channels would also be helpful

OK, I take it back … my script only works sometimes, not consistently it seems ... :(.

It is frustrating - every reboot I have to go and unplug and re-plug the USB adapter, then press enter. Any suggestions are welcome!

Thanks.

I did, yes. Once as part of the update process and another time after the update was done.

Can I suggest a warning on the bridge setup page at a minimum? The ipv6 issue is not obvious at all. I had been running this config for over a year without realizing why my internet kept breaking so particularly…

The only way the rule could end up on LAN is if you selected LAN for the interface where the VPN should bind/listen. That's a manual option you would have had to set in the wizard. The code uses the selected interface specifically and does not make any assumptions about the interface name.

I'm not sure what's going on here, but while swapping modems this afternoon (upgraded to a DOCSIS 3.1 modem), I had my pfSense WAN interface not connected for a bit. After reconnecting it, and just now looking in the DNS Resolver logs, I have extended the log view up to 5000 lines and over 95% of the lines are…

Jul 18 17:30:46 unbound 82208:1 error: can't bind socket: Can't assign requested address for x.x.x.x

or replace the IPv4 address with an IPv6 address. The timestamp is the exact same to the minute, with a variance of 3 seconds over more than 4900 lines. That's some MAJOR log spamming going on while the connection is down.

Maybe it's always done that and I just haven't noticed (I don't tend to look at dns resolver logs often)… but that's pretty severe to be writing over 4900 lines to a log file in just three seconds. Possibly related? If not, please feel free to split this to a new topic.

@mais_um:

If you edit a gateway in System > Routing > Gateways > Edit you have a advanced button, there you can change Latency thresholds; Probe Interval; Alert interval and  other related dpinger stuff.

Is that what you looking for?

yep thats it thanks.

I have the same reboot issue. However, what works for me is the command:

shutdown -r now

This will at the end show some ACPI Errors, but at least it does reboot the box.

Unless "reboot" command get fixed, maybe make a function to use the alternative "shutdown" reboot?

I tried to fiddle with ACPI and power settings in BIOS, but nothing helped. - Newest BIOS is there as well. Halt/Shutdown does work as intended.

I have a different issue with gateway groups and failover, but you should check to see if Sticky Connections is enabled…  It will retain the gateway in use for all past and current connections.  Future ones should revert to highest tier though.  You could always try resetting the state table after Tier 1 comes back up as a test, it should assign to highest tier at that point.