Subcategories

• Cache/Proxy

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

  3.7k
  Topics
  20.5k
  Posts

  B

  @michmoor
  Yes, it works for them, unfortunately only there :(

• IDS/IPS

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

  2.2k
  Topics
  15.6k
  Posts

  K

  @bmeeks THank you so much will do thanks

• Traffic Monitoring

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

  553
  Topics
  2.7k
  Posts

  A

  @CZvacko said in Telegraf service stops when the physical interface is reconnected or reconfigured:

  In the last version 2.7.2 I noticed several times that the Telegraf service stopped working, now I found that it happens when reconnecting the physical interface. Probably also when adjusting interface parameters such as MTU. Is this considered a bug or how to prevent it ? (I have to remember to check it after such actions)

  This might be a bug. Check Telegraf logs for details, and configure it to restart automatically by editing its service file:

  Restart=always
  Restart with sudo systemctl daemon-reload && sudo systemctl restart telegraf. Update to the latest version and report the issue on Telegraf's GitHub if it persists.

• pfBlockerNG

  Discussions about the pfBlockerNG package

  2.5k
  Topics
  19.0k
  Posts

  S

  @tinfoilmatt I deleted my other posts to avoid confusion. It may have added to things, Suricata I only run on LAN, VLAN and VPN interfaces but have the same whitelist configured in an alias for it. Currently, the FTP site loads perfectly fine in a ftp or file manager also whether Suricata is disabled or enabled. Reading from why others changed their URL in the past also was due to the FTP link being intermittent at times, changing the feed URL in config.xml when FTP feed is down does allow the file to download and clear the download error itself. After further looking into though, doing this causes the processing of it to stop there and not update the UT1 orig files or populate them if they didn't already previously before changing the feed URL. Having pfBlocker enabled while disabling DNSBL followed with a reboot, re-enable DNSBL, reload restored my "ftp://ftp.ut-capitole.fr/pub/reseau/cache/squidguard_contrib/blacklists.tar.gz" feed URL into my config.xml without needing to manually edit it back, downloaded and fully processed updates.

  Lesson learned, if and when UT1's ftp goes down temporarily, leave things as is, it will come back up. More would have to be re-wrote to completely change over to a different URL feed by default but FTP maybe is preferred. Thank you for guiding me to dig further, thought I fixed one issue but led myself to turning it into another

• UPS Tools

  Discussions about Network UPS Tools and APCUPSD packages for pfSense

  86
  Topics
  2.3k
  Posts

  D

  @netboy Glad you got it sorted.

• ACME

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

  474
  Topics
  2.7k
  Posts

  T

  For (nearly) the second time now the ACME package has filled up the disk on my pfSense. A recap of some history:

  On August 8, the ACME package updated the certificate On October 7, I came home in the afternoon to find the internet not working. Eventually determined the disk was full and deleted some zfs filesystems associated with old versions. This got things working but the webgui was totally borked. On October 11, I finally did a factory reset, and restored a configuration backup from August 8, after the certificate update

  Things were working fine until a couple of days ago when I started getting HSTS errors when trying to connect. My browser showed I was being served the August 8 certificate, which expired on November 6. The certificate seemed legit (as in, one that was issued to my pfSense) but for whatever reason a newer cert (that was present in the GUI) wasn't being used. I couldn't find any evidence of this August 8th cert in the GUI or configs, but that's not actually the point of the story.

  While trying to figure this out, I noticed that /cf was using a large amount of space. This was one of the things that eventually led to the previous install crashing:
  ce5f6f00-8e84-4c7e-a832-560c8c29ee07-image.png

  Poking around I found a config file every second in the backup directory:
  4715cf3b-c4cb-4739-b212-23875c10069b-image.png

  Looking at the timestamps on these config files you can see about when it started:
  610c4531-0070-42ac-835b-9191f897a80b-image.png

  The first config in that 1731701* bunch had this change, me forcing a certificate issuance in the hope that would fix something:
  6cf88b4e-f8e1-4406-824f-2df44f8d9106-image.png

  After that, there is an "identical" config every second looking like:
  40b5bb0c-a638-4b95-b404-689c4e351e9d-image.png

  time is /pfsense/revision/time, and lastrenewal is /pfsense/installedpackages/acme/certificates/item/lastrenewal. The comment on every one of thos configs is the same as above, "(system): Services: Acme: Storing signed certificate". I assume ACME is somehow in a loop where modifying the config is causing it to update the config.

  I ended up uninstalling ACME which stopped the problem, but once I re-installed ACME and forced another Issue/Renew, it started again. System Logs shows this loop:
  2380115f-0204-4f3f-9f2f-480f5b3ee984-image.png

  This is with pfSense-pkg-acme-0.8_1 on a Netgate 1100 running 24.03-RELEASE

• FRR

  Discussions about the FRR Dynamic Routing package on pfSense

  278
  Topics
  1.1k
  Posts

  B

  @frijolierthnthou Were you able to solve this issue? I've been dealing with this same exact problem from the past 2 weeks

• Tailscale

  Discussions about the Tailscale package

  74
  Topics
  417
  Posts

  D

  Screenshot_20241113_175104.jpg Good day everyone,
  Im getting this notification on my pfsense, can someone tell me what is it?

• WireGuard

  Discussions about WireGuard

  625
  Topics
  3.3k
  Posts

  B

  Hello, i know there is another post about this, but it is marked as solved and it's few months old, also the solution is not really clear to me, so i decided to create a new one.

  I did setup a wireguard site to site vpn between two pfsense firewalls.
  Everything looked good until i tried to mount a nfs share from a site A server in a site B client, the server sees the connection as from the wg tunnel ip and not from the real client ip, not allowing me to mount the share.

  I don't want to nat connections in my wg tunnel.

  i tried to switch to hybid nat and create a rule to disable nat in the tunnel interface but that broke the site to site vpn.

  i must also mention that i have set an upstream gateway in the tunnel interface in each site, because the netgate guide i followed said to do so, but at this point i am not sure this is necessary.

  Can anyone point me in the right direction to solve this?
  Thanks