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)
  • Schedule with squidguard

    2
    0 Votes
    2 Posts
    878 Views
    N
    not sure if is a squid problem or an very old pfsense bug that keep connection established before the off interval. you can try an experiment and manual clear the firewall states for that IP and check if he still have access.
  • FreeRadius2 Diffie-Hellman 2048 bit iOS9 OSX 10.11

    8
    0 Votes
    8 Posts
    2k Views
    N
    The miscalculated MPPE keys with TLS 1.2 issue has nothing to do with weak DH. The best solution for weak DH is to configure your cipher_list directive in FreeRADIUS to one of the following two. Where there is a desire to only support modern clients: "EECDH+ECDSA+AESGCM:EECDH+aRSA+AESGCM:EECDH+ECDSA+AES+SHA384:EECDH+aRSA+AES+SHA384:EECDH+ECDSA+AES+SHA256:EECDH+aRSA+AES+SHA256:EECDH+ECDSA+AES+SHA1:EECDH+aRSA+AES+SHA1:RSA+AES+SHA256:RSA+AES+SHA1" We can verify what this gives us via: openssl ciphers -v "EECDH+ECDSA+AESGCM:EECDH+aRSA+AESGCM:EECDH+ECDSA+AES+SHA384:EECDH+aRSA+AES+SHA384:EECDH+ECDSA+AES+SHA256:EECDH+aRSA+AES+SHA256:EECDH+ECDSA+AES+SHA1:EECDH+aRSA+AES+SHA1:RSA+AES+SHA256:RSA+AES+SHA1" And where there is a want/need for 3DES for compatibility for legacy clients (such as Windows XP), append RSA+3DES+SHA1 to the end of that string. This gives: "EECDH+ECDSA+AESGCM:EECDH+aRSA+AESGCM:EECDH+ECDSA+AES+SHA384:EECDH+aRSA+AES+SHA384:EECDH+ECDSA+AES+SHA256:EECDH+aRSA+AES+SHA256:EECDH+ECDSA+AES+SHA1:EECDH+aRSA+AES+SHA1:RSA+AES+SHA256:RSA+AES+SHA1:RSA+3DES+SHA1" Again, the resultant set of cipher suites can be seen via: openssl ciphers -v "EECDH+ECDSA+AESGCM:EECDH+aRSA+AESGCM:EECDH+ECDSA+AES+SHA384:EECDH+aRSA+AES+SHA384:EECDH+ECDSA+AES+SHA256:EECDH+aRSA+AES+SHA256:EECDH+ECDSA+AES+SHA1:EECDH+aRSA+AES+SHA1:RSA+AES+SHA256:RSA+AES+SHA1:RSA+3DES+SHA1"
  • MOVED: DNS Resolver

    Locked
    1
    0 Votes
    1 Posts
    589 Views
    No one has replied
  • Bind VIEWS -> access denied?

    2
    0 Votes
    2 Posts
    1k Views
    ?
    Hi! Solved it on my own! I had to set the "allow-query" to localhost and localnets. Even though this setting seems to be irrelevant as it is under the "Master Zone Configuration" part…. Now it is working fine! /KNEBB
  • Sshdcond - call to undefined function

    5
    0 Votes
    5 Posts
    991 Views
    A
    The documentation eventually led me to the bit about ALIX boards defaulting to 38400 BAUD. With my terminal set accordingly, I got a series of boot messages along the lines of: FreeBSD/x86 boot Default: 0:ad(0,a)/boot/kernel/kernel boot: PC Engines ALIX.2 v0.99m 640 KB Base Memory 261120 KB Extended Memory 01F0 Master 044A CF Card Phys C/H/S 7745/16/63 Log C/H/S 968/128/63 1  pfSense 2  pfSense F6 PXE Boot:  1 No /boot/loader FreeBSD/x86 boot Default: 0:ad(0,a)/boot/kernel/kernel boot: No /boot/kernel/kernel FreeBSD/x86 boot Default: 0:ad(0,a)/boot/kernel/kernel boot: No /boot/kernel/kernel FreeBSD/x86 boot Default: 0:ad(0,a)/boot/kernel/kernel boot: 2No 2 FreeBSD/x86 boot Default: 0:ad(0,a)2 boot: No 2 FreeBSD/x86 boot Default: 0:ad(0,a)2 boot: No 2 FreeBSD/x86 boot Default: 0:ad(0,a)2 boot: No 2 Which I loosely translated as "Well and Truly Dead - Give up now!". So I flashed a fresh image to the card and started over. But that's a whole new story for the Installations and Upgrades section…
  • Manually installing newer packages?

    4
    0 Votes
    4 Posts
    2k Views
    A
    Hello Roy I have SquidGuard working on a new install X700.  Message me if you have any questions. It's only been in 2 weeks but it seems to be running very well. Andy
  • What comes first?

    2
    0 Votes
    2 Posts
    1k Views
    bmeeksB
    Although not stated, I assume from the question and apparent rule GID:SID given in your post that you are asking about Snort.  First, are you sure your client's IP is still the same (just double-checking …  ;) ).  The settings that are important when using the Blacklist/Whitelist options of the IP REPUTATION preprocessor in Snort are PRIORITY and WHITELIST MEANING.  Of these, the most critical is WHITELIST MEANING.  It controls what happens to an IP that is on the whitelist.  If set to the default of "Unblack", then the IP is simply not immediately blocked and is instead routed through to be compared against all the other rules.  That means it is still possible one of the other rules might block the IP.  When set to "Trust", then the traffic from that IP is passed on and skips all other Snort rules.  This means no downstream Snort rules (on that interface) will block it.  This latter may be what you want if you implicitly trust that client.  If you change any of the IP REPUTATION preprocessor settings, be sure to manually stop and restart Snort on that interface using the GUI controls on the SNORT INTERFACES tab. Another possibility, if you are running Snort on multiple interfaces, is another Snort instance's rule nabbed your "trusted" client.  If that is the case, then you would need to adjust settings on that Snort instance as well to honor your trusted client. Bill
  • What happened to bluetack.co.uk?

    3
    0 Votes
    3 Posts
    3k Views
    M
    Thanks!
  • Syslog-ng package cannot be updated or uninstalled

    7
    0 Votes
    7 Posts
    1k Views
    D
    Just to get the info out - I had the same issue just now and reinstalling GUI component only helped - I was able to uninstall and then install Syslog-ng package again. Running full version - 2.2.4-RELEASE  (i386)
  • Safesearch does not work anymore after squidguard upgrade

    4
    0 Votes
    4 Posts
    1k Views
    E
    Thanks buddy it works
  • Miniupnpd Crash Report

    2
    0 Votes
    2 Posts
    791 Views
    D
    /usr/local/pkg/miniupnpd.inc is part of core pfSense install. https://github.com/pfsense/pfsense/tree/RELENG_2_2/usr/local/pkg
  • Tracking a package

    1
    0 Votes
    1 Posts
    571 Views
    No one has replied
  • MOVED: Squid 0.3.9.2 wipes web server list

    Locked
    1
    0 Votes
    1 Posts
    553 Views
    No one has replied
  • Postfix - config changes dont stick.

    4
    0 Votes
    4 Posts
    982 Views
    D
    Patch the source code if things are not configurable via the GUI, Luke… https://github.com/pfsense/pfsense-packages/tree/master/config/postfix
  • MOVED: squid 0.3.9.2 ICAP protocol error.

    Locked
    1
    0 Votes
    1 Posts
    1k Views
    No one has replied
  • PfBlocker - Need way to allow certain internal IP's to bypass rules

    2
    0 Votes
    2 Posts
    1k Views
    BBcan177B
    Did you select one of the "Rule Order" options in the General Tab?
  • 0 Votes
    4 Posts
    11k Views
    D
    Because PBI packages suck. Big time.  >:(
  • 'Lzma library error' trying to install bandwidthd on 2.1.5

    2
    0 Votes
    2 Posts
    1k Views
    D
    Probably means you should upgrade your pfSense.
  • Is arpwatch still supported in pfsesne 2.2.4?

    6
    0 Votes
    6 Posts
    2k Views
    D
    You are welcome…  ::) :o
  • MOVED: x-forward squid reverse Proxy

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