See instructions below for configuring either BU Linux or Ubuntu to use BU (802.1x).

Using BU (802.1x) with BU Linux

If you installed BU Linux on a computer with built-in wireless
networking, or if you’re using a pcmcia card that was already installed
in the computer when you installed BU Linux, then wireless networking
should have been set up automatically.

The wireless connection can be brought up and brought down using the
“ifup <device-name>” and “ifdown <device-name>” commands by
specifying the correct device (usually eth1).

This requires sudo privileges, so it would look like this:
% sudo ifup eth1
or
% sudo ifdown eth1

However, if the device is not already configured, which often
happens when you add a wireless pcmcia card to a laptop after you’ve
already installed linux, you will need to configure your network files.
These are in the directory: /etc/sysconfig/network-scripts/

% cd /etc/sysconfig/network-scripts/

% ls -Fl ifcfg-*
-rw-r–r– 3 root root   236 Aug 20  2008 ifcfg-eth0
-rw-r–r– 1 root root   254 Jul  4  2009 ifcfg-lo

In this case, I have one device, eth0, which is the
nic (network interface card/controller) for the network connection
that I plug in. You can ignore ifcfg-lo (loopback) for these purposes.

If there were already two nics in the computer, they
would be eth0 and eth1, and adding a wireless card
would make that eth2. Please adjust accordingly.

To configure the wireless device, I usually just create
the file ifcfg-eth1 with any editor (eg. vi, emacs, nedit)
using these lines:

DEVICE=eth1
BOOTPROTO=dhcp
ONBOOT=yes
TYPE=Wireless
RATE=Auto

Save your file, then start up your wireless connection with the ifup command:

% sudo ifup eth1

NOTE: If you set ONBOOT=yes, then from now on the wireless connection
will come up by itself whenever you boot up your computer.
If you don’t leave your pcmcia card in all the time,
you might want to set ONBOOT=off
and run the ifup command when you need it.

Using BU (802.1x) with Linux (generic)

PLEASE NOTE: These instructions are not officially supported or regularly maintained. They were contributed by users in the community and we hope they will be helpful.

Lucid Lynx(Ubuntu 10.04)

  1. Click on the Network Manager applet.
  2. From the drop-down menu, select “BU (802.1x)”.
  3. If you are connecting to this network for the first time, enter the following information:
    Security: WPA & WPA2 Enterprise
    Authentication: Protected EAP (PEAP)
    Anonymous identity:
    CA certificate: radius.bu.edu
    PEAP version: Automatic
    Inner authentication: MSCHAPv2
    Username: [Your BU username]
    Password: [Your BU password]

    Select “Connect”.

Hardy Heron(Ubuntu 8.04)

1. Update Ubuntu-Hardy using the update manager. Apply all the recent updates. (Note: This could mess up Compiz users as there is a bug in the recent updates for Ubuntu that will mess up Compiz-Fusion.)

2. Right click the network manager icon in the system tray and select 802.1x. Hopefully, a dialog window will pop up asking for your credentials and the connection details. Select WPA enterprise at the security option drop-down menu. Then select PEAP under EAP method option drop-down menu. Type your BU login name where it says “Identity” and the Kerberos password where it says “Password” (Right below Identity – not where it says private key).

3. Once done, hit Connect. It will struggle for a while, but will eventually connect. You should now be all set, until you try to disconnect/access another network. If you do, you will not be able to connect again to 802.1x until you reboot.

4. So, if you do want to connect again, reboot your computer. Right click network manager icon, select edit wireless networks, select 802.1x and remove it (i.e. delete the settings for 802.1x.).

5. Once you have completed step 4. Repeat steps 1 and 2. It might not work right away. If it stalls at the point where it says “Waiting for network key” when you hover over the network-manager icon, simply delete the settings for 802.1x again and retry steps 1 and 2. It should eventually work.

Using wpa_supplicant

1.Install wpa_supplicant with your package manager (Note: You must be connected to the Internet through other means)

Debian/Ubuntu/Generic Apt-Get:
# apt-get install wpasupplicant

2.Locate wpa_supplicant
# updatedb && locate wpa_supplicant.conf

3.Backup wpa_supplicant.conf

#cp /etc/wpa_supplicant.conf /etc/wpa_supplicant.conf.back

4.Fill in new wpa_supplicant.conf (see Notes below).

# BU wireless. Does not need vpnc to go online.

network={
ssid=”BU (802.1x)”
priority=15
key_mgmt=WPA-EAP
eap=PEAP MSCHAPV2
identity=”yourloginname”
password=”yourKerberos”   (SEE NOTE BELOW*)
phase2=”auth=MSCHAPV2″
}

# The BU website says to disable fast reconnect
fast_reauth=0

5.Run wpa_supplicant and hopefully connect
(The actual command to use wpa_supplicant may differ based on the wireless drivers and the wireless interface.)

# wpa_supplicant -Bw -Dwext -i wlan0 -c/etc/wpa_supplicant

*NOTE

Storing the Kerberos password in clear text is not recommended. Two alternative options have been provided by contributors to this page.
  • You can change permissions of the wpa_supplicant file to only be read by root because the Kerberos login and password are stored in plain text. Using chmod, for example ‘chmod 600 ./file’, will only allow read/write access to root. If you change your Kerberos password, remember to change the wpa_supplicant.conf file.
  • You can use the ntpassword hash of you Kerberos password instead. This can be done by installing “freeRADIUS” which gives you the program “smbencrypt”. Using smbencrypt, one can get the ntpassword hash of their password and put that into the wpa_supplicant.conf file using the format: password=hash:<32hex digits>