Skip to content

Instantly share code, notes, and snippets.

@tatumroaquin
Last active December 20, 2021 10:47
Show Gist options
  • Select an option

  • Save tatumroaquin/6ceae86068ac09d5e445cc5d4c853e04 to your computer and use it in GitHub Desktop.

Select an option

Save tatumroaquin/6ceae86068ac09d5e445cc5d4c853e04 to your computer and use it in GitHub Desktop.
A simple guide for authorization against enteprise wireless networks which utilises PEAP and MSCHAPv2

WPA Enterprise / University Wi-Fi Networks

This document serves as a guide for authenticating and connecting towards enterprise level or university wireless networks. From a linux host using NetworkManager and the nmcli tool.

Add Connection Profile

nmcli connection add type <wifi/ethernet> ifname <wlp4s0/wlan0> con-name <profile-name> ssid <wifi-ssid>

Turn on DHCP

nmcli connection edit <profile-name>
nmcli> set ipv4.method auto

Edit Profile Security

nmcli> set 802-1x.eap peap
nmcli> set 802-1x.phase2-auth mschapv2
nmcli> set 802-1x.identity <username>
nmcli> set 802-1x.anonymous-identity <username>
nmcli> set 802-1x.password <password>
nmcli> set wifi-sec.key-mgmt wpa-eap

These are the standard parameters required to authenticate to an enterprise network. Even if these properties doesn't exist on the current network profile they can be created and set. Do not edit 802-11-wireless as this is a different property and will not produce the same effect.

There may be additional requirements depending on your organisation, if such requirements exist. You must contact your I.T. Support Team and ask them for help to connect to the network.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment