Subcategories

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

    4k Topics
    21k Posts
    L
    @KOM said in Squid: "Undefined symbol "_ZTVNSt3__117bad_function_callE" after upgrade to 2.8: I'm also not comfortable with the 'move lib somewhere else' fix as I don't know what side-effects it may have and I don't know how a future upgrade will handle it. I have two pfSense with longer upgrade history running, came across the same problem when upgrading to 2.8 and my thoughts were exactly the same. But then I was diving deeper and... The upgraded one, after the upgrade: # ls -l /usr/lib/libc++* -r--r--r-- 1 root wheel 9415736 May 22 03:19 /usr/lib/libc++.a -r--r--r-- 1 root wheel 48 May 22 03:19 /usr/lib/libc++.so -r--r--r-- 1 root wheel 819952 Jan 31 2022 /usr/lib/libc++.so.1 -r--r--r-- 1 root wheel 952 May 22 03:19 /usr/lib/libc++experimental.a The one still on 2.7.2 / FreeBSD 14: # ls -l /usr/lib/libc++* -r--r--r-- 1 root wheel 8603484 Dec 6 2023 /usr/lib/libc++.a -r--r--r-- 1 root wheel 48 Dec 6 2023 /usr/lib/libc++.so -r--r--r-- 1 root wheel 819952 Jan 31 2022 /usr/lib/libc++.so.1 -r--r--r-- 1 root wheel 87114 Dec 6 2023 /usr/lib/libc++experimental.a And last, but not least a stock FreeBSD 14.0 REL-p4: # ls -l /usr/lib/libc++* -r--r--r-- 1 root wheel 8579844 Nov 10 2023 /usr/lib/libc++.a -r--r--r-- 1 root wheel 48 Nov 10 2023 /usr/lib/libc++.so -r--r--r-- 1 root wheel 86778 Nov 10 2023 /usr/lib/libc++experimental.a As i see it, this libc++.so.1 as of 2022 must have been left back by an earlier update. Especially when looking at such a commonly used lib, I would speculate that the rm command used to remove it during this earlier update was using it itself and thus, was unable to remove it. Knowing this, I followed the recommendation to just remove it (or move it away to /root), rebooted and everything works fine. There is no need to un/reinstall squid. Just move away /usr/lib/libc++.so.1 and reboot. When updating from 2.7.2 or another FreeBSD 14 based release, it may also be an option to do this before starting the update to keep the downtime as short as possible. And, coming back to the concern quoted initially: I beleive that it is very unlikely that anybody will miss this old lib. Maybe somebody who upgraded an instance with less upgrade history can have a look in his /usr/lib and confirm that there is no libc++.so.1 at all.
  • 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
    T
    Ran into this issue today as well running on 25.07.1 with pfblockerNG-devel 3.2.7. Followed the steps outlined in this thread to edit the pfblockerng.sh file, then deleted/force reloaded all the lists, and all was well again. Thank you everyone in this thread for your your help and great instructions.
  • 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
    R
    @provels said in updating to acme 1.0 breaks system beyond repair: need to restore from backup: This same mess happened to me, even w/o Acme, going from 25.07 to *.1. Blew, reinstalled w/ Crowdsec, blew again, reinstalled, clipped all the Crowdsec info from config.xml, restored config, back to normal. Crowdsec is a great concept, but I think I'm out. I never had this issue with Crowdec before the ACME update, even with updating from 2.7 to 2.8 there was no issues. In fact after restoring from a backup after the ACME update, Crowdsec reinstalled just fine, and this was before the recent release a couple days ago that contained a fix.
  • 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
    606 Posts
    M
    @yobyot I've SSHed into pfsense and for the sake of testing I've simply run the command: tailscale up --auth-key=tskey-client-kQ_THE_REST_IS_A_SECRET\?preauthorized=true\&ephemeral=false --accept-dns=false --accept-routes --advertise-exit-node --advertise-routes=X.X.X.X/24 --advertise-tags=tag:pfsense Note the preauthorized=true and ephemeral=false I gave this key all permissions (temporarly as I just wanted to verify it's working) of course I had to register the tag used also in the ACL tags pane: https://login.tailscale.com/admin/acls/visual/tags so far so good
  • Discussions about WireGuard

    697 Topics
    4k Posts
    H
    I figured out the issue. I missed adding the 3rd locations Lan to the static routing. Now all is working perfect.
  • Reverse-squid OWA,activesync attachement problem

    1
    0 Votes
    1 Posts
    873 Views
    No one has replied
  • Tincd and nat

    4
    0 Votes
    4 Posts
    2k Views
    P
    well this worked.  thanks.  I forgot about the interface assign page…
  • Brain-dead postfix postscreen function

    6
    0 Votes
    6 Posts
    2k Views
    B
    If anyone is running postfix and doesn't find this too fugly ;) I found this about how to whitelist Google servers: Comparing the list of subnets to one seen in another thread (now lost) it seems they haven't changed in over a year.  Not too surprising, since they are pretty big subnets. Paste the following into Services > Postfix Forwarder > Access Lists > Client Access Lists > CIDR: # Google IPv4 addresses 64.18.0.0/20 permit 64.233.160.0/19 permit 66.102.0.0/20 permit 66.249.80.0/20 permit 72.14.192.0/18 permit 74.125.0.0/16 permit 173.194.0.0/16 permit 207.126.144.0/20 permit 209.85.128.0/17 permit 216.239.32.0/19 permit # Google IPv6 addresses 2001:4860:4000::/36 permit 2404:6800:4000::/36 permit 2607:f8b0:4000::/36 permit 2800:3f0:4000::/36 permit 2a00:1450:4000::/36 permit 2c0f:fb50:4000::/36 permit Haven't been able to find anything similar for HotMail but no one I know uses it anyway  :)
  • Lightsquid reports via email

    2
    0 Votes
    2 Posts
    2k Views
    jimpJ
    I've seen it done with mailreports before. You can use "/usr/bin/fetch -o - https://[…]" to include the contents of the page in the report, though I seem to remember that having a formatting issue of some sort.
  • How to install g729 on pfsense & asterisk

    2
    0 Votes
    2 Posts
    1k Views
    A
    friend succeeded in installing the codec? Thank!
  • Squid will not work at all

    2
    0 Votes
    2 Posts
    943 Views
    C
    Do you have a backup you can try to restore from? System -> Firmware -> Restore Full Backup or Diagnostics -> Backup/Restore
  • Install the full FreeBSD-GENERIC on pfSense 2.2

    3
    0 Votes
    3 Posts
    2k Views
    D
    Hello again  :) I've just improved to the procedure for installing Finch on pfSense. Now more resilient to upgrading of the pfSense host system. Before these changes, the Finch boot scripts could be wiped away after pfSense upgrade. Now, the only manual thing a user needs to do after upgrading pfSense, is restore their "fstab" file from a Backup. But it's very easy and full instructions are given. All new installation procedure is documented on Finch's website: http://dreamcat4.github.io/finch/install/ Other improvements: Better handling of admin user accounts. The presence of a temporary file "$finch_realpath/var/db/finch/installing…" now allows a simple way to query Finch's installation progress (i.e. "not installed, installing, installed"). (Useful for pfSense pkg makers).
  • Squid service stops on backup box when primary goes down

    1
    0 Votes
    1 Posts
    662 Views
    No one has replied
  • How to add snortsam on pfsense

    3
    0 Votes
    3 Posts
    1k Views
    bmeeksB
    @bmeeks: @magedtab: I tried to add snortsam to pfsense . snortsam 2.7 failed in installation i need the steps to install snortsam on pfsense thank you friends I'm pretty sure snortsam is not supported on pfSense, and the package has not been updated for quite a long time now.  So far as I know, the original creator/maintainer no longer visits the forums here. Bill
  • What is the difference between Suricata and snort ?

    2
    0 Votes
    2 Posts
    2k Views
    bmeeksB
    @firefox: I understand that they both IDS/IPS Daemon What is the difference between them ? Nothing really except two different vendors.  Snort is an open-source version of the IDS engine used by Sourcefire.  Suricata is a totally open-source effort partially funded by the U.S. Government and some private companies.  Well, technically Suricata is funded by the Open Information Security Foundation, but they get funding from the U.S. Department of Homeland Security and others.  Here is a link describing Suricata:  https://www.openinfosecfoundation.org/index.php/download-suricata.  Suricata is multi-threaded and should theoretically scale better in very high throughput networks.  However, extensive testing by the Snort guys and some independents shows there really is not much difference in the packet throughput in real-world networks between Snort and Suricata. In the end it comes down to personal preference.  Currently Suricata captures and logs a little bit more "context" around alerts, but Snort is catching up in this area. Bill
  • Squid3 disable caching and masking

    1
    0 Votes
    1 Posts
    630 Views
    No one has replied
  • Squid error page time difference

    1
    0 Votes
    1 Posts
    512 Views
    No one has replied
  • Snort/Barnyard2 interface via Stunnel

    2
    0 Votes
    2 Posts
    825 Views
    bmeeksB
    @wq6n: pfSense 2.1.3 Snort 2.9.6 Barnyard2 ? Stunnel 4.43.0 Unified2 feed from Snort remains constant on all sensors First off, thank you for such a great software security suite of tools. Pointing several Snort IDS sensors to a remote MYSQL server using a common port (lets call it TCP 3333). Created the Stunnel cert at the remote server using: openssl req -new -x509 -days 365 -nodes -config stunnel.cnf -out stunnel.pem -keyout stunnel.pem I did not create the Diffie-Hellman 'openssl gendh 512 >> stunnel.pem' as I did not see anything in the pfSense Barnyard2 configuration that suggested integration. However the other native Stunnel relationships do support the DH key. All Stunnel connections are in place and operational to the remote MYSQL server. I did have to go into the working pfSense Barnyard2.conf and append [port = 3333] to the MYSQL line. The remote Stunnel takes the incoming port TCP 3333 feeds and port forwards the data streams to the local TCP 3306 MYSQL listener. Restarting the Snort interface everything comes up and the remote end does see the incoming connection from the pfSense Snort application. My challenge is that Barnyard2 stops working and the connection is closed after a while. The Native feeds from the other remote Snort senors remain functional. Any ideas on keeping the Barnyard2 application running? Do you see any Barnyard2 related messages in the system log on the pfSense side?  The latest Barnyard2 binary seems to have a problem with multiple instances concurrently accessing the same SQL DB.  This usually manifests itself with a "duplicate key" error written to the pfSense system log. The fix, if you have this error, is to choose only one Barnyard2 instance to update the References table.  There is a checkbox to handle this on the BARNYARD tab in Snort. Bill
  • Blocking specific items on a web page?

    1
    0 Votes
    1 Posts
    523 Views
    No one has replied
  • Unable to determine IP address from host name for ….

    5
    0 Votes
    5 Posts
    7k Views
    E
    thank you rjcrowder for your time. I find the solution, the sites i got the massage was host in my vpn network and i should check the option "Disable DNS Rebinding Checks" at menu System->Advanced->Admin Access
  • Squid RealTime Log

    2
    0 Votes
    2 Posts
    728 Views
    C
    not really an answer but different developers built the packages. That is why Squid 2 doesn't have the real-time logging feature
  • Squid Authentication - Almost there…but not yet

    3
    0 Votes
    3 Posts
    2k Views
    G
    Final Update & Closing: My settings: LDAP base domain: cn=Users,dc=ads,dc=example,dc=local LDAP username DN attribute: samAccountName LDAP search filter: (&(memberOf=CN=InternetUsers,CN=Users,DC=ads,DC=example,DC=local)(sAMAccountName=%s)) AD structure: Container: Users > squid, test, administrator Other Containers (OU): OU Main             –- OU1 --- User1             --- OU2 --- User2 All these users have been added to security group (global) named InternetUsers and this group resides in the "Users" container. I am able to verify three users - test, squid, and administrator which are in Users container; but I am not able to authenticate User1 and User2 which are placed elsewhere in AD even though they are members of InternetUsers group. I conclude that the search is limited to one level only. So either I have to find a way to provide multiple Base Domain values, or find a way to make the search query recursive. Both would perhaps require me to directly edit the .inc file. I am not planning to do it and will leave it at that. I would rather create local users in Squid and now focus on learning SquidGuard. Thanks
  • Squidguard LOG and ERROR message

    4
    0 Votes
    4 Posts
    1k Views
    L
    this is solved. please close. thanks to all
  • Lightsquid Will Not Install

    2
    0 Votes
    2 Posts
    1k Views
    A
    Never mind, I figured out the problem… it was Snort getting in the way. I had disabled Snort as part of my routine checks; but forgot to clear the blocks it had put into place. ::) Once the blocks were cleared and with Snort temporarily disabled Lightsquid installed just fine. :)
  • Vhosts

    6
    0 Votes
    6 Posts
    4k Views
    N
    Every-time i reboot Pfsense the vhost configuration file is deleted, and must go to vhost service page and save the previous config to recreate the config file. Pfsense 2.1.3 i386
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.