We expect the store will be back online soon, then we can confirm the status. I'm truly sorry for this inconvenience. I'll update you once the store is back online. Thanks!

e: can you please send an email to sales@netgate.com so our sales can contact you with shipping status? Thanks!

No, courses are not recorded and are interactive. It's divided in segments allowing you to step away for a bit but, just like any other education such as Microsoft or Cisco, you will have to devote your day to it.

I replaced my USG router with the QNAP pfSense VM image and it seems to be running fine. Our DLS internet is VERY bad so I can't comment on speed. The QNAP is a TVS-882 with SSD's and spinning disks; running on Qtier. Might not be required but I dedicated two on the Qnap's NICs to WAN/LAN each on a differnt Qnap vSwitch. Had some issues with Container services not working. I'm also new to running pfSense but I like it so far and like having one less box in the closet. Couldn't get OpenVPN running (probably just me) on pfSense so I'm just running it on the QNAP like before.

@jimp said in Moving the pfSense® Documentation to GitHub:

The only parts you could lose in the process are specific to Github, like PRs, issues (if you use them), access controls on repos, and so on. But the contents are always easy to shove wherever you want with git.

Right, and as you are using internal systems to push that out to Github and run Redmine as issue tracker, you actually don't use that much Github specific features that would depend on the platform to continue as-is ;) Loosing issue/ticket informations (when using GitHub internal issue tracking) would be worse.

5 seconds searching this forum and you would already have your answer.

I am not panicking.

I dont run a web browser on my unit, and I dont give public users access to my unit either, it has no WAN entry allowed at all.

People need to remember these "potential" exploits dont have super powers, they dont bypass other barriers.  So yes I do think meltdown and spectre have had excessive public attention compared to other exploits.

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

@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.

Please open a new topic about it.

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)?

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.

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