I just upgraded to today's snapshot too.

2.4.0-BETA (amd64)
built on Wed Jun 07 09:27:01 CDT 2017
FreeBSD 11.0-RELEASE-p10

It seems to have fixed avahi

/root: ps aux | grep ava avahi      54058  0.0  0.1  29896  4128  -  I    22:11    0:00.12 avahi-daemon root      96242  0.0  0.0  14700  2408  0  S+  22:12    0:00.00 grep ava

The daemon runs now  :)

By just upgrading

Thanx for helping out

/Bingo

that seems like no troubleshooting at all.  I did not install that snapshot but on the current one dated Jun 7, see my sig.

And dhcp is running.  What was in the log that showed it didn't start on your opt, but started on your lan?  Seems unlikely.

What does your dhcpd log show?

For example here is mine starting up, as just did a update to latest snap from one on may 27th

Jun 7 12:59:14 dhcpd DHCPOFFER on 192.168.2.220 to de:ad:c0:de:ca:fe via em2 Jun 7 12:59:13 dhcpd DHCPDISCOVER from de:ad:c0:de:ca:fe via em2 Jun 7 12:56:03 dhcpd Server starting service. Jun 7 12:56:03 dhcpd Sending on Socket/fallback/fallback-net Jun 7 12:56:03 dhcpd Sending on BPF/em1/00:50:56:00:00:02/192.168.9.0/24 Jun 7 12:56:03 dhcpd Listening on BPF/em1/00:50:56:00:00:02/192.168.9.0/24 Jun 7 12:56:03 dhcpd Sending on BPF/em2/00:50:56:00:00:03/192.168.2.0/24 Jun 7 12:56:03 dhcpd Listening on BPF/em2/00:50:56:00:00:03/192.168.2.0/24 Jun 7 12:56:03 dhcpd Sending on BPF/em2_vlan600/00:50:56:00:00:03/192.168.3.0/24 Jun 7 12:56:03 dhcpd Listening on BPF/em2_vlan600/00:50:56:00:00:03/192.168.3.0/24 Jun 7 12:56:03 dhcpd Sending on BPF/em2_vlan200/00:50:56:00:00:03/192.168.4.0/24 Jun 7 12:56:03 dhcpd Listening on BPF/em2_vlan200/00:50:56:00:00:03/192.168.4.0/24 Jun 7 12:56:03 dhcpd Sending on BPF/em2_vlan100/00:50:56:00:00:03/192.168.5.0/24 Jun 7 12:56:03 dhcpd Listening on BPF/em2_vlan100/00:50:56:00:00:03/192.168.5.0/24 Jun 7 12:56:03 dhcpd Sending on BPF/em2_vlan300/00:50:56:00:00:03/192.168.6.0/24 Jun 7 12:56:03 dhcpd Listening on BPF/em2_vlan300/00:50:56:00:00:03/192.168.6.0/24 Jun 7 12:56:03 dhcpd Sending on BPF/em2_vlan500/00:50:56:00:00:03/192.168.7.0/24 Jun 7 12:56:03 dhcpd Listening on BPF/em2_vlan500/00:50:56:00:00:03/192.168.7.0/24

You can see it starting on all my interfaces, physical and vlans on top of that 1 physical.  And it getting discover and then sending an offer.

another forum with same backtrace actually has led me to this unresolved bug report on FreeBSD,  has been confirmed to affect 11 as well as 12.

So I think this might be what I have

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903

Have compiled the pfsense kernel now with the patch, will report back here if all good or not, only just booted into it so need to give it some time.

@w0w:

There is nothing to do with pfSense when hardware is some chinese crap.  :D
I don't know what exactly is "saumang ssd", but I think it's the root cause. Double check you hardware connections, firmwares etc

bad.  :-[  when i forget that word.  old MB has no new bois.  ;)

Almost couldn't believe your statement that it is working.
So I went and downloaded the latest 2.4 beta build (dated 06.05.2017).
And indeed this one now works.
Some FreeBSD fixes must have been applied this past week to the pfSense build.

Just for clarification:
pfSense 2.3.x never had a problem with 2012R2 (as far as I know), only with 2008R2. This is a FreeBSD 10.3 bug that still isn't fixed, at least to my knowledge. (unless the fix is to go to FreeBSD 11+)
pfSense 2.4 Beta had a problem with 2012R2 (did not test with 2008R2). This was a FreeBSD 11.0 bug. I read on the FreeBSD forum, that it was fixed in 11.0 stable p8 (or something like that). It seems pfSense has now picked up that fix and all is well :)

2008R2 might be considered "old" by some, but there are still a lot of servers out there with it and it is still supported by Microsoft (albeit only the Extended Support cycle).
And it's not like anyone is going to splash out 1000+€ for a new Windows Server license just to upgrade for the sake of running a newer pfSense version.
Not to mention that the server motherboards might not support a newer Windows Server version, which would require a huge amount of money to upgrade…

Anyway, the underlying problem seems to be fixed now, making me one happy puppy :)

Any updates on this? Last July ticket set to high priority. Still broke.

https://redmine.pfsense.org/issues/6606

I used the console and updated from there. All sorted.

Thanks guys.

It was the static entries box.  I read that as if the DHCP server was disabled, those would be the only working entries.

I disabled that box and it works as it should now.  Good call.  Thanks for the help.

Agreed you could run zfs if your hypervisor supports it.. That is not what the OP is doing..

No, it doesn't.

Boot-environment support at the boot-loader was available with FreeBSD 10.3.

https://www.freebsd.org/releases/10.3R/relnotes.html#boot

@yodaphone:

@jimp:

Both of those crashes are very low-level and highly unlikely to be software-related.

The fact that the system is so new does not necessarily mean the hardware is good. It could be defective, rather than developing a fault over time.

will run a few more iterations & check

i cant rule it out but will do more iterations .. thanks

Pretty sure the problems are actually to do with PIA. I was using them until the end of last year when speeds through to the same server dropped considerably without any changes.

Moved to OVPN.com and now that some initial teething issues with 2.4 snapshot AES-NI, I can push 250/20+ through my connection to their Amsterdam server. They've recently upgraded their servers to OpenVPN 2.4 so you can benefit by using AES-GCM anfd LZ4 on the link too.

This is HUGE!  Thank you for all your hard work in getting this pushed through.

Those are questions for a new topic under a hardware-related section.

Works well over here!

That did the trick, thanks!

That just means powerd was enabled and doing its job, throttling the CPU down if it didn't need to operate at full speed.

Refreshing the dashboard a couple times would drive up the CPU load and probably made it throttle back up to full speed.

https://redmine.pfsense.org/issues/6911
Unfortunately, the only solution is to use the legacy network adapter…