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.
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.
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.
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 :)
