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
  • This topic is deleted!

    1
    0 Votes
    1 Posts
    4 Views
    No one has replied
  • [Haproxy-devel] GZIP-Compression?

    3
    0 Votes
    3 Posts
    3k Views
    C
    Hello, Is there an updated step by step way to do this? It is unclear if things have been changed since this original post was made but there isn't an apparent way to do this. Thanks in advance!
  • CRON job - calling URL

    3
    0 Votes
    3 Posts
    1k Views
    M
    @rcoleman-netgate THANK YOU :) That did the trick
  • Netgate SG-1100 unable to install packages

    8
    0 Votes
    8 Posts
    1k Views
    R
    @spectre-988 said in Netgate SG-1100 unable to install packages: I've been working on using the device at my home for a HA fail over device. I've got the device to become part of the HA but when the primary wants to sync the packages they aren't able to due to packages not being installed. I try to install myself but package manager just sits at waiting for the update system to initiate. I am not sure if the version of Pfsense I am using is the problem or the Bios. I know both are older and tried to update Pfsense version and get that the system is on a later version than the official release. Without physically separated interfaces the 1100 is not suited for HA. It could do it, sure, but the WAN, LAN, and OPT are all the same NIC in the system, just VLAN'd to a switch. Your expectations should be very tempered -- failover cannot happen based on physical disconnection and is going to be unreliable.
  • Zabbix Uncaught Error

    5
    0 Votes
    5 Posts
    1k Views
    J
    Hi, The solution it'a in this link: https://github.com/rbicelli/pfsense-zabbix-template/pull/118 I hope help somebody.
  • This topic is deleted!

    1
    0 Votes
    1 Posts
    69 Views
    No one has replied
  • HAproxy can only connect to "Default Backend"

    1
    0 Votes
    1 Posts
    856 Views
    No one has replied
  • Tailscale - package request / work opportunity

    2
    0 Votes
    2 Posts
    2k Views
    J
    @returntrip https://youtube.com/watch?v=Fg_jIPVcioY
  • HAProxy - route by domain name

    haproxy acl
    2
    0 Votes
    2 Posts
    1k Views
    N
    @nasheayahu said in HAProxy - route by domain name: wwwkohanyimcom Host matches: no no www.kohanyin.com kohanyimcom Host contains: no no kohanyin.com I found the problem, my domain was spelled incorrectly...
  • How to get tcptraceroute, or a functional equivalent

    3
    0 Votes
    3 Posts
    1k Views
    E
    I know that this question is old, but it actually helped me getting tcptraceroute on opnsense. The key thing was pkg add from freebsd. So for me it needed to be updated since I am on freebsd:13:amd64, I found https://freebsd.pkgs.org/13/freebsd-amd64/ with search :) So for me the resulting command was: pkg add http://pkg.freebsd.org/FreeBSD:13:amd64latest/All/tcptraceroute-1.5beta7.txz Still same version of tcptraceroute 2 years later, but it is how to find the package name that is important So thanks for this thread.
  • Wireguard Works only when OpenVPN Running in 2.6.0

    1
    0 Votes
    1 Posts
    660 Views
    No one has replied
  • 22.05 upgrade - site-to-site wireguard broken

    2
    0 Votes
    2 Posts
    1k Views
    J
    @buzz2912 Sounds like; https://forum.netgate.com/topic/173074/22-05-upgrade-breaks-remote-access-openvpn/15 same problem.
  • stunnel won't start

    2
    0 Votes
    2 Posts
    845 Views
    N
    Nvm im dumb... didn't read this line: [!] Service [Wireguard_SSL]: Protocol not supported
  • Freeradius limit access

    7
    0 Votes
    7 Posts
    2k Views
    G
    @mcury Thanks but this doesn't work in the users file. I think it's very restricted in what sort of entries can be made :(
  • pfSense+ 22.05/Wireguard dependency not documented

    Moved
    15
    0 Votes
    15 Posts
    2k Views
    B
    @jimp Ok. So I took a few minutes and there's somthing I'm not getting. When the Update setting is set to 22.05 the Package Manager shows two updatable packages, WireGuard 0.1.6_1 and ipsec-profile-wizard 1.0_4. [image: 1656626435886-screenshot-22.05.png] And much to my surprise, when the Update setting is set to 22.01, I see one updatable package WireGuard 0.1.6_1 !: [image: 1656626445074-screenshot-22.01.png] Is this correct? Is WireGuard 0.1.6_1 supposed to work on 22.01, or not? Upgrading WireGuard to 0.1.6_1 is the action that took down WireGuard in our NH router. Here are the messages from the NH log that appear to describe the problem: Jun 27 21:12:15 kernel linker_load_file: /boot/modules/if_wg.ko - unsupported file type Jun 27 21:12:15 kernel KLD if_wg.ko: depends on kernel - not available or version mismatch What's wrong?
  • bind no longer running after pkg/pfsense updates

    4
    0 Votes
    4 Posts
    1k Views
    S
    @dvl Great. Option 2 would have been to reinstall and restore from backup. The upgrade thing catches lots of people. I put it in my sig a while back. One such problem is when the package is dependent on a PHP version that doesn't exist in the older pfSense, so it gets upgraded. There's a redmine to hopefully fix it or at least block/warn people.
  • Bind upgrade producing errors on pfsense 2.5 upgrade

    112
    4 Votes
    112 Posts
    34k Views
    A
    Well one issue with the move to the new version. Previously bind was installed on my /cf now it is in /var/etc/named/etc/namedb/ a side effect, is whenever the router is restarted all my keys specified as global option will vanish include "/etc/namedb/acme-keys.key"; include "/etc/namedb/ddns-key-inf.key"; include "/etc/namedb/ddns-key-sec.key"; include "/etc/namedb/ddns-key.key"; An idea would be to save them in the pfsense configuration.
  • WebUI takes forever to load if UPS unreachable...

    Moved
    8
    0 Votes
    8 Posts
    1k Views
    J
    @dennypage said in WebUI takes forever to load if UPS unreachable...: I am assuming that the host running the NUT sever is using a fixed IP address, yes? And in the NUT config on pfSense, are you using the IP address (rather than hostname) to identify the NUT sever? Yep, my whole network is based around fixed IP's, either both on the machine and dhcp server or only in dhcp server. And yes pfsense connects via IP. @dennypage said in WebUI takes forever to load if UPS unreachable...: You might want to consider moving to using pfSense as the NUT sever and having the other host as a client. NUT on pfSense is very stable. Well my room is kinda limited because of the network cabling, the pfsense box and the UPS is on the opposite end of my room. Would require a 5 meter+ cable to connect the 2. Thats why i opted for a dedicated box and ATM this problematic box is the only one i can use. Done a few things to it including installing intel-microcode package and seems to be stable now ( knocks on wood ).
  • System -> Patches results in 404 after 22.05 upgrade from 22.01

    Moved
    5
    0 Votes
    5 Posts
    1k Views
    V
    @jimp Thanks that worked. It seems like the install process did not recognize that the Patches package was there and re-installed it. But left the menu option in place. [image: 1656510068927-420937b5-a131-4cd4-9c3e-8450d18f77e7-image.png]
  • PF, FreeRadius and SQL

    1
    0 Votes
    1 Posts
    828 Views
    No one has replied
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.