• Offline Development package creation

    2
    0 Votes
    2 Posts
    1k Views
    MikeV7896M
    I can't help with the package creation part of your post, but thought I'd mention that one of the pfSense developers is working on the return of vnstat. A promising screen capture was posted the other day in this post of the graphing, but the caveat is that the developer working on it doesn't have a timeline for completion, and the level of effort depends on workload of other more important items. But there is work in progress to bring vnstat back to pfSense. :)
  • RRD RAM Disk Backup/Restore

    6
    0 Votes
    6 Posts
    2k Views
    N
    @cmb: @NOYB: Thanks Jim.  So is there a use case for doing the rrddump in the reboot/shutdown/periodic backup for ram disk instead of the *.rrd files directly?  Would make that process cleaner, and straight forward without the rrddump. Wouldn't be a good idea. That's a lot of processing for no reason in that case. It's fast and low-resource to copy the rrd files, doing a dump and restore chews up CPU and RAM. In the past, at times enough RAM that it runs an ALIX out of RAM and kills off the process. Good chance of data issues on low RAM systems if you did a dump on every shut down and restore at boot up. That's how it's currently being done.  So should it be changed?  Just tar the *.rrd files and do away with the rrdtool dump at shutdown and rrdtool restore at boot up? In the ram disk management commit/pr submitted it should be pretty easy eliminate the rrdtool dump/restore on shutdown/boot up.
  • Replacing unbound/dnsmasq with custom resolver package

    3
    0 Votes
    3 Posts
    1k Views
    artooroA
    Just continuing to answer my own questions here. It looks like the <dns>system_services entry is likely related to a pull requests here https://github.com/pfsense/pfsense/pull/679/commits/513d61a8934989be0b9332d29d0f80926302344e#diff-163d9a46abf34586e1f87297c7670978R193 that was never actually merged. So basically it does nothing at this time. But it would be really great if that function would exist as mentioned in the pull request. Instead of hard coding a check for specifically unbound or dnsmasq if any package that provides the DNS system service is enabled then those triggers would apply. Since pfSense is open source I may send a new pull request myself at some point when I'm done my current port. What I've done in my package is I wrote some code that configures unbound on a non-standard port and makes it enabled while making sure dnsmasq is disabled. Just so that any pfSense functions that depend on the DNS Resolver/Forwarder (which we've replaced) being enabled will work.</dns>
  • MOVED: Separator bug

    Locked
    1
    0 Votes
    1 Posts
    708 Views
    No one has replied
  • Speed up the WebGui using Ajax instead of HTML

    1
    0 Votes
    1 Posts
    721 Views
    No one has replied
  • Add packages to PFSense 2.3 repository

    3
    0 Votes
    3 Posts
    2k Views
    S
    @heper: -https://forum.pfsense.org/index.php?topic=103481.0 -creating pull requests for them on https://github.com/pfsense/FreeBSD-ports -creating a redmine ticket for feedback there is also the chance that someone of the coredevs is already working on a pkg for NUT … Thanks. I have created the pull requests + tickets in redmine.
  • Callback custom_php_deinstall_command in PFSense 2.3

    3
    0 Votes
    3 Posts
    925 Views
    bmeeksB
    With the change to pkg to fully manage installs and uninstalls of packages, the old _<custom_php_deinstall_command></custom_php_deinstall_command>_still gets called, but the problem now is it gets called after pkg has already deleted all the PHP and INC files from the system.  So naturally your deinstall routines can't be called because they no longer exist.  I hit the same problem in one of my packages. The command BBcan177 referenced gets called before pkg removes all the files, so your uninstall routine can run. Bill
  • MOVED: 2.3 separator character support

    Locked
    1
    0 Votes
    1 Posts
    854 Views
    No one has replied
  • Generate custom iso pfsense

    1
    0 Votes
    1 Posts
    951 Views
    No one has replied
  • Captive Portal RADIUS MAC Authentication Improvement Idea

    1
    0 Votes
    1 Posts
    1k Views
    No one has replied
  • How to re-build pfsense packages ?

    1
    0 Votes
    1 Posts
    775 Views
    No one has replied
  • PfSense 2.2.6/i386 segmentation fault, illegal operations

    3
    0 Votes
    3 Posts
    1k Views
    D
    Oh, thank you very much ! :)
  • BUG on GRE interface page

    2
    0 Votes
    2 Posts
    798 Views
    jimpJ
    Thanks for the report, I can confirm it is a problem and I opened a ticket for it here https://redmine.pfsense.org/issues/6010 – I also pushed a fix to 2.3 for it, so it won't be a problem in the future. They are OK at boot time, so once you have the interface saved it's OK from then on if you have to reboot. GIF interfaces also had the same problem for interface flags so I applied the same fix there.
  • Replacement of Layer7 Filter

    1
    0 Votes
    1 Posts
    902 Views
    No one has replied
  • Using pkg_edit.php file

    4
    0 Votes
    4 Posts
    1k Views
    P
    @André: Pkg_edit then sends the changes made in the xml file for packages? It renders UI pages of packages based on the fields defined in the package XML, and does the necessary stuff to save the user-defined values into the package's section of config.xml.
  • Languages used in pfsense

    7
    0 Votes
    7 Posts
    5k Views
    S
    Thanks for the reply, Why choose Python? Thanks
  • How useful will the new dummynet AQMs be to ALTQ users?

    1
    0 Votes
    1 Posts
    951 Views
    No one has replied
  • PHP coding standard

    16
    0 Votes
    16 Posts
    4k Views
    P
    What should the standard be for tabbing in parameters on function calls that span multiple lines? i.e. when stringing the function name and all the parameters in one line makes the line "too long". e.g. Try to "line up" the additional parameters under the first parameter. a) By putting enough TAB and space characters assuming that each TAB is being displayed at 4-space intervals in some editor: TAB do_stuff($parameter1, TAB TAB TAB space "Second parameter is some literal text", TAB TAB TAB space $parameter3); b) By putting enough TAB and space characters assuming that each TAB is being displayed at 8-space intervals in some editor: TAB do_stuff($parameter1, TAB TAB space "Second parameter is some literal text", TAB TAB space $parameter3); c) By putting TAB characters to the function name then space characters to fill out under the function name: This avoids any assumption about the editor TAB display mode. TAB do_stuff($parameter1, TAB 9space "Second parameter is some literal text", TAB 9space $parameter3); Forget about lining up under the parameter on the first line, always indent subsequent lines by 1 TAB: TAB do_stuff($parameter1, TAB TAB "Second parameter is some literal text", TAB TAB $parameter3); Put the function name on a line by itself and all the parameters on later lines, always indented by 1 TAB: TAB do_stuff( TAB TAB $parameter1, TAB TAB "Second parameter is some literal text", TAB TAB $parameter3); and if one of the parameters has some really long literal stuff, like long text, then extra lines that continue the same parameter are indented an extra TAB: TAB do_stuff( TAB TAB $parameter1, TAB TAB gettext("Second parameter is some literal text that goes on and on and has line breaks.") . ' ' . TAB TAB TAB gettext("There is a lot to explain to the user.") . " " . TAB TAB TAB gettext("So we need to concatenate a lot of text together into a single parameter."), TAB TAB $parameter3); TAB do_stuff( TAB TAB $parameter1, TAB TAB gettext("Second parameter is some literal text that goes on and on and has line breaks.") . ' ' . TAB TAB TAB gettext( TAB TAB TAB TAB "There is a lot to explain to the user. " . TAB TAB TAB TAB TAB "So we need to concatenate a lot of text together into a single parameter. " . TAB TAB TAB TAB TAB "And sometimes the parameters passed are themselves a function that spans multiple lines."), TAB TAB $parameter3); The code currently uses various ways to do it, and it would be nice if there was a standard so that there does not need to a banter about it with each pull request! Personally I like (3)+(4).
  • RFC 4638 client support (PPPoE MTU > 1492) - testing

    35
    0 Votes
    35 Posts
    14k Views
    M
    2.3 is now BETA! Removed RFC 4638 patch. Updated to pfSense from 2.3.a to 2.3-BETA (amd64) built on Tue Jan 05 13:19:26 CST 2016 FreeBSD 10.2-STABLE Refetched and applied PPP IPv6 fix and rebooted. MTU=1500 en instant IPv6 access. Looking good, have to wait if stable. edit: Please go ahead for pull request! Your effort paid off, thank you so much David_W!
  • Steps to recompile kernel for pfsense 2.2.5

    5
    0 Votes
    5 Posts
    5k Views
    D
    The correct way is to use the build scripts in the RELENG_2_2 branch of the pfsense-tools repository. The instructions thread will likely help, though note that access to the pfsense-tools repository is now granted on github using the github user name you provided on the portal. There is no way to build a working pfSense 2.2 kernel without pfsense-tools, as the kernel patches are contained in this repository. I know this repository is deprecated, but this deprecation only applies from pfSense 2.3 (still not yet beta) onwards. Your build environment needs to be FreeBSD 10.1 of the appropriate architecture (amd64 or i386).
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.