Subcategories

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

    4k Topics
    21k Posts
    J
    @JonathanLee use Pfsense 2.8.1.
  • Discussions about packages whose functions are Intrusion Detection and Intrusion Prevention such as snort, suricata, etc.

    2k Topics
    16k Posts
    DARAD
    Hello team, I have a Netgate 8200 running 24.11-RELEASE (amd64) with Suricata 7.0.8_5 package installed. Suricata doesn't seem to start. It loops to red once I press the Play button on the interface. It leaves no logs in the System logs, it leaves no logs in suricata.log at /var/log/suricata/suricata_ovpns933787/suricata.log I tried launching it manually: # /usr/local/bin/suricata -V or # /usr/local/bin/suricata -c /usr/local/etc/suricata/suricata_33787_ovpns9/suricata.yaml -i suricata_ovpns933787 and I get this output ld-elf.so.1: /usr/local/bin/suricata: Undefined symbol "__strlcpy_chk@FBSD_1.8" Thanks in advance, Dara
  • Discussions about packages that handle bandwidth and network traffic monitoring functions such as bandwidtd, ntopng, etc.

    573 Topics
    3k Posts
    dennypageD
    @kabeda If memory serves, that old version of ntopng did not run as user ntopng, but as user nobody. There are lots of problems in that old version. Anyway, check the ownership and permissions of /var/db/ntopng and make sure it matches the user that ntopng runs as. You may need to set ownership of the entire hierarchy. Example: /usr/sbin/chown -R nobody:nobody /var/db/ntopng However, the better choice would be to upgrade to a more recent version.
  • Discussions about the pfBlockerNG package

    3k Topics
    20k Posts
    tinfoilmattT
    @vicking said in No blocks on IP: Is it a bad idea to have the action set to deny both instead of inbound only? Question is squarely for admin. Per the infoblock which explains, in part, the "Deny Inbound", "Deny Outbound", and "Deny Both" actions: 'Deny' Rules: 'Deny' rules create high priority 'block' or 'reject' rules on the stated interfaces. They don't change the 'pass' rules on other interfaces. Typical uses of 'Deny' rules are: Deny Both - blocks all traffic in both directions, if the source or destination IP is in the block list Deny Inbound/Deny Outbound - blocks all traffic in one direction unless it is part of a session started by traffic sent in the other direction. Does not affect traffic in the other direction. One way 'Deny' rules can be used to selectively block unsolicited incoming (new session) packets in one direction, while still allowing deliberate outgoing sessions to be created in the other direction. In other words: When set to "Deny Inbound", incoming connection requests from WAN hosts are blocked and therefore no state will be created. However a LAN host can still establish state to an otherwise listed IP. If set to "Deny Outbound", outgoing connection requests from LAN hosts are blocked and therefore no state will be created. However an incoming connection request from an otherwise listed IP to an 'open' WAN port can still establish state. If set to "Deny Both", both incoming connection requests and outbound connections requests are blocked and therefore no state will be created regardless of connection direction.
  • Discussions about Network UPS Tools and APCUPSD packages for pfSense

    102 Topics
    3k Posts
    C
    @dennypage Nicely done sir!
  • Discussions about the ACME / Let’s Encrypt package for pfSense

    503 Topics
    3k Posts
    M
    I am using the DNS-Update method I have to use a DNS-Sleep of 5 minutes to let the letsencrypt txt dns record update propagate. During this 5 minutes the acme-webgui times out. when the acme-webgui times out the Action list is NOT executed. How can I solve this ? Would it maybe be an idea to let the acme.sh script execute the actions in the action list as a post-hook instead of the web-gui? Or maybe add an option to add post-hooks in the webUI ?
  • Discussions about the FRR Dynamic Routing package on pfSense

    296 Topics
    1k Posts
    C
    This one has been tricky still not sure what to try. Any ideas?
  • Discussions about the Tailscale package

    93 Topics
    654 Posts
    C
    @luckman212, Thanks for your suggestion. I will check what I have in /usr/local/pkg/tailscale/state, and also the RAM disk settings others have brought up. I could learn more about where Tailscale and pfSense store system files. If I find anything worth sharing, I will let you know.
  • Discussions about WireGuard

    715 Topics
    4k Posts
    H
    @RNM-0 Thanks for your comment and sharing your fix. Unfortunately I don't want to take down pfsense and downgrade versions. I'm currently fine at the moment since I'm using Tailscale and that works. I also fixed the other crash I was having with pfblocker by changing a line code that wasn't pushed out under this version. Hopefully the stable release won't take too long to release but it appears there's still some open bugs that need to be fixed before that happens, and ironically, both the pfblocker and wireguard issues aren't on that list of bug fixes.
  • Connect squid3 to LDAP

    Locked
    1
    0 Votes
    1 Posts
    822 Views
    No one has replied
  • Snort, Variables tab, Define Ports Error

    Locked
    4
    0 Votes
    4 Posts
    2k Views
    bmeeksB
    Well, if the rule itself is hard-coded, then you are not protected unless you manually change the rule.  If the rule, for example, said something like $FTP_PORTS instead of "21", then you would be protected.  Unfortunately we are somewhat at the mercy of the rule writers from both Emerging Threats and Snort VRT. So it sounds like in your particular case, you might be better off using the default FTP port instead of an alternate one.  The only other fix I can think of would be to manually edit the affected rules, but then at the next rules update you would have to do it again. Bill
  • Freeradius2+SQLite in pfsense

    Locked
    1
    0 Votes
    1 Posts
    956 Views
    No one has replied
  • Weird temporary problem with quagga routing

    Locked
    1
    0 Votes
    1 Posts
    839 Views
    No one has replied
  • Squid3 RealTime monitoring…!!!

    Locked
    1
    0 Votes
    1 Posts
    1k Views
    No one has replied
  • HAVP issue

    Locked
    1
    0 Votes
    1 Posts
    885 Views
    No one has replied
  • Need Help To make Snort working

    Locked
    1
    0 Votes
    1 Posts
    740 Views
    No one has replied
  • HaProxy in reverse

    Locked
    1
    0 Votes
    1 Posts
    981 Views
    No one has replied
  • Squidguard blocking valid sites

    Locked
    3
    0 Votes
    3 Posts
    1k Views
    S
    No sorry, already tried that and it didnt work… If i may add, this seems to happen only in IE. Chrome works fine.
  • SARG Reports can not be displayed

    Locked
    5
    0 Votes
    5 Posts
    6k Views
    S
    I'm having issues with sarg reports too. Also my realtime view stopped working since i updated to the latest 2.1 beta yesterday. I was on 2.0.2 before and at least the realtime view was working. but now with 2.1 beta i can get havp + squid working, so I think there's some tweaking for the realtime view to work again with taht new configuration, not sure.
  • Problem SquidGuard + Blacklist updates - Filter Fails after update script

    Locked
    8
    0 Votes
    8 Posts
    6k Views
    D
    I am concerned about the "Exit Code 127" errors.  I cannot find a definition for that error and I have tried running the commands by hand, but do not get those errors.
  • SQUIDGUARD SGERROR PAGE FOR HTTPS/SSL HOW?

    Locked
    5
    0 Votes
    5 Posts
    2k Views
    M
    the same rule is valid also for http but sgerror page is displayed my rules just prevets bypassing proxy and block direct connect to http, https or ftp . clients can access theese protocols if they use proxy
  • Siproxd for server behind firewall

    Locked
    5
    0 Votes
    5 Posts
    1k Views
    X
    the problem is the port, currently it allows only listening to one port and to truly make it work would need some work
  • 0 Votes
    3 Posts
    3k Views
    D
    I just confirmed - the alarm FAILS to trigger a filter update for ANY time crossing even though the SquidGuard log shows that the alarms are being calculated: 2013-03-05 14:02:43 [25967] squidGuard ready for requests (1362513763.536) 2013-03-05 14:02:43 [26036] squidGuard 1.4 started (1362513763.329) 2013-03-05 14:02:43 [26036] Info: recalculating alarm in 737 seconds 2013-03-05 14:02:43 [26036] squidGuard ready for requests (1362513763.558) 2013-03-05 14:02:43 [26132] squidGuard 1.4 started (1362513763.689) 2013-03-05 14:02:43 [26132] Info: recalculating alarm in 737 seconds 2013-03-05 14:02:43 [26132] squidGuard ready for requests (1362513763.764) VERIFIED: The change FAILS for both ON/OFF transition and OFF/ON transition.
  • Quagga OSPF bug: no redistribution networks are written in wrong order

    Locked
    10
    0 Votes
    10 Posts
    7k Views
    R
    @rubic: @jimp: That may be a completely separate error from this. I think the error is this commit related. While Quagga OSPF 0.99.20.1 v0.5.0 works fine in my production environment, in my fresh test setup with Quagga OSPF 0.99.20.1 v0.5.1 any value in the "Disable Redistribution" field prevents the service to start. Ah this way I can try it, too: [2.1-BETA1][root@fw1.zws8.local]/root(134): /usr/local/bin/quaggactl start There is no such command. Error occured during reading below line.   distribute-list dnr-list out connected mmmh… I've tested my patch and it worked with several config modifications/reboots in my test setup... so a little surprising that it's now damaging OSPF package... sorry. Without my above fix it works again. router ospf   ospf router-id 192.168.6.3   log-adjacency-changes detail   redistribute connected   redistribute static   network 192.168.6.0/24 area 192.168.6.0   distribute-list dnr-list out connected   distribute-list dnr-list out kernel   distribute-list dnr-list out static   access-list dnr-list deny xx.xx.176.0/24   access-list dnr-list permit any One problem / unknown difference: I have one stable/old pfSense 2.0.1 pair and actual pfSense 2.1-BETA1 pair on other side… The stable version didn't redistribute the network: [2.0.1-RELEASE][root@fw1.jws1.local]/root(133): vtysh Hello, this is Quagga (version 0.99.20.1). Copyright 1996-2005 Kunihiro Ishiguro, et al. fw1.jws1.local# sh ip route Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF,       I - ISIS, B - BGP, > - selected route, * - FIB route K>* 0.0.0.0/0 via 91.102.12.193, lagg0_vlan2 O  xx.xx.176.0/24 [110/20] via 192.168.6.12, lagg1_vlan6, 00:31:09                             via 192.168.6.13, lagg1_vlan6, 00:31:09 C * xx.xx.176.0/24 is directly connected, vip47 C>* xx.xx.176.0/24 is directly connected, lagg0_vlan7 C>* xx.xx.176.4/32 is directly connected, vip40 C>* xx.xx.176.7/32 is directly connected, vip49 … but BETA does? [2.1-BETA1][root@fw1.zws8.local]/root(139): vtysh Hello, this is Quagga (version 0.99.21). Copyright 1996-2005 Kunihiro Ishiguro, et al. fw1.zws8.local# show ip route Codes: K - kernel route, C - connected, S - static, R - RIP,       O - OSPF, I - IS-IS, B - BGP, A - Babel,       > - selected route, * - FIB route K>* 0.0.0.0/0 via xx.xx.176.254, lagg0_vlan7 O  xx.xx.176.0/24 [110/20] via 192.168.6.13, lagg0_vlan6, 00:24:14 C * xx.xx.176.0/24 is directly connected, opt14_vip120 C * xx.xx.176.0/24 is directly connected, opt14_vip117 C * xx.xx.176.0/24 is directly connected, opt14_vip103 C * xx.xx.176.0/24 is directly connected, opt14_vip119 C * xx.xx.176.0/24 is directly connected, opt14_vip118 C * xx.xx.176.0/24 is directly connected, opt14_vip116 C * xx.xx.176.0/24 is directly connected, opt14_vip115 C * xx.xx.176.0/24 is directly connected, opt14_vip114 C * xx.xx.176.0/24 is directly connected, opt14_vip109 C>* xx.xx.176.0/24 is directly connected, lagg0_vlan7 … I tested before only with BETA versions… and got problems with public routing. (1st firewall pair got .1/.2/.3, 2nd fw pair .254/.253/.252) Because without this "Disable Redistribution" of this public network the firewalls didn't saw itselfes and therefore shutting down their gateways. ah... different BSD package versions which causes the problem: 2.0.1        => Hello, this is Quagga (version 0.99.20.1). 2.1-BETA1 => Hello, this is Quagga (version 0.99.21). so please remove my patch… and we must search for other places to patch the behavior in package for 2.1... Thanks. Bests Reiner
  • Problem whit squidGuard

    Locked
    19
    0 Votes
    19 Posts
    7k Views
    K
    Reinstalling the xml worked at least in one installation. Thx!
  • Install squid 3.3

    Locked
    4
    0 Votes
    4 Posts
    3k Views
    W
    I have been able to build squid 3.3 on a FreeBSD 8.3 machine and it seems to work ok with a few minor changes.  Even working with squidguard. Needed a few things like the ssl-bump-server-first feature and dynamic certificate generation, plus the request_header_add option. I've been attempting this http://support.google.com/a/bin/answer.py?hl=en&answer=1668854 but haven't quite managed it yet. I built the squid32 port which pulled all the build dependencies then built 3.3.1 from source.
  • How to manually install squid + squidguard

    Locked
    2
    0 Votes
    2 Posts
    1k Views
    K
    What's wrong with it using squid custom options?!
  • Snort blocks WAN IP….!

    Locked
    20
    0 Votes
    20 Posts
    12k Views
    S
    Thats a good question… It has been a long journey with Snort since it has a lot of problems with PfSense. You helped to make the package significantly better and that helped a lot! A fair guess would be after we had the last discussion and I implemented your fixes.
  • How to backup and restore FreeRadius users.

    Locked
    4
    0 Votes
    4 Posts
    4k Views
    T
    Thank you. I found it. Thanks.
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.