Subcategories

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

    4k Topics
    21k Posts
    N

    Can I use pgblockerng aliases in Haproxy?

    80758505-9bad-4dad-a80b-c159be1045a2-image.png

    If it was a firewall rule, typing pfb would produce a dropdown to select.

    Here it has to be written, but will it work? Is it supported?

  • Discussions about packages whose functions are Intrusion Detection and Intrusion Prevention such as snort, suricata, etc.

    2k Topics
    16k Posts
    bmeeksB

    I saw where the Netgate kernel developer updated the Suricata package in the pfSense 25.07 development branch to work with the new kernel PPPoE driver. But so far as I know that updated package has not been migrated to 2.8 CE.

    Here is the commit into the DEVEL branch: https://github.com/pfsense/FreeBSD-ports/commit/68a06b3a33c690042b61fb4ccfe96f3138e83b72.

  • 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
    M

    @Laxarus This worked for me as well. Though I had to search the web how to edit the file (the easiest way).

    Therefore:

    Addition for anyone struggling to find where to edit files on your pfsense system.

    Go to Diagnostics --> Edit File --> insert the location of the file:

    /usr/local/pkg/pfblockerng/pfblockerng.sh

    Go to line number 1232 by filling it in the Go to line field.

    That line should read:

    s1="$(grep -cv ^${ip_placeholder2}$ ${masterfile})"

    replace only (leave the rest intact):

    masterfile

    to

    mastercat

    Then follow the above instructions from @Laxarus https://forum.netgate.com/post/1219635

  • Discussions about Network UPS Tools and APCUPSD packages for pfSense

    99 Topics
    2k Posts
    K

    @elvisimprsntr thanks for your suggestion. I will give it a try.

  • Discussions about the ACME / Let’s Encrypt package for pfSense

    493 Topics
    3k Posts
    johnpozJ

    @MacUsers

    https://help.zerossl.com/hc/en-us/articles/360060119933-Certificate-Revocation

    edit: oh you prob out of luck

    You can revoke any certificate issued via the ZeroSSL portal. Currently, certificates issued via ACME can not be revoked from inside the portal - please follow the instructions of your ACME client for revoking those certificates.

    the gui in pfsense does not have the ability to revoke - you prob have to move the certs to something you have certbot installed to and revoke that way.

  • Discussions about the FRR Dynamic Routing package on pfSense

    294 Topics
    1k Posts
    R

    I had a similar issue with Routed VTI over IPsec recently. FRR lost its neighbors after rebooting or when a tunnel went down. It never re-discovered it automatically. Only restarting FRR (either in GUI or via CLI) brought the neighbors back.

    When I manually added those under the OSPF neighbors tab in the GUI it seems to solve the problem as well.

  • Discussions about the Tailscale package

    88 Topics
    572 Posts
    A

    We have a very basic configuration between three locations. All are running Netgate firewalls (1x 4100, 1x 6100 & 1x 4200). All are on the latest firmware (03.00.00.01-2Ct-uc-15) and system versions (24.11-RELEASE).

    The local subnets are as follows:
    4100 - 192.168.5.0/24
    4200 - 192.168.4.0/24
    6100 - 192.168.1.0/24

    The VPN traffic between the 4100 and 4200 is functioning 100% as expected

    The traffic between 6100 and the 4100 works going from the 4100 subnet (192.168.5.0/24) to the 6100 subnet (192.168.1.0/24)

    Traffic from the firewall (i.e. the 6100 device) to the 4100 subnet works (i.e. I can ping any device on the 192.168.5.0/24 subnet from the 6100 firewall) but I cannot ping any device on the 4100 (192.168.5.0/24) subnet from any device on the 6100 subnet (192.168.1.0/24) - other than from the firewall itself.

    All routes are correct, but it seems that traffic from the 192.168.1.0/24 subnet hits the firewall and then gets lost - traceroute shows that it goes off into the internet.

    Note too that the 6100 has IPsec VPN configured on it as well

    Suggestions would be appreciated

    Attached is a zipped pdf file with the relevant screenshots
    Relevant screen shots.zip

  • Discussions about WireGuard

    689 Topics
    4k Posts
    P

    @patient0 Thanks for further suggestions. The tunnel is definitely up and so I don't think this is a CGNAT issue after all. WAN firewall rule is in place for UDP on port 51823 (otherwise the tunnel wouldn't work, right?). I can ping from client 1 -> client 2 and visa versa and also ping all points in between like you suggest. I just can't open an HTTPS connection from pfSenseB from Client 1 using a browser. But I can do this the other way round i.e. from Client 2 to pfSenseA

    I will try and do some packet capture to see if that reveals anything.

  • Re: 2.2-RELEASE now available!

    2
    0 Votes
    2 Posts
    579 Views
    jimpJ

    Not that I'm aware of

  • Urgent Issue : BANDWIDTHD failed to boot up pfSense

    8
    0 Votes
    8 Posts
    3k Views
    W

    Same here, new install, bandwidthd error.

    Installed the 2.2 upgrade on another machine and it got hosed, won't reboot….

    ugh.

  • Snort fails on 2.2

    5
    0 Votes
    5 Posts
    2k Views
    W

    Yup, I just rebooted and reinstalled and it installed fine.  It also started snort fine too.

    Thanks!

  • Upgraded to Squid3-dev, now traffic is being blocked

    2
    0 Votes
    2 Posts
    814 Views
    marcellocM

    What you get on access.log and cache.log?

    Setup looks fine…

    ... acl safeports port 21 70 80 210 280 443 488 563 591 631 777 901 2083 3128 3127 1025-65535 21-65535 acl allowed_subnets src 192.168.1.0/24 http_access allow allowed_subnets http_access allow localnet
  • 0 Votes
    9 Posts
    4k Views
    B

    I am going to have to give up and accept that I have to get a more powerful system to do this.  I tried reducing the size of the shallalist.tar.gz to only what I want.  But for some reason, while it appears that the databases are being updated, they apparently are not as the blacklist.files file does not exist as it should per this log entry.

    klist_update.sh: The command '/bin/cp -f -p /tmp/squidGuard/arcdb/blacklist.files /usr/pbi/squidguard-i386/etc/squidGuard' returned exit code '1', the output was 'cp: /u6/etc/squidGuard/blacklist.files: Read-only file system'

    I also do not appear to be able to hack the config files to make it work.  You guys did too good of a job at securing this thing down.

    Thank you for your help.  At least now I know.

  • Updating to snort 3.9.7/3.2.2 breaks snort

    6
    0 Votes
    6 Posts
    1k Views
    bmeeksB

    @lshiry:

    … I found a workaround for this by killing the process "/bin/sh /usr/local/etc/rc.d/snort.sh start", which returns to the install script so it can complete the rest of its tasks.  After that, snort was in the services menu.  It was not started, but at least I can manage it now.  Thanks for the help, got me looking in the right direction.  Perhaps a fix for this would be to implement some sort of keepalive in the install php page, or background the service start step so it can complete.

    Thanks for the information on how you solved it.  Something got hung up in that sub-process on your box.  You are not the only one to experience the issue, but the number who have is quite low (maybe 3 or 4 that I can recall).  The install process calls a system function to execute that shell script.  I will look into it some more.

    Thanks,
    Bill

  • Sarg Stops After 10 Minutes

    7
    0 Votes
    7 Posts
    1k Views
    marcellocM

    what squid version are you using?

  • Snort: log: VLAN message on LAN?

    5
    0 Votes
    5 Posts
    1k Views
    M

    @bmeeks:

    No, the Promiscuous Mode feature has been in Snort since the beginning.  It is something the underlying binary controls and not the GUI package.  Since you say you have done a complete fresh install from the ground up, are you absolutely positive that all the pfSense settings are exactly the same as before?  Was perhaps your VLAN formerly associated with a different interface?

    Bill

    Thank you Bill  ;D

    No, it is completely 100% the same. I meticulously created screenshots of all settings, and setup everything again, fresh, by hand according to these screenshots :-[

  • SquidGuard 1.9.10 problem

    9
    0 Votes
    9 Posts
    2k Views
    D

    @KOM:

    Just curious, but why do you need to stop it?  Just disable it.

    +1
    SquidGuard may be only disabled. Otherwise Squid will crash.

  • Bandwidthd problem

    48
    0 Votes
    48 Posts
    50k Views
    T

    Edit: found info on 2.2 problems here: https://forum.pfsense.org/index.php?topic=84642.0

  • [Resolved] pfBlocker logs?

    2
    0 Votes
    2 Posts
    2k Views
    B

    Nevermind, I think I found what I'm looking for. Under status->system logs->firewall I can see all blocked connections. I'm not 100% sure I'm seeing pfBlocker kills here, but I think I am because I'm seeing some blocks on outbound connection attempts to Netherlands (a country I blocked) (no, I don't have kazy, it's a damn Kaspersky IP).

  • Package for daily and montly traffic

    8
    0 Votes
    8 Posts
    1k Views
    KOMK

    Is it better to put the tracking to the VLAN or the WAN Interface?

    That depend on what it is you're trying to measure.  Total bandwidth in/out would require WAN if you have multiple vLANs.  If you have just the one vLAN and no others then I suspect it doesn't make any difference.  It's just adding up all bytes going in/out of the specified interface.

  • Ha proxy-devel client certificates optional

    2
    0 Votes
    2 Posts
    686 Views
    P

    When creating this i choose to do it like this and allow for using acl's like 'SSL client certificate valid.' to be used for selecting the normal backend, or redirecting to a custom 'error' backend. Ill have to re-check if it actually works like i intended (i don't actually use it myself)..
    It does seem that i forgot to implement the 'none' option which can be selected for a , which i intended to allow for switching between 'optional' and 'required'.

    Thanks for your sharing your opinion and experience with haproxy-devel, it will take me a while before i get to this though. Put your item on my list of items to check/improve. Thanks.

  • Squid 3 Reverse Proxy Help

    4
    0 Votes
    4 Posts
    1k Views
    J

    I've had issues with reverse proxy (which typically publishes internal servers over HTTP and HTTPS ports 80 and 443) when the web configurator itself is also listening on one of those ports. Nowadays, I change the port the pfSense web configurator listens to as a rule of thumb - anything really as long as it's not 80 or 443. You could try that and see if it helps?

    Refer to "TCP port" under System | Advanced menu on where to change it.
    Remember that you would then need to specify that port number in the URL in your browser to access the pfSense web configurator.

    Also, have a look at the "DNS Rebind Check" option (also under the System | Advanced menu).

  • TFTP Server

    1
    0 Votes
    1 Posts
    739 Views
    No one has replied
  • 0 Votes
    2 Posts
    2k Views
    KOMK

    I just went through this same exercise a few weeks ago.  Nice job.  The only things I would suggest would be for you to clean up some of the inconsistencies.  For example, it's pfSense, not pfsense or PFsense.  Facebook, not facebook.  HTTPS, not HTTPs.  Squid, not SQUID.  SquidGuard, not SQUID Guard.  WPAD, not Wpad.  Prerequisites ordered list has unbold #2.  Your guide would be more universal if you didn't assume that they had an AD network.  I might instead host the WPAD file on pfSense itself as per their guide:

    WPAD Autoconfigure for Squid

    Good job, though.

  • Simple Squidguard question - Google Ads - Can't believe I can't find this

    6
    0 Votes
    6 Posts
    2k Views
    E

    For google I have set these two entries:

    googlesyndication.com 0.0.0.0 Block Advertising
    googletagservices.com 0.0.0.0 Block Advertising

    This also takes care of any subdomain like "pagead.googlesyndication.com" for example.
    I found in another topic that people advised to use "host" entries, this however was not working for me.

    Important, you have to set pfsense dns server to 127.0.0.1 and clients have to use pfsense exclusively as a dns server.
    To achieve this, I've made a firewall rule to block all other dns servers (port 53) and only allow the pfsense box as a dns server for clients.
    This works wonders, I absolutely hate ads.

    Cheers.

  • Snort 2.9.7.0 pkg v3.2.1 Update Release Notes

    22
    0 Votes
    22 Posts
    6k Views
    C

    Hello,

    I tried to get OpenAppId working, but it doesn't want to…

    My snort is working, VRT & OpenAppId rules are downloaded. VRT alerts appear.
    I followed this tutorial : https://forum.pfsense.org/index.php?topic=84227.0
    When I go to reddit, nothing is logged in alerts. Nothing useful in the firewall logs neither.

    I'm running pfsense 2.1.5 with the latest version of snort.

    Any idea ?

    Thanks !

  • Bug on squid reverse proxy

    3
    0 Votes
    3 Posts
    904 Views
    K

    squid3 3.1.20 pkg 2.1.2

    which part do u want? its huge… the problem appears when i add a cache_peer, example code in squid.conf is like this:

    #192.168.84.101 cache_peer 192.168.84.101 parent 80 0 proxy-only no-query no-digest originserver login=PASS round-robin name=rvp_HTTP-101

    all the mappings start using that peer, until i assing the peer to a mapping, then it start working as it should…

  • Squid3-dev transparent…again

    2
    0 Votes
    2 Posts
    749 Views
    marcellocM

    It works.

Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.