@soulmaster179 have you looked at your NAT setting for lan to wan is that set to default? Has your firewall ever worked? Can you ping anything internally on the LAN from the firewall? Do you have port 53 or 853 in use for DNS to allow that traffic on your ACLs?

@stephenw10 Yes it does.

I was willing to try this, but after many years of computers, I wanted to do my due diligence first. I used to do PDP8s. I learned to be careful about deleting things.

I'm back to running 2.6.0-RELEASE (amd64) and I'm a happy camper! pfsense appears to be as happy as I am. ☺ System says I'm on the latest version, no notices that stuff can't be upoaded, I've got a list of installed packages and they all are running! Life is good. 😁

c05a2dea-3cf0-466b-a6dc-fd112d829564-image.png

Yes, you can upgrade to Plus from 2.6. You may want to wait until we switch the Plus upgrade repo to 23.05.1 so you can do it in one step. That should be happening imminently.

The same precautions as the 2.7 upgrade apply there. The safest way to upgrade is to remove packages first.

Steve

If pfBlocker (or some other package) gets hung up it's install script then subsequent packages might not get reinstalled.

The upgrade from 2.6 to 2.7 is large and includes a PHP change which makes pkg issues like this more likely.
Hence: https://docs.netgate.com/pfsense/en/latest/releases/2-7-0.html#upgrade-notes

The wireless interface type in pfSense is for wifi hardware in pfSense itself which is not what you have.

Your access point should simply be connected to one of the LAN ports in the 2100. Devices that connect to the AP will just get an IP from pfSense in the LAN subnet. Later you may want to move those to a new subnet so you can filter between them but I would only attempt that after first making it work as part of LAN.

The pfSense WAN should be set to PPPoE but that can only work if the upstream device is bridging the PPPoE connection correctly.

Steve

@stephenw10 said in System General Logs flooded:

Yes, it's fixed 'correctly' upstream now. it just wasn't accepted soon enough to be included in 23.05.1.

https://reviews.freebsd.org/D39966

It will be fixed in 23.09.

Steve

You guys are the BEST.

Thanks,
Rick

@stephenw10 done

@AK_4_Life said in Using Static ARP vs IPVLAN:

you will get a new IP every time you connect to the WIFI.

As mentioned by JKnott if you have devices that might use different macs, and not really allow for assignment of specific IPs that you can then filter or schedule in your firewall rules based on the IP, since it could change.

The best solution here is to put these devices on a common network(ssid) and then you can create your rules for the whole network/vlan and not really care what specific IPs might be in use - because all devices on this network get the same rules regardless of their specific IP.

I would try vmstat -i and make sure you see interrupts on both queues on each NIC when it's passing traffic.

@droidus

Enable console password under System --A Advanced --> Admin access

0d6c8c3f-008c-4815-b52e-b132c41a5fd8-image.png
..
Scroll to bottom
..
90e0ab80-570a-41ce-b194-de6f87bb5ffc-image.png

@nima because I am in the middle of converting from using local.lan to home.arpa - When I created the new ssl cert I put both on their as SAN..

Was not sure if I had anything using the local.lan as yet... I could prob remove it as this point..

I'm not aware of anything in 2.4.4p2 but that was a long while ago, I may have just forgotten! There have been thousands of fixes since then.

@mauro-tridici you can not route a fqdn, you would route the IP or network that IP resides on.

@SteveITS said in Release notes for pfSense Plus?:

@furom https://docs.netgate.com/pfsense/en/latest/releases/index.html#current-and-upcoming-supported-releases

Thank you! Of all places i looked, documentation was not one of them :)

@CrowFather May have answered this on Reddit…? Just reinstall from ISO and restore your config backup. Fastest way forward.

@emefff

That's kind'a as expected , based on my experience when upgrading to Plus 23.01
That's also based on FreeBSD v14

My home boxes uses i5-5250U , that CPU is to old to use the new "Speed/Power stuff" so those behaved as usual, using the "Old Power settings"
But my i3 test box was "hit" , and was what i described in the thread i pointed to.

/Bingo

Thanks a lot