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
  • How does snort performing the block action?

    Locked
    3
    0 Votes
    3 Posts
    2k Views
    G
    Thanks, and sorry about originally posting in the wrong area. Can you explain a little more or point me in the direction of where to look?  Is there any possibility of modifying the action to redirect the user to a remediation page or drop only the P2P traffic?  If we wanted to pay for support hours to cover the cost of developing this feature, how many hours would you estimate?
  • How to configure the auto detect squid proxy?

    Locked
    7
    0 Votes
    7 Posts
    7k Views
    S
    my wpad file looks like that as i don't want proxy for local and vpn servers maybe this can help you function FindProxyForURL(url, host) { // If IP address is internal or hostname resolves to internal IP, send direct.        var resolved_ip = dnsResolve(host);        if (isInNet(resolved_ip, "10.0.0.0", "255.0.0.0") ||                isInNet(resolved_ip, "172.16.0.0",  "255.240.0.0") ||                isInNet(resolved_ip, "192.168.0.0", "255.255.0.0") ||                isInNet(resolved_ip, "127.0.0.0", "255.0.0.0"))                return "DIRECT";        return "PROXY proxy.domain.lan:3128; DIRECT"; } maybe you could also check the webserver logs to see if your hosts grab the wpad file
  • Snort - How to Supress priority "3" events

    Locked
    3
    0 Votes
    3 Posts
    2k Views
    M
    Well, I am faced with the same problem. Therefore I dont dare to activate the blocking feature in pfsense snort. The only thing you can do is to go through ALL the rules an activate only those which are relevant to your network (i.e. disable rules for INFO, POLICY, and so on). If there are still alerts you have to add them to the suppress list and unblock affected hosts.
  • LCDproc problem. HD44780 in LPT

    Locked
    1
    0 Votes
    1 Posts
    2k Views
    No one has replied
  • (imspector-dev) Logging Facebook Chats to meet New Gov't Compliance regs?

    Locked
    11
    0 Votes
    11 Posts
    5k Views
    N
    @Metu69salemi: I think, that those use some kind of man-in-the-middle attack by using their own ssl-certificate. But not sure at all Yep. They MITM the traffic, which requires a trusted CA cert to be installed on the machines you want to capture data from.
  • Two Minor GUI related bugs in Squidguard.1.3_1 pkg v.1.9.1

    Locked
    1
    0 Votes
    1 Posts
    885 Views
    No one has replied
  • SqudGuard - Individual logging option not working

    Locked
    1
    0 Votes
    1 Posts
    887 Views
    No one has replied
  • Help mail report

    Locked
    4
    0 Votes
    4 Posts
    1k Views
    R
    hello ptt, I did but doesnt work.. :( I dont know where is the wrong… thanksss [image: alert.png] [image: alert.png_thumb]
  • [SOLVED] Snort not starting after removal of Nmap

    Locked
    1
    0 Votes
    1 Posts
    1k Views
    No one has replied
  • SIP preprocessor configuration (snort 2.9.2.3 pkg v. 2.5.1)

    Locked
    1
    0 Votes
    1 Posts
    1k Views
    No one has replied
  • Update to stunnel 4.54

    Locked
    1
    0 Votes
    1 Posts
    809 Views
    No one has replied
  • Help Installation Sarg

    Locked
    4
    0 Votes
    4 Posts
    1k Views
    R
    hello to everybody! i found solution…just reboot pfsense  :) thanks to everybody and in particular to marcellc
  • Squid install gone wrong?

    Locked
    11
    0 Votes
    11 Posts
    3k Views
    ?
    @extide: honestly you are probably best off doing a fresh install and re-loading your config. I got my box into a state once where the filesystem got messed up and even a factory reset did not fix it. In that situation the best move is probably just to do a clean install from ISO, and then apply your config. i actually ended up doing a fresh install before a reply was made.  i had the .iso i used inside the case of the computer and pfsense installed in 10 minutes (maybe less, i stepped away after the prompts).  i wanted to do a restore to see how well the backup config files worked and they worked well….worked as designed. i was a little disappointed that i didn't uncheck the box to save rrd graph info, but that wasnt a huge deal. however, i am still glad i got the info from marcelloc incase a package install doesnt go as planned, in the future.
  • - help - proxy filter -

    Locked
    5
    0 Votes
    5 Posts
    2k Views
    R
    Thanks marcelloc, but i did what u suggestion and I had same problem so after I checked better, I disabled (NOT TO ALLOW IP ADDRESS IN URL) and now I can watch video.  :) byee
  • Is pfsense meant to help with installing snort?

    Locked
    4
    0 Votes
    4 Posts
    1k Views
    M
    @cmb: Installing Snort from the packages adds the package via pkg_add, or PBI if 2.1, and has a GUI to set it up and manage. Thanks for your response. From a human-factors standpoint, it would be better to use a more explicit button on that page and move it into the leftmost column under the name of the package. The link attached to the name is a "garden path" trap:  it sets up expectations that it doesn't fulfill.  Since the person on that page might not have set up any rules at that point, the cryptic, monochromatic "+" button over on the right side is hard to even notice, never mind interpret, especially next to the eye-attracting column in white reversed out of what looks like #CC0000 red. Imagine how different the effect would be even just changing that description to black-on-white and reversing the button out of red instead. Generally speaking, it's a bad idea to use color where it can mislead.  There's no reason for the "description" column to be emphasised (the same righthand column is reversed out of red on other pages, too, with the same lack of meaning).  Color should only be used where it can't be misinterpreted (e.g., the menu bar, the page title) or where it focuses attention on something significant.  Because of how many people can't perceive color at the usual level of accuracy, the choice of a specific color should never be used to encode meaning (not that that's being done here). It would also be better to have the left column alphabetised.  Right now it's almost alphabetised, which sets up another incorrect expectation. Even the choice of greyscale on the packages page is hard to interpret.  The darker grey in the not-selected tab is "stronger" than the lighter grey, and therefore appears to be selected.  The standard for selected vs not-selected is to lower the contrast on the not-selected tab.  So both tabs should have the same background, but the text on the unselected tab should have a lower contrast with the background, in this case the grey of the es.
  • Snort 2.9.2.3 pkg v. 2.5.1 - 'ssl_state' error - unable to start

    Locked
    2
    0 Votes
    2 Posts
    2k Views
    T
    I have exactly the same problem - did you find a solution to this?
  • LCDProc and IPSec

    Locked
    2
    0 Votes
    2 Posts
    1k Views
    G
    Keep in mind LCDproc is almost a year old, and the support was made by an user, not from internal/dev personal.
  • Freeswitch and X100P PCI Card

    Locked
    2
    0 Votes
    2 Posts
    1k Views
    L
    http://www.hurdman.net/mirror/voip-info/tiki-index8ca4e3b6ac72bf72669a823dd6f99495.html?page=FreeBSD+zaptel x100 card is more trouble than it's worth especially if you want caller id etc far better with a tdm400 which will go straight away, is reliable and supports caller id etc
  • Notes added to 'things than can be synced' /pfsync?

    Locked
    1
    0 Votes
    1 Posts
    798 Views
    No one has replied
  • HOW TO: pfSense as a transparent IPS

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