Ah thanks thats one that was fixed in haproxy-devel, sending pullrequest for haproxy now..

Good catch, thanks. Fixed.
https://redmine.pfsense.org/issues/6063

@bsdkllr:

hi,

i have a single realtek nic set up with the wan on a vlan and native lan. if powerd is enabled and i try and do a speedtest it will cause the nic to throw a re0 watchdog time out.

light internet browsing will be fine but any time you start consuming bandwidth it will error out.

thanks

Hi,

I'm pretty sure it's not 2.3 related coz I'm having the same issue, and I'm on stable 2.2.6. My box will eventually "crash / hang" (regardless the load) can't access webconfig and internet etc, has to reboot the box to get access again. Now I've switched off (unchecked) powerd and it's been up and running for more than 30 hours and 0 error / drop.

This is my box (bought off of China):
https://world.taobao.com/item/525567399176.htm?fromSite=main&spm=a312a.7700846.0.0.QWscLQ&_u=21igi6h264bf

Spec:
CPU: i3-4025u 2C - 4T - AES-NI
RAM: 8GB 1.35v DDR3L
LAN: Dual RT8111E
SSD: Msata Plextor 128GB
WAN: 500/500 Fibre to Home

Hopefully, this will be fixed in the future.

Cheers!

Oh, right, it's the same update file regardless of how you installed it. We should clarify that. Most people update via auto-update so that page doesn't get used much for update purposes (outside things like RC).

Hmm. Right there in the 2.3 new features and changes file. :/

It was buggy I believe. I am using Lightsquid. The only thing I miss from sarg is the ability to easily see the denied access reports so I can quickly see what was blocked for my clients. I hope sarg will return one day as this is a very useful feature.

Don't you love it when impatience gets the better of you?

Upgrading now, thanks to the clear & present instructions of pmisch above. Wish me luck….

UPDATE: Wow. That was quick & painless. All up an running inside 5 minutes, with all my old configs, including cron and pfBlockerNG all imported automagically.

Also loving the slick, light interface :)

@bluepr0:

I just upgraded but Squid is not starting. Log below:

Apr 1 22:31:52 (squid-1) UFSSwapDir::openLog: Failed to open swap log. Apr 1 22:31:48 (squid-1) UFSSwapDir::openLog: Failed to open swap log. Apr 1 22:31:45 (squid-1) UFSSwapDir::openLog: Failed to open swap log.

If I disable the logs then it works, but otherwise it won't start!

might be related to:
https://forum.pfsense.org/index.php?topic=105399.msg588219#msg588219

Yup, that I knew.  Thanks a lot for all of your help CMB.  I really appreciate your time.    Looking forward to the continued updates!

Unfortunate, (and circumstancial) that the upgrade from 2.1.1 to 2.3 (so I can use IPSEC, HA, SNORT etc) had me tripping over so many bugs.  I feel like I have a grasp on what happened and where, and really the only bug affecting the config is the pfsync and HA with limiters.  The limiters are not detrimental as I actually have a separate pipeline I can funnel the traffic out of if I need to, so I can function.  IPSEC and Snort were big ones for me, glad the IPSEC issue that plagued 2.2.x due to OS issues wasn't an issue in 2.3.

Again, my sincerest thanks!

-D

You'd better not change that css file as that will get overwritten.

Better copy the default theme and give it a new name. Then and add your changes to it.

Hi All,

Just done the installation today and I got a positive result, rtl8111h now supported in 2.3 tho I haven't done an extensive test yet. Will update this thread when i performed more test. I kind sleepy now. Lol

"can't remember having this issue, with it  any of the previous snapshots"
I started using the Beta March 20th and after any update requiring a reboot also needed a restart of unbound to get the log file showing it was indeed running. After reboot I also had to "Reload" the DNSBL to get it showing in the widget for that database.
Also I found the running/stopped icon not showing unbound as stopped. It always showed as running.
Still, thank you for a great firewall. Everything else went very smoothly in the upgrade to RC.

Currently using 2.2.6 production environment on Dual core cpu ,2 x NIC  ,  Snort , Pfblocker NG , bandwidthd , unbound resolver, squid proxy non transparent(Wpad hosted on diff server) , DHCP , and
SquidGuard . Is it safe to update to RC or should i wait for stable Release

if upgrading what is the best way ?

That'll be there when we get to FreeBSD 11, which is slated for 2.4 later this year.

Actually I was the one who upgraded your system. Didn't realize who you were until looking at your profile. That makes even less sense knowing what's on your system.

I'd like to work with you on testing this over the weekend. I'll PM you to see if we can arrange.