vpnaccess
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| vpnaccess [2018/06/29 15:59] – djgalloway | vpnaccess [2026/09/16 18:42] (current) – djgalloway | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== VPN Access ====== | ====== VPN Access ====== | ||
| - | ===== Requesting Access ===== | + | ===== Requesting |
| - | To request access to the Sepia lab, | + | |
| - | - Generate login credentials by following directions under **VPN Client Access** below. | + | |
| - | - [[http:// | + | |
| - | For details on our particular OpenVPN server setup, see [[services:openvpn|OpenVPN]]. | + | Visit https:// |
| - | ===== VPN Client Access | + | ===== Existing User Additional Credential |
| - | Follow the instructions corresponding to your workstation' | + | |
| - | **NOTE:** You will need VPN credentials for each machine/ | + | Use this form if you are registering an additional machine and need another Wireguard or SSH key. |
| - | ==== Linux ==== | + | See https://onboarding.sepia.ceph.com/wireguard/request |
| - | < | + | |
| - | sudo [apt-get|yum] install openvpn | + | |
| - | cd / | + | |
| - | wget http:// | + | |
| - | sudo tar zxvf sepia-vpn-client.tar.gz | + | |
| - | # Generate client credentials | + | ===== Existing User Replace Credential ===== |
| - | # USER should be your desired username and HOST should describe your workstation | + | |
| - | # e.g., dgalloway@thinkpad | + | |
| - | sudo ./sepia/new-client USER@HOST | + | Use this form if you are //replacing// a machine and no longer need your previous Wireguard key/SSH key. |
| - | # Submit the command output in your ticket | + | https:// |
| - | # After you've been notified in your ticket that access has been granted, | + | |
| - | sudo service openvpn restart | + | ===== Existing User Remove SSH Key ===== |
| - | OR | + | |
| - | sudo systemctl restart openvpn@sepia | + | |
| - | # If you have a /etc/openvpn/client/ directory, you may need to: | + | https://onboarding.sepia.ceph.com/keys/request |
| - | sudo mv / | + | ===== Approvals ===== |
| - | # before you can run openvpn-client@sepia.service. | + | User access requests from @ibm.com and @redhat.com e-mail addresses are automatically approved once they confirm their e-mail via a magic link. (Other domains can be added. For now, IBM and Red Hat seemed safest.) |
| - | # This is because the OpenVPN systemd unit file looks in / | + | |
| - | </ | + | |
| - | === Linux Gotchas === | + | Non-whitelisted domains require an existing lab user to " |
| - | You may need to modify '' | + | |
| - | < | + | Once an account is approved, automation runs to add the user's public key to https:// |
| - | - user nobody | + | |
| - | - group nogroup | + | |
| - | + user openvpn | + | |
| - | + group openvpn | + | |
| - | </code> | + | |
| - | If you're using OpenVPN for any other VPN connection (e.g., Red Hat' | + | The user will then be e-mailed their Wireguard IP and can log in. |
| - | < | + | Admins can approve/deny/clean up at https://onboarding-admin.front.sepia.ceph.com/ |
| - | - dev tun | + | |
| - | + dev sepia0 | + | |
| - | + dev-type tun | + | |
| - | </code> | + | |
| - | + | ||
| - | === Troubleshooting === | + | |
| - | To troubleshoot your VPN connection, try running the following command to determine where the connection is failing: | + | |
| - | + | ||
| - | < | + | |
| - | openvpn --config | + | |
| - | </ | + | |
| - | + | ||
| - | ==== Fedora NetworkManager GUI ==== | + | |
| - | + | ||
| - | - Make sure you've followed all the prerequisite steps [[vpnaccess# | + | |
| - | - Right click the NetworkManager icon | + | |
| - | - **Edit Connections** | + | |
| - | - Click the + symbol | + | |
| - | - Select **Import a saved VPN configuration** from the bottom | + | |
| - | - Click **Create** | + | |
| - | - Browse to ''/ | + | |
| - | - Enter your the first line in ''/ | + | |
| - | - Enter the second line in your ''/ | + | |
| - | + | ||
| - | + | ||
| - | ==== Mac/OS X ==== | + | |
| - | Tunnelblick and Viscosity are two clients known to work with the Sepia VPN. | + | |
| - | + | ||
| - | === Tunnelblick **UNTESTED** === | + | |
| - | - Download and untar the Sepia VPN client [[http:// | + | |
| - | mkdir / | + | |
| - | cd / | + | |
| - | wget http:// | + | |
| - | sudo tar zxvf sepia-vpn.client.tar.gz | + | |
| - | + | ||
| - | # Generate client credentials | + | |
| - | # USER should be your desired username and HOST should describe your workstation | + | |
| - | # e.g., dgalloway@thinkpad | + | |
| - | + | ||
| - | sudo ./ | + | |
| - | + | ||
| - | # Submit the output of this command in your ticket</ | + | |
| - | - Replace the line '' | + | |
| - | - Follow [[https://tunnelblick.net/ | + | |
| - | | + | |
| - | - Save to your keychain if you wish | + | |
| - | + | ||
| - | === Viscosity === | + | |
| - | + | ||
| - | - Download http://ceph.com/ | + | |
| - | - Download http:// | + | |
| - | - Import the Sepia.visz config into Viscosity | + | |
| - | - Extract sepia-vpn-client.tar.gz | + | |
| - | - Save '' | + | |
| - | - Run '' | + | |
| - | - Replace '' | + | |
| - | - In Viscosity, under the Authentication tab, set: | + | |
| - | - **Authentication: | + | |
| - | - Check **Use Username/ | + | |
| - | - **CA:** to the ca.crt file you saved earlier | + | |
| - | - **Tls-Auth: | + | |
| - | - When connecting to the VPN for the first time, | + | |
| - | - Enter your '' | + | |
| - | - Enter the second line of '' | + | |
| - | - Save the credentials to your keychain | + | |
| - | - You can now delete any downloaded and created files (except ca.crt) | + | |
| - | + | ||
| - | ===== A Note About DNS ===== | + | |
| - | Due to complexities around adding nameservers to various Linux distro VPN clients, our OpenVPN server does not use the [[https:// | + | |
| - | + | ||
| - | Instead, we serve our private DNS records publicly. | + | |
| - | + | ||
| - | If you're using dnsmasq, you can add '' | + | |
vpnaccess.1530287965.txt.gz · Last modified: by djgalloway
