Navigation

For those of us who do not use the KDE or Gnome network managers, there is another simple way to gain access to the campus wireless networks using wpa_supplicant directly. Below is the config required to get it operating, compliments of Philip White. It would be wise to read man wpa_supplicant to figure out how to run it.

network={
	ssid="CometNet2"
	key_mgmt=WPA-EAP
	eap=PEAP
	proto=WPA2
	identity="<Your NetID>"
	password="<Your NetID Password>"
	phase2="auth=MSCHAPV2"
	priority=9
}

network={
	ssid="UTDALLAS"
	key_mgmt=IEEE8021X
	auth_alg=OPEN
	eap=PEAP
	identity="<Your NetID>"
	password="<Your NetID Password>"
	phase2="auth=MSCHAPV2"
	priority=10
}

network={
	ssid="WATERVIEW"
	key_mgmt=IEEE8021X
	auth_alg=OPEN
	eap=PEAP
	identity="<Your NetID>"
	password="<Your NetID Password>"
	phase2="auth=MSCHAPV2"
	priority=0
}

Due to the extreme length, the long version has been split out into its own page: long_wpa_supplicant.conf.

At any given time, you will probably be within range of more than one of these networks. The priority field in each network declaration specifies which one to try first, lower numbers mean earlier attempts. In the above listing, WATERVIEW has priority of 0, which means it will be selected over the others if available. If WATERVIEW isn't available, CometNet2 is 9 and UTDALLAS is 10, which means CometNet2 will be selected over UTDALLAS. This is probably how you want it, since CometNet2 is 802.11G and UTDALLAS is only B.