Subcategories

  • Discussions about development snapshots for pfSense Plus 25.07

    58 Topics
    819 Posts
    J

    I would agree. 18 hours in and everything continues to run smoothly. The issue related to image availability I believe is the valid answer and we can close this out as solved. Thanks everyone. -JD

  • Question about builder

    3
    0 Votes
    3 Posts
    871 Views
    ?

    No

  • Pfsense-tools patching errors

    5
    0 Votes
    5 Posts
    2k Views
    E

    Out of curiosity why you are building a custom pfSense?

  • Export NANO_DATASIZE

    2
    0 Votes
    2 Posts
    1k Views
    E

    No, there is no provision today for that.
    You have to create it yourself.

  • Who writes pfSense?

    6
    0 Votes
    6 Posts
    4k Views
    ?

    First we have to find them.  Some of them haven't been heard from in years.

    But if anyone in the top 10% of committers would like a year of free gold, have them get in-touch.

  • MOVED: Wlan working fine, after 2 hours not?

    Locked
    1
    0 Votes
    1 Posts
    766 Views
    No one has replied
  • Pfsense-packages GitHub public repo not synching

    2
    0 Votes
    2 Posts
    903 Views
    jimpJ

    As noted in the other thread (for service watchdog) that has been fixed.

  • 0 Votes
    7 Posts
    2k Views
    S

    @gonzopancho:

    I would invite you to fellate a dog, but I actually like dogs.

    Is this the same ganzopancho = Jim Thompson / James Thompson, officer/director/manager of Electric Sheep Fencing, LLC (ESF)?

    Surreal doesn't describe this particular remark, regardless of who it's directed at.

    @phil.davis:

    This sets a whole new stardard for ESF

    I was actually offended by this language when I read it a few days ago. It is possible to have a disagreement and even argument on a forum without using language like that.
    I hadn't thought of the "Report to moderator" button, should have done that straight away, but I have done that now, and stating that I am offended, which I am. Regardless of who the poster is, it is not acceptable to me. Maybe parts of these posts can be removed so that this sort of offensive language is not forever publicly visible on this otherwise friendly forum.
    I have a feeling that there are other posts with offensive language - when I come across them again I will report those also.

    I've only recently signed up for the forums due to an abundant willingness to dig further and provide some of the changes I've made to my own installation(s), so my 'post count' means little in terms of matters to this point.  I must admit, after reading this section and the way "administration" [sic] has mishandled what is clearly becoming a marketing and management fiasco to just about anyone who reads an overview of the situation, I'm disturbed and appalled, and have rapidly grown distrustful of "leadership".

    A difference in viewpoints, no matter how large, should never descend to such a level, even if the provocateur is as skilled as doktornotor.  Does the "administration" have any idea how that looks when they're marketing their services, at least in part, as first-line support for the product?  As a client, what kind of support could be expected from those with such patently horrible public manners?

    No one is asking for my $0.02 as an relative new-comer, so I'm offering it without respect to the inquisition.

    If administration wants to call it open source - let it be purely open source, flaws within the model and all - we all know it's not perfect, and we all know it rarely puts food on the table.  Free is free.  To date, it has served pfSense well it seems.

    If administration wants to turn it into a commercial product - call it as much, and let simple economics have their way with it, along with the exceptionally-poor marketing strategy currently in place.  At least someone knows what business model to which their efforts are being applied.

    I personally have no problem with either as long as I know what I'm getting into, but the situation in which the project currently finds itself is exceptionally bad.

  • PHP validity checker

    8
    0 Votes
    8 Posts
    2k Views
    jimpJ

    At one time we talked about a git hook that would reject a push if it failed a simple "php -l" validation. It's not perfect, but it would catch common mistakes/obvious typos.

  • Pfsense-tools repo details

    1
    0 Votes
    1 Posts
    850 Views
    No one has replied
  • [BUG] Easy rule passes invalid options to rules (ICMPv6)

    3
    0 Votes
    3 Posts
    1k Views
    L

    Works like a charm…  8)

  • Future code branches after 2.1 is released

    16
    0 Votes
    16 Posts
    4k Views
    ?

    Heck, there was even a 2.1.2.

  • Custom pfSense

    22
    0 Votes
    22 Posts
    4k Views
    ?

    We are unaware of any patches sent by doktornotor.

  • Announcement needed from ESF

    2
    0 Votes
    2 Posts
    1k Views
    ?

    https://forum.pfsense.org/index.php?topic=75651.msg412566#new

  • Enhancements to pfSense

    4
    0 Votes
    4 Posts
    1k Views
    ?

    Thanks, Phil

  • Redesigning pfSense interface

    13
    0 Votes
    13 Posts
    3k Views
    C

    Those who provided us keys had access last week. We haven't "gone to the dark side."  ::)

  • How to submit a patch (adding ovh.com DDNS service) ?

    4
    0 Votes
    4 Posts
    1k Views
    DerelictD

    Can anyone help me with the process to apply patches to different branches?

    I want to submit an enhancement I've written and tested against 2.1.2 but it needs to be submitted as a pull to master?

    I've forked on github and am working with a local clone with these upstreams and origins:

    [core]
    repositoryformatversion = 0
    filemode = true
    bare = false
    logallrefupdates = true
    ignorecase = true
    precomposeunicode = false
    [remote "origin"]
    url = https://github.com/derelict-pf/pfsense.git
    fetch = +refs/heads/:refs/remotes/origin/
    [branch "master"]
    remote = origin
    merge = refs/heads/master
    [remote "upstream"]
    url = https://github.com/pfsense/pfsense.git
    fetch = +refs/heads/:refs/remotes/upstream/

    If I want to make and test my changes against 2.1.2, do I checkout origin/RELENG_2_1 (or upstream/RELENG_2_1 ??), then create a feature branch there and somehow get just those changes back to master for submission as a pull request?

    Or do I checkout master, create a feature branch there, make my changes and somehow apply them to RELENG_2_1 for testing?

    Thanks for any guidance that can be provided.  Creating the simple feature has been much easier than getting me head wrapped around git.

    I also want to use git to manage changes I make to files that get whacked when I upgrade, such as /usr/local/captiveportal/index.php, with the goal of making it easier to reapply my changes to the new version.

  • Data flow in pfsense

    5
    0 Votes
    5 Posts
    2k Views
    ?

    separate engines perform security functions. This means a packet may be examined several times by different engines. This approach adds latency, which may affect network performance.

  • ESF Individual Contributor License Agreement

    4
    0 Votes
    4 Posts
    1k Views
    ?

    it was intended to be friendly, while maintaining the ability of the project to not be subject to an attack by a contributor.

  • Re-Brand pfSense as a different product

    9
    0 Votes
    9 Posts
    3k Views
    ?

    Yes, an answer (apart from perhaps pricing and very specific contractual details) will be public.

  • New package: tinc (mesh VPN) - Need assistance packaging

    25
    0 Votes
    25 Posts
    16k Views
    G

    I've just been fiddling some more. I just discovered, that I actually cant ping my router. For some reason my tun0 interface is getting the same ip as my router, so i was pinging myself…

    tun0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 
              inet addr:192.168.5.254  P-t-P:192.168.5.254  Mask:255.255.0.0
              UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:27 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:500
              RX bytes:0 (0.0 B)  TX bytes:2028 (2.0 KB)

    This explains why the ping time was so low 0.09ms  :-\ Should have picked it up earlier, guess that's what you get for working at 2am...

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