I can't see how maximum states is linked to bandwidth.  They should operate exactly the same until a threshold condition is reached.

@ghulands: This looks to be the issue. Strange. Your first post doesn't mention any openvpn usage. More strange : using openvpn myself - and the resolver, I didn't saw any issues. But : after an update, when all is ok, I always reboot the system my self to see if it comes up fine by itself. So, if there was an issue, I never saw it.

Reinstalled the pfsenses with zfs mirroring today. Switched the SATA Bios Config back from softraid to AHCI and destroyed the softraid config on the HDDs. Everything is ok. Is there any monitoring or messaging if one drive fails (wigget, mail, or something else)?

My Pleasure, glad you were able to get your users working.

@KOM: Yes, interfaces will usually need to be remapped but I thought you already knew that from your first post. I did.  It's just that the hardware looked so similar…...  :)

Is that the full install on a CF card or Nano? What exact image? A 4GB card should be fine, on that box especially. Does it show any valid devices if you type ? at that prompt? Did it not come with a HD? Are you installing to that? Steve

I´ve updated yesterday to 2.4.2-RELEASE-p1 (amd64) built on Tue Dec 12 13:45:26 CST 2017 FreeBSD 11.1-RELEASE-p7 . Now I have DNS Problems. I´ve worked with Backups und, now, I´ve set pfsense back to factory defaults -  still DNS Problems. If I do not use e.g. 192.168.1.1 in my devices but use a DNS Server like 8.8.8.8 - internet works. Please note: The problem exists directly after "factory defaults" - without any special settings… I consider to install an older version of pfsense? Thank you Kohji [image: dns.JPG] [image: dns.JPG_thumb]

YAY!!!!!! I solved my own problem, posting for anyone else who's interested. I have outbound NAT set to manual, and I had not created any rules for this range. Once i created the rule to NAT traffic from that network, it worked.

Well, I guess that's the best way forward. Thanks for the help.  :)

https://forum.pfsense.org/index.php?topic=145990.0

https://doc.pfsense.org/index.php/PfSense_on_Watchguard_Firebox

After 2.4.3 upgrade ran its course on my APU2 (and I did the upgrade from the console so I could see all the phases), I noticed the dashboard had an error for the NUT package status.  I had noticed that during the upgrade, then NUT package was referenced (although I didn't record the details).  After a bit more looking around, I found that the NUT processes weren't running.  An additional clean reboot was all that was needed to bring everything back to normal.

@anttechs search for one of the many recent posts talking about being unable to update packages to find how to manually bootstrap the package process. @pwilliz did you try with at lower case "y"?  It could be that it was coded to only proceed if the input matched just the lower case y suggested and otherwise aborts.  As for the GUI, it can only show you the first phase of an update, until the beginning of the initial reboot.  In 2.4.3, alot goes on after that and may take a while depending on your hardware and packages.  Generally a lot of patience is recommended using the GUI route.  Similarly for an SSH initiated upgrade.  Doing the upgrades from the console, you can watch all the progress.  I also found for  the 2.4.3 upgrade I had to do an additional reboot to get my package (NUT) working properly.

As additional info,  I've spotted /usr/local/etc/rd.d/microcode_update:  exec_format_error Oops!

https://forum.pfsense.org/index.php?action=search

Which bios version do you have? There are known problems with latest bios (4.6.x mainline branch) when accessing hard disks: v4.6.x BIOSes need to have MSI disabled, due to signal races causing disk write commands timeouts. Read more at pc engines github page. Maybe your issue is related to this bug?

Well, I am in Sweden, so that might be a reason. There are more fiber here than blonde girls…