Subcategories

• Cache/Proxy

  Discussions about packages which handle caching and proxy functions such as squid, lightsquid, squidGuard, etc.

  3.8k
  Topics
  20.6k
  Posts

  C

  Hi all. After updated squid should I use or any alternative ?

  squid.png

• IDS/IPS

  Discussions about packages whose functions are Intrusion Detection and Intrusion Prevention such as snort, suricata, etc.

  2.2k
  Topics
  15.7k
  Posts

  B

  @tchadrack said in Suricata - interface show the service as stopped after sometime.:

  Notice, that suricata pid file is not here.. That is the motive why Suricata / Interfaces page shows them as down.

  Yes, that is why the GUI interface code thinks it is not running. It checks for the presence of a PID file named with the UUID of the interface.

  I have no idea why the PID files would be missing, though. They are created by the Suricata binary as part of its startup procedure. The GUI code has nothing to do with that. It simply checks they are present to determine which icon to display -- Suricata "running" or "stopped".

• Traffic Monitoring

  Discussions about packages that handle bandwidth and network traffic monitoring functions such as bandwidtd, ntopng, etc.

  557
  Topics
  2.7k
  Posts

  D

  This doesn't have anything to do with VPN, multi WAN, etc. It's the same interface ("PLDT") in either case.

  I checked the code. Both graphs are produced by /usr/local/www/js/traffic-graphs.js and the data for both comes from the same rrd file.

  The graphs have different refresh rates, resulting in different time periods, which results in different time averaging intervals for rrd. The Traffic Graph page, with a hard-coded refresh rate of 1, ends up with a shorter time interval (magnified view) when compared to the Dashboard widget with a default refresh rate of 3. So on the Traffic Graph page you might see two brief spikes of 40M in quick succession, however on the dashboard widget only see one spike of 20M. It's still the same data.

  FWIW, The graphs also have different smoothing applied, but this doesn't have nearly as much of an impact as the time averaging interval.

  If you really want the Dashboard widget and the Traffic Graph page to match, you would need to change the widget refresh period to 1 second. In general this is not recommended due to the increased CPU requirement, but you have to decide what's more important to you.

• pfBlockerNG

  Discussions about the pfBlockerNG package

  2.6k
  Topics
  19.3k
  Posts

  D

  My only concern was that I generated a lot of entries during testing and I wanted to clean them up.
  However, the idea with the SSD is good to reduce the load on the system.

  I'll find out the best way to do this.

• UPS Tools

  Discussions about Network UPS Tools and APCUPSD packages for pfSense

  89
  Topics
  2.3k
  Posts

  Z

  @dennypage I will go for your suggested solution:

  UPS 1: pfSense as NUT server and the rest as NUT clients
  UPS 2: one system attached to the UPS as the NUT server and the others as NUT clients

  Since I don't have enough knowledge of NUT I guess I will be back several time to this forum.
  Thanks for you gudelines and Merry Christmas !!!

• ACME

  Discussions about the ACME / Let’s Encrypt package for pfSense

  482
  Topics
  2.7k
  Posts

  I

  Hello,

  Since 24.11 I've had PHP errors flagged in the pfsense interface, I tracked them down to ACME so thought the simplest thing would be to reinstall. I get this on install now...

  Executing custom_php_install_command()...<pre style="white-space: pre-wrap;">PHP ERROR: Type: 1, File: /usr/local/pkg/acme/acme.inc, Line: 2938, Message: Uncaught TypeError: Cannot access offset of type string on string in /usr/local/pkg/acme/acme.inc:2938 Stack trace: #0 /usr/local/pkg/acme/acme.inc(2916): pfsense_pkg\acme\acme_convert_letsencryptv1_to_letsencryptv2() #1 /etc/inc/pkg-utils.inc(800) : eval()&#039;d code(1): pfsense_pkg\acme\acme_custom_php_install_command() #2 /etc/inc/pkg-utils.inc(800): eval() #3 /etc/inc/pkg-utils.inc(917): eval_once() #4 /etc/rc.packages(76): install_package_xml() #5 {main} thrown</pre>===== Message from php83-ftp-8.3.12:

  Running on a Netgate 3100, no other mods, very vanilla.

  Any ideas?

• FRR

  Discussions about the FRR Dynamic Routing package on pfSense

  282
  Topics
  1.2k
  Posts

  C

  @Gorf Did you look at your primary config file? I can see some "FRR" info on mine that is still there even though I took the package off..

• Tailscale

  Discussions about the Tailscale package

  77
  Topics
  436
  Posts

  E

  @atlmcw

  I had no issues.

• WireGuard

  Discussions about WireGuard

  646
  Topics
  3.4k
  Posts

  L

  ok. so I just checked with my pfSense and I don't see any info with the netstat command (just like you).
  What I see in Diagnostics > Sockets is the same info as in your 1 screenshot:

  8b740de0-3350-4ef1-88c2-66793c4decbf-image.png

  Can you please try the following:

  verify in VPN > WireGuard > Settings that "Enable is checked

  c1b5a656-f4cf-410c-8932-744b375e6b93-image.png

  verify that you have assigned an interface to the network port in Interfaces > Interface Assignments

  ef4d242f-8cc9-4915-a352-9eb9e7bb1017-image.png

  As for the wireguard package version. I just realized that the version is different on my pfSense Plus. Regulard pfSense has 0.2.1 meaning yours is up-to-date.

  I also found some posts where users reported that removing the wireguard package WITHOUT keeping the configuration and then reinstall the package, did the trick.

  b636a67a-fef8-449c-bc8e-5899e8c4dd44-image.png
  --> "Keep Configuration" needs to be unckecked