Virginia Tech Wifi: Difference between revisions

Waldrep (talk | contribs)
Waldrep (talk | contribs)
m Undo revision 7818 by Waldrep (talk)
Tag: Undo
 
(9 intermediate revisions by 2 users not shown)
Line 1: Line 1:
On campus, there are 2 wireless networks. '''eduroam''' is the preferred method, which uses PEAP-MSCHAPv2 to authenticate to the RADIUS server, while the second SSID, '''VirginiaTech''', provides a captive-portal and allows for guest account creation.
On campus, there are 2 wireless networks:
* '''eduroam''': uses federated credentials and is the preferred method.
* '''VirginiaTech''': for guests and devices that cannot use the authentication method of '''eduroam'''.
Any remotely modern/complete Linux or Unix system will be able to connect to eduroam without any issues.


As of January 2015 the [https://4help.vt.edu/sp?id=kb_article&sys_id=3886a7206f7721003fbcb03f5d3ee42f preferred method] of wireless access at Virginia Tech is through the [https://eduroam.org/ eduroam] network. eduroam is a secure wireless access service that was developed for the use of research and educational institutions. One of the advantages of the eduroam network is that you will be able to connect to the Internet at any participating institution using your Virginia Tech credentials. The eduroam-US site provides a [https://www.eduroam.us/technical_overview technical overview] of how the network authenticates you to the Virginia Tech RADIUS servers.
Because '''eduroam''''s credentials are federated, it means that a VT user is able to automatically connect to the Internet at participating institutions. The eduroam-US site provides a [https://www.eduroam.us/technical_overview technical overview] of the authentication system.


==General Connection Information==
==General Connection Information==
Line 34: Line 37:
''Subject:'' C = US, ST = New Jersey, L = Jersey City, O = The USERTRUST Network, CN = USERTrust RSA Certification Authority
''Subject:'' C = US, ST = New Jersey, L = Jersey City, O = The USERTRUST Network, CN = USERTrust RSA Certification Authority


This is a common root CA and should have shipped with your OS. It is likely located in <code>/etc/ssl/certs/USERTrust_RSA_Certification_Authority.pem</code>. Note that if you follow the Authority Information Access of the intermediate certificate, it may direct you to a URL which points to a different version of this certficate, which is cross signed by AddTrust and expires in May 2020. The one in your cert store is self-signed and expires in 2038. You want the one from your cert store.
This is a common root CA and should have shipped with your OS. It is likely located in <code>/etc/ssl/certs/USERTrust_RSA_Certification_Authority.pem</code>. Note that if you follow the Authority Information Access of the intermediate certificate, it may direct you to a URL which points to a different version of this certficate, which is cross signed by AddTrust and expired in May 2020. The one in your cert store is self-signed and expires in 2038. You want the one from your cert store.


====InCommon RSA Server CA====
====InCommon RSA Server CA====
Line 42: Line 45:
''Subject:'' C = US, ST = MI, L = Ann Arbor, O = Internet2, OU = InCommon, CN = InCommon RSA Server CA
''Subject:'' C = US, ST = MI, L = Ann Arbor, O = Internet2, OU = InCommon, CN = InCommon RSA Server CA


This is an intermediate certificate issued by InCommon. You can get it directly from InCommon [http://crt.usertrust.com/InCommonRSAServerCA_2.crt here].
This is an intermediate certificate issued to InCommon. You can get it directly from InCommon [http://crt.usertrust.com/InCommonRSAServerCA_2.crt here].


====eduroam.nis.vt.edu====
====eduroam.nis.vt.edu====
Line 85: Line 88:
printf 'YOUR-NETW-ORKP-SSWD' \
printf 'YOUR-NETW-ORKP-SSWD' \
   | iconv -f ASCII -t UTF-16LE \
   | iconv -f ASCII -t UTF-16LE \
   | openssl md4 \
   | openssl dgst -md4 \
   | cut -d ' ' -f 2
   | cut -d ' ' -f 2
</pre>
If you are using OpenSSL 3, you will need to specify the legacy provider:
<pre>
  | openssl dgst -md4 -provider legacy \
</pre>
</pre>


Line 130: Line 138:
     phase2="auth=MSCHAPV2"
     phase2="auth=MSCHAPV2"
     anonymous_identity="anonymous@vt.edu"
     anonymous_identity="anonymous@vt.edu"
    #THIS HASH IS OUT OF DATE, PLEASE FOLLOW INSTRUCTIONS ABOVE
     # if you prefer to pin the certificate, follow the instructions above to generate a hash
     # if you prefer to pin the certificate
     ca_cert="hash://server/sha256/0000111122223333444455556666777788889999aaaabbbbccccddddeeeeffff"
     ca_cert="hash://server/sha256/216c5f2568c6e84860b12535efe93500623ccee999306b84260f951bcbd57b1a"
     # if you prefer to dynamically validate the certificate by its cryptographic attributes
     # if you prefer to dynamically validate the certificate by its cryptographic attributes
     ca_cert="/path/to/USERTrust_RSA_Certification_Authority.pem"
     ca_cert="/path/to/USERTrust_RSA_Certification_Authority.pem"
     domain_match="eduroam.nis.vt.edu"
     domain_match="eduroam.nis.vt.edu"
     identity="YourPidHere@vt.edu"
     identity="PID@vt.edu"
     password="YourNetworkPasswordHere"
     password="YOUR_NETWORK_PASSWORD"
  }
  }


Line 144: Line 151:
  $ sudo wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant/eduroam.conf
  $ sudo wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant/eduroam.conf
  $ sudo dhcpcd wlan0
  $ sudo dhcpcd wlan0
On [[OpenBSD]], the process is a little more complicated:
# ifconfig wlan0 nwid eduroam wpa wpaakms 802.1x up
# /usr/local/sbin/wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant.conf
# dhclient wlan0
# ifconfig wlan0 inet6 autoconf


Alternate config options, besides domain_match are as follows (obviously not correct):
Alternate config options, besides domain_match are as follows (obviously not correct):
Line 158: Line 158:


More thorough documentation is available at [https://w1.fi/cgit/hostap/plain/wpa_supplicant/wpa_supplicant.conf]
More thorough documentation is available at [https://w1.fi/cgit/hostap/plain/wpa_supplicant/wpa_supplicant.conf]
===OpenBSD Instructions===
Since the [[OpenBSD]] network stack doesn't support 802.1x authentication, wpa_supplicant is needed to connect. wpa_supplicant on OpenBSD is different from its Linux counterpart in that it is only capable of 802.1x authentication and nothing more. First, install wpa_supplicant from ports if it is not already installed. After that, add just the <code>network={ .. }</code> portion of the above configuration to <code>/etc/wpa_supplicant.conf</code>. The wpa_supplicant service can be enabled with (where iwm0 is your wireless interface):
$ rcctl enable wpa_supplicant
$ rcctl set wpa_supplicant flags -c /etc/wpa_supplicant.conf -s -D openbsd -i iwm0
$ rcctl start wpa_supplicant
Finally, connect to the network with (again, replacing iwm0 with your wireless interface):
$ ifconfig iwm0 join eduroam wpa wpaakms 802.1x up
$ dhclient iwm0
$ ifconfig iwm0 inet6 autoconf


==netctl Instructions==
==netctl Instructions==
Line 279: Line 292:
* From the "WiFi networks" listing, click on eduroam.
* From the "WiFi networks" listing, click on eduroam.
* Choose PEAP as the EAP method and MSCHAPv2 as the phase two authentication mechanism.
* Choose PEAP as the EAP method and MSCHAPv2 as the phase two authentication mechanism.
* For the CA certificate, select "Use system certificates"
* For the CA certificate, select "Use system certificates". Optionally, import the root CA from above, and select that instead for better security.
  * Optionally, import the root CA from above, and select that instead for better security.
* For the domain, enter ```eduroam.nis.vt.edu```
* For the domain, enter ```eduroam.nis.vt.edu```
* Enter your pid@vt.edu for the identity
* Enter your pid@vt.edu for the identity