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 create new GrayLog Extractors v21.02_1?

    3
    0 Votes
    3 Posts
    2k Views
    C
    @beachbum2021 I used this one. It seems to only be missing snort. https://github.com/jbsky/graylog
  • Client Export Can't Locate "the Requested Certificate"

    Moved
    9
    1 Votes
    9 Posts
    2k Views
    C
    @jimp Fixed!
  • iperf3 won't automatically restart after reboot

    7
    0 Votes
    7 Posts
    2k Views
    S
    @sgseidel, Understood. I just posted into the developer forum asking for some assistance in getting started to setup a development environment, how to build pfSense packages and that. I am hopeful that I will get some guidance and then move forward in improving the pfSense implementation of iPerf3. Stuart
  • Patches package gone from 2.5.2 branch??

    14
    0 Votes
    14 Posts
    2k Views
    Cool_CoronaC
    @bcdouglas [image: 1667942055758-a77176e9-98be-4909-84d9-d182f3597f01-billede.png]
  • HAProxy 301 Redirect

    9
    0 Votes
    9 Posts
    2k Views
    V
    @johnoatwork Dude, you have two ACLs in this single rule which are mutually exclusive! So this rule cannot work at all. www.example.net - requires that the host name includes "www.example.net" aclcrt_SharedFrontendHTTPS - requires that the host name includes "example.com" Both will never match to the requested host. So remove the second ACL from this rule.
  • HAProxy php error after devel-update

    1
    0 Votes
    1 Posts
    556 Views
    No one has replied
  • PfSense 2.0.3 OpenVPN Client Export Utility config file name

    4
    0 Votes
    4 Posts
    4k Views
    B
    @jimp after so many years, searching in the forum came to this post. I need to rename the config file for the export, to be more clearly named. Is there any way to have it in the Additional configuration options ?
  • ntopng Ghost hosts?

    3
    0 Votes
    3 Posts
    1k Views
    M
    @deanfourie did u ever find out? i would also like to understand this as i have the same issue
  • ntopng not displaying properly on firefox

    3
    0 Votes
    3 Posts
    816 Views
    bingo600B
    @jsbsmd Seems to work fine on FF linux Mint [image: 1667415375155-07784cef-4a8f-4098-a9f0-86003f39a945-image.png] [image: 1667415388069-9e22f710-27cb-44d7-a513-cda8552f1c58-image.png]
  • openvpn client import can't import tls-crypt info

    1
    0 Votes
    1 Posts
    612 Views
    No one has replied
  • OpenVPN/Freeradius issue

    1
    0 Votes
    1 Posts
    615 Views
    No one has replied
  • Suricata does not start the interface

    6
    0 Votes
    6 Posts
    2k Views
    bmeeksB
    @fox95 said in Suricata does not start the interface: but what does work, is deleting the interface each time you want to make a change to the value because if you don't whatever new value you enter makes no difference. this was the original posters best advice. You should not have to delete the interface. I suspect what is actually happening is the stale PID file is preventing Suricata from starting with the new stream memcap value. Each time Suricata tries to start, the daemon creates a PID file in /var/run/ on pfSense. But due to the stream memcap error, the startup of the daemon is aborted and it fails to clean up after itself (leaving the now "stale" PID file). Simply go delete that file and it should start fine (once you get it happy with the stream memcap value). Notice the original error the OP posted about: 24/11/2019 -- 12:08:14 - <Error> -- [ERRCODE: SC_ERR_INITIALIZATION(45)] - pid file '/var/run/suricata_bce11963.pid' exists but appears stale. Make sure Suricata is not running and then remove /var/run/suricata_bce11963.pid. Aborting! It is complaining about the leftover PID file. Simply deleting that referenced file will let it start. The reason deleting the interface appears to work is that each time an interface is created, a new UUID is also created. So that 11963 number that is part of the file name will change when a new interface is created, and therefore the daemon will not detect an "existing" file matching the new UUID.
  • 0 Votes
    4 Posts
    1k Views
    S
    and then its just suddenly worked, typical technology. Thanks for the info!
  • 0 Votes
    2 Posts
    880 Views
    provelsP
    Yes, system patches is for seldom issued bug fixes between releases. But it doesn't cost you anything to install, and will be there should you need it.
  • PHP Error openvpn-client-export sice update to pfSense 2.7

    3
    0 Votes
    3 Posts
    1k Views
    T
    @bmeeks Thanks, I opend a corresponding Ticket https://redmine.pfsense.org/issues/13570
  • This topic is deleted!

    1
    0 Votes
    1 Posts
    4 Views
    No one has replied
  • This topic is deleted!

    1
    0 Votes
    1 Posts
    11 Views
    No one has replied
  • log alert

    10
    0 Votes
    10 Posts
    1k Views
    GertjanG
    @norvik-it Ah, ok, nice example of taking care of a sick person with a shotgun. I use pfBlockerng-devel with dnsbl myself. It's web server doesn't "stop" like that every minute. The PID is here (according to the info found in the pfBlockerng-devel lighty webserver config file here /var/unbound/pfb_dnsbl_lighty.conf ) : /var/run/dnsbl.pid The process number is in that file : does it really stops every minute ? All the others : SquidGuard, ntopng iperf ClamAV ICAP are part of the 'do not belong on a firewall anyway (my opinion). I've installed this 'Service Watchdog' package and added a task : [image: 1665136084300-d9a1111e-b619-4028-9580-7a90f6642019-image.png] Unselecting the notification box will stop sending you mails. The issue is now a bit solved. Next step : check if the service is really stopped. And if so, why / by who / what reasons ?! Example : [22.05-RELEASE][admin@pfSense.xxxxx.net]/root: cat /var/run/dnsbl.pid 4622 [22.05-RELEASE][admin@pfSense.xxxxx.net]/root: ps ax | grep '4622' 4622 - S 0:00.02 /usr/local/sbin/lighttpd_pfb -f /var/unbound/pfb_dnsbl_lighty.conf 35843 1 S+ 0:00.00 grep 4622 So the process running. If all these process are really killed on your system every minute, I can advise you to do one thing : Remove / disable all these packages. Or, as stated above, find the reason why they are dying on your pfSense, or are getting killed. Remove the issue for each of them. Example : if free RAM gets low, the system will kill processes, this is known as the OOM (Out Of Memory) event. Restarting them in that case is a really bad idea.
  • Alias Match vs Native

    1
    0 Votes
    1 Posts
    549 Views
    No one has replied
  • openvpn-client-export - naming openvpn client config

    2
    0 Votes
    2 Posts
    928 Views
    V
    @ppcm The export bundle is an self-extracting 7-zip. You can simply open it with the 7-zip FM and rename the .ovpn file.
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.