Subcategories

  • Discussions about development snapshots for pfSense Plus 25.07

    52 Topics
    770 Posts
    stephenw10S

    Most commonly new sensors appeared because an update had new drivers that exposed them. The chipset PCH sensor was pulled into base for 23.09 (I think!) for example.

  • Update to pfSense packages with XMLRPC sync functionality

    Pinned
    7
    2 Votes
    7 Posts
    369 Views
    RobbieTTR

    @LukasInCloud
    Thanks but I would not know where to start to help trim the boot time. Is there a guide somewhere or a resource I could lean on?

    ☕️

  • 25.03-BETA snapshots are now available

    Pinned Locked
    2
    3 Votes
    2 Posts
    805 Views
    johnpozJ

    If you want to discuss 25.03 snapshots the section is here

    https://forum.netgate.com/category/102/plus-25-03-develoment-snapshots

  • What skills are needed for Development

    Pinned
    8
    0 Votes
    8 Posts
    14k Views
    J

    Core skills needed for development:

    Problem-solving Programming languages Version control Databases APIs Testing Soft skills like communication, collaboration, time management Continuous learning, staying updated with tools and trends Optional but valuable DevOps basics, cloud platforms (AWS, Azure) and UI/UX awareness
  • 0 Votes
    21 Posts
    581 Views
    stephenw10S

    It should be fine. Or at least no worse than mpd5/netgraph. Bouncing the WAN every 20s is going to be pretty disruptive on a default install. With all the services and additional sub-interfaces you have it 's going to be a lot for the firewall to do. If it takes longer than 20s to reload all the tunnels and services then it could be in a continuous churn with high load.

  • Built-in NetBox importer for DNS, DHCP, etc

    Moved
    1
    0 Votes
    1 Posts
    72 Views
    No one has replied
  • New PPPoE backend, some feedback

    216
    0 Votes
    216 Posts
    31k Views
    rlinnemannR

    To clarify on what's happening with the pending gateway, in your instances IPV6CP negotiation establishes the IPv6 endpoints on the PPP session, and the link local peer address is intended to be the gateway for your DHCPv6 assigned address, with no RAs to nominate a gateway. The interface gateway is correctly set to the address of the peer endpoint by the driver, but the existing LL address on the interface is not updated with the remote destination address, and that destination address is expected to be present in order to identify the PPP gateway when the gateway monitoring setup is triggered. The patch intuits the PPP gateway from the routing table instead of the interface address in the IPv6 case. I'm working on a correction to the driver that should eliminate the need for this special case handling.

  • 0 Votes
    3 Posts
    162 Views
    M

    @stephenw10 The Ultra Ethernet Consortium

  • Looking for PfSense Github 2.8.0 branch.

    1
    0 Votes
    1 Posts
    91 Views
    No one has replied
  • Bugs/Problems with Netgate Installer Beta

    13
    0 Votes
    13 Posts
    2k Views
    JeGrJ

    @stephenw10 Aye that's right

  • AbuseIPDB Scripting

    5
    0 Votes
    5 Posts
    1k Views
    0

    Hi guys,
    I create simple shell script reports for AbuseIPDB from filter.log file. Maybe it will be helpful to someone.
    It was tested over a one-week period and works as expected.
    Here is the link: ttps://github.com/whoami-0x44/abuseipdb-reporting-pfsense

  • QEMU VM: Version 2.8 Won't Boot

    24
    0 Votes
    24 Posts
    3k Views
    stephenw10S

    Yes you can choose 2.8.0-beta from the installer menu.

    Edit: Now 2.8.0-RC

  • Sharing Errors in the Logfiles, which might need attention!

    2
    0 Votes
    2 Posts
    295 Views
    stephenw10S

    Nope, none of those are a big concern. Some of that could be cleaned up but they are just ugly.

  • 25.03 beta - Bufferbloat / FQ CoDel issues

    26
    0 Votes
    26 Posts
    3k Views
    RobbieTTR

    @w0w

    Seems so or possibly an interaction with if_pppoe and something else within the new beta.

    Regressing to 24.11 again and symptoms vanish. Reverting to the old backend on the beta seems fine too (albeit with the old pppoe issues).

    I had to work back again and re-test as I had the test diff patch applied with the revised beta, which drew some doubts on my results for a while. Fat-fingering in a config error when testing is something I try to avoid but you have to admit your mistakes.

    I'm waiting for the next beta drop really, to see if the changes also impact the issues I see. Opening up all the cores may just be peeling back something that was already latent and just masked by the old backend process.

    I did do a couple of tests that suggests the upload fq_codel settings may need adjusting against a different workload for if_pppoe; but too early to be sure.

    I'm also being nudged to try Kea again, as apparently it has matured a bit since its launch.

    ☕️

  • X-ray VPN implementation in future releases of pfSense+

    6
    0 Votes
    6 Posts
    855 Views
    stephenw10S

    Hmm, it does seem kinda shady!

    There's no FreeBSD port as far as I can see, though there is one for v2ray which this was forked from.

    You are asking about adding it as a client to connect to the xrayvpn service only?

    I'm not really seeing any advantages over existing VPN options TBH.

  • 2.8.0-BETA snapshots are now available

    24
    10 Votes
    24 Posts
    4k Views
    M

    @matthijs

    I had an issue with a static arp entry, but it was a wrong configuration on my side (an old wrong static arp entry/Mac address) The IP adres with this static ARP entry was in use by another host (with another MAC address) an that was an issue. I did not experience this in 2.7.2 So in fact 2.8.0 is behaving correctly

  • Understanding config.xml

    3
    0 Votes
    3 Posts
    534 Views
    P

    @jimp oh cool, it never even occurred to me that ppl would carry around a universal cert

  • 25.03-BETA - Trace Route Doesn't work?

    3
    0 Votes
    3 Posts
    458 Views
    K

    @patient0 Worked! thanks!

  • How to verify rule and separator position in the Firewall Rules menu !?

    3
    0 Votes
    3 Posts
    485 Views
    M

    The rule order in the configuration file is supposed to reflect both the rule processing and rule position (i.e. what's shown in the GUI) order. Ultimately, the processing itself is determined by what gets put into /tmp/rules.debug. As for the rule position in the GUI, there are multiple factors involved. With the latest fixes (referenced in the thread linked above), what does happen should finally match what is supposed to happen.

  • is plus discontinued?

    16
    0 Votes
    16 Posts
    3k Views
  • How to define path when uploading file to src?

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