• PfSense 2.4.3-RC snapshots now available for testing!

    11
    0 Votes
    11 Posts
    2k Views
    ivorI

    OK, good but please start a new thread with next time and with more details instead of just leaving partial replies like this.

  • 0 Votes
    8 Posts
    3k Views
    L

    @PiBa:

    Still leaves the strange loader.conf behavior thought where the vm.pmap.pti="0" setting gets added multiple times upon rebooting..

    This is fixed now PiBa, thanks.

  • QNAP to add pfSense to its products

    Locked
    11
    0 Votes
    11 Posts
    3k Views
    ivorI

    Work is still in progress so I can't say for now as it might change. More info soon!

  • PfSense 2.4.2-RELEASE-p1 and 2.3.5-RELEASE-p1 now available!

    3
    0 Votes
    3 Posts
    3k Views
    ivorI

    Please open a new topic about it.

  • PfSense 2.4.2-RELEASE Now Available!

    10
    0 Votes
    10 Posts
    4k Views
    E

    I run pfSense on ESXI 6.0 latest update. I removed "kern.vty=sc" of /boot/loader.conf.local (I had this VT issue with pfSense 2.4.0).

    Then I upgraded via Shell to 2.4.2 and everything is working fine (No VT issue and no Framebuffer issue https://redmine.pfsense.org/issues/7975 )

    So thank you for your work!

    One question remains: Is pfSense still based on PHP 5.6 and why is it not upgraded to the much faster PHP 7.1.2 or 7.2 (release date on 30 November)?

  • 0 Votes
    1 Posts
    889 Views
    No one has replied
  • A pfSense roadmap

    66
    0 Votes
    66 Posts
    45k Views
    P

    Regarding the roadmap.
    Do we have any approximate timeframe when PFSense 2.5 will be out ? Maybe when a beta will be available for testing ?
    Since AES-NI will be required, I want to know how much time to I have until I would need new hardware :)

    Thanks a lot,
    Andy.

  • PfSense 2.4.1-RC snapshots Now Available!

    7
    0 Votes
    7 Posts
    3k Views
    B

    It spontaneously started working on its own. I updated to 2.4.1 RC.

  • PfSense 2.4.0-RELEASE Now Available!

    14
    0 Votes
    14 Posts
    6k Views
    ivorI

    Open a new topic with issues you're having please.

  • No Plan Survives Contact with the Internet

    6
    0 Votes
    6 Posts
    3k Views
    GrimsonG

    Thanks for answering my questions.

  • Contributing to the pfSense project gets easier!

    1
    0 Votes
    1 Posts
    1k Views
    No one has replied
  • PfSense 2.4.0-RC Now Available!

    8
    0 Votes
    8 Posts
    5k Views
    jimpJ

    @chudak:

    Any plans for GA soon ?

    Yes.

  • PfSense 2.3.4-RELEASE Now Available!

    1
    0 Votes
    1 Posts
    5k Views
    No one has replied
  • Help us translate pfSense, get a free Netgate SG-1000 microFirewall!

    1
    0 Votes
    1 Posts
    2k Views
    No one has replied
  • PfSense 2.3.3-RELEASE Now Available!

    9
    0 Votes
    9 Posts
    5k Views
    jimpJ

    The tag was done locally but hadn't been pushed out yet. It's there now: https://github.com/pfsense/pfsense/tree/v2.3.3_1

  • Announcing forum maintenance - March 16, 2017

    2
    0 Votes
    2 Posts
    1k Views
    H

    May the beeps be with you

  • Announcing a new trademark policy for pfSense

    Locked
    6
    0 Votes
    6 Posts
    4k Views
    J

    @vbentley:

    From the moment an organisation chooses to register a trademark they are obliged to enforce it or they risk losing it.
    https://secureyourtrademark.com/blog/trademark-101-can-lose-trademark/

    An organisation cannot write a trademark policy and expect to not have to comply with it themselves. If they do so, they are eroding their own brand.

    It is my opinion that the term 'pfSense' can no longer be used interchangeably to describe pfSense® commercial products and the pfSense community editions. Each time pfSense is used to describe the community edition it is diluting its validity to the commercial product. If ESF do not enforce this on their own public forum then they risk the community being able to prove that the use of the mark is more commonly used to describe the community edition than the commercial product. This might be important if installations of the community edition outnumber pfSense® installations.

    I am not a fan of RedHat, but I understand why the company decided to distinguish their commercial product from the community edition by creating the FedoraProject.

    Are you an attorney?

    If you're not an attorney, have you consulted with one on this?

    You're wrong, but this is not the venue to explain how.

  • PfSense Hangout - Feb 2017 - Advanced OpenVPN topics on pfSense 2.4

    9
    0 Votes
    9 Posts
    4k Views
    M

    @jimp:

    @mrzaz:

    I have another small comment that relates to the section on page 35 "RA TAP Bridge" that is worth mentioning
    is that neither Android or IOS supports TAP in the current API.  (tried Android 6.0.1 and IOS 10.2.1)

    I mentioned that on slide 7.

    Yep you did, I could see that now. Maybe a reminder on that page could have been done but lets just drop it
    as you have already mentioned it elsewhere which was most important. :-)

    //Dan Lundqvist

  • Automatic conversion from GET to POST in pfSense Software version 2.4

    1
    0 Votes
    1 Posts
    2k Views
    No one has replied
  • PfSense® software translations with Zanata

    22
    0 Votes
    22 Posts
    6k Views
    A

    @KOM:

    I suppose new subforums will be created to match every additional language?

    Want to lure out those Klingons hidden all over earth? Neat.

    If memory serves Gonzopancho once said that he only creates forums for languages he has someone for to speak/understand.

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