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

    @bmeeks So after upgrading to the newest PfSense 2.8.0 everything is now working like a charm!

    Suricata no longer seems to strip off tags like it did before! Which means I can now use my network segmented by VLANs and still use the benefits of Suricata Inline IPS! Very niiize!

    I checked in the Alerts section and it is indeed generating the correct alerts from the different VLAN sections, I put Inline IPS on the parent interface of all the VLANs.

    I assume this is because the FreeBSD version is also updated with the new PfSense 2.8.0 version?

    Because before, as soon as I selected Inline IPS mode, my entire VLAN tagging would break and nothing was reachable until I switched back to Legacy mode.

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

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

    89 Topics
    576 Posts
    TommyMooT

    @elvisimprsntr Thanks, just updated, works fine! 👍 😊

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

  • Iperf guide for pfsense

    1
    0 Votes
    1 Posts
    2k Views
    No one has replied
  • APCUPSD problem, ups status data don't update, error in log.

    2
    0 Votes
    2 Posts
    954 Views
    L

    @LucaTo:

    apcupsd (latest: 0.3.8 ), pfsense 2.2.5-RELEASE 64bit (but the problem was the same also with previous realease)

    Same identical issue after update to new release 0.3.9

  • Apache path error apache_mod_security.inc with fix

    18
    0 Votes
    18 Posts
    2k Views
    D

    0.1.9 merged - good luck :P

  • Setting up access to packages GUI in System - User Manager

    3
    0 Votes
    3 Posts
    978 Views
    D

    Should be almost complete now, added to ~30 other packages. There are some ~10 packages remaining.

  • FreeRaduis installation failed on pfsense 2.2.5

    2
    0 Votes
    2 Posts
    907 Views
    D
    Include freeradius.inc is missing! Include file freeradius.inc could not be found for inclusion. Not executing custom deinstall hook because an include is missing.

    As noted above, you are missing required INC file. Try again.

  • Apcupsd - modbus recent

    1
    0 Votes
    1 Posts
    813 Views
    No one has replied
  • Quick easy way to determine if an IP is on a pfBlocker-NG list?

    2
    0 Votes
    2 Posts
    3k Views
    BBcan177B

    You should be able to see this in the pfBNG Alerts tab… v2.0 will have an improved lookup for CIDRs...

    You can also grep from the shell..

    cd /var/db/pfblockerng/deny/
    grep "^1.2.3.4" *

    Other examples:

    grep "^1.2.3" *
    grep "^1.2." *
    grep "^1." *

    add    | grep '/'  to only report CIDRs.

  • Is mailscanner working with PFSense 2.2.4 or 2.2.5?

    2
    0 Votes
    2 Posts
    938 Views
    T

    Hate to bump, but anyone?

  • Init/DROther with OSPF

    5
    0 Votes
    5 Posts
    2k Views
    S

    I'm not saying you shouldn't use TAP, but if you want to use TUN I think it should work with "topology subnet".

    If you are allowing all traffic in the OpenVPN tab of your firewall rules, you won't need another rule to allow the OSPF traffic.  If you are only allowing specific traffic in, I think you will need a rule to allow the OSPF traffic.  The reason I mentioned this is that in your original post you said the server is showing the client as "Init/DROther" and the client is not showing anything, which sounds like traffic is getting through from the client to the server, but not the other way.  The server would need to negotiate with the client before showing it as "Full/DROther", etc.  Of course by "server" and "client" I'm talking about the OpenVPN role, not OSPF.

  • 0 Votes
    3 Posts
    4k Views
    G

    this worked for me as well in conjunction with Watchdog package as discussed at https://forum.pfsense.org/index.php?topic=87441.30

  • HAProxy, just use custom configuration file and no UI?

    3
    0 Votes
    3 Posts
    2k Views
    J

    Awesome. the "devel" package does exactly what we need it to do, without a whole lot of custom options. The big thing was to have multiple backends per frontend.

  • Haproxy-devel 0.33 service won't start after upgade to 2.2.5

    6
    0 Votes
    6 Posts
    1k Views
    K

    Hello and thanks for your help. The removal of the empty global dns resolvers did the trick. All is fine now.

    As for version 0.32, yes I had it installed prier to upgrading.

    Regards,

  • Packages unavailable?

    3
    0 Votes
    3 Posts
    1k Views
    E

    @maverick_slo:

    They have ipv6 problems again…
    Ipv4 works for me, also forums are not reachable via 6...

    Thanks! IPv4 works for me as well. Problem solved :-)

  • Freeradius won't start

    6
    0 Votes
    6 Posts
    3k Views
    D

    Thanks for reporting back.

  • Service vHosts-http won't start.

    18
    0 Votes
    18 Posts
    4k Views
    D

    Perhaps install and uninstall the updated rewritten package and see if it helps? Other than that, editing config.xml manually.

  • OpenVPN Client Export Utility - Additional configuration options saving

    5
    0 Votes
    5 Posts
    2k Views
    C

    Hi,

    yes, very useful.

    This way, the user would be able to export multiple clients at different times, with similar settings.

    +1
    Nice when i have to export packages for 50 users.

  • Lcdproc-0.5.5 pkg.v.1.0.2

    1
    0 Votes
    1 Posts
    585 Views
    No one has replied
  • LADVD 1.0.4.2 problem and suggestion

    9
    0 Votes
    9 Posts
    3k Views
    johnpozJ

    "That's a work round of sorts. However, the package should forbid you from selecting a vlan. If you do so, ladvd keeps on churning out errors to the system log."

    But how is not just selecting the interface you have assigned to the physical not a solution to the OP problem?  I have lavd on my em1 and em2, which I do have L3 assigned too.. But you wouldn't have to if all you want to do is use vlans on that physical interface.

    That being said cdp and lldp would go out on the physical and works on whatever vlan you have as the native, be 1 or 10 or 200, etc..  To me this is untagged traffic and just the physical wire at layer 2.  Only reason you set it at the switch is too isolate that to its own broadcast domain..  So switch ports that are not part of that native vlan do not see this traffic.

    If lavd does not work and generates errors when you pick a vlan interface, then sure guess that should be removed.. And you should only be able to pick the actual physical be it em0, 1, etc.. or the interface you assigned to that physical be it lan, opt1, opt2 (or whatever you change the label too).

    I can how it should be updated in the package - I would think a note to the package maintainer could get that fixed up.. But still not seeing how this is any sort of real issue in the big picture.

    "working LLDP on pfSense would be nice to have, but is hardly critical in my deployment."

    It does work…
    edit:  hmm that is odd why is showing same mac for the ID.. em1 and em2 ... hmmm hose should be 02 and 03 for the last number in the mac..  Oh that is the device ID.. hmm would be better if that was the actual mac of the interface - which I thought it should be..

    ah it shows it
    sg300#sho lldp neighbors GE 3

    Device ID: 00:50:56:00:00:01
    Port ID: em2
    Capabilities: Router
    System Name: pfSense.local.lan
    System description: FreeBSD 10.1-RELEASE-p15 #0 c5ab052(releng/10.1)-dirty: Sat Jul 25 20:20:58 CDT 2015    root@pfs22-amd64-builder:/usr/obj.amd64/usr/pfSensesrc/src/sys/pfSense_
    Port description: Intel(R) PRO/1000 Legacy Network Connection 1.0.6
    Management Address: 192.168.9.253
    Management Address: 32.1.4.112.31.17
    Management Address: 00:50:56:00:00:02
    Time To Live: 172

    lldppfsense.png
    lldppfsense.png_thumb

  • MOVED: configuring dansguardian nd squid

    Locked
    1
    0 Votes
    1 Posts
    508 Views
    No one has replied
  • 0 Votes
    1 Posts
    629 Views
    No one has replied
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.