diff --git a/docs/guides/Linux Cyberlab Secure.md b/docs/guides/Linux Cyberlab Secure.md new file mode 100644 index 0000000..60aad84 --- /dev/null +++ b/docs/guides/Linux Cyberlab Secure.md @@ -0,0 +1,81 @@ +# How to use Cyberlab Secure on Linux + +1. Install nm-connection-editor + - **Ubuntu** + ``` + sudo apt update && + sudo apt install network-manager-gnome + ``` + + - **Fedora** + ``` + sudo dnf install nm-connection-editor + ``` + + - **Arch** + ``` + sudo pacman -S network-manager-applet + ``` + + +??? note "Note about compatibility" + + This should work on most distributions that use NetworkManager and wpa_supplicant. If you are using a different network manager, you may need to use a different tool to connect to Cyberlab Secure. + Other distros are officially unsupported, but you can try to use the nm-connection-editor tool to connect to Cyberlab Secure. + + +2. Run nm-connection-editor +```bash +sudo nm-connection-editor +``` + +3. Click on the + button to add a new connection + - ![Select the plus on the bottom left](../img/linux-cyberlab-secure/nm-step-1.png) + +4. Select Wifi and click Create + - ![Select Wifi and click Create](../img/linux-cyberlab-secure/nm-step-2.png) + +5. In the wifi tab fill in the following: + * Connection Name: `Cyberlab Secure` + * SSID: `Cyberlab Secure` + * Mode: `Client` + * Band: `Automatic` + * Device: `leave blank` + * MAC Address: `leave blank` + * Cloned MAC Address: `leave blank` + * MTU: `Automatic` + * Available to all users: `checked` + * All other fields can be left as default + * ![Fill in the fields](../img/linux-cyberlab-secure/nm-step-3.png) + +6. In the wifi security tab fill in the following: + * Security: `WPA & WPA2 Enterprise` + * Authentication: `Protected EAP (PEAP)` + * Anonymous Identity: `leave blank` + * Domain: `leave blank` + * CA Certificate: `leave blank` + * Check box for No CA certificate is required + * PEAP Version: `Automatic` + * Inner Authentication: `MSCHAPv + * Username: `Your SSO Username` + * Password: `Your SSO Password` + * ![Fill in the fields](../img/linux-cyberlab-secure/nm-step-4.png) + +7. Select Save + +8. Connect to the network +The Cyberlab Secure network should be available where you normally connect to Wi-Fi. If not, run +```bash +nmcli connection up "Cyberlab Secure" +``` + + +### Troubleshooting + +If you are having trouble connecting to the network, try the following steps: + +1. Run ``sudo journaclctl -u NetworkManager`` to see if there are any errors + +2. Run ``sudo journalctl -u wpa_supplicant`` to see if there are any errors + +3. Create ticket in infra help desk diff --git a/docs/img/linux-cyberlab-secure/nm-step-1.png b/docs/img/linux-cyberlab-secure/nm-step-1.png new file mode 100644 index 0000000..fe5a2d2 Binary files /dev/null and b/docs/img/linux-cyberlab-secure/nm-step-1.png differ diff --git a/docs/img/linux-cyberlab-secure/nm-step-2.png b/docs/img/linux-cyberlab-secure/nm-step-2.png new file mode 100644 index 0000000..fed8435 Binary files /dev/null and b/docs/img/linux-cyberlab-secure/nm-step-2.png differ diff --git a/docs/img/linux-cyberlab-secure/nm-step-3.png b/docs/img/linux-cyberlab-secure/nm-step-3.png new file mode 100644 index 0000000..b3ca8fd Binary files /dev/null and b/docs/img/linux-cyberlab-secure/nm-step-3.png differ diff --git a/docs/img/linux-cyberlab-secure/nm-step-4.png b/docs/img/linux-cyberlab-secure/nm-step-4.png new file mode 100644 index 0000000..c5d0f0c Binary files /dev/null and b/docs/img/linux-cyberlab-secure/nm-step-4.png differ diff --git a/mkdocs.yml b/mkdocs.yml index 6aae5c0..01fe6c1 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -50,5 +50,10 @@ nav: - "Migration Guide": "guides/Migrate Instance.md" - "Windows Instances": "guides/How to access Windows Instances.md" - "Troubleshooting": "guides/Troubleshooting.md" + - "Linux Cyberlab Secure": "guides/Linux Cyberlab Secure.md" #extra_css: # - stylesheets/extra.css +markdown_extensions: + - admonition + - pymdownx.details + - pymdownx.superfences