An Arizona Adventure – Caving Dum Ditty
An Arizona Adventure: For anyone who is familiar with electronics there is a guy named Don Lancaster who wrote "The TTL Cookbook". He preceded me working at Goodyear Aerospace too. Anyway he discovered a cave up on the rim which got named "Dum Ditty". It was one of the throw away caves they use in case you're a real tool that likes to go into caves and spray paint your name. Anyway I go to Az Cave Club and hook up. We go to this cave and go in the relatively roomy entrance and there in front of me is a big boulder with a teeny tiny opening at its base. My partner says that's the way. I'm like "waaaaaaa ??? seriously???" He replies "yes". I screw myself up and manage to do the crawl. Now you may or may not know you MUST wear a helmet caving. Otherwise you're going to knock the fuck out of your head. So my improvised unit was a construction helmet I found by the highway. If you pay attention while driving any highway you'll eventually start noticing there are construction helmets to be fairly readily found. So I had mounted a strap. Long story short only way to get through this hole was take off the helmet because IT WAS TOO WIDE to go through with that orientation. I had to do the turn your head and cough position to get through. I could then put my helmet back on and continue. Time after time in that cave – helmet off – turn your head and cough – slither – helmet back on. Looking back I wonder why I'm not still stuck in that cave.
When we finished up with that cave we went to one near by that was supposedly used as a speak easy during prohibition. It had a large antechamber. But someone had taken a crap somewhere and you've never smelt it like "someone shat in a cave" and it lays festering for years. I was out of there withing minutes.
Set Up WireGuard on Ubuntu Linux
Summary of Successful Path – path through the maze
- wireguard – wireguard comes with Ubuntu installs already
- Install resolvconf: sudo apt install resolvconf
- Installing the WireGuard Client App on Ubuntu – First install did not require. Second install did this.
- Use Mulivad VPN site to generate a configuration ( .conf ) file
- Place config file in /etc/wireguard You will have to create /wireguard
- File must have the .conf extension: VpnFile.conf
- Server is taken care of by the fact I'm using Mulivad
- Use command wg-quick up VpnFile ( note: no .conf extension here! )
- Test with WhatIsMyIP shows IP located in Chicago
Where to go next
Process Notes – the maze I started with
- resolvconf – was not installed. Errored out before Wireguard could run
- At first IIRC – I got an error when I tried to use FullFileName.conf ( with extension – ( still do )
- CONF file does not work without the .conf extention
- Works: wg-quick up wg0
- Does not work: wg-quick up wg0.conf
- IIRC: Part of the problem is that I was trying to test with my home wireguard server that now appears to be down
Research Links
- WireGuard.com: Wireguard overview
- Introduction to WireGuard VPN
- WireGuard Installation
- How to Set Up a WireGuard Client on Linux with .conf File
- How To Set Up WireGuard on Ubuntu 20.04 – Only used the first part for install of wireguard since I am using Mulivad. This takes the server issue out of the problem
- How to Set Up WireGuard VPN Client on Ubuntu Desktop – Only used the first part for install of wireguard since I am using Mulivad. This takes the server issue out of the problem
- Mulivad: WireGuard configuration file generator – Used this to generate the .conf file. Store off with .conf extension. You call without extension but the file must not have.
- Install wireguard-gui on Ubuntu – installed and got errors – delay till later
- What Is My IP – test to see if IP address of machine has changed to relevant IP address.
Theory
Other Links
- Connect to a VPN – covers the network interface you can click to from desktop network icon
- Install NetworkManager
- How to configure WireGuard VPN client with NetworkManager GUI –
- Can't add WireGuard VPN connection to Ubuntu Network Manager
While watching this video I realized that while the configuration file must have the .conf extension you call refer to this file without the extension and I had been trying to test with my home server which had gotten jammed up and needs rebooting.
