Hi to all,
I have used pfsense on two apollo lake setups.

My first apollo lake setup was an ASROCK mATX J3455 with two additional NICs and a Draytek VigorNic 132 occupying the expansion slots. I had no problems before the hpet bug. The setup was basic intended for home use. The hpet bug hit me after update and made the system unbootable. After reading the forums, I managed to successfully install (safe mode, loader.conf etc) a fresh 2.4.3 and setup a working firewall. I didn't notice any high CPU usage, but as I wrote it is a basic setup.

I replaced the setup with another apollo lake, an ASROCK J3355 ITX (the VigorNic in the single expansion slot) due to a hardware problem of the previous MOBO. Interestingly, this MOBO was not affected with the hpet bug and installed 2.4.3 normally. Actually what happened was I forgot to enter safe mode but to my surprise the setup didn't freeze and continued. With respect to CPU usage, again I didn't notice any abnormality. However, I had to stop using pfsense, because for some unknown reason (I couldn't figure out anything from the logs) the box was crashing and rebooting every 15 mins or so. I have excluded hardware fault because this box now runs opnsense without any problems.

The hpet bug that hit me with an update was a big let-down. Don't get me wrong or anything by no means do I blame pfsense or so; this was a core freebsd bug from what I have read.
Having running stable for 6 months or so, it was shocking that an update would essentially destroy the system and also was a hassle trying to fix it. After this I keep my ISP's modem preconfigured and aside. I also beats me why j3355 was not affected by the bug.

Best

Ok thanks, I will try to contact the Lanner support, maybe the know what's going on.

Bump.

Anybody else experiencing this?

Everything seems fine… speed gave me issues but with a Ubiquiti AP if slected fulldx speed instead of auto..

i just tried without the bridge... same thing... going to install 2.4.2 from scratch and see if it makes any difference.

I had a similar issue when upgrading to 2.4.2. I haven't solved it…

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

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

dns.JPG
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.