Subcategories

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

    4k Topics
    21k Posts
    J
    @qupfer What did I bang my head over this strange 502 issue. Your solution did it! Thank you so much, even 2.5 years later!
  • 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
    fireodoF
    @tinfoilmatt said in Failed or invalid Mime Type: [application/SIMH-tape-data|0]: (ASN data is IPinfo, not Maxmind) Thats correct but "GeoLite2-Country" is from Maxmind ... (that confused me) I'm considering simply adding "application/SIMH-tape-data" to the list to test. Thats what i tought too ... I'll try when I have the time for it ... Edit: I can confirm - adding "application/SIMH-tape-data" to the list at line 257 in /usr/local/pkg/pfblockerng/pfblockerng.inc did the trick - no more error! Edit: OK, problem resolved but I would like to know, whats the cause for that error! (SIMH-tape-data sounds like a "blast from the past" ...) Thanks a lot!
  • 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
    GertjanG
    @jimp Done. I was on acme.sh 1.0 (25.07.1) and a downgrade was proposed. Now, the issue is gone.
  • 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
    599 Posts
    S
    Upgraded to 25.07 and facing the same issue. Tried the "tailscale up" command as suggested above but restarting the tailscale service kills the login again.[image: 1755715824513-tailscale_logged_out_25_07.jpg]
  • Discussions about WireGuard

    695 Topics
    4k Posts
    R
    @Gertjan Hello, I installed the official app of vpn #1 on the crappy laptop but on the main laptop I did not install official app of vpn #2, I used it via wireguard. I am not worried about vpn #1 provider and how much they know about me. They already have my ip address since I connect to them direct. My goal is to hide from vpn #2. I don't want them to know I am the same person who used this service before. and thanks for the heads up regarding windows. I had a feeling that would come up. I know windows is spyware but for my purposes it doesn't matter since I really just need to make sure vpn #2 doesn't know this user is the same user who signed up last year. (ok yes I know, how do you know vpn #1 or #2 are not owned by ms? I agree, you dont know)
  • Dansguardian Weighted Lists doesn't work

    2
    0 Votes
    2 Posts
    957 Views
    marcellocM
    What you get on logs?
  • Postfix forwarder - quick start guide

    3
    0 Votes
    3 Posts
    6k Views
    B
    /your_domain_here/ REJECT [HELO01] marcelloc, Would it be sensible to add this as well? /127.0.0.1/ REJECT [HELO02]
  • Snort 2.9.5.5 pkg. v3.0.0 – Update Released

    67
    0 Votes
    67 Posts
    25k Views
    bmeeksB
    @BBcan17: Hi Bill, I have been going thru the Snort rules and disabling/Enabling the ones to suit my network and I came across a few ideas. My replies are below.  Thank you for the ideas.  Unfortunately, one of them I really don't think can ever work; however, the other two are possible. @BBcan17: Ability to create Multiple Snort Interfaces. Only one Interface per NIC would be online, the others could be offline.  It could also allow testing of Rulesets without compromising the Primary Interface settings. I think the template idea suggested by user Supermule is a way to accomplish this.  It sounds like what you are really talking about is a way to quickly switch on or off a group of rules for an interface. @BBcan17: The ability to Copy the "Snort Interface" to another pfSense Box. This would allow managing rulesets for several boxes with similar setups. This feature is available now thanks to user Marcelloc here on the forum.  He contributed the XML RPC sync part of Snort.  It is currently marked experimental, but in fact works quite well.  You can sync the Snort configuration across multiple boxes.  The one requirement for now is they must have the same NIC hardware so the real interface names match.  For example, em0, em1, etc.  I think the users currently making use of this sync feature are doing so on groups of virtual machines where the virtual hardware is identical. The template idea I mentioned above might also fill this need when implemented.  Maybe I can incorporate something into the template code that would handle automatically the change in real interface names. @BBcan17: In Global Settings, the option for "Remove Blocked Host Interval" could be set separately in each category so that we can better control how long the Block should last for. This one can't be done because it's not Snort that does the clearing.  Remember Snort is simply stuffing IP addresses into a pf table.  The table is called snort2c.  Once an IP is inserted there, it's the responsibility of the packet filter engine code to keep up with it.  The pf engine keeps a counter on "activity" by IP address.  In other words, it monitors the connections.  There is a cron job that the Snort package creates that calls the expiretable utility once per the interval you set (1 hr, 1 day, etc.).  The expiretable utility is given the pf table to clear and how many seconds of "no activity" must be in the stats for an entry to be removed.  The pf table has no way to store additional data about the IP address (such as what rule fired it, etc.).  This means Snort can't offer selective clear times based on rule origin. Bill
  • Snort rules will not update - pfSense noobie

    6
    0 Votes
    6 Posts
    2k Views
    ?
    As none other than Mr. Allan Jude himself would have said; "Patch your shit!". (not a personal attack in any way, shape and/or form. A strong suggestion to keep up to date with all software) As suggested, always upgrade to the latest versions of everything (I'll do my psychic voodoo and say the web app being protected is something based on a no longer maintained version of a webserver, quite possibly IIS). The proper procedure to upgrade is: First upgrade, then notify the customers of what's not working. A golden rule in my case. Any system running 1month old software (of which a new version has been available for the past 3 weeks) is to be considered compromised, no questions asked. A zeroing of the drive and,if it's UEFI*,  a new motherboard, installed with a newer version of the software is the only industry accepted practice to recover it. As soon as a new update is available, start testing it. You have 24 hours to update the production systems, or they are to be considered highly likely to be compromised and should be treated as hostile to other hosts on the network. My personal suggestion is to stop looking for ways to work around a 2 year old appliance and start downloading the new version. *there are ways to flash a pre-OS exploit on a motherboard, have been publicly available for the past year. Not publicly available, well that's another story  ;)
  • Squidguard Auto Blacklist Updating

    6
    0 Votes
    6 Posts
    3k Views
    C
    "if I am not completly wrong your cron job updates the blacklist every 10min" : i know, it was just for test with update blacklist. First time, when i installed pfsense 2.1 , i choose squid3 et squidguard for squid3 but i had many problemes (impossible reload of squid or squidguard for example). I installed and uninstalled them , reinstalled but i always had problems with them. This the reason i chose v2.02 and upgrade v2.1. I don't understand why squidGuard_blacklist_update.sh don't work completely with my version 2.02 and work with 2.1 without I do anything more best regards
  • Squid continuously ask me the upstream proxy password…

    1
    0 Votes
    1 Posts
    930 Views
    No one has replied
  • Apinger / openvpn nanobsd 2.1

    1
    0 Votes
    1 Posts
    761 Views
    No one has replied
  • Snort: edit ftp preprocessor configuration

    13
    0 Votes
    13 Posts
    5k Views
    D
    Bill thanks for your help. Yes I've checked the configuration file too. But now I think it's my bad. Sorry. Snort is running on WAN and DMZ interface. All my playing around with the FTP preprocessor setting I have done on the WAN interface, not thinking about that maybe I have to do this also on the DMZ interface. The Block list didn't gave me any infromation from which interface the block was set. I have now disables on both interfaces the FTP preprocessor and insert the custum setting on the bottom of the first side ON BOTH interfaces. Now I'm waiting for the result and will inform you shortly. Sorry again - my bad. best regards Frank
  • NRPE Monitoring CARP Status?

    2
    0 Votes
    2 Posts
    2k Views
    M
    I believe I ended up finding a solution.  I found a third-party bash script called check_carp_if that checks output of ifconfig to see if the VIPs are set as master or backup.  I added it to the /usr/pbi/nrpe-i386/libexec/nagios folder, made a couple of modifications to it to fix some broken paths, and voila, I now have an nrpe check that tells me for each box whether the VIPs are master/slave. I would have liked for this to be a module that was already built-in to the NRPE package so that I could minimize what needs to be done if I have to restore from backups to a new pfsense box, but c'est la vie.
  • Bug: Package Quagga_OSPF: startup after pfSense boot failed

    3
    0 Votes
    3 Posts
    2k Views
    R
    mmh, sorry. Our firewalls are running weeks/months without reboot since 2.1 is out and some reconfiguring is done… So I must see when I can help with more debugging... Do you have special logs for such case? I checked for ospf / zebra entries and found only these ones: /var/log/routing.log: Dec  4 12:53:55 fw2 ospfd[16271]: nsm_change_state(192.168.6.2, Loading -> Full): scheduling new router-LSA origination Dec  4 12:53:56 fw2 ospfd[16271]: DR-Election[1st]: Backup 192.168.6.12 Dec  4 12:53:56 fw2 ospfd[16271]: DR-Election[1st]: DR    192.168.6.2 Dec  8 11:17:15 fw2 zebra[23085]: Zebra 0.99.22.3 starting: vty@2601 Dec  8 11:17:15 fw2 ospfd[23308]: ASBR[Status:1]: Update Dec  8 11:17:15 fw2 ospfd[23308]: ASBR[Status:2]: Update Dec  8 11:17:15 fw2 ospfd[23308]: ASBR[Status:2]: Already ASBR Dec  8 11:17:15 fw2 ospfd[23382]: OSPFd 0.99.22.3 starting: vty@2604 Dec  8 11:17:15 fw2 zebra[23085]: client 17 says hello and bids fair to announce only ospf routes Firewall was rebootet /var/log/system.log: Dec  8 11:05:13 fw2 syslogd: kernel boot file is /boot/kernel/kernel Dec  8 11:05:13 fw2 syslogd: sendto: Network is unreachable … Dec  8 11:05:14 fw2 kernel: ifa_del_loopback_route: deletion failed Dec  8 11:05:14 fw2 kernel: ifa_add_loopback_route: insertion failed ... many of such del/add failures... ... Dec  8 11:05:27 fw2 php: rc.start_packages: Restarting/Starting all packages. Dec  8 11:05:31 fw2 php: rc.start_packages: XML error: SYSTEM or PUBLIC, the URI is missing at line 1 in /usr/local/pkg/iftop.xml Dec  8 11:05:31 fw2 php: rc.start_packages: XML error: SYSTEM or PUBLIC, the URI is missing at line 1 in /usr/local/pkg/iftop.xml Dec  8 11:05:33 fw2 php: rc.start_packages: XML error: SYSTEM or PUBLIC, the URI is missing at line 1 in /usr/local/pkg/ipmitool.xml Dec  8 11:05:33 fw2 php: rc.start_packages: XML error: SYSTEM or PUBLIC, the URI is missing at line 1 in /usr/local/pkg/ipmitool.xml Dec  8 11:05:37 fw2 php: rc.start_packages: [Squid] - Squid_resync function call pr: bp:1 rpc:no Dec  8 11:05:38 fw2 check_reload_status: updating dyndns WAN_TDSLGW Dec  8 11:05:38 fw2 check_reload_status: Restarting ipsec tunnels Dec  8 11:05:38 fw2 check_reload_status: Restarting OpenVPN tunnels/interfaces Dec  8 11:05:38 fw2 check_reload_status: Reloading filter Dec  8 11:05:38 fw2 check_reload_status: updating dyndns IPSec Dec  8 11:05:38 fw2 check_reload_status: Restarting OpenVPN tunnels/interfaces … Dec  8 11:11:40 fw2 php: rc.start_packages: Restarting/Starting all packages. Dec  8 11:11:44 fw2 php: rc.start_packages: XML error: SYSTEM or PUBLIC, the URI is missing at line 1 in /usr/local/pkg/iftop.xml Dec  8 11:11:44 fw2 php: rc.start_packages: XML error: SYSTEM or PUBLIC, the URI is missing at line 1 in /usr/local/pkg/iftop.xml Dec  8 11:11:46 fw2 php: rc.start_packages: XML error: SYSTEM or PUBLIC, the URI is missing at line 1 in /usr/local/pkg/ipmitool.xml Dec  8 11:11:46 fw2 php: rc.start_packages: XML error: SYSTEM or PUBLIC, the URI is missing at line 1 in /usr/local/pkg/ipmitool.xml Dec  8 11:11:50 fw2 php: rc.start_packages: [Squid] - Squid_resync function call pr: bp:1 rpc:no …
  • No packages?

    3
    0 Votes
    3 Posts
    909 Views
    jimpJ
    Your platform is still "cdrom". If you installed, you didn't eject the CD from the VM or adjust the boot order so that the HDD is first.
  • Squid 2.x + Dansguardian never ending webpage

    4
    0 Votes
    4 Posts
    1k Views
    marcellocM
    @grinderfurax: is there a tweak to check it ? It's during install. Or you can try this by you own risk 1. Boot server with FreeBSD or pfSense livecd 2. enable soft-updates using 'tunefs -n enable /dev/xxxx' 3. run fsck on / partition 4. reboot and check what you get with cmd mount on console/ssh -> /dev/ad0s1a on / (ufs, local, soft-updates)
  • Snort 2.9.4.6 pkg v. 2.6.1 cannot get VRT updates

    18
    0 Votes
    18 Posts
    4k Views
    bmeeksB
    @shpokas: "Problematic" one is fresh install :) Now I have discovered that symlink to /usr/local/bin/snort is gone  :-[ But that's not all. When I execute /usr/pbi/snort-i386/.sbin/snort, nothing happens. With switches or without, just nothing. Size of the file is the same as on the other machine where snort is working. Time to reinstall again. Will be back with update  8) [/quote] That really sounds like the PBI package manager is hosed up somehow.  The new 2.1 pfSense uses PBI packages that more or less put each installed package in its own chroot environment.  This way the packages can't interfere with each other's shared libraries and such.  As you have noticed, there should be a working symlink from /usr/local/bin/snort pointing to /usr/pbi/snort-i386/.sbin/snort.  If that symlink won't properly execute the command "snort -V", then that is what is wrong with the update process.  Can also be why Snort won't start properly either. Bill
  • CANNOT START BARNYARD..please help me!

    12
    0 Votes
    12 Posts
    4k Views
    bmeeksB
    @sinikel: Yeah, I read through all of your other posts.  Would be cool if the devs made a feature to allow us to add that src IP to the firewall rules section.. Again, thanks for all of your help!!! I might be able to do that from the Snort side by copying some functionality available from the Firewall Log page.  Not sure, as I have not investigated in detail; just thinking off the top of my head. Of course something like that might have limited usefulness because many times "bad actor host IP addresses" frequently change, so an IP block today may well be worthless tomorrow.  Or worse yet, if it was a dynamically assigned IP and now a "good guy" has it, he will be permanently blocked from your network.  Better in my view to use the automatic 1-hour clearing of Snort-blocked IPs.  You can set this on the Global Settings tab.  Right now, with the random early clearing of the block table, you may not see a true 1-hour interval, though. Bill
  • Varnish 3: Can't create director

    4
    0 Votes
    4 Posts
    1k Views
    marcellocM
    Sorry for the late reply. I've found the bug. It's fixed on 0.2.1
  • Squid 3.1.20 pkg 2.0.6 header issue?

    7
    0 Votes
    7 Posts
    3k Views
    marcellocM
    I'll include it on squi3-dev. Thanks for the feedback.
  • Postfix secure SMTP should use PFSense certs

    2
    0 Votes
    2 Posts
    1k Views
    marcellocM
    Post here your config modification. This way I can try to include on package gui.
  • P5-Mozilla-CA-20130114.tbz not avail on download site

    1
    0 Votes
    1 Posts
    834 Views
    No one has replied
  • Snort and Chinese attackers

    11
    0 Votes
    11 Posts
    4k Views
    ?
    Unless there are 5 zeros after a number, no government will bother with it. If tomorrow (or next week, since it's a weekend) pfsense starts selling for a 6 digit number, every single government on the entire planet will write laws requiring its use. Then there will be the "Security Experts" that studied "Information Systems Security" and took a couple of "Security in an Inter-connected World" seminars. Those insert a not-so-flattering comment here will come along, sign a contract for "Systems Support and Maintenance" and will take 3 years to install a patch. During those years every (as the saying here goes) dog will piss on the systems. Disclaimer: This paragraph has been an actual fact. A well known middle-East ISP, whose name shall not be mentioned, in order to protect the guilty, took 3 years to patch a damned system. In the meantime, every single username and password of every single customer was leaked on the internet. Anyone with a computer that knew how to download an exploit (ie most "hackers") was granted free access to it. Last time I checked, the list is still there. You can now understand why I sound so angry on these forums (usually) because I have to deal with the "Security Experts" that studied "Information Systems Security" and took a couple of "Security in an Inter-connected World" seminars, daily. For example last week I called a guy, which I'm sure has 20 years experience in IT. I can actually vouch,without ever talking to him before, that he is the best there is in this country. "Hi, this is ….. you talked with ..... to get a domain transfered. Have you prepared the domain for the transfer?" The 20-years-of-experience guy's response was "I don't need to prepare anything, you just initiate the transfer and I get an email to accept it." My response "no, actually the transfer will fail, unless the domain status is ACTIVE or OK. You can check it with a whois on the domain. Right now it says...clickety-click Registrar-lock. Can you please remove the transfer lock and get back to me?" A week later, and I'm still waiting for the "Expert" to remove a domain's transfer lock. A process which takes exactly 17 seconds to complete. sigh Nobody bothers with security or learning something new each day to be honest. Most "Experts" are happy to know how to turn on a system and get on fb and that's it. That actually makes them the very best there is in multiple countries, the geek-elite. I could go on all day, but it's getting off-topic. My apologies to the OP for going off-topic.
  • Snort Blocked Host

    2
    0 Votes
    2 Posts
    1k Views
    bmeeksB
    @jdeloach: Does Snort Block Hosts work? In Snort Interfaces, Alert settings, I have "Block offenders" checked.  Since I'm still learning my way around PfSense and it's packages, is there some other place that I need to enable something so Snort will block offenders or at least list them under the Block tab? I have several entries in Alerts but Blocked is always empty. Couple of things to check.  First, examine the IP addresses of the entries on the Alerts tab and see if they are part of any whitelist.  Snort automatically whitelists any locally-attached IP networks and the WAN interface IP and far-end gateway.  Second, it could be that the hosts are blocked but the "clearing the block table" issue discussed here frequently is removing them before you see them.  This refers to an issue that cropped up in the 2.1 release of pfSense where any thing that causes a reload of the firewall filter clears the Snort block table.  However, as has also been written about here on the Forum many times; clearing the block list is not a huge deal because the offending host will be "re-blocked" when more traffic is observed by Snort. Bill
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.