HOWTO_Wireless_Configuration_for_TUE

This article is part of the HOWTO series.

Installation • Kernel & Hardware • Networks • Portage • Software • System • X Server • Gaming • Non-x86 • Emulators • Misc

This page is a candidate for deletion: Reason given: This is not Gentoo specific

If you disagree with its deletion, please explain why on its discussion page.

If you intend to fix it, please remove this notice, but do not remove this notice from articles that you have created yourself.

Make sure no other pages link here and check the page's history before deleting.

Wireless Networking on TUE

The TU/e (Eindhoven University of Technology) uses EAP-TLS and MSCHAPV2 as authentication protocols. This page will tell you how to connect to the TU/e wireless network with a registered account and MAC_address. It will not tell you how to configure your wireless antenna on GNU/Linux systems.

Install wpa_supplicant

You'll need wpa_supplicant to have decent WPA support, so emerge it:

Code: emerge wpa_supplicant

# emerge -va wpa_supplicant

If you use madwifi as a driver don't forget to set USE="madwifi" before emerging.

Setup wpa_supplicant

Open /etc/wpa_supplicant.conf in your favourite editor (which is ofcourse vim) and put the following in it:

Code: /etc/wpa_supplicant.conf

# wpa supplicant config
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
ap_scan=1

network={
        ssid="tue"
        key_mgmt=IEEE8021X
        eap=TLS PEAP
        auth_alg=OPEN
        phase2="auth=MSCHAPV2"
        identity="tue\s######"
        password="********"
}

Ofcourse you should change the identity and password values according to the identity and password of your NT account. Now you should be able to connect by issuing the command:

Code: Connecting with the network

# wpa_supplicant -Ddriver -iinterface -c/etc/wpa_supplicant.conf

And once again, change the driver and interface according to your specific system. In my case it's madwifi and ath0.

Note: if this doesn't work, and you just 'happen' to have your hostname different from the traditional sxxxxx, you may want to force your dhcp client to override the hostname. in the case of dhcpcd and device ath0, this would be: