Subcategories

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

    4k Topics
    21k Posts
    J
    @andrew_cb ChatGPT had the right idea but gave me 100 different places to put "load-server-state-from-file none". Your post was worth more than ChatGPT could ever offer!
  • Discussions about packages whose functions are Intrusion Detection and Intrusion Prevention such as snort, suricata, etc.

    2k Topics
    16k Posts
    JonathanLeeJ
    @bmeeks your work outclasses so many individuals and developers. Your stuff is amazing. Cheers
  • Discussions about packages that handle bandwidth and network traffic monitoring functions such as bandwidtd, ntopng, etc.

    572 Topics
    3k Posts
    keyserK
    @Antibiotic No it’s not possible with NtopNG as it is not a Netflow collector. You need nProbe for that which will “translate” recieved netflows into flows that NtopNG understands and can visualize (with very very little detail might I add as Netflows has no additonal information apart from sender/reciever and volume). The NtopNG package and the product in general is more geared towards visualising and recording traffic details from actual packet captures. This contains MUCH more metadata about the sessions than netflows (DNS names, protocol information and myriads of other things). But pffSense Plus has a builtin Netflow exporter if you have an external netflow collector on hand.
  • Discussions about the pfBlockerNG package

    3k Topics
    20k Posts
    johnpozJ
    @High_Voltage I don't think there is anything to do.. Pretty sure those are the defaults.. When you query pihole for something that is blocked.. By default it returns some sort of answer - I am not aware of a setting that would wait for a timeout. [image: 1757768975895-blockmode.jpg] So I really have no idea he would of been doing. If something is blocked in pfblocker you would either get back the vip (so you could see a block page) or you would get all zeros. Same goes for pihole - I am not aware of a setting that would just time out and not send an answer if you asked for something that was blocked. The only reason pihole would time out on sending you a response is what you were asking for actually just never responded to pihole. If some fqdn you were asking for was being blocked you would get the answer almost instantly. If pihole was forwarding to unbound which I believe is a common sort of setup for stuff that is not blocked. Again if pfblocker was blocking it, you for sure should get a response right away of either the vip or all zeros. Its possible maybe pihole doing rebind protection, and pfblocker handing back the rfc1918 of your vip maybe causes pihole some sort of hangup, but normally when that happens it just returns a null to the client since it got an answer, it just not suppose to hand it back to the client.. But again no time out. Only time I could see a timeout issue is when unbound didn't answer the pihole, again if something unbound doesn't get an answer from how its resolving/forwarding. Maybe he was sending back nodata, and the client didn't take that as an answer and kept asking for the same thing until it gave up?
  • 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

    501 Topics
    3k Posts
    A
    Hi, Please help to forward / report the bugs in ACME 1.0 package. Thanks.
  • Discussions about the FRR Dynamic Routing package on pfSense

    295 Topics
    1k Posts
    J
    Anyone else happen to notice that when configuring BFD, if you create a peer and select a profile - after save, re-edit the peer and the Profile is not represented. It appears as "None". You have to check the raw config to determine if the profile was actually assigned to the peer. This is on 2.8.1 (all packages up to date as of the date/time of this post). UPDATE: if re-edit and save (without re-configuring the profile none to what you want) - the save will strip the profile from the peer.
  • Discussions about the Tailscale package

    91 Topics
    611 Posts
    T
    Hi All, I use HAProxy to redirect to a range of https internal resources, this works really well at the moment through the WAN where I have source limits set up, and I can connect to the internal resources from limited external IP Addresses. Given I have tailscale I would like to basically be able to put custom dns entries in to point these hostnames to my pfsense tailscale IP4 address (100.89.148.118) but I am not having any luck getting this working. At the moment, I am just trying to connect to HAProxy using https://100.89.148.118 but it is getting blocked by the firewall. Sep 11 11:55:58 tailscale0 Default deny rule IPv4 (1000000103) 100.89.148.10:53148 100.89.148.118:443 TCP:S I have tried with and without NAT redirecting internally to 127.0.0.1, and I also have rules set up to allow any traffic to and from my tailnets (defined in an alias) but I still keep getting these connections from my other tailscale machines being blocked on the pfsense machine. Can someone give me some pointers on what I am missing because I can see the requests are coming through to the pfsense machine, and in theory the rules should allow it through but I cant see why they don't. I do have tailscale ACL in place, but clearly that is not an issue as the requests are making it through to the firewall. 0/0 B IPv4+6 TCP/UDP TailNets * TailNets * * none Allow across Tailnets 0/0 B IPv4+6 TCP/UDP * * * 443 (HTTPS) * none Allow Tailscale IP4 I also tried adding a EasyRule but because the tailscale0 interface doesn't exist in pfsense it throws an error and won't let me add that rule. Appreciate any help or tips, Cheers.
  • Discussions about WireGuard

    702 Topics
    4k Posts
    P
    Yes
  • Dashboard Widget: Snort Alerts pkg v0.3.6 Update

    4
    0 Votes
    4 Posts
    1k Views
    bmeeksB
    @denningsrogue: Installed but the changes don't save. Try adding the widget first, then click the SAVE button for the Dashboard itself.  After that, go back into the Snort Alerts widget, click the wrench icon in the upper right, enter a number of rows to display and then click Save in the Alerts widget.  See if that works.  It did for me.  For some reason, trying to enter and save a value at the same time you add the widget to the Dashboard failed with a session state error. Bill
  • Windows Activation

    3
    0 Votes
    3 Posts
    2k Views
    D
    Thank you very much! I made exception such as *microsoft.com. Everything is fine. Unfortunately direct links doesn't work, because IE don't understand CRL lists. Thanks again
  • 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
    939 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
    911 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
    845 Views
    No one has replied
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.