Subcategories

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

    4k Topics
    21k Posts
    A
    I have been experiencing this issue for a while now, so it is nice to know the cause! I updated the redmine and posted screenshots of the issue. https://redmine.pfsense.org/issues/15274
  • Discussions about packages whose functions are Intrusion Detection and Intrusion Prevention such as snort, suricata, etc.

    2k Topics
    16k Posts
    S
    @bmeeks :( well thank you for your time, sir. 🫡
  • Discussions about packages that handle bandwidth and network traffic monitoring functions such as bandwidtd, ntopng, etc.

    571 Topics
    3k Posts
    K
    @pulsartiger The database name is vnstat.db and its location is under /var/db/vnstat. With "Backup Files/Dir" we are able to do backup or also with a cron.
  • Discussions about the pfBlockerNG package

    3k Topics
    20k Posts
    R
    @Gertjan s7.vonderste.in resolves to 94.16.122.152. I just saw a dns request for that. In the whitelist on OTX Alienvault there is a timeserver: 3.de.pool.ntp.org I just don't know why a timeserver runs on a TOR node and seems to be hosted by a private person. Maybe pfblocker resolves it incorrectly becaues the time server is hosted on the same IP? Anyway I see this coming from my ASUS router which is in Access Point mode. These weird domains always come up every hour and I think they are related to ntp on that ASUS router. Since I disconnected it it has stopped. Here is an example of what I see. Scanning these IPs shows nothing malicious but who knows. 93.122.215.85.in-addr.arpa,192.168.1.8,sonne.floppy.org,unk 94.244.38.46.in-addr.arpa,192.168.1.8,basilisk.mybb.de What didn't stop was on my work computer these weird replies as mentioned above. reply,A,NSEC,1081,domaincontroller-gPHvwjYS.local,192.168.1.86,NXDOMAIN,unk But it only happend once today instead of multiple times like the days before. @Gertjan said in pfBlockerNG not logging anything by default?: Where - what log - did you find that URL (DNS only deals with host names) ? I find them in pfblockerNG dns_reply log under Logs EDIT: I just realized that it is kind of in the name pool.ntp.org its made up of multiple sources so it does make sense that it resolves some of these weird private hosts?
  • 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

    493 Topics
    3k Posts
    GertjanG
    @EChondo What's your pfSense version ? The instructions are shown here : [image: 1753262126227-1acdc586-cb29-4148-9e36-81ade4e5e60c-image.png] A restart of a service will start by re creating their config files. If a certificate changed, it will get included. When the process starts, it will use the new certificate. @EChondo said in Issue with ACME Certificates Refresh & Restarting HAProxy: I haven't been able to confirm if the above works(mine just renewed, don't feel like doing it again just to test), so we'll see in 60 days I guess. No need to wait x days. You can re test / renew right away, as you are 'allowed' to renew a couple (5 max ?) of times per week.
  • 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
    594 Posts
    E
    @totalimpact Tailscale 1.54.0 is 2+ years out of date. Tailscale has made quite a number of changes since Tailscale 1.54.0, likely rendering it incompatible with their servers. I would consider manually updating the Tailscale FreeBSD package. FreshPorts does not maintain an archive of all the releases, only the latest compiled by the volunteer maintainers. The key to manually upgrading is knowing which FreeBSD version your pfSense release is running, i.e. 14 or 15. You can following along here.
  • Discussions about WireGuard

    692 Topics
    4k Posts
    M
    This is still an issue as of 2.8.0 / 25.07, and it drives me crazy. Gateway failure works as expected, the wireguard tunnels will fail over to the backup gateway and continue on as normal, but will never recover once the failed gateway comes back online. While a reboot will (usually) fix it, I usually just go into my routing settings and mark the secondary gateway as down, forcing it to revert back to the primary... the users tend to dislike it when I reboot the firewall in the middle of the day
  • Anyone successfully deployed WPA3 with Freeradius?

    3
    0 Votes
    3 Posts
    3k Views
    L
    @gertjan Ah, I forgot that say that everything works well in WPA2 mode. My setting is the same with the tutorial, I wonder if there’s any special requirement on WPA3 radius. Anyway, thank you for your help.
  • Which packages should I install?

    7
    0 Votes
    7 Posts
    2k Views
    LPD7L
    @michmoor Yes going to see if PFB will be the right solution, seems like squid would be a lot of overhead and not serve all current needs. Thanks for your input.
  • Packages unavailable when using IPv6

    2
    0 Votes
    2 Posts
    2k Views
    ?
    Performed a new test with Prefer IPv4 disabled and enabled and captured DNS queries Prefer_IP_Disabled_Enabled_DNS_queries.txt
  • Can't access LAN from wireguard tunnel.

    2
    0 Votes
    2 Posts
    1k Views
    4
    @4rt PLEASE DETELE I figured it out. Thanks anyway.
  • Zabbix6 agent & proxy

    2
    0 Votes
    2 Posts
    2k Views
    M
    Looks like this was added! Thanks!
  • Package updates don't restart services

    5
    0 Votes
    5 Posts
    2k Views
    P
    Thanks all for the explanation!
  • 1 Votes
    20 Posts
    4k Views
    viktor_gV
    Redmine issue created: https://redmine.pfsense.org/issues/13002
  • System Patches update on 2.5.2

    5
    0 Votes
    5 Posts
    2k Views
    jimpJ
    There is an update for System Patches on Plus 21.05/CE 2.5.2, even if your update branch is set to stay on Plus 21.05/CE 2.5.2. We put an update there to add the recommended patches list populated with important security and stability fixes for people who couldn't upgrade to 2.6.0 right away.
  • DynDNS updates deprecated ipv6 addresses, resulting in service disruption

    3
    0 Votes
    3 Posts
    2k Views
    S
    @bob-dig yes. I consider it normal after a forced disconnect, being offline for a couple minutes until the new prefix has propagated downstream and every system chose it's new address. This is a design issue in ipv6 as a whole, amplified by fraudulent ISP's. Downtime due to this is definitely longer than we remember from ipv4/nat. But that's not at all part of my topic. This topic is all about the dyndns script not working for ipv6.
  • is it conceivable to arrange numerous standards in SQuidGuard?

    1
    0 Votes
    1 Posts
    796 Views
    No one has replied
  • No packages available on multiple CE 2.6 devices

    13
    1 Votes
    13 Posts
    3k Views
    GertjanG
    Instead of manipulating IPv6 settings and impacting all local networks, what about informing the 'package update' scripts from pfSense to prefer IPv4 ? Have a look at /usr/local/libexec/pfSense-upgrade - line 24 That's just what we need. To implement : Goto line 1415 and change unset force_ipv4 to force_ipv4=1 So, instead of "let the system decide if IPv4 or IPv6 is used" the calls to the pkg commands are now instructed to use IPv4. Later on, undo the change or just forget about it as an update will take care of undoing it anyway. Btw : I had a console open, implement the change and used option 13 : Update from console. It took seconds to sync up and finish.
  • Dear PF users, what happened to SquidGuard blacklists web pages?

    2
    0 Votes
    2 Posts
    1k Views
    jimpJ
    There are not many people still maintaining lists for squidGuard. It's not so useful these days compared to other methods such as DNS based blacklists. Browsers are making it more and more difficult to safely and securely use a proxy for these kinds of tasks. The list at http://www.squidguard.org/blacklists.html used to have all of them, though I don't know how viable any of them are. It still lists Shalla even though that's gone, so the others may be questionable as well.
  • no menu updates after un-/installs of modules

    Moved
    1
    0 Votes
    1 Posts
    757 Views
    No one has replied
  • WireGuard can connect but has error in and out at Interface Statistics.

    1
    0 Votes
    1 Posts
    705 Views
    No one has replied
  • 0 Votes
    1 Posts
    1k Views
    No one has replied
  • FreeRadius, filter user with groups

    2
    0 Votes
    2 Posts
    3k Views
    E
    Some improuvment... It works but I am not satified! I put in the user filter (and desactivate the Group Membership part) : (&(uid=%{User-Name})(memberOf=cn=wifi,ou=group,dc=mydomain,dc=net)) => It work fine... only user in "wifi" group can be connected => I have to add the "menberOf" module in ladap I have know the following ldap/freeradius conf : ldap { server = "ldap.mydomain.net" port = "389" identity = "cn=admin,dc=mydomain,dc=net" password = 'xxxx base_dn = "dc=mydomain,dc=net" user { base_dn = "${..base_dn}" filter = "(&(uid=%{User-Name})(memberOf=cn=wifi,ou=group,dc=mydomain,dc=net))" } group { base_dn = "${..base_dn}" filter = '(objectClass=posixGroup)' } profile { filter = "(objectclass=radiusprofile)" } I think there is a better way... if some knows how ?
  • bind 9.16_13 - rndc delays

    1
    1 Votes
    1 Posts
    946 Views
    No one has replied
  • NMap scan GUI timeout fix

    1
    0 Votes
    1 Posts
    667 Views
    No one has replied
  • Cron-Package sort by time

    1
    0 Votes
    1 Posts
    612 Views
    No one has replied
  • squid / squidguard reliability

    6
    0 Votes
    6 Posts
    1k Views
    M
    @michmoor Thank you a lot for this clear answer, I will follow your advice for next questions.
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.