Subcategories

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

    4k Topics
    21k Posts
    JonathanLeeJ
    @firefox I don’t think so, to be honest with you I am on an older version also. Just make sure you do the patch package and install all the system patches.
  • 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
    keyserK
    @jrey said in pfBlockerNG syslog logentries to remote SIEM: @keyser I so want to answer this, but then at the same time (no I don't) ... pfblocker using syslog messaging in real time. no tailing of files, no other packages, just code. Huuuh? That seems very very interesting I noticed your name in other posts around the forum where you seemed to be QUITE proficient at coding/developing. Are you by any chance considering involvement in developing and refining the pfBlockerNG package? It would be SO great if you are looking into adding native syslog to the pfBlockerNG package - or an easy workaround that does not require additional packages and “temporary” edits in files that does not survive service restarts or pfSense updates. Here’s that you will fill me/us in on the solution you are using to your Greylog - please, pretty please with sugar on top
  • 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
    R
    @provels said in updating to acme 1.0 breaks system beyond repair: need to restore from backup: This same mess happened to me, even w/o Acme, going from 25.07 to *.1. Blew, reinstalled w/ Crowdsec, blew again, reinstalled, clipped all the Crowdsec info from config.xml, restored config, back to normal. Crowdsec is a great concept, but I think I'm out. I never had this issue with Crowdec before the ACME update, even with updating from 2.7 to 2.8 there was no issues. In fact after restoring from a backup after the ACME update, Crowdsec reinstalled just fine, and this was before the recent release a couple days ago that contained a fix.
  • 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
    606 Posts
    M
    @yobyot I've SSHed into pfsense and for the sake of testing I've simply run the command: tailscale up --auth-key=tskey-client-kQ_THE_REST_IS_A_SECRET\?preauthorized=true\&ephemeral=false --accept-dns=false --accept-routes --advertise-exit-node --advertise-routes=X.X.X.X/24 --advertise-tags=tag:pfsense Note the preauthorized=true and ephemeral=false I gave this key all permissions (temporarly as I just wanted to verify it's working) of course I had to register the tag used also in the ACL tags pane: https://login.tailscale.com/admin/acls/visual/tags so far so good
  • Discussions about WireGuard

    697 Topics
    4k Posts
    lvrmscL
    Same here. It started after I installed 25.07. Then it settled down by itself after a few days. It started again after upgrading to 25.07.1. WireGuard works fine (it merely connects to the remote site from this one). However, I am refraining from upgrading the remote, because if the 'service' does not start, I fear it will not listen to incoming connections, which would leave me in a difficult situation. The other topic I had opened before finding this: https://forum.netgate.com/topic/198449/25.07-release-amd64-wireguard-service-reported-stopped-yet-tunnel-trafic-clearly-is-ok
  • Darkstat Reports in MB /GB

    1
    0 Votes
    1 Posts
    935 Views
    No one has replied
  • Check_MK Package for 2.3

    6
    0 Votes
    6 Posts
    2k Views
    J
    I have started trying to make one. I've already managed to get check_mk working manually, you can see my post here https://forum.pfsense.org/index.php?topic=111517.0 Once I have something to show, even if it just the GUI i'll create a new post / update this post. This is the first time I've looked at creating a pfsense package, so it might take me a few weeks to get my head round how it works.
  • Newbie Package Question

    3
    0 Votes
    3 Posts
    1k Views
    G
    @AR15USR: You have the latest version. If it were yellow color there would be an update. If it were red it is not fully installed. OK, dumb mistake. The stuff on the bottom is a legend, not a notification. Thanks.
  • Siproxyd on 2.3 just exits randomly without reason

    4
    0 Votes
    4 Posts
    2k Views
    jimpJ
    It may be something about the request, then. I have heard recently from the siproxd author that he is working on a new version, it's possible it's a bug that has been corrected there.
  • Quagga ospf don't work with static routes

    3
    0 Votes
    3 Posts
    2k Views
    M
    After long hours of search I come to believe, that package incorrectly builded. Do you have any idea how to resolve the problem?
  • IGMP Proxy bus error (Core dumped)

    9
    0 Votes
    9 Posts
    4k Views
    C
    Sorry… I mean the igmpproxy configuration.
  • QuaggaOSPFd / pfSense upgrade 2.2.6 -> 2.3

    3
    0 Votes
    3 Posts
    1k Views
    jimpJ
    There was an update to the quagga package to help here. The problem tends to be from an empty interface landing in the quagga configuration. It probably started to work after the package was updated on the server, so the reinstall pulled a fixed copy.
  • 0 Votes
    6 Posts
    1k Views
    F
    I was just going to create a topic for this :). Thank you for the quick response.
  • OpenBGPd 0.11_4 on 2.3: Incorrect setup on package installation

    1
    0 Votes
    1 Posts
    666 Views
    No one has replied
  • Softflowd Multiple Interface problem

    1
    0 Votes
    1 Posts
    1k Views
    No one has replied
  • Monitoring Internet Link

    3
    0 Votes
    3 Posts
    1k Views
    E
    Hi, I'm new with PFsense handling. I would like to ask from some help with pfsense settings and monitoring. Is there any chance that i can see continues logs and save it to my PC with Source Port, Destination site and bandwidth usage??? I been looking for days still can't find any solution. :'( :'( Please do help me.
  • Compat6x - pfSense 2.3

    5
    0 Votes
    5 Posts
    2k Views
    C
    Should be no need for VMware's tools. What problem were you having with open-vm-tools?
  • Mailreport

    3
    0 Votes
    3 Posts
    1k Views
    V
    Thanks, I searched for the application and didn't get any hits.
  • Where did the APCUPSd package go?

    10
    0 Votes
    10 Posts
    3k Views
    M
    @jbhowlesr: I'm not spreading bad info. My UPS is software dependant and without it, it doesn't operate like you specify. I know this because I have experienced a few power failures while using this UPS. With NUT only, my pfsense ran until it killed the battery in the UPS and hard powered off due to lack of power. With APCUPSd installed in ran until parameters were met in the settings I put in then it shut down my pfsense box before the battery died. Now as far as monitoring goes, I don't need a monitoring widget seeing how my UPS has a large LCD display on it. What I do need however is control fearures APCUPSd. I can't help but wonder if this was merely a NUT configuration problem.  Usually all the UPS does (regardless of model or software  on the host it is attached to) is report statistics, like % battery and estimated time left at current load, and the software processes this data and decides when to shut down the host. I wonder if there were some sort of permission issues preventing NUT from initiating proper shutdown, or if it was not reading the statistics from the UPS properly.
  • Ipguard package

    57
    0 Votes
    57 Posts
    39k Views
    A
    Some news regarding removed packages from 2.3: https://doc.pfsense.org/index.php/2.3_Removed_Packages . I also regret that ipguard was not included in pfSense 2.3.
  • Sqiud+AD problem

    1
    0 Votes
    1 Posts
    744 Views
    No one has replied
  • After upgrading from 2.2.6 to 2.3 named dont work

    4
    0 Votes
    4 Posts
    2k Views
    GertjanG
    @paulopastoriza: which the service is used in place of the bind / named in the new version? MENU => Services => DNS Forwarder or Resolver (you chose).
  • Creating first package - next steps?

    2
    0 Votes
    2 Posts
    658 Views
    BBcan177B
    Here is the Bootstrap conversion guide: https://forum.pfsense.org/index.php?topic=101062.0
  • Monitor Ip activity

    4
    0 Votes
    4 Posts
    1k Views
    V
    You have to setup squid as transparent proxy, that wil allow lightsquid to see traffic. But in my experience Bandwithd gives you better ip info.
  • Service_Watchdog 1.8.3 fails install [SOLVED]

    5
    0 Votes
    5 Posts
    1k Views
    ?
    @cmb: "No route to host" means you don't have a default gateway on the system. Or maybe that you have IPv6 configured internally but no IPv6 default route/Internet connectivity. Set the system to prefer IPv4 in that case under System>Advanced, Networking. Im marking this issue as solved and posting a thank you for the fix in the quote above. +1 Karma to cmb. Thank you for your reply. It solved my issue. It was indeed not having IPv6 under my WAN interface set to DHCP.
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.