SYS255: Week 4 - DHCP

DHCP Setup Guides:

CentOS: Set Up DHCP Service

Windows 10: Accessing IPv4 Settings

vi Guide:

Basic how to for vi

Working Notes

INTRODUCING THE HIT NEW MYSTERY/HORROR/ADVENTURE SERIES: NIGHTMARISH VM-CEPTION

Nightmarish VM-ception and the mystery of the glitchy cursor

Starting this week, instead of accessing the network that the lab VMs are on using VMWare Horizon, I decided to try connecting with a VPN. I had tried that previously on my laptop, but the school network's VPN software doesn't seem to play nice with Linux desktops. The difference this time is that I'm connecting via my Windows 10 VM, rather than my host OS, which is an Ubuntu-based Linux distro. As I'm writing this, there's been one problem, and as I'm writing this, I have no idea whether it's with the VSphere software, my VSphere Windows 10 VM, my local Windows 10 VM, my VirtualBox installation, or my Kubuntu host. Enabling "Display Cursor Trail" on the VSphere Windows 10 VM fixes it, but also can be a bit jarring on its own.

Image of the glitched cursor:

After completing the lab for this week, I intend to attempt to connect via VMWare Horizon, as I had previously, and see whether or not the problem persists.

I changed my setup a bit, installing the VSphere Client within my VM, so that I was no longer connecting through a Firefox tab. The cursor's appearence was no longer glitched, but it seemed to rapidly accelerate to an unusable speed whenever I moved it even a bit. I solved this by disabling Mouse Integration in VirtualBox.

Nightmarish VM-ception and the great vi escape

When editing the DHCP config file with vi, I ran into a problem. To exit vi, first, you must first switch from insert mode to command mode, which requires hitting escape. Because I accessed VSphere through a browser, hitting escape also took me out of fullscreen. Not the end of the world, but an annoyance nonetheless. My workaround is not to have anything in fullscreen, but that can get annoying, with my host OS bottom panel, the VirtualBox User Interface, Local Windows 10 VM taskbar, the Firefox user interface, the VSphere control panel, and the VSphere VM taskbar all taking up screen space. I will change the Firefox settings in my VM, so that a different key or combination exits fullscreen after I complete the lab so that this doesn't happen again.