Subcategories

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

    4k Topics
    21k Posts
    E
    I even tried deleting and creating a new certificate. Any suggestions?
  • Discussions about packages whose functions are Intrusion Detection and Intrusion Prevention such as snort, suricata, etc.

    2k Topics
    16k Posts
    S
    @Smeg.Head I'd think the main question would be whether it's a one-off or reproducible. Obviously that situation isn't correct but it's a question of why, and I haven't seen any other recent posts about it. Was the install done on 2.7.2 or is it older? I don't recall offhand when the bug was, but I'd guess 5-8 years ago.
  • Discussions about packages that handle bandwidth and network traffic monitoring functions such as bandwidtd, ntopng, etc.

    572 Topics
    3k Posts
    keyserK
    @Antibiotic No it’s not possible with NtopNG as it is not a Netflow collector. You need nProbe for that which will “translate” recieved netflows into flows that NtopNG understands and can visualize (with very very little detail might I add as Netflows has no additonal information apart from sender/reciever and volume). The NtopNG package and the product in general is more geared towards visualising and recording traffic details from actual packet captures. This contains MUCH more metadata about the sessions than netflows (DNS names, protocol information and myriads of other things). But pffSense Plus has a builtin Netflow exporter if you have an external netflow collector on hand.
  • Discussions about the pfBlockerNG package

    3k Topics
    20k Posts
    tinfoilmattT
    @BiloxiGeek said in DNSBL and IPv6: Does it just follow the IPv4 address that is listed above that? In my case it would end up being ::10.0.0.86 Yes. In this specific context that's the notation being used. (Full IPv6 web server address, for reference then, would be: http://[0000:0000:0000:0000:0010:0000:0000:0086]) Nota bene: I use 0.0.0.0 which renders the DNSBL webserver useless and inaccessible, but otherwise returns 0.0.0.0 or ::/NOERROR answers to all blocked lookups.
  • 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

    501 Topics
    3k Posts
    A
    Hi, Please help to forward / report the bugs in ACME 1.0 package. Thanks.
  • 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
    610 Posts
    E
    Updated CE 2.7.2 to 1.86.4_1 Changelog pkg add -f https://pkg.freebsd.org/FreeBSD:14:amd64/latest/All/tailscale-1.86.4_1.pkg Freshports
  • Discussions about WireGuard

    700 Topics
    4k Posts
    Bob.DigB
    @HFADmin said in Wireguard Multi VPN Tunnels: Can I have the main pfsense monitor all the gateways That is the default.
  • 0 Votes
    4 Posts
    7k Views
    N
    CP on pfsense 2.0.x does not support encrypted passwords in freeradius users file because it is using PAP as authentication method. If I remember correct there were some changes on pfsense 2.1 CP but not sure. In general it is not neccessary that the passwords are encrypted on freeradius as long as noone has access to pfsense. I implemented this feature because a user asked if it would be possible: http://forum.pfsense.org/index.php/topic,43675.msg297759.html#msg297759 Don't know why and in which environment he wants to use this.
  • PPTP working on 2.0.2?? Anyone??

    Locked
    3
    0 Votes
    3 Posts
    1k Views
    S
    Same config but a clean install and it worked. Dont ask why because I havent got a clue!
  • 0 Votes
    1 Posts
    2k Views
    No one has replied
  • 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
    948 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
    869 Views
    No one has replied
  • Need Help To make Snort working

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

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