Subcategories

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

    4k Topics
    21k Posts
    JonathanLeeJ
    @firefox you could always turn off save settings on squid and squid guard and delete the package and reinstall. You could also manually remove the config from the xml file. Those are also options but I think the fresh firmware is the best approach. It does work on that version I got it going.
  • Discussions about packages whose functions are Intrusion Detection and Intrusion Prevention such as snort, suricata, etc.

    2k Topics
    16k Posts
    M
    Hi, I had a problem with my home network today, so I checked pfsense and discovered that suricata had blocked the wan ip. After some tests and triggering some suricata alerts, the wan ip was blocked. I restarted pfsense and ran some more tests, but the problem no longer occurred. I then checked the wan interface settings and indeed the ip list does not include the wan ip, both now that it's working and before, when it was blocked. I'm using pfsense 2.8.0 and suricata 7.0.8_2. I use PPPoE to access the Internet.
  • Discussions about packages that handle bandwidth and network traffic monitoring functions such as bandwidtd, ntopng, etc.

    571 Topics
    3k Posts
    dennypageD
    @Leon-Straathof Data retention settings are handled inside of ntopng. Documentation here. Pay attention to the RRD note. Also, if you've turned on some of the slice and dice time series information (is off by default), I'd suggest turning them back off. These balloon the storage requirements and are of little actual use.
  • Discussions about the pfBlockerNG package

    3k Topics
    20k Posts
    keyserK
    @jrey said in pfBlockerNG syslog logentries to remote SIEM: @keyser I so want to answer this, but then at the same time (no I don't) ... pfblocker using syslog messaging in real time. no tailing of files, no other packages, just code. Huuuh? That seems very very interesting I noticed your name in other posts around the forum where you seemed to be QUITE proficient at coding/developing. Are you by any chance considering involvement in developing and refining the pfBlockerNG package? It would be SO great if you are looking into adding native syslog to the pfBlockerNG package - or an easy workaround that does not require additional packages and “temporary” edits in files that does not survive service restarts or pfSense updates. Here’s that you will fill me/us in on the solution you are using to your Greylog - please, pretty please with sugar on top
  • Discussions about Network UPS Tools and APCUPSD packages for pfSense

    101 Topics
    2k Posts
    dennypageD
    @jhg said in NUT fails to start after 2.7.2 -> 2.8.0 upgrade: Interesting. I would have thought the initial reboot, which occurred as part of the upgrade, would have done the trick, but it took a second reboot, just now, to get things working. Glad you have it sorted. There was no difference in the output of usbconfig show_ifdrv at any point -- before or after unplugging/replugging the USB cable, nor after rebooting. ... Question: What would tell me whether or not a driver was loaded? If there were an attached driver, it should have shown up with the show_ifdrv command. If you use the command and look at the other usb devices, I think they will show attached drivers. I don't expect to see a driver attached to the ups, because there is a quirk that tells the OS to ignore that device (and not attach a driver). Look for idVendor and idProduct in the above output. The Vendor ID for your device is 0764, which corresponds to Cyber Power Systems, and the Product ID for your device is 0601, which is registered as "PR1500LCDRT2U UPS" (don't sweat an exact match for the name). You can see the quirk with the following command: [25.07-RC][root@fw]/root: usbconfig dump_device_quirks | grep 0764 VID=0x0764 PID=0x0005 REVLO=0x0000 REVHI=0xffff QUIRK=UQ_HID_IGNORE VID=0x0764 PID=0x0501 REVLO=0x0000 REVHI=0xffff QUIRK=UQ_HID_IGNORE VID=0x0764 PID=0x0601 REVLO=0x0000 REVHI=0xffff QUIRK=UQ_HID_IGNORE [25.07-RC][root@fw]/root: Your device is third on the list. The HID_IGNORE quirk says to ignore the device and not attach a driver. @jhg said in NUT fails to start after 2.7.2 -> 2.8.0 upgrade: You might consider adding this resolution to the release notes for 2.8. LOL... sorry, I don't have input to the release notes (I don't work here). While I wrote and maintain various packages, including NUT, I'm still just a volunteer. Most packages are actually written by volunteers.
  • Discussions about the ACME / Let’s Encrypt package for pfSense

    496 Topics
    3k Posts
    R
    @provels said in updating to acme 1.0 breaks system beyond repair: need to restore from backup: This same mess happened to me, even w/o Acme, going from 25.07 to *.1. Blew, reinstalled w/ Crowdsec, blew again, reinstalled, clipped all the Crowdsec info from config.xml, restored config, back to normal. Crowdsec is a great concept, but I think I'm out. I never had this issue with Crowdec before the ACME update, even with updating from 2.7 to 2.8 there was no issues. In fact after restoring from a backup after the ACME update, Crowdsec reinstalled just fine, and this was before the recent release a couple days ago that contained a fix.
  • Discussions about the FRR Dynamic Routing package on pfSense

    294 Topics
    1k Posts
    yon 0Y
    said in Please update frr on Pfsense+ to FRR 10.3: https://redmine.pfsense.org/issues/15785 now frr 10.4.1
  • Discussions about the Tailscale package

    90 Topics
    606 Posts
    M
    @yobyot I've SSHed into pfsense and for the sake of testing I've simply run the command: tailscale up --auth-key=tskey-client-kQ_THE_REST_IS_A_SECRET\?preauthorized=true\&ephemeral=false --accept-dns=false --accept-routes --advertise-exit-node --advertise-routes=X.X.X.X/24 --advertise-tags=tag:pfsense Note the preauthorized=true and ephemeral=false I gave this key all permissions (temporarly as I just wanted to verify it's working) of course I had to register the tag used also in the ACL tags pane: https://login.tailscale.com/admin/acls/visual/tags so far so good
  • Discussions about WireGuard

    697 Topics
    4k Posts
    H
    I figured out the issue. I missed adding the 3rd locations Lan to the static routing. Now all is working perfect.
  • NanoBSD url filtering

    2
    0 Votes
    2 Posts
    646 Views
    jimpJ
    They don't. Use a full install, not NanoBSD. NanoBSD is going away in 2.4, may as well switch to a full install now and use squidGuard how it's intended.
  • LCDproc Crystalfontz CFA634 USB

    1
    0 Votes
    1 Posts
    851 Views
    No one has replied
  • MOVED: Only block source on specific SIDs

    Locked
    1
    0 Votes
    1 Posts
    492 Views
    No one has replied
  • Ping: sendto: Permission denied and snort

    1
    0 Votes
    1 Posts
    2k Views
    No one has replied
  • FreeRADIUS with Android and Unifi access point - problem to get going

    6
    0 Votes
    6 Posts
    5k Views
    P
    OK Here's what's happening: I created a FW rule to allow traffic from wifi AP to LAN on port 1812.  That definitely was missing!  Good catch ;)  At least now I see something in the system logs… After that I followed your instructions, that is, created a new cert under "System > Cert. manager > Certificates" (named pfsense-RADIUS) then exported the root CA (under System > Cert. manager > CAs) to my Android phone. Then I modified the wifi connection on the phone and assigned the newly imported root CA to it.  Then I modified RADIUS's config and selected the certificate "pfSense-RADIUS"  (under EAP tab > SSL Server Certificate). Finally I tried connecting to the Wifi network, but the phone still says "Authentication problem" and pfsense logs show: Oct 16 18:54:11 radiusd 22391 Login incorrect (TLS Alert read:fatal:unsupported certificate): [wifiuser] (from client unifi-ap-ac-lite port 0 cli XX-XX-XX-XX-XX-XX) Oct 16 18:54:11 radiusd 22391 SSL: SSL_read failed inside of TLS (-1), TLS session fails. Oct 16 18:54:11 radiusd 22391 rlm_eap: SSL error error:14094413:SSL routines:SSL3_READ_BYTES:sslv3 alert unsupported certificate Oct 16 18:54:11 radiusd 22391 TLS_accept: failed in SSLv3 read client certificate A Oct 16 18:54:11 radiusd 22391 TLS Alert read:fatal:unsupported certificate Oct 16 18:53:31 radiusd 22391 Login incorrect (TLS Alert read:fatal:unsupported certificate): [wifiuser] (from client unifi-ap-ac-lite port 0 cli XX-XX-XX-XX-XX-XX) Oct 16 18:53:31 radiusd 22391 SSL: SSL_read failed inside of TLS (-1), TLS session fails. Oct 16 18:53:31 radiusd 22391 rlm_eap: SSL error error:14094413:SSL routines:SSL3_READ_BYTES:sslv3 alert unsupported certificate Oct 16 18:53:31 radiusd 22391 TLS_accept: failed in SSLv3 read client certificate A Oct 16 18:53:31 radiusd 22391 TLS Alert read:fatal:unsupported certificate Oct 16 18:53:09 radiusd 22391 Login incorrect (TLS Alert read:fatal:unsupported certificate): [wifiuser] (from client unifi-ap-ac-lite port 0 cli XX-XX-XX-XX-XX-XX) Oct 16 18:53:09 radiusd 22391 SSL: SSL_read failed inside of TLS (-1), TLS session fails. Oct 16 18:53:09 radiusd 22391 rlm_eap: SSL error error:14094413:SSL routines:SSL3_READ_BYTES:sslv3 alert unsupported certificate Oct 16 18:53:09 radiusd 22391 TLS_accept: failed in SSLv3 read client certificate A Oct 16 18:53:09 radiusd 22391 TLS Alert read:fatal:unsupported certificate Oct 16 18:51:34 radiusd 22391 Login incorrect (TLS Alert read:fatal:unsupported certificate): [wifiuser] (from client unifi-ap-ac-lite port 0 cli XX-XX-XX-XX-XX-XX) Oct 16 18:51:34 radiusd 22391 SSL: SSL_read failed inside of TLS (-1), TLS session fails. Oct 16 18:51:34 radiusd 22391 rlm_eap: SSL error error:14094413:SSL routines:SSL3_READ_BYTES:sslv3 alert unsupported certificate Oct 16 18:51:34 radiusd 22391 TLS_accept: failed in SSLv3 read client certificate A Oct 16 18:51:34 radiusd 22391 TLS Alert read:fatal:unsupported certificate Oct 16 18:50:52 radiusd 22391 Login incorrect (TLS Alert read:fatal:unsupported certificate): [wifiuser] (from client unifi-ap-ac-lite port 0 cli XX-XX-XX-XX-XX-XX) Oct 16 18:50:52 radiusd 22391 SSL: SSL_read failed inside of TLS (-1), TLS session fails. Oct 16 18:50:52 radiusd 22391 rlm_eap: SSL error error:14094413:SSL routines:SSL3_READ_BYTES:sslv3 alert unsupported certificate Oct 16 18:50:52 radiusd 22391 TLS_accept: failed in SSLv3 read client certificate A Oct 16 18:50:52 radiusd 22391 TLS Alert read:fatal:unsupported certificate Oct 16 18:50:29 radiusd 22391 Login incorrect (TLS Alert read:fatal:unsupported certificate): [wifiuser] (from client unifi-ap-ac-lite port 0 cli XX-XX-XX-XX-XX-XX) Oct 16 18:50:29 radiusd 22391 SSL: SSL_read failed inside of TLS (-1), TLS session fails. Oct 16 18:50:29 radiusd 22391 rlm_eap: SSL error error:14094413:SSL routines:SSL3_READ_BYTES:sslv3 alert unsupported certificate Oct 16 18:50:29 radiusd 22391 TLS_accept: failed in SSLv3 read client certificate A Oct 16 18:50:29 radiusd 22391 TLS Alert read:fatal:unsupported certificate Oct 16 18:50:16 radiusd 22391 Ready to process requests. Oct 16 18:50:16 radiusd 22010 Loaded virtual server <default></default> Thats weird no?
  • Siproxd 0.8.1 to 0.8.2 ?

    3
    0 Votes
    3 Posts
    865 Views
    T
    Thanks a lot !  ;D
  • Syslog-ng advanced tab broken in pfsense 2.3.2

    1
    0 Votes
    1 Posts
    685 Views
    No one has replied
  • Bind DNS Server with Master over IPSEC VPN

    2
    0 Votes
    2 Posts
    1k Views
    C
    I vaguely recall a similar behavior with pfSense looking at Name Servers over an IPSec tunnel.  IIRC, they had a static route configured for the IP of the DNS server which used the pfSense LAN IP as the Gateway.  (This was an infrastructure I inherited, I promptly dropped IPSec and moved to OpenVPN.) Might also work with the Null4 (127.0.0.1) entry?  Would have to try it. …ct
  • NRPE in pfsense 2.3

    22
    0 Votes
    22 Posts
    9k Views
    J
    Im using Check_mk, can it talk to this nrpe plugin?
  • Successfully monitoring a UPS connected to a Synology RS?

    25
    0 Votes
    25 Posts
    17k Views
    dennypageD
    Note that even if there were a way to override the fsd signal on the slave, it would be a bad idea because the signal generally indicates that the master is about to instruct the UPS to turn the load off.
  • FreeRADIUS XMLRPC sync not working automatically

    3
    0 Votes
    3 Posts
    2k Views
    J
    The "Authentication servers (e.g. LDAP, RADIUS)" checkbox under System > High Avail. Sync doesn't seem to have anything to do with the freeradius2 package because the package continues to try XMLRPC syncs even when that box is not checked.
  • NUT Package - UPS Load: 0%

    2
    0 Votes
    2 Posts
    1k Views
    dennypageD
    It appears that this unit is known to incorrectly report load as 0. http://networkupstools.org/ddl/APC/Back-UPS_ES_550.html
  • Whitelist domains on incoming WAN interface

    1
    0 Votes
    1 Posts
    1k Views
    No one has replied
  • 2.3.2-p1 regression - NUT will no longer start, config page is 404

    5
    0 Votes
    5 Posts
    1k Views
    dennypageD
    https://forum.pfsense.org/index.php?topic=115349.msg650408#msg650408
  • Any Spam Solution for 2.3.2?

    5
    0 Votes
    5 Posts
    2k Views
    jimpJ
    Then perform spam checking on the mail server(s) or use a separate VM/appliance for mail filtering, it's not the firewall's job. A spam-filtering MTA combination like postfix adds a gigantic attack surface to the firewall. Far too many moving parts that interact and could break in insecure ways.
  • Restarting OpenVPN with cron job

    6
    0 Votes
    6 Posts
    4k Views
    B
    I tried this command "/usr/local/sbin/pfSsh.php playback svc restart openvpn client 1" and now I can't login to the web interface, not even after restart. any tips for me? :P
  • Help for c-icap/e2guardian access.log rotation and low free memory

    2
    0 Votes
    2 Posts
    2k Views
    R
    @CBRom: /var/log/c-icap/access.log (that actually does not contain useful data) Hi. I've just been struggling to disable this file. It was receiving several lines of useless information every few seconds. The c-icap configuration file is located in /usr/local/etc/c-icap/c-icap.conf. You can edit it but, somehow, the webinterface replaces it while saving the configuration so this is what I (blindly) did. I'm sure there has to be a better way: Edit /usr/local/etc/c-icap/c-icap.conf.pfsense Locate the line AccessLog /var/log/c-icap/access.log Replace it with AccessLog /dev/null Go to Services/Squid Proxy Server and just save the configuration Check that both /usr/local/etc/c-icap/c-icap.conf.pfsense and /usr/local/etc/c-icap/c-icap.conf have the "AccessLog /dev/null" line Reboot the server (maybe restarting the icap service would be enough) Browse some site and check for modifications to the access.log file Regards.
  • Syslog-NG Package Broken after Update to Version 2.3.2

    3
    0 Votes
    3 Posts
    1k Views
    S
    What can be done about this?
  • Unable to install openvpn-client-export, wrong version

    4
    0 Votes
    4 Posts
    2k Views
    DerelictD
    Excellent. Glad it's working.
  • Minidlna on pfSense

    2
    0 Votes
    2 Posts
    2k Views
    johnpozJ
    Well for starters what are you interfaces called in pfsense.  From this error seems it can not even find the interface it wants to bind too "Network interface ath0 not found"
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.