The resolver log is also rotating every 15mins but, yes, the filter log is was rotating every minute when that data was taken.

I should have been more clear when I said containers, I was actually talking about containers and virtual machines, which I serve via HAProxy.

Everytime I configure a new container I have to use the HAProxy web gui in pfsense, I do this frequently enough that I was wondering if pfsense had an API, which I now know it does not.

I like to automate things when I can, thanks for the responses.

I mean I would expect to see increased CPU usage when passing traffic. But that does look higher than expected. Suricata running on that traffic would explain it though as you say.

@SteveITS said in Trouble Accessing Internet on pfSense fresh install.:

trying to decide how the Cheez-it scale is scored… 🧐

Oh the brand name ones are "meh" you come above them ;-)

@jimp I'm pretty sure at this point that the problem was caused by the MACs changing. Since I set the MACs to static and the problem has not reoccurred.

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

@rtorres https://docs.netgate.com/pfsense/en/latest/vpn/wireguard/index.html
https://docs.netgate.com/pfsense/en/latest/recipes/index.html#id1
:)

Looks like your webgui is open to the internet and those are drive-by connection attempts.

Make sure your WAN firewall rules are now passing traffic to the webgui.

Steve

@04CC40
Good update. 👍

Are you able to show the MySQL service in 2.6? It doesn't exist AFAIK. This could also just be terminology confusion.

@SteveITS

I have literally been laying in the closet for 3 whole days. Factory reseting things, changing settings until it breaks, and starting over. Thank you so much!

Was that after upgrading?

The de-install error is common across an upgrade because php gets upgraded before the deinstall script. That's normally not an issue.

The filter reload errors are because those pfBlocker aliases are not populated yet. That is usually resolved after the first boot.

If you clear those errors and they do not return it's unlikely to be a problem.

Steve

Thank you both for your help! I wanted to follow up and let you know that Option 2 worked like a charm. I installed pfSense 2.7 CE, moved the NIC over to the new system, upgraded to pfSense Plus 23.05.1, and then restored the 23.05.1 config from the old system. The whole process probably took less than 30 minutes and everything was working fine by the end of it.

I only ran into two minor issues:

After config restoration the udpbroadcastrelay package service refused to start. Disabling / Re-Enabling the package via its GUI configuration page solved the issue and the service started fine. I was greeted with a bunch of errors after the initial reboot that followed config restoration. These were mainly pfBlockerNG related. I use pfBlockerNG lists as aliases in firewall rules and these lists don't exist without the initial pfBlockerNG update (that downloads and creates them). Once I ran a manual pfBlockerNG update, the lists were created everything was fine going forward.

Overall I'm very impressed with how smoothly the hardware upgrade went - a big thank you to everyone at Netgate for making the installation and restoration process so seamless.

There is no change in 2.7. RSS still does not support it so it cannot be used by multiple queues and hence threads/cores.

Yup, the fix for this is non-trivial!

Steve

@stephenw10
I know. However, it's way more comfortable to have all functions integrated in a single box, and can control them all with a single remote.

And as my TV is in my IoT wifi, which neither does allow communications between the wifi clients nor to other local subnets, but only the isolated DLNA server, which is bridged to the IoT on pfSense, if have not much security concerns regarding this to be honest.

@stephenw10

I helped him to do a clean new install of ver 2.7.
All is working now.

You need to NICS....

One for WAN and one for LAN.

Add the VLAN's on the LAN parent interface.

That the way (best practice).

I'm not aware of a limit there. You might hit usability issues in the webgui eventually.

Mmm, unfortunately there isn't really any other options there. There are a lot of cases where more fine grained notification control would be useful. There's probably already a feature request open but if not you can add one: https://redmine.pfsense.org/

Like: https://redmine.pfsense.org/issues/12531