Subcategories

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

    4k Topics
    21k Posts
    J
    @qupfer What did I bang my head over this strange 502 issue. Your solution did it! Thank you so much, even 2.5 years later!
  • 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
    fireodoF
    @tinfoilmatt said in Failed or invalid Mime Type: [application/SIMH-tape-data|0]: (ASN data is IPinfo, not Maxmind) Thats correct but "GeoLite2-Country" is from Maxmind ... (that confused me) I'm considering simply adding "application/SIMH-tape-data" to the list to test. Thats what i tought too ... I'll try when I have the time for it ... Edit: I can confirm - adding "application/SIMH-tape-data" to the list at line 257 in /usr/local/pkg/pfblockerng/pfblockerng.inc did the trick - no more error! Edit: OK, problem resolved but I would like to know, whats the cause for that error! (SIMH-tape-data sounds like a "blast from the past" ...) Thanks a lot!
  • 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
    GertjanG
    @jimp Done. I was on acme.sh 1.0 (25.07.1) and a downgrade was proposed. Now, the issue is gone.
  • 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
    599 Posts
    S
    Upgraded to 25.07 and facing the same issue. Tried the "tailscale up" command as suggested above but restarting the tailscale service kills the login again.[image: 1755715824513-tailscale_logged_out_25_07.jpg]
  • Discussions about WireGuard

    695 Topics
    4k Posts
    GertjanG
    @rosskan In theory, when you tunnel a 'VPN1' over another 'VPN2', VPN2 will see the originating IP as the one belonging to VPN1, not your real WAN IP. So far, ok. That said, when you subscribed to VPN1 and VPN2, you probably used your ISP IPv4 ^^ You installed the VPN1 (or2) application on your crappy laptop ?, if so, 'forget about it' ^^ 'as they know', the app is at an end point, and can see 'everything'. Don't forget that you pay for your VPN subscription, but you give them more then your money. They can see and use your data connection for 'data mining'. And they will make use of that data - by selling it. Why ? Because the share holders want a good financial result. If you need to connect two (your !) networks (or sites) together, use your own VPN solution. Don't use a commercial company. For example, take the ones you got with pfSense. If you really need to use that public network (aka : the Internet) to contact public servers, you are aware that the connection is already encrypted end-to-end ? That's what https is all about. 'http' doesn't really exist anymore / shouldn't be used. Also, you need to take other steps to be safe : you really should start with removing "windows 10" out of the equitation .... @rosskan said in What information can vpn provider see when I use wireguard?: does wireguard share the mac address of the ethernet port of the crappy laptop with vpn provider #2? MAC addresses travel on a local segment. Your laptop's MAC doesn't travel any further then the first hop, this is most probably your first router (gateway) like pfSense. Packet capture your traffic to check this. The Ethernet headers are not encrypted.
  • Apcupsd with UPSTYPE net

    2
    0 Votes
    2 Posts
    1k Views
    D
    And why are you leaving the 'Device' field empty and sticking the stuff into 'UPS Type' field instead?! There's even a detailed table showing what to put where for each UPS type. Sigh.  >:(
  • Which package provides more details on MAC address

    10
    0 Votes
    10 Posts
    2k Views
    F
    will it be built in in The new version 2.3 ?
  • 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
    960 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
    986 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
    918 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
    814 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
    945 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
    592 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 [image: lldppfsense.png] [image: lldppfsense.png_thumb]
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.