Subcategories

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

    4k Topics
    21k Posts
    A
    i am using pfsense 2.8.0 with haproxy 0.63_10 and i have 4 sites that redirect to two different web server, i am using two frontend, one for http request redirect to https using rule: scheme https, and a second with type ssl/https(tcp mode) to redirect the request with the acl and the action, now i want to add a new site to one of the web servers i create a new backend (and even tried duplicate) and add the proper acl and action as always did but for some reason since the update to 2.8.0 the redirect keeps going to the wrong backend, i tried a test and rewrote and old backend and updated the acl and rule in the frontend and it works fine, is there a known bug since the update because it keeps happening even after reboot to pfsense and the haproxy service and reinstall of the package.
  • Discussions about packages whose functions are Intrusion Detection and Intrusion Prevention such as snort, suricata, etc.

    2k Topics
    16k Posts
    cyb3rtr0nianC
    @rlrobs Yes it’s still working fine here.
  • 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
    I resolved this by accepting the T+Cs via https://www.maxmind.com/en/accounts/1205389/geolite2/eula
  • 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

    493 Topics
    3k Posts
    GertjanG
    @EChondo What's your pfSense version ? The instructions are shown here : [image: 1753262126227-1acdc586-cb29-4148-9e36-81ade4e5e60c-image.png] A restart of a service will start by re creating their config files. If a certificate changed, it will get included. When the process starts, it will use the new certificate. @EChondo said in Issue with ACME Certificates Refresh & Restarting HAProxy: I haven't been able to confirm if the above works(mine just renewed, don't feel like doing it again just to test), so we'll see in 60 days I guess. No need to wait x days. You can re test / renew right away, as you are 'allowed' to renew a couple (5 max ?) of times per week.
  • Discussions about the FRR Dynamic Routing package on pfSense

    294 Topics
    1k Posts
    J
    @div444 i'm finding the same - did you find a solution or did reverting fix it? Hoping there is a patch fix or something to get it working! Rather not rollback if i can avoid it
  • Discussions about the Tailscale package

    90 Topics
    578 Posts
    T
    Re: How to update to the latest Tailscale version? I am on latest released Netgate 6100 pfSense PLUS v24 ( pfSense_plus-v24_11_amd64-pfSense_plus_v24_11 ) pkg config abi FreeBSD:15:amd64 pkg -vv | grep -A 3 "pfSense:" pfSense: { url : "pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_11_amd64-pfSense_plus_v24_11", enabled : yes, priority : 0, cat /usr/local/etc/pkg.conf ABI=FreeBSD:15:amd64 ALTABI=freebsd:15:x86:64 PKG_ENV { SSL_CA_CERT_FILE=/etc/ssl/netgate-ca.pem SSL_CLIENT_CERT_FILE=/usr/local/etc/pfSense/pkg/repos/pfSense-repo-0001-cert.pem SSL_CLIENT_KEY_FILE=/usr/local/etc/pfSense/pkg/repos/pfSense-repo-0001-key.pem } This firewall is obviously running on FreeBSD 15 no longer on 14. But can I use the freshports link for FreeBSD 14 amd64 quarterly which is at tailscale 1.86.2 or can I only go up to version tailscale 1.84.2_1, and need to wait until they have a version of tailscale 1.86.2 or higher for the FreeBSD 15? Would it be good enough to tell it to ignore the OSVERSION? export IGNORE_OSVERSION=yes Note: use of 14 and not 15 ? pkg add https://pkg.freebsd.org/FreeBSD:14:amd64/quarterly/All/tailscale-1.86.2.pkg service tailscaled restart tailscale up
  • Discussions about WireGuard

    690 Topics
    4k Posts
    J
    I've read through some other posts about this, but they either didn't say whether the proposed solution worked or they were very convoluted and difficult to understand. Here is our scenario: We have 6 locations--Las Cruces (LC), Sunland Park (SP), El Paso (EP), Abilene (ABI), Fort Worth (FW), and Plano (PL). LC and ABI have software that is accessed by the other 4 locations via VPN. There are WireGuard VPNs set up between LC and those 4 locations (SP, EP, FW, PL), and ABI and those 4 locations (SP, EP, FW, PL). There is also a WireGuard VPN connection between LC and ABI. LC and ABI have 2 internet connections. SP, EP, FW, and PL each have one internet connection. If the primary internet connection goes down at either LC or ABI and failover occurs to the secondary internet connection, is there a way to set up the WireGuard VPN connections so that they also failover without purchasing some 3rd party application? Thanks.
  • Snort not capturing any events from internal NICS lan's

    Locked
    4
    0 Votes
    4 Posts
    1k Views
    T
    Hi, Just found out what was wrong , since the HTTP is routed to port 3128 with SQUID i had to fill out Define variable HTTP_PORTS 80 and 3128 now i have all alerts showing as used to Thanks
  • Connect squid3 to LDAP

    Locked
    1
    0 Votes
    1 Posts
    813 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
    947 Views
    No one has replied
  • Weird temporary problem with quagga routing

    Locked
    1
    0 Votes
    1 Posts
    835 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
    862 Views
    No one has replied
  • Need Help To make Snort working

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

    Locked
    1
    0 Votes
    1 Posts
    961 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
    5k 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
    2k 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.
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.