@stephenw10 thanks for responding -- yup pfSense update solved this particular issue. Now I'm running into TLS/ cert issues on my dockerized graylog setup, which is probably outside the scope of this forum.
Would be nice to have a standard way to securely manage logs in Pfsense -- one that does not encourage people to send logs in the clear.
I know you can just run a local server and have some security with Rules, but would suggest to have a more formal secure integration with Graylog given how popular it seems to be with people here. Also for people that want to monitor more than one network with one Graylog instance
@Gertjan thanks for the info, I got brave yesterday and ordered this one...
APC Back-UPS 600VA, 120V, 1 USB charging port, 7 NEMA outlets (2 surge)
BE600M1
@stephenw10 I set a session timeout of 10 minutes. I have never entered a value in that field before. Logged back in after it timed out, cleared the session timeout field. This morning the login page came up normally.
Yes and you can set it to import only the aliases in the import utility so you don't mess up your config.
Use "Restore Area"
[image: 1721240177107-screenshot-2024-07-17-at-11.15.07.png]
@stephenw10 the duplicate echo, is with the stable configuration. current. what works. I believe is an ISP issue.
When i had the wan gateway on the rules. never actually saw duplicate reply, but again things were unstable and just occasionally crashed.
I would certainly expect to. I've never had any issues enabling RAM disks. Just make sure the size you set for /var is at least larger than it's currently using.
There are some packages that won't work with RAM disks or at least not without significant tuning. Snort or Suricata primarily.
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.