@bassplayaman re: latest, see https://docs.netgate.com/pfsense/en/latest/releases/2-7-1.html#troubleshooting

I know what your thinking, Big deal, I got logs in pfSense, But here the issue is, most often you will be running your AP in bridge mode and having pfSense hand out the DHCP addresses, and if your in bridge mode not much info on whats connecting to the NAS internally behind the firewall is ever seen on the firewall logs. This gives you a level of visibility not normally seen within pfSense unless it is configured. Again if you can do it with one AP you can do it with an alias for many APs on a bigger network. This gives you more information into possibile mac spoofing and unauthorized access. If you use remote access and Dynamic DNS for your network, you can see the firewall logs and the AP logs as well.

@johnpoz said in SG-3100 switch weird behavior (resolved): once you put it up, I will give it a go via a VM maybe. I don't as of yet have a pi4 to play with.. Been looking for an excuse to get one hehe.. But they have been hard to find as well, I would prob go with the 8GB ram model as well. Done, english is not my first language so I hope its okay. https://forum.netgate.com/topic/175394/graylog-server-on-a-raspberry-pi

The logging used by pfSense can be seen here: /var/etc/syslog.d/pfSense.conf As it says there though that file is auto-generated and should not be edited directly. However if you look there you will see that kern.debug is already being written to the system log so I would expect that to include anything at the lower priority level 'info'. Steve