@cylosoft I agree, the systemlogs is a great potential area for a new package for pfSense. Obviously having some real log analytics and trend history with filtering capabilities straight out of the Firewall would be nice, but I understand that larger installs would not need that - hence an add-on package that you could elect to use - in case a graylog/splunk whatever install is not an option to you. If only I was a developer and knew how to code…..:-)

@luckman212 said in Live refresh for dashboard Services Status widget: snapshot and try to update this to merge cleanly. Thanks Cool then we get "live widget updates", thank you both also.

@lanna Why posting an actual photo?

@petri said in webGUI not accessible from VLAN but ...: Client connected to em2 cannot access to GUI if em1 doesn't have an active connection Normally you would have interfaces connected to a switch, and not some single device.. But if an interface is not up then no you wouldn't be able to connect to its up, because the interface is not up.. https://docs.netgate.com/pfsense/en/latest/multiwan/policy-route.html#policy-routing-configuration Why would you not just fix whatever it is your wanting to happen on lan interface not doing what you want for your vpn??

@johnpoz and @bingo600 Thank you! That did the trick.

@johnpoz Thank you so much, now im working on it, i was able to see that the rules on wan settings was gone and a new rule was created on the LAN settings.. THanks, joe

UPDATE: I've been doing some tests trying to know where the problem is and it seems that finally it comes from WAN interface. I configured first WAN but until I configured the IPSEC tunnels the problem didnt appear. Today I reinstall a fresh pfsense and first of all I configured the tunnels with no problems and when I configured the WAN the problem start. If I enable WAN with DHCP or Static IP without a gateway it works everything fine, when I choose a IPv4 Upstream gatewy then return the problem. At this point this topic can be closed.

@gertjan I will attempt this tonight and report back. Thanks.

@publictoiletbowl You mean the status monitoring page ? You have access to the page, but .... the page builder, PHP; is probably using commands that need root/admin access.

@gertjan Did as you suggested and turned off the Wireguard tunnel and the web page response time improved dramatically, unless I tried to go to: Status/ Wireguard - which was still slow. Memory usage is at 12% and cpu at 33%. It simply appears to be very slow in pulling data from the Status of the Wireguard peers and displaying this data on a web page.

@jimmychoosshoes The UI display and filter only handles 10.000 logentries from the current logfile/rotation. If your current logfile is much larger than 10.000 lines, it becomes REALLY slow to load. If you want lots of log retention, create a MUCH bigger rotation and use smaller logfiles. This will make the UI much faster since the 10.000 lines does not require loading a 400Mb file. This way you still have a lot of retention. The only drawback (regardless of which settings you use) is you can’t find older log entries from the UI as that only goes back 10.000 lines in the combined log rotation. So the remaining rotation logs can only be searched from the CLI or som external tool. I’m still hoping a log analysis/parsing package will be created for pfSense, or that Netgate will create an option for letting the UI filter feature go MUCH further back than 10.000 lines.

ntopng, darkstath, bandwidthd probably there are other packages now that can give you a better log view, idk, personally i send everything to grafana and i let the firewall do the firewall.

@jimp said in Firewall filter LOG, GUI search and Circular logging: It's partially a holdover from the days when clog could rarely have more than a few thousand lines and partially because parsing that many filter log lines can be a burden on the firewall so it is limited so it doesn't put undue strain on the system. You can increase it on your own by editing the line at https://github.com/pfsense/pfsense/blob/master/src/etc/inc/syslog.inc#L705 We haven't come to a decision on what the best course of action is there overall. Okay - that is very good to know. I think you should make a GUI setting for limiting how far it goes back - with a memory use estimator explaining the consequenses of increasing it (Just like you do where you can edit the current log file size in diskspace terms). Alternatively there should be developed a dedicated log processing and analytical package people can install if they have CPU/memory enough.

@ddbnj When you have a screen that can show all the content this is what you get. Without the redaction square, of course. [image: 1660082609792-screen-shot-2022-08-09-at-5.03.00-pm-resized.png]