Subcategories

  • 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
    795 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
    927 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).

  • Form Input Width Granularity

    2
    0 Votes
    2 Posts
    1k Views
    jimpJ

    Is this for 2.3? If so it belongs on the 2.3 board.

  • Checkbox Display as Radio Duplicate ID Error

    1
    0 Votes
    1 Posts
    772 Views
    No one has replied
  • Sample Logs for Dev/Test

    1
    0 Votes
    1 Posts
    758 Views
    No one has replied
  • Dev Shell

    6
    0 Votes
    6 Posts
    2k Views
    D

    I think it used to auto-exit for a reason. The relevant stuff appears to be in /etc/phpshellsessions/gitsync in case someone's bored.

  • [solved] 'Trick' (patch) Captive Portal into using LDAP User backend

    4
    0 Votes
    4 Posts
    2k Views
    F

    From https://redmine.pfsense.org/issues/5112 :

    With some help from PiBa-NL via IRC I can confirm that the hackish approach works fine.

    $authcfg = auth_get_authserver("YOUR LDAP BACKEND NAME"); $_attributes = array(); $loginok = authenticate_user($_POST['auth_user'], $_POST['auth_pass'], $authcfg, $_attributes);

    I then uncommented the privilege checking. I hope I find the time to layout changes in a github PR and would like some guidance on how the new configuration options should be structured. It can get complicated if one wishes, but there I will not help much.

    I thus consider this thread to be closed, but are happy to find collaborators for a github PR (join me on https://redmine.pfsense.org/issues/5112 ). Thanks.

  • Testing Request: LDAP/AD Authentication

    2
    0 Votes
    2 Posts
    3k Views
    F

    That sounds a lot like RFC2307bis authentication as in https://redmine.pfsense.org/issues/5461 .

  • Packages doing crazy things (sysctls, /boot/loader.conf mods)

    2
    0 Votes
    2 Posts
    1k Views
    J

    obviously(?) sysctl needs an API, so we can ensure it occurs correctly, and perhaps within some limit.

  • Use Network Aliases in OpenVPN configuration too?

    2
    0 Votes
    2 Posts
    1k Views
    P

    https://redmine.pfsense.org/issues/2668
    I thought about this a long time ago and never did anything about it!
    Someone (me?) should look at it again when the 2.3 code is stable.

  • Packet Fence evaluations

    5
    0 Votes
    5 Posts
    3k Views
    D

    Apparently…

  • Dhcpd rrd graph

    6
    0 Votes
    6 Posts
    1k Views
    H

    new version with additional info:

  • Firewall Log Display Descriptions Performance

    10
    0 Votes
    10 Posts
    2k Views
    N

    What would be the implications of eliminating table "persist file" lines from the pfctl -vvPnf input in these two /etc/inc/filter_log.inc functions?

    function find_rule_by_number($rulenum, $trackernum, $type="block") {
    function buffer_rules_load() {

    grep -v "persist file" /tmp/rules.debug | /sbin/pfctl -vvPnf -

    Speeds it right up.

Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.