cloudXabide | to the Cloud

Ugh... Comcast.  This sucked particularly much as this was my first attempt to configure a VPN back to my HomeLab and therefore was not sure what options I should have *known* would work.  Anywho... Sophos SSL VPN uses 8443 by default.  I spent a few hours trying to get through the config on the Sophos and my Linux client.  Nothing was working. For giggles I changed the Sophos to use 443, and then updated my client on my Linux workstation.  And suddenly it all works.  Fowk.  Tried 8443 again.  No love. I don't want to utilize port 443 as I intend to actually host some web apps for testing.  So, I have finalized on an "alternate" port which had to be configured on both the Sophos and the Linux client. I'l be doing a better write-up about this later.  I still need to figure out how to configure all this via the Gnome Network-Manager GUI.

It had been about 10 months since I had done any "hardcore" Linux stuff and I need to get ramped up on a bunch of Red Hat technologies again - namely OCP and Satellite.  So, I decided I would use my laptop to spin-up a bunch of VMs.  I build my own "kickstart" environment using ISOs on my "KVM Host" to build the KVM Guests.  They are NAT'd using 192.168.122.0/24 address space and virbr0. I had everything setup and when I would monitor the console of the VM I was building, I would see "connection refused" when it would go to pull any content (i.e. my kickstart configuration). Initially I thought I simply had to update the "public" firewall zone. Then, I assumed I had to add the "virbr0" or "virbr0-nic0" to the zone's interfaces. Nope... Then I ran "setenforce 0" to see if SELinux was hosing it up.  Nope. chcon -Rvv --type=httpd_sys_content_t /var/www/html.  Nope (still a good measure though). ...