-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
5 changed files
with
82 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,82 @@ | ||
# 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 should be available where you normally connect to wifi. | ||
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 |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.