Thanks guys latest snap + gitsync resolved all issues.
But it brought new one, will start new thread.

Realtek cards/chips have, unfortunately, plenty of issues like this. You also can't set speed/duplex manually on most (all?) of them. The problems aren't inherent to the FreeBSD driver, either, IIRC it's the card/chip itself.

One of many reasons to avoid Realtek…

There are already some threads around discussing that, best not to rehash it here, though the Sandisk Ultra 30MB/s is a good choice if it works fast for you.

Thanks for the Heads Up. Don't have any PPP connections but I updated/gitsynced and tested: Default Gateway Switching with two static GWs still works fine.

Yes, 1015 Gib is less than 1TiB. So is does GiB up to 1023.99, then would switch to TiB.
Same applies for 1023.99 MiB then 1 GiB …

He's confusing that log with the other. The "can't allocate llinfo" is normal when the default gateway you previously had is unreachable, which is normal in the circumstance you describe.

The other logs indicate unbound was trying to start while it was already running. The dhclient error on linkup is similar. I was able to replicate both of those by cycling link on a DHCP client NIC multiple times in succession, will track down the root cause from there. It's harmless log spam in this case though.

Looks like 2.2 went to pretty extensive lengths to preserve the order.  So probably good idea to stay with that.  Even though it probably doesn't make any functional difference, as Jim and Phil point out it probably wouldn't be as external processes friendly.

OMG Im such a dumbass. Why the hell Im working this on friday night geez.

OK, I tested on a virtual machine on server which has flaky DLINK NIC.

Sure, virtual machine was showing me 10Gig (default for Hyper-v guest) and after I checked actual NIC it was 100Mbit/s.

Tomorrow morning this NIC leaves for good.

Now speeds are OK again.

Sorry for the trouble.

I have an APU2B4 with latest pfSense 2.3 64-bit nano 4GB image (I'll update daily via webinterface) installed on an USB stick and I don't have any problems since about 2 weeks.

I also had the reboot bug, but it is gone. I assume it was after the update to FreeBSD 10.3-PRERELEASE.

Also no problems with PowerD like it is described here: https://forum.pfsense.org/index.php?topic=106444.msg593107#msg593107

Really fixed this time, thanks xbipin.

@cmb:

Which lists did you have in pfblocker that would trigger it?

Spearpoint https://spearpointing.com/cbl.txt

And an old Shellshock list I made (that's prob outdated by now).
Not sure how I let 127.0.0.1 into mine.

It's not a problem, it's by design and how it's always been. Those pages can have long lists of static mappings, domain overrides, host overrides, at the bottom so putting the save button above those is the best place.

I made sure that all separator sections were removed from /cf/conf/config.xml and updated to today's snapshot and now I can duplicate a floating rule.

I will test other scenarios but I did run into another separator case, where if you create two separators and move them into place before clicking save (before apply), only one is retained and I think it moves the remaining separator down one rule as well.  I'll post that into the separators post.

I do see for the first time that moving rules/separators around the page is very snappy now on OSX Firefox 44.0.1 which is great!

In regards to the other post I removed and reinstalled. It did go quicker but still at several minutes vs the seconds another poster had mentioned.

Yeah, but I cant help myself, I like to know when Im wrong and this time my config checked out just fine :)

This is now fixed.

2.3 was missing the upgrade code to cope with CARP changes.

The upgrade process was reviewed and fixed.