Hello @Kyle-Hardin-0 ,

You are correct, command history in PowerShell is handled differently starting with PowerShell v5.0 and the introduction of the PSReadline module. This module introduced persistent command history, and is accessed differently. I cover this topic in the "PowerShell Basics for Administrators" series. Here is a link to the specific episode.

https://itpro.tv/course-library/powershell-2017/2017-command-historyaliases/

The course "PowerShell for Administrators" was filmed using PowerShell v4.0. This series will eventually be moved to the legacy courses, but much of the content is still relative.

I agree this could be a point of confusion, and will add something to the show notes or maybe hide that particular episode.

Thanks for bringing this to our attention!!

Mike

+1 on the voting

wvykid,
It's been a while since we filmed that episode so my memory is a little fuzzy but here is how I remember it.

For the initial installation of pfSense we hooked a monitor and keyboard directly to the firewall box and did the local install. Once that was done we switched to my laptop for the rest. We didn't discuss it on the show, but I had two network adapters on my laptop. One NIC was connected to our studio network so that I could share my desktop with our video switcher. The other NIC was run to a switch which then connected to the LAN interface of the pfSense firewall. That effectively placed me on the inside of the firewall network and allowed me to access the web UI for configuration. Since my laptop had two default gateways, I manipulated my network interface priorities to ensure that my outbound traffic went through the firewall. I don't remember specifically, but the DMZ interface was either unplugged or we stuck a loopback plug in it to bring the link up without actually plugging it in to a network. Either way, the DMZ interface was not connected to a real network. The WAN interface was plugged in to our studio network so that the firewall had internet access. From there we were able to configure firewall rules to block/allow traffic as it passed between the firewall's LAN interface and the studio network.
I think that sums it up, but if you want any other details just let me know.
Don Pezet
Host, ITProTV