@bcnx Glad you got it sorted.. Here all the time if you have questions - happy to help!

Hello, I've solved the problem by increasing the max table entries allowed. KR, P' Bear

Guys, thank you, ended up with the console access and rebuilding the LAN configuration through it, all is working now...

@mrturner19 sure.. You could do it for 200 ips if had that many..

@gertjan I am aware that I am dealing with topics far far beyond my knowledge. Thanks a lots Ilario

@stephenw10, the User to Authenticate is mine. And i can Logon, also if the User was Expired the "Select Container" function woulden work. But it dose and i selectet a Container for Authentication.

@gertjan I guess that is the "nuclear" option to the original issue, remove the underlying functionality that caused the log entries to begin with...

@swemattias nic pass though to pfsense is simpler imo. Hardware off loading can also then still be used

Ok, you probably need to use NetFlow data then.

@steve_b I am looking into moving the users and the certificates of the pfSense machines to a dedicated solution. Thanks for the help with this issue!

@slu said in Export CA | Do I have to pay attention to anything?: You mean the CN name or something like this? Yes. Or someones email address etc. Something you may not want public. Steve

So you just need to redirect traffic to them in pfSense? You can just use port forwards for that. That's what Squid does if you set it to transparent mode. Steve

Yikes that is ugly. If it's that badly configured, have you tried logging into that random device with default credentials and turning off DHCP? :-)

@stephenw10 Hi Steve I submitted a post earlier, here https://forum.netgate.com/topic/166622/i-need-to-restart-the-ovpn-tunnels-after-a-pfsense-reboot/2

Read thru most however I have a protectli PFSENSE ( 2.5..2 ) box behind my ISP fiber modem. In the setup i just put in my PPPOE username and password and it set it up and just works. My ISP here in Dubai requires my wan to be connected on a certain port on the modem ( ONT4) Otherr than that it just works and I am not a real technical guy.

Solved this issue. It appears that the most recent macOS update disabled the UART bridge used for serial comms. Re-installed the driver from Silicon Labs and everything is working.

@steveits lol you're amazing :D that's exactly it! Thanks a lot!! Cheers

@mgcsec said in pfsense packet process order: @stephenw10 thank you! and then where are local services/plugins involved? for example Nginx in that chain? NAT=>FW=>Nginx=>NAT=>FW=>Upstream? For some services, yes, this is the processing order. But for others such as the IDS/IPS packages, this is the processing order: IDS/IPS => NAT => FW (for inbound traffic on WAN) IDS/IPS => FW => NAT (for inbound traffic on LAN)