In this step by step instruction, we take WIRE1x 2.2 for
example, which executes on Windows XP with SP2,
and our Wireless Network Interface Card is Intel(R) PRO/Wireless 3945ABG.
Note that we assume before following
our step, you have installed your wireless interface correctly and successfully,
so if you have any problem when
installing hardware, please consult your hardware manufacturer or system administrator.
In addition, you also
have to have enough information about the wireless network you want to connect
and access, such as which
kind of authentication method (EAP-MD5, EAP-TLS, EAP-TTLS,
or EAP-PEAP) should be used, whether
WEP encryption is enabled in this network (if so, you may have at least
one pre-shared WEP key, sometimes
you have to provide WEP key before associate to an AP), what IP configuration
you should use, and most
importantly, the credential you should use in this network
(such as username, password, or even certificate).
If you find that you lack any required information, please consult your network
service provider. If you are not
sure about who you should ask, send us
a mail. We welcome everyone to use this web page as a template to
create your own instruction page to assist your users to execute WIRE1x. Any
kind of non-commercial use is allowed.
- Go to WIRE1x website and download the desired version.
Take WIRE1x 2.0 for example.
- Extract the zip file you have downloaded.
- Execute the MSI program and follow the instructions in the
installation wizard.(Typically, just follow the default settings.)
(NOTE that since this package is generated by Visual Studion .NET, if you
did not install .NET framewrok,
Windows may ask you to download and install .NET framework. If you use Windows
XP, don't worry about
- Go to WinPcap website to download the latest stable version and install.
- Right click the "Wireless Network Connection" icon in your notification area, and select
"View Available Wireless Networks."
- Click "Change advanced settings" in the bottom
of the left-half window.
- Click the tabsheet "Wireless Networks." and UNMARK the box
"Use Windows to configure my wireless network settings."
- If you are going to use EAP-TLS,
you must also have your client certificate (with your private
key inside) in P12 or PFX format.
Double click your certificate and Windows will guide you how to import.
Don't forget to store this certificate in the "Personal" container
and make the private key exportable.
- If you are going to use EAP-TLS, EAP-TTLS, or EAP-PEAP,
and the CA that signed the server certificate is not trusted yet,
you have to import the CA certificate into the "Trusted
Root CA" container.
- Now, go back to the desktop and double click "WIRE1x
- Select the interface you want to use.
- Click "Scan" to view available wireless networks or select existing profile to associate.
If you use existing profile ,please jump to step
You can click "Edit" or "Delete" to modify or delete existing profiles.
- Select one network and then click "Associate."
- Configure profile name and SSID.
Please do not modify anything, unless it is necessary.
- Configure Wireless Encryption (WEP, WPA-TKIP, WPA2-CCMP).
Click "Setting..." to configure authentication methods (EAP-MD5, EAP-TLS, EAP-TTLS, EAP-PEAP).
NOTE that if your network service provider requires you to use DHCP,
please check the box "Enable DHCP."
- Click "next"
- Enable any authentication method you want to use and provide your credential.
- Double check your configuration.
- Click "OK" to finish configuration.
- Select one profile and click "Associate."
- If the "Authenticated" message appears, congratulations.
If the message appeared is "HELD" or stay in "Authenticating"
for more than one minute,
there may be something wrong, so you may have to check one more time.
(I know it really makes people tired, so if you'd like, you could also send
me a mail and briefly
the situation you face, I will try to help you.)
Click "Disassociate" to disassociate.
- If you check the box "Enable DHCP" in step
15,please wait for about half a minute.
You will notice that you receive new IP configuration by your DHCP server.
Copyright © 2003-2008
WIRE Lab., National Tsing Hua University,
Hsinchu, Taiwan, R.O.C. All Rights Reserved.