HOWTO: Wireless Security - WPA1, WPA2, LEAP, etc.

[wieman01]

This guide was tested with:

Jaunty Jackalope (9.04)
Oneiric Ocelot (11.10)
--
Since it appears that very few people take wireless security seriously, I'd like to come up with my first HOWTO and explain how I was able to configure a secure home network using WPA2, the latest encryption & authentication standard. There are also other types of configuration (WPA1, mixed mode, LEAP, PEAP, DHCP, etc.) shown in the appendix. Feedback is much appreciated.

Common stumbling blocks - Make sure that:
1. Ethernet cable is unplugged.
2. No firewall & configuration tool is running (e.g. Firestarter).
3. MAC filtering is disabled.
4. NetworkManager, Wifi-Radar & similar wireless configuration tools are disabled/turned off and not in use.
5. Some cards/drivers (e.g. Madwifi) do not support WPA2 (AES). Try WPA1 (TKIP) if WPA2 secured connections fail.
6. Set router to BG-Only if using ndiswrapper (and perhaps Broadcom 43xx as I don't know about others).

My Requirements:
1. WPA2 / RSN
2. AES / CCMP
3. Hidden ESSID (no broadcast)
4. Static IP (because I use port forwarding & firewall, etc.)
5. Pre-shared key (no EAP)

If you want to know more about WPA / RSN & 802.11i security specification, I recommend this site (http://en.wikipedia.org/wiki/IEEE_802.11i).

Now let's get started (wpa-suplicant is usually installed by default):
0. Install "wpa-supplicant":

sudo apt-get install wpasupplicant
1. Verify that your network device ("wlan0"?) is working & your wireless network is detected:

iwconfig

sudo iwlist scan
Your network device & wireless network should appear here.

2. Open "/etc/network/interfaces":

sudo gedit /etc/network/interfaces
The content should look similar to this:

auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dhcp
3. Now replace the last 2 lines with the following using your own network settings (the sequence in which the lines appear is crucial):

auto wlan0
iface wlan0 inet static
address 192.168.168.40
gateway 192.168.168.230
dns-nameservers 192.168.168.230
netmask 255.255.255.0
wpa-driver wext
wpa-ssid <your_essid>
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk <your_hex_key> [IMPORTANT: See "WPA-PSK key generation"]

auto wlan0:
Your network interface (e.g. wlan0, eth1, rausb0, ra0, etc.).


iface wlan0 inet static:
Self-explanatory... I am using a Static IP instead of DHCP. "iface wlan0" must correspond to your network interface (see above).


address, netmask, [..], dns-nameservers:
Also self-explanatory... Be aware that "broadcast" needs to end with ".255" for negotiation with the router. These lines need to be according to your own (static) network settings. For DHCP see further below.


wpa-driver:
Use "wext" only. All other drivers are outdated no longer used.
[/QUOTE]


wpa-ssid:
Your network's ESSID (no quotes ""). Please avoid blanks/spaces as they will created problems during key generation (see below).


wpa-ap-scan:
"1" = Broadcast of ESSID.
"2" = Hidden broadcast of ESSID.


wpa-proto:
"RSN" = WPA(2)
"WPA" = WPA(1)


wpa-pairwise & wpa-group:
"CCMP" = AES cipher as part of WPA(2) standard.
"TKIP" = TKIP cipher as part of WPA(1) standard.


wpa-key-mgmt:
"WPA-PSK" = Authentication via pre-shared key (see 'key generation' further below).
"WPA-EAP" = Authentication via enterprise authentication server.

VERY IMPORTANT ("WPA PSK Key Generation"):
Now convert your WPA ASCII password using the following command:

wpa_passphrase <your_essid> <your_ascii_key>
Resulting in an output like...

network={
ssid="test"
#psk="12345678"
psk=fe727aa8b64ac9b3f54c72432da14faed933ea511ecab1 5bbc6c52e7522f709a
}
Copy the "hex_key" (next to "psk=...") and replace <your_hex_key> in the "interfaces" files with it. Then save the file and restart your network:

sudo /etc/init.d/networking restart
You should be connecting to your router now... However, I figured that a restart is sometimes necessary so that's what I usually do (I know this sounds a bit clumsy - see post #2 for startup script).


*****************************Revoking read-permission from 'others'*********************************

sudo chmod o=-r /etc/network/interfaces
*****************************Revoking read-permission from 'others'*********************************

*****************************Sample configuration WPA2 & DHCP, ESSID broadcast enabled***************

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid <your_essid>
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk <your_hex_key> [IMPORTANT: See "WPA-PSK key generation"]
*****************************Sample configuration WPA2 & DHCP, ESSID broadcast enabled***************

*****************************Sample configuration WPA1 & DHCP, ESSID broadcast enabled***************

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid <your_essid>
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <your_hex_key> [IMPORTANT: See "WPA-PSK key generation"]
*****************************Sample configuration WPA1 & DHCP, ESSID broadcast enabled***************

****************************Sample configuration mixed mode (WPA1, WPA2) & DHCP, ESSID broadcast*****

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid <your_essid>
wpa-ap-scan 1
wpa-proto WPA RSN
wpa-pairwise TKIP CCMP
wpa-group TKIP CCMP
wpa-key-mgmt WPA-PSK
wpa-psk <your_hex_key> [IMPORTANT: See "WPA-PSK key generation"]
****************************Sample configuration mixed mode (WPA1, WPA2) & DHCP, ESSID broadcast*****

****************************Sample conf. LEAP, WEP, DHCP, ESSID broadcast***************************

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid <your_essid>
wpa-ap-scan 1
wpa-eap LEAP
wpa-key-mgmt IEEE8021X
wpa-identity <your_user_name>
wpa-password <your_password>
****************************Sample conf. LEAP, WEP, DHCP, ESSID broadcast***************************

****************************Sample conf. PEAP, AES, DHCP, ESSID broadcast***************************

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid <your_essid>
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-eap PEAP
wpa-key-mgmt WPA-EAP
wpa-identity <your_identity>
wpa-password <your_password>
****************************Sample conf. PEAP, AES, DHCP, ESSID broadcast***************************

*****************************Sample conf. TTLS, WEP, DHCP, ESSID broadcast**************************

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid <your_essid>
wpa-ap-scan 1
wpa-eap TTLS
wpa-key-mgmt IEEE8021X
wpa-anonymous-identity <anonymous_identity>
wpa-identity <your_identity>
wpa-password <your_password>
wpa-phase2 auth=PAP [Also: CHAP, MSCHAP, MSCHAPV2]
*****************************Sample conf. TTLS, WEP, DHCP, ESSID broadcast**************************

*****************************NOT TESTED: Sample conf. EAP-FAST, WPA1/WPA2, DHCP, ESSID broadcast****

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid <your_essid>
wpa-ap-scan 1
wpa-proto RSN WPA
wpa-pairwise CCMP TKIP
wpa-group CCMP TKIP
wpa-key-mgmt WPA-EAP
wpa-eap FAST
wpa-identity <your_user_name>
wpa-password <your_password>
wpa-phase1 fast_provisioning=1
wpa-pac-file /path/to/eap-pac-file
*****************************NOT TESTED: Sample conf. EAP-FAST, WPA1/WPA2, DHCP, ESSID broadcast****

*****************************Tested adapters****************************************** *********

1. Linksys WUSB54G V4 (ndiswrapper; wpa-driver = wext)
2. Intel IPW2200 (Linux driver; wpa-driver = wext)
3. Linksys WPC54G (ndiswrapper; wpa-driver = wext)
4. D-Link WNA-2330 (Linux driver; wpa-driver = madwifi)
5. Linksys WMP54G V2 (ndiswrapper; wpa-driver = wext)
6. D-Link WDA-2320 (Linux driver; wpa-driver = madwifi)
7. Netgear WPN311 (Linux driver; wpa-driver = wext)
8. Netgear WG511v2 (ndiswrapper; wpa-driver = wext)
*****************************Tested adapters****************************************** *********

*****************************Post this if you are stumped******************************************

# route
# iwconfig
# sudo iwlist scan
# sudo lshw -C network
# sudo cat /etc/network/interfaces
# sudo ifdown -v <your_interface>
# sudo ifup -v <your_interface>

*****************************Post this if you are stumped******************************************

*****************************Other useful commands****************************************** ***


# Ubuntu version & kernel >> uname -a
# Root file access >> alt F2 then 'gksudo nautilus' in cli
# Get IP Address or Renew >> sudo dhclient wlan0 [or whatever your wl adapter is]
# Get wireless info >> iwconfig
# Get AP info >> iwlist scan
# Get wireless info >> iwlist (lots of options will list)
# Routes if wlan0 working >> route
# DNS resolving via eth1 >> cat /etc/resolv.conf
# List devices/modules >> lspci, lsusb, lshw, lsmod
# Restart network >> sudo /etc/init.d/networking restart
# Boot messages >> dmesg
# Kill NWM >> sudo killall NetworkManager
# Events from your wl >> iwevent
# Restart all daemons >> sudo /etc/init.d/dbus restart
# Restart network >> sudo /etc/init.d/networking restart
*****************************Other useful commands****************************************** ***

CHANGE LOG:
08/11/2006: Added section "Post this if you are stumped" (SquibT).
08/11/2006: Added sample configuration for WPA2 with DHCP & ESSID broadcast (Wieman01).
08/11/2006: Added sample configuration for WPA1 with DHCP & ESSID broadcast (Wieman01).
08/11/2006: Added section "Tested adapters" (Wieman01).
08/11/2006: Added section "Useful commands" (SquibT).
08/11/2006: Added section "Common stumbling blocks" (Wieman01).
08/11/2006: Changed section "wpa-driver" and added new drivers (Wieman01).
08/11/2006: Added section "Revoking read-permission from group 'others'" (Wieman01).
09/11/2006: Minor changes in layout (Wieman01).
09/11/2006: Added sample configuration for mixed mode (WPA1, WPA2) with DHCP & ESSID broadcast (Wieman01).
09/11/2006: Added experimental sample configuration for LEAP with WEP, DHCP & ESSID broadcast (Wieman01).
09/11/2006: Added section "Install wpa-supplicant" (Wieman01).
10/11/2006: Added experimental sample configuration for TTLS with WEP, DHCP & ESSID broadcast (Wieman01).
15/11/2006: Added experimental sample configuration for EAP-FAST with WPA1/WPA2, DHCP & ESSID broadcast (Wieman01).
04/12/2006: Changed "wpa_passphrase" section & added quotes ("") for encryption keys containing special characters (Wieman01).
04/01/2007: Added various security options (Wieman01).
15/01/2007: Added valid script for EAP-LEAP (Wieman01).
31/01/2007: Added valid script for EAP-PEAP (Wieman01).
21/04/2007: Removed "wpa-conf" for Edgy Eft (Wieman01).
22/04/2007: Simplified section concerning static network settings (Wieman01).
02/05/2007: Added note concerning WPA2 support for Atheros cards & drivers (Wieman01).
13/05/2007: Added note on Ralink drivers (Wieman01).
15/04/2008: Tested with HardyHeron (Wieman01).
04/09/2008: Added note on wireless B/G/N (Wieman01).
06/12/2008: Note for Intrepid Ibex users (Wieman01).
07/03/2009: Closed thread (Wieman01).
05/04/2009: Re-opened and enhanced thread (Wieman01).

[wieman01]

Some users reported (including myself) that the network has to be restarted every time after startup... Apparently this is a bug.

Here is a workaround that helps restart the network during boot so that one does not have to do it manually after logging on to the system.

Create startup script:

sudo gedit /etc/init.d/wireless-network
Add this line & save file:

/etc/init.d/networking restart
Change permission (executable):

sudo chmod +x /etc/init.d/wireless-network
Create symbolic link:

sudo ln -s /etc/init.d/wireless-network /etc/rcS.d/S40wireless-network
[Note: You may have to choose a boot sequence other than S40.]

Restart...

[sionghua]

How to adapt this to WPA(1)?

I got everything setup and running ok, except that it is not automated even though I included the wpa_supplicant command in /etc/network/interfaces so everytime I start my computer I need to run wpa_supplicant manually and then dhclient manually as well in order to access to internet. Any idea why automation is not working?

my interfaces file as follow:


auto wlan0
iface wlan0 inet dhcp
wireless-mode Managed
wireless-essid bplus1
pre-up wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -Bw
post-down killall -q wpa_supplicant
By the way I notice that I need to completely shut down my computer before I login to ubuntu again to make sure the usb adapter refresh, if I simply restart it will not be detected.

[wieman01]

For WPA1 my example would look like this:

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid your_essid
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk your_wpa_psk
I have never bothered to setup wpa_supplicant outside of "interfaces" because I don't think it is nice. So I cannot give you any advice there. However, I am having a similar issue as you whereby I need to initialize my wireless network at startup, then immediately bring it down & restart it. For some reason the network would remain disconnected if I did not restart it.

So my advice is to follow post #2 and restart the network during the boot process. Not sure if this is a bug but I have not found a solution ever since.

[wieman01]

By the way... This also works for Atheros chipsets ("ath0") as shown in here:http://www.ubuntuforums.org/showthread.php?t=225290

[sionghua]

I followed all the instructions but it won't connect, when issuing iwconfig i get

essid: off/any

[sionghua]

here's my wpa_supplicant.conf


ctrl_interface=/var/run/wpa_supplicant
network={
ssid="bplus1"
psk=xxxxxxx
key_mgmt=WPA-PSK
proto=WPA
pairwise=TKIP
}

[sionghua]

Commands that i use to invoke wpa_supplicant is
sudo wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -Bw
and for dhcp
sudo dhclient wlan0

I invoke this commands with

auto wlan0
iface wlan0 inet dhcp
wireless-mode Managed
wireless-essid bplus1
in the interfaces file than it works

[squibT]

@weiman01,

Hi again weiman01...I reinstalled Edgy just to get a fresh start and tried to use this guide to setup my Interfaces file and not use the wpa_supplicant.conf file. If you recall I did have the wpa_supplicant.conf file working and connecting but I wanted to go your route with the Interfaces file.

Good news and bad...My (Linksys wpc54gs)lsbcmnds drivers work fine and report as installed and present, card lights up and flashes connectivity, "iwlist wlan0 scan" reports my AP info correctly (encryption on, correct ESSID ****, etc...) I have a wireless signal meter on the taskbar 100%
This is with the Networking GUI though...and a etc/init.d/network restart reports the key is wrong (obviously..no wpa- in front of any items in the Interfaces file yet.

After setting up your/my Interfaces file (see below):

No internet access, can't get a ping reply from my AP, Iwlist wlan0 scan shows no results .
I have the Interfaces file shown below taken from this HowToo (my IPs are different):

auto wlan0
iface wlan0 inet static
wpa-driver wext (tried ndiswrapper also)
wpa-conf managed
wpa-ssid <my_essid>
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk <my_64_hex_key>
address 192.168.168.40
netmask 255.255.255.0
network 192.168.168.0
broadcast 192.168.168.255
gateway 192.168.168.230
dns-nameservers 192.168.168.230

I tried enabeling wireless via the GUI. Are you also using the Networking GUI and enabling your wireless there also? When I do and I enter the basic information it writes in to the bottom of your/my Interfaces file this:

My_ip_information....
wireless-essid <my-essid>
wireless-key <my-hex-key>

auto wlan0

Basically adding these lines again...incorrectly.

If I modify the file it does not work...

And "/etc/init.d/network restart" cant read the Interfaces file.

And if I just use your/my config file exactly as you wrote it, "/etc/init.d/network restart" reads the Interfaces file OK but still no connection...like it is not communicating with WPA_Supplicant...or my router....router is setup correctly though.
Iwconfig shows not associated with AP ( of course)
Iwlist wlan0 scan shows no results.

Your file seems to be the closest I have got to getting this going...no errors when I "/etc/init.d/network restart"...just says Reconfiguring then OK which is great.

Using just a basic Interfaces file with no security "iwlist wlan0 scan" reports my AP info correctly (encryption on, correct ESSID ****, etc...) I have a wireless signal meter on the taskbar 100%...

I am missing something...

Any ideas? I dont want to take a lot of your time but if you can think of anything I am missing let me know.

Thanx,

squibt

[squibT]

Success!

I was using my 64 char hex key from my router (WPA-PSK AES) and not using the directions on page 4 of your instructions. I entered my hex key and it would not work in the Network-Applet Hex box or in the Interfaces file. It seems I have to use an Ascii pass-phrase like BillyBob on my router and then in the Network-Applet enter my info and then run wpa_passphrase <my-essid> <BillyBob (my ascii-key)> to generate a psk hex key....this new key is entered into your Interfaces file like you state on page 4.

Let me experiment with this a little and get back to you...gonna try to use my hex key as a ascii key and regenerate it.

BTW...nice HowToo...if you follow it....](*,) :-D

squibt

[squibT]

So it looks like you CAN use your routers 64 hex key to setup your Network-applet and Interfaces file.

I took my 64 char hex key and entered it in both the ascii and hex boxes (different times) and then followed page 4 of your doc and generated a psk for the Interfaces file. Entering both (at different times) worked fine. The only problem is at sudo /etc/init.d/networking restart....

* Reconfiguring network interfaces... Error for wireless request "Set Encode" (8B2A) :
invalid argument "0EGgN94V5rER1EAGNw7KIGOTJbfyBNoT3UQEeblubdYLvMZAPy YRk93CwPgGvdR".
That is my real hex key the Network-applet adds to your/my Interfaces file along with another entry for my ESSID, both at the bottom of the file. Delete them and restart networking and you get just an OK and no error.

AES works fine...same key I always had...no wpa_supplicant.conf file used.

Thanx weiman01...great HowToo....I just needed to understand the process a little better and not rely on what I thought was the correct procedure...read page 4 :-D

squibt

[wieman01]

Hi Squibt,

Reading this makes me smile... You have probably fallen into every single trap I have fallen into myself. So you have my sympathy... :-) Apparently you need no more help, but I'd appreciate if you posted your "interfaces" file just for the fun of it. I am a bit nosy, that's all.

By the way... The Networking Applet won't help you in Dapper as it does not have a WPA option. Does the Edgy one have??

EDIT:
What "page 4" of my documentation are you referring to??? You mean the other thread mentioned?

[squibT]

Hi Squibt,

Reading this makes me smile... You have probably fallen into every single trap I have fallen into myself. So you have my sympathy... :-) Apparently you need no more help, but I'd appreciate if you posted your "interfaces" file just for the fun of it. I am a bit nosy, that's all.

By the way... The Networking Applet won't help you in Dapper as it does not have a WPA option. Does the Edgy one have??

EDIT:
What "page 4" of my documentation are you referring to??? You mean the other thread mentioned?

Hey weiman01,
Lol...traps is right! but this thread and a little research was key to understanding what Edgy needs to get wl going. This "doc" is point number 9 of this thread...sorry I was not clear...when it prints out on paper page 4 is the key to getting your Internet connection working with any type of encryption...
I think it is on the first page of this same thread you will see the below quote...

>>9. address, netmask, network, broadcast, gateway, dns-nameservers:
>> Also self-explanatory... be aware that "broadcast" needs to end with ".255" for negotiation with the router. These lines need to be according to your own network settings.

As for WPA-PSK key generation, type the following command in a terminal:

Quote:
wpa_passphrase <your_essid> <your_ascii_key>
Resulting in an output like...

Quote:
network={
ssid="test"
#psk="12345678"
psk=fe727aa8b64ac9b3f54c72432da14faed933ea511ecab1 5bbc6c52e7522f709a
}
Copy the "hex_key" (next to "psk=...") and replace <your_hex_key> in the "interfaces" files with it. Then save the file and restart your network:

Quote:
sudo /etc/init.d/networking restart
You should be connecting to your router now...<<


Edgy's Networking_applet does not allow for any obvious differences in configuration...they just removed the word WEP and changed it to Network Password....I am thinking you do not need to use it at all to get setup or connected.....just follow your HowToo. Right now my wireless setup in the Networking_applet is now disabled...I enabled it to set it up last night thinking that was how Edgy would know I had a card, ESSID, PSK, etc....but I am thinking now it is not needed. Im guessing you did not use it? If you do use it you get this at the bottom of your Interfaces file:

auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet static
wpa-driver wext
wpa-conf managed
wpa-ssid Digger
wpa-ap-scan 2
wpa-proto RSA
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 2e89d446b73d2281c685f087c76742bb2409b17f175774acdd 82b3e438f0580a
address 10.18.81.25
netmask 255.255.255.0
network 10.18.81.0
broadcast 10.18.81.255
gateway 10.18.81.2
dns-nameservers 10.18.81.2
wireless-essid Digger
wireless-key 0EGgN94V5rER1EAGNw7KIGOTJbfyBNoT3UQEeblubdYLvMZAPy YRk93CwPgGvdR


That is my routers hex key entered into the Network_applet....you can simply delete the two lines and your Interface file works fine using /etc/init.d/networking restart....if you don't delete the lines /etc/init.d/networking restart, at cli, will generate errors but still work. Of course you still have to generate a wpa_passphrase like page 4 says "wpa_passphrase <essid> <hex or ascii key>"

and enter it into your Interfaces file. So I am thinking you do not need the Networking_applet at all for this. Just use an Interfaces file with a generated psk.

My config file:

auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet static
wpa-driver wext
wpa-conf managed
wpa-ssid Digger
wpa-ap-scan 2
wpa-proto RSA
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 2e89d446b73d2281c685f087c76742bb2409b17f175774acdd 82b3e438f0580a
address 10.18.81.25
netmask 255.255.255.0
network 10.18.81.0
broadcast 10.18.81.255
gateway 10.18.81.2
dns-nameservers 10.18.81.2

You can see the psk is the one generated by Edgy...not the one I have in my router or the one I put in Networking_applet (which is now turned off for all devices...actually it is on but all devices are not enabled....not needed)

Anyway...TKIP, then CCMP worked fine for me also....easy and quick change in testing. I think a lot of people do not understand this procedure and are getting stuck trying to config wl....some are using wpa_supplicant like I was but I believe this is the recommended configuration. It is simple if your drivers show they are working and active before you start configuring the Interfaces file.

Thanx again,

squibt

[wieman01]

The Gnome networking applet does WEP only. That's why it adds those 2 lines at the bottom of the "interfaces" configuration file. That's WEP terminology:

wireless-key 0EGgN94V5rER1EAGNw7KIGOTJbfyBNoT3UQEeblubdYLvMZAPy YRk93CwPgGvdR
So yes, we can forget about the applet if we use WPA.

If you choose to set up WPA encryption/authentication using "interfaces" then wpa_supplicant will configure "/etc/wpa_supplicant.conf" for you. The file is still there & apparently used by the system, it's just the way of controlling it what is different. Check it out on your system.

Ok, I think it makes probably sense to enhance this documentation & include WPA1, WEP, LEAP, EAP, etc. as well as other chipsets. Perhaps there is a chance that we get together soon.

[squibT]

So the Network_applet is misleading...they just renamed the Key box from WEP to Network Password....be nice if it would have the options WEP, WPA1, WPA2, Radius,...whatever and have it really config your Interface file for you. And allow you to enable and disable an interface via this tool so you can switch between wl and wired. Right now if you mess with the wl in it it sometimes deletes all your Interfaces settings. And too it seems a bit odd you can enter your Hex key from your router say....but it is not recognized by Edgy as a valid key....you have to tell Edgy to make a new key for the Interfaces file...from your router key...seems like a needless duplication to me.

Anyway, I will test out WEP, WPA1 (AES/TKIP fall back), WPA2 going by the HowToo step by step to make sure all works like it should.

I will keep in touch....

squibt

[wieman01]

Yes, I think the default network applet is kind of flawed. That's why most people prefer NetworkManager over the applet, however, NetworkManager has certain drawbacks (e.g. no support for static IP or hidden ESSID, etc.) that make it impossible for me to use.

BTW: AES (CCMP) is part of the WPA2 specification as opposed to TKIP (WPA1). You'll find all the technical details on the Wikipedia website.

EDIT:
Or more precisely, this guide covers what most people refer to as WPA2: AES with PSK (pre-shared key) rather than EAP (Extensible Authentication Protocol). The latter requires a authentication server which is costly & complex and therefore not suitable for home use. I have never tried out the full implementation of 802.11i (= WPA2) including an EAP server, simply because I don't happen to have one back home. My company has implemented it of course, but you can do nothing in a Windows based environment.

[squibT]

I guess Ubuntu/Edgy still needs some wl app-driver connectivity work...we will have to be patient till the devs get around to it and the IT community and companys dealing in wl products in general come more on onboard with Linux...and stop holding their proprietary drivers so close to their vests.

The reason why I included AES/TKIP is that I am using DD-WRT on my routers and have the options TKIP, AES, TKIP+AES which is supposed to give the client the option to fall back to TKIP if they cannot do AES....dunno if it works but I will test this also.

Later...

[wieman01]

This does work also... You can simply add options:

auto wlan0
iface wlan0 inet static
wpa-driver wext
wpa-conf managed
wpa-ssid <your_essid>
wpa-ap-scan 2
wpa-proto WPA RSN
wpa-pairwise TKIP CCMP
wpa-group TKIP CCMP
wpa-key-mgmt WPA-PSK
wpa-psk <your_hex_key>
address 192.168.168.40
netmask 255.255.255.0
network 192.168.168.0
broadcast 192.168.168.255
gateway 192.168.168.230
dns-nameservers 192.168.168.230
RSN stands for WPA2 actually; CCMP "kind of" for AES.

[mahy]

Hi,

what about moving around with a laptop? Will have to edit /etc/network/interfaces everytime i come across a new network? (Pretty clumsy, eh?) I hope not so. Can you explain it to me?

[wieman01]

Hi,

what about moving around with a laptop? Will have to edit /etc/network/interfaces everytime i come across a new network? (Pretty clumsy, eh?) I hope not so. Can you explain it to me?
In that case you have 2 options I am aware of:

1. gnome-network-manager (GUI), network-manager (daemon)
2. wifi-radar

Hope this helps.

[tedrogers]

Can you please explain (and sorry for being a dumbass) what the typical equivalents of these are:

address 192.168.168.40
netmask 255.255.255.0
network 192.168.168.0
broadcast 192.168.168.255
gateway 192.168.168.230
dns-nameservers 192.168.168.230

I'm just a bit confused between address and network, broadcast and dns-nameservers.

Netmask and gateway are easy.

Another thing....if I set all this up by DHCP (i.e. replace STATIC with DHCP in the interfaces file) - do I even need to bother setting any of the IP addresses for the router?

Thanks.

[wieman01]

DHCP is - of course - possible. See post #4 (WPA1). In that case you would not have to worry about address, netmask, etc. Still want to know what address and network, broadcast and dns-nameservers stand for?

[tedrogers]

Thanks...and yes...what are the equivalents of these. Ubuntu seems to call things by different names...e.g. why would AES be CCMP?? I'd never guess this.

Not had much luck with WPA so far, tried for 6 hours last night...will keep at it though. Have posted in lost of places, some of them were yours.

Also, is there any reason why I can't use a 63 character PSK?

And...why don't I have a wpa_supplicant.conf file in /etc? Should I have one of these?

Finally (for now) - could you replace the line 'wext' for 'ndiswrapper'?

Thanks.

[wieman01]

I have replied to you in the other thread.

1. You have probably skipped the part where I mention the PSK key generation (passphrase).
2. "wext" is the right driver for "ndiswrapper". The latter is obsolete.
3. The relationship between CCMP & AES is explained in the Wiki (link also given). They explain it in a much more accurate manner than I could possibly do.
4. "/etc/wpa_supplicant.conf" was part of the previous versions of "ndiswrapper". The latest once don't seem to have it by default.
5. I send you a link on networking later on.

[apis]

Wow! I just did it! I was desperate before I encountered this thread! You did really good job guys! Thanks for that! :D

I used "Sample configuration WPA1 & DHCP, ESSID broadcast enabled" and it worked perfectly for my hardware.

Linksys WMP54G rev2 (Broadcom 4306) PCI network card and router Linksys WRT54G.

[wieman01]

Wow! I just did it! I was desperate before I encountered this thread! You did really good job guys! Thanks for that! :D

I used "Sample configuration WPA1 & DHCP, ESSID broadcast enabled" and it worked perfectly for my hardware.

Linksys WMP54G rev2 (Broadcom 4306) PCI network card and router Linksys WRT54G.
Using "ndiswrapper"? And what "wpa-driver" are you using (I assume "wext")? Just for the record...

[Dr. Cox]

hi there,

i've tried your instructions for wpa1,etc. only problem for me is that my essid is hidden and not being broadcasted.
iwlist scan notices the signal being present as well as the channel.

i tried your sample for wpa1, dhcp and tried both, wpa-ap-scan 1 as well as 2. it wouldn't work.

sometimes it just didn't work without any error message.
sometimes it gave me error 9 or error 10, i think, saying that ifup and ifdown couldn't read or open /etc/network/interfaces

any idea? i'm sorry i couldn't provide the usual output you asked for, but i've i-net only at work right now. any help is appreciated.

cheers

[wieman01]

That's a tough question... "wpa-ap-scan 2" is certainly the right setting if the broadcast of ESSID is disabled. It would certainly help if you posted your "interfaces" config-file and told us a bit more about your card/chipset. I am sure we can resolve this.

As for the read-permission... Please check if "interfaces" has the right permission settings:

ls -l /etc/network/
If not that's how you change the permissions:

sudo chmod ug=+rw /etc/network/interfaces

[Dr. Cox]

it's a intel centrino ipw2100 wireless chipset.
read and write permission are granted.
i also tried running it as root.
didn't change anything. try to post config files tonight

cheers

[wieman01]

it's a intel centrino ipw2100 wireless chipset.
read and write permission are granted.
i also tried running it as root.
didn't change anything. try to post config files tonight

cheers
That'd be best... Post the error message you encounter at the same time.

[apis]

Using "ndiswrapper"? And what "wpa-driver" are you using (I assume "wext")? Just for the record...

I am using ndiswrapper and wext, it looks like wpa_supplicator doesn't work with standard bcm43xx driver, although if you don't need WPA bcm43xx works reasonably well. Few more details I am on edgy and ndiswrapper and wpa_supplicant are from standard edgy repositories as well. And I also have issue with network restart.

[DavidTangye]

This thread resulted in my getting a Broadcom 4318 wireless installed and running with WPA(1) under Edgy. I am basically using your example '*Sample configuration WPA1 & DHCP, ESSID broadcast enabled*' from your message #1. Thanks very much.:D

A slight improvement on this is that actually, to get wireless up at bootup, all you need is to do this as root:

echo 'ifdown wlan0' >/etc/init.d/WlanDown
chmod +x /etc/init.d/WlanDown
ln -s ../init.d/WlanDown /etc/rcS.d/S40WlanDown
This runs S40WlanDown just before S40networking, so tidies up something in the wlan setup. Then S40networking runs ../init.d/networking which runs 'ifup -a' which successfully starts wlan0 and all other interfaces.

The source problem is a bug whereby at shutdown 'ifdown -a' does not seem to run (successfully) :not effectively doing an 'ifdown wlan0'.

Now I just gotta find again (for the record) where is the other forum message that told me where to get a tarball, that had the driver, and a script to do a lot of the work for me.

[wieman01]

This thread resulted in my getting a Broadcom 4318 wireless installed and running with WPA(1) under Edgy. I am basically using your example '*Sample configuration WPA1 & DHCP, ESSID broadcast enabled*' from your message #1. Thanks very much.:D

A slight improvement on this is that actually, to get wireless up at bootup, all you need is

This runs S40WlanDown just before S40networking, so tidies up something in the wlan setup. Then S40networking runs ../init.d/networking which runs 'ifup -a' which successfully starts wlan0 and all other interfaces.
Great. Thank you as well for the script. I will try it out sometime this week & update the guide.

Would you mind sharing your configuration with us? So the I can take a glance at the "wpa-driver", etc. Just curious, and it it perhaps helpful for others with Broadcom chipsets as well.

[tedrogers]

This thread resulted in my getting a Broadcom 4318 wireless installed and running with WPA(1) under Edgy. I am basically using your example '*Sample configuration WPA1 & DHCP, ESSID broadcast enabled*' from your message #1. Thanks very much.:D

A slight improvement on this is that actually, to get wireless up at bootup, all you need is

This runs S40WlanDown just before S40networking, so tidies up something in the wlan setup. Then S40networking runs ../init.d/networking which runs 'ifup -a' which successfully starts wlan0 and all other interfaces.

The source problem is a bug whereby at shutdown 'ifdown -a' does not seem to run (successfully) :not effectively doing an 'ifdown wlan0'.

Now I just gotta find again (for the record) where is the other forum message that told me where to get a tarball, that had the driver, and a script to do a lot of the work for me.

Hi,

I assume by 'bootup' you mean outside of X windows in a plain old terminal? Before X is loaded, perhaps in Recovery Mode?

I can see why this would be useful.

Thanks.

[wieman01]

Hi,

I assume by 'bootup' you mean outside of X windows in a plain old terminal? Before X is loaded, perhaps in Recovery Mode?

I can see why this would be useful.
Yes, this kind of operation can only be run as "root" process. Once X is up & running you are sort confined as to what process you can run. That's to do with Linux' architecture (without going into detail). Found this link which may be interesting in that respect:

https://wiki.ubuntu.com/StreamlinedBoot?highlight=%28rcs%29

[tedrogers]

When I run this in X windows...


echo 'ifdown wlan0' >/etc/init.d/WlanDown
ln -s ../init.d/WlanDown /etc/rcS.d/S40WlanDown

...I get permission denied...even with sudo appended to the front.

Do I need to run this in a root terminal, or by CTRL + ALT + F1 and logging in?

Also have you tried this yet Wieman?

Thanks.

[wieman01]

Deleted...

[tedrogers]

Even if I run these using sudo...


sudo echo 'ifdown wlan0' >/etc/init.d/WlanDown
sudo ln -s ../init.d/WlanDown /etc/rcS.d/S40WlanDown

...I get permission denied.

Could this be because of the chmod command we ran before to change permissions on the wlan config files?

[tedrogers]

Sorry for the double post here, but the solution is listed at this post:

http://ubuntuforums.org/showthread.php?t=299651

Basically, these commands need to run at a root terminal. To get access through a normal terminal, type the following:


sudo -i

Then issue these commands without the 'sudo' prefix (as mentioned by me previously).


echo 'ifdown wlan0' >/etc/init.d/WlanDown
ln -s ../init.d/WlanDown /etc/rcS.d/S40WlanDown

Alternatively, you should be able to run the root terminal from the Application > System Tools menu...as long as you have enabled this option within the Preferences > Menu Layout configuration.

Hope this helps.

[DavidTangye]

sudo echo 'ifdown wlan0' >/etc/init.d/WlanDown

Yes this line is incorrect because >/etc/init.d/WlanDown is checked in the shell that presents that line, ie your current shell. At that point 'you' are the command presenter not root, so 'you' get the erro message that 'you' do not have the necessary permissions, and the sudo command is not even attempted.

This works:

sudo bash -c 'echo "ifdown wlan0" >/etc/init.d/WlanDown'

because here the access to /etc/init.d/WlanDown is not attempted until a bash shell is run by the user root.

The command "echo 'ifdown wlan0' >/etc/init.d/WlanDown" must be run by root, from a bash shell started by, eg

"sudo -i" (login fully and run your default shell, probably bash), or
"sudo bash" (just run a bash shall)
"sudo bash -c ... " (just run a single command in a bash shell as per above)

[giruzz]

Success!

Thansk to SquibT and wieman01 for your guide. I just switched from WinXp and everything worked without problems.

FYI, I first followed another guide (the one that you can find in the wiki section) and didn't work. Following your instructions solved all my problems in 30sec :D

Great job!

giruzz

[wieman01]

Since it's a pretty common & popular wireless card, I am including a sample configuration for IPW2200, DHCP, WPA1 (TKIP), broadcast of ESSID enabled.

auto lo
iface lo inet loopback

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid your_essid
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk MY_GENERATED_PSK_THINGIE
Thanks to user "Karmapolice" for it. Perhaps this helps others.

[giruzz]

Just one little problem...

now when the system is re-booting it takes ages to start...

this because the system is re-starting my lan card and because there isn't a cable connected the system waits..and waits...and finally goes on timeout...

just wondering..there is any way to re-restart only the wifi card?

thanks

giruzz

[wieman01]

Just one little problem...

now when the system is re-booting it takes ages to start...

this because the system is re-starting my lan card and because there isn't a cable connected the system waits..and waits...and finally goes on timeout...

just wondering..there is any way to re-restart only the wifi card?
Can you try post #32 / #40 instead of my script? Would that help? If not, we go for plan B.

[giruzz]

Sorry,

not sure I understood what I should change the current

networking script with the script of post #32?

thanks

giruzz

[cantormath]

Nice tutorial.

[wieman01]

Sorry,

not sure I understood what I should change the current

networking script with the script of post #32?
Yes, please delete my stuff & try the other script. That's all.

[tedrogers]

Wieman01 means that all of the posts on this forum are numbered on the right hand side...he is just asking you to use the script listed in post number 32 instead .

[giruzz]

Sorry..but I cannot get it work....

I'm really sorry..but I couldn't understand where to replace what... (ok..I know I have to change/delete the old script)

(I'm a n00b)

byeee

g.

[tedrogers]

I think this is right. First get to a Root Terminal (not the regular terminal). You get to a Root Terminal by running this code in a normal terminal:


sudo su

Now enter your password and you are now a root (super)user.

Right, here is the code from post number 32:


echo 'ifdown wlan0' >/etc/init.d/WlanDown
ln -s ../init.d/WlanDown /etc/rcS.d/S40WlanDown

Try running this in the Root Terminal. Make sure you copy and paste each line seperately...do not copy and paste both lines as this will not work. Do each line at a time.

Then make it executable (so it can be run at startup) using this command:


chmod +x /etc/init.d/WlanDown

Once you have done this, try rebooting and see if your wireless wlan works on reboot.

If it doesn't work try using the code from post number 40, which you can run in a normal terminal I believe (but if it doesn't work try as a root terminal just like above):


sudo bash -c 'echo "ifdown wlan0" >/etc/init.d/WlanDown'

Don't forget to make it executable (so it can be run at startup) using this command:


chmod +x /etc/init.d/WlanDown

Then restart again and see if that has fixed it for you.

[wieman01]

Obsolete...

[giruzz]

Thanks for your help.
I couldn't make it work.

I opened a new thread here (http://ubuntuforums.org/showthread.php?p=1799852#post1799852),

I hope that somebody can help me!

thanks

g.

[tebibyte]

You have to go through all this just to get WPA to work? This is absolutly rediculous. Users shouldn't even have to go to the command propmt to use something that is used this widely.

[tedrogers]

There really is only about 4 -5 steps to get it working.

Yes...it should work out of the box...but with some wireless pcmcia (inc. broadcom chips) it doesn't...so this is the fix.

This ain't win-blows - but it's free (!!) and just as good once you are up and running.

Don't get me wrong...this is one of the more problematic areas - most stuff works straight out of the box.

Don't get disheartened...the community is here to help you.

[wieman01]

You have to go through all this just to get WPA to work? This is absolutly rediculous. Users shouldn't even have to go to the command propmt to use something that is used this widely.
There are options: NetworkManager or Wifi-Radar... However, all of these tools have certain drawbacks. Nonetheless, see for yourself what's the best solution. Wireless support in Linux is not yet perfect, in particular when it comes to EAP.

[aysiu]

You have to go through all this just to get WPA to work? This is absolutly rediculous. Users shouldn't even have to go to the command propmt to use something that is used this widely.
Good thing the Ubuntu developers are working on improving this.

[tedrogers]

This is good to hear.

Do ya think they'll include (by default) build-essential, w32codec and the rest of the stuff we all use in the next release?

Fingers crossed.

[aysiu]

This is good to hear.

Do ya think they'll include (by default) build-essential, w32codec and the rest of the stuff we all use in the next release?

Fingers crossed.
No, they won't.

w32codecs are owned by Microsoft, and they've decided for "security reasons" that build-essential won't be installed by default (I happen to disagree, but that's their decision).

[tedrogers]

I suspected that thye might think that build-essential might be a bit dangerous for new users...but I have to agree with you that I don't quite see how.

[usererror]

Kudos to those have have contributed to this thread and the original poster! this is great. Using the WPA1 sample and my Intel 3945 wifi card it worked perfect on the 2nd try! (first try was user error :D )

I am now trying to test the EAP-FAST environment. At work we are in a domain environment, which requries EAP-FAST using DOMAIN\username format with domain password, the certificate and WEP...

If anyone has any ideas off the bat i'm open to them. I'm working from the EAP-FAST sample on page 1 of this thread. :)

[wieman01]

I am now trying to test the EAP-FAST environment. At work we are in a domain environment, which requries EAP-FAST using DOMAIN\username format with domain password, the certificate and WEP...
Excellent. I was actually looking for users that could test EAP scripts for me. Back home I don't happen to have an authentication server... Please don't hesitate to ask for help. I really want to sort this out & update the thread. Thank you!

[tedrogers]

Hi,

I just went back from Edgy to Dapper...and the weird thing for me is that all instances of wlan0 in the /etc/network/interfaces file had to be changed to eth1 for it to work.

So in order to get it to work I had to change this:


auto wlan0
iface wlan0 inet dhcp
etc...

...to this:


auto eth1
iface eth1 inet dhcp
etc...

Does anyone know why this is?

Is there a way I can change this so that my wireless is called wlan0 and not eth1.

Forgive me for being picky, but I like it to be called what it actually is! It's less confusing that way.

Thanks.

[wieman01]

Hi Ted,

Let's discuss this on another thread in detail. Hard to tell what the problem is but "wlan0" usually refers to "ndiswrapper" which I don't think is installed in a fresh system. I reckon your wireless card has been recognized out of the box, hence the system refers to your interface as "eth1".

That said, let's discuss that in another (more appropriate) thread.

[roachk71]

Many thanks indeed!

Before these hints were available I kept trying (unsuccessfully each time) to configure wpasupplicant using the advanced method; this procedure has changed to the simpler /etc/network/interfaces approach since Hoary.

An extremely helpful set of instructions! 8)

By the way: My card's a Netgear WG511v2 (Made in China, Libertas chipset); if anybody else has this card, you don't really have to compile a custom kernel to make it work (unless your computer has a high-end AMD,) but you need the server kernel and headers, along with build-essential and the latest NDISwrapper from source.

Once you've installed the necessary packages (and you're running the newly-downloaded kernel,) unpack the NDISwrapper tarball and follow the instructions in the INSTALL document, then use this configuration for the card.

Another thing: Some computers won't keep the link up (this is a bug, which is easy to remedy.)

From the terminal, type:

sudo gedit /etc/init.d/wireless-network.sh
and add this line:

/etc/init.d/networking restart

Save this file and exit your text editor. Then, create a symlink:

sudo ln -s /etc/init.d/wireless-network.sh /etc/rcS.d/S42wireless-network

Now, make this change executable (nearly forgot):

sudo chmod +x /etc/init.d/wireless-network.sh

and restart. Your card should be up and running after the reboot. Enjoy!

[jinhr]

I am using WPA2 +AES with hidden ESSID.
Router = Linksys WRT 54GC
Laptop = IBM Thinkpad R52 with iwp2200.

Here are my successful codes.

===start===
auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid skywalker
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 3c00852a3d2ab654d7290a98534d8574d1aca3061621d6cd47 9e1275c145802a
===end===

The only problem:
I can not run "/etc/init.d/networking restart" without sudo.

jinhr@Ubuntu:~$ /etc/init.d/networking restart
open: Permission denied
* Reconfiguring network interfaces... ifdown: failed to open statefile /var/run/network/ifstate: Permission denied
ifup: failed to open statefile /var/run/network/ifstate: Permission denied
open: Permission denied
[fail]

I checked "ls -ln /var/run/network/ifstate" which says:
-rwxr-xr-x 1 0 0 26 2006-12-12 00:22 /var/run/network/ifstate

I think I can not run the sh file at start up due to no-right for "/var/run/network/ifstate"

Can wieman01 help me on this?

Currently I have to type manually "sudo /etc/init.d/networking restart" after ubuntu starts up.

[wieman01]

Hello Jinhr,

Post #2 definitely works... Just follow the steps given & restart the computer. All init-script are run by the system with root privileges, so you don't have to worry about "sudo" at all. Simply add the mentioned script & reboot. That's it.

I have a IPW2200 as well & therefore I can confirm that this works.

[sefs]

This is the best wpa tutorial ever!

Finally i am able to move from wep to wpa and did not even have to fiddle with networkmanager or wpasupplicant or any of that nonsense.

Thanks to the creator of this great tutorial!

I'm using a cnet usb key (Ralink - RT73) with ndiswrapper and the windows drivers for this card that came on the CD

[Floor19]

Thanks for this great HOWTO, finally i can use WPA encryption with the WPA2 only conf file and a Linksys WPC54G PMCIA card.

I only have one problem.

With the PMCIA plugged in i can't get past the login screen. Everything loads fine but after entering my login and password i get a black screen with only my mouse symbol visible (no lockup)

Without my card plugged in I can login as normal and when i plug in the card ndiswrapper loads my conf file i am up and running.

It works but does someone knows the problem for the black screen?!

Thanks and again for the HOWTO.

Floor

EDIT

added the folowing lines in etc/network/interfaces and no more problems with startup.

auto lo
iface lo inet loopback

Cheers!

[compwiz18]

Great tutorial.

You are right, it is far easier then using the wpa_supplicant.conf file. Just pop the settings in, restart networking, and you're connected :D

Now to make connection-manager do this automatically.

And I'm gonna need some to test LEAP, like we discussed.

[compwiz18]

Question: It would appear that the dns-nameservers line doesn't do anything, and I can't find anything about it in the man interfaces manual page...

any ideas?

thanks again for your help and this tutorial

[wieman01]

Please let us know once your "network-manager" is ready. I will post a link to your site in my tutorial because I am really convinced it could make "life" considerably easier.

As for "dns-nameserver", it does serve a purpose. As the name suggests this refers to the IP address of the server that resolves domain names & lets you browse the Internet using words rather than IP addresses. :-) Since routers normally act as gateways & communicate with DNS servers provided by your ISP, all you have to do is state your gateway's IP address here. Using STATIC IP rather than DHCP requires you to set the DNS server manually as well. Does that more or less answer the question?

[compwiz18]

Right. But it doesn't update resolv.conf with the new addresses...which is what is confusing me. Am I correct in thinking that /etc/resolv.conf should be updated with those addresses when I sudo /etc/init.d/networking restart?

[wieman01]

I would think that "/etc/resolv.conf" updates itself... Usually there is no need to update it yourself, it takes whatever information is available through "/etc/networking/interfaces".

[compwiz18]

I would think that "/etc/resolv.conf" updates itself... Usually there is no need to update it yourself, it takes whatever information is available through "/etc/networking/interfaces".
Well, it doesn't seem to be updating automatically. Oh well, not a giant problem, I'll just have the program update it. I'm just wondering why it doesn't do it by itself.

Thanks for you help, and thanks for the great tutorial.

[uber_nerd11]

I know that some people are working on different EAP situations, so I have a question concerning that. The university I am attending is using WPA or WPA2 Enterprise with PEAP and a security certificate. For Windows machines the network fails if they do not have the right certificate selected for use. When I signed on to the wireless for the first time it asks for my username and password for the school as it should. From there everything works fine even though I don't have a certificate set. My first question is where can I go to get the security certificates? My second is am I still securely using the network even though I don't have a security certificate tied to the connection?

[wieman01]

My first question is where can I go to get the security certificates?
You network administrator should provide it. So the first thing you should do is get in touch the staff there.

My second is am I still securely using the network even though I don't have a security certificate tied to the connection?
Well, you probably won't be able to authenticate and hence connect to the university network. That's the whole point of a certificate: authentication.

That said, I would use NetworkManager for EAP-PEAP. Of course I appreciate if you tested the scripts given, but it's probably wasting your time so I recommend that you take a look at this thread (http://www.ubuntuforums.org/showthread.php?t=316582&page=2&highlight=PEAP). The guy also attached a screenshot of NetworkManager which is a tool that actually supports PEAP out of the box. No need to mess around with text files as it seems.

[compwiz18]

Which in the first post would be used for PEAP?

Again, thanks for your help.

[wieman01]

Which in the first post would be used for PEAP?

Again, thanks for your help.

I have not published anything with regard to PEAP... But let's try to work it out together:

EAP-PEAP (MSCHAPV2):

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid your_essid
wpa-ap-scan 1
wpa-eap PEAP
wpa-key-mgmt WPA-EAP
wpa-identity your_identity
wpa-password your_password
wpa-ca-cert /etc/cert/ca.pem
wpa-phase1 peaplabel=1
wpa-phase2 auth=MSCHAPV2
wpa-priority 10
But we need someone who has got access to a RADIUS server and can test this for us... Settings are:

>> EAP-PEAP
>> ESSID broadcast enabled
>> DHCP
>> Network interfaces = eth1

[compwiz18]

Thanks :D

Is it possible to run a RADIUS server in Ubuntu? (Never mind, I searched the Repos, it is) My router is capable of using a RADIUS server, so maybe I'll see if I can get that to fly. Chances are I won't though, so if someone else out there has access to an already setup RADIUS server, that would be helpful.

edit: i gave up on the setting-up-a-RADIUS-server idea, so if someone could test it, thanks :D

[uber_nerd11]

The security certificate is one of the one's that come with WINXP. Its the Equifax Secure Certificate Authority one. I didn't know if there was a way to import this and other default certificates or if there were Linux versions of them out there. I have been able to connect to the wireless here on campus, so thats why I was curious about my security. I am currently using Network Manager. It was suggested to me when I first installed Ubuntu. Thanks.

[wieman01]

Thanks :D

Is it possible to run a RADIUS server in Ubuntu? (Never mind, I searched the Repos, it is) My router is capable of using a RADIUS server, so maybe I'll see if I can get that to fly. Chances are I won't though, so if someone else out there has access to an already setup RADIUS server, that would be helpful.

edit: i gave up on the setting-up-a-RADIUS-server idea, so if someone could test it, thanks :D
You router certainly has a RADUIS setting, however, you need to set up a RADUIS to support it. The RADIUS function only allows you to connect to a dedicated RADIUS server. I am sure you would be able to set it up using Ubuntu. I would do it, unfortunately I will be on the road in the next couple of weeks.

EDIT:
I asked other users to help me with testing a while ago... Perhaps we can make use of this thread (http://www.ubuntuforums.org/showthread.php?t=304706). Feel free to join in. Really like to see this go ahead.

[compwiz18]

I just finished incorporating all the info into connection-manager on the first page of this thread, and it works like a charm :D at least for wpa2 and hidden essid and static ips, and normal unsecured visible dhcp.

And I'll put a note on my thread asking for users to test. maybe between us we can get a couple.

thanks again.

[wieman01]

I just finished incorporating all the info into connection-manager on the first page of this thread, and it works like a charm :D at least for wpa2 and hidden essid and static ips, and normal unsecured visible dhcp.

And I'll put a note on my thread asking for users to test. maybe between us we can get a couple.

thanks again.
Man, that's great. I will give it a go soon & post a link to your site/package after testing it myself. Good job, buddy.

[compwiz18]

I need to finish the GUI, I'll do that tomorrow. But the hard part (the part that does the work) is finished. I hope to release it by December 25. But I'll PM it to you first (as soon as it is done) so you can have a look and make sure it works.

[usererror]

I am having a heck of a time getting this to work in my network environment:

We use the following:

EAP-FAST (using our active directory username and password)
Dynamic WEP
802.1x Authentication
Open Authentication.

I tried using the EAP-FAST (untested one in the howto) and it does not connect me. Does anyone else have this type of network environment? ](*,)

[wieman01]

Have you tried this?

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid <your_essid>
wpa-ap-scan 1
wpa-group WEP104 WEP40
wpa-key-mgmt IEEE8021X
wpa-eap FAST
wpa-identity <your_user_name>
wpa-password <your_password>
wpa-phase1 fast_provisioning=1
wpa-pac-file /path/to/eap-pac-file
You also need the stuff in 'green'.

[usererror]

Wieman01,

I think I had the green code, but the WEP part you have posted I did not have. I'll try this today and post back, thank you for your assistance!

[wieman01]

No worries, I am glad you help us out as well. Would love to see this work as well because this would help a lot of other users as you can image (including me of course).

[iceman1234]

VERY good HOWTO. It worked the first time, after reading the very important rule about WPA-PSK :-)

Again, many thx.
cheers

[Lysi]

finally, I got it working as well. Thx 4 the HOWTO.

One thing bothers me still, because I haven't totally understood the process yet.

is /etc/wpa_supplicant/wpa_supplicant.conf necessary? it is used in other threads herein the forum. because everything is configured /etc/network/interfaces and it works without it.
and one more thing to add here. maybe it helps someone else.

if you have a password including bash special characters, e.g.
234$42er24r
then, a backslash in front of $ is necessary to remove its bash interpretation,

wpa_passphrase "NET1" "234\$42er24r"
network={
ssid="NET1"
#psk="234$42er24r"
psk=d95df02d0eece531d1d266ea4aa8c61691be8cc66ebde7 e2810df676b1439d97
}


it took me some time to realize that I always got the wrong network psk ](*,) ](*,)

[wieman01]

"/etc/wpa_supplicant/wpa_supplicant.conf" is not necessary if you make use of this approach.

As for the generation of the network key (PSK), it's a bit tricky if you use special characters, etc. Thanks for your post. I will update this thread in a short while and be a bit more specific in that respect. Thanks again.

[nakko]

Great howto, I got my wifi up in pretty much no time. I am not exaggerating when I say it probably took me about five minutes.

I do have a problem, however! Not merely when the machine boots, but seemingly every time a DHCP lease expires, it won't renew automatically. So, every forty-thousand seconds or so (10-12 hours, usually), I have to do a

sudo /etc/init.d/networking restart
All over again. So I cannot leave the computer running, leave the house and expect to necessarily be able to SSH back into it later, among other things. =/

Something I am missing, doing wrong? Any tips?

Edit: Here's my /etc/network/interfaces file, names have been changed to protect the innocent.

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto ath0
iface ath0 inet dhcp
wpa-driver madwifi
wpa-conf managed
wpa-ssid {*}
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk {*}
wireless-essid {*}
wireless-key {*}

[wieman01]

Great howto, I got my wifi up in pretty much no time. I am not exaggerating when I say it probably took me about five minutes.

I do have a problem, however! Not merely when the machine boots, but seemingly every time a DHCP lease expires, it won't renew automatically. So, every forty-thousand seconds or so (10-12 hours, usually), I have to do a

sudo /etc/init.d/networking restart
All over again. So I cannot leave the computer running, leave the house and expect to necessarily be able to SSH back into it later, among other things. =/

Something I am missing, doing wrong? Any tips?
I suspect this has rather to do with the settings of your physical network. Usually the router allows you to change certain settings such as the beacon interval, etc. I used to have a similar problem and cautiously changing some of the settings eventually did the trick for me (e.g. reducing beacon interval default value).

[nakko]

I suspect this has rather to do with the settings of your physical network. Usually the router allows you to change certain settings such as the beacon interval, etc. I used to have a similar problem and cautiously changing some of the settings eventually did the trick for me (e.g. reducing beacon interval default value).

I'm going to have to (politely!) disagree with you on that one, since the other desktops in the house & my laptop don't have this problem. And, since the router isn't mine, I cannot tinker with it.

[wieman01]

I'm going to have to (politely!) disagree with you on that one, since the other desktops in the house & my laptop don't have this problem. And, since the router isn't mine, I cannot tinker with it.
I experienced the problem only after installing Ubuntu. Windows used to be no problem at all. That's all I can say... Have you got "firestarter" or something like that by chance? Perhaps that's the issue. But if you do not have access to the router, then there is not much you can do I guess. I did some thorough stability testing and the only (but ugly) option that yielded good results was to mess around with the mentioned settings.

EDIT:
What card have you got?

[nakko]

What card have you got?

I'm using a D-Link DWL-G510, which comes in two revisions, but I happen to be using the one with the Atheros chipset, so I am using the madwifi drivers, and they do function perfectly (albeit only for however long). I haven't even looked into ndiswrapper.

[bleearg]

I personally am about ready to throw my Ubuntu laptop out the window. I have been utterly unsuccessful in keeping my wireless connection working. ](*,)

First of all, this guide is definitely helpful - it assisted me in getting my wireless working...initially. However, after a reboot, the wireless simply won't work. It won't associate with my AP. I'm using WPA2/CCMP, which is not at all complicated. My SSID is hidden, and I do have the 'wpa-ap-scan' set to '2'.

Output from the 'wpa_cli' simply states:


<2>Authentication with 00:00:00:00:00:00 timed out.
<2>Trying to associate with SSID 'blah'

Here is my 'interfaces' file:


auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid <ssid>
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk <secret_key>

Here is the output of 'iwconfig' and 'iwlist scan':


lo no wireless extensions.

eth0 no wireless extensions.

irda0 no wireless extensions.

eth1 IEEE 802.11g ESSID:"myssid"
Mode:Managed Frequency:2.412 GHz Access Point: 00:12:17:AA:7A:CC
Bit Rate:54 Mb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=86/100 Signal level=-44 dBm Noise level=-90 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:11 Missed beacon:0

sit0 no wireless extensions.

user@host:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

irda0 Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:12:17:AA:7A:CC
ESSID:"<hidden>"
Protocol:IEEE 802.11bg
Mode:Master
Channel:1
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=91/100 Signal level=-37 dBm
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
Extra: Last beacon: 268ms ago

sit0 Interface doesn't support scanning.

I'm on an IBM T43 laptop with an Intel 2200BG wireless adapter. What's the deal?

EDIT:
No less than two minutes after posting this, but after having done absolutely nothing to change anything, I did an 'ifdown eth1' and 'ifup eth1' and my wireless was suddenly associated. What would cause this behavior?

[wieman01]

Take a look at the second post (#2) of this thread. I am having the exact same problem with the Intel IPW2200. I have to restart the network during startup in order to get connected while the computer is booting. Try post #2 and see if it does the job for you. I am sure it will.

EDIT:
This is a bug by the way...

[bleearg]

Thanks for the response, weiman01, but that didn't work. At first, I thought it had something to do with whether or not 'eth0' was enabled in the /etc/network/interfaces file. However, last night, it stopped working altogether. When my 'iwlist scan' is run, it never sees my SSID.

[lo900]

My hat off to you, many thanks for this how to

it worked perfect for me (WPA2-psk)

on Toshiba-Tecra and on HP-dv5000

Thanks gain

Lo900

[squibT]

Thanks for the response, weiman01, but that didn't work. At first, I thought it had something to do with whether or not 'eth0' was enabled in the /etc/network/interfaces file. However, last night, it stopped working altogether. When my 'iwlist scan' is run, it never sees my SSID.

...... Extra: Last beacon: 268ms ago

This beacon interval should probably read 100 or 50 if modified because your are having connectivity problems. Not that your beacon interval is set at 268....it is just odd you lost your connection for a while..Let me ask this...

Is it you dont wish to mess with the router your ISP gave you or is it a shared router that a neighbor manages?

[giosetti]

I proceeded the way described in "Sample configuration mixed mode (WPA1, WPA2) & DHCP, ESSID broadcast" with this result:

giosetti@ubuntu:~$ sudo /etc/init.d/networking restart
* Reconfiguring network interfaces... Internet Systems Consortium DHCP Client V3.0.3
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

Listening on LPF/eth0/00:80:5a:24:c1:35
Sending on LPF/eth0/00:80:5a:24:c1:35
Sending on Socket/fallback
DHCPRELEASE on eth0 to 192.168.2.1 port 67
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - Internet Systems Consortium DHCP Client V3.0.3
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

Listening on LPF/rausb0/00:13:d4:09:29:9c
Sending on LPF/rausb0/00:13:d4:09:29:9c
Sending on Socket/fallback
DHCPDISCOVER on rausb0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on rausb0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on rausb0 to 255.255.255.255 port 67 interval 21
DHCPDISCOVER on rausb0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on rausb0 to 255.255.255.255 port 67 interval 12
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
Internet Systems Consortium DHCP Client V3.0.3
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

Listening on LPF/eth0/00:80:5a:24:c1:35
Sending on LPF/eth0/00:80:5a:24:c1:35
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
DHCPOFFER from 192.168.2.1
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 192.168.2.1
bound to 192.168.2.102 -- renewal in 133651 seconds.
[ ok ]
giosetti@ubuntu:~$

Complementary data:

giosetti@ubuntu:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

sit0 no wireless extensions.

rausb0 RT2500USB WLAN ESSID:""
Mode:Managed Frequency=2.412 GHz Bit Rate=11 Mb/s
RTS thr:off Fragment thr:off
Link Quality=0/70 Signal level:-120 dBm Noise level:-216 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

giosetti@ubuntu:~$

giosetti@ubuntu:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

sit0 Interface doesn't support scanning.

rausb0 Scan completed :
Cell 01 - Address: 00:12:BF:9B:B1:A7
Mode:Managed
ESSID:"mywlanessid"
Encryption key:on
Channel:1





Any idea what my problem might be? Thanx.

[bleearg]

...... Extra: Last beacon: 268ms ago
Is it you dont wish to mess with the router your ISP gave you or is it a shared router that a neighbor manages?

I have no qualms about editing the AP config myself, as it is mine. If you are saying I should edit the beacon interval, I'll go ahead and try that.

EDIT: I just realized that I think you are confusing my issue with another user, who didn't want to mess with his router's settings. However, I will check the beacon interval in the AP and see what it's set to.

[wieman01]

ioctl[SIOCSIWENCODEEXT]: Operation not supported
That's no good sign. I suspect that you are using the Linux driver for your Linksys card (Ralink), is that correct? I don't think Serialmonkey's driver for Ralink chipsets support WPA like other cards do. At least that's what the error message is about. You either try to install "ndiswrapper" and get your card working by using the native Windows driver, or you check on their website for support:

http://rt2x00.serialmonkey.com/wiki/index.php?title=Main_Page

I have a Linksys card myself (WUSB54G) and never got it to work with WPA, only after removing the Linux driver and installing "ndiswrapper"...

EDIT:
What wireless adapter are you using? Besides please try WPA1 (only) first and let me know if the error message keeps occurring...

[Gladier]

gladier@gladier-desktop:~$ uname -a
Linux gladier-desktop 2.6.17-10-generic #2 SMP Tue Dec 5 22:28:26 UTC 2006 i686 GNU/Linux
gladier@gladier-desktop:~$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:16:17:E8:70:4D
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Base address:0xbf00 Memory:fd8e0000-fd900000

eth1 Link encap:Ethernet HWaddr 00:16:17:E8:70:4E
inet addr:192.168.15.135 Bcast:192.168.15.255 Mask:255.255.255.0
inet6 addr: fe80::216:17ff:fee8:704e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1735 errors:0 dropped:0 overruns:0 frame:0
TX packets:1670 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:1300445 (1.2 MiB) TX bytes:260569 (254.4 KiB)
Base address:0xaf00 Memory:fdee0000-fdf00000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:100 (100.0 b) TX bytes:100 (100.0 b)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

wlan0 Link encap:Ethernet HWaddr 00:16:E3:21:D0:CF
inet6 addr: fe80::216:e3ff:fe21:d0cf/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:21 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:5082 (4.9 KiB)

gladier@gladier-desktop:~$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.15.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
0.0.0.0 192.168.15.1 0.0.0.0 UG 0 0 0 eth1
gladier@gladier-desktop:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

eth1 no wireless extensions.

wlan0 IEEE 802.11g ESSID:off/any
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Bit Rate:54 Mb/s Tx-Power:25 dBm
RTS thr:2347 B Fragment thr:2346 B
Power Management:off
Link Quality:100/100 Signal level:-10 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

sit0 no wireless extensions.

gladier@gladier-desktop:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:16:17:E8:70:4D
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Base address:0xbf00 Memory:fd8e0000-fd900000

eth1 Link encap:Ethernet HWaddr 00:16:17:E8:70:4E
inet addr:192.168.15.135 Bcast:192.168.15.255 Mask:255.255.255.0
inet6 addr: fe80::216:17ff:fee8:704e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1747 errors:0 dropped:0 overruns:0 frame:0
TX packets:1670 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:1301924 (1.2 MiB) TX bytes:260569 (254.4 KiB)
Base address:0xaf00 Memory:fdee0000-fdf00000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:100 (100.0 b) TX bytes:100 (100.0 b)

wlan0 Link encap:Ethernet HWaddr 00:16:E3:21:D0:CF
inet6 addr: fe80::216:e3ff:fe21:d0cf/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:5766 (5.6 KiB)

gladier@gladier-desktop:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:0F:B5:3E:46:4A
ESSID:"VANHOUTEN"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:35/100 Signal level:-73 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 02 - Address: 00:14:BF:EC:D0:E0
ESSID:"MuWaPa"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.457 GHz (Channel 10)
Quality:46/100 Signal level:-66 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK

sit0 Interface doesn't support scanning.

gladier@gladier-desktop:~$ cat /etc/network/interfaces
auto lo
iface lo inet loopback


iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp

auto eth2
iface eth2 inet dhcp

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid MuWaPa
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 8271c094cb6412345asfg97bfb0d45054asdfa231175d8 [changed for posting]

auto eth0
gladier@gladier-desktop:~$ cat /etc/modprobe.d/ndiswrapper
install usb:v0B05p1717d*dc*dsc*dp*ic*isc*ip* /sbin/modprobe ndiswrapper
gladier@gladier-desktop:~$ cat /etc/resolv.conf
search ctrl-esc.local
nameserver 192.168.15.254
nameserver 192.168.15.1


hopefully thats enough...

i can see my network(MuWaPa) - however i cant connect to it. running hidden SSID WPA no mac filtering etc.

and i know my local connection is still plugged in - but that shouldnt make a difference.

Regards,
Gladier

[wieman01]

If your Ethernet cable is plugged in, you won't be able to connect to your wireless network. It does make a difference.

Second, "iwlist scan" says that your network is using TKIP which happens to be WPA1 (ESSID:"MuWaPa"):

IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Either change to WPA2 or use the sample script for WPA1 instead:

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid MuWaPa
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk 8271c094cb6412345asfg97bfb0d45054asdfa231175d8 [changed for posting]

[t_anjan]

I've followed the HOW-TO exactly.
I've got a Netgear WG111v2 USB dongle that I have installed using NDISWRAPPER.

'iwlist scan' shows me the available network:


anjan@supernal:~$ iwlist wlan0 scan
wlan0 Scan completed :
Cell 01 - Address: 00:14:6C:F0:03:06
ESSID:"AnjanWireless"
Protocol:IEEE 802.11bg
Mode:Master
Channel:11
Encryption key:on
Bit Rates:54 Mb/s
Extra: Rates (Mb/s): 1 2 5.5 6 9 11 12 18 22 24 36 48 54
Quality:17 Signal level:0 Noise level:2
Extra: Last beacon: 0ms ago

Output of 'iwconfig'

anjan@supernal:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 802.11b/g link.. ESSID:"AnjanWireless"
Mode:Managed Channel=11 Access Point: Not-Associated
Bit Rate=11 Mb/s
Retry:on Fragment thr:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

sit0 no wireless extensions.

Contents of my 'interfaces' file:


auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp

auto eth2
iface eth2 inet dhcp

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp
wireless-essid AnjanWireless
wpa-driver wext
wpa-conf master
wpa-ssid AnjanWireless
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <hidden>


First, before reading this How-To, I had my 'interfaces' file without all the wpa config commands. Instead I had these two lines:


pre-up wpa_supplicant -Bw -Dwext -ieth0 -c/etc/wpa_supplicant.conf
post-down killall -q wpa_supplicant

Contents of my 'wpa_supplicant.conf' file:


# Minimal /etc/wpa_supplicant.conf to associate with open
# access points. Please see
# /usr/share/doc/wpasupplicant/wpa_supplicant.conf.gz for more complete
# configuration parameters.

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0

eapol_version=1
ap_scan=2
fast_reauth=1

network={
ssid="AnjanWireless"
scan_ssid=1
key_mgmt=WPA-PSK
proto=WPA
#pairwise=CCMP TKIP
#group=CCMP TKIP
#psk="<hidden>"
psk=<hidden>
}

Everything seems OK to me. But I just cannot hook up to my wireless router, even after disabling my wired connection (eth0) and disconnecting my ethernet cable.

Please, I've spent three days on this now and Ubuntu is really starting to frustrate me. Someone help!

[wieman01]

t_anjan:

What are your router's security settings? It looks to me as if it is set to WEP. Could you check? If it is set to WPA, is it WPA with TKIP (WPA1) or AES (WPA2)? Is broadcasting of ESSID enabled or hidden?

[t_anjan]

t_anjan:

What are your router's security settings? It looks to me as if it is set to WEP. Could you check? If it is set to WPA, is it WPA with TKIP (WPA1) or AES (WPA2)? Is broadcasting of ESSID enabled or hidden?

No, my router is set to WPA-PSK, with TKIP. I know this is correct, because I connect to the same router from my windows laptop. SSID broadcasting is ON.

[wieman01]

No, my router is set to WPA-PSK, with TKIP. I know this is correct, because I connect to the same router from my windows laptop. SSID broadcasting is ON.
Have you got Firestarter, NetworkManager, or Wifi-Radar running? If so, uninstall them for the time being... Please also post the output when you restart the network:


sudo ifdown -v wlan0

sudo ifup -v wlan0

[t_anjan]

I don't have any of Firestarter, Network Manager or WiFi-Radar installed.

The output of sudo ifdown -v wlan0


Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 5068
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:18:4d:08:c7:0e
Sending on LPF/wlan0/00:18:4d:08:c7:0e
Sending on Socket/fallback
ifconfig wlan0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan0.pid
Stopped /sbin/wpa_supplicant (pid 3738).

The output of sudo ifup -v wlan0


Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...


ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan0
wpa_supplicant: wpa-ap-scan 1 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "AnjanWireless" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise TKIP -- OK
wpa_supplicant: wpa-group TKIP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto WPA -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 5798864
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:18:4d:08:c7:0e
Sending on LPF/wlan0/00:18:4d:08:c7:0e
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 2
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntp-server
run-parts: executing /etc/network/if-up.d/ntpdate
Synchronizing clock to ntp.ubuntu.com...

Thanks for taking the time to help out.

[giosetti]

That's no good sign. I suspect that you are using the Linux driver for your Linksys card (Ralink), is that correct?

Yes, it is the driver that comes out of the box.


What wireless adapter are you using?

It is the ASUS WL-167g.


I don't think Serialmonkey's driver for Ralink chipsets support WPA like other cards do.

But that's what they say - for WPA2 at least: http://rt2x00.serialmonkey.com/phpBB2/viewtopic.php?t=1822&highlight=wpa2


Besides please try WPA1 (only) first and let me know if the error message keeps occurring...

It does:


giosetti@ubuntu:/etc/network$ sudo /etc/init.d/networking restart
Listening on LPF/eth0/00:80:5a:24:c1:35
Sending on LPF/eth0/00:80:5a:24:c1:35
Sending on Socket/fallback
DHCPRELEASE on eth0 to 192.168.2.1 port 67
ioctl[SIOCSIWPMKSA]: Network is down
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - Internet Systems Consortium DHCP Client V3.0.3
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

Listening on LPF/rausb0/00:13:d4:09:29:9c
Sending on LPF/rausb0/00:13:d4:09:29:9c
Sending on Socket/fallback
DHCPDISCOVER on rausb0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on rausb0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on rausb0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on rausb0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on rausb0 to 255.255.255.255 port 67 interval 17
No DHCPOFFERS received.



Here the /etc/network/interfaces:


# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface

auto rausb0
iface rausb0 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid WLAN-9BB139
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk SP-3091A7330


iface eth0 inet dhcp


Should I try any other WPA driver such as hostap? Or should I try to run ndiswrapper straight away? I need to see how that works. Do I need a certain windows driver in that case? And how do eliminate the linux driver? There are how-tos I guess, I'll look around. Is there BTW any conflict with the applications|system|networking menue?

Thx.

[giosetti]

You either try to install "ndiswrapper"

I was just reading the avialable ndiswrapper howtos, went to the Asus site to retrieve a suitable driver, when I realized that they indicated "USB2.0 adapter".

But AFAIK the Dell Latitude CPi operates USB1.0:



giosetti@ubuntu:~$ lspci
0000:00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03)
0000:00:01.0 PCI bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03)
0000:00:03.0 CardBus bridge: Texas Instruments PCI1225 (rev 01)
0000:00:03.1 CardBus bridge: Texas Instruments PCI1225 (rev 01)
0000:00:07.0 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 02)
0000:00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
0000:00:07.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01)
0000:00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02)
0000:01:00.0 VGA compatible controller: Neomagic Corporation NM2200 [MagicGraph 256AV] (rev 12)
0000:01:00.1 Multimedia audio controller: Neomagic Corporation NM2200 [MagicMedia 256AV Audio] (rev 12)
0000:02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)

However iwconfig gives the RA2500:


giosetti@ubuntu:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

sit0 no wireless extensions.

rausb0 RT2500USB WLAN ESSID:""
Mode:Managed Frequency=2.412 GHz Bit Rate=11 Mb/s
RTS thr:off Fragment thr:off
Link Quality=0/70 Signal level:-120 dBm Noise level:-202 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

Now - is this a/the problem? And what could be done? Better buy a PCMCIA card (which would be more useful anyway, because I need the (only) USB slot for saving files (the notebook has no CDWR). And which one could that be?

[wieman01]

First of all, the error message suggests that the driver does not support WPA the way we are trying to set it up. That's definitely a no-go. I suggest that you either check out their website for suitable support or give "ndiswrapper" a go. This is a good start:

https://help.ubuntu.com/community/WifiDocs/Driver/Ndiswrapper

Before you do so, you could also try other wpa-drivers, however, I believe "wext" is the right one.

[t_anjan]

First of all, the error message suggests that the driver does not support WPA the way we are trying to set it up. That's definitely a no-go. I suggest that you either check out their website for suitable support or give "ndiswrapper" a go. This is a good start:

https://help.ubuntu.com/community/WifiDocs/Driver/Ndiswrapper

Before you do so, you could also try other wpa-drivers, however, I believe "wext" is the right one.

If this message was directed at me, I'm already using ndiswrapper. Any other suggestions?

[giosetti]

First of all, the error message suggests that the driver does not support WPA the way we are trying to set it up. That's definitely a no-go. I suggest that you either check out their website for suitable support or give "ndiswrapper" a go. This is a good start:

https://help.ubuntu.com/community/WifiDocs/Driver/Ndiswrapper



Does my Dell notebook supporting USB1.0 where the Asus WL-167G is based on USB2.0 affect the whole process substantially?

As I wrote previously lspci doesn't identify the USB dongle. On the other hand iwconfig comes up with indication "RT2005".

So does it makes sense to go this way?

[wieman01]

If this message was directed at me, I'm already using ndiswrapper. Any other suggestions?
So you can connect to unsecured networks? Have you tried the latest version of the driver for your card? Perhaps the current one does not support WPA. wpa-driver "wext" is definitely the right one if you are using "ndiswrapper".

EDIT:
Hang on, there is a problem with your script:

auto wlan0
iface wlan0 inet dhcp
wpa-ssid AnjanWireless
wpa-driver wext
wpa-conf master
wpa-ssid AnjanWireless
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <hidden>
Your script says "wireless-essid" which is incorrect if you use WPA.

[wieman01]

Does my Dell notebook supporting USB1.0 where the Asus WL-167G is based on USB2.0 affect the whole process substantially?

As I wrote previously lspci doesn't identify the USB dongle. On the other hand iwconfig comes up with indication "RT2005".

So does it makes sense to go this way?
Let's put the question this way: Can you or can you not connect to unsecured networks using your dongle?

[t_anjan]

So you can connect to unsecured networks? Have you tried the latest version of the driver for your card? Perhaps the current one does not support WPA. wpa-driver "wext" is definitely the right one if you are using "ndiswrapper".

I'm using AMD64 version of Edgy and have used the 64 bit RT8187 driver (available on the Realtek Site) in ndiswrapper. I'm using the same driver on Win x64 where WPA works. So the driver definitely supports WPA. But WPA is not the problem here. I can't connect to even unsecure networks.



EDIT:
Hang on, there is a problem with your script:

Your script says "wireless-essid" which is incorrect if you use WPA.

I actually have the "wpa-ssid" command 3 lines below. The "wireless-essid" command is added by the "System->Administration->Networking" automatically. I removed the line manually. But it doesn't make a difference.

[Catsworth]

I don't know what to say other than:

"Thank You So Very Much!"

I followed your steps through one at a time, restarted the network and held my breath. Everything connected first time and I'm now wireless with WPA enabled.

I really cannot thank you enough for posting this.

[t_anjan]

So you can connect to unsecured networks?

To heck with WPA. I've temporarily disabled all security on my router. I want Edgy to connect to my unsecured router.

My "interfaces" file:

auto lo
iface lo inet loopback

#auto eth0
#iface eth0 inet dhcp

#auto eth1
#iface eth1 inet dhcp

#auto eth2
#iface eth2 inet dhcp

#auto ath0
#iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp
wireless-essid AnjanWireless
wireless-channel 2
wireless-mode managed

Output of sudo /etc/init.d/networking restart


anjan@supernal:~$ sudo /etc/init.d/networking restart
* Reconfiguring network interfaces... There is already a pid file /var/run/dhclient.wlan0.pid with pid 8963
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:18:4d:08:c7:0e
Sending on LPF/wlan0/00:18:4d:08:c7:0e
Sending on Socket/fallback
Error for wireless request "Set Frequency" (8B04) :
SET failed on device wlan0 ; Operation not supported.
There is already a pid file /var/run/dhclient.wlan0.pid with pid 5798864
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:18:4d:08:c7:0e
Sending on LPF/wlan0/00:18:4d:08:c7:0e
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

I think these two lines are the most important:

Error for wireless request "Set Frequency" (8B04) :
SET failed on device wlan0 ; Operation not supported.

I have no idea why SET is not working. Any ideas? I can't even connect to an unsecured network!!!

[wieman01]

I think these two lines are the most important:

Error for wireless request "Set Frequency" (8B04) :
SET failed on device wlan0 ; Operation not supported.

I have no idea why SET is not working. Any ideas? I can't even connect to an unsecured network!!!
I cannot tell for sure what's going on but perhaps open another thread for your problem as it seems to relate to your driver rather than WPA security.

Just a last thought: Check that both router and wireless adapter are running on either wireless B or G. Put them in sync.

[Catsworth]

I don't know what to say other than:

"Thank You So Very Much!"

I followed your steps through one at a time, restarted the network and held my breath. Everything connected first time and I'm now wireless with WPA enabled.

I really cannot thank you enough for posting this.

With just one minor problem.....

I have to open a terminal and type:


/etc/init.d/networking restart

every time I start Ubuntu, otherwise my wireless connection doesn't work. Anybody got any ideas why this might be?

Thanks.

[wieman01]

With just one minor problem.....

I have to open a terminal and type:


/etc/init.d/networking restart

every time I start Ubuntu, otherwise my wireless connection doesn't work. Anybody got any ideas why this might be?

Thanks.
I was expecting that. :-) Please read post #2 of this thread. It's a bug so you have to restart the network while the computer is booting.

[Catsworth]

I was expecting that. :-) Please read post #2 of this thread. It's a bug so you have to restart the network while the computer is booting.

Tee Hee :)

That'll teach me to read a bit further next time even if I think everything's working fine :)

Thanks, I'll reboot now and see how it goes.....

[Catsworth]

Ok, that didn't work - I still had to restart the network after I'd logged in.

Any ideas why that might be?

There was a note in post 2 regarding possibly having to change the S40 value.....could that be it?

I've seen that other people are having this problem but the solutions posted didn't make any sense, and I'm having a brain-hurting time as it is without making matters worse. Could you let me know which of the many posts concerning this has the right instructions to follow?

Thanks.

[wieman01]

Ok, that didn't work - I still had to restart the network after I'd logged in.

Any ideas why that might be?

There was a note in post 2 regarding possibly having to change the S40 value.....could that be it?

I've seen that other people are having this problem but the solutions posted didn't make any sense, and I'm having a brain-hurting time as it is without making matters worse. Could you let me know which of the many posts concerning this has the right instructions to follow?
I am afraid I don't know any other solution... Changing the S40 value may be worth a try but I doubt this will solve your problem. Sorry I cannot be of any help here. But a solution would be appreciate if you came across one.

[palomuuri]

Maybe my eyes are blurring, but the instructions on how to use wpa_passphrase show an example where the hexadecimal output appears to be two strings. I get a single string:

$ wpa_passphrase '<my ESSID>' '<my passphrase>'
network={
ssid="my ESSID"
#psk="my password"
psk=47965933a8937a4a9443bb0ff6e04d7b06ad10731d361c ddbf9f92bf97e30e21
}

The example at the beginning of this thread shows
psk=fe727aa8b64ac9b3f54c72432da14faed933ea511ecab1 5bbc6c52e7522f709a

Which is correct? I tend to believe the output of wpa_passphrase.

Best regards,

[Catsworth]

Sorry I cannot be of any help here. But a solution would be appreciate if you came across one.

I think it's something to do with getting the network to restart automatically at boot, which your post #2 was trying to do, for some reason it just doesn't work on my machine and I have to do it manually:(

[Catsworth]

Ok, in your post #2 you wrote:


sudo ln -s /etc/init.d/wireless-network.sh /etc/rcS.d/S40wireless-network

I think I *might* have put rc5 instead of rcS (a five instead of the required 'S'". Is there anyway that I can check this, or better still just delete the symbolic link so that I can redo it?

Thanks.

[Pollywoggy]

I used the info in this thread to set up my router for WPA, which I had already done, but now I have a static IP address. My router software, DD-WRT, can only use TKIP and AES and I have a question.

Are all WPA2 variants capable of ESSID; of hiding the SSID?


Until I read the info here, I had not set up my router to map MAC addresses to static IP addresses, I had to play with this since I had not done it before, but it works now.
My router does WPA2 but only with AES and/or TKIP.

[Pollywoggy]

Initially I had voted that this thread was "somewhat helpful" but if I could change my vote I would say that it has been very helpful.

[wieman01]

Ok, in your post #2 you wrote:


sudo ln -s /etc/init.d/wireless-network.sh /etc/rcS.d/S40wireless-network

I think I *might* have put rc5 instead of rcS (a five instead of the required 'S'". Is there anyway that I can check this, or better still just delete the symbolic link so that I can redo it?

Thanks.
Yes, you can check by typing this:

ls -l /etc/rc5.d/S40wireless-network
If this command returns your link, then you have previously created it. Nonetheless, it does not harm redoing it & creating the right symblink.

[wieman01]

Are all WPA2 variants capable of ESSID; of hiding the SSID?
Basically yes. "wpa-ap-scan" controls this part of your security settings. Check it out if you have not done so already.

[katu]

ok. I made a large post here:
problems with WPa... (http://http://ubuntuforums.org/showthread.php?t=340552)

but was directed here. Now my interfaces looks like this:

auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0

#auto eth0
#iface eth0 inet static
#address 172.16.11.87
#netmask 255.255.0.0
#gateway 172.16.1.1

auto eth1
iface eth1 inet dhcp

wpa-driver wext
wpa-conf managed
wpa-ssid WAiRPort
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 256db0e3d42e7d5e879d933bcc91cee41c275be013c47dc75a aaacac287f36c3



and I tried running /etc/init.d networking restart
and the firs time I actually got an IP, but the net didn't go through. So I tried to shut down eth0 (which I had not yet done at the time), made a mistake and shutdown eth1 instead :(.
Any subsequent attempts to try run it didn't work. I also tried restarting the comp, with the above interfaces file. The result is:

* Deconfiguring network interfaces... Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:90:4b:9a:0e:d6
Sending on LPF/eth1/00:90:4b:9a:0e:d6
Sending on Socket/fallback
DHCPRELEASE on eth1 to 10.0.1.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
[ ok ]
root@warpik:/home/andrzej# /etc/init.d/networking start
* Configuring network interfaces... There is already a pid file /var/run/dhclient.eth1.pid with pid 5798864
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:90:4b:9a:0e:d6
Sending on LPF/eth1/00:90:4b:9a:0e:d6
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 21
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 2
No DHCPOFFERS received.
No working leases in persistent database - sleeping.



the highlight is mine. The address it sees is right. Of what I know the router gives adresses like 10.0.1.1 .
I think the send_packet thing may be a problem, but I don't know. I also tried moving the file mentioned
/var/run/dhclient.eth1.pid to a different location - no difference and I think the number stays the same as well... ;/

[wieman01]

wpa-ap-scan 2
Is the ESSID hidden? If not, this line needs to be:

wpa-ap-scan 1
Can you connect to unsecured networks? Please do a...

iwlist scan
... while you are near the network in questions & post the results.

Please try this script as well:

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid WAiRPort
wpa-ap-scan 1
wpa-proto RSN WPA
wpa-pairwise CCMP TKIP
wpa-group CCMP TKIP
wpa-key-mgmt WPA-PSK
wpa-psk 256db0e3d42e7d5e879d933bcc91cee41c275be013c47dc75a aaacac287f36c3
That should do!

[giosetti]

Let's put the question this way: Can you or can you not connect to unsecured networks using your dongle?

It seems I cannot. I have deactivated encryption, booted the notebook, checked system|networking where the interface rausb0 is identified. When I try to activate it, the computer freezes.

So I quit system|networking and sudo /etc/init.d/networking restart and again the computer freezes at:



*Reconfiguring network interfaces...

Listening on LPF/rausb0/00:13:d4:09:29:9c
Sending on LPF/rausb0/00:13:d4:09:29:9c
Sending on Socket/Fallback
DHCPRELEASE on rausb to 192.168.2.1 port 67
Internet Systems Consortium Client V3.0.3

Listening on LPF/rausb0/00:13:d4:09:29:9c
Sending on LPF/rausb0/00:13:d4:09:29:9c
Sending on Socket/Fallback


What bothers me is that I don't know if it is ok that system|networking is running. I thought I've read it should not be running, but I may have messed that with Network-manager, which is not installed on that computer.

The other thing that I find strange is that the computer often freezes while booting. At some point I booted with the options "acpi=off" with no problems, at another point "noapm" did the trick. Now it seems that the computer freezes while booting when the dongle is attached while the machine boots correctly when the dongle is not attached. I'm not sure if I can nail things down like this because I lack the time to reboot systematically to exactly find the problem, but the dongle seems to cause the trouble. A memory stick BTW causes no problems.

So I'd rather think there is a hardware problem at hand.

[katu]

Is the ESSID hidden? If not, this line needs to be:

Can you connect to unsecured networks? Please do a...

... while you are near the network in questions & post the results.

Please try this script as well:

That should do!

I hate to say this, but it didn't work ;/.

I used ap-scan 2, because the admin hid the essid again. I tried also with wpa-ap-scan 1, but the result is pretty much the same:


* Reconfiguring network interfaces...
There is already a pid file /var/run/dhclient.eth1.pid with pid 4966
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:90:4b:9a:0e:d6
Sending on LPF/eth1/00:90:4b:9a:0e:d6
Sending on Socket/fallback
DHCPRELEASE on eth1 to 10.0.1.1 port 67
There is already a pid file /var/run/dhclient.eth1.pid with pid 5798864
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:90:4b:9a:0e:d6
Sending on LPF/eth1/00:90:4b:9a:0e:d6
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 17
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 19
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 3
No DHCPOFFERS received.
No working leases in persistent database - sleeping.


I hihglihted the 2 pid lines again. the firs one seem right, as far as the number. the second one is crazy though. And the same as yesterday...

also iwlist scan gives:



lo Interface doesn't support scanning.

eth1 No scan results
eth0 Interface doesn't support scanning.

sit0 Interface doesn't support scanning.




But as I mentioned earlier, I was able to connect to unsecured networkss with this card. So I think it's either something wrong with what I'm doing here with the WPA or something weird with the wireless hub (apple).

Cheers and I really appreciate the help,

[wieman01]

But as I mentioned earlier, I was able to connect to unsecured networkss with this card. So I think it's either something wrong with what I'm doing here with the WPA or something weird with the wireless hub (apple).

Cheers and I really appreciate the help,
Question: Have you got any other wireless tool e.g. network-manager, wifi-radar installed? It looks to me as if something is interfering. If so, please uninstall them.

PLUS: Make sure the Ethernet cable is pulled while you are trying to connect through wireless.

[katu]

I don't have wi-fi radar and I shut down knetworkmanager as specified in the howto. a couple of searches with ps aux revelaed that there was indeed a NetworkManager and NetworkManagerDispatcher running. I killed those and apparently the connection is still not there, but the error messages are different:


* Reconfiguring network interfaces... Ignoring unknown interface eth0=eth0.
wpa_supplicant: unknown or stale ctrl_interface socket located at /var/run/wpa_supplicant/eth1...aborting!
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1
There is already a pid file /var/run/dhclient.eth1.pid with pid 5798864
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:90:4b:9a:0e:d6
Sending on LPF/eth1/00:90:4b:9a:0e:d6
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 13
No DHCPOFFERS received.
No working leases in persistent database - sleeping.


maybe the highilighted part will shed some light on the subject?
Once again thanks a lot for all your time.

[wieman01]

Katu:

Could you post your entire "/etc/network/interfaces" once again, please, and also do a "iwlist scan" and post the results?

Uninstalling "network-manager" would be best... And is DHCP enabled?

[Mujaheiden]

Hi, concerning your 2nd post - anyway, thanks for this extremely useful post :KS - now if I startup, It gives some lines saying

DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 2
but before it already stated that it obtained a lease or smt for a lot of seconds. So then I just press CTRL-C. Should I wait a bit more, or is something stil misconfigured?

And another question, how abour roaming? If this laptop is going to go places, is it only able to work with the current setup, or, well, how does it go, if I cant use eg. wifi radar?

[wieman01]

Hi, concerning your 2nd post - anyway, thanks for this extremely useful post :KS - now if I startup, It gives some lines saying

but before it already stated that it obtained a lease or smt for a lot of seconds. So then I just press CTRL-C. Should I wait a bit more, or is something stil misconfigured?

And another question, how abour roaming? If this laptop is going to go places, is it only able to work with the current setup, or, well, how does it go, if I cant use eg. wifi radar?
Perhaps you don't require the solution described in post #2. Please try without it. If your computer is online after rebooting, you don't need to do a restart at all. Simply ignore post #2 in that case.

As for roaming, no, that's not possible. You would have to use tools like wifi-radar or network-manager instead. Unless you want to mess around with text files/command line all the time (which I prefer).

[katu]

Katu:

Could you post your entire "/etc/network/interfaces" once again, please, and also do a "iwlist scan" and post the results?

Uninstalling "network-manager" would be best... And is DHCP enabled?

Yeah, dhcp is enabled. Or at least the client is there, that is what's trying to get the lease, if I understood your question right.

ok. interfaces in all it's glory:


auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0

#auto eth0
#iface eth0 inet static
#address 172.16.11.87
#netmask 255.255.0.0
#gateway 172.16.1.1

auto eth1
iface eth1 inet dhcp

wpa-driver wext
wpa-conf managed
wpa-ssid WAiRPort
wpa-ap-scan 1
wpa-proto RSN WPA
wpa-pairwise CCMP TKIP
wpa-group CCMP TKIP
wpa-key-mgmt WPA-PSK
wpa-psk 256db0e3d42e7d5e879d933bcc91cee41c275be013c47dc75a aaacac287f36c3

iwlist scan is a bit funny. firs when I tried it it gave:


lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 No scan results
sit0 Interface doesn't support scanning.

I got the admin to broadcast the essid and then I got:



eth1 Scan completed :
Cell 01 - Address: 00:0D:88:8C:89:62
ESSID:"daqborex"
Protocol:IEEE 802.11bg
Mode:Master
Channel:6
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 22 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Quality=100/100 Signal level=-74 dBm
Extra: Last beacon: 344ms ago
Cell 02 - Address: 00:0A:95:F5:69:37
ESSID:"WAiRPort"
Protocol:IEEE 802.11bg
Mode:Master
Channel:13
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=100/100 Signal level=-46 dBm
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
Extra: Last beacon: 52ms ago



the crazy part is that the first network daqborex is not ours, but didn;t show up before... Anyway I tried reconnecting (changed wpa-ap-scan to 1) and it still didn;t connect, but the end of dmesg is pretty interesting:



10232.731916] ADDRCONF(NETDEV_UP): eth1: link is not ready
[10413.238194] SoftMAC: Open Authentication completed with 00:0a:95:f5:69:37
[10413.248929] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[10423.362897] eth1: no IPv6 routers present
[10435.638362] SoftMAC: Open Authentication completed with 00:0a:95:f5:69:37
[10459.030061] SoftMAC: Open Authentication completed with 00:0a:95:f5:69:37
[10482.419793] SoftMAC: Open Authentication completed with 00:0a:95:f5:69:37
[10498.024806] SoftMAC: Received deauthentication packet from 00:13:02:3f:74:d8, but that network is unknown.
[10498.025934] SoftMAC: Received deauthentication packet from 00:13:02:3f:74:d8, but that network is unknown.
[10498.026780] SoftMAC: Received deauthentication packet from 00:13:02:3f:74:d8, but that network is unknown.
[10498.028430] SoftMAC: Received deauthentication packet from 00:13:02:3f:74:d8, but that network is unknown.
[10498.032557] SoftMAC: Received deauthentication packet from 00:13:02:3f:74:d8, but that network is unknown.
[10498.046790] SoftMAC: Received deauthentication packet from 00:13:02:3f:74:d8, but that network is unknown.
[10498.051162] SoftMAC: Received deauthentication packet from 00:13:02:3f:74:d8, but that network is unknown.
[10498.071699] SoftMAC: Received deauthentication packet from 00:13:02:3f:74:d8, but that network is unknown.
[10498.083476] SoftMAC: Received deauthentication packet from 00:13:02:3f:74:d8, but that network is unknown.
[10498.088160] SoftMAC: Received deauthentication packet from 00:13:02:3f:74:d8, but that network is unknown.
[10748.381445] ADDRCONF(NETDEV_UP): eth1: link is not ready



the other MAC is from the laptop of another guy in the room...
(oh yeah - I deinstalled network-manager. knetworkmanager went as well. I also threw out wlassitant for good measure.)
Thanks,

[katu]

Another thing I noticed. When I execute iwconfig the result is:


eth1 IEEE 802.11b/g ESSID:"WAiRPort" Nickname:"Broadcom 4306"
Mode:Managed Frequency=2.472 GHz Access Point: 00:0A:95:F5:69:37
Bit Rate=1 Mb/s Tx-Power=15 dBm
RTS thr:off Fragment thr:off
Encryption key:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


My question is. should the encryption key be off? Maybe I'm making a mistake there?

[wieman01]

My question is. should the encryption key be off? Maybe I'm making a mistake there?
"iwconfig" is irrelevant at this stage... Another question: Can you connect to unsecured networks for sure? We should start from there... If you can't, we need to fix your card first.

[lukemack]

Hi,

I'm having trouble getting WPA set up with my broadcom 4306 card. I'm running 6.10-server on i386 (dell dimension 4500)

i'm trying to connect to a netgear DG834GT. I can connect fine without the encryption and am using bcmwl5.inf with ndiswrapper.

i've attached the output from wpa_supplicant, iwlist scan and the contents of my wpa_supplicant.conf file.

can anyone help?

many thanks,

lukemack.

[wieman01]

Hi,

I'm having trouble getting WPA set up with my broadcom 4306 card. I'm running 6.10-server on i386 (dell dimension 4500)

i'm trying to connect to a netgear DG834GT. I can connect fine without the encryption and am using bcmwl5.inf with ndiswrapper.

i've attached the output from wpa_supplicant, iwlist scan and the contents of my wpa_supplicant.conf file.

can anyone help?
Hi Luke,

This thread uses a different approach to wireless security. Please read the HOWTO first. I won't be able to help you with this one...

[lukemack]

thanks. i;ve switched to using the interfaces file but get an error when trying to restart the network:

* Reconfiguring network interfaces... /etc/network/interfaces:14: option with empty value
ifdown: couldn't read interfaces file "/etc/network/interfaces"
/etc/network/interfaces:14: option with empty value
ifup: couldn't read interfaces file "/etc/network/interfaces"

any idea what might be causing this?

contents of /etc/interfaces:


# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid="OLDSCHOOLHOUSE"
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
psk=696251dd95c4238af640bb6b3a78e615372d0771e31axx xxxxxxxxxxxxxxxxx

i think its complaining about line 14 which is the ssid - i;ve tried this with and without quotes

[wieman01]

Try this instead (simply copy and paste):

auto lo
iface lo inet loopback

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid OLDSCHOOLHOUSE
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk 696251dd95c4238af640bb6b3a78e615372d0771e31axxxxxx xxxxxxxxxxxxx
Have you generated the key as suggested in the first post?

[lukemack]

thanks - i get a bit further with that (the network tries to restart) but get the attached output (i dont receive a DHCP lease). The subnet mask looks wrong to me. anything I can do about that?

Also, do i still need to make changes in the networking gui to get this working?

thanks,

lukemack.

[wieman01]

Looks much better now... Have you got network-manager or wifi-radar installed? Please remove it before you go ahead.

This error message does not look right:

/var/run/dhclient.eth1.pid with pid 134993416
Perhaps restart the computer after uninstalling the mentioned tools.

[lukemack]

i dont have those installed no. i did want to install network manager but add/remove programs says it is not supported on i386?

a reboot hasnt helped unfortunately. would you expect these lines?

DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 18

when eth0 is connected (ethernet cable), ifconfig shows:

eth0 Link encap:Ethernet HWaddr 00:07:E9:00:7C:F2
inet addr:192.168.0.5 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::207:e9ff:fe00:7cf2/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3699 errors:0 dropped:0 overruns:0 frame:0
TX packets:3415 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3585950 (3.4 MiB) TX bytes:547529 (534.6 KiB)

so isnt it trying to discover something at the wrong address?

[wieman01]

Pull the Ethernet cable while you are trying to connect through wireless. You cannot run both in Linux... Please try again with the cable unplugged.

[lukemack]

i tried that - same thing. the ethernet cable is always unplugged when i am trying to connect via the wireless card. i also tried disabling the wired interface in administration->networking, various reboots and nothing works. i still get:

DHCPRELEASE on eth1 to 192.168.0.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
There is already a pid file /var/run/dhclient.eth1.pid with pid 134993416

i have tried deleting the file it is complaining about but it just gets recreated when i run networking restart.

[wieman01]

i tried that - same thing. the ethernet cable is always unplugged when i am trying to connect via the wireless card. i also tried disabling the wired interface in administration->networking, various reboots and nothing works. i still get:

DHCPRELEASE on eth1 to 192.168.0.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
There is already a pid file /var/run/dhclient.eth1.pid with pid 134993416

i have tried deleting the file it is complaining about but it just gets recreated when i run networking restart.
But you can connect to unsecured / WEP secured networks no problem, right?

[lukemack]

yes

[wieman01]

yes
I am afraid I cannot help you there then. I have seen this problem before but not sure what the solution is. But perhaps try using other "wpa-drivers" as explained in the HOWTO. Sorry I cannot advice more.

[flatfish]

Thank you for this incredibly useful HOWTO. I am a complete novice, but I've been able to connect to my network (with WPA !!) by following your instructions. One problem: I cannot get the network to restart during boot (Post #2). In order to connect, I must use the following after I log in:

sudo wpa_supplicant -D madwifi -i ath0 -c /etc/wpa_supplicant.conf -w -dd
sudo dhclient ath0


Here are the relevant files (I think)
/etc/wpa_supplicant.conf

ctrl_interface=/var/run/wpa_supplicant
network={
ssid="Planet Express"
scan_ssid=1
proto=WPA
pairwise=TKIP
key_mgmt=WPA-PSK
psk=*key*
}


/etc/network/interfaces

auto lo
iface lo inet loopback

auto ath0
iface ath0 inet dhcp
wpa-driver madwifi
wpa-conf managed
wpa-ssid Planet Express
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk *key*
}

I'm using Edgy, there are no other network applications installed (network manager, wifi radar, etc.), and there is no ethernet cable plugged in. Any Idea what I'm doing wrong?

[wieman01]

Flatfish:

First off, please make sure your "/etc/network/interfaces" file has no "}", that will confuse wpa_supplicant.

Second, you don't need "sudo wpa_supplicant -D madwifi -i ath0 -c /etc/wpa_supplicant.conf -w -dd" if your script is fine... So I suspect you have misconfigured something. Please consider the following:

1. Your router's ESSID is not hidden as suggested by this line:

wpa-ap-scan 1
2. You follow the steps outlined in the HOWTO when generating your WPA key, that's crucial:

wpa-psk
3. After updating the script, please restart the network & post the output if you cannot connect (yet):

sudo /etc/init.d/networking restart

[Catsworth]

Yes, you can check by typing this:

If this command returns your link, then you have previously created it. Nonetheless, it does not harm redoing it & creating the right symblink.

Ok, I tried typing the above and got an error that says there is no such file or directory, so I redid the link and then retried and I'm still getting an error. This seems to suggest that the command to set up the symblink isn't working.

[Catsworth]

Ok, sorted. I re-did the link and it seems to have taken this time. The network came up straight away after a reboot (which is nice :) ).

Looks like it's all working ok now, all I need to do now is find a better way of changing/storing the configurations. When I go to help my mates with their crappy ******* installs, and then try to show off Ubuntu, I don't wat to spend half an hour trying to get the wireless to work each time if I can help it :)

[wieman01]

Ok, sorted. I re-did the link and it seems to have taken this time. The network came up straight away after a reboot (which is nice :) ).

Looks like it's all working ok now, all I need to do now is find a better way of changing/storing the configurations. When I go to help my mates with their crappy ******* installs, and then try to show off Ubuntu, I don't wat to spend half an hour trying to get the wireless to work each time if I can help it :)
Yes, good point. You might want to try graphical tools instead... Give Wifi-Radar, Network-Manager, or this one (http://ubuntuforums.org/showthread.php?t=299462) a try.

[flatfish]

I removed the '}' from etc/network/interfaces, and yes the router's ESSID is not hidden. I re-generated the hex key and it is identical to the one I have in the script-I think it must be correct, since I am able to connect to the router.

sudo /etc/init.d/networking restart


* Reconfiguring network interfaces... Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:15:e9:88:c7:45
Sending on LPF/ath0/00:15:e9:88:c7:45
Sending on Socket/fallback
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 20
DHCPOFFER from 192.168.1.254
DHCPREQUEST on ath0 to 255.255.255.255 port 67
DHCPACK from 192.168.1.254
bound to 192.168.1.70 -- renewal in 42010 seconds.


It is definitely connected now, since I am able to browse. I'll now reboot and see what happens.

[wieman01]

It is definitely connected now, since I am able to browse. I'll now reboot and see what happens.
Looks ok now. If you have to restart the network after rebooting, please refer to post #2 of this thread. There is a solution posted.

May I ask what card have you got?

[flatfish]

That did It! It connected automatically on reboot. Thanks a ton! The card is a DLink WDA 2320.

[lukemack]

I got mine working in the end. wpa-supplicant.conf worked for me instead of using the interfaces file. i used the driver suggested here:

http://ubuntuguide.org/ see the section on ndiswrapper for broadcom chipsets and follow the instructions.

[wieman01]

I got mine working in the end. wpa-supplicant.conf worked for me instead of using the interfaces file. i used the driver suggested here:

http://ubuntuguide.org/ see the section on ndiswrapper for broadcom chipsets and follow the instructions.
For some reason, Broadcom chips are a bit of a trouble here. Will have to mention that in my guide. Strange thing.

[katu]

"iwconfig" is irrelevant at this stage... Another question: Can you connect to unsecured networks for sure? We should start from there... If you can't, we need to fix your card first.

Sorry, had to leave for a few days. So I couldn't do anything with this net. I did try with a wep encrypted network at a firend's house. And it didn't connect either. And used to be able to connect to that one, when I was still o dapper and using ndiswrapper ;/. Now it sees the network, but never gets the dhcp lease. I don't have access to an unsecure network. The earliest I'll be able to try will be Thursday (the one I was bale to connect, before this fun with trying WPA). darn.

Maybe Ill try to install ndiswrapper tomorrow and see how that goes.

[wieman01]

Sorry, had to leave for a few days. So I couldn't do anything with this net. I did try with a wep encrypted network at a firend's house. And it didn't connect either. And used to be able to connect to that one, when I was still o dapper and using ndiswrapper ;/. Now it sees the network, but never gets the dhcp lease. I don't have access to an unsecure network. The earliest I'll be able to try will be Thursday (the one I was bale to connect, before this fun with trying WPA). darn.

Maybe Ill try to install ndiswrapper tomorrow and see how that goes.
That's bad news... Try to connect to unsecured networks first, that'll be a lot easier. When you do so, please make sure that you definitely remove programs like Wifi-Radar, Network-Manager, and Firestarter. Those can create a nightmare for you.

Once you can connect to unsecured networks, I am sure WPA will be an easy one.

[compwiz18]

Hi wieman01, I'm back with another weird question: How do I use iwconfig to connect to a hidden wireless network? I _think_ it is possible, but I'm not sure. I thought I had done it before by using the command iwconfig wlan0 essid "someonesessid", but that appears not to work today.

Thanks again for all your help.

[wieman01]

Hi wieman01, I'm back with another weird question: How do I use iwconfig to connect to a hidden wireless network? I _think_ it is possible, but I'm not sure. I thought I had done it before by using the command iwconfig wlan0 essid "someonesessid", but that appears not to work today.
All you need to do is set the ESSID in the used manner as you have pointed out... Hiding the ESSID merely entails that scanning yields no results. That's it. Only if you configure WPA using my approach do you have to specify whether the ID is broadcast or not.

[compwiz18]

Darn. Well, exams now, program later.

I'll get back to you if it still doesn't work.

Thanks for your help :D

[Megabuntu]

Hi!
I'm a new convert to the linux OS. I'm using Xubuntu 6.10 on a Dell Inspiron 2100. I have been trying for days to use my wireless. I have a Dell Truemobile 1150. I tried to go about connecting to the internet via wpa_supplicant.conf. I was able to connect when the encryption was off, but once it was turned on, i couldn't connect. The encryption is WPA1 and I set up the network/interfaces with Dhcp as you described.

I noticed that you told several people that they should remove the Network Manager program. I wasn't sure if I should because during the day I connect via wired ethernet, but at home I'd like to use wireless, and I thought it would be nice to have a GUI to do the switching with.

Here's what happens when I try to restart the network:
sudo /etc/init.d/networking restart
* Reconfiguring network interfaces... There is already a pid file /var/run/dhclient.eth1.pid with pid 5119
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:02:2d:8b:53:1b
Sending on LPF/eth1/00:02:2d:8b:53:1b
Sending on Socket/fallback
DHCPRELEASE on eth1 to 192.168.12.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODE]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODE]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODE]: Invalid argument
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - There is already a pid file /var/run/dhclient.eth1.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:02:2d:8b:53:1b
Sending on LPF/eth1/00:02:2d:8b:53:1b
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 21
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 4
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

Here's my network/interfaces:
cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid ****
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk 455edbd8f697***.....

I'm sorry to be so verbose and take up space but I am at wit's end.
](*,)

[wieman01]

What wireless card have you got? Broadcom by chance? And what driver are you using.

This information is crucial because the wpa-driver "wext" complains that there is an issue with compatibility. Moreover it's necessary to remove Network-Manager as it will interfer with this approach. Does Network-Manager work for you in general? If so, I'd go for it instead.

EDIT:
This might be interesting for you as well: http://www.ubuntuforums.org/showthread.php?t=304217&highlight=Lucent+IEEE

[Megabuntu]

It's a Dell TrueMobile 1150 and it's supposed to use (?) an orinoco driver. I read about wext and what I understood was that it could work for a lot of cards. Should my network/interfaces list orinoco as the driver?

Network Manager works only for the wired connection. I can't get it to work for the wireless. I just didn't know that if I took networtk manager off then basically i'd have to go through terminal (which isn't a big problem, but slightly less convenient than the gui) to connect through the wired ethernet.

the link you sent looks like it deals with a similar problem as mine, but I know so little, I am not sure what applies and what doesn't.

[Megabuntu]

the link you posted (http://www.ubuntuforums.org/showthread.php?t=304217&highlight=Lucent+IEEE) mentions options of network manager that I don't have. Maybe it's a difference between xubuntu and ubuntu????

[wieman01]

the link you posted (http://www.ubuntuforums.org/showthread.php?t=304217&highlight=Lucent+IEEE) mentions options of network manager that I don't have. Maybe it's a difference between xubuntu and ubuntu????
I am not entirely sure to be honest. Orinoco could be a problem, but check out other threads before you give up. You may also deploy your card's Windows driver instead using "ndiswrapper"... Is that an option? Normally "ndiswrapper" yields better results as it relies on the native Windows driver for your card.

Sorry I cannot advise more.

[compwiz18]

Darn. Well, exams now, program later.

I'll get back to you if it still doesn't work.

Thanks for your help :D
Well, it seems to be working this morning...weird. I even rebooted yesterday.

[ryu kun]

How can I make it search only a specific interval?

[wieman01]

How can I make it search only a specific interval?
You need to help me there... Are you referring to DHCP intervals? That's nothing I can help you with since this has nothing to do with wireless security. Have you got trouble connecting?

[ryu kun]

You need to help me there... Are you referring to DHCP intervals? That's nothing I can help you with since this has nothing to do with wireless security. Have you got trouble connecting?

Thanks for quick reply. Yes, I have a problem. I added a script called "S95wireless-network" to /etc/rcS.d but sometimes Ubuntu starts without a connection and in this case I have to restart networking manually with this command: sudo /etc/init.d/networking restart.

Sometimes it can't find any DHCP offer and can't connect when booting. So I thought that if I can set a static interval maybe I could solve this problem and speed up the DHCP offer/receive process, but today I realised that I was wrong, it doesn't use the same interval each time...

So, I wonder how can I make it regularly establish my connection when booting.

[wieman01]

Thanks for quick reply. Yes, I have a problem. I added a script called "S95wireless-network" to /etc/rcS.d but sometimes Ubuntu starts without a connection and in this case I have to restart networking manually with this command: sudo /etc/init.d/networking restart.

Sometimes it can't find any DHCP offer and can't connect when booting. So I thought that if I can set a static interval maybe I could solve this problem and speed up the DHCP offer/receive process, but today I realised that I was wrong, it doesn't use the same interval each time...

So, I wonder how can I make it regularly establish my connection when booting.
Have you tried the solution as posted in post #2 of this thread? Please let me know if this does the job for you.

In addition, you might want to try static IP configuration instead. There could be a problem with DHCP. If all this does not help, drop me a note.

EDIT:
What card/adapter have you got again?

[frick]

I am still a real new guy to Unbuntu edgy....

Many of the steps in this wep fix are not working or necessary in Edgy. The only problem is that I am to new to figure out the steps necessary in Edgy to make this wep fix to work.

Right now, I am running with no WIFI security... and that makes me a bit twitchy.

In 6.10 my card and drivers come up out of the box. The native Network Connection manager does little to make things work.

Wifi-radar worked to get me up on the net, but it does not help with WEP or WPA at all.

Any EDGY EFT fix?

Frick

[Peacepunk]

*****************************Revoking read-permission from 'others'*********************************

sudo chmod o=-r /etc/network/interfaces
*****************************Revoking read-permission from 'others'*********************************

A bit more info on this part maybe ?

Cheers - congrats

I still have to restart my network after login in ubuntu 6.06, but it does work.
[ See my post on sniffing right here & you'll understand THIS howto was crucial. Bandwith is very expensive in Cambodia.]

wpa_gui returns the right info BTW, and allow me to disconnect-connect when needed.

Heading to the "startup Script" phase now...

Jean-Philippe

[wieman01]

I am still a real new guy to Unbuntu edgy....

Many of the steps in this wep fix are not working or necessary in Edgy. The only problem is that I am to new to figure out the steps necessary in Edgy to make this wep fix to work.

Right now, I am running with no WIFI security... and that makes me a bit twitchy.

In 6.10 my card and drivers come up out of the box. The native Network Connection manager does little to make things work.

Wifi-radar worked to get me up on the net, but it does not help with WEP or WPA at all.

Any EDGY EFT fix?

Frick
Wifi-Radar should be fine with WPA and WEP as well.

[wieman01]

A bit more info on this part maybe ?
This ensures that no unprivileged users can read the contents of "/etc/network/interfaces" and thus gain access to secret network keys. It a simple security measure and you might as well ignore it. But I'll update the thread one of these days and highlight the purpose of this section.

[gamerteck]

I can confirm this worked on my laptop, connecting though LEAP authentication.

HP/Compaq NC6230

The only hitch was that on this model, which comes with integrated wireless, you have to input the config in the eth1 field. Config as follows.



auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid <your_essid>
wpa-eap LEAP
wpa-key-mgmt IEEE8021X
wpa-identity <your_user_name>
wpa-password <your_password>


Big-up to you wieman01 for posting this howto!!=D>

Thank you very much!!

[cara_cooper]

Hey,

I followed the directions to set up a wpa tkip psk and it's not working. it keeps finding errors. and why is it that when i go to get the wpa-psk key it is different everytime? should i just type in the key that we use for the other computers?

[cara_cooper]

I keep getting the error while getting interface flags: no such device

and what driver interface am i supposed to use there's madwifi and wext and some others but they aren't working i have a belkin/atheros wireless card. i thought that i was supposed to use madwifi with that idk.
it seems like i don't have the right driver interface or something. was there something else i am supposed to do besides type one of the interface names (like wext or madwifi etc...)


thanks for the help

yael

p.s i'm new at this i'm trying to learn though :D

[javapinoy]

well i just found this website today, and i followed the instructions provided and it worked out for me. but i originally followed the directions of a separate website to setup my wireless usb device and ndiswrapper and such and only this website to setup wpa.

i had a similar problem when i rebooted my computer and i got a lot of device not found sort of errors because my device wasn't turning on (the leds were off so i assumed it was off) but i just went through and did some commands like:

sudo depmod -a
sudo modprobe ndiswrapper

and it turned back on and i was then able to use the instructions provided above

sudo /etc/init.d/networking restart

to get it up and running again

maybe some of these commands are useful to you too
here are the websites i followed before getting to here

http://www.linuxquestions.org/questions/showthread.php?t=406333&highlight=mn710
http://ndiswrapper.sourceforge.net/mediawiki/index.php/Installation

hopefully some of those pages are relevant to you

noel

[wieman01]

I keep getting the error while getting interface flags: no such device
I suppose that your network adapter / Linux driver does not support WPA. What adapter have you got & what driver do you use?

Plus it would be important to know if you can connect to unsecured networks. Please also post your script.

EDIT:
As pointed out by Javapinoy, "ndiswrapper" could an option for you. Check it out.

[d3dtn01]

I followed the excellent HowTo, but have had no success. I setup my network with WPA2 and DHCP, so my interfaces files reads like this:



auto lo
iface lo inet loopback

# The primary network interface
iface eth0 inet dhcp

# The wireless network interface
auto wlan0
iface wlan0 inet dhcp
wpa-driver ndiswrapper
wpa-conf managed
wpa-ssid habibi
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk c1cc29f9151cedb15d292d1607e4aba74e8680cda61986f122 5702668b818873


I saved the file, then restart my network with the command:


sudo /etc/init.d/networking restart

This is the output that I got:


daren@DellB120:~$ sudo /etc/init.d/networking restart
Password:
* Reconfiguring network interfaces... There is already a pid file /var/run/dhclient.eth0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:14:22:9a:89:92
Sending on LPF/eth0/00:14:22:9a:89:92
Sending on Socket/fallback
DHCPRELEASE on eth0 to 192.168.1.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:14:a5:4f:36:1a
Sending on LPF/wlan0/00:14:a5:4f:36:1a
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
There is already a pid file /var/run/dhclient.eth0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:14:22:9a:89:92
Sending on LPF/eth0/00:14:22:9a:89:92
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
No DHCPOFFERS received.
No working leases in persistent database - sleeping.


Did I make any obvious mistakes? Any suggestions?

[wieman01]

Assuming that you use "ndiswrapper" (either "wlan0" or "eth1") in connection with a WPA2-capable(!) Windows driver, your file should read like this (I am commenting the eth0 interface for testing):

auto lo
iface lo inet loopback

# The primary network interface
#iface eth0 inet dhcp

# The wireless network interface
auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid habibi
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk c1cc29f9151cedb15d292d1607e4aba74e8680cda61986f122 5702668b818873
The correct wpa-driver for "ndiswrapper" is "wext". You are not hiding your ESSID, are you? Can you connect to unsecured networks?

[d3dtn01]

Yipee! I'm connected. Thanks for your help. I changed my driver to wext. I also realized that my router broadcast was disabled. After enabling it and modifying the driver in the interfaces file I was able to connect. Let's hope it lasts. Many, many thanks for resolving this annoying problem.

[wieman01]

Yipee! I'm connected. Thanks for your help. I changed my driver to wext. I also realized that my router broadcast was disabled. After enabling it and modifying the driver in the interfaces file I was able to connect. Let's hope it lasts. Many, many thanks for resolving this annoying problem.
No problem. Change "wpa-ap-scan" if you want to disable broadcast nonetheless:

wpa-ap-scan 2

[heyo]

good post thats very useful for alot of pppl.. wireless is very widespread and unfortunatelty many of them are unsecured

[FrancoNero]

all this should work out-of-the-box without anyone having to edit anything or run any command lines.... seriously, an ubuntu user should just have to click on his/her network manager icon, select the wireless lan he wants to connect to and select the sorts of options like wpa, aes etc and enter the passphrase.... we're in 2007, people do things by clicking and selecting, not by typing commands and editing text files. is it linux for human beings or not?

[Peacepunk]

It Works! I sure feel the same, but if dumb people like me & my wife can do it, the point-and-click option isn't _that_ important.
Check this (http://www.ubuntuforums.org/showthread.php?t=349980).

To keep this discussion technical, why don't you try wpa_gui, so to make the thread progress on the point'N'click options?

Currently, I have to command-line the start of it, then I can use the wpa GUI thingy to disconnect/reconnect when needed.


As stated by frodon, the actual discussion happens here (http://www.ubuntuforums.org/showthread.php?t=202834).



They should lock this one with a Top-Page notice on the open discussion thread.

Cheers

Jean-Philippe.

[wieman01]

all this should work out-of-the-box without anyone having to edit anything or run any command lines.... seriously, an ubuntu user should just have to click on his/her network manager icon, select the wireless lan he wants to connect to and select the sorts of options like wpa, aes etc and enter the passphrase.... we're in 2007, people do things by clicking and selecting, not by typing commands and editing text files. is it linux for human beings or not?
You do have a point, I wasn't happy when I found out either. Unfortunately all existing graphical tools don't deliver (yet) what I was in need of in the first place, i.e. WPA2 with static IP (DHCP disabled) and hidden broadcast of the ESSID. There are standard tools such as Network Manager, Wifi-Radar, etc. but all of them have certain drawbacks and insufficiencies.

Give this (http://ubuntuforums.org/showthread.php?t=299462) program a go, I have heard it works for a lot people.

Let's hope this thread will become moot by the time the next stable release of Ubuntu comes out. Look forward to it.

[brodiepearce]

I followed the guide step for step, unfortunately I'm still having issues. Previously Ubuntu was idling on "Configuring Network Interfaces" on boot, Ctrl-C would skip it, but then a blank screen would occur after login.

After doing this guide, it gets through the interface configuration, however I still get a blank screen. I'm using a Minitar MN54GPC-RC pci wifi NIC, I'm guessing that the rest of the issue is due to the card? Should I install some drivers for it or are there still some settings that could be changed to fix the issue?

[wieman01]

I followed the guide step for step, unfortunately I'm still having issues. Previously Ubuntu was idling on "Configuring Network Interfaces" on boot, Ctrl-C would skip it, but then a blank screen would occur after login.

After doing this guide, it gets through the interface configuration, however I still get a blank screen. I'm using a Minitar MN54GPC-RC pci wifi NIC, I'm guessing that the rest of the issue is due to the card? Should I install some drivers for it or are there still some settings that could be changed to fix the issue?
Can you connect to unsecured networks? Second, please try WPA1 before you go ahead with WPA2 which some cards don't seem to support.

[brodiepearce]

Can you connect to unsecured networks? Second, please try WPA1 before you go ahead with WPA2 which some cards don't seem to support.

Tried again just now on a fresh install of Dapper, the same problem still occurs on WPA1. I'll try it again with just SSID enabled.

*edit* Doesn't work with just SSID without encryption either. I'm using a Minitar MN54GPC pci card, "unco" has published a pretty comprehensive guide (http://www.ubuntuforums.org/showthread.php?t=259355&highlight=minitar) on getting this card to work with Dapper, I was hoping that it wouldn't be necessary but it appears it is. Currently I'm just using the wext driver as defined in the example code, should I try using the Minitar driver instead? Dapper comes with the Ralink RT2500 driver by default though...

[wieman01]

Tried again just now on a fresh install of Dapper, the same problem still occurs on WPA1. I'll try it again with just SSID enabled.

*edit* Doesn't work with just SSID without encryption either. I'm using a Minitar MN54GPC pci card, "unco" has published a pretty comprehensive guide (http://www.ubuntuforums.org/showthread.php?t=259355&highlight=minitar) on getting this card to work with Dapper, I was hoping that it wouldn't be necessary but it appears it is. Currently I'm just using the wext driver as defined in the example code, should I try using the Minitar driver instead? Dapper comes with the Ralink RT2500 driver by default though...
The RT2500 driver is fairly BETA as far as I remember (Serialmonkey). I us "ndiswrapper" and the native Windows driver instead (also a Ralink chipset). Please try to connect to unsecured networks first of all, this thread won't be much of help otherwise.

[scoggy]

Just a quicky to say thanks to all for this thread. I'm a linx n00b, and have recently installed Ubuntu on my Dell Inspiron 6000 to dual boot with XP. I was getting a bit frustrated with Ubuntu which I'd heard was great for n00bs. I was getting frustrated trying to solve my wireless issues without internet access. I saved the first page of this thread to my hard drive and it solved my problems (after a bit of user error).

I'm getting long boot times as others are, so I'll look into that next, but it should be easier now I have web access and don't have to go into XP all the time.

I have to say, until this sort of thing is easier Linux is always going to be not-for-the-masses, but helpful people on forums like this go a long way to making it possible for reasonably technical (but not hugely technical) people like me.

Thanks again!

[wieman01]

Just a quicky to say thanks to all for this thread. I'm a linx n00b, and have recently installed Ubuntu on my Dell Inspiron 6000 to dual boot with XP. I was getting a bit frustrated with Ubuntu which I'd heard was great for n00bs. I was getting frustrated trying to solve my wireless issues without internet access. I saved the first page of this thread to my hard drive and it solved my problems (after a bit of user error).

I'm getting long boot times as others are, so I'll look into that next, but it should be easier now I have web access and don't have to go into XP all the time.

I have to say, until this sort of thing is easier Linux is always going to be not-for-the-masses, but helpful people on forums like this go a long way to making it possible for reasonably technical (but not hugely technical) people like me.

Thanks again!
Thanks for posting your note. To shorten boot times, try Static IP instead of DHCP. I use Static IP and there is virtually no delay during startup. Give it a go!

[shaftoe]

First of all, thanks to all of those who have maintained this thread; it has contributed greatly to my sanity.

Recently I installed Ubuntu 5.10 on an old P3 I am attempting to rehabilitate and subsequently upgraded (via the editing sources.list route) to 6.06 LTS. I am a Linux n00b but I have been excited to give it a try, Wired internet works great, but WPA wireless has been a 2+ day headache so far.

I am using a D-link DWL-G520 PCI card and trying to connect to a D-Link router with WPA authentication. If I disable authentication on the router, I can connect to it and browse normally.

Here are the outputs from my system:


foos@waterhouse:~$ uname -a
Linux waterhouse 2.6.15-28-386 #1 PREEMPT Thu Feb 1 15:51:56 UTC 2007 i686 GNU/Linux

foos@waterhouse:~$ ifconfig -a
ath0 Link encap:Ethernet HWaddr 00:0D:88:C8:7D:CF
inet addr:192.168.0.103 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::20d:88ff:fec8:7dcf/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:13 errors:13 dropped:13 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:452 (452.0 b) TX bytes:830 (830.0 b)

eth0 Link encap:Ethernet HWaddr 00:01:02:76:97:DF
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:5388 errors:0 dropped:0 overruns:46 frame:0
TX packets:1637 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2481836 (2.3 MiB) TX bytes:246976 (241.1 KiB)
Interrupt:9 Base address:0x8000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:48905 errors:0 dropped:0 overruns:0 frame:0
TX packets:48905 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3983636 (3.7 MiB) TX bytes:3983636 (3.7 MiB)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

wifi0 Link encap:UNSPEC HWaddr 00-0D-88-C8-7D-CF-61-74-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5251 errors:0 dropped:0 overruns:0 frame:1894386
TX packets:4427 errors:0 dropped:13 overruns:0 carrier:0
collisions:0 txqueuelen:199
RX bytes:704790 (688.2 KiB) TX bytes:240881 (235.2 KiB)
Interrupt:9

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 ath0
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 ath0

foos@waterhouse:~$ iwconfig
lo no wireless extensions.

wifi0 no wireless extensions.

ath0 IEEE 802.11g ESSID:"seaview"
Mode:Managed Frequency:2.447 GHz Access Point: Not-Associated
Bit Rate:54 Mb/s Tx-Power:31 dBm Sensitivity=0/3
Retry:off RTS thr:off Fragment thr:off
Power Management:off
Link Quality=34/94 Signal level=-51 dBm Noise level=-85 dBm
Rx invalid nwid:3428 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

eth0 no wireless extensions.

sit0 no wireless extensions.

foos@waterhouse:~$ lsmod | grep ath
ath_rate_sample 13568 1
ath_pci 97440 0
wlan 210756 4 wlan_scan_sta,ath_rate_sample,ath_pci
ath_hal 191824 3 ath_rate_sample,ath_pci

foos@waterhouse:~$ iwlist scan
lo Interface doesn't support scanning.

wifi0 Interface doesn't support scanning.

ath0 Scan completed :
Cell 01 - Address: 00:0F:3D:4F:26:76
ESSID:"seaview"
Mode:Master
Frequency:2.412 GHz (Channel 1)
Quality=36/94 Signal level=-59 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Extra:ath_ie=dd0900037f01010006ff7f

eth0 Interface doesn't support scanning.

sit0 Interface doesn't support scanning.

foos@waterhouse:~$ cat /etc/network/interfaces
auto lo
iface lo inet loopback


auto ath0
iface ath0 inet static
address 192.168.0.103
netmask 255.255.255.0
network 192.168.0.1
broadcast 192.168.0.255
gateway 192.168.0.1
dns-nameservers 192.168.0.1
wpa-driver madwifi
wpa-conf managed
wpa-ssid seaview
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk HEX-PASSWORD-FROM-WPA_PASSPHRASE

foos@waterhouse:~$ cat /etc/resolv.conf
nameserver 192.168.0.1


I'd appreciate any help that anyone can offer.

Cheers.

[wieman01]

"wifi0" suggests that you have Wifi-Radar installed. Please uninstall it in order for this thread to work for you.

Second there is a minor error as far as the (static) network settings are concerned:

auto ath0
iface ath0 inet static
address 192.168.0.103
netmask 255.255.255.0
network 192.168.0.0
broadcast 192.168.0.255
gateway 192.168.0.1
dns-nameservers 192.168.0.1
wpa-driver madwifi
wpa-conf managed
wpa-ssid seaview
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk HEX-PASSWORD-FROM-WPA_PASSPHRASE
The rest should be fine actually. Please try again and post the results here.

[shaftoe]

Thanks for the quick reply. I changed /etc/network/interfaces per your suggestion. Synaptic shows that the wifi radar package is not installed.

Unfortunately, my problems have persisted. Any further help is appreciated. Thanks.

[ubuntu_demon]

shaftoe :

From https://help.ubuntu.com/community/HardwareSupportComponentsWirelessNetworkCardsDlink :


DAPPER: Nearly works out-of-the-box, but had to add "wireless-rate 11M" to /etc/network/interfaces + reboot or two.


So you may want to experiment with this wireless-rate setting but I hope you won't need to set it to a lower speed.

I'm interested in your result with wpa and especially wpa2 because I'm considering buying the same pci card see :
http://www.ubuntuforums.org/showthread.php?t=363633

[ubuntu_demon]

Thanks for the quick reply. I changed /etc/network/interfaces per your suggestion. Synaptic shows that the wifi radar package is not installed.

Unfortunately, my problems have persisted. Any further help is appreciated. Thanks.
Do you have restricted modules installed ? To install them :

If you are running 686 kernel (works for p3) then :
$sudo aptitude install linux-686

If you are running 386 kernel (default and you are running 386) then :
$sudo aptitude install linux-386

After you have installed them you should do a reboot.

[wieman01]

Thanks for the quick reply. I changed /etc/network/interfaces per your suggestion. Synaptic shows that the wifi radar package is not installed.

Unfortunately, my problems have persisted. Any further help is appreciated. Thanks.
Could you do a:

ifdown ath0
...and a:

ifup -v ath0
Just to see what's really going on. Please post the output.

[wieman01]

Do you have restricted modules installed ? To install them :

If you are running 686 kernel (works for p3) then :
$sudo aptitude install linux-686

If you are running 386 kernel (default and you are running 386) then :
$sudo aptitude install linux-386

After you have installed them you should do a reboot.
Good point...

@shaftoe:

Can you connect to unsecured wireless networks at this stage? Have you tried and are you positive it works?

[shaftoe]

Ok. I have the necessary restricted modules, as
sudo aptitude install linux-386 does not install anything.

I must have been mistaken earlier, because disabling the security on my router does not allow me to connect.

outputs:

foos@waterhouse:~$ sudo ifup -v ath0
Configuring interface ath0=ath0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: ctrl_interface=/var/run/wpa_supplicant
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.ath0.pid -i ath0 -C /var/run/wpa_supplicant -D madwifi
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/ath0
wpa_supplicant: wpa-ap-scan : OK
wpa_supplicant: configuring new network block "0"wpa_supplicant: wpa-ssid : OK
wpa_supplicant: wpa-psk : OK
wpa_supplicant: wpa-pairwise : OK
wpa_supplicant: wpa-group : OK
wpa_supplicant: wpa-key-mgmt : OK
wpa_supplicant: wpa-proto : OK
wpa_supplicant: enabling network 0 : OK

ifconfig ath0 192.168.0.103 netmask 255.255.255.0 broadcast 192.168.0.255 up
route add default gw 192.168.0.1 ath0
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
Synchronizing clock to ntp.ubuntu.com...
Error : Temporary failure in name resolution



foos@waterhouse:~$ sudo ifdown -v ath0
Configuring interface ath0=ath0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/wpasupplicant
wpa_supplicant: ctrl_interface=/var/run/wpa_supplicant
route del default gw 192.168.0.1 ath0
ifconfig ath0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: ctrl_interface=/var/run/wpa_supplicant
wpa_supplicant: terminating wpa_supplicant daemon
Stopped wpa_supplicant (pid 5447).


Thanks for the help.

[ubuntu_demon]

shaftoe :
If you want to connect unsecured make sure the "ath0" part of your /etc/network/interfaces looks like this and nothing else for static (assuming these parameters are correct ):



auto ath0
iface ath0 inet static
address 192.168.0.103
netmask 255.255.255.0
network 192.168.0.0
broadcast 192.168.0.255
gateway 192.168.0.1
dns-nameservers 192.168.0.1


and for dhcp:



auto ath0
iface ath0 inet dhcp


In other words remove the "wpa-" lines when trying to connect unsecured

[shaftoe]

ubuntu_demon:

I made the modification to interfaces but it was fruitless. The output (with dhcp; static did not work either).


foos@waterhouse:~$ sudo /etc/init.d/networking restart
* Reconfiguring network interfaces... Internet Systems Consortium DHCP Client V3.0.3
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:0d:88:c8:7d:cf
Sending on LPF/ath0/00:0d:88:c8:7d:cf
Sending on Socket/fallback
DHCPRELEASE on ath0 to 192.168.0.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
Internet Systems Consortium DHCP Client V3.0.3
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:0d:88:c8:7d:cf
Sending on LPF/ath0/00:0d:88:c8:7d:cf
Sending on Socket/fallback
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 7
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
[ ok ]


I am well and truly stumped.

[wieman01]

Just a thought... Do you want to use the interface "wifi0" instead of "ath0"? Would that make a difference? If it doesn't then you best open a new thread as this rather relates to getting your wireless adapter to work.

[shaftoe]

wieman01:

My wireless card works properly on an unsecured network with the following /etc/network/interfaces:


foos@waterhouse:~$ cat /etc/network/interfaces
auto lo
iface lo inet loopback

iface ath0 inet dhcp
wireless-essid seaview

auto ath0

Here is the output when I bring the connection up:



foos@waterhouse:~$ sudo ifup -v ath0
Configuring interface ath0=ath0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant

dhclient3 -pf /var/run/dhclient.ath0.pid -lf /var/lib/dhcp3/dhclient.ath0.leases ath0
Internet Systems Consortium DHCP Client V3.0.3
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:0d:88:c8:7d:cf
Sending on LPF/ath0/00:0d:88:c8:7d:cf
Sending on Socket/fallback
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 6
DHCPOFFER from 192.168.0.1
DHCPREQUEST on ath0 to 255.255.255.255 port 67
DHCPACK from 192.168.0.1
bound to 192.168.0.100 -- renewal in 292317 seconds.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if- up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
Synchronizing clock to ntp.ubuntu.com...

WPA, unfortunately, still does not work. If anyone has any ideas I am all ears. Thanks much.

[ubuntu_demon]

to shaftoe :

Did you try WPA(2) without hidden essid ?

Did you try both wext and madwifi ?

Did you try connecting in this way ? (more d's means more debug information. try both wext and madwifi) :
$ sudo wpa_supplicant -c/etc/wpa_supplicant/wpa_supplicant.conf -i ath0 -D wext
$ sudo wpa_supplicant -c/etc/wpa_supplicant/wpa_supplicant.conf -i ath0 -D wext -d
$ sudo wpa_supplicant -c/etc/wpa_supplicant/wpa_supplicant.conf -i ath0 -D wext -dd

Now you can puzzle around and see what goes wrong and change that specific setting. That's how I was able to "reverse engineer" the wireless network settings of my university.

[wieman01]

wieman01:

WPA, unfortunately, still does not work. If anyone has any ideas I am all ears. Thanks much.
Ok, that's good news. Please give me a few more details with regard to:

1. ESSID broadcast enabled or not.
2. WPA with TKIP or AES (WPA1 vs. WPA2) -> Check the router's settings please.
3. IP address of your router (which I seem to know already).

Once I know this I am sure we will be able to come up with a working script.

EDIT:
Have you got "wpa-supplicant" installed?

[gejr]

I managed to connect to my wpa-psk network thanks to this guide. The problem is I'm moving my laptop around and sometimes I need to be easily able to connect to other networks. Isn't this type of solution a bit too static? How can I swap easily between networks? Do I have to reconfig /etc/network/interfaces every time?

[wieman01]

I managed to connect to my wpa-psk network thanks to this guide. The problem is I'm moving my laptop around and sometimes I need to be easily able to connect to other networks. Isn't this type of solution a bit too static? How can I swap easily between networks? Do I have to reconfig /etc/network/interfaces every time?
Then you'd better install Network-Manager or Wifi-Radar. This is a static approach, I must agree.

[ubuntu_demon]

I managed to connect to my wpa-psk network thanks to this guide. The problem is I'm moving my laptop around and sometimes I need to be easily able to connect to other networks. Isn't this type of solution a bit too static? How can I swap easily between networks? Do I have to reconfig /etc/network/interfaces every time?
Did you manage to get wpa-psk working with CCMP ? I would be very interested in this because I'm going to buy a PCI card soon. I want a PCI card which supports WPA2 personal with CCMP. Could you please try for me ? Also which step solved the problem ? What were you doing wrong to make it work ?

I use different networks and I use wpa-supplicant. IMHO wpa-supplicant can be a quite dynamic approach.

wpasupplicant.conf :


ap_scan=2

network={
ssid="myhomenetwork"
proto=WPA2
pairwise=CCMP
group=CCMP
key_mgmt=WPA-PSK
psk=********************************
}

network={
ssid="university"
key_mgmt=IEEE8021X
wep_key0=******************
phase2="auth=MSCHAPV2"
identity="************"
password="************"
}

network={
ssid="friend1
psk="******"
# this guy is is living with students in a house where they are using WEP encryption
}

network={
ssid="friend2"
proto=WPA2
key_mgmt=WPA-PSK
psk="******"
# you don't need to specifiy group and pairwise. wpasupplicant will figure it out.
}

network={
ssid="friend3"
proto=WPA
key_mgmt=WPA-PSK
psk="********"
}



my /etc/network/interfaces :



auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf


Now I only have to bring it up (wherever I am) using :
$sudo ifdown eth1 && sudo ifup eth1

The configuration of new networks is often easy because they tend to be like friend1,friend2 and friend3 in my experience (but I only have this laptop for a few months). There's good documentation available in /usr/share/doc/wpasupplicant especially the example configs for all kind of networks are handy.Those reside in /usr/share/doc/wpasupplicant/examples. Finally /usr/share/doc/wpasupplicant/wpa_supplicant.conf shows all the different options.

If you encounter a WPA2 enterprise network (such as universities and companies have). Making small adjustments to your wpasupplicant and looking at the resulting debugging output is your best shot (try both wext and madwifi) :
$ sudo wpa_supplicant -c/etc/wpa_supplicant/wpa_supplicant.conf -i ath1 -Dwext
$ sudo wpa_supplicant -c/etc/wpa_supplicant/wpa_supplicant.conf -i ath1 -Dwext -d
$ sudo wpa_supplicant -c/etc/wpa_supplicant/wpa_supplicant.conf -i ath1 -Dwext -dd

If you on the other hand log into new networks often and you don't want to edit wpasupplicant each time you want to access a new network and you never need WPA(2) then I would suggest network-manager.

networkmanager is often not an option when you need to connect to WPA2 enterprise networks such as universities and companies can have.

Personally I'm a fan of wpasupplicant because I like being in control. But networkmanager is easier. It's your choice :).

[zcik]

I don't have wi-fi radar and I shut down knetworkmanager as specified in the howto. a couple of searches with ps aux revelaed that there was indeed a NetworkManager and NetworkManagerDispatcher running. I killed those and apparently the connection is still not there, but the error messages are different:


* Reconfiguring network interfaces... Ignoring unknown interface eth0=eth0.
wpa_supplicant: unknown or stale ctrl_interface socket located at /var/run/wpa_supplicant/eth1...aborting!
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1
There is already a pid file /var/run/dhclient.eth1.pid with pid 5798864
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:90:4b:9a:0e:d6
Sending on LPF/eth1/00:90:4b:9a:0e:d6
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 13
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

I had a problem that looked similar (the bold text). The reason was spa_supplicant, that was for some strange reason run twice during the bootup process.
TRY killing the wpa_supplicant by

sudo killall wpa_supplicant
and then restarting the network

sudo /etc/init.d/networking restart

If this works for you,
you can try adding an init script that will kill the other annoying instance of wpa_supplicant prior the network is configured durign the bootup:

sudo gedit /etc/init.d/kill-wpa
insert there:

killall -w wpa_supplicant
save
and make executable:

sudo chmod +x /etc/init.d/kill-wpa
make it run during the startup prior to the network config:

sudo ln -s /etc/init.d/kill-wpa /etc/rcS.d/40kill-wpa

I m not sure if this is the right solution but it worked for me :)

[wieman01]

I m not sure if this is the right solution but it worked for me :)
Interesting solution, buddy. Thanks for the post.

[gejr]

When I installed networkmanager and clicked on the nmapplet, all I get is a "Wired network", no way to configure anything wireless. I might've overseen something essential here. Anyone able to point me in the right direction?:)

[ubuntu_demon]

When I installed networkmanager and clicked on the nmapplet, all I get is a "Wired network", no way to configure anything wireless. I might've overseen something essential here. Anyone able to point me in the right direction?:)

You can't combine this howto with networkmanager. So you have to choose.

If you want to use networkmanager you have to remove your wireless interface from /etc/network/interfaces

Then :
$sudo /etc/init.d/networking restart

Then logout of gnome and login again

good luck!

[gejr]

Ah..thanks man! That was the helping sentence I've been looking for a long time. Network manager seems SO much better than the default ubuntu network-admin. I've been tired of being unable to use WPA and having to use iwconfig to find essid's for me. Now networkmanager works perfectly for my needs! Thanks again! :)

[arpad3]

Hi all,
Read your post..nearly understood all of it (I'm new to Linux)..followed the process and it worked well. But,just as a follow up for those who refer this post for wireless connectivity..there is a program 'netmanager' that can be loaded/installed. This program allows you connect networks without much hassel ...great for laptops...supports encriptions....you may need a hard wired connection to download a few files that are not on your pc. It can be found in the Synaptic Package Manager. Ubuntu 6.10 :)

[SVWander]

I have read through all the pages and printed out the howto but I am still confuse and haven't gotten my wireless card to work in a secure environment. You have asked a number of people that question. Mine will work flawlessly without security settings. If seems you say that certain cards are not supported and I am wondering whether the Ralink RT2500 802.11g is one of those cards.

When restarting the network I get this:

im2@tim2-desktop:~$ sudo /etc/init.d/networking restart
Password:
* Reconfiguring network interfaces... There is already a pid file /var/run/dhclient.ra0.pid with pid 4917
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/ra0/00:11:09:07:f4:1f
Sending on LPF/ra0/00:11:09:07:f4:1f
Sending on Socket/fallback
DHCPRELEASE on ra0 to 10.95.0.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - There is already a pid file /var/run/dhclient.ra0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/ra0/00:11:09:07:f4:1f
Sending on LPF/ra0/00:11:09:07:f4:1f
Sending on Socket/fallback
DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 13
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

My network configuration is:

auto ra0
iface ra0 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid NETGEAR
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIO
wpa-key-mgmt WPA-PSK
wpa-pks 095b7f325ed7003f53fad72f8399effa4c37e <my code>



#iface eth1 inet dhcp

#auto eth1

#iface ra0 inet dhcp
#wireless-essid cctexas

and if of any value (I believe in one post you said it wasn't) ifconfig yields this:

tim2@tim2-desktop:~$ ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:130 errors:0 dropped:0 overruns:0 frame:0
TX packets:130 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:8376 (8.1 KiB) TX bytes:8376 (8.1 KiB)

ra0 Link encap:Ethernet HWaddr 00:11:09:07:F4:1F
inet6 addr: fe80::211:9ff:fe07:f41f/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:117 errors:0 dropped:0 overruns:0 frame:0
TX packets:538561 errors:576 dropped:576 overruns:0 carrier:0
collisions:125 txqueuelen:1000
RX bytes:42097 (41.1 KiB) TX bytes:24730395 (23.5 MiB)
Interrupt:11 Base address:0x8000

Any ideas on how I can get this card secured?

Thanks, Tim

[frioux]

Hi!
I am trying to get this LEAP stuff going and I am not really having a lot of luck. I am supposed to be authenticating w/ LEAP (I'm trying to use my school's wireless.) Here is the info you asked for:

Linux FrewSchmidt2 2.6.17-11-386 #2 Thu Feb 1 19:50:13 UTC 2007 i686 GNU/Linux
eth0 Link encap:Ethernet HWaddr 00:11:D8:C9:0B:89
inet addr:10.255.31.59 Bcast:10.255.31.255 Mask:255.255.255.0
inet6 addr: fe80::211:d8ff:fec9:b89/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:188 errors:0 dropped:0 overruns:0 frame:0
TX packets:28 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:80987 (79.0 KiB) TX bytes:2812 (2.7 KiB)
Interrupt:217 Base address:0x6c00

eth1 Link encap:Ethernet HWaddr 00:12:F0:21:E6:85
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:83024 errors:0 dropped:0 overruns:0 frame:0
TX packets:6839 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:177 Base address:0x8000 Memory:fe8ff000-fe8fffff

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:399 errors:0 dropped:0 overruns:0 frame:0
TX packets:399 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:134427 (131.2 KiB) TX bytes:134427 (131.2 KiB)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.255.31.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
0.0.0.0 10.255.31.1 0.0.0.0 UG 0 0 0 eth0
eth1 unassociated ESSID:"letnet"
Mode:Managed Channel=0 Access Point: Not-Associated
Bit Rate:0 kb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

eth0 Link encap:Ethernet HWaddr 00:11:D8:C9:0B:89
inet addr:10.255.31.59 Bcast:10.255.31.255 Mask:255.255.255.0
inet6 addr: fe80::211:d8ff:fec9:b89/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:346 errors:0 dropped:0 overruns:0 frame:0
TX packets:48 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:142573 (139.2 KiB) TX bytes:5503 (5.3 KiB)
Interrupt:217 Base address:0x6c00

eth1 Link encap:Ethernet HWaddr 00:12:F0:21:E6:85
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:86004 errors:0 dropped:0 overruns:0 frame:0
TX packets:7083 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:177 Base address:0x8000 Memory:fe8ff000-fe8fffff

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:405 errors:0 dropped:0 overruns:0 frame:0
TX packets:405 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:136251 (133.0 KiB) TX bytes:136251 (133.0 KiB)

Module Size Used by
rfcomm 38936 0
hidp 32000 2
l2cap 23300 10 rfcomm,hidp
bluetooth 48996 5 rfcomm,hidp,l2cap
ipv6 257632 19
i915 20608 2
drm 72468 3 i915
video 16644 0
tc1100_wmi 7428 0
sbs 15776 0
sony_acpi 5516 0
pcc_acpi 13184 0
i2c_ec 5376 1 sbs
i2c_core 22288 1 i2c_ec
hotkey 10660 0
dev_acpi 11140 0
button 7056 0
battery 10756 0
container 4736 0
ac 5892 0
asus_acpi 16792 0
dm_mod 60088 4
af_packet 21768 6
md_mod 78740 0
cpufreq_ondemand 6944 1
speedstep_centrino 8576 1
freq_table 4996 1 speedstep_centrino
sr_mod 17060 0
sbp2 23304 0
scsi_mod 141320 2 sr_mod,sbp2
parport_pc 36132 0
lp 11972 0
parport 37320 2 parport_pc,lp
pcmcia 38972 0
8139cp 22528 0
ipw2200 113476 0
joydev 10304 0
usbhid 42464 0
8139too 27136 0
mii 6016 2 8139cp,8139too
ieee80211 33608 1 ipw2200
ieee80211_crypt 6016 1 ieee80211
sdhci 18316 0
mmc_core 30232 1 sdhci
tsdev 8256 0
yenta_socket 27916 1
rsrc_nonstatic 14336 1 yenta_socket
pcmcia_core 42128 3 pcmcia,yenta_socket,rsrc_nonstatic
snd_hda_intel 18580 1
snd_hda_codec 163712 1 snd_hda_intel
snd_pcm_oss 46080 0
snd_mixer_oss 18560 1 snd_pcm_oss
snd_pcm 80520 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_timer 23172 1 snd_pcm
snd 55428 8 snd_hda_intel,snd_hda_codec,snd_pcm_oss,snd_mixe
r_oss,snd_pcm,snd_timer
soundcore 9952 1 snd
snd_page_alloc 10504 2 snd_hda_intel,snd_pcm
evdev 10496 2
psmouse 40072 0
pcspkr 3072 0
serio_raw 7300 0
intel_agp 25116 1
agpgart 33456 3 drm,intel_agp
rtc 12596 0
ext3 138888 2
jbd 55700 1 ext3
ohci1394 35248 0
ieee1394 302904 2 sbp2,ohci1394
ehci_hcd 32520 0
uhci_hcd 23176 0
usbcore 130304 4 usbhid,ehci_hcd,uhci_hcd
ide_generic 1536 0
ide_cd 32416 0
cdrom 37792 2 sr_mod,ide_cd
ide_disk 17664 4
piix 10628 1
generic 5252 0
thermal 14600 0
processor 26028 2 speedstep_centrino,thermal
fan 5124 0
fbcon 40480 0
tileblit 2944 1 fbcon
font 8448 1 fbcon
bitblit 6272 1 fbcon
softcursor 2432 1 bitblit
vesafb 8348 0
capability 5000 0
commoncap 7808 1 capability
eth1 Scan completed :
Cell 01 - Address: 00:19:A9:CC:85:70
ESSID:"<hidden>"
Protocol:IEEE 802.11bg
Mode:Master
Channel:1
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=78/100 Signal level=-51 dBm
IE: WPA Version 1
Group Cipher : WEP-104
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : 802.1X
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-104
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : 802.1X
Extra: Last beacon: 248ms ago
Cell 02 - Address: 00:19:A9:CC:9A:00
ESSID:"<hidden>"
Protocol:IEEE 802.11bg
Mode:Master
Channel:6
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=67/100 Signal level=-60 dBm
IE: WPA Version 1
Group Cipher : WEP-104
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : 802.1X
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-104
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : 802.1X
Extra: Last beacon: 100ms ago
Cell 03 - Address: 00:19:A9:CC:7E:30
ESSID:"<hidden>"
Protocol:IEEE 802.11bg
Mode:Master
Channel:6
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=42/100 Signal level=-75 dBm
IE: WPA Version 1
Group Cipher : WEP-104
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : 802.1X
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-104
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : 802.1X
Extra: Last beacon: 124ms ago
Cell 04 - Address: 00:13:C3:05:DD:F0
ESSID:"<hidden>"
Protocol:IEEE 802.11bg
Mode:Master
Channel:9
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=37/100 Signal level=-78 dBm
Extra: Last beacon: 92ms ago
Cell 05 - Address: 00:19:A9:CC:92:70
ESSID:"<hidden>"
Protocol:IEEE 802.11bg
Mode:Master
Channel:11
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=90/100 Signal level=-39 dBm
IE: WPA Version 1
Group Cipher : WEP-104
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : 802.1X
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-104
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : 802.1X
Extra: Last beacon: 44ms ago
Cell 06 - Address: 96:4D:AB:E5:A4:1F
ESSID:"WLCM"
Protocol:IEEE 802.11b
Mode:Ad-Hoc
Channel:11
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Quality=29/100 Signal level=-82 dBm
Extra: Last beacon: 40ms ago
Cell 07 - Address: 00:19:A9:CC:81:C0
ESSID:"<hidden>"
Protocol:IEEE 802.11bg
Mode:Master
Channel:11
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=48/100 Signal level=-72 dBm
IE: WPA Version 1
Group Cipher : WEP-104
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : 802.1X
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-104
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : 802.1X
Extra: Last beacon: 40ms ago
Cell 08 - Address: 00:19:A9:CC:99:B0
ESSID:"<hidden>"
Protocol:IEEE 802.11bg
Mode:Master
Channel:1
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=20/100 Signal level=-86 dBm
IE: WPA Version 1
Group Cipher : WEP-104
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : 802.1X
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-104
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : 802.1X
Extra: Last beacon: 2500ms ago
Cell 09 - Address: 00:19:A9:CC:85:70
ESSID:"letnet"
Protocol:IEEE 802.11bg
Mode:Master
Channel:1
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=76/100 Signal level=-53 dBm
IE: WPA Version 1
Group Cipher : WEP-104
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : 802.1X
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-104
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : 802.1X
Extra: Last beacon: 640ms ago
Cell 10 - Address: 00:19:A9:CC:9A:00
ESSID:"letnet"
Protocol:IEEE 802.11bg
Mode:Master
Channel:6
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=68/100 Signal level=-59 dBm
IE: WPA Version 1
Group Cipher : WEP-104
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : 802.1X
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-104
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : 802.1X
Extra: Last beacon: 540ms ago
Cell 11 - Address: 00:19:A9:CC:92:70
ESSID:"letnet"
Protocol:IEEE 802.11bg
Mode:Master
Channel:11
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=90/100 Signal level=-39 dBm
IE: WPA Version 1
Group Cipher : WEP-104
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : 802.1X
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-104
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : 802.1X
Extra: Last beacon: 408ms ago
Cell 12 - Address: 00:19:A9:CC:7E:30
ESSID:"letnet"
Protocol:IEEE 802.11bg
Mode:Master
Channel:6
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=41/100 Signal level=-76 dBm
IE: WPA Version 1
Group Cipher : WEP-104
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : 802.1X
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-104
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : 802.1X
Extra: Last beacon: 7992ms ago
Cell 13 - Address: 00:19:A9:CC:81:C0
ESSID:"letnet"
Protocol:IEEE 802.11bg
Mode:Master
Channel:11
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=39/100 Signal level=-77 dBm
IE: WPA Version 1
Group Cipher : WEP-104
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : 802.1X
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-104
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : 802.1X
Extra: Last beacon: 404ms ago

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid letnet
wpa-ap-scan 2
wpa-eap LEAP
wpa-key-mgmt IEE8021X
wpa-identity FrewSchmidt
wpa-password ###########

search lgv1.dungeon.letnet.net
nameserver 10.0.2.6


Any help at all would be killer.

[wieman01]

Any ideas on how I can get this card secured?

Thanks, Tim
I used to mention this in the thread... the Ralink driver that comes with Ubuntu is not quite suitable and - as far as I know - won't work with this approach. But you will find help here:

http://rt2x00.serialmonkey.com/wiki/index.php?title=Main_Page

I will update my thread accordingly.

[wieman01]

Cell 13 - Address: 00:19:A9:CC:81:C0
ESSID:"letnet"
Protocol:IEEE 802.11bg
Mode:Master
Channel:11
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=39/100 Signal level=-77 dBm
IE: WPA Version 1
Group Cipher : WEP-104
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : 802.1X
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-104
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : 802.1X
Extra: Last beacon: 404ms ago
This is definitely LEAP, right? I'd try this:

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid letnet
wpa-ap-scan 2
wpa-pairwise TKIP CCMP
wpa-group WEP104
wpa-eap LEAP
wpa-key-mgmt IEE8021X
wpa-identity FrewSchmidt
wpa-password ###########

Does your wireless driver support LEAP?

[frioux]

I tried with the

wpa-pairwise TKIP CCMP
wpa-group WEP104
lines and it didn't help. My driver supports LEAP I think. It's the ipw2200. Also, I think that entry 13 is a false entry as our network doesn't broadcast their ESSID (I think). And my signal strength should be really high since I am about 12 feet from one of the wireless APs. I really appreciate your help. It would be so cool to have wireless in linux.

[wieman01]

I tried with the

wpa-pairwise TKIP CCMP
wpa-group WEP104
lines and it didn't help. My driver supports LEAP I think. It's the ipw2200. Also, I think that entry 13 is a false entry as our network doesn't broadcast their ESSID (I think). And my signal strength should be really high since I am about 12 feet from one of the wireless APs. I really appreciate your help. It would be so cool to have wireless in linux.
Perhaps try this as well:

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid letnet
wpa-ap-scan 1
wpa-pairwise TKIP CCMP
wpa-group WEP104
wpa-eap LEAP
wpa-key-mgmt IEE8021X
wpa-identity FrewSchmidt
wpa-password ###########
Could you post the output of this please (try both scripts):

sudo ifdown -v eth1

sudo ifup -v eth1
Let's see what's going on then...

[LanikSJ]

Thank you to those who took the time to write the above guide, once I found it took me about 10 mins to get my wireless up and running.

:popcorn:

[pleurastic]

Toshiba Satellite L25-S1195 with D-Link DWL-G630 (AR5005G 01)
XUBUNTU 2.6.17.11
Working!

/interfaces
# see http://www.ubuntuforums.org/showthread.php?t=202834
# and http://www.ubuntuforums.org/showthread.php?t=225290
auto lo
iface lo inet loopback


iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp

auto eth2
iface eth2 inet dhcp


auto ath0
iface ath0 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid <my ssid>
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <generated per message 1>
wireless-essid <my essid>

After reboot I had to go to Applications>System>Networking and reenter the Network name (ESSID)

It took 10 days of messin' about to find this info....30 minutes to get up and running.
Thank You All!

[H.E. Pennypacker]

I have read through all the pages and printed out the howto but I am still confuse and haven't gotten my wireless card to work in a secure environment. You have asked a number of people that question. Mine will work flawlessly without security settings. If seems you say that certain cards are not supported and I am wondering whether the Ralink RT2500 802.11g is one of those cards.

My network configuration is:

auto ra0
iface ra0 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid NETGEAR
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIO
wpa-key-mgmt WPA-PSK
wpa-pks 095b7f325ed7003f53fad72f8399effa4c37e <my code>

#iface eth1 inet dhcp
#auto eth1
#iface ra0 inet dhcp
#wireless-essid cctexas

and if of any value (I believe in one post you said it wasn't) ifconfig yields this:

Any ideas on how I can get this card secured?

Thanks, Tim

Bro, don't you realize the simple mistake you've made? It may not be your only problem, but you want to get rid of typos first.

The last uncommented line in /etc/network/interfaces should be "wpa-psk," not "wpa-pks." Please review your entire /etc/network/interfaces matches the one on the first page of this thread.

[wieman01]

Bro, don't you realize the simple mistake you've made? It may not be your only problem, but you want to get rid of typos first.

The last uncommented line in /etc/network/interfaces should be "wpa-psk," not "wpa-pks." Please review your entire /etc/network/interfaces matches the one on the first page of this thread.
You are right actually. Have not noticed the typos. Thanks, bro.

[cr4z3d]

I have a Netgear WG511, which seems to have a Prism Duette chip in it. I'm able to connect to any WEP and unsecured networks with no problems. Also I've been using Network Manager, since i'm pretty new to Linux. I followed the steps and changed things where they needed changing. This is what i get when i try restarting the network:


All the commands from "post if stumped"


cr4z3d@cr4z3d-laptop:~$ sudo /etc/init.d/networking restart
* Reconfiguring network interfaces... Ignoring unknown interface eth0=eth0.
There is already a pid file /var/run/dhclient.eth2.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth2/00:09:5b:45:28:f5
Sending on LPF/eth2/00:09:5b:45:28:f5
Sending on Socket/fallback
DHCPRELEASE on eth2 to 192.168.1.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - There is already a pid file /var/run/dhclient.eth2.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth2/00:09:5b:45:28:f5
Sending on LPF/eth2/00:09:5b:45:28:f5
Sending on Socket/fallback
DHCPDISCOVER on eth2 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth2 to 255.255.255.255 port 67 interval 11
DHCPOFFER from 192.168.1.1
DHCPREQUEST on eth2 to 255.255.255.255 port 67
DHCPACK from 192.168.1.1
bound to 192.168.1.109 -- renewal in 37296 seconds.
[ ok ]


cr4z3d@cr4z3d-laptop:~$ uname -a
Linux cr4z3d-laptop 2.6.17-11-generic #2 SMP Thu Feb 1 19:52:28 UTC 2007 i686 GNU/Linux
cr4z3d@cr4z3d-laptop:~$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:0B:CD:33:A6:A6
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:11 Base address:0x8000

eth2 Link encap:Ethernet HWaddr 00:09:5B:45:28:F5
inet addr:192.168.1.109 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::209:5bff:fe45:28f5/64 Scope:Link
UP BROADCAST MULTICAST MTU:1492 Metric:1
RX packets:1943 errors:0 dropped:0 overruns:0 frame:0
TX packets:1651 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1362694 (1.2 MiB) TX bytes:238610 (233.0 KiB)
Interrupt:5

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:6 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:300 (300.0 b) TX bytes:300 (300.0 b)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)



cr4z3d@cr4z3d-laptop:~$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth2
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth2


cr4z3d@cr4z3d-laptop:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

eth2 IEEE 802.11b/g ESSID:"linksys"
Mode:Managed Frequency:2.437 GHz Access Point: 00:0F:66:83:AE:DE
Bit Rate:54 Mb/s Tx-Power=31 dBm Sensitivity=20/200
Retry min limit:8 RTS thr:2347 B Fragment thr:2346 B
Link Quality:181/0 Signal level:-56 dBm Noise level:-3 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

sit0 no wireless extensions.



cr4z3d@cr4z3d-laptop:~$ ifconfig
eth2 Link encap:Ethernet HWaddr 00:09:5B:45:28:F5
inet addr:192.168.1.109 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::209:5bff:fe45:28f5/64 Scope:Link
UP BROADCAST MULTICAST MTU:1492 Metric:1
RX packets:1955 errors:0 dropped:0 overruns:0 frame:0
TX packets:1653 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1366240 (1.3 MiB) TX bytes:238762 (233.1 KiB)
Interrupt:5

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:6 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:300 (300.0 b) TX bytes:300 (300.0 b)



cr4z3d@cr4z3d-laptop:~$ cat /etc/network/interfaces
auto lo
iface lo inet loopback

#auto eth0
#iface eth0 inet dhcp

#auto eth1
#iface eth1 inet dhcp

auto eth2
iface eth2 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid 2041 Red Light Room
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk 8944ef49f8f357d014d060a07b855c5db6b519ad911f73d866 91a130dfb42a03

#auto ath0
#iface ath0 inet dhcp

#auto wlan0
#iface wlan0 inet dhcp


cr4z3d@cr4z3d-laptop:~$ cat /etc/modprobe.d/ndiswrapper
cat: /etc/modprobe.d/ndiswrapper: No such file or directory


cr4z3d@cr4z3d-laptop:~$ cat /etc/resolv.conf
search ph.cox.net
nameserver 68.2.16.30
nameserver 68.2.16.25
nameserver 68.6.16.30


EDIT: noticed some pasting issues, fixed them

[wieman01]

Try "hostap" instead of "wext" (wpa-driver). Any better now?

[cr4z3d]

I got it working using ndiswrapper and networkmanager. That worked fine and seems a little more stable.

[wieman01]

I got it working using ndiswrapper and networkmanager. That worked fine and seems a little more stable.
NetworkManager is certainly the best option if you don't need a static IP address.

[gatoruss]

[Note: You may have to choose a boot sequence other than S40.]



How do I know what "boot sequence" to choose?

[Apperture]

This howto helped me a lot for making 1 connection.
But I have multiple Access Points to connect to (one home, one work, one at customer)
I can not find a good manual that explains how to configure more then one access point.
Can somebody help me with that? And maybe not a bad Idea to stick it to this howto.

[Casla]

Hey wieman01, just want to say thanks for the brilliant HowTo. I v been working on setting up my wifi for ages, your guide cleared out lot of confusions i had, including not knowing that the PSK hex key is generated from wpa_passphrase. :)

I had a bit of trouble just after following your guide, for some reason "Networking restart" is not picking up the lines i added for the wifi interface (eth1 in my case). I went around a big circle reading heaps "info" of dhclient, wpa_supplicant, etc. But in the end, I got it working by removing all other lines in the "/etc/network/interface" file, just leave the wifi (eth1) lines. So if anyone else running to that problem may want try that.

Again, thanks for the guide, and good luck every1.

[wieman01]

How do I know what "boot sequence" to choose?
You'd best choose S40. I guess this will do for you (it did the trick for me).

[wieman01]

This howto helped me a lot for making 1 connection.
But I have multiple Access Points to connect to (one home, one work, one at customer)
I can not find a good manual that explains how to configure more then one access point.
Can somebody help me with that? And maybe not a bad Idea to stick it to this howto.
This HOWTO won't help you I am afraid. You need to go for Network-Manager for instance.

[wieman01]

Hey wieman01, just want to say thanks for the brilliant HowTo. I v been working on setting up my wifi for ages, your guide cleared out lot of confusions i had, including not knowing that the PSK hex key is generated from wpa_passphrase. :)

I had a bit of trouble just after following your guide, for some reason "Networking restart" is not picking up the lines i added for the wifi interface (eth1 in my case). I went around a big circle reading heaps "info" of dhclient, wpa_supplicant, etc. But in the end, I got it working by removing all other lines in the "/etc/network/interface" file, just leave the wifi (eth1) lines. So if anyone else running to that problem may want try that.

Again, thanks for the guide, and good luck every1.
One thing that is important when trying to connect through wireless: You must unplug your Ethernet cable by all means. Not sure if that was your problem, but I am glad you solved it. Thanks for the note.

[acconrad]

I was wondering if someone could tell me whether I will be able to connect to my campus' secure network. I'm currently connected via the open wireless network, but with the secure one it requires some software to install:

https://wiki.brown.edu/confluence/display/CISDOC/Wireless+-+Connecting+to+the+Brown-Secure+Wireless+Network+with+Windows

There it says you need to download this software because our secure network is WPA1/TKIP/EAP, and it requires the SecureW2 client software from Alfa and Ariss Network Solutions. I found that it's a Windows-only program which I guess I could run through Wine, but I don't see how that's going to help me with connecting to the network. Anyway so I did more perusing and I found this one for Mac

https://wiki.brown.edu/confluence/display/CISDOC/Wireless+-+Connecting+to+the+Brown-Secure+Wireless+Network+with+a+Mac

and that talks about 802.1X which my iwlist scan returns when I look at the secure network.

Anyone have any ideas how I would go about connecting to this network?

[Metallinut]

This runs S40WlanDown just before S40networking, so tidies up something in the wlan setup. Then S40networking runs ../init.d/networking which runs 'ifup -a' which successfully starts wlan0 and all other interfaces.


Sorry if this has been answered, but: What makes this run before S40networking? I mean...alphabetically S40WlanDown comes AFTER S40networking.

Also, I've done this on my machine, but have not yet tested. My adapter is eth1 instead of wlan0. I assume that I just need to use ifdown eth1 instead?

Thanks!

[tritohc]

I'm trying to set up a PCMCIA WPC11 v4 card on Xubuntu for use on a WAP secured ESSID broadcast network with PSK & TKIP

I imported the 8180.INF file and installed wpa_supplicant

I get some strange (probably wext related) errors when i restart networking




/etc/network/interfaces
auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet static
address 192.168.1.220
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.1
dns-nameservers 205.171.2.65
wpa-driver wext
wpa-conf managed
wpa-ssid MYSSID
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA_PSK
wpa-psk h3xv4lu3

uname -a
Linux ubuntu 2.6.15-28-386

sudo /etc/init.d/networking restart
*Reconfiguring network interfaces...
ioctl[SIOSCIWAUTH]: Operation not supported
WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH: Operation not supported
WEXT auth param 5 value 0x1 -

(this is where it hangs)


if any text is one off go ahead and comment on it but i had to copy this over manually from my laptop screen so assume that text errors are from the copy and NOT THE MAIN PROBLEM.

[wieman01]

I'm trying to set up a PCMCIA WPC11 v4 card on Xubuntu for use on a WAP secured ESSID broadcast network with PSK & TKIP

I imported the 8180.INF file and installed wpa_supplicant

I get some strange (probably wext related) errors when i restart networking

if any text is one off go ahead and comment on it but i had to copy this over manually from my laptop screen so assume that text errors are from the copy and NOT THE MAIN PROBLEM.
Question: Can you connect to unsecured networks without problem?

[wieman01]

I was wondering if someone could tell me whether I will be able to connect to my campus' secure network. I'm currently connected via the open wireless network, but with the secure one it requires some software to install:

https://wiki.brown.edu/confluence/display/CISDOC/Wireless+-+Connecting+to+the+Brown-Secure+Wireless+Network+with+Windows

There it says you need to download this software because our secure network is WPA1/TKIP/EAP, and it requires the SecureW2 client software from Alfa and Ariss Network Solutions. I found that it's a Windows-only program which I guess I could run through Wine, but I don't see how that's going to help me with connecting to the network. Anyway so I did more perusing and I found this one for Mac

https://wiki.brown.edu/confluence/display/CISDOC/Wireless+-+Connecting+to+the+Brown-Secure+Wireless+Network+with+a+Mac

and that talks about 802.1X which my iwlist scan returns when I look at the secure network.

Anyone have any ideas how I would go about connecting to this network?
Sorry for replying so late... Could your check this out? May be interesting for you. Post there if you need support.

http://ubuntuforums.org/showthread.php?t=304706

[mackyman]

Really many thanks...
Read through this great howto and modified it a bit... And now I can atlast connect to my works wireless network!

Thanks!

[wieman01]

Really many thanks...
Read through this great howto and modified it a bit... And now I can atlast connect to my works wireless network!

Thanks!
Interesting... What wireless network are we talking about (e.g. PEAP, LEAP, etc.)? Just curious which script you may have used.

[mackyman]

Interesting... What wireless network are we talking about (e.g. PEAP, LEAP, etc.)? Just curious which script you may have used.

Well... I just read about the first post and didn't use any script.

And it was a WAP(1) network, wich I didn't know (as noone on the work knew anything about the network, they just use it in windows...).
All I did was change the parameters a bit and iflist scan:ed to find the network, and then adjusted the parameters to fit those last settings.

[johnnyxf]

Greetings.

My 2 cents:
Running Ubuntu 6.10 with a BT Voyager 1105 dongle, which uses the Broadcom4320 chipset. Using WPA-PSK with hidden SSID.

My interfaces file contains:
auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid <ESSID>
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <PASSPHRASE>
wireless-essid <ESSID>

I had the customary trouble with restart. After much fiddling about, I combined methods from posts #2 and #32.

In rcS.d, I inserted the symlinks:
S39wlandown->../init.d/wlandown containing 'ifdown wlan0'
S42wireless-restart->../init.d/wireless-restart containing '/etc/init.d/networking restart'

And this works [for me]. Many thanks to all who have contributed to this thread, especially wieman01 and David Tangye.

I have a couple of questions:
1. I put #! /bin/sh at the top of the shell script files, because it seemed sensible, and because the Debian policy document in init.d said to. Is this actually necessary, or will the system assume that anything in this directory is a shell script? I wondered if you guys assumed that anyone reading this thread would have the sense to do this as a matter of course - I didn't, until I did some learning.

2. What is the significance of 'restart' in the command "/etc/init.d/networking restart"? I have looked in my tutorials, and cannot find a reference to this. What is the distinction between that and simply running "/etc/init.d/networking"?

Thanks again, guys.

[wieman01]

I have a couple of questions:
1. I put #! /bin/sh at the top of the shell script files, because it seemed sensible, and because of the Debian policy document in init.d said to. Is this actually necessary, or will the system assume that anything in this directory is a shell script? I wondered if you guys assumed that anyone reading this thread would have the sense to do this as a matter of course - I didn't, until I did some learning.

2. What is the significance of 'restart' in the command "/etc/init.d/networking restart"? I have looked in my tutorials, and cannot find a reference to this. What is the distinction between that and simply running "/etc/init.d/networking"?
Hi there,

1. No, you don't have to add "#! /bin/sh". The script is recognized as such as soon as you put in the corresponding folder and make it "executable".
2. "/etc/init.d/networking" is a script which you can execute in 3 different manners:
a. start -> start network
b. stop -> stop network
c. restart -> restart network

"/etc/init.d/networking" is pretty much like doing "ifup" or "ifdown". Does this kind of answer your questions?

[johnnyxf]

Greetings wieman01.

Excellent, thanks very much. I have had a look at /etc/init.d/networking, have looked up a few things, and understand what you mean.

atb jxf

[tritohc]

Question: Can you connect to unsecured networks without problem?

i can connect using the wireless network manager application that comes with ubuntu on a WEP network

[mackyman]

Is it possible to make a bash script (or any type of script) that recognizes the network I'm in and change the config-file depending on wich network I am on...

I have 3 different config-files, one at home, one at work, and one by my gf's place. Feels quite unnecessary to start the computer without the wireless connection and start it afterwards with the right config-file

[wieman01]

i can connect using the wireless network manager application that comes with ubuntu on a WEP network
Assuming that there aren't any typos, could it be that you have not generated the PSK correctly? See PSK generation for more... Not sure what else could be wrong.

[wieman01]

Is it possible to make a bash script (or any type of script) that recognizes the network I'm in and change the config-file depending on wich network I am on...

I have 3 different config-files, one at home, one at work, and one by my gf's place. Feels quite unnecessary to start the computer without the wireless connection and start it afterwards with the right config-file
Not if you use this method I am afraid...

[cbrolin]

Do these instructions also work for Ubuntu 6.10 (Edgy)? And how does it relate to the Network Monitor, which also writes into the /etc/network/interfaces file?

By the way, I can't get it working without removing the encryption. I have tried both your instructions and just entering the hexadecimal key into the Network Monitor password field. I also don't understand the relation between wlani and ethj. My file looks like this when it is not encrypted:


auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

iface eth1 inet dhcp
wireless-essid <my-essid>

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp

auto eth1

[Griffiss]

I've been trying to get my wireless to work for 3 days now (since installing Edgy with ASUS WL-138G card + ndiswrapper), and I'm now connected with WPA for the first time thanks to this HowTo!!:)

Nice one Wieman!

Griff

[wieman01]

Do these instructions also work for Ubuntu 6.10 (Edgy)? And how does it relate to the Network Monitor, which also writes into the /etc/network/interfaces file?

By the way, I can't get it working without removing the encryption. I have tried both your instructions and just entering the hexadecimal key into the Network Monitor password field. I also don't understand the relation between wlani and ethj. My file looks like this when it is not encrypted:


auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

iface eth1 inet dhcp
wireless-essid <my-essid>

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp

auto eth1

Network Monitor is the standard networking tool for GNOME which does not support WPA, only WEP. If you need a graphical WPA tool, go for Gnome-Network-Manager. Otherwise give this HOWTO a go and follow the instruction to the T.

[mackyman]

Ok, thanks anyway for the answer. Now I atleast know it's not possible =P

[elamericano]

I think this is a great service to help people be more aware of their options regarding the security of their wireless networks. The only thing I'd add is that a hidden SSID provides no security at all unless you have no encryption on your network. Your router is beaconing just as much as when it's not hidden, and Aircrack will happily list it by MAC address until the client transmits the ssid. Any traffic captured between your client and router is just as captured - the ssid is irrelevant

If anyone is ever adversely affected by this, it would be you or guests to your network - not an attacker. You may have a non-security related reason to do this, but I wouldn't mislead people that it provides them with any security. :-$

[wieman01]

I think this is a great service to help people be more aware of their options regarding the security of their wireless networks. The only thing I'd add is that a hidden SSID provides no security at all unless you have no encryption on your network. Your router is beaconing just as much as when it's not hidden, and Aircrack will happily list it by MAC address until the client transmits the ssid. Any traffic captured between your client and router is just as captured - the ssid is irrelevant

If anyone is ever adversely affected by this, it would be you or guests to your network - not an attacker. You may have a non-security related reason to do this, but I wouldn't mislead people that it provides them with any security. :-$
Hi,

Thanks for the post. Of course hiding your ESSID does not provide any additional security at all under the circumstances as all other security options are turned on. But some people prefer it nonetheless and it "feels" it is safer somehow. I am not writing anywhere in the HOWTO that it adds any security to your network. Guess few people care anyway. Got your point though.

[tedrogers]

But of course, if your router will allow such an option, you could enable MAC address filtering to only allow MAC addresses that you know and trust. Anyone else would be locked out.

[compwiz18]

But of course, if your router will allow such an option, you could enable MAC address filtering to only allow MAC addresses that you know and trust. Anyone else would be locked out.
On the other hand, anyone can change their MAC address to match yours....

[wieman01]

I agree, guys. The only way to fully secure your wireless network is WPA2 with EAP. PSK is a good alternative though. I don't think anyone can compromise a WPA2-PSK secured network if the personal key has sufficient length (say 20 characters) in a reasonable amount of time.

This is my unqualified opinion though.

[wieman01]

But of course, if your router will allow such an option, you could enable MAC address filtering to only allow MAC addresses that you know and trust. Anyone else would be locked out.
MAC cloning is a piece of cake, I must agree with Compwiz18 here.

[tedrogers]

I had no idea it was so easy to clone a MAC address.

Lucky I'm using WPA2 with EAP and a huge random key then eh! ;)

[wieman01]

I had no idea it was so easy to clone a MAC address.

Lucky I'm using WPA2 with EAP and a huge random key then eh! ;)
Guess you are using PSK rather than EAP? :-)

WPA2-PSK is safe by all means.

[p51d78th]

I have a laptop that will disconnect from the router after sitting idle for a while. I can use

sudo /etc/init.d/networking restart

no problem but some people use the laptop that i don't want to give sudo rights. I tried making a ln to the /etc/init.d/wireless-network.sh on the desktop for the user but it doesn't work. Any ideas on how to make it so a non sudo user can reset the networking?

[wieman01]

I have a laptop that will disconnect from the router after sitting idle for a while. I can use

sudo /etc/init.d/networking restart

no problem but some people use the laptop that i don't want to give sudo rights. I tried making a ln to the /etc/init.d/wireless-network.sh on the desktop for the user but it doesn't work. Any ideas on how to make it so a non sudo user can reset the networking?
I don't think you can do this without root privileges.

However, I believe there is a problem with your router if your PC keeps disconnecting. What model do you use? I used to have the same issue with a Linksys WRT54G and it turned out that I had to change one setting (beacon interval from 100 to 20). That did the trick for me.

[cxterm]

I configured my destop using this tutorial. the wireless is connected. But it was disconnected randomly. may be several minutes, or may be several hours. My router is Belkin wireless G router(part #F5D7230-4) and the wireless pci cards is AirLink101 AWLH4030 super G wireless PCI. I use ndiswrapper. My computer is dual system and under windowsxp the wireless connection is good and didn't have the problem. I have searched this forum but didn't find a solution. Any ideas on solving this problem or how to configure the wireless reconnected automatically when it was disconected?

[wieman01]

I configured my destop using this tutorial. the wireless is connected. But it was disconnected randomly. may be several minutes, or may be several hours. My router is Belkin wireless G router(part #F5D7230-4) and the wireless pci cards is AirLink101 AWLH4030 super G wireless PCI. I use ndiswrapper. My computer is dual system and under windowsxp the wireless connection is good and didn't have the problem. I have searched this forum but didn't find a solution. Any ideas on solving this problem or how to configure the wireless reconnected automatically when it was disconected?
Hello,

Used to have the same problem. Take a look at the previous post (#278). I reckon you need to play around with the router's settings a bit.

[ubuntu_demon]

my /etc/network/interfaces :



#auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf


my /etc/wpa_supplicant/wpa_supplicant.conf :



ap_scan=2 # is more secure and first network block is tried first. sort your networks by amount of use

# my own (very secure) WPA2 personal network which also uses hidden essid and (whitelist) macfiltering :
network={
ssid="*****"
bssid=**:**:**:**:**:**
# I added the bssid of my router because I don't want to try to connect to other bssids which could have the same ssid
scan_ssid=1
proto=WPA2
pairwise=CCMP
group=CCMP
key_mgmt=WPA-PSK
#psk="******"
#wpa_passphrase **** ****
#wpa_passphrase wants ssid and plain psk and generates a big psk
psk=********************************************** **************************
}

ap_scan=1 # faster than ap_scan=2

#my university :
network={
ssid="****"
key_mgmt=IEEE8021X
wep_key0=************************
phase2="auth=MSCHAPV2"
identity="******"
password="******"
}



# now follow other networks ...

network={
ssid="typicalwep"
psk="*********"
}

network={
ssid="typicalwpa2"
proto=WPA2
key_mgmt=WPA-PSK
psk="*****"
}

network={
ssid="typicalwpa"
proto=WPA
key_mgmt=WPA-PSK
psk="********"
}



I'm a fan of this approach because it allows me to specify multiple networks and have complete control over the settings. Connecting to the available network is always simple by doing :

$sudo ifdown eth1 && sudo ifup eth1

[wieman01]

I'm a fan of this approach because it allows me to specify multiple networks and have complete control over the settings. Connecting to the available network is always simple by doing :

$sudo ifdown eth1 && sudo ifup eth1
Hi Ubuntu_Demon,

What card have you finally got? And what chipset does it use? Are you happy with it? I am asking because I am looking for a Atheros card at the moment because I want to do away with "ndiswrapper" and need support for injection... for audit reasons.

[ubuntu_demon]

Hi Ubuntu_Demon,

What card have you finally got? And what chipset does it use? Are you happy with it? I am asking because I am looking for a Atheros card at the moment because I want to do away with "ndiswrapper" and need support for injection... for audit reasons.
I recently bought a wg311T and it works perfectly. (I was busy with other stuff lately. I plan to blog about it tomorrow)

[wieman01]

I recently bought a wg311T and it works perfectly. (I was busy with other stuff lately. I plan to blog about it tomorrow)
Cool. Would be nice if you mentioned the Linux driver as well as the chipset.

[ubuntu_demon]

Cool. Would be nice if you mentioned the Linux driver as well as the chipset.
Netgear WG311T
chipset = atheros
linux driver = madwifi

detected out of the box in Dapper but you have to add it in your /etc/network/interfaces yourself.

[Synless]

I just wanted to give some well deserved kudos to all of you for contributing to this worthy cause. :) Also, wanted to post some info regarding LEAP and our environment in hopes it will help someone else out.

We're running Microsoft AD (radius), Cisco Secure ACS (MAC/LEAP/WEP) BSSID. Following your instructions to enable LEAP on an IBM R40 couldn't have been more simple. I am up and running! Thanks.

Syn.

[wieman01]

I just wanted to give some well deserved kudos to all of you for contributing to this worthy cause. :) Also, wanted to post some info regarding LEAP and our environment in hopes it will help someone else out.

We're running Microsoft AD (radius), Cisco Secure ACS (MAC/LEAP/WEP) BSSID. Following your instructions to enable LEAP on an IBM R40 couldn't have been more simple. I am up and running! Thanks.

Syn.
You're welcome. This is an interesting read concerning LEAP & its (low) level of security:

http://asleap.sourceforge.net/README

[Mujaheiden]

Hi,

Ive upgraded fro Dapper to Edgy, and I have the feeling that wireless support out of the box is really better in Edgy (Is this true, also for TKIP encrypted, etc?)

But for Dapper to come online on our encrypted WAN I changed all this wpa supplicant settings, boot up codes, and whatever, so now this laptop only works on the encrypted home network. Only when I put in the live disk it works on unencrypted networks, or allows other logins.

So now my question is: how can Iundo all the things I did before for setting up wireless? You would say that i would be the best to know, but as it is some months ago, and i really cant remember everything I did. So maybe there is a way to undo all the wireless settings? Thus make wpasupplicant shut up, undo startup scripts etc, or do i really have to look for everything i did, and how it should in the original state? I reckon thats gonna be a pretty difficult excercise...

So any tips? Thanx.

[wieman01]

Hi,

Ive upgraded fro Dapper to Edgy, and I have the feeling that wireless support out of the box is really better in Edgy (Is this true, also for TKIP encrypted, etc?)

But for Dapper to come online on our encrypted WAN I changed all this wpa supplicant settings, boot up codes, and whatever, so now this laptop only works on the encrypted home network. Only when I put in the live disk it works on unencrypted networks, or allows other logins.

So now my question is: how can Iundo all the things I did before for setting up wireless? You would say that i would be the best to know, but as it is some months ago, and i really cant remember everything I did. So maybe there is a way to undo all the wireless settings? Thus make wpasupplicant shut up, undo startup scripts etc, or do i really have to look for everything i did, and how it should in the original state? I reckon thats gonna be a pretty difficult excercise...

So any tips? Thanx.
All you have to do is open your "interfaces" file and remove the corresponding lines:

sudo gedit /etc/network/interfaces
Then only leave the first two lines of the section that relate to your interface, e.g.:

auto eth1
iface eth1 inet dhcp
Now uninstall wpa-supplicant if you don't need it (althought uninstalling it is not necessary... it won't start up after removing the respective lines from "interfaces" & rebooting):

sudo apt-get remove wpasupplicant
Does this help?

[3mbc]

A lot of info in this thread and my head is swimming, but I don't want to quit. Belkin F5D7010 (RA2500 out of the box) works fine with no security. Any ideas?

auto ra0
iface ra0 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid Blackhole
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 773e970a9915049c7d22a56671daa512c2fdbb9fc53374eef2 d9baf4d518739a


ra0 Scan completed :
Cell 01 - Address: **********************
Mode:Managed
ESSID:"Blackhole"
Encryption key:on
Channel:6
Quality:0/100 Signal level:-35 dBm Noise level:-192 dBm
Cell 02 - Address: **********************
Mode:Managed
ESSID:"default"
Encryption key:on
Channel:6
Quality:0/100 Signal level:-85 dBm Noise level:-194 dBm

[wieman01]

A lot of info in this thread and my head is swimming, but I don't want to quit. Belkin F5D7010 (RA2500 out of the box) works fine with no security. Any ideas?
I am not entirely sure if this tutorial works for Ralink... I replaced the Ralink driver for my card with "ndiswrapper" in order to get this to work. But I found this link for you:

http://pastebin.ca/408779


auto ra0
iface ra0 inet dhcp
pre-up iwconfig ra0 essid Blackhole
pre-up iwpriv ra0 set NetworkType=Infra
pre-up iwpriv ra0 set AuthMode=WPA2PSK
pre-up iwpriv ra0 set EncrypType=AES
pre-up iwpriv ra0 set WPAPSK="your_password"

[karachuonyo]

Thanks for this how-to wieman01. Even a newbie like me seems to understand the details. However i have been unable to connect with WPA encryption on my wifi pcmcia card under ubuntu. With WEP encryption it connects fine with the generic linux driver. I tried the how-to with wpa-tkip encryption with wext as driver but i get errors which seem to be related to the wext driver and my laptop really really slows down. When i use atmel as the driver then i still get errors claiming wpa_driver_atmel_set_drop_unencrypted and countermeasures not yet implemented. However the green light on the card is blinking showing that it's working ok (with the atmel driver, not wext). Is it possible the generic driver (wext) or atmel do not support wpa encryption. My wifi card is made by safecom with the texas instruments ACX 111 chipset. Any thoughts are welcome.

[wieman01]

Thanks for this how-to wieman01. Even a newbie like me seems to understand the details. However i have been unable to connect with WPA encryption on my wifi pcmcia card under ubuntu. With WEP encryption it connects fine with the generic linux driver. I tried the how-to with wpa-tkip encryption with wext as driver but i get errors which seem to be related to the wext driver and my laptop really really slows down. When i use atmel as the driver then i still get errors claiming wpa_driver_atmel_set_drop_unencrypted and countermeasures not yet implemented. However the green light on the card is blinking showing that it's working ok (with the atmel driver, not wext). Is it possible the generic driver (wext) or atmel do not support wpa encryption. My wifi card is made by safecom with the texas instruments ACX 111 chipset. Any thoughts are welcome.
It is possible that certain cards do not support WPA(2). I don't know your card well enough, but I'd suggest that you do some research on the web. It is certainly the case that some cards support WPA while others don't...

[3mbc]

I got it to work using RutILT: http://cbbk.free.fr/bonrom/

I had to back down to WPA versus WPA2 but it works - great job you guys are doing here.

[Esky]

Great thread and very helpful!

but...
my newbie *** is still stuck :(

I have a SMC SMCWPCI-G EU with RTL818? chip and a WPA2 AP (Siemens gigaset wlan repeater 108). This combo works under windows (dual boot).

some info on my system:

$ uname -a
Linux desktop 2.6.17-11-generic #2 SMP Thu Feb 1 18:03:05 UTC 2007 x86_64 GNU/Linux


$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:19:DB:5D:98:D8
inet addr:192.168.1.36 Bcast:192.168.1.255 Mask:255.255.255.0(works)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0(...)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

wlan0 Link encap:Ethernet HWaddr 00:13:F7:29:FF:55
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:356 dropped:25 overruns:0 frame:0
TX packets:3830 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:160312 (156.5 KiB)
Interrupt:225 Memory:ffffc20000052c00-ffffc20000052d00


$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0



$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 802.11b/g link.. ESSID:"PKS4U2"
Mode:Managed Frequency=2.437 GHz Access Point: Not-Associated
Bit Rate=11 Mb/s
Retry:on Fragment thr:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

sit0 no wireless extensions.


$ ifconfig
same as -a only without sit0


$ lsmod
Module Size Used by
arc4 3712 0
binfmt_misc 16012 1
rfcomm 51360 0
l2cap 31744 5 rfcomm
bluetooth 64644 4 rfcomm,l2cap
powernow_k8 16576 2
cpufreq_userspace 6560 0
cpufreq_stats 9312 0
freq_table 7104 2 powernow_k8,cpufreq_stats
cpufreq_powersave 3456 0
cpufreq_ondemand 10928 1
cpufreq_conservative 11272 0
video 22920 0
tc1100_wmi 10632 0
sbs 20928 0
sony_acpi 7704 0
pcc_acpi 19968 0
i2c_ec 7808 1 sbs
i2c_core 29312 1 i2c_ec
hotkey 14536 0
dev_acpi 17540 0
button 9888 0
battery 14088 0
container 6656 0
ac 8328 0
asus_acpi 21924 0
ipv6 334432 10
af_packet 29452 6
lp 16584 0
tsdev 11136 0
sg 44584 0
snd_hda_intel 23452 1
snd_hda_codec 219392 1 snd_hda_intel
usb_storage 89792 4
r818x 111632 0
snd_pcm_oss 57344 0
snd_mixer_oss 22784 1 snd_pcm_oss
libusual 21544 1 usb_storage
psmouse 51088 0
ieee80211_rtl 99728 1 r818x
pcspkr 5248 0
evdev 14592 1
r1000 20608 0
serio_raw 10244 0
parport_pc 43560 1
parport 49932 2 lp,parport_pc
snd_pcm 108168 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_timer 31112 1 snd_pcm
snd 79016 8 snd_hda_intel,snd_hda_codec,snd_pcm_oss,snd_mixer_ oss,snd_pcm,snd_timer
soundcore 14112 1 snd
snd_page_alloc 13200 2 snd_hda_intel,snd_pcm
shpchp 49068 0
pci_hotplug 38912 1 shpchp
ext3 164880 1
jbd 74024 1 ext3
ehci_hcd 40456 0
ohci_hcd 25988 0
usbcore 167840 5 usb_storage,libusual,ehci_hcd,ohci_hcd
ide_generic 2944 0
ide_disk 21248 3
ide_cd 39584 0
cdrom 43816 1 ide_cd
atiixp 9232 1
sd_mod 25728 12
generic 7940 0
ahci 24452 0
libata 88984 1 ahci
scsi_mod 181424 5 sg,usb_storage,sd_mod,ahci,libata
thermal 19472 0
processor 38280 2 powernow_k8,thermal
fan 7432 0
vesafb 11048 0
capability 7304 0
commoncap 10752 1 capability
vga16fb 16656 1
cfbcopyarea 5376 2 vesafb,vga16fb
vgastate 10368 1 vga16fb
cfbimgblt 4352 2 vesafb,vga16fb
cfbfillrect 6272 2 vesafb,vga16fb
fbcon 45824 72
tileblit 4736 1 fbcon
font 10240 1 fbcon
bitblit 8064 1 fbcon
softcursor 3968 1 bitblit



$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:01:E3:5E:0E:AA
ESSID:"NAME"
Protocol:IEEE 802.11bg
Mode:Master
Channel:6
Encryption key:on
Bit Rates:54 Mb/s
Extra: Rates (Mb/s): 1 2 5.5 9 11 6 12 18 24 36 48 54
Quality:0 Signal level:0 Noise level:158
Extra: Last beacon: 2ms ago

sit0 Interface doesn't support scanning.



$ cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid NAME
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
psk <HASH KEY GENERATED WITH SHELL COMMAND>


$ cat /etc/modprobe.d/ndiswrapper
cat: /etc/modprobe.d/ndiswrapper: No such file or directory


cat /etc/resolv.conf
nameserver 217.19.16.131
nameserver 217.19.16.132


dmesg after running network restart:
[ 3316.498198] rtl8180: bad CRC in monitor mode are accepted
[ 3316.498205] rtl8180: bad CRC in monitor mode are accepted
[ 3316.498234] rtl8180: bad CRC in monitor mode are accepted
[ 3316.498237] rtl8180: bad CRC in monitor mode are accepted
[ 3316.498240] rtl8180: bad CRC in monitor mode are accepted
[ 3320.936432] rtl8180: Bringing up iface
[ 3321.044637] rtl8180: Card successfully reset
[ 3321.504013] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 3321.501498] rtl8180: Setting SW wep key
[ 3321.501578] rtl8180: Setting SW wep key
[ 3321.501791] rtl8180: Setting SW wep key
[ 3321.501952] rtl8180: Setting SW wep key


$ sudo /etc/init.d/networking restart
* Reconfiguring network interfaces... There is already a pid file /var/run/dhclient.eth0.pid with pid 8317
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:19:db:5d:98:d8
Sending on LPF/eth0/00:19:db:5d:98:d8
Sending on Socket/fallback
DHCPRELEASE on eth0 to 192.168.1.1 port 67
There is already a pid file /var/run/dhclient.wlan0.pid with pid 8378
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:13:f7:29:ff:55
Sending on LPF/wlan0/00:13:f7:29:ff:55
Sending on Socket/fallback
There is already a pid file /var/run/dhclient.eth0.pid with pid 5798864
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:19:db:5d:98:d8
Sending on LPF/eth0/00:19:db:5d:98:d8
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
DHCPOFFER from 192.168.1.1
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 192.168.1.1
bound to 192.168.1.36 -- renewal in 119380 seconds.
ioctl[IEEE80211_IOCTL_DELKEY]: Operation not supported
ioctl[IEEE80211_IOCTL_DELKEY]: Operation not supported
ioctl[IEEE80211_IOCTL_DELKEY]: Operation not supported
ioctl[IEEE80211_IOCTL_DELKEY]: Operation not supported
There is already a pid file /var/run/dhclient.wlan0.pid with pid 5798864
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:13:f7:29:ff:55
Sending on LPF/wlan0/00:13:f7:29:ff:55
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 21
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 1
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

[wieman01]

The last line in "/etc/network/interfaces" looks a bit odd. It should read:

wpa-psk <HASH KEY GENERATED WITH SHELL COMMAND>
Can you connect to unsecured wireless networks? And are you sure your router runs WPA2 and not WEP?

What would be helpful as well are these commands:

sudo ifdown wlan0

sudo ifup -v wlan0
Please post the results of both commands.

[Esky]

okay edited the wpa-psk line must have mistyped that. :oops:

changed the AP to not use any security and edited /etc/network/interfaces and that works, but when I change it back to WPA2 or WPA or mixed mode it doesn work :(

Hereś the output you requested:


$ sudo ifdown wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 5798864
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:13:f7:29:ff:55
Sending on LPF/wlan0/00:13:f7:29:ff:55
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 192.168.1.1 port 67
$ sudo ifup -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...

ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan0
wpa_supplicant: wpa-ap-scan 1 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "NAME" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise CCMP TKIP -- OK
wpa_supplicant: wpa-group CCMP TKIP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto RSN WPA -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 5798864
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:13:f7:29:ff:55
Sending on LPF/wlan0/00:13:f7:29:ff:55
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 21
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 17
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
Synchronizing clock to ntp.ubuntu.com...

[wieman01]

okay edited the wpa-psk line must have mistyped that. :oops:

changed the AP to not use any security and edited /etc/network/interfaces and that works, but when I change it back to WPA2 or WPA or mixed mode it doesn work :(

Hereś the output you requested:
It looks to me as if the current (Windows) driver does not support WPA2:

ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWAUTH]: Operation not supported
Have you used the latest driver? Your script is definitely ok.

[Forgott3n]

I am so lost its not even funny. I have tried virtually anything that I come across on the forums or google.

At this point its clear that I need some help...

Here is a dump of commands and their results:


justin@bullbox:~$ uname -a
Linux bullbox 2.6.17-10-generic #2 SMP Fri Oct 13 18:45:35 UTC 2006 i686 GNU/Linux
justin@bullbox:~$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:11:09:76:D3:F1
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:169 Base address:0x6000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:20 errors:0 dropped:0 overruns:0 frame:0
TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1384 (1.3 KiB) TX bytes:1384 (1.3 KiB)

ra0 Link encap:Ethernet HWaddr 00:16:B6:57:46:9C
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:838 errors:70 dropped:70 overruns:0 carrier:0
collisions:191 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:27801 (27.1 KiB)
Interrupt:161 Base address:0x4000

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

justin@bullbox:~$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
justin@bullbox:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

ra0 RT2500 Wireless ESSID:"gray-network"
Mode:Managed Frequency=2.412 GHz Bit Rate:11 Mb/s Tx-Power:0 dBm
RTS thr:off Fragment thr:off
Link Quality=0/100 Signal level=-81 dBm Noise level:-192 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

sit0 no wireless extensions.

justin@bullbox:~$ ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:20 errors:0 dropped:0 overruns:0 frame:0
TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1384 (1.3 KiB) TX bytes:1384 (1.3 KiB)

justin@bullbox:~$ lsmod
Module Size Used by
nls_utf8 3200 1
nls_cp437 6912 1
vfat 14720 1
fat 56348 1 vfat
binfmt_misc 13448 1
ipv6 272288 8
rfcomm 42260 0
l2cap 27136 5 rfcomm
bluetooth 53476 4 rfcomm,l2cap
apm 23280 1
i915 21632 2
drm 74644 3 i915
speedstep_lib 5764 0
cpufreq_userspace 5408 0
cpufreq_stats 7744 0
freq_table 6048 1 cpufreq_stats
cpufreq_powersave 2944 0
cpufreq_ondemand 8876 0
cpufreq_conservative 8712 0
sg 37404 0
sr_mod 18212 0
sd_mod 22656 2
ndiswrapper 208656 0
lp 12964 0
af_packet 24584 2
8139cp 24832 0
rt2500 188004 0
tsdev 9152 0
8139too 29056 0
mii 6912 2 8139cp,8139too
usb_storage 75072 1
scsi_mod 144648 4 sg,sr_mod,sd_mod,usb_storage
snd_intel8x0 34844 1
snd_ac97_codec 97696 1 snd_intel8x0
snd_ac97_bus 3456 1 snd_ac97_codec
snd_pcm_oss 47360 0
snd_mixer_oss 19584 1 snd_pcm_oss
libusual 17040 1 usb_storage
usbhid 45152 0
snd_pcm 84612 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
snd_timer 25348 1 snd_pcm
evdev 11392 3
psmouse 41352 0
serio_raw 8452 0
shpchp 42144 0
pci_hotplug 32828 1 shpchp
snd 58372 8 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_ oss,snd_pcm,snd_timer
soundcore 11232 1 snd
snd_page_alloc 11400 2 snd_intel8x0,snd_pcm
parport_pc 37796 1
parport 39496 2 lp,parport_pc
i2c_i810 6276 0
pcspkr 4352 0
i2c_algo_bit 10376 1 i2c_i810
i2c_core 23424 1 i2c_algo_bit
intel_agp 26012 1
agpgart 34888 3 drm,intel_agp
ext3 142728 1
jbd 62228 1 ext3
ehci_hcd 34696 0
uhci_hcd 24968 0
usbcore 134912 7 ndiswrapper,usb_storage,libusual,usbhid,ehci_hcd,u hci_hcd
ide_generic 2432 0
ide_cd 33696 0
cdrom 38944 2 sr_mod,ide_cd
ide_disk 18560 3
piix 11780 1
generic 5764 0
processor 31560 0
fbcon 41504 0
tileblit 3840 1 fbcon
font 9344 1 fbcon
bitblit 7168 1 fbcon
softcursor 3328 1 bitblit
vesafb 9244 0
capability 5896 0
commoncap 8704 1 capability
justin@bullbox:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

ra0 Scan completed :
Cell 01 - Address: 00:40:10:10:00:03
Mode:Managed
ESSID:"gray-network"
Encryption key:on
Channel:11
Quality:0/100 Signal level:-65 dBm Noise level:-192 dBm

sit0 Interface doesn't support scanning.

justin@bullbox:~$ cat /etc/network/interfaces
auto lo
iface lo inet loopback


iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp

auto eth2
iface eth2 inet dhcp

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp

auto ra0
iface ra0 inet dhcp
pre-up iwconfig ra0 essid gray-network
pre-up iwpriv ra0 set NetworkType=Infra
pre-up iwpriv ra0 set AuthMode=WPA2PSK
pre-up iwpriv ra0 set EncrypType=AES
pre-up iwpriv ra0 set WPAPSK="6049133380"
justin@bullbox:~$ cat /etc/modprobe.d/ndiswrapper
alias wlan0 ndiswrapper
justin@bullbox:~$ cat /etc/resolv.conf
justin@bullbox:~$ sudo /etc/init.d/networking restart
* Reconfiguring network interfaces... There is already a pid file /var/run/dhclient.eth1.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

SIOCSIFADDR: No such device
eth1: ERROR while getting interface flags: No such device
eth1: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up eth1.
There is already a pid file /var/run/dhclient.eth2.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

SIOCSIFADDR: No such device
eth2: ERROR while getting interface flags: No such device
eth2: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up eth2.
There is already a pid file /var/run/dhclient.ath0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

SIOCSIFADDR: No such device
ath0: ERROR while getting interface flags: No such device
ath0: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up ath0.
There is already a pid file /var/run/dhclient.wlan0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

SIOCSIFADDR: No such device
wlan0: ERROR while getting interface flags: No such device
wlan0: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up wlan0.
Interface doesn't accept private ioctl...
set (8BE2): Invalid argument
Failed to bring up ra0.
[ ok ]
justin@bullbox:~$ sudo ifdown ra0
ifdown: interface ra0 not configured
justin@bullbox:~$ sudo ifup -v ra0
Configuring interface ra0=ra0 (inet)
iwconfig ra0 essid gray-network
iwpriv ra0 set NetworkType=Infra
iwpriv ra0 set AuthMode=WPA2PSK
Interface doesn't accept private ioctl...
set (8BE2): Invalid argument
Failed to bring up ra0.
justin@bullbox:~$




I'm really at my wits end here... and I noticed that last command returned (what appears to be) a syntax error... So I don't know why WPA2PSK isn't working...

This is a brandnew install of ubuntu 6.10 and a brandnew Linksys WMP54G PCI card (RT2500 - RaLink?) and I have a router that is Linksys WRT54G v5 (DD-WRT Firmware installed) with WPA2-PSK Mixed (legacy support of WPA-PSK) and TKIP+AES algorithms. So my router is set up for virtually anything.

I haven't been able to get this to work once, at all, for a moment. I have not tried connecting with out any encryption due to security. Any help, especially if it fixes the problem ;), is greatly, greatly, appreciated.

[Esky]

It looks to me as if the current (Windows) driver does not support WPA2:

Have you used the latest driver? Your script is definitely ok.

The AP doesn't seem to do plain WPA, only a mix WPA/WPA2 and that doesn't help :(

Downloaded the latest driver from the realtek site but that doesn't help :(

guess I've got to give up on linux till I buy a new wifi card :cry:

[elmar]

Hi Ubuntu_Demon,

What card have you finally got? And what chipset does it use? Are you happy with it? I am asking because I am looking for a Atheros card at the moment because I want to do away with "ndiswrapper" and need support for injection... for audit reasons.

Hi wieman01,

I´ve got the same problem as Jan Hrbacek: "NetworkManager works for hidden ssid but wpa_supplicant doesn't".

Unfortunately his (your) solution didn´t work on my computer (Celeron 600MHz, Ubuntu 6.10).

I´m using a TP-Link-Card with Atheros-Chipset, so this might be of interst to you.
I can connect with WPA using Network-Manager, but I don´t manage with wpa_supplicant.

I followed all steps (- at least I believe it -) described in your and Jan´s thread.

Some Output:


elmar@graue-kiste:~$ uname -a
Linux graue-kiste 2.6.17-11-generic #2 SMP Thu Feb 1 19:52:28 UTC 2007 i686 GNU/Linux



dmesg:

[17179603.556000] ath_hal: module license 'Proprietary' taints kernel.
[17179603.560000] ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
[17179603.616000] wlan: 0.8.4.2 (0.9.2.1)
[17179603.624000] ath_rate_sample: 1.2 (0.9.2.1)
[17179603.644000] ath_pci: 0.9.4.5 (0.9.2.1)
[17179603.648000] ACPI: PCI Interrupt 0000:01:04.0[A] -> Link [LNKB] -> GSI 11 (level, low) -> IRQ 11
[17179604.244000] wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
[17179604.244000] wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
[17179604.244000] wifi0: turboG rates: 6Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
[17179604.244000] wifi0: H/W encryption support: WEP AES AES_CCM TKIP
[17179604.244000] wifi0: mac 7.9 phy 4.5 radio 5.6
[17179604.244000] wifi0: Use hw queue 1 for WME_AC_BE traffic
[17179604.244000] wifi0: Use hw queue 0 for WME_AC_BK traffic
[17179604.244000] wifi0: Use hw queue 2 for WME_AC_VI traffic
[17179604.244000] wifi0: Use hw queue 3 for WME_AC_VO traffic
[17179604.244000] wifi0: Use hw queue 8 for CAB traffic
[17179604.244000] wifi0: Use hw queue 9 for beacons
[17179604.272000] wifi0: Atheros 5212: mem=0xd4000000, irq=11
...
[17179643.068000] NET: Registered protocol family 10
[17179643.068000] lo: Disabled Privacy Extensions
[17179643.068000] IPv6 over IPv4 tunneling driver
[17179653.584000] ath0: no IPv6 routers present
[17179655.496000] FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[17179978.340000] ath0: no IPv6 routers present
[17180630.112000] ath0: no IPv6 routers present


iwlist scan

lo Interface doesn't support scanning.

wifi0 Interface doesn't support scanning.

ath0 Scan completed :
Cell 01 - Address: 00:15:0C:FD:F9:CC
ESSID:""
Mode:Master
Frequency:2.422 GHz (Channel 3)
Quality=23/94 Signal level=-72 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:bcn_int=100
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 02 - Address: 00:15:0C:84:AC:F7
ESSID:"Beaune"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=3/94 Signal level=-92 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:bcn_int=100
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 03 - Address: 00:15:0C:2E:4A:B4
ESSID:"FRITZ!Box Fon WLAN 7050"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=16/94 Signal level=-79 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:bcn_int=100

sit0 Interface doesn't support scanning.

The first cell is probably mine...


elmar@graue-kiste:~$ lsmod
Module Size Used by
nls_cp437 6912 1
vfat 14720 1
fat 56348 1 vfat
ipv6 272288 8
binfmt_misc 13448 1
rfcomm 42260 0
l2cap 27136 5 rfcomm
bluetooth 53476 4 rfcomm,l2cap
cpufreq_userspace 5408 0
cpufreq_stats 7744 0
freq_table 6048 1 cpufreq_stats
cpufreq_powersave 2944 0
cpufreq_ondemand 8876 0
cpufreq_conservative 8712 0
video 17540 0
tc1100_wmi 8324 0
sbs 16804 0
sony_acpi 6412 0
pcc_acpi 14080 0
i2c_ec 6272 1 sbs
hotkey 11556 0
dev_acpi 12292 0
button 7952 0
sg 37404 0
battery 11652 0
container 5632 0
ac 6788 0
asus_acpi 17688 0
sd_mod 22656 2
nls_utf8 3200 2
ntfs 112116 1
lp 12964 0
af_packet 24584 4
tsdev 9152 0
usb_storage 75072 1
scsi_mod 144648 3 sg,sd_mod,usb_storage
libusual 17040 1 usb_storage
usbhid 45152 0
usblp 15488 0
irtty_sir 10112 0
sir_dev 18308 1 irtty_sir
evdev 11392 1
wlan_scan_sta 15744 1
ath_pci 100000 0
ath_rate_sample 16512 1 ath_pci
wlan 207708 4 wlan_scan_sta,ath_pci,ath_rate_sample
ath_hal 192976 3 ath_pci,ath_rate_sample
psmouse 41352 0
irda 214332 2 irtty_sir,sir_dev
crc_ccitt 3200 1 irda
serio_raw 8452 0
pcspkr 4352 0
analog 12960 0
gameport 17160 1 analog
snd_mpu401 9640 0
snd_mpu401_uart 10240 1 snd_mpu401
snd_rawmidi 27264 1 snd_mpu401_uart
snd_seq_device 9868 1 snd_rawmidi
parport_pc 37796 1
parport 39496 2 lp,parport_pc
floppy 63044 0
snd_intel8x0 34844 1
snd_ac97_codec 97696 1 snd_intel8x0
snd_ac97_bus 3456 1 snd_ac97_codec
snd_pcm_oss 47360 0
snd_mixer_oss 19584 1 snd_pcm_oss
snd_pcm 84612 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
snd_timer 25348 1 snd_pcm
snd 58372 12 snd_mpu401,snd_mpu401_uart,snd_rawmidi,snd_seq_dev ice,snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mi xer_oss,snd_pcm,snd_timer
soundcore 11232 1 snd
snd_page_alloc 11400 2 snd_intel8x0,snd_pcm
hw_random 7320 0
i2c_i810 6276 0
i2c_algo_bit 10376 1 i2c_i810
intel_agp 26012 1
agpgart 34888 2 intel_agp
i2c_core 23424 2 i2c_ec,i2c_algo_bit
shpchp 42144 0
pci_hotplug 32828 1 shpchp
ext3 142856 1
jbd 62228 1 ext3
ehci_hcd 34696 0
uhci_hcd 24968 0
ohci_hcd 22532 0
ide_generic 2432 0
usbcore 134912 8 usb_storage,libusual,usbhid,usblp,ehci_hcd,uhci_hc d,ohci_hcd
ide_disk 18560 4
ide_cd 33696 0
cdrom 38944 1 ide_cd
piix 11780 1
generic 6276 0
thermal 15624 0
processor 31560 1 thermal
fan 6020 0
fbcon 41504 0
tileblit 3840 1 fbcon
font 9344 1 fbcon
bitblit 7168 1 fbcon
softcursor 3328 1 bitblit
vesafb 9244 0
capability 5896 0
commoncap 8704 1 capability

In summary I´d guess, the madwifi-driver is properly installed.

Is set up my interfaces.conf as follows:



auto lo
iface lo inet loopback

auto ath0
iface ath0 inet dhcp
wpa-driver madwifi
wpa-conf managed
wpa-ssid ´hidden ssid name´
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-key-mgmt WPA-PSK
wpa-psk ´secret hex key´


But when I do sudo /etc/init.d/networking restart
I get:


* Reconfiguring network interfaces... There is already a pid file /var/run/dhclient.ath0.pid with pid 4606
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:14:78:10:c1:af
Sending on LPF/ath0/00:14:78:10:c1:af
Sending on Socket/fallback
DHCPRELEASE on ath0 to 192.168.178.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
There is already a pid file /var/run/dhclient.ath0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:14:78:10:c1:af
Sending on LPF/ath0/00:14:78:10:c1:af
Sending on Socket/fallback
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 20
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 2
No DHCPOFFERS received.
No working leases in persistent database - sleeping.


A lot of information - I don´t see through it...

Where´s my mistake?

Thanks in advance!

[wieman01]

Hi wieman01,

I´ve got the same problem as Jan Hrbacek: "NetworkManager works for hidden ssid but wpa_supplicant doesn't".

Unfortunately his (your) solution didn´t work on my computer (Celeron 600MHz, Ubuntu 6.10).

I´m using a TP-Link-Card with Atheros-Chipset, so this might be of interst to you.
I can connect with WPA using Network-Manager, but I don´t manage with wpa_supplicant.

I followed all steps (- at least I believe it -) described in your and Jan´s thread.

A lot of information - I don´t see through it...

Where´s my mistake?

Thanks in advance!
Just in case you have not removed Wifi-Radar ("wifi0" ?) or Gnome-Network-Manager, please do so. I suppose that's the problem here. Post here if the problem persists.

[elmar]

No, Network-manager has been deinstalled by ´apt-get remove´ (as described in one of your threads). I never installed Wifi-Manager, and concerning the graphical ubuntu package manager it is not installed.

Any further suggestions?

Thanks,

Elmar

[wieman01]

No, Network-manager has been deinstalled by ´apt-get remove´ (as described in one of your threads). I never installed Wifi-Manager, and concerning the graphical ubuntu package manager it is not installed.

Any further suggestions?

Thanks,

Elmar
What does "wifi0" refer to in your opinion? Trying to figure out what that error message is about.

[che-hai]

Hi,
I don't know much but I can tell that my ath0 is disconnected from the wifi router when proto is wpa2-psk(aes). I succeded in connecting it using wpa-psk proto but trying wpa2 i got this trouble. Analyzing your thread it seems that my config is ok...
In brief, here's the output of: sudo wpa_supplicant -Dmadwifi -iath0 -c/etc/wpa_supplicant/wpa_supplicant.conf -dd

bla bla...

RSN: encrypted key data - hexdump(len=76): /* bla/bla - the encrypted keys - end bla/bla */
WPA: Unsupported AES-WRAP len 76
CTRL-EVENT-TERMINATING - signal 2 received
Removing interface ath0
State: 4WAY_HANDSHAKE -> DISCONNECTED
wpa_driver_madwifi_deauthenticate

...end bla bla

If you have any ideas why this is not working please let me know. Thanks.

[GoBieN]

I am having trouble connecting to my WPA2 (personal AES) secured wifi network at home.
I al running Ubuntu 7.04 but i think its pretty much the same.

My wireless interface was recognized during install and is using the bmwcutter(?) linux driver, so not ndiswrapper.

I followed the steps mentioned, please help me what can i do further ?


stan@laptop-ubuntu:~$ uname -a
Linux laptop-ubuntu 2.6.20-13-generic #2 SMP Sat Mar 24 23:12:02 UTC 2007 x86_64 GNU/Linux
stan@laptop-ubuntu:~$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:16:36:93:8E:7E
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:10 Base address:0xc000

eth1 Link encap:Ethernet HWaddr 00:14:A5:F3:64:F2
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:255

eth0:avah Link encap:Ethernet HWaddr 00:16:36:93:8E:7E
inet addr:169.254.6.234 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Interrupt:10 Base address:0xc000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:45 errors:0 dropped:0 overruns:0 frame:0
TX packets:45 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4117 (4.0 KiB) TX bytes:4117 (4.0 KiB)

stan@laptop-ubuntu:~$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
0.0.0.0 0.0.0.0 0.0.0.0 U 1000 0 0 eth0
stan@laptop-ubuntu:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

eth1 IEEE 802.11b/g ESSID:off/any Nickname:"Broadcom 4311"
Mode:Managed Access Point: Invalid
RTS thr:off Fragment thr:off
Link Quality=0/100 Signal level=-256 dBm Noise level=-256 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

stan@laptop-ubuntu:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:16:36:93:8E:7E
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:10 Base address:0xc000

eth0:avah Link encap:Ethernet HWaddr 00:16:36:93:8E:7E
inet addr:169.254.6.234 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Interrupt:10 Base address:0xc000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:45 errors:0 dropped:0 overruns:0 frame:0
TX packets:45 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4117 (4.0 KiB) TX bytes:4117 (4.0 KiB)

stan@laptop-ubuntu:~$ lsmod
Module Size Used by
binfmt_misc 14604 1
rfcomm 45352 0
l2cap 28160 5 rfcomm
bluetooth 62340 4 rfcomm,l2cap
ppdev 11272 0
powernow_k8 16480 1
cpufreq_stats 8416 0
cpufreq_userspace 6176 0
cpufreq_conservative 9736 0
cpufreq_powersave 3072 0
cpufreq_ondemand 10640 1
freq_table 6336 3 powernow_k8,cpufreq_stats,cpufreq_ondemand
sony_acpi 7064 0
dev_acpi 17028 0
tc1100_wmi 9224 0
pcc_acpi 15616 0
sbs 17856 0
i2c_ec 6784 1 sbs
dock 11992 0
button 10016 0
container 6144 0
asus_acpi 19756 0
backlight 8448 1 asus_acpi
video 19080 0
ac 6920 0
battery 12040 0
nls_utf8 3456 2
ntfs 101960 2
sbp2 26628 0
parport_pc 40104 0
lp 15048 0
parport 43404 3 ppdev,parport_pc,lp
snd_hda_intel 24224 1
snd_hda_codec 261888 1 snd_hda_intel
snd_pcm_oss 49536 0
snd_mixer_oss 19840 1 snd_pcm_oss
snd_pcm 92808 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_seq_dummy 5380 0
joydev 12928 0
snd_seq_oss 36608 0
snd_seq_midi 11008 0
snd_rawmidi 29696 1 snd_seq_midi
snd_seq_midi_event 9856 2 snd_seq_oss,snd_seq_midi
bcm43xx 135828 0
snd_seq 61856 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_mid i_event
snd_timer 26632 2 snd_pcm,snd_seq
snd_seq_device 10260 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi ,snd_seq
nvidia 7761432 22
sdhci 20748 0
ieee80211softmac 34688 1 bcm43xx
serio_raw 9092 0
ieee80211 37064 2 bcm43xx,ieee80211softmac
ieee80211_crypt 8064 1 ieee80211
ide_cd 35104 0
psmouse 43536 0
mmc_core 31624 1 sdhci
pcspkr 4736 0
cdrom 40744 1 ide_cd
snd 68904 12 snd_hda_intel,snd_hda_codec,snd_pcm_oss,snd_mixer_ oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_ti mer,snd_seq_device
soundcore 10272 1 snd
k8temp 7552 0
shpchp 37404 0
pci_hotplug 36228 1 shpchp
snd_page_alloc 11792 2 snd_hda_intel,snd_pcm
i2c_nforce2 7680 0
i2c_core 26624 3 i2c_ec,nvidia,i2c_nforce2
af_packet 27020 6
tsdev 10112 0
evdev 13056 5
ext3 143760 2
jbd 68208 1 ext3
mbcache 11400 1 ext3
sg 40616 0
sd_mod 25092 6
amd74xx 16944 0 [permanent]
generic 6532 0 [permanent]
usbhid 29088 0
hid 34048 1 usbhid
sata_nv 24580 5
ohci_hcd 24196 0
forcedeth 48776 0
ata_generic 10628 0
ehci_hcd 37004 0
libata 130728 2 sata_nv,ata_generic
scsi_mod 166968 4 sbp2,sg,sd_mod,libata
ohci1394 38088 0
ieee1394 369784 2 sbp2,ohci1394
usbcore 154416 4 usbhid,ohci_hcd,ehci_hcd
thermal 16912 0
processor 34952 2 powernow_k8,thermal
fan 6536 0
fbcon 44416 0
tileblit 4096 1 fbcon
font 9856 1 fbcon
bitblit 7296 1 fbcon
softcursor 3712 1 bitblit
vesafb 10376 0
cfbcopyarea 5120 1 vesafb
cfbimgblt 4096 1 vesafb
cfbfillrect 5632 1 vesafb
capability 7048 0
commoncap 9472 1 capability
stan@laptop-ubuntu:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 No scan results

stan@laptop-ubuntu:~$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid dd-wrt
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 7b7e32e6e56a29edb1f5348d94c8aaf22b34e2acc967092d03 3663172f6475ce

stan@laptop-ubuntu:~$ cat /etc/modprobe.d/ndiswrapper
cat: /etc/modprobe.d/ndiswrapper: No such file or directory

stan@laptop-ubuntu:~$ cat /etc/resolv.conf
# generated by NetworkManager, do not edit!

search gobien.local


nameserver 192.168.1.254


stan@laptop-ubuntu:~$

[GoBieN]

Nevermind my previous post.

It seems I had to get some firmware for my adapter for the wlan would actually be activated. After a reboot i saw the blue light come on. After login i did not have an IP adress but after issuing a sudo dhclient eth1 i got my IP just fine :D

Only one thing dough, i am at 11 mb/sec while my adapter and my router are both 54g.

[wieman01]

Hi,
I don't know much but I can tell that my ath0 is disconnected from the wifi router when proto is wpa2-psk(aes). I succeded in connecting it using wpa-psk proto but trying wpa2 i got this trouble. Analyzing your thread it seems that my config is ok...
In brief, here's the output of: sudo wpa_supplicant -Dmadwifi -iath0 -c/etc/wpa_supplicant/wpa_supplicant.conf -dd

bla bla...

RSN: encrypted key data - hexdump(len=76): /* bla/bla - the encrypted keys - end bla/bla */
WPA: Unsupported AES-WRAP len 76
CTRL-EVENT-TERMINATING - signal 2 received
Removing interface ath0
State: 4WAY_HANDSHAKE -> DISCONNECTED
wpa_driver_madwifi_deauthenticate

...end bla bla

If you have any ideas why this is not working please let me know. Thanks.
Perhaps your card/driver does not support WPA2. What driver are you using?

[elmar]

What does "wifi0" refer to in your opinion? Trying to figure out what that error message is about.

I found out that wifi0 is added by the madwifi driver:

madwifi.org/wiki/UserDocs/UsersGuide (http://madwifi.org/wiki/UserDocs/UsersGuide)

Every Linux network device consists of a prefix followed by a number indicating the device number of the network device. For instance, the ethernet devices are named eth0, eth1, eth2, etc. Each VAP which is created is also registered as a Linux network device. The value VAP can be either a prefix name of the Linux network device, or it can be the entire device name. For instance, specifying VAP as ath lets the Linux kernel add the network device as the next device with the prefix ath. Thus, the Linux kernel appends the proper number to the end to form the full device name, e.g., ath1 if ath0 already exists. However, the full device name can also be specified. For instance, VAP can also be ath2. In this case, the network device ath2 is registered, regardless of whether ath1 exists.

The Base Device is the underlying wireless network device name created when the driver is loaded. The MadWifi driver creates wifi0, wifi1, etc. as the underlying devices. By specifying the Base Device, the VAP is created with the Base Device as the parent device. The mode is the operating mode of the VAP. The operating mode of the VAP cannot be changed once it is created. In special cases, the operating mode of the VAP can be different from the operating mode of the underlying parent device. The first VAP which is created sets the operating mode of the underlying device. If the first VAP is deleted and a new VAP is created with a different operating mode than the original VAP, then the operating mode of the underlying device is changed to the new operating mode. The valid operating modes and their descriptions are given in Table 1.

I must admit I don´t really understand what a "virtual" AP is and why a "Base device" is needed and exspecially what all this means for me... maybe I would save time and sweat by drilling holes and pulling a cable through my house...

[che-hai]

Perhaps your card/driver does not support WPA2. What driver are you using?

I'm sorry, I do not know how to get the version of the driver (is there any command that I should know?). You refeer to madwifi or there are also another drivers implied in the stack? Sorry but I did not faced such deep problems.

The hardware that I got is working ok with wpa2-psk(aes) on another operating system.

[wieman01]

I found out that wifi0 is added by the madwifi driver:

I must admit I don´t really understand what a "virtual" AP is and why a "Base device" is needed and exspecially what all this means for me... maybe I would save time and sweat by drilling holes and pulling a cable through my house...
Perhaps "wifi0" does not play a role after all. That said, I do remember that another guy I helped a while ago mentioned that his device did not support WPA2, only WPA-TKIP. Can you try to connect to an WPA-TKIP secured network? Just change your router's settings and give it a go.

[wieman01]

I'm sorry, I do not know how to get the version of the driver (is there any command that I should know?). You refeer to madwifi or there are also another drivers implied in the stack? Sorry but I did not faced such deep problems.

The hardware that I got is working ok with wpa2-psk(aes) on another operating system.
Maybe the current Linux driver does not support WPA2... I am not entirely sure. See previous post.

Can you at least connect to WPA-TKIP secured networks?

[che-hai]

Maybe the current Linux driver does not support WPA2... I am not entirely sure. See previous post.

Can you at least connect to WPA-TKIP secured networks?

Yes, I am able to connect using wpa-tkip. I think the driver supports wpa2 since the error that I get "Unsupported AES-WRAP len 76" (please see the previous post) is returned after the protocol startup is established between ath0 and router and two keys - 2 out of 4- (or something like that - I need to look over the output again) were already exchanged. In fact the error message itself denotes that the driver supports AES (AES is specific to WPA2, isn't it?) - . When disconnected state is entered (please see the previos post indicating the output) it is stated that a 4 way handshake protocol is implied - so there is a known protocol.
All I know is that the linux-restricted-modules-2.6.15-28-386 is installed, I think that this comprise the madwifi but I do not know any command to list the driver's version.

[Kizilbas]

Wow, very nice tutorial thanks.

[elmar]

Perhaps "wifi0" does not play a role after all. That said, I do remember that another guy I helped a while ago mentioned that his device did not support WPA2, only WPA-TKIP. Can you try to connect to an WPA-TKIP secured network? Just change your router's settings and give it a go.

I´m using WPA-TKIP (see my interfaces file). Nonetheless ist does´nt work.

Elmar

[Sporkmaster]

This isn't working for me. Every time I put in my interfaces file, the computer lags to a Windows degree and the net don't work

non hidden SSID
WPA TKIP security
Yes, the PSK is hex
It's a Linksys wireless G router... I hate said router anyway

auto eth0
iface eth0 inet static
# wireless-* options are implemented by the wireless-tools package
address 192.168.1.103
netmask 255.255.255.0
network 192.168.1.1
broadcast 192.168.1.255
gateway 192.168.1.1
dns-nameservers 192.168.1.1
wpa-driver wext
wpa-conf managed
wpa-ssid ****************************
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk ****************************

This is what iwconfig turned up
eth0 IEEE 802.11g ESSID:"NETGEAR"
Mode:Managed Frequency:2.462 GHz Access Point: 00:0F:B5:5F:C3:C6
Bit Rate:54 Mb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr: off Fragment thr: off
Power Management: off
Link Quality=61/100 Signal level=-64 dBm Noise level=-79 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries 0 Invalid misc:0 Missed beacon:18

Also, I installed Network-Manager-Gnome but it doesn't appear in my sys tray

[wieman01]

This isn't working for me. Every time I put in my interfaces file, the computer lags to a Windows degree and the net don't work

non hidden SSID
WPA TKIP security
Yes, the PSK is hex
It's a Linksys wireless G router... I hate said router anyway

Also, I installed Network-Manager-Gnome but it doesn't appear in my sys tray
Can you try a...

iwlist scan
...and post the results?

Also what card are you using? Is "eth0" the right interface? "Normally" this refers to your Ethernet connection and not wireless. But that could be different on your PC.

[fdhenard]

WPA is not working. It's an old pc that I'm trying to get Ubuntu to work on. I'm a newbie. Before I found this how-to, I was able to get internet working by turning off WPA on my router. However, I would prefer to use WPA encryption.

Adapter: Linksys WUSB11 ver 2.6 - pretty old - will it work with WPA?
I'm surprised (and happy) that Ubuntu recognized my adapter without installing drivers. Windows XP didn't do that!

Router: Fairly new Linksys W54???G - I'm not at home at the moment. I can update later if needed.

#uname -a

Linux fdhenard-desktop 2.6.15-26-386 #1 PREEMPT Thu Aug 3 02:52:00 UTC 2006 i586 GNU/Linux


# ifconfig -a

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:13 errors:0 dropped:0 overruns:0 frame:0
TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:672 (672.0 b) TX bytes:672 (672.0 b)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

wlan0 Link encap:Ethernet HWaddr 00:06:25:26:BB:D9
UP BROADCAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)


# route -n

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface

#iwconfig

lo no wireless extensions.

wlan0 IEEE 802.11-DS ESSID:"okuwlan" Nickname:"okuwlan"
Mode:Managed Frequency:2.457 GHz Access Point: Not-Associated
Bit Rate:11 Mb/s Tx-Power=15 dBm
Retry limit:8 RTS thr=1536 B Fragment thr=1536 B
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

sit0 no wireless extensions.


# ifconfig

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:13 errors:0 dropped:0 overruns:0 frame:0
TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:672 (672.0 b) TX bytes:672 (672.0 b)

wlan0 Link encap:Ethernet HWaddr 00:06:25:26:BB:D9
UP BROADCAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)


#lsmod

Module Size Used by
ipv6 265728 6
rfcomm 40216 0
l2cap 26244 5 rfcomm
bluetooth 49892 4 rfcomm,l2cap
ppdev 9220 0
cpufreq_userspace 4696 0
cpufreq_stats 5636 0
freq_table 4740 1 cpufreq_stats
cpufreq_powersave 1920 0
cpufreq_ondemand 6428 0
cpufreq_conservative 7332 0
video 16260 0
tc1100_wmi 6916 0
sony_acpi 5644 0
pcc_acpi 12416 0
hotkey 11556 0
dev_acpi 11140 0
container 4608 0
button 6672 0
acpi_sbs 19980 0
battery 9988 1 acpi_sbs
i2c_acpi_ec 5120 1 acpi_sbs
ac 5252 1 acpi_sbs
af_packet 22920 6
dm_mod 58936 1
md_mod 72532 0
lp 11844 0
at76c503_rfmd 5260 0
at76c503 88544 1 at76c503_rfmd
at76_usbdfu 5764 1 at76c503
tsdev 8000 0
snd_cmipci 34336 1
gameport 15496 1 snd_cmipci
snd_pcm_oss 53664 0
snd_mixer_oss 18688 1 snd_pcm_oss
snd_pcm 89864 2 snd_cmipci,snd_pcm_oss
snd_page_alloc 10632 1 snd_pcm
snd_opl3_lib 10624 1 snd_cmipci
snd_timer 25220 2 snd_pcm,snd_opl3_lib
snd_hwdep 9376 1 snd_opl3_lib
snd_mpu401_uart 7808 1 snd_cmipci
snd_rawmidi 25504 1 snd_mpu401_uart
snd_seq_device 8716 2 snd_opl3_lib,snd_rawmidi
floppy 62148 0
parport_pc 35780 1
parport 36296 3 ppdev,lp,parport_pc
snd 55268 12 snd_cmipci,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_o pl3_lib,snd_timer,snd_hwdep,snd_mpu401_uart,snd_ra wmidi,snd_seq_device
pcspkr 2180 0
i2c_via 4484 0
i2c_algo_bit 9608 1 i2c_via
i2c_core 21904 2 i2c_acpi_ec,i2c_algo_bit
soundcore 10208 1 snd
psmouse 36100 0
serio_raw 7300 0
rtc 13492 0
shpchp 45632 0
pci_hotplug 29236 1 shpchp
via_agp 9856 1
agpgart 34888 1 via_agp
evdev 9856 1
ext3 135688 1
jbd 58772 1 ext3
ide_generic 1536 0
uhci_hcd 33680 0
usbcore 130692 5 at76c503_rfmd,at76c503,at76_usbdfu,uhci_hcd
ide_cd 33028 0
cdrom 38560 1 ide_cd
ide_disk 17664 3
via82cxxx 9988 0 [permanent]
generic 5124 0
thermal 13576 0
processor 23360 1 thermal
fan 4868 0
capability 5000 0
commoncap 7296 1 capability
vga16fb 13704 1
vgastate 10368 1 vga16fb
fbcon 42784 72
tileblit 2816 1 fbcon
font 8320 1 fbcon
bitblit 6272 1 fbcon
softcursor 2304 1 bitblit


# iwlist scan

lo Interface doesn't support scanning.

wlan0 Failed to read scan data : Resource temporarily unavailable

sit0 Interface doesn't support scanning.


# cat /etc/network/interfaces

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp

auto eth2
iface eth2 inet dhcp

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid ballparkfh
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk 523ee409XXXXREMOVEDXXXXXXXX4817e764721903286261580 c

# cat /etc/modprobe.d/ndiswrapper

cat: /etc/modprobe.d/ndiswrapper: No such file or directory

# cat /etc/resolve.conf

search myhome.westell.com
nameserver 192.168.1.1

[GoBieN]

Is there a place somewhere where I would need to specify the speed of the wireless network ?

iwconfig says i'm at 11mb/s while my router and onboard adapter (pavilion dv6000, broadcom 43xx) are both capable of 54mb/s ?



stan@laptop-ubuntu:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

eth1 IEEE 802.11b/g ESSID:"dd-wrt" Nickname:"Broadcom 4311"
Mode:Managed Frequency=2.437 GHz Access Point: 00:40:10:10:00:03
Bit Rate=11 Mb/s Tx-Power=18 dBm
RTS thr:off Fragment thr:off
Link Quality=83/100 Signal level=-48 dBm Noise level=-71 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

stan@laptop-ubuntu:~$

stan@laptop-ubuntu:~$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp
wireless-essid dd-wrt
wpa-driver wext
wpa-conf /etc/wpa_supplicant.conf
stan@laptop-ubuntu:~$

stan@laptop-ubuntu:~$ sudo cat /etc/wpa_supplicant.conf
Password:
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
network={
ssid="dd-wrt"
scan_ssid=1
psk="suXXXXXag"
}
stan@laptop-ubuntu:~$

Using native linux driver (the cutter thing) with firmware downloaded from internet by cutter script.

Please tell me how to get on 54mb/s ! Thank you

[fdhenard]

deleted

[wieman01]

WPA is not working. It's an old pc that I'm trying to get Ubuntu to work on. I'm a newbie. Before I found this how-to, I was able to get internet working by turning off WPA on my router. However, I would prefer to use WPA encryption.

Adapter: Linksys WUSB11 ver 2.6 - pretty old - will it work with WPA?
I'm surprised (and happy) that Ubuntu recognized my adapter without installing drivers. Windows XP didn't do that!
Depending on the (Windows) driver that you use, it either supports WPA or it doesn't. Can you download the latest driver from Linksys' website and deploy it? I doubt it will support WPA2, but WPA1 should not be a big issue.

[wieman01]

Is there a place somewhere where I would need to specify the speed of the wireless network ?

iwconfig says i'm at 11mb/s while my router and onboard adapter (pavilion dv6000, broadcom 43xx) are both capable of 54mb/s ?

Using native linux driver (the cutter thing) with firmware downloaded from internet by cutter script.

Please tell me how to get on 54mb/s ! Thank you
This is not quite the place to ask that question, but you could try:

iwconfig --help
This will list all the options for "iwconfig". Nonetheless here is a link to the "man" pages:

http://www.die.net/doc/linux/man/man8/iwconfig.8.html

[Staudie]

Wieman01,

Great guide, I'm not sure what I wold have done with out it. I do have one item that is giving me grief. I'm using a Netgear WG111T and it times out during boot. I followed "Post 2" to set up the script and set it to "S40". Could it be since this is a USB device I need to use a different timing? Once the system is up and running "sudo /etc/init.d/networking restart" works with out a hitch. Do you have any ideas? By the way I'm running Feisty.

Thanks in advance,
-Staudie

[wieman01]

Wieman01,

Great guide, I'm not sure what I wold have done with out it. I do have one item that is giving me grief. I'm using a Netgear WG111T and it times out during boot. I followed "Post 2" to set up the script and set it to "S40". Could it be since this is a USB device I need to use a different timing? Once the system is up and running "sudo /etc/init.d/networking restart" works with out a hitch. Do you have any ideas? By the way I'm running Feisty.

Thanks in advance,
-Staudie
A lot of other users have experienced the same problem (timeout) and one user proposed that this must be due to a bug which I cannot really explain.

As for the timing ("S40") I am using a USB device as well (Linksys wusb54g v4). The sequence has more to do with certain services that need to be initialized at certain stages while the system boots. "S40" seems appropriate.

If you want to shorten boot times and avoid a DHCP timeout, use Static IP instead which causes virtually no delay.

[gen_x]

Dude you are the wiseman! You rock man! :guitar: Literally 2 minutes and I'm on. Struggled form several hours.

Specs:
Acer 5670 Intel 3945ABG
Ubuntu Edy Eft

Note: Didn't have to install anything! Just follow this tutorial, it's so simple!

******interfaces*********

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid test
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <don't forget to generate your hex key>

******iwlist scan**********

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:00:00:00:00:00
ESSID:"test"
Protocol:IEEE 802.11bg
Mode:Master
Channel:6
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=96/100 Signal level=-30 dBm Noise level=-30 dBm
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Extra: Last beacon: 4ms ago

sit0 Interface doesn't support scanning.

*******iwconfig*******
lo no wireless extensions.

eth0 no wireless extensions.

eth1 IEEE 802.11g ESSID:"test"
Mode:Managed Frequency:2.437 GHz Access Point: 00:00:00:00:00:00
Bit Rate:54 Mb/s Tx-Power:15 dBm
Retry limit:15 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=96/100 Signal level=-31 dBm Noise level=-32 dBm
Rx invalid nwid:0 Rx invalid crypt:1 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:133 Missed beacon:0

sit0 no wireless extensions.


Again great how to! Many thanks! :)

[sefs]

Tell me where I am going wrong...

I had this previously working in edgy, but since moving to Feisty the old ndiswrapper would not compile and I had to go with there newest version. ver 1.42

WPA no longer works and have had to fall back to WEP.

I want to get WPA working again. I've followed the HOWTO as before.

my /etc/network/interfaces looks like



# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# This is a list of hotpluggable network interfaces.
# They will be activated automatically by the hotplug subsystem.
mapping hotplug
script grep
map wlan0

# The wireless network interface
iface wlan0 inet static

# General settings
#------------------------------
address 192.168.1.55
netmask 255.255.255.0
network 192.168.1.0
gateway 192.168.1.1
dns-nameservers 205.214.192.201 205.214.192.202 208.67.222.222 208.67.220.220 192.168.254.254

# WPA settings
#------------------------------
wpa-driver wext
wpa-ssid fshome
wpa-conf managed
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise AES
wpa-group AES
wpa-key-mgmt WPA-PSK
wpa-psk xxxx

auto wlan0


The errors i am getting when restarting the network (i have rebooted, shut right off and restarted) are



funkycold@funkycold:~$ sudo /etc/init.d/networking restart
* Reconfiguring network interfaces...
wpa_supplicant: cannot read contents of managed
run-parts: /etc/network/if-down.d/wpasupplicant exited with return code 1
wpa_supplicant: cannot read contents of managed
run-parts: /etc/network/if-post-down.d/wpasupplicant exited with return code 1
wpa_supplicant: cannot read contents of managed
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1
wpa_supplicant: cannot read contents of managed
run-parts: /etc/network/if-up.d/wpasupplicant exited with return code 1
[ OK ]



what can i do to rectify.

Thanks.

[wieman01]

Sefs,

The settings for WPA1 are...

wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
And WPA2...

wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
Your code does not look right.

wpa-ap-scan 2
...suggests that you have your ESSID broadcast disabled. Is that correct?

[corax]

Hi all !

I have exactly the same problem ... I have upgraded (reinstalled) to feisty and I can't connect to WPA (WEP works fine). I have two cards one intel ipw2200 and a netgear wg511T (atheros with madwifi) both of them worked with WPA under edgy. None of them works with WPA now :) I have the same /etc/network/interfaces file (backed up) and I have no idea what is the problem :(

Can someone help me ? :)

THX

------------------------------------------------------
EDIT:

sorry it happens me all time ... :( I post a question after 2 hours of searching then I find the solution myself 10 minutes later :(

so

my /etc/network/interfaces was :


iface lo inet loopback
auto lo

#iface eth0 inet dhcp
#auto eth0

iface eth1 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid sssssiiiiiddddd
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk keykeykey............
auto eth1

and this above said when i entered

sudo ifup eth1


wpa_supplicant: cannot read contents of managed
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1
There is already a pid file /var/run/dhclient.eth1.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
....

and I was unable to connect ...

The solution was to delete the line "wpa-conf managed" from /etc/network interfaces

so it is like


iface lo inet loopback
auto lo

#iface eth0 inet dhcp
#auto eth0

iface eth1 inet dhcp
wpa-driver wext
wpa-ssid sssssiiiiiddddd
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk keykeykey............
auto eth1

It works now as I see ... Can someone tell me what is "wpa-conf managed" for ?

Thanks !

[wieman01]

It works now as I see ... Can someone tell me what is "wpa-conf managed" for ?

Thanks !
I could not find any documentation on "wpa-conf". I will remove this line from my script as it does not appear to serve any purpose any longer. Thanks for highlighting it.

[sefs]

Hi again.

Weeima01 I want to confirm that WPA1 with AES works. Here is why.

I have a wrt54gl. the ssid broadcast is set to enabled. But I am as confused as you as to why wpa-ap-scan 2 works and wpa-ap-scan 1 does not ... when wpa-ap-scan 1 I cannot connect to the network but when I go wpa-ap-scan 2 I am able to connect. This is very very weird.

I also want to know what "wpa-conf managed" is for. I followed corax's suggestion and commented it out. And what would you know...after restarting the network ... I was back in business again using WPA-Personal which I assume is WPA1 and with AES encryption.

My /etc/network/interfaces now looks like this...


# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# This is a list of hotpluggable network interfaces.
# They will be activated automatically by the hotplug subsystem.
mapping hotplug
script grep
map wlan0

# The wireless network interface
iface wlan0 inet static

# General settings
#------------------------------
address 192.168.1.55
netmask 255.255.255.0
network 192.168.1.0
gateway 192.168.1.1
dns-nameservers 205.214.192.201 205.214.192.202 208.67.222.222 208.67.220.220 192.168.254.254

# WPA settings
#------------------------------
wpa-driver wext
wpa-ssid xxxxx
#wpa-conf managed
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise AES
wpa-group AES
wpa-key-mgmt WPA-PSK
wpa-psk xxxxxxxxxxxxxxxxxxx

auto wlan0


Can you shed some light on why it would wpa-ap-scan 2 works with ssid broadcast enabled and not wpa-ap-scan 1.

Can you also let us know whats this wpa-conf.

and how can I specify infrastructure mode.

While researching wpa_supplicant I saw ppl using the wpa-conf line to specify the path to /etc/wpa_supplicant.conf.

At one point i went this rout and made better progress where it detected the network but could not connect.

Thanks very much.


UPDATE:

I've tried WPA2 Personal on the WRT54GL with these settings ...



# WPA settings
#------------------------------
wpa-driver wext
wpa-ssid xxxxx
#wpa-conf managed
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk xxxxxx


now the wpa-ap-scan works when both set to 1 or 2.

So now I'm able to use WPA2 with AES.

Discussions on WPA+AES and WPA2+AES ect... it sounds rather confusing (AES was apprently added to WPA1 as an afterthought?)
http://www.dslreports.com/forum/remark,12691890
http://forums.practicallynetworked.com/showthread.php?t=7119

[wieman01]

Hi Sef:

I will update my tutorial immediately and remove the line in question (wpa-conf). Not sure why your version of wpa-supplicant works the way it does, however, it used to be the case that wpa-ap-scan would control the scanning logic of your wireless card (ESSID broadcast enabled vs. disabled).

Again, I'll remove the line from my scripts. I have not found any documentation on it so far.

[wieman01]

I have updated the HOWTO. Really appreciated your feedback as I have not tried Feisty yet. Still on Dapper which I plan to change soon. :-) So I really depend on your input. Sorry I have not found anything on the "wpa-conf" issues yet, but I will check it out over the weekend or so.

[sefs]

Just in case you were wondering its the wpa-supplicant that comes with a default upgrade to feisty.


Hi Sef:

I will update my tutorial immediately and remove the line in question (wpa-conf). Not sure why your version of wpa-supplicant works the way it does, however, it used to be the case that wpa-ap-scan would control the scanning logic of your wireless card (ESSID broadcast enabled vs. disabled).

Again, I'll remove the line from my scripts. I have not found any documentation on it so far.

[wieman01]

Just in case you were wondering its the wpa-supplicant that comes with a default upgrade to feisty.
Cool. Got it. Hope things will work out for Feisty users from now on. Thanks for your help.

EDIT:
One more question: Why would Feisty users still requires this HOWTO at all? I thought Feisty comes with enhanced wireless support including the support for Static IP and WPA? Just curious... Does the standard install not work for you?

[corax]

Hi all !

I think this howto is great. You should update it sometimes like remove the wpa-conf thing ... I think it is much cleaner (you don't need an additional program) and more straight than the network manager. And you can't configure WPA in NM as much as here in /etc/network/interfaces. And the NM works about 90 % of all cases because you can't setup everything in GUI. (extreme cases like WPA1 + WPA2 (mixed) + hidden essid + RADIUS. I don't think you can do it with network manager).

This is my opinion :)

[mr_delphi]

it works !!!
Removed "managed"
and put 2 in wpa-ap-scan 2

another thing is that for my router, AES does not work, WPA personal =tkip here

thanks everybody here



Hi again.

Weeima01 I want to confirm that WPA1 with AES works. Here is why.

I have a wrt54gl. the ssid broadcast is set to enabled. But I am as confused as you as to why wpa-ap-scan 2 works and wpa-ap-scan 1 does not ... when wpa-ap-scan 1 I cannot connect to the network but when I go wpa-ap-scan 2 I am able to connect. This is very very weird.

I also want to know what "wpa-conf managed" is for. I followed corax's suggestion and commented it out. And what would you know...after restarting the network ... I was back in business again using WPA-Personal which I assume is WPA1 and with AES encryption.

My /etc/network/interfaces now looks like this...


# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# This is a list of hotpluggable network interfaces.
# They will be activated automatically by the hotplug subsystem.
mapping hotplug
script grep
map wlan0

# The wireless network interface
iface wlan0 inet static

# General settings
#------------------------------
address 192.168.1.55
netmask 255.255.255.0
network 192.168.1.0
gateway 192.168.1.1
dns-nameservers 205.214.192.201 205.214.192.202 208.67.222.222 208.67.220.220 192.168.254.254

# WPA settings
#------------------------------
wpa-driver wext
wpa-ssid xxxxx
#wpa-conf managed
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise AES
wpa-group AES
wpa-key-mgmt WPA-PSK
wpa-psk xxxxxxxxxxxxxxxxxxx

auto wlan0


Can you shed some light on why it would wpa-ap-scan 2 works with ssid broadcast enabled and not wpa-ap-scan 1.

Can you also let us know whats this wpa-conf.

and how can I specify infrastructure mode.

While researching wpa_supplicant I saw ppl using the wpa-conf line to specify the path to /etc/wpa_supplicant.conf.

At one point i went this rout and made better progress where it detected the network but could not connect.

Thanks very much.


UPDATE:

I've tried WPA2 Personal on the WRT54GL with these settings ...



# WPA settings
#------------------------------
wpa-driver wext
wpa-ssid xxxxx
#wpa-conf managed
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk xxxxxx


now the wpa-ap-scan works when both set to 1 or 2.

So now I'm able to use WPA2 with AES.

Discussions on WPA+AES and WPA2+AES ect... it sounds rather confusing (AES was apprently added to WPA1 as an afterthought?)
http://www.dslreports.com/forum/remark,12691890
http://forums.practicallynetworked.com/showthread.php?t=7119

[sefs]

I wasn't aware of that. I will have to investigate that and see. I took a cursory glance at NM after upgrading to feisty immediately looking for the static IP support but I must have missed it so I removed it immediately to go back to what I knew was working (this tutorial). I'll have to reinstall NM to take a closer look.



Cool. Got it. Hope things will work out for Feisty users from now on. Thanks for your help.

EDIT:
One more question: Why would Feisty users still requires this HOWTO at all? I thought Feisty comes with enhanced wireless support including the support for Static IP and WPA? Just curious... Does the standard install not work for you?

[wieman01]

Hi all !

I think this howto is great. You should update it sometimes like remove the wpa-conf thing ... I think it is much cleaner (you don't need an additional program) and more straight than the network manager. And you can't configure WPA in NM as much as here in /etc/network/interfaces. And the NM works about 90 % of all cases because you can't setup everything in GUI. (extreme cases like WPA1 + WPA2 (mixed) + hidden essid + RADIUS. I don't think you can do it with network manager).

This is my opinion :)
If you have suggestions as to how we can improve this thread, you are welcome to post them here. It will be nice to keep this thread alive. I have removed that "wpa-conf" stanza in the meantime.

[wieman01]

Well, I have just tried Feisty Kubuntu (actually I am writing this while running the LiveCD) and I must say it is beautiful. More than that I had no problems whatsoever connecting to my local wireless network (Static IP, ESSID broadcast disabled) without installing any additional software packages. I am impressed... Having said that the new version of Ubuntu pretty much renders this thread unnecessary. Eventually!

EDIT:
On a Sony Vaio with Intel IPW2200 B/G that is.

[mabelrxu]

For WPA1 my example would look like this:

I have never bothered to setup wpa_supplicant outside of "interfaces" because I don't think it is nice. So I cannot give you any advice there. However, I am having a similar issue as you whereby I need to initialize my wireless network at startup, then immediately bring it down & restart it. For some reason the network would remain disconnected if I did not restart it.

So my advice is to follow post #2 and restart the network during the boot process. Not sure if this is a bug but I have not found a solution ever since.

actually, here's how you create your /etc/wpa_supplicant.conf file:



wpa_passphrase <network essid> <network password>


then some text comes up that's like


network={
ssid="ssid"
#psk="password"
psk=q45kl3j45;l3kj45h345lkj34h5;l2k3j45k3j4l5;h34j 5
}


so, you copy that psk, then do


sudo gedit /etc/wpa_supplicant.conf

and type (copy & paste) this:


ctrl_interface=/var/run/wpa_supplicant
ap_scan=1

network={
ssid="yourNetworkSsid"
scan_ssid=1
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP
group=CCMP
psk=blah-;kljl23j4h2l3kj4h2l34h23lk4j23hl4h-blah
}


i have wpa2 with ipw2200 and wext, so you might need to change ap_scan, proto, pairwise, and group to match your network settings ... hope this helps!

[KiwiPete]

Hi there

I'm running Xubuntu 6.10 and need help getting my wireless PCI card recognised.
I'm using a LinkSys Wireless-G router.

Read your original post and followed all the instructions, but no joy.
Here are the results for running the various terminal commands you suggested.
-----------------------------------------------------------
uname -a
Linux ubuntu 2.6.17-11-generic #2 SMP Thu Feb 1 19:52:28 UTC 2007 i686 GNU/Linux

ifconfig -a
ath0 Link encap:Ethernet HWaddr 00:19:E0:83:24:D5
inet6 addr: fe80::219:e0ff:fe83:24d5/64 Scope:LinkOn,
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

eth0 Link encap:Ethernet HWaddr 00:05:1C:19:DE:45
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:7871 errors:0 dropped:0 overruns:0 frame:0
TX packets:7579 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4741783 (4.5 MiB) TX bytes:672194 (656.4 KiB)
Interrupt:3 Base address:0xc00

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:306 errors:0 dropped:0 overruns:0 frame:0
TX packets:306 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:15300 (14.9 KiB) TX bytes:15300 (14.9 KiB)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

wifi0 Link encap:UNSPEC HWaddr 00-19-E0-83-24-D5-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3288 errors:0 dropped:0 overruns:0 frame:33430
TX packets:7692 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:199
RX bytes:289523 (282.7 KiB) TX bytes:353932 (345.6 KiB)
Interrupt:11 Memory:d0920000-d0930000

route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface

iwconfig
lo no wireless extensions.

wifi0 no wireless extensions.

ath0 IEEE 802.11g ESSID:""
Mode:Managed Frequency:2.467 GHz Access Point: Not-Associated
Bit Rate:0 kb/s Tx-Power:18 dBm Sensitivity=0/3
Retry:off RTS thr:off Fragment thr:off
Power Management:off
Link Quality=0/94 Signal level=-95 dBm Noise level=-95 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

eth0 no wireless extensions.

sit0 no wireless extensions.

ifconfig
ath0 Link encap:Ethernet HWaddr 00:19:E0:83:24:D5
inet6 addr: fe80::219:e0ff:fe83:24d5/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:696 errors:0 dropped:0 overruns:0 frame:0
TX packets:696 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:34800 (33.9 KiB) TX bytes:34800 (33.9 KiB)

wifi0 Link encap:UNSPEC HWaddr 00-19-E0-83-24-D5-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3288 errors:0 dropped:0 overruns:0 frame:33430
TX packets:8680 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:199
RX bytes:289523 (282.7 KiB) TX bytes:399380 (390.0 KiB)
Interrupt:11 Memory:d0920000-d0930000

lsmod
Module Size Used by
ipv6 272288 8
apm 23280 1
cpufreq_userspace 5408 0
cpufreq_stats 7744 0
freq_table 6048 1 cpufreq_stats
cpufreq_powersave 2944 0
cpufreq_ondemand 8876 0
cpufreq_conservative 8712 0
nls_iso8859_1 5248 1
nls_cp437 6912 1
vfat 14720 1
fat 56348 1 vfat
lp 12964 0
af_packet 24584 4
snd_ens1371 28704 1
gameport 17160 1 snd_ens1371
snd_rawmidi 27264 1 snd_ens1371
snd_seq_device 9868 1 snd_rawmidi
snd_ac97_codec 97696 1 snd_ens1371
snd_ac97_bus 3456 1 snd_ac97_codec
snd_pcm_oss 47360 0
snd_mixer_oss 19584 1 snd_pcm_oss
snd_pcm 84612 3 snd_ens1371,snd_ac97_codec,snd_pcm_oss
snd_timer 25348 1 snd_pcm
tsdev 9152 0
parport_pc 37796 1
parport 39496 2 lp,parport_pc
snd 58372 10 snd_ens1371,snd_rawmidi,snd_seq_device,snd_ac97_co dec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
soundcore 11232 1 snd
floppy 63044 0
i2c_i810 6276 0
snd_page_alloc 11400 1 snd_pcm
serio_raw 8452 0
8139cp 24832 0
8139too 29056 0
mii 6912 2 8139cp,8139too
evdev 11392 1
wlan_scan_sta 15744 1
psmouse 41352 0
i2c_algo_bit 10376 1 i2c_i810
ath_pci 100000 0
ath_rate_sample 16512 1 ath_pci
wlan 207708 4 wlan_scan_sta,ath_pci,ath_rate_sample
ath_hal 192976 3 ath_pci,ath_rate_sample
i2c_core 23424 1 i2c_algo_bit
intel_agp 26012 1
agpgart 34888 2 intel_agp
hw_random 7320 0
pcspkr 4352 0
shpchp 42144 0
pci_hotplug 32828 1 shpchp
ext3 142856 1
jbd 62228 1 ext3
uhci_hcd 24968 0
ide_generic 2432 0
usbcore 134912 2 uhci_hcd
ide_cd 33696 0
cdrom 38944 1 ide_cd
ide_disk 18560 4
piix 11780 1
generic 6276 0
processor 31560 0
fbcon 41504 0
tileblit 3840 1 fbcon
font 9344 1 fbcon
bitblit 7168 1 fbcon
softcursor 3328 1 bitblit
vesafb 9244 0
capability 5896 0
commoncap 8704 1 capability

iwlist scan
lo Interface doesn't support scanning.
wifi0 Interface doesn't support scanning.
ath0 No scan results
eth0 Interface doesn't support scanning.
sit0 Interface doesn't support scanning.

cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

auto ath0
iface ath0 inet dhcp
wpa-driver madwifi
wpa-essid linksys
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk 8d796ee354033e76a823bbab3996249c1e4e9c0af571a252de aec99fff1b537d

cat /etc/modprobe.d/ndiswrapper
cat: /etc/modprobe.d/ndiswrapper: No such file or directory

cat /etc/resolv.conf
nameserver 203.96.152.4
nameserver 203.96.152.12
-----------------------------------------------------------
Any suggestions on what I should try next?
Thanks
KiwiPete

[wieman01]

If I were you, I'd to connect up to unsecure networks first. As you have said, your card does not seem to work, therefore this thread won't help you much.

Sorry I cannot say more, but this thread is meant for wireless security rather than hardware problems. I will try to help you though, if you send me a link by PM.

[mills]

maybe i should have come here first

http://ubuntuforums.org/showthread.php?p=2517527#post2517527

](*,)

[gamerteck]

I can confirm that removing wpa-conf managed fixed my LEAP authentication issue.
It worked before, in 6.10, I upgrade to 7.04


My interface config for WPA on eth1 looked as so:


auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid <something>
wpa-eap LEAP
wpa-key-mgmt IEEE8021X
wpa-identity <user>
wpa-password <password>



When I restarted networking I would gett the same error:


wpa_supplicant: cannot read contents of managed
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1
There is already a pid file /var/run/dhclient.eth1.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/


Removed the wpa-conf manager from my interfaces WPA config paramaters and it worked like a charm...
Thanks corax for squashing this issue! :guitar:

[chevkoch]

Some users reported (including myself) that the network has to be restarted every time after startup... Apparently this is a bug.
...quote from post #2
Why is this bug still there in Feisty? It's been two new releases since then!!!! Sometimes I doubt open source works.

[wieman01]

...quote from post #2
Why is this bug still there in Feisty? It's been two new releases since then!!!! Sometimes I doubt open source works.
No idea... I have not reported anything on launchpad, maybe I should do that.

EDIT:
This has nothing to do with Open Source though...

[chevkoch]

No idea... I have not reported anything on launchpad, maybe I should do that.


yeah you should do it

[sdjkfhk123j4h2jk]

I agree with removing "wpa-conf managed" to make it work. From the man page, the wpa-conf option is for choosing an wpasupplicant.conf file, so if you don't have a file called "managed" it will give an error.

[nab]

Hi,
I'm having problems with my wlan ;-(

Yesterday I switched from dapper to feisty. According to this howto I installed and configured my wlan and everything worked fine.

After rebooting I can't connect anymore to the wlan. The Network-Manager I see only LAN and manual configuratio no wlan.

My wlan card is an IPW 2200.
In the Network Administration Tool wlan is switched to roaming.

with iwconfig I get:


eth1 IEEE 802.11g ESSID:"GDP"
Mode:Managed Frequency:2.462 GHz Access Point: 00:03:C9:B3:13:75
Bit Rate:54 Mb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=92/100 Signal level=-35 dBm Noise level=-85 dBm
Rx invalid nwid:0 Rx invalid crypt:128 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


with iwlist scan I get:

Cell 02 - Address: 00:03:C9:B3:13:75
ESSID:"GDP"
Protocol:IEEE 802.11bg
Mode:Master
Channel:11
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=93/100 Signal level=-34 dBm
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
Extra: Last beacon: 1428ms ago


My /etc/network/interfaces looks like:



auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-ssid GDP
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk ####...###


on sudo /etc/init.d/networking restart I get:


* Reconfiguring network interfaces... There is already a pid file /var/run/dhclient.eth0.pid with pid 8225
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:0f:b0:57:18:25
Sending on LPF/eth0/00:0f:b0:57:18:25
Sending on Socket/fallback
DHCPRELEASE on eth0 to 192.168.2.1 port 67
There is already a pid file /var/run/dhclient.eth1.pid with pid 8250
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:0e:35:bd:b2:b7
Sending on LPF/eth1/00:0e:35:bd:b2:b7
Sending on Socket/fallback
DHCPRELEASE on eth1 to 192.168.2.1 port 67
There is already a pid file /var/run/dhclient.eth0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:0f:b0:57:18:25
Sending on LPF/eth0/00:0f:b0:57:18:25
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPOFFER from 192.168.2.1
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 192.168.2.1
bound to 192.168.2.32 -- renewal in 138107 seconds.
There is already a pid file /var/run/dhclient.eth1.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:0e:35:bd:b2:b7
Sending on LPF/eth1/00:0e:35:bd:b2:b7
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
DHCPOFFER from 192.168.2.1
DHCPREQUEST on eth1 to 255.255.255.255 port 67
DHCPACK from 192.168.2.1
bound to 192.168.2.33 -- renewal in 130447 seconds.
RTNETLINK answers: File exists
run-parts: /etc/network/if-up.d/avahi-autoipd exited with return code 2
eth2: ERROR while getting interface flags: No such device
There is already a pid file /var/run/dhclient.eth2.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

SIOCSIFADDR: No such device
eth2: ERROR while getting interface flags: No such device
eth2: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up eth2.
ath0: ERROR while getting interface flags: No such device
There is already a pid file /var/run/dhclient.ath0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

SIOCSIFADDR: No such device
ath0: ERROR while getting interface flags: No such device
ath0: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up ath0.
wlan0: ERROR while getting interface flags: No such device
There is already a pid file /var/run/dhclient.wlan0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

SIOCSIFADDR: No such device
wlan0: ERROR while getting interface flags: No such device
wlan0: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up wlan0.


Well ...
What can I do to get my wlan working?

Any help or link is welcome!

TIA
Nikolaus

[wieman01]

Hi,
I'm having problems with my wlan ;-(

Yesterday I switched from dapper to feisty. According to this howto I installed and configured my wlan and everything worked fine.

After rebooting I can't connect anymore to the wlan. The Network-Manager I see only LAN and manual configuratio no wlan.
Well, that"s what I have mentioned under "Common stumbling blocks"... You cannot manually configure your wireless network using WPA and have NetworkManager running at the same time. Surprises me it did work after upgrading to Feisty. Weird.

Have you got Firestarter installed? What is the result of:

route

[imekon]

I tried the following with my D-Link DWL-G650 PCMCIA card:



auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
# wpa-conf managed
wpa-ssid <your_essid>
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <your_wpa_psk>


it worked once I rebooted, and restarted the network with /etc/init.d/networking/restart. :)

This morning, it no longer works! :confused:

DHCP tries to get and address continuously then gives up.

The card flashed both lights continuously when it worked - when it doesn't work they flash alternately as they did this morning. It's almost as if the card hasn't been configured right.

(This is on Ubuntu desktop 7.04)

[wieman01]

I tried the following with my D-Link DWL-G650 PCMCIA card:

This morning, it no longer works! :confused:

DHCP tries to get and address continuously then gives up.

The card flashed both lights continuously when it worked - when it doesn't work they flash alternately as they did this morning. It's almost as if the card hasn't been configured right.

(This is on Ubuntu desktop 7.04)
Please try to disable all security settings and connect to an unsecured network, just to see if card cards works fine. When you scan for your network ("iwlist scan") do you get any results?

[imekon]

Well it did connect last night, now today it doesn't. I haven't changed any settings either end, so this is a bit strange?

[wieman01]

Well it did connect last night, now today it doesn't. I haven't changed any settings either end, so this is a bit strange?
Definitely is. Does restarting the network right after restarting your computer do any good? Does scanning yield any results? Odd...

[nab]

Hi wieman01,

I haven't installed any firewall, because I'm sitting behind a router.

with route I get:


Kernel IP Routentabelle
Ziel Router Genmask Flags Metric Ref Use Iface
172.16.145.0 * 255.255.255.0 U 0 0 0 vmnet8
192.168.2.0 * 255.255.255.0 U 0 0 0 eth0
192.168.252.0 * 255.255.255.0 U 0 0 0 vmnet1
link-local * 255.255.0.0 U 0 0 0 eth1
link-local * 255.255.0.0 U 1000 0 0 eth0
default 192.168.2.1 0.0.0.0 UG 0 0 0 eth0
default * 0.0.0.0 U 1000 0 0 eth1


Well, I'm not sure I understand you right (being non-native in English)

I didn't configure my wlan card in Network Administration Tool. The setting there is roaming. I never changed that.

What I don't understand is that I see the wlan-router with iwconfig and iwlist scan, but that I don't have the menu point wlan in nm-applet listed (There are only the menu points: LAN and "manual configuration", which brings me to the Network Administration Tool.)

On the first installation the wlan-router was listed in the menu.

Repeating the installation steps -including restarting the network and rebooting didn't help me to connect with the wlan.

Well, I hope I was able to clarify what I did.

TIA,
Nikolaus

[wieman01]

Hi wieman01,

I haven't installed any firewall, because I'm sitting behind a router.

Well, I'm not sure I understand you right (being non-native in English)

Well, I hope I was able to clarify what I did.

TIA,
Nikolaus
No prob. :-)

I couldn't quite figure out what method you have used to connect to your wireless network... manually editing "/etc/network/interfaces" or using the Network-Manager applet?

Nevertheless "route" seems to suggest that you are connected. Please trying to ping your router and see if you get a response:

ping 192.168.2.1
And ensure that your Ethernet cable is not connected to your computer while you are attempting to connect via wireless. Feel free to PM me if there are any other problems.

[d3dtn01]

I upgrade to Feisty last week and it blew away my wireless card drivers. Having gone through the whole ndiswrapper process and such, I now have wireless working. However, I'm only able to connect to a neighbor's unprotected network, not my WPA protected network. I used this HowTO in the past (before the upgrade) and it worked great. This time, I can't seem to connect. Here's the output I get when I run
sudo /etc/init.d/networking restart:


* Reconfiguring network interfaces... wpa_supplicant: cannot read contents of managed
run-parts: /etc/network/if-down.d/wpasupplicant exited with return code 1
There is already a pid file /var/run/dhclient.wlan0.pid with pid 6789
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:14:a5:4f:36:1a
Sending on LPF/wlan0/00:14:a5:4f:36:1a
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 192.168.1.1 port 67
wpa_supplicant: cannot read contents of managed
run-parts: /etc/network/if-post-down.d/wpasupplicant exited with return code 1
RTNETLINK answers: No such process
There is already a pid file /var/run/dhclient.eth0.pid with pid 6857
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:14:22:9a:89:92
Sending on LPF/eth0/00:14:22:9a:89:92
Sending on Socket/fallback
DHCPRELEASE on eth0 to 192.168.1.1 port 67
wpa_supplicant: cannot read contents of managed
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1
There is already a pid file /var/run/dhclient.wlan0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:14:a5:4f:36:1a
Sending on LPF/wlan0/00:14:a5:4f:36:1a
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
DHCPOFFER from 192.168.1.1
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPACK from 192.168.1.1
bound to 192.168.1.142 -- renewal in 82167 seconds.
wpa_supplicant: cannot read contents of managed
run-parts: /etc/network/if-up.d/wpasupplicant exited with return code 1
There is already a pid file /var/run/dhclient.eth0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:14:22:9a:89:92
Sending on LPF/eth0/00:14:22:9a:89:92
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16
No DHCPOFFERS received.
No working leases in persistent database - sleeping.


What should I make of this?

[wieman01]

I upgrade to Feisty last week and it blew away my wireless card drivers. Having gone through the whole ndiswrapper process and such, I now have wireless working. However, I'm only able to connect to a neighbor's unprotected network, not my WPA protected network. I used this HowTO in the past (before the upgrade) and it worked great. This time, I can't seem to connect. Here's the output I get when I run
sudo /etc/init.d/networking restart:

What should I make of this?
Simply remove this line from your interfaces config files:

wpa-conf managed
Then restart the network or your computer.

[reauthor]

Hy guys!
First,I wish to thanks for this great HOWTO..it works perfectly for me on Feisty.
I have a laptop whit Intel wireless card 2200BG.For encryption I using WPA2 and radius server for authentication,shortly WPA2 AES Enterprise.
Like I said,thanks one more time.

[wieman01]

Hy guys!
First,I wish to thanks for this great HOWTO..it works perfectly for me on Feisty.
I have a laptop whit Intel wireless card 2200BG.For encryption I using WPA2 and radius server for authentication,shortly WPA2 AES Enterprise.
Like I said,thanks one more time.
Great stuff. Would you mind sharing your script with us so that I can update the HOWTO and change the status from "not tested" to "sample configuration"? Would be nice... Thanks.

[d3dtn01]

I followed wieman01's suggestion


Simply remove this line from your interfaces config files: "wpa-conf managed".

I saved the interfaces file then I rebooted. Still doesn't work. New suggestions?

[reauthor]

Great stuff. Would you mind sharing your script with us so that I can update the HOWTO and change the status from "not tested" to "sample configuration"? Would be nice... Thanks.

Yes,ofcourse,Iam glad I can help. Maybe I have a little confused network configuration but just point to eth1 interface.
Before I made some changes first I disabled roaming mode in System->Administration->Network for wireless interface
#My interfaces configuration.

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-ssid my_ssid
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-eap PEAP
wpa-key-mgmt WPA-EAP
wpa-identity my_username
wpa-password my_password

auto eth1:0
iface eth1:0 inet static
address 10.x.x.x
netmask 255.255.255.0

#my static routes
up /sbin/route add -net 10.x.x.x/24 gw 10.x.x.x dev eth1
down /sbin/route del -net 10.x.x.x/24 gw 10.x.x.x dev eth1

up /sbin/route add -net 10.x.x.x/24 gw 10.x.x.x dev eth1
down /sbin/route del -net 10.x.x.x/24 gw 10.0.x.x.x dev eth1

up /sbin/route add -net 10.x.x.x/24 gw 10.x.x.x dev eth1
down /sbin/route del -net 10.x.x.x/24 gw 10.x.x.x dev eth1

up /sbin/route add -net 10.x.x.x/24 gw 10.x.x.x dev eth1
down /sbin/route del -net 10.x.x.x/24 gw 10.x.x.x dev eth1

After I made this configuration I added few lines from tedrogers post (post #50)where I replaced wlano whit eth1.
echo 'ifdown eth1' >/etc/init.d/WlanDown
ln -s ../init.d/WlanDown /etc/rcS.d/S40WlanDown
chmod +x /etc/init.d/WlanDown


Sorry for my english,it isnt my native language.

[wieman01]

Yes,ofcourse,Iam glad I can help. Maybe I have a little confused network configuration but just point to eth1 interface.
Before I made some changes first I disabled roaming mode in System->Administration->Network for wireless interface

Sorry for my english,it isnt my native language.
Excellent, buddy. Thank you.

[wieman01]

I followed wieman01's suggestion

I saved the interfaces file then I rebooted. Still doesn't work. New suggestions?
Guess it's worth taking a look at you configuration once again. Could you post it? Also including the output after restarting the network. No idea yet what is going on.

[d3dtn01]

OK, here's the content of my interfaces file:


auto lo
iface lo inet loopback
iface eth0 inet dhcp

iface wlan0 inet dhcp
wpa-driver wext
# wpa-conf managed
wpa-ssid habibi
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk c1cc29f9151cedb15d292d1607e4aba74e8680cda61986f122 5702668b818873

auto eth0

When I restart my network, I get the following output:


* Reconfiguring network interfaces... RTNETLINK answers: No such process
There is already a pid file /var/run/dhclient.eth0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:14:22:9a:89:92
Sending on LPF/eth0/00:14:22:9a:89:92
Sending on Socket/fallback
DHCPRELEASE on eth0 to 192.168.1.1 port 67
There is already a pid file /var/run/dhclient.eth0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:14:22:9a:89:92
Sending on LPF/eth0/00:14:22:9a:89:92
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16
No DHCPOFFERS received.
No working leases in persistent database - sleeping.


See anything wrong here? Thanks for the help.

[reauthor]

OK, here's the content of my interfaces file:


auto lo
iface lo inet loopback
iface eth0 inet dhcp

iface wlan0 inet dhcp
wpa-driver wext
# wpa-conf managed
wpa-ssid habibi
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk c1cc29f9151cedb15d292d1607e4aba74e8680cda61986f122 5702668b818873

auto eth0

When I restart my network, I get the following output:


* Reconfiguring network interfaces... RTNETLINK answers: No such process
There is already a pid file /var/run/dhclient.eth0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:14:22:9a:89:92
Sending on LPF/eth0/00:14:22:9a:89:92
Sending on Socket/fallback
DHCPRELEASE on eth0 to 192.168.1.1 port 67
There is already a pid file /var/run/dhclient.eth0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:14:22:9a:89:92
Sending on LPF/eth0/00:14:22:9a:89:92
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16
No DHCPOFFERS received.
No working leases in persistent database - sleeping.


See anything wrong here? Thanks for the help.

Hy d3dtn01.

Did you unchecked roaming mode in network-manager(System->Adminstration->Network)
If you do so,can you please put your iwconfig output here.
Dont worry,we will try to make your wifi on:)

[GuruX]

Before upgrading to Feisty Fawn I had WPA running very nicely with this type of config. nm-applet was used to connect to different APs.

Inetfaces file


auto lo
iface lo inet loopback
;auto ath0
;iface ath0 inet dhcp
wpa-driver madwifi
wpa-conf /etc/wpa_supplicant.conf


iface ppp0 inet ppp
provider ppp0


I'm no expert, so I guess there is some junk in it.


And the wpa_supplicant.conf looked like this.



network={
ssid="My SSID"
proto=WPA
key_mgmt=WPA-PSK
#psk="my key in ascii"
psk=my key in hex
}

Worked really fine. I could connect to my own AP with WPA encryption, and to other WEP encrypted APs. But now after upgrading to Feisty, it doesn't work. I really haven't found out why.

[wieman01]

Before upgrading to Feisty Fawn I had WPA running very nicely with this type of config. nm-applet was used to connect to different APs.

Inetfaces file


auto lo
iface lo inet loopback
;auto ath0
;iface ath0 inet dhcp
wpa-driver madwifi
wpa-conf /etc/wpa_supplicant.conf


iface ppp0 inet ppp
provider ppp0


I'm no expert, so I guess there is some junk in it.


And the wpa_supplicant.conf looked like this.



network={
ssid="My SSID"
proto=WPA
key_mgmt=WPA-PSK
#psk="my key in ascii"
psk=my key in hex
}

Worked really fine. I could connect to my own AP with WPA encryption, and to other WEP encrypted APs. But now after upgrading to Feisty, it doesn't work. I really haven't found out why.
Try our approach then. I cannot give you advice. But I reckon you will find an answer here:

http://ubuntuforums.org/showthread.php?t=263136

[wieman01]

OK, here's the content of my interfaces file:


auto lo
iface lo inet loopback
iface eth0 inet dhcp

iface wlan0 inet dhcp
wpa-driver wext
# wpa-conf managed
wpa-ssid habibi
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk c1cc29f9151cedb15d292d1607e4aba74e8680cda61986f122 5702668b818873

auto eth0

When I restart my network, I get the following output:


* Reconfiguring network interfaces... RTNETLINK answers: No such process
There is already a pid file /var/run/dhclient.eth0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:14:22:9a:89:92
Sending on LPF/eth0/00:14:22:9a:89:92
Sending on Socket/fallback
DHCPRELEASE on eth0 to 192.168.1.1 port 67
There is already a pid file /var/run/dhclient.eth0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:14:22:9a:89:92
Sending on LPF/eth0/00:14:22:9a:89:92
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16
No DHCPOFFERS received.
No working leases in persistent database - sleeping.


See anything wrong here? Thanks for the help.
Looks to me as if you have not pulled your Ethernet cable. You cannot have a wireless and wired connection at the same time as far as I remember. Pull the plug and restart the network.

If this does not help, please follow Reauthor's suggestion.

[GuruX]

Try our approach then. I cannot give you advice. But I reckon you will find an answer here:

http://ubuntuforums.org/showthread.php?t=263136

Yeah, that's pretty much what I did last time. And tried again this time. But it didn't work.

Anyway, I came to the solution now. The problem was obviously patched madwifi drivers for aircrack-ng. I compiled and installed the unpatched madwifi, and the compiled wpa_supplicant towards the unpatched madwifi. And now my setup is working again. I'll try to install the patched drivers again, that might work.


edit:
Yeah that worked. So, if you want to run wpa with the patched madwifi drivers. The installation order must be this.
1. Compile/install madwifi
2. Compile/install wpa_supplicant (towards unpatched madwifi)
3. Compile/install patched madwifi

[Forgott3n]

Hello,

I am using the D-Link WDA-1320 card (Atheros) and it uses the restricted drivers (as said in Feisty).

I have followed the directions precisely but with no luck.

I also noticed with the d-link card I have ath0, eth2, and wlan0 (eth1 is my wired connection) So I added the static configuration to all of them.

I have removed NetworkManager and NetworkManager-Gnome, I have WPA_Supplicant, and I'm running Feisty Fawn 7.04


Any help would be greatly appreciated.


[Edit] Here's what I get when I restart, what iwconfig dumps, and what I have in /etc/networking/interfaces


justin@bullbox:~$ sudo /etc/init.d/networking restart
Password:
* Reconfiguring network interfaces... SIOCDELRT: No such process
eth1: ERROR while getting interface flags: No such device
There is already a pid file /var/run/dhclient.eth1.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
SIOCSIFADDR: No such device
eth1: ERROR while getting interface flags: No such device
eth1: ERROR while getting interface flags: No such device
wifi0: unknown hardware address type 801
Bind socket to interface: No such device
Failed to bring up eth1.
eth2: ERROR while getting interface flags: No such device
ioctl[SIOCSIWPMKSA]: No such device
ioctl[SIOCSIWMODE]: No such device
Could not configure driver to use managed mode
ioctl[SIOCGIFFLAGS]: No such device
Could not set interface 'eth2' UP
ioctl[SIOCGIWRANGE]: No such device
ioctl[IEEE80211_IOCTL_SETPARAM]: No such device
ioctl[SIOCSIWAP]: No such device
ioctl[SIOCGIFFLAGS]: No such device
Failed to initialize driver interface
wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1
SIOCSIFADDR: No such device
eth2: ERROR while getting interface flags: No such device
SIOCSIFNETMASK: No such device
eth2: ERROR while getting interface flags: No such device
Failed to bring up eth2.
ioctl[SIOCSIWPMKSA]: Invalid argument
ioctl[SIOCSIWMODE]: Invalid argument
Could not configure driver to use managed mode
ioctl[SIOCGIWRANGE]: Invalid argument
ioctl[IEEE80211_IOCTL_SETPARAM]: Invalid argument
ioctl[SIOCSIWAP]: Invalid argument
Failed to initialize driver interface
wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1
RTNETLINK answers: File exists
run-parts: /etc/network/if-up.d/avahi-autoipd exited with return code 2
wlan0: ERROR while getting interface flags: No such device
ioctl[SIOCSIWPMKSA]: No such device
ioctl[SIOCSIWMODE]: No such device
Could not configure driver to use managed mode
ioctl[SIOCGIFFLAGS]: No such device
Could not set interface 'wlan0' UP
ioctl[SIOCGIWRANGE]: No such device
ioctl[IEEE80211_IOCTL_SETPARAM]: No such device
ioctl[SIOCSIWAP]: No such device
ioctl[SIOCGIFFLAGS]: No such device
Failed to initialize driver interface
wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1
There is already a pid file /var/run/dhclient.wlan0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
SIOCSIFADDR: No such device
wlan0: ERROR while getting interface flags: No such device
wlan0: ERROR while getting interface flags: No such device
wifi0: unknown hardware address type 801
Bind socket to interface: No such device
Failed to bring up wlan0.
[ OK ]
justin@bullbox:~$


=======


justin@bullbox:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wifi0 no wireless extensions.

ath0 IEEE 802.11g ESSID:"" Nickname:""
Mode:Managed Channel:0 Access Point: Not-Associated
Bit Rate:0 kb/s Tx-Power:18 dBm Sensitivity=0/3
Retry:off RTS thr:off Fragment thr:off
Power Management:off
Link Quality=0/94 Signal level=-96 dBm Noise level=-96 dBm
Rx invalid nwid:11990 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

justin@bullbox:~$

=======


auto lo
iface lo inet loopback

auto eth1
iface eth1 inet dhcp

auto eth2
iface eth2 inet static
address 192.168.1.127
gateway 192.168.1.1
dns-nameservers 192.168.1.1
netmask 255.255.255.0
wpa-driver madwifi
wpa-ssid gray-network
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 9783db4dfeaf61f96982d0791f15534ea0d9d98d55267bdf2b a750501f98a80d

auto ath0
iface ath0 inet static
address 192.168.1.127
gateway 192.168.1.1
dns-nameservers 192.168.1.1
netmask 255.255.255.0
wpa-driver madwifi
wpa-ssid gray-network
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 9783db4dfeaf61f96982d0791f15534ea0d9d98d55267bdf2b a750501f98a80d

auto wifi0
iface wifi0 inet static
address 192.168.1.127
gateway 192.168.1.1
dns-nameservers 192.168.1.1
netmask 255.255.255.0
wpa-driver madwifi
wpa-ssid gray-network
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 9783db4dfeaf61f96982d0791f15534ea0d9d98d55267bdf2b a750501f98a80d

auto wlan0
iface wlan0 inet dhcp
wpa-driver madwifi
wpa-ssid gray-network
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 9783db4dfeaf61f96982d0791f15534ea0d9d98d55267bdf2b a750501f98a80d



Note: I added wifi0 into the mix because on first attempt I noticed that the restart was complaining about a wifi0.

[wieman01]

Hello,

I am using the D-Link WDA-1320 card (Atheros) and it uses the restricted drivers (as said in Feisty).

I have followed the directions precisely but with no luck.

I also noticed with the d-link card I have ath0, eth2, and wlan0 (eth1 is my wired connection) So I added the static configuration to all of them.

I have removed NetworkManager and NetworkManager-Gnome, I have WPA_Supplicant, and I'm running Feisty Fawn 7.04


Any help would be greatly appreciated.
Two quesiton before we proceed... Have you scanned for your network yet & does it yield any results?

iwlist scan
Second, have you been able to connect to unsecured networks yet? That is particularly important because I need to now if you card is working or not.

Lastly, some card do not support WPA2 (RSN-CCMP) but only WPA1 (WPA-TKIP). Please try both options.

[Forgott3n]

Two quesiton before we proceed... Have you scanned for your network yet & does it yield any results?

Second, have you been able to connect to unsecured networks yet? That is particularly important because I need to now if you card is working or not.

Lastly, some card do not support WPA2 (RSN-CCMP) but only WPA1 (WPA-TKIP). Please try both options.


Ahh yes, forgot to mention. I was able to connect to my secured AP and unsecured APs via NetworkManager prior to attempting to make my system static. Here is the iwlist scan


justin@bullbox:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wifi0 Interface doesn't support scanning.

ath0 Scan completed :
Cell 01 - Address: 00:40:10:10:00:03
ESSID:"gray-network"
Mode:Master
Frequency:2.462 GHz (Channel 11)
Quality=31/94 Signal level=-64 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
Cell 02 - Address: 00:13:46:87:0F:74
ESSID:"default"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=1/94 Signal level=-94 dBm Noise level=-95 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:ath_ie=dd0900037f01010020ff7f
Cell 03 - Address: 00:0C:41:B3:06:C0
ESSID:"linksys"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=10/94 Signal level=-85 dBm Noise level=-95 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Extra:bcn_int=100
Cell 04 - Address: 00:0F:3D:5B:23:BA
ESSID:"ottis"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=2/94 Signal level=-93 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:ath_ie=dd0900037f010100170000

[wieman01]

Ahh yes, forgot to mention. I was able to connect to my secured AP and unsecured APs via NetworkManager prior to attempting to make my system static. Here is the iwlist scan:
I see... Please try WPA1 (TKIP) instead (sample script on first page), I don't know if the Madwifi driver supports WPA with CCMP (AES). Any better now?

[Forgott3n]

I see... Please try WPA1 (TKIP) instead (sample script on first page), I don't know if the Madwifi driver supports WPA with CCMP (AES). Any better now?

Thank you! It works perfectly.

[wieman01]

Thank you! It works perfectly.
It's the driver then. I should mention that in the tutorial. No all adapters/drivers support WPA2. :-)

[Forgott3n]

It's the driver then. I should mention that in the tutorial. No all adapters/drivers support WPA2. :-)

WPA2 worked alright, but its the encryption method (AES). Once I switched to TKIP it worked just fine.

A little side note: after boot up I have to restart the /etc/init.d/networking in order for it to work. I guess thats what the scripts are for on the tutorial page.

Thanks again!

[d3dtn01]

Wieman01,

Thanks for the suggestion about taking the "enable roaming" off. I deactivated that and now I'm connected to my network. Thanks for the great help!

[wieman01]

Wieman01,

Thanks for the suggestion about taking the "enable roaming" off. I deactivated that and now I'm connected to my network. Thanks for the great help!
That was Reauthor's idea. But anyway, good to hear it worked for you. :-)

[Forgott3n]

Interesting... For some reason, every once in a while I have to restart the networking because the server will stop staying connected.

Can a script be written to restart the networking if the server cannot ping google?

[wieman01]

Interesting... For some reason, every once in a while I have to restart the networking because the server will stop staying connected.

Can a script be written to restart the networking if the server cannot ping google?
I suppose one could do that altough I can't. But if you don't stay connected wouldn't it be easier if you played around with the settings of your physical network e.g. RTS threshold, beacon interval, channel, etc.? I am sure the problem lies there. The wireless channel is a usual suspect for instance as your network might interfer with others around you.

[pleurastic]

Thanks for the note of removing the "wpa_conf managed". Solved the fiesty upgrade failure in 2 minutes. My ath0 device was working but not connecting and I'd never have thought to remove the line you suggested.

[50ftrobot]

Hi there,

I'm a bit of a noob so please be patient!

I previously had my mum's pc setup with Ubuntu installed and working fine on our wireless network so I know the wireless card and drivers etc work.

The problem I've got is that I upgraded our home wireless network to WPA from WEP and followed a guide online to setup WPA in Ubuntu. This then [i think] broke everything and I couldn't connect to wireless at all even when the network was set back to WEP. This also resulted ina very slow boot up as I think the networking config was broken.

I followed this guide which which seems to have sorted the boot-up problem as the system is now quick and responsive again, however, when I restart the network it says 'Couldn't read interfaces file'

I know the network is fine because my mac and pc connect without an issue on WEP and WPA.

Any suggestions on how I can solve my problem would be much appreciated.

Many Thanks

[reauthor]

Hi there,

I'm a bit of a noob so please be patient!

I previously had my mum's pc setup with Ubuntu installed and working fine on our wireless network so I know the wireless card and drivers etc work.

The problem I've got is that I upgraded our home wireless network to WPA from WEP and followed a guide online to setup WPA in Ubuntu. This then [i think] broke everything and I couldn't connect to wireless at all even when the network was set back to WEP. This also resulted ina very slow boot up as I think the networking config was broken.

I followed this guide which which seems to have sorted the boot-up problem as the system is now quick and responsive again, however, when I restart the network it says 'Couldn't read interfaces file'

I know the network is fine because my mac and pc connect without an issue on WEP and WPA.

Any suggestions on how I can solve my problem would be much appreciated.

Many Thanks

Which version of Ubuntu you using?

[50ftrobot]

Hi,

Thanks for getting back to me.!

I installed theversion before [i can't remember the name] but then it got upgraded to the current one Edgy Eft [that's the version it states in the about Ubuntu Version info]

Thanks,

Chris

[wieman01]

Hi,

Thanks for getting back to me.!

I installed theversion before [i can't remember the name] but then it got upgraded to the current one Edgy Eft [that's the version it states in the about Ubuntu Version info]

Thanks,

Chris
More importantly what wireless network card have you got? And could you also post the contents of "/etc/network/interfaces" please? Simply connect your computer via Ethernet, that should do.

Reauthor and I can only help you if you provide a little more information. Actually, please provide as much as possible...

[50ftrobot]

Hi,

Thanks for getting back to me - I've got the details of all the things you ask for in the thread [i think]

I apologise in advance for any schoolboy errors you spot....

uname

Linux maggie-desktop 2.6.17-11-generic #2 SMP Thu Feb 1 19:52:28 UTC 2007 i686 GNU/Linux

route:

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface

lsmod:

Module Size Used by
nls_utf8 3200 1
nls_cp437 6912 1
vfat 14720 1
fat 56348 1 vfat
binfmt_misc 13448 1
ipv6 272288 8
rfcomm 42260 0
l2cap 27136 5 rfcomm
bluetooth 53476 4 rfcomm,l2cap
i915 21632 2
drm 74644 3 i915
sg 37404 0
sd_mod 22656 2
speedstep_lib 5764 0
cpufreq_userspace 5408 0
cpufreq_stats 7744 0
freq_table 6048 1 cpufreq_stats
cpufreq_powersave 2944 0
cpufreq_ondemand 8876 0
cpufreq_conservative 8712 0
video 17540 0
tc1100_wmi 8324 0
sbs 16804 0
sony_acpi 6412 0
pcc_acpi 14080 0
i2c_ec 6272 1 sbs
hotkey 11556 0
dev_acpi 12292 0
button 7952 0
battery 11652 0
container 5632 0
ac 6788 0
asus_acpi 17688 0
lp 12964 0
8139cp 24832 0
tsdev 9152 0
8139too 29056 0
mii 6912 2 8139cp,8139too
usb_storage 75072 1
scsi_mod 144648 3 sg,sd_mod,usb_storage
usblp 15488 0
acx 102540 0
libusual 17040 1 usb_storage
snd_intel8x0 34844 1
snd_ac97_codec 97696 1 snd_intel8x0
snd_ac97_bus 3456 1 snd_ac97_codec
snd_pcm_oss 47360 0
snd_mixer_oss 19584 1 snd_pcm_oss
evdev 11392 1
i2c_i810 6276 0
i2c_algo_bit 10376 1 i2c_i810
pcspkr 4352 0
psmouse 41352 0
serio_raw 8452 0
parport_pc 37796 1
parport 39496 2 lp,parport_pc
snd_pcm 84612 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
snd_timer 25348 1 snd_pcm
floppy 63044 0
i2c_core 23424 2 i2c_ec,i2c_algo_bit
snd 58372 8 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_ oss,snd_pcm,snd_timer
soundcore 11232 1 snd
snd_page_alloc 11400 2 snd_intel8x0,snd_pcm
shpchp 42144 0
pci_hotplug 32828 1 shpchp
intel_agp 26012 1
agpgart 34888 3 drm,intel_agp
ext3 142856 1
jbd 62228 1 ext3
ehci_hcd 34696 0
uhci_hcd 24968 0
usbcore 134912 7 usb_storage,usblp,acx,libusual,ehci_hcd,uhci_hcd
ide_generic 2432 0
ide_cd 33696 0
cdrom 38944 1 ide_cd
ide_disk 18560 3
piix 11780 1
generic 6276 0
thermal 15624 0
processor 31560 1 thermal
fan 6020 0
fbcon 41504 0
tileblit 3840 1 fbcon
font 9344 1 fbcon
bitblit 7168 1 fbcon
softcursor 3328 1 bitblit
vesafb 9244 0
capability 5896 0
commoncap 8704 1 capability

iwlist scan:

lo Interface doesn't support scanning.

iwconfig:

lo no wireless extensions.

wlan0 IEEE 802.11b+/g+ ESSID:"STAD7D5D3" Nickname:"acx v0.3.21"
Mode:Managed Channel:1 Access Point: Not-Associated
Bit Rate:54 Mb/s Tx-Power=15 dBm Sensitivity=1/3
Retry min limit:7 RTS thr:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

eth0 no wireless extensions.

sit0 no wireless extensions.

interfaces:

auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet sdhcp
wpa-driver wext
wpa-ssid skelligs
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk da56438a0c62b1bbd02a48789c5b5f650a009275a5b85bdb42 f2e42b88cd8a88

ifconfig:

eth0 Link encap:Ethernet HWaddr 00:01:6C:30:59:7B
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:209 Base address:0x4000

lo Link encap:Local Loopback
LOOPBACK MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

wlan0 Link encap:Ethernet HWaddr 00:C0:49:D7:D5:D3
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:169


cat resolve:

cat: /etc/resolve.conf: No such file or directory

cat network:

auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet sdhcp
wpa-driver wext
wpa-ssid skelligs
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk da56438a0c62b1bbd02a48789c5b5f650a009275a5b85bdb42 f2e42b88cd8a88

cat modprobe

cat: /etc/modprobe.d/ndiswrapper: No such file or directory

let me know if you need to see anything else [though you might need to supply the terminal command as I'm not clued up on this but can follow instructions easily]

Thanks!

[wieman01]

50ftrobot:

Are your sure "iwlist scan" does not yield any results with regard to your wireless interface ("wlan0")? Have you installed "ndiswrapper"?

One thing I saw immediately although I am not sure if it is a typo:

auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet sdhcp
wpa-driver wext
wpa-ssid skelligs
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk da56438a0c62b1bbd02a48789c5b5f650a009275a5b85bdb42 f2e42b88cd8a88
The line in red should read:

iface wlan0 inet dhcp
It would be helpful to know what your wireless interface is referred to normally (e.g. eth1, wlan0, etc.). Any idea?

[50ftrobot]

I changed the line to read dhcp but it's not helped.

I don't think ndiswrapper is installed, but I didn't need it before I had this problem so would I still need it as I thought that is just for the driver for the wireless card [the card was working on WEP]?

no results on iwlist scan

Thanks

[wieman01]

I changed the line to read dhcp but it's not helped.

I don't think ndiswrapper is installed, but I didn't need it before I had this problem so would I still need it as I thought that is just for the driver for the wireless card [the card was working on WEP]?

no results on iwlist scan

Thanks
No results? Then your card is not working... Have you switched it off (physical switch) perhaps?

[50ftrobot]

No results? Then your card is not working... Have you switched it off (physical switch) perhaps?
i don't think it has an actual physical switch on it - it just has an antenna on it sticking out the back of the pc. I'm not sure if following a guide elsewhere has broken the settings for it [or perhaps I did unknowingly which is just as likely].

Is there a terminal command you could suggest which would determine whether the card was working or not?

[wieman01]

i don't think it has an actual physical switch on it - it just has an antenna on it sticking out the back of the pc. I'm not sure if following a guide elsewhere has broken the settings for it [or perhaps I did unknowingly which is just as likely].

Is there a terminal command you could suggest which would determine whether the card was working or not?
It is a PCI card, isn't it? So you should try this:

lspci
Please open a new thread, however... Apparently you have got a problem with your wireless card... I would not try to configure wireless security unless you get it working.

[reauthor]

Hy,can you give me output of this command.

iwlist wlan0 scan

[jago25_98]

I'm stumped. It was working before? -using knetworkmanager but that has stopped listing networks.

iwconfig truncates the 64character key to 32characters so I'm trying WPA instead.

I can't even get to my router to see what it's setup as because I don't know what the IP is anymore.


Linux r40 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux
eth0 Link encap:Ethernet HWaddr 00:06:1B:DA:41:F9
inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::206:1bff:feda:41f9/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3327 errors:0 dropped:0 overruns:0 frame:0
TX packets:3334 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2147076 (2.0 MiB) TX bytes:619149 (604.6 KiB)

eth2 Link encap:Ethernet HWaddr 00:0E:35:FA:80:8B
inet6 addr: fe80::20e:35ff:fefa:808b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:18 errors:0 dropped:0 overruns:0 frame:0
TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:490 (490.0 b) TX bytes:1348 (1.3 KiB)
Interrupt:11 Base address:0x6000 Memory:d0200000-d0200fff

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:170 errors:0 dropped:0 overruns:0 frame:0
TX packets:170 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:15417 (15.0 KiB) TX bytes:15417 (15.0 KiB)

Kernel IP routeing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth0
0.0.0.0 192.168.1.10 0.0.0.0 UG 0 0 0 eth0
eth2 IEEE 802.11g ESSID:"hillpark"
Mode:Managed Frequency:2.412 GHz Access Point: 00:0E:A6:CE:E2:37
Bit Rate:54 Mb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr:off Fragment thr:off
Encryption key:1CA5-BD93-FAF3-5945-A096-BD17-3F Security mode:restricted
Power Management:off
Link Quality=73/100 Signal level=-55 dBm Noise level=-92 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

eth0 Link encap:Ethernet HWaddr 00:06:1B:DA:41:F9
inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::206:1bff:feda:41f9/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3327 errors:0 dropped:0 overruns:0 frame:0
TX packets:3334 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2147076 (2.0 MiB) TX bytes:619149 (604.6 KiB)

eth2 Link encap:Ethernet HWaddr 00:0E:35:FA:80:8B
inet6 addr: fe80::20e:35ff:fefa:808b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:18 errors:0 dropped:0 overruns:0 frame:0
TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:490 (490.0 b) TX bytes:1348 (1.3 KiB)
Interrupt:11 Base address:0x6000 Memory:d0200000-d0200fff

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:170 errors:0 dropped:0 overruns:0 frame:0
TX packets:170 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:15417 (15.0 KiB) TX bytes:15417 (15.0 KiB)

Module Size Used by
michael_mic 3584 2
ieee80211_crypt_tkip 12032 1
ipv6 268704 8
binfmt_misc 12680 1
rfcomm 40856 2
l2cap 25728 5 rfcomm
bluetooth 55908 4 rfcomm,l2cap
nvram 9992 1
uinput 10240 1
radeon 124576 2
drm 81044 3 radeon
ppdev 10116 0
speedstep_ich 6288 0
speedstep_lib 6148 1 speedstep_ich
cpufreq_ondemand 9228 1
cpufreq_conservative 8200 0
cpufreq_stats 7360 0
cpufreq_powersave 2688 0
cpufreq_userspace 5408 0
freq_table 5792 3 speedstep_ich,cpufreq_ondemand,cpufreq_stats
dev_acpi 12292 0
pcc_acpi 13184 0
tc1100_wmi 8068 0
sony_acpi 6284 0
ibm_acpi 31512 0
sbs 15652 0
container 5248 0
i2c_ec 5888 1 sbs
i2c_core 22784 1 i2c_ec
ac 6020 0
dock 10268 0
battery 10756 0
asus_acpi 17308 0
backlight 7040 2 ibm_acpi,asus_acpi
button 8720 0
video 16388 0
nls_iso8859_1 5120 1
nls_cp437 6784 1
vfat 14208 1
fat 53916 1 vfat
lp 12452 0
fuse 46612 0
snd_intel8x0 34204 2
snd_ac97_codec 98336 1 snd_intel8x0
ac97_bus 3200 1 snd_ac97_codec
arc4 2944 4
ecb 4480 4
blkcipher 6784 1 ecb
joydev 10816 0
snd_pcm_oss 44544 0
snd_mixer_oss 17408 1 snd_pcm_oss
irtty_sir 9600 0
sir_dev 17156 1 irtty_sir
ieee80211_crypt_wep 6144 1
snd_pcm 79876 4 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
pcmcia 39212 0
irda 201276 2 irtty_sir,sir_dev
snd_seq_dummy 4740 0
snd_seq_oss 32896 0
crc_ccitt 3072 1 irda
ipw2200 148040 0
snd_seq_midi 9600 0
snd_rawmidi 25472 1 snd_seq_midi
snd_seq_midi_event 8448 2 snd_seq_oss,snd_seq_midi
snd_seq 52592 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_mid i_event
snd_timer 23684 3 snd_pcm,snd_seq
snd_seq_device 9100 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi ,snd_seq
parport_pc 36388 1
psmouse 38920 0
ieee80211 34760 1 ipw2200
ieee80211_crypt 7040 3 ieee80211_crypt_tkip,ieee80211_crypt_wep,ieee80211
parport 36936 3 ppdev,lp,parport_pc
yenta_socket 27532 1
rsrc_nonstatic 14080 1 yenta_socket
pcmcia_core 40852 3 pcmcia,yenta_socket,rsrc_nonstatic
pcspkr 4224 0
snd 54020 12 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_ oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_ti mer,snd_seq_device
serio_raw 7940 0
soundcore 8672 1 snd
snd_page_alloc 10888 2 snd_intel8x0,snd_pcm
shpchp 34324 0
pci_hotplug 32576 1 shpchp
intel_agp 25116 1
agpgart 35400 2 drm,intel_agp
iTCO_wdt 11812 0
iTCO_vendor_support 4868 1 iTCO_wdt
af_packet 23816 12
evdev 11008 5
tsdev 8768 0
ext3 133128 1
jbd 59816 1 ext3
mbcache 9604 1 ext3
sg 36252 0
sr_mod 17060 0
cdrom 37664 1 sr_mod
sd_mod 23428 4
generic 5124 0 [permanent]
ata_generic 9092 0
floppy 59524 0
ehci_hcd 34188 0
e100 36232 0
mii 6528 1 e100
ata_piix 15492 3
libata 125720 2 ata_generic,ata_piix
scsi_mod 142348 4 sg,sr_mod,sd_mod,libata
uhci_hcd 25360 0
usbcore 134280 3 ehci_hcd,uhci_hcd
thermal 14856 0
processor 31048 1 thermal
fan 5636 0
fbcon 42656 0
tileblit 3584 1 fbcon
font 9216 1 fbcon
bitblit 6912 1 fbcon
softcursor 3200 1 bitblit
vesafb 9220 0
capability 5896 0
commoncap 8192 1 capability
eth2 Scan completed :
Cell 01 - Address: 00:0E:A6:CE:E2:37
ESSID:"hillpark"
Protocol:IEEE 802.11bg
Mode:Master
Channel:1
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=71/100 Signal level=-57 dBm
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Extra: Last beacon: 136ms ago

auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0

auto eth0
iface eth0 inet dhcp

auto eth2
iface eth2 inet dhcp
wpa-ssid hillpark
wpa-key-mgmt WPA-PSK
wpa-psk <64character,256bit-wep-key-censored)
wireless-essid hillpark# generated by NetworkManager, do not edit!



nameserver 192.168.1.10

[reauthor]

hy everybody...

I have a one suggestion..It is much easier and faster for me and I belive for other members to give help if I we have some information. So,I suggest that everybody who needs a help follow this protocol.

Example:

Hy,I using_________(Edgy,Feisty)and can not connect to my AP/wireless router.
Roaming mode in Network Manager is disabled(only if using Feisty).

My iwconfig

My /etc/network/interfaces

My iwlist ________(eth1,wlanO,ath0)scan

So,like I said,this is suggestion,if somebody have better idea....

[KiwiPete]

Thank you Wieman01

Having finally got my wireless card working (with no security) I have now followed the instructions in your original post (at top of this thread) and got the wireless enabled successfully with WPA1.

The only extra question I have is that I using a wireless card with Atheros chipset, but I just used 'driver wext' in my interfaces file - and it seems to work fine.
Should I change it to 'driver madwifi' to get better performance??

KiwiPete

[wieman01]

Thank you Wieman01

Having finally got my wireless card working (with no security) I have now followed the instructions in your original post (at top of this thread) and got the wireless enabled successfully with WPA1.

The only extra question I have is that I using a wireless card with Atheros chipset, but I just used 'driver wext' in my interfaces file - and it seems to work fine.
Should I change it to 'driver madwifi' to get better performance??

KiwiPete
Hello,

Glad to hear it. I don't know if the driver makes any difference at all in terms of performance. Use whatever works for you. :-)

[wieman01]

hy everybody...

I have a one suggestion..It is much easier and faster for me and I belive for other members to give help if I we have some information. So,I suggest that everybody who needs a help follow this protocol.

Example:

Hy,I using_________(Edgy,Feisty)and can not connect to my AP/wireless router.
Roaming mode in Network Manager is disabled(only if using Feisty).

My iwconfig

My /etc/network/interfaces

My iwlist ________(eth1,wlanO,ath0)scan

So,like I said,this is suggestion,if somebody have better idea....
That's a good idea actually. I'll try to update my thread over the weekend, Reauthor. Could make the whole procedure a bit smoother.

[jago25_98]

I got mine working in the end when knetworkmanager started working again. The trick was to enter the 256 WEP key as WPA.

[smiley1962]

hy i'm using feisty and can not connect to my AP/wireless router.
Roaming mode in Network Manager is disabled

My iwconfig

eth1 IEEE 802.11b ESSID:"smiley2" Nickname:"Broadcom 4301"
Mode:Managed Frequency=2.472 GHz Access Point: 00:01:E3:D9:C7:C2
Bit Rate=1 Mb/s Tx-Power=16 dBm
RTS thr:off Fragment thr:off
Encryption key:off
Link Quality=0/100 Signal level=-256 dBm Noise level=-256 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

My /etc/network/interfaces

auto lo
iface lo inet loopback

auto eth1
iface eth1 inet static
address 192.168.2.2
gateway 192.168.2.1
dns-nameservers 195.121.1.34
netmask 255.255.255.0
wpa-driver wext
wpa-ssid smiley2
wpa-ap-scan 2
wpa-proto WPA RSN
wpa-pairwise TKIP CCMP
wpa-group TKIP CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 898e115c50e2a053ea04a161cb95aa7a1e9f40f8971373117e 228fda2d50201a

iface eth0 inet static
address 192.168.2.2
netmask 255.255.255.0
gateway 192.168.2.1

auto eth0

My iwlist eth1 scan

eth1 Scan completed :
Cell 01 - Address: 00:01:E3:D9:C7:C2
ESSID:"smiley2"
Protocol:IEEE 802.11bg
Mode:Master
Channel:13
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 9 Mb/s; 11 Mb/s
6 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=80/100 Signal level=-55 dBm Noise level=-43 dBm
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : TKIP CCMP
Authentication Suites (1) : PSK
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : TKIP CCMP
Authentication Suites (1) : PSK
Preauthentication Supported
Extra: Last beacon: 32ms ago

I have tried almost every howto on the net but can't get it working.
about the wpa_supplicant.conf; it does not exist

Ihope you guys can help me:)

[wieman01]

Smiley1962:

First, what wireless card have you got?

Second this line needs to be changed as ESSID broadcast is enabled in your case:

wpa-ap-scan 1
Third, can you connect to unsecured networks?

EDIT:
This is the right place for you. So stay with us, I am sure we will be able to get you connected in the end.

[smiley1962]

First, what wireless card have you got?
a broadcom 4303 (with the linux driver)

second this line needs to be changed as ESSID broadcast is enabled in your case:

ok i wil change the 2 into a 1

Third, can you connect to unsecured networks?

Tried that but unsuccesfull

[wieman01]

First, what wireless card have you got?
a broadcom 4303 (with the linux driver)

second this line needs to be changed as ESSID broadcast is enabled in your case:

ok i wil change the 2 into a 1

Third, can you connect to unsecured networks?

Tried that but unsuccesfull
Ok... I would not proceed here before you have not been able to establish a connection in unsecured mode if you know what I mean. WPA will make things even more complicated. Post your problem in the forums, there should be people who are able to help.

[smiley1962]

ok thanks anyway

[reauthor]

Hy smiley1962..
Can you setup your AP whitout encryption and put this configuration in your interfaces

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp
wireless-essid smiley2

than save your configuration and restart network whit sudo /etc/init.d/networking restart

Please tell me if this work for you...

[reech]

I have recently decided to switch to wpa - I'm having problems with my fiesty box - it's been using wep with no problems. I can use the WPA AP with my laptop no problem (winXP)

I'm using a netgear ma101 usb card (at76_usb) -

I get the following output when attempting to start networking...



root@reech-desktop:/home/reech# /etc/init.d/networking restart
* Reconfiguring network interfaces... wpa_driver_atmel_set_wpa wlan0
ioctl[ATMEL_WPA_IOCTL_PARAM]: Operation not supported
ioctl[ATMEL_WPA_IOCTL_PARAM]: Operation not supported
ioctl[ATMEL_WPA_IOCTL]: Argument list too long
Failed to set encryption.
ioctl[ATMEL_WPA_IOCTL]: Argument list too long
Failed to set encryption.
ioctl[ATMEL_WPA_IOCTL]: Argument list too long
Failed to set encryption.
ioctl[ATMEL_WPA_IOCTL]: Argument list too long
Failed to set encryption.
wpa_driver_atmel_set_countermeasures - not yet implemented
wpa_driver_atmel_set_drop_unencrypted - not yet implemented


here is the output from the syslog:



May 8 00:09:08 reech-desktop kernel: [ 4673.260000] ubuntu/wireless/at76/at76c503.c: 2492: assertion dev->istate == SCANNING failed
May 8 00:09:35 reech-desktop ntpdate[9080]: can't find host ntp.ubuntu.com
May 8 00:09:35 reech-desktop ntpdate[9080]: no servers can be used, exiting
May 8 00:11:35 reech-desktop kernel: [ 4820.756000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 8 00:11:37 reech-desktop kernel: [ 4822.864000] ubuntu/wireless/at76/at76c503.c: 2522: assertion dev->istate == INIT failed
May 8 00:11:38 reech-desktop kernel: [ 4823.592000] ubuntu/wireless/at76/at76c503.c: 2492: assertion dev->istate == SCANNING failed
May 8 00:12:05 reech-desktop ntpdate[9226]: can't find host ntp.ubuntu.com
May 8 00:12:05 reech-desktop ntpdate[9226]: no servers can be used, exiting


below is my interfaces file:



auto wlan0
iface wlan0 inet static
address 192.168.0.12
netmask 255.255.255.0
gateway 192.168.0.1
wpa-driver atmel
##wpa-conf managed
wpa-ssid reechy
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk 495c57eed85a88a04d2a1567b1db83bf188caff9929be64445 a0fb8a066c9bd4


...seems fine no?

I'm running kernel 2.6.20-15-generic

Is this a driver problem? I'm at my wit's end.

](*,)

[wieman01]

Is this a driver problem? I'm at my wit's end.
Looks like it is a driver problem indeed. Have you downloaded the latest Windows driver for your adapter? If not, please do so and deploy it using "ndiswrapper".

Before you do so, please try another wpa-driver (i.e. wext) which should be the right one in your case ("ndiswrapper"):

wpa-driver wext
Also ensure that ESSID broadcast is disabled as that's what this line says:

wpa-ap-scan 2
If you want to enable broadcast it should read:

wpa-ap-scan 1

[reech]

Thank you for the reply - although I had hoped to get it working without resorting to ndiswrapper.

I had thought it would be supported with the kernel module driver as the at_76 module is loaded and working:

I had tried wext with no joy.



hostap = Host AP driver (Intersil Prism2/2.5/3)
atmel = ATMEL AT76C5XXx (USB, PCMCIA)
wext = Linux wireless extensions (generic)
madwifi = Atheros
wired = wpa_supplicant wired Ethernet driver

[wieman01]

Thank you for the reply - although I had hoped to get it working without resorting to ndiswrapper.

I had thought it would be supported with the kernel module driver as the at_76 module is loaded and working:

I had tried wext with no joy.
Well, the interface name "wlan0" suggests you are using "ndiswrapper" already... Are you sure you are referring to the right interface then?

What does a scan yield?

iwlist scan

[reech]

scan finds my AP

I think the wlan0 label is legacy as I think I was using ndiswrapper with edgy, and fiesty seems to have decided to use the kernel module (after upgrading).

[wieman01]

scan finds my AP

I think the wlan0 label is legacy as I think I was using ndiswrapper with edgy, and fiesty seems to have decided to use the kernel module (after upgrading).
Alright then. Then give 'wext' a go please. If that does not yield any good results, then I am afraid the Linux driver does not support WPA after all. At least that's how I interpret the error message.

Can you connect to unsecured networks at all?

[reech]

Thanks for your patience wieman01 - I can connect fine at the moment using wep and the current kernel module - so I assume an unsecured network will be fine.

I have tried WEXT with similar results - but of course the ndiswrapper module is not loaded.

[wieman01]

Thanks for your patience wieman01 - I can connect fine at the moment using wep and the current kernel module - so I assume an unsecured network will be fine.

I have tried WEXT with similar results - but of course the ndiswrapper module is not loaded.
No problem.

I would do some more research concerning your adapter and WPA support. I can't tell for sure, but it appears to me that the current driver does not really support WPA. That said "ndiswrapper" may be worth a short after all. The latest driver for Windows will certainly support WPA(2).

[deevus]

This worked for me, but Im only connected at 1mbit/s .. Im using a Broadcom 4306 on a PPC, capable of 54mbit. What can I do to speed it up?

[reech]

I would do some more research concerning your adapter and WPA support. I can't tell for sure, but it appears to me that the current driver does not really support WPA. That said "ndiswrapper" may be worth a short after all. The latest driver for Windows will certainly support WPA(2).

Indeed - ndiswrapper is looking like my only option - thanks again.:)

[Zoufiax]

I can't get my wireless connection to work when using WPA1 security, I have tried the suggestions of the first post of this topic. However, I do get it working using WEP security, this reply was sent using it actually.

I wanted to post all results here of the commands we had to enter when "stumped", but when I try, the forum gives me an error that I'm using too many pictures, which is not correct. If anyone needs specific information please let me know, as well as how I can retrieve it as I'm a Linux newbie.

[wieman01]

I can't get my wireless connection to work when using WPA1 security, I have tried the suggestions of the first post of this topic. However, I do get it working using WEP security, this reply was sent using it actually.

I wanted to post all results here of the commands we had to enter when "stumped", but when I try, the forum gives me an error that I'm using too many pictures, which is not correct. If anyone needs specific information please let me know, as well as how I can retrieve it as I'm a Linux newbie.
What card have you got and what driver is in use? The issue could be that either card or driver does not support WPA.

[Zoufiax]

I'm using Speedtouch 121g, and it does support WPA1, for previously I was using Windows on my laptop, and WPA was working fine. But now I have installed Ubuntu Fiesty Fawn and can't get it working. I'm using ndiswrapper with the Windows drivers for the 121g, and that works fine for I can get online when using WEP-security. Also I can get my passphrase (64 characters), and I see all wireless networks in the neighborhood, so it has to do something with my Linux-WPA-configuration. Too bad Ubuntu doesn't support WPA as it supports WEP yet.

[wieman01]

I'm using Speedtouch 121g, and it does support WPA1, for previously I was using Windows on my laptop, and WPA was working fine. But now I have installed Ubuntu Fiesty Fawn and can't get it working. I'm using ndiswrapper with the Windows drivers for the 121g, and that works fine for I can get online when using WEP-security. Also I can get my passphrase (64 characters), and I see all wireless networks in the neighborhood, so it has to do something with my Linux-WPA-configuration. Too bad Ubuntu doesn't support WPA as it supports WEP yet.
Alright. Then I would ask you to post the contents of "/etc/network/interfaces". That's shed some light on the issue.

[mazz]

Hi,I using Feisty and can not connect to my AP/wireless router.
Roaming mode in Network Manager is disabled(only if using Feisty).

My iwconfig:

lo no wireless extensions.



eth0 no wireless extensions.



ra0 RT2500 Wireless ESSID:""

Mode:Managed Frequency=2.412 GHz Bit Rate:11 Mb/s Tx-Power:0 dBm

RTS thr:off Fragment thr:off

Link Quality=0/100 Signal level=-120 dBm Noise level:-192 dBm

Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0

Tx excessive retries:0 Invalid misc:0 Missed beacon:0


My /etc/network/interfaces:

auto lo

iface lo inet loopback



auto eth0

iface eth0 inet dhcp



auto eth1

iface eth1 inet dhcp



auto eth2

iface eth2 inet dhcp



auto ath0

iface ath0 inet dhcp



auto wlan0

iface wlan0 inet dhcp



address 192.168.168.0.3

gateway 192.168.0.255

dns-nameservers 192.168.0.1

netmask 255.255.255.0

wpa-driver wext

wpa-ssid <MyNetwork>

wpa-ap-scan 1

wpa-proto WPA

wpa-pairwise TKIP

wpa-group CCMP

wpa-key-mgmt WPA-PSK

wpa-psk <ccdc167d0597b7acb5336dfd8a3bc598da8472fed4c2cf7084 18a27d35c20080>


My iwlist scan:
Usage: iwlist [interface] scanning

[interface] frequency

[interface] channel

[interface] bitrate

[interface] rate

[interface] encryption

[interface] key

[interface] power

[interface] txpower

[interface] retry

[interface] ap

[interface] accesspoints

[interface] peers

[interface] event


I have tried both WAP 1 and WAP 2. stil cant get it to work.
My wireless card is a Linksys Wmp54G v4. I am trying to connect to a Netgear router.
See if something is wrong with my info.

[Zoufiax]

Alright. Then I would ask you to post the contents of "/etc/network/interfaces". That's shed some light on the issue.
Here it is:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

# auto eth1
# iface eth1 inet dhcp
#
# auto eth2
# iface eth2 inet dhcp
#
# auto ath0
# iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp
wireless-essid SpeedTouch3C153D
wireless-key [secret hexadecimal string]
wpa-driver wext
wpa-ssid SpeedTouch3C153D
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk [secret hexadecimal string consisting of 64 characters (lower case, does that matter?)]

If there is some more information you need please let me know.

[venky80]

@Weiman
Hi It seems you have been helping people here for quite a long time.
I have intel pro wireless 3945ABG in my toshiba laptop
my wireless device is eth01
iwlist scan
shows my wireless
with IE WPA version 1
group chiper as WEP-40
pairwise chipher WEP-40
authentication suites PSK
IE IEEE 802.11i/WPA2 version 1
group chiper as WEP-40
pairwise chipher WEP-40
authentication suites PSK

I have put the necessary lines in interfaces but iam not able to connect
do i need to do something to my wpa_supplicant?
thanks for any help

[wieman01]

Here it is:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

# auto eth1
# iface eth1 inet dhcp
#
# auto eth2
# iface eth2 inet dhcp
#
# auto ath0
# iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp
wireless-essid SpeedTouch3C153D
wireless-key [secret hexadecimal string]
wpa-driver wext
wpa-ssid SpeedTouch3C153D
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk [secret hexadecimal string consisting of 64 characters (lower case, does that matter?)]

If there is some more information you need please let me know.
Looks a bit different from mine. Please try this instead:

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid SpeedTouch3C153D
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <your_hex_key>
I have removed 2 lines (wireless-essid, wireless-key) which refer to WEP security.

Please restart the computer and restart the network right after that:

sudo ifdown -v wlan0

sudo ifup -v wlan0
If possible post the output.

[wieman01]

@Weiman
Hi It seems you have been helping people here for quite a long time.
I have intel pro wireless 3945ABG in my toshiba laptop
my wireless device is eth01
iwlist scan
shows my wireless
with IE WPA version 1
group chiper as WEP-40
pairwise chipher WEP-40
authentication suites PSK
IE IEEE 802.11i/WPA2 version 1
group chiper as WEP-40
pairwise chipher WEP-40
authentication suites PSK

I have put the necessary lines in interfaces but iam not able to connect
do i need to do something to my wpa_supplicant?
thanks for any help
WPA-Supplicant won't help you there as you use WEP, not WPA. Ubuntu supports WEP security out of the box. Just use the default networking tool for wireless.

[nab]

well,

I solved my problem.

It seems that the manual configuration in /etc/network/interfaces and nm-applet broke my system, because after removing all edits from /etc/network/interfaces my wlan works fine again.

Thanks for the help.
Niko

[Zoufiax]

Looks a bit different from mine. Please try this instead:

I have removed 2 lines (wireless-essid, wireless-key) which refer to WEP security.

Please restart the computer and restart the network right after that:

If possible post the output.

If have changed my /etc/network/interfaces according to your suggestions, and restarted the computer and after that the network (sudo ifdown -v wlan0, and: sudo ifup -v wlan0), but it still doesn't work. The output of these ifdown and ifup commands was as follows:

zoufiax@zoufiax-laptop:~$ sudo ifdown -v wlan0
Password:
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
RTNETLINK answers: No such process
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 3984
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:12:bf:08:59:49
Sending on LPF/wlan0/00:12:bf:08:59:49
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 10.0.0.138 port 67
ifconfig wlan0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan0.pid
Stopped /sbin/wpa_supplicant (pid 3913).

zoufiax@zoufiax-laptop:~$ sudo ifup -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan0
wpa_supplicant: wpa-ap-scan 1 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "SpeedTouch3C153D" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise TKIP -- OK
wpa_supplicant: wpa-group TKIP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto WPA -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:12:bf:08:59:49
Sending on LPF/wlan0/00:12:bf:08:59:49
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant
zoufiax@zoufiax-laptop:~$

[venky80]

WPA-Supplicant won't help you there as you use WEP, not WPA. Ubuntu supports WEP security out of the box. Just use the default networking tool for wireless.

I think you misunderstood my router is setup for WPA-PSK
here are the details


venky@venky-laptop:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

eth1 unassociated ESSID:off/any
Mode:Managed Frequency=nan kHz Access Point: Not-Associated
Bit Rate:0 kb/s Tx-Power:16 dBm
Retry limit:15 RTS thr:off Fragment thr:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:80 Missed beacon:0

venky@venky-laptop:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:13:46:3F:99:A2
ESSID:"nyf"
Protocol:IEEE 802.11bg
Mode:Master
Channel:11
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 9 Mb/s; 11 Mb/s
6 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=61/100 Signal level=-71 dBm Noise level=-71 dBm
Extra: Last beacon: 84ms ago
Cell 02 - Address: 00:0C:E5:4E:88:2F
ESSID:"wastintime"
Protocol:IEEE 802.11bg
Mode:Master
Channel:11
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=97/100 Signal level=-29 dBm Noise level=-29 dBm
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : PSK
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : PSK
Extra: Last beacon: 140ms ago


My Interfaces file according to the tutorial (hopefully I made no mistakes)
Is it necessary to get rid of knetworkmanager?

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-ssid wastintime
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wap-psk <my key>

auto eth2
iface eth2 inet dhcp

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp

Thanks

[wieman01]

If have changed my /etc/network/interfaces according to your suggestions, and restarted the computer and after that the network (sudo ifdown -v wlan0, and: sudo ifup -v wlan0), but it still doesn't work. The output of these ifdown and ifup commands was as follows:

zoufiax@zoufiax-laptop:~$ sudo ifdown -v wlan0
Password:
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
RTNETLINK answers: No such process
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 3984
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:12:bf:08:59:49
Sending on LPF/wlan0/00:12:bf:08:59:49
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 10.0.0.138 port 67
ifconfig wlan0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan0.pid
Stopped /sbin/wpa_supplicant (pid 3913).

zoufiax@zoufiax-laptop:~$ sudo ifup -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan0
wpa_supplicant: wpa-ap-scan 1 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "SpeedTouch3C153D" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise TKIP -- OK
wpa_supplicant: wpa-group TKIP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto WPA -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:12:bf:08:59:49
Sending on LPF/wlan0/00:12:bf:08:59:49
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant
zoufiax@zoufiax-laptop:~$
A few more questions:

a. MAC filtering is disabled (router settings)?
b. Is your firewall up (using Firestarter for instance)?

Can you check your router's log-files? What do they say?

The authentication/encryption bit seems ok, we need to figure out why you cannot connect via DHCP. Has this worked before on unsecured networks?

[wieman01]

I think you misunderstood my router is setup for WPA-PSK
here are the details


venky@venky-laptop:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

eth1 unassociated ESSID:off/any
Mode:Managed Frequency=nan kHz Access Point: Not-Associated
Bit Rate:0 kb/s Tx-Power:16 dBm
Retry limit:15 RTS thr:off Fragment thr:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:80 Missed beacon:0

venky@venky-laptop:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:13:46:3F:99:A2
ESSID:"nyf"
Protocol:IEEE 802.11bg
Mode:Master
Channel:11
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 9 Mb/s; 11 Mb/s
6 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=61/100 Signal level=-71 dBm Noise level=-71 dBm
Extra: Last beacon: 84ms ago
Cell 02 - Address: 00:0C:E5:4E:88:2F
ESSID:"wastintime"
Protocol:IEEE 802.11bg
Mode:Master
Channel:11
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=97/100 Signal level=-29 dBm Noise level=-29 dBm
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : PSK
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : PSK
Extra: Last beacon: 140ms ago


My Interfaces file according to the tutorial (hopefully I made no mistakes)
Is it necessary to get rid of knetworkmanager?

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-ssid wastintime
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wap-psk <my key>

auto eth2
iface eth2 inet dhcp

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp

Thanks
What confuses me is the fact that the scan says that your router is set to use "WEP-40" as cipher which is referring to WEP, not WPA. WPA supports both TKIP and AES, but certainly not WEP-40 which would defeat the purpose of WPA i.e. enhanced security.

Now... Would you mind changing the cipher from WEP-40 to TKIP on the router? Your client script mentions TKIP ("wpa-pairwise TKIP") so the easiest way from here is to tell your router to use TKIP (WPA) instead of WEP-40.

EDIT:
If you don't have access to the router because it isn't yours, let me know. Then we'll change your script although that's not my preferred solution as WEP-40 is not part of the WPA suite.

[Zoufiax]

A few more questions:

a. MAC filtering is disabled (router settings)?
b. Is your firewall up (using Firestarter for instance)?

Can you check your router's log-files? What do they say?

The authentication/encryption bit seems ok, we need to figure out why you cannot connect via DHCP. Has this worked before on unsecured networks?
a. I don't know what MAC filtering is. I have a Speedtouch 580 router and don't know if it supports MAC filtering. Should it be on or off? By the way, before Ubuntu I used Windows XP, and had no problem connecting to the wireless network using WPA so I guess it has to do with the setup of Ubuntu rather then my router.
b. I am not using a firewall on my Ubuntu laptop as far as I know.

I don't think my router has any log files as it is not a computer.

[VorDesigns]

Hi,

Used this document after trying others, still no joy. This is one of the reason I can't get business users to switch to Linux but I'm still trying.

I have tried excluding the eth0 device in the interfaces to no avail. This will work with some tweaking using WEP, been there, done that.
Current status is card show connected briefly then disconnected, cycle and repeat.

This is a fresh install/patch.
----------------------
tanuki@pikunikubasukitu:~$ uname -a
Linux pikunikubasukitu 2.6.15-28-386 #1 PREEMPT Tue Mar 13 20:49:31 UTC 2007 i686 GNU/Linux
tanuki@pikunikubasukitu:~$ ifconfig -a
ath0 Link encap:Ethernet HWaddr 99:99:99:99:99:99
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:703 errors:1707 dropped:0 overruns:0 frame:1707
TX packets:742 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:200
RX bytes:79439 (77.5 KiB) TX bytes:104109 (101.6 KiB)
Interrupt:11 Memory:d8a40000-d8a50000

eth0 Link encap:Ethernet HWaddr 99:99:99:99:99:99
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:13 errors:0 dropped:0 overruns:0 frame:0
TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2282 (2.2 KiB) TX bytes:1791 (1.7 KiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:15 errors:0 dropped:0 overruns:0 frame:0
TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:772 (772.0 b) TX bytes:772 (772.0 b)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

tanuki@pikunikubasukitu:~$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
tanuki@pikunikubasukitu:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

ath0 IEEE 802.11g ESSID:"too_ishi_o_ishi_ashi"
Mode:Managed Frequency:2.452 GHz Access Point: 99:99:99:99:99:99
Bit Rate:36 Mb/s Tx-Power:18 dBm Sensitivity=0/3
Retry:off RTS thr:off Fragment thr:off
Power Management:off
Link Quality=28/94 Signal level=-67 dBm Noise level=-95 dBm
Rx invalid nwid:57 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

sit0 no wireless extensions.

tanuki@pikunikubasukitu:~$ ifconfig
ath0 Link encap:Ethernet HWaddr 99:99:99:99:99:99
inet6 addr: fe80::20d:88ff:feaa:a1a6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:742 errors:1753 dropped:0 overruns:0 frame:1753
TX packets:789 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:200
RX bytes:83846 (81.8 KiB) TX bytes:110876 (108.2 KiB)
Interrupt:11 Memory:d8a40000-d8a50000

eth0 Link encap:Ethernet HWaddr 99:99:99:99:99:99
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:13 errors:0 dropped:0 overruns:0 frame:0
TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2282 (2.2 KiB) TX bytes:1791 (1.7 KiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:15 errors:0 dropped:0 overruns:0 frame:0
TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:772 (772.0 b) TX bytes:772 (772.0 b)

tanuki@pikunikubasukitu:~$ lsmod
Module Size Used by
rfcomm 40216 0
l2cap 26244 5 rfcomm
bluetooth 50020 4 rfcomm,l2cap
ppdev 9220 0
ipv6 265856 6
speedstep_smi 5904 0
speedstep_lib 4484 1 speedstep_smi
cpufreq_userspace 4696 1
cpufreq_stats 5636 0
freq_table 4740 2 speedstep_smi,cpufreq_stats
cpufreq_powersave 1920 0
cpufreq_ondemand 6428 0
cpufreq_conservative 7332 0
video 16260 0
tc1100_wmi 6916 0
sony_acpi 5644 0
pcc_acpi 12416 0
hotkey 11556 0
dev_acpi 11140 0
container 4608 0
button 6672 0
acpi_sbs 19980 0
battery 9988 1 acpi_sbs
ac 5252 1 acpi_sbs
i2c_acpi_ec 5120 1 acpi_sbs
dm_mod 58936 1
md_mod 72532 0
lp 11844 0
af_packet 22920 6
joydev 10048 0
e100 40580 0
ath_pci 80540 0
ath_rate_sample 17160 1 ath_pci
ltserial 11056 0
ltmodem 566638 1 ltserial
mii 5888 1 e100
wlan 144924 3 ath_pci,ath_rate_sample
ath_hal 148816 3 ath_pci,ath_rate_sample
tsdev 8000 0
pcspkr 2180 0
floppy 62148 0
rtc 13492 0
pcmcia 40508 0
parport_pc 35780 1
parport 36296 3 ppdev,lp,parport_pc
psmouse 36100 0
snd_maestro3 25380 1
snd_ac97_codec 93216 1 snd_maestro3
snd_ac97_bus 2304 1 snd_ac97_codec
serio_raw 7300 0
snd_pcm_oss 53664 0
snd_mixer_oss 18688 1 snd_pcm_oss
snd_pcm 89864 3 snd_maestro3,snd_ac97_codec,snd_pcm_oss
snd_timer 25220 1 snd_pcm
snd_page_alloc 10632 1 snd_pcm
snd 55268 8 snd_maestro3,snd_ac97_codec,snd_pcm_oss,snd_mixer_ oss,snd_pcm,snd_timer
i2c_piix4 9104 0
soundcore 10208 1 snd
i2c_core 21904 2 i2c_acpi_ec,i2c_piix4
yenta_socket 28428 3
rsrc_nonstatic 13440 1 yenta_socket
shpchp 45632 0
pci_hotplug 29236 1 shpchp
pcmcia_core 42640 3 pcmcia,yenta_socket,rsrc_nonstatic
intel_agp 22940 1
agpgart 34888 1 intel_agp
evdev 9856 2
ext3 135944 1
jbd 58772 1 ext3
ide_generic 1536 0
uhci_hcd 33808 0
usbcore 130820 2 uhci_hcd
ide_cd 33028 0
cdrom 38560 1 ide_cd
ide_disk 17664 3
piix 11012 1
generic 5124 0
thermal 13576 0
processor 23360 1 thermal
fan 4868 0
capability 5000 0
commoncap 7296 1 capability
vga16fb 13704 1
vgastate 10368 1 vga16fb
fbcon 42784 72
tileblit 2816 1 fbcon
font 8320 1 fbcon
bitblit 6272 1 fbcon
softcursor 2304 1 bitblit
tanuki@pikunikubasukitu:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

ath0 Scan completed :
Cell 01 - Address: 99:99:99:99:99:99
ESSID:"too_ishi_o_ishi_ashi"
Mode:Master
Frequency:2.452 GHz (Channel 9)
Quality=27/94 Signal level=-68 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:wpa_ie=dd180050f20101000050f20201000050f2020 1000050f2020000
Cell 02 - Address: 00:00:00:00:00:00
ESSID:"some_other_ap_not_mine"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=2/94 Signal level=-93 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 22 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:bcn_int=100

sit0 Interface doesn't support scanning.

tanuki@pikunikubasukitu:~$ cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto ath0
iface ath0 inet dhcp
wpa-driver madwifi
wpa-ssid too_ishi_o_ishi_ashi
wpa-ap-scan 1
# wpa-conf managed
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <reallylongjumbleofnumbersbasedonmyapkeywhichworkso nwindowsfine>

# auto wlan0
# iface wlan0 inet dhcp
tanuki@pikunikubasukitu:~$ cat /et/modprobe.d/ndiswrapper
cat: /et/modprobe.d/ndiswrapper: No such file or directory
<probably no data hear because I have an atheros based card>
tanuki@pikunikubasukitu:~$ cat /etc/resolv.conf
search vordesigns.net
nameserver retained from eth0 last connection
nameserver retained from eth0 last connection
tanuki@pikunikubasukitu:~$

tanuki@pikunikubasukitu:~$ sudo ifdown -v ath0
Configuring interface ath0=ath0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/wpasupplicant
wpa_supplicant: ctrl_interface=/var/run/wpa_supplicant
dhclient3 -r -pf /var/run/dhclient.ath0.pid -lf /var/lib/dhcp3/dhclient.ath0.leases ath0
Internet Systems Consortium DHCP Client V3.0.3
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

Listening on LPF/ath0/00:0d:88:aa:a1:a6
Sending on LPF/ath0/00:0d:88:aa:a1:a6
Sending on Socket/fallback
ifconfig ath0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: ctrl_interface=/var/run/wpa_supplicant
wpa_supplicant: terminating wpa_supplicant daemon
Stopped wpa_supplicant (pid 7694).
tanuki@pikunikubasukitu:~$ sudo ifup -v ath0
Configuring interface ath0=ath0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: ctrl_interface=/var/run/wpa_supplicant
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.ath0.pid -i ath0 -C /var/run/wpa_supplicant -D madwifi
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/ath0
wpa_supplicant: wpa-ap-scan : OK
wpa_supplicant: configuring new network block "0"wpa_supplicant: wpa-ssid : OK
wpa_supplicant: wpa-psk : OK
wpa_supplicant: wpa-pairwise : OK
wpa_supplicant: wpa-group : OK
wpa_supplicant: wpa-key-mgmt : OK
wpa_supplicant: wpa-proto : OK
wpa_supplicant: enabling network 0 : OK

dhclient3 -pf /var/run/dhclient.ath0.pid -lf /var/lib/dhcp3/dhclient.ath0.leases ath0
Internet Systems Consortium DHCP Client V3.0.3
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

Listening on LPF/ath0/00:0d:88:aa:a1:a6
Sending on LPF/ath0/00:0d:88:aa:a1:a6
Sending on Socket/fallback
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 4
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
Synchronizing clock to ntp.ubuntu.com...
tanuki@pikunikubasukitu:~$

[venky80]

What confuses me is the fact that the scan says that your router is set to use "WEP-40" as cipher which is referring to WEP, not WPA. WPA supports both TKIP and AES, but certainly not WEP-40 which would defeat the purpose of WPA i.e. enhanced security.

Now... Would you mind changing the cipher from WEP-40 to TKIP on the router? Your client script mentions TKIP ("wpa-pairwise TKIP") so the easiest way from here is to tell your router to use TKIP (WPA) instead of WEP-40.

EDIT:
If you don't have access to the router because it isn't yours, let me know. Then we'll change your script although that's not my preferred solution as WEP-40 is not part of the WPA suite.


I Checked my router settings it is WPA-PSK TKIP
I am attaching the screenshot maybe you might see something I missed
Also I am on Gutsy (yes I know it is supposed to break and yes I know it is for developers and yes I am prepared for data loss) and knetworkmanager is broken so I am trying to connect using good old interfaces
Meanwhile my other laptop which runs feisty shows
iwlist scan as TKIP so it might be a Gutsy bug...well then I really dont know what to do unless u have some tricks
Thanks for all the help

[wieman01]

a. I don't know what MAC filtering is. I have a Speedtouch 580 router and don't know if it supports MAC filtering. Should it be on or off? By the way, before Ubuntu I used Windows XP, and had no problem connecting to the wireless network using WPA so I guess it has to do with the setup of Ubuntu rather then my router.
b. I am not using a firewall on my Ubuntu laptop as far as I know.

I don't think my router has any log files as it is not a computer.
Using the same network interface and turning off security on the router (while commenting the corresponding lines in "interfaces") can you connect to your network using DHCP? WPA handshake seems ok, but for some reason the router does not assign an IP via DHCP.

Please try the unsecured method once again, if that fails would you mind assigning a static IP for a minute? Just for the sake of testing.

[wieman01]

Hi,

Used this document after trying others, still no joy. This is one of the reason I can't get business users to switch to Linux but I'm still trying.

I have tried excluding the eth0 device in the interfaces to no avail. This will work with some tweaking using WEP, been there, done that.
Current status is card show connected briefly then disconnected, cycle and repeat.

This is a fresh install/patch.
Same to you, can you assign a static IP and try once again? Are you sure your wireless card and driver do support WPA? And do router settings match those of your PC?

Sorry for asking these simple questions, but we need to start somewhere. :-)

[wieman01]

I Checked my router settings it is WPA-PSK TKIP
I am attaching the screenshot maybe you might see something I missed
Also I am on Gutsy (yes I know it is supposed to break and yes I know it is for developers and yes I am prepared for data loss) and knetworkmanager is broken so I am trying to connect using good old interfaces
Meanwhile my other laptop which runs feisty shows
iwlist scan as TKIP so it might be a Gutsy bug...well then I really dont know what to do unless u have some tricks
Thanks for all the help
Could you please set WPA to "Enabled" and scan once again? Try various settings there until scanning shows something along these lines:

Cell 01 - Address: 00:13:10:41:A8:E5
ESSID:"<hidden>"
Protocol:IEEE 802.11bg
Mode:Master
Channel:6
Encryption key:on
Bit Rates:54 Mb/s
Extra: Rates (Mb/s): 1 2 5.5 6 9 11 12 18 24 36 48 54
Quality=93/100 Signal level=-35 dBm
IE: IEEE 802.11i/WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Extra: Last beacon: 1996ms ago

Your router settings are incorrect as it expects WEP-40 rather than TKIP.

[VorDesigns]

Same to you, can you assign a static IP and try once again? Are you sure your wireless card and driver do support WPA? And do router settings match those of your PC?

Sorry for asking these simple questions, but we need to start somewhere. :-)

No problem, I won't treat you like I would an MS, CA, Infor, or Intuit grunt reading a script and thank you for the help.
--
Cllient Wireless NIC
================================================== ===========
DWL-G650
version B4
reported as compatible with madwifi
http://madwifi.org/wiki/Compatibility/D-Link-
D-Link asserts that this card supports
- 64 bit and 128 WEP
- 802.1x
- WPA Wi-Fi Protected Access
- WPA PSK (Pre-Shared Key)
http://www.dlink.com/products/resource.asp?pid=11&rid=34&sec=0
-

Access Point Wireless to wired host
================================================== ===========
Linksys WRT54GL
Firmware version v4.30.5, Apr. 27, 2006
Security Mode: WPA Personal
WPA Algoritims: TKIP
================================================== ===========
Set client to static: Fails connectivity.
Air Snare running on Windows client connected to AP showed
intermittent reports of wireless intruder. <edit> I unregistered the MAC address of the D-Link card so
that Air Snare would let me know. <edit>
Visual monitoring of the DWL-G650 card shows intermittent
connection to the AP, LED's flash in unison, of about two seconds and then returns
to unconnected state, LED's cycle.
================================================== ===========
<edit>
This system/card configuration worked great with WEP.
I am using an internal DHCP server not the Linksys WRT54GL and it is leasing IP addresses successfully
to two Windows systems running on the same WRT54GL router.<edit>

[venky80]

Could you please set WPA to "Enabled" and scan once again? Try various settings there until scanning shows something along these lines:

Your router settings are incorrect as it expects WEP-40 rather than TKIP.

well that is what is puzzling coz I have a laptop with feisty which connects to the same wireless router and the one I am trying to fix is running gutsy

the gutsy gibbon laptop iwlist scan shows for my wireless as


Address: 00:0C:E5:4E:88:2F
ESSID:"wastintime"
Protocol:IEEE 802.11bg
Mode:Master
Channel:11
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=98/100 Signal level=-26 dBm Noise level=-26 dBm
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : PSK
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : PSK
Extra: Last beacon: 256ms ago

but for the same wireless connection my feisty laptop shows this


Address: 00:0C:E5:4E:88:2F
ESSID:"wastintime"
Protocol:IEEE 802.11bg
Mode:Master
Channel:11
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality:96 Signal level:0 Noise level:0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK

[WhiteHorse]

Hi I tried this and about 40 other things to no avail. I tried the wpa_supplicant stuff(all versions), I tried the /etc/network/interfaces stuff(all versions), I downloaded beta drivers, recompiled modules, tried RAconfig2500 or whatever it's called, tried latest CVS drivers, rebooted about 20 times, reinstalled ubuntu, etc(oh yeah and the ndiswrapper). It's been 28 hours of work and now I've given up.

Here's what works:
I can connect with WEP(oh joy) through System->Amin->Network and I disable roaming and set my wep key in there. It works flawlessly.

iwconfig shows:
ra0 RT2500 Wireless ESSID:"myessid"
Mode:Managed Frequency=2.412 GHz Access Point: 00:14:BF:0F:CE:27
Bit Rate=54 Mb/s Tx-Power:0 dBm
RTS thr:off Fragment thr:off
Link Quality=63/100 Signal level=-65 dBm Noise level:-192 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

my dmesg output shows:
[ 37.794864] rt2500 1.1.0 BETA4 2006/06/18 http://rt2x00.serialmonkey.com
[ 37.912497] rt2500 EEPROM: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 Channel
[ 37.912505] rt2500 EEPROM: 4 4 4 4 4 4 3 3 3 3 3 3 3 3 dBm Maximum
[ 51.609223] ra0: no IPv6 routers present

lspci shows:
02:09.0 Network controller: RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01)

lsmod shows:
rt2500 202088 1

/etc/network/interfaces shows:
auto lo
iface lo inet loopback

iface ra0 inet dhcp
wireless-essid myessid
wireless-key myweakasswepkey

auto ra0

Here's what doesn't work:
WPA/WPA2 and nm-applet. When I try to use the nm-applet( for n00biez:the computer icon in the task bar) I can connect to a network only if it is broadcasting it's network ssid and has no wep(eg open). otherwise, if wep is enabled, it asks for the key and then just hangs and says "Waiting for network key". There is no option to select anything other than wep.

My Configuration:
Feisty(7.04)
amd64(MS-1029 aka megabook 635)
minipci Ralink rt2500

Summary:
I know the card supports it because I can use wpa on windows. The access point is a standard OpenWRT Linksys WRT54G. I read some bug reports and it appears this may be a known bug with network manager, something to do with wireless extensions that network manager uses aren't compatible with the extensions available on the rt2500 driver. I have read as many posts and how-to's as I could and I just wound up with a really screwed up system and no WPA.

To be honest, the 28 hours I lost on this could have been better spent on the other open source projects I contribute to and has(according to other posts) cost a lot of other people time wasted as well. Can't we just PUSH A GODDAM UPDATE THAT FIXES THIS CRAP???? I mean make 2 developers waste one day rather than 2000 users/developers/testers/potential devs waste 3 days each? Not to flame anybody but hopefully I can spark some response on the part of the Ubuntu team to get this fixed. Any suggestions at this point would be great, thanks. I have 8 wireless networks in proximity and I'm sure someone has sniffed my passwords and arp poisoned me already. I'll just keep changing my wep key every day and never send passwords in the clear on my wireless or my lan until something comes along.

](*,) :-x :cry:

[wieman01]

No problem, I won't treat you like I would an MS, CA, Infor, or Intuit grunt reading a script and thank you for the help.
--
Cllient Wireless NIC
================================================== ===========
DWL-G650
version B4
reported as compatible with madwifi
http://madwifi.org/wiki/Compatibility/D-Link-
D-Link asserts that this card supports
- 64 bit and 128 WEP
- 802.1x
- WPA Wi-Fi Protected Access
- WPA PSK (Pre-Shared Key)
http://www.dlink.com/products/resource.asp?pid=11&rid=34&sec=0
-

Access Point Wireless to wired host
================================================== ===========
Linksys WRT54GL
Firmware version v4.30.5, Apr. 27, 2006
Security Mode: WPA Personal
WPA Algoritims: TKIP
================================================== ===========
Set client to static: Fails connectivity.
Air Snare running on Windows client connected to AP showed
intermittent reports of wireless intruder. <edit> I unregistered the MAC address of the D-Link card so
that Air Snare would let me know. <edit>
Visual monitoring of the DWL-G650 card shows intermittent
connection to the AP, LED's flash in unison, of about two seconds and then returns
to unconnected state, LED's cycle.
================================================== ===========
<edit>
This system/card configuration worked great with WEP.
I am using an internal DHCP server not the Linksys WRT54GL and it is leasing IP addresses successfully
to two Windows systems running on the same WRT54GL router.<edit>
Looks ok to me. Would you mind trying static IP instead of DHCP?

Another idea would be (as mentioned by another user in earlier posts) to disable "roaming" using the networking applet.

[wieman01]

well that is what is puzzling coz I have a laptop with feisty which connects to the same wireless router and the one I am trying to fix is running gutsy

the gutsy gibbon laptop iwlist scan shows for my wireless as


Address: 00:0C:E5:4E:88:2F
ESSID:"wastintime"
Protocol:IEEE 802.11bg
Mode:Master
Channel:11
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=98/100 Signal level=-26 dBm Noise level=-26 dBm
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : PSK
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : PSK
Extra: Last beacon: 256ms ago

but for the same wireless connection my feisty laptop shows this


Address: 00:0C:E5:4E:88:2F
ESSID:"wastintime"
Protocol:IEEE 802.11bg
Mode:Master
Channel:11
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality:96 Signal level:0 Noise level:0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
That is indeed odd. Perhaps something IS wrong with Gutsy at this stage... No idea how I can help you there.

[wieman01]

Hi I tried this and about 40 other things to no avail. I tried the wpa_supplicant stuff(all versions), I tried the /etc/network/interfaces stuff(all versions), I downloaded beta drivers, recompiled modules, tried RAconfig2500 or whatever it's called, tried latest CVS drivers, rebooted about 20 times, reinstalled ubuntu, etc(oh yeah and the ndiswrapper). It's been 28 hours of work and now I've given up.
RT2500 (Ralink) is a bit of a headache as Serialmonkey's driver does not quite work the way others do. As a consequence wpa-supplicant won't help you and you need to do some extra work. Check this out:

http://rt2x00.serialmonkey.com/phpBB2/viewtopic.php?p=21546&sid=c5e02ed97dde07681fb564639e9f50c5

I'll update my HOWTO and mention this issue like I used to in the past. Install "ndiswrapper" if you prefer to do it our way. That's all I can say... I have a RT25700 as well and I only got this working after deploying the Windows driver.

EDIT:
You find stuff here as well:

http://ubuntuforums.org/showthread.php?t=202834&page=30

[mksec]

Nå. I have a headache with this. I'm sue something really obvious is missing but i can't figure it out. I'm posting all my config info from the stumped part of your excellent tutorial. So close yet so far.

I can see my network. I have the card working. But can't seem to connect to it. Ideas most appreciated.


uname -a
Linux laptop 2.6.20-15-386 #2 Sun Apr 15 07:34:00 UTC 2007 i686 GNU/Linux

ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:08:02:D9:8E:E5
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:11

eth1 Link encap:Ethernet HWaddr 00:07:40:DC:28:08
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:21 overruns:0 frame:0
TX packets:35538 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:1564168 (1.4 MiB)
Interrupt:10 Base address:0x8000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:110 errors:0 dropped:0 overruns:0 frame:0
TX packets:110 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:9760 (9.5 KiB) TX bytes:9760 (9.5 KiB)

vmnet1 Link encap:Ethernet HWaddr 00:50:56:C0:00:01
inet addr:172.16.210.1 Bcast:172.16.210.255 Mask:255.255.255.0
inet6 addr: fe80::250:56ff:fec0:1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:42 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

vmnet8 Link encap:Ethernet HWaddr 00:50:56:C0:00:08
inet addr:192.168.63.1 Bcast:192.168.63.255 Mask:255.255.255.0
inet6 addr: fe80::250:56ff:fec0:8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:42 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)


route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
172.16.210.0 0.0.0.0 255.255.255.0 U 0 0 0 vmnet1
192.168.63.0 0.0.0.0 255.255.255.0 U 0 0 0 vmnet8


iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

eth1 IEEE 802.11b/g ESSID:"MKSEC" Nickname:"MKSEC"
Mode:Managed Frequency=2.484 GHz Access Point: Invalid
Bit Rate=1 Mb/s Tx-Power=15 dBm
RTS thr:off Fragment thr:off
Link Quality=0/100 Signal level=-256 dBm Noise level=-256 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

vmnet1 no wireless extensions.

vmnet8 no wireless extensions.


[B]ifconfig
eth0 Link encap:Ethernet HWaddr 00:08:02:D9:8E:E5
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:11

eth1 Link encap:Ethernet HWaddr 00:07:40:DC:28:08
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:21 overruns:0 frame:0
TX packets:36034 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:1586984 (1.5 MiB)
Interrupt:10 Base address:0x8000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:110 errors:0 dropped:0 overruns:0 frame:0
TX packets:110 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:9760 (9.5 KiB) TX bytes:9760 (9.5 KiB)

vmnet1 Link encap:Ethernet HWaddr 00:50:56:C0:00:01
inet addr:172.16.210.1 Bcast:172.16.210.255 Mask:255.255.255.0
inet6 addr: fe80::250:56ff:fec0:1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:42 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

vmnet8 Link encap:Ethernet HWaddr 00:50:56:C0:00:08
inet addr:192.168.63.1 Bcast:192.168.63.255 Mask:255.255.255.0
inet6 addr: fe80::250:56ff:fec0:8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:42 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

lsmod
Module Size Used by
nls_iso8859_1 4224 0
nls_cp437 5888 0
vfat 12800 0
fat 52380 1 vfat
ipv6 252512 8
binfmt_misc 11272 1
rfcomm 37660 0
l2cap 22276 5 rfcomm
bluetooth 51300 4 rfcomm,l2cap
vmnet 36388 13
vmmon 111244 0
ppdev 9220 0
radeon 123680 3
drm 79380 4 radeon
speedstep_centrino 8072 0
cpufreq_userspace 4116 0
cpufreq_stats 5508 0
cpufreq_powersave 1792 0
cpufreq_ondemand 7676 1
freq_table 4740 3 speedstep_centrino,cpufreq_stats,cpufreq_ondemand
cpufreq_conservative 6560 0
tc1100_wmi 7172 0
pcc_acpi 12160 0
dev_acpi 11140 0
sony_acpi 5388 0
video 15492 0
sbs 14752 0
i2c_ec 4992 1 sbs
i2c_core 21776 1 i2c_ec
dock 9216 0
button 7696 0
battery 9860 0
container 4352 0
ac 5124 0
asus_acpi 16412 0
backlight 6016 1 asus_acpi
fuse 44436 1
lp 11332 0
bcm43xx 123924 0
joydev 9920 0
snd_intel8x0 32796 1
snd_ac97_codec 97184 1 snd_intel8x0
ac97_bus 2304 1 snd_ac97_codec
snd_pcm_oss 43264 0
snd_mixer_oss 16512 1 snd_pcm_oss
snd_pcm 76680 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
ieee80211softmac 30720 1 bcm43xx
ieee80211 33608 2 bcm43xx,ieee80211softmac
ieee80211_crypt 6144 1 ieee80211
snd_seq_dummy 3844 0
snd_seq_oss 31616 0
irtty_sir 8448 0
sir_dev 15748 1 irtty_sir
pcmcia 38316 0
snd_seq_midi 8576 0
snd_rawmidi 24448 1 snd_seq_midi
snd_seq_midi_event 7424 2 snd_seq_oss,snd_seq_midi
snd_seq 49648 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_mid i_event
snd_timer 22276 2 snd_pcm,snd_seq
snd_seq_device 8204 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi ,snd_seq
irda 191036 2 irtty_sir,sir_dev
snd 51716 12 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_ oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_ti mer,snd_seq_device
rtc 13104 0
pcspkr 3072 0
parport_pc 34980 1
parport 35272 3 ppdev,lp,parport_pc
crc_ccitt 2176 1 irda
soundcore 7520 1 snd
psmouse 37640 0
serio_raw 6916 0
yenta_socket 26636 3
rsrc_nonstatic 13184 1 yenta_socket
pcmcia_core 39696 3 pcmcia,yenta_socket,rsrc_nonstatic
snd_page_alloc 9992 2 snd_intel8x0,snd_pcm
intel_agp 24220 1
agpgart 34096 2 drm,intel_agp
iTCO_wdt 10656 0
iTCO_vendor_support 3972 1 iTCO_wdt
af_packet 20872 6
shpchp 33300 0
pci_hotplug 31160 1 shpchp
evdev 10112 4
tsdev 7872 0
ext3 129288 1
jbd 53032 1 ext3
mbcache 8196 1 ext3
sg 35484 0
sr_mod 15908 0
cdrom 36512 1 sr_mod
sd_mod 22292 4
usb_storage 70976 1
libusual 17040 1 usb_storage
ata_piix 14596 4
ata_generic 8196 0
libata 125208 2 ata_piix,ata_generic
scsi_mod 141580 5 sg,sr_mod,sd_mod,usb_storage,libata
floppy 58020 0
tg3 107396 0
generic 4228 0 [permanent]
ehci_hcd 32780 0
uhci_hcd 23952 0
usbcore 131480 5 usb_storage,libusual,ehci_hcd,uhci_hcd
raid10 24704 0
raid456 123408 0
xor 15752 1 raid456
raid1 23936 0
raid0 8704 0
multipath 8832 0
linear 6400 0
md_mod 77076 7 raid10,raid456,raid1,raid0,multipath,linear
thermal 13832 0
processor 22956 1 thermal
fan 4740 0
dm_mod 57164 5
fbcon 41760 0
tileblit 2688 1 fbcon
font 8320 1 fbcon
bitblit 6016 1 fbcon
softcursor 2304 1 bitblit
vesafb 8196 0
capability 5000 0
commoncap 7296 1 capability

iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:A0:C5:63:80:1E
ESSID:"neighbourtotheleftofme"
Protocol:IEEE 802.11b
Mode:Master
Channel:6
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Quality=79/100 Signal level=-71 dBm Noise level=-71 dBm
Extra: Last beacon: 3260ms ago
Cell 02 - Address: 00:13:49:CE:88:2D
ESSID:"jokertotheright"
Protocol:IEEE 802.11bg
Mode:Master
Channel:6
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 22 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Quality=72/100 Signal level=-77 dBm Noise level=-71 dBm
Extra: Last beacon: 3256ms ago
Cell 03 - Address: 00:14:85:0D:C7:76
ESSID:"MKSEC"
Protocol:IEEE 802.11bg
Mode:Master
Channel:1
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 9 Mb/s; 11 Mb/s
6 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=88/100 Signal level=-60 dBm Noise level=-71 dBm
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : TKIP CCMP
Authentication Suites (1) : PSK
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : TKIP CCMP
Authentication Suites (1) : PSK
Preauthentication Supported
Extra: Last beacon: 3336ms ago

vmnet1 Interface doesn't support scanning.

vmnet8 Interface doesn't support scanning.


cat /etc/network/interfaces

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# This is a list of hotpluggable network interfaces.
# They will be activated automatically by the hotplug subsystem.


# The primary network interface


auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-ssid MKSEC
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk HEXKEY as stated in tutorial

sudo cat /etc/modprobe.d/ndiswrapper
alias wlan0 ndiswrapper

cat /etc/resolv.conf
# generated by NetworkManager, do not edit!

search opasia.dk


nameserver 192.168.2.1

[wieman01]

Nå. I have a headache with this. I'm sue something really obvious is missing but i can't figure it out. I'm posting all my config info from the stumped part of your excellent tutorial. So close yet so far.
I have made slight changes as I don't know if your card supports WPA2. Please try this one first and let me know if this works for you:

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-ssid MKSEC
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise CCMP TKIP
wpa-group CCMP TKIP
wpa-key-mgmt WPA-PSK
wpa-psk HEXKEY as stated in tutorial
Then restart the network:

sudo /etc/init.d/networking restart
Please post the results.

And by the way... please state what card you have got. IPW2200 by chance?

[mksec]

whatcha know!!! It worked. Thanks alot. I knew it was something obvious.

Card is a Buffalo WLI-CB-G54Awith a broadcom chipset. I installed it using bcm43xx-fwcutter.


Thanks again.

[venky80]

That is indeed odd. Perhaps something IS wrong with Gutsy at this stage... No idea how I can help you there.

How can I report a bug. I mean I dont even know how to point out this problem

[wieman01]

How can I report a bug. I mean I dont even know how to point out this problem
You can file bugs here (https://launchpad.net/ubuntu). Let me know if you need a hand.

[VorDesigns]

Hi,

I gave up on using the interfaces and went to trying nm-applet; post the headscratching and commenting out almost everything in the interfaces file as directed, I was able to get the nm-applet to function.
I still couldn't connect.
So, I decided that I must have introduced an operator error into the process based on Windows laxity; I was correct. While I entered the psk in lower case on the Windows systems, the key itself is displayed in upper case on the router. I reentered the key substituting upper-case for all the alpha key characters and was prompted for a key-ring password.
I stopped to thank you for your assistance using my now functional connection prior to reactivating the eth0 device.
Again, thank you for your help.
I am debating whether to go back and put everything into the interfaces file but, having a functional nm-applet gives my the ability to roam a little more simply.

[venky80]

You can file bugs here (https://launchpad.net/ubuntu). Let me know if you need a hand.
yes definitely so that i can make an impact with the submission
Thanks

[Skolem45]

Thank you!!! It worked. After two days of bashing my head against the table, I finally have working WPA. Its just WPA1, that's all that my router will support, but still. My card is Airlink101 AWLH3026T; I'm using ndiswrapper.

:)

[Zoufiax]

Using the same network interface and turning off security on the router (while commenting the corresponding lines in "interfaces") can you connect to your network using DHCP? WPA handshake seems ok, but for some reason the router does not assign an IP via DHCP.

Please try the unsecured method once again, if that fails would you mind assigning a static IP for a minute? Just for the sake of testing.

What do you mean with turning security off on the router? Setting it to WEP or no encryption / protection? When I set it to WEP I can connect to my router. Also when I had Windows XP installed on my laptop, I could connect with WPA security.

Also I do want to assign a static IP to my laptop, but please tell me how to do that. And with WPA or WEP security or something else? I hope you don't mind my ignorance...

[wieman01]

What do you mean with turning security off on the router? Setting it to WEP or no encryption / protection? When I set it to WEP I can connect to my router. Also when I had Windows XP installed on my laptop, I could connect with WPA security.

Also I do want to assign a static IP to my laptop, but please tell me how to do that. And with WPA or WEP security or something else? I hope you don't mind my ignorance...
Let's configure your PC to use static IP then:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto wlan0
iface wlan0 inet static
address 192.168.1.xxx
gateway 192.168.1.xxx
dns-nameservers 192.168.1.xxx
netmask 255.255.255.0
wpa-driver wext
wpa-ssid <your_essid>
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <your_hex_key>
Please replace the blue bits with your networks IP range and desired client IP. If you don't know what I am referring to, please post your router's IP address. I will give you a hand.

Please use upper case for the the hex key (I assume you have generated the key the way I have suggested in my tutorial). Then restart the network:

sudo /etc/init.d/networking restart
Post the contents of "interfaces", etc. after that.

[waylow]

hey thanks for the helpful thread

I have managed to get my wireless internet working - the only thing that didn't work was trying to get it automated

I created the sh file and followed the instructions but it gave a DCHP -sleeping message

I then had to delete the .sh file and sybolic link (whatever that is) to get it able to work again


what did I do worng when I made the .sh file?


thanks

[wieman01]

hey thanks for the helpful thread

I have managed to get my wireless internet working - the only thing that didn't work was trying to get it automated

I created the sh file and followed the instructions but it gave a DCHP -sleeping message

I then had to delete the .sh file and sybolic link (whatever that is) to get it able to work again


what did I do worng when I made the .sh file?


thanks
Not sure what you did in the first place. :-)

Seriously, static IP will resolve your problem with having to restart the network. Want to try that instead?

[waylow]

Not sure what you did in the first place. :-)

neither am I - going to try it again and see how it goes



Seriously, static IP will resolve your problem with having to restart the network. Want to try that instead?
I can't because it isn't my network - just moved into my brothers house and thats the way he wants it to stay

the network does seem to stop working and I have to restart it again

but sometimes that doesn't work and I need to reboot then restart

I'm assuming that has to do with the dhcp renewal

bound to 192.168.0.3 -- renewal in 41716 seconds

anything I can do (apart from convince my brother to change it to static)??

[wieman01]

neither am I - going to try it again and see how it goes


I can't because it isn't my network - just moved into my brothers house and thats the way he wants it to stay

the network does seem to stop working and I have to restart it again

but sometimes that doesn't work and I need to reboot then restart

I'm assuming that has to do with the dhcp renewal

bound to 192.168.0.3 -- renewal in 41716 seconds

anything I can do (apart from convince my brother to change it to static)??
Actually you could use a static IP configuration anytime you want. Just use the IP address that you were assigned before and use 192.168.0.3 as DNS and gateway. That's all you need to do. Then restart the network and there you go. :-) There won't be any sort of conflict with DHCP of course.

[waylow]

Actually you could use a static IP configuration anytime you want. Just use the IP address that you were assigned before and use 192.168.0.3 as DNS and gateway. That's all you need to do. Then restart the network and there you go. :-) There won't be any sort of conflict with DHCP of course.

GREAT!!:) I don't know exactly how to do that but you have given me enough to go on

thanks heaps :KS

-waylow
-over

[wieman01]

GREAT!!:) I don't know exactly how to do that but you have given me enough to go on

thanks heaps :KS

-waylow
-over
Just follow the steps on page 1 of this thread. That should do. If you still have problems, just post here, buddy. :-)

[waylow]

Yep still seem to be having trouble trying to change it to static
I am confused a bit about making it static


Actually you could use a static IP configuration anytime you want. Just use the IP address that you were assigned before and use 192.168.0.3 as DNS and gateway. That's all you need to do. Then restart the network and there you go. :-) There won't be any sort of conflict with DHCP of course.

I am confused as to what address I should use

here is my /etc/network/interfaces file



auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet static
#iface wlan0 inet dchp

#not sure what addresses are correct and which are wrong
#I comment out the next bit and switch the comment
#on the dchp line above to the static one and
#the internet sometimes connects - for about 3 - 4 minutes

address 192.168.0.1
gateway 192.168.0.3
dns-nameservers 192.168.0.3
netmask 255.255.255.0

wpa-driver wext
wpa-ssid Megadeth
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk (really long hex PSK Key)


am I mental in the brain?

[wieman01]

Yep still seem to be having trouble trying to change it to static
I am confused a bit about making it static



I am confused as to what address I should use

here is my /etc/network/interfaces file



auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet static
#iface wlan0 inet dchp

#not sure what addresses are correct and which are wrong
#I comment out the next bit and switch the comment
#on the dchp line above to the static one and
#the internet sometimes connects - for about 3 - 4 minutes

address 192.168.0.1
gateway 192.168.0.3
dns-nameservers 192.168.0.3
netmask 255.255.255.0

wpa-driver wext
wpa-ssid Megadeth
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk (really long hex PSK Key)


am I mental in the brain?
You are not. :-) Your configuration looks actually quite correct. The only thing that you need to find out about is what "address" you should actually use:

address 192.168.0.xxx
The problem is that the router reserves certain IP ranges for its clients. So you must pick one that is within that range (e.g. address 192.168.0.4 - address 192.168.0.10).

What IP address were you assigned while you used DHCP? You could use that one. Or ask you brother what IP range he is using, so that you could pick one. Just make sure you pick an address that does not conflict with one that the router assign's to your bother's PC, if you know what I mean. IPs are unique.

[waylow]

just a quick update

I have changed my interfaces file back to:


auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dchp


then I restarted the network and it seemed to work fine - I tested it for about 30mins or so and the internet was working the whole time (that's the longest it has managed to work)

then I rebooted and it doesn't want to work - even after trying to restart the network several times
-it says it's sleeping

WAKE UP DAMMIT

any ideas??

[waylow]

You are not. :-) Your configuration looks actually quite correct. The only thing that you need to find out about is what "address" you should actually use:

The problem is that the router reserves certain IP ranges for its clients. So you must pick one that is within that range (e.g. address 192.168.0.4 - address 192.168.0.10).

What IP address were you assigned while you used DHCP? You could use that one. Or ask you brother what IP range he is using, so that you could pick one. Just make sure you pick an address that does not conflict with one that the router assign's to your bother's PC, if you know what I mean. IPs are unique.

OK so I have uncommented the bits that I need to (changing back to static)

the IP that I have managed to connect on is alway 192.168.0.3

Is this the one I use for the
address
gateway
or dns

Thanks for your help too - by the way

it has been greatly appreciated

waylow

[waylow]

YAY! I seem to have figured it out

tried it a few different combo's and got it to work with a static address

The only thing now is to get it to happen on boot
but I will sort that out tommorrow

Thanks A LOT for your help
(hopefully I won't need it again for this wireless problem - touch wood)

I have only been using Linux for less than a week now but I feel like I have had a crash course

TA
Have a Good Week end:):)

-waylow

[wieman01]

YAY! I seem to have figured it out

tried it a few different combo's and got it to work with a static address

The only thing now is to get it to happen on boot
but I will sort that out tommorrow

Thanks A LOT for your help
(hopefully I won't need it again for this wireless problem - touch wood)

I have only been using Linux for less than a week now but I feel like I have had a crash course

TA
Have a Good Week end:):)

-waylow
Have a nice weekend too. :-)

As for your boot problem, see post #2 of this thread. I am sure you will be able to fix it. If not, you know where you find me.

[waylow]

I am having trouble with the instructions for post #2

can't get it to restart the network at boot

I have created the .sh script - changed the permission - then created the symbolic link

you mention that you might need to change the number of the boot sequence from S40

well on my system there was S40networking (I'm not sure if this is the thing that we are trying to restart so I tried 2 things)
I have tried changing this the S40wireless-network file to S41 and S39 - both end up with me still having to restart the network manually

drawing a blank now:confused:

[wieman01]

I am having trouble with the instructions for post #2

can't get it to restart the network at boot

I have created the .sh script - changed the permission - then created the symbolic link

you mention that you might need to change the number of the boot sequence from S40

well on my system there was S40networking (I'm not sure if this is the thing that we are trying to restart so I tried 2 things)
I have tried changing this the S40wireless-network file to S41 and S39 - both end up with me still having to restart the network manually

drawing a blank now:confused:
What happens when you execute the script?

sudo /etc/init.d/wireless-network.sh
Does that restart the network? And what about:

sudo /etc/rcS.d/S40wireless-network

[waylow]

What happens when you execute the script?

Does that restart the network? And what about:

yep they both restart the network


aahh crap now I'm having trouble connecting at all
-I haven't changed any setting to when it worked for over 30mins

[waylow]

OK managed to get it back up

but I had to change the static address in the interfaces file from 192.168.0.3 to 192.168.0.4

does this mean that I haven't got the interfaces file setup correctly?

(trying to re-do the auto restart at boot again)

[wieman01]

OK managed to get it back up

but I had to change the static address in the interfaces file from 192.168.0.3 to 192.168.0.4

does this mean that I haven't got the interfaces file setup correctly?

(trying to re-do the auto restart at boot again)
192.168.0.3 is your router? Perhaps it is best if you posted the contents of your "interfaces" file once again for reference.

EDIT:
Also post the results of this one please:

route

[waylow]

my router is 192.168.0.1 - the .3 was the only IP I manged to get connected on before

anyway here is my interfaces - (typed by hand - don't know how to share drives with windows (yet) and I am getting my removable media fixed ie. my iRiver is getting fixed so I can't just pop it into a text file and transfer it across)

interfaces


auto lo
iface lo inet loopback

auto wlan0
iface wlan inet static

address 192.168.0.3
gateway 192.168.0.1
dns-nameserver192.168.0.3
netmask 255.255.255.0

wpa-driver wext
wpa-ssid Megadeth
wpa-ap scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk MY PSK


route


Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 wlan0
link-local * 255.255.0.0 U 1000 0 0 wlan0
default 192.168.0.1 0.0.0.0 UG 0 0 0 wlan0



does it look wrong (except for the formatting - sorry :( stupid broken iRiver)

[wieman01]

my router is 192.168.0.1 - the .3 was the only IP I manged to get connected on before

anyway here is my interfaces - (typed by hand - don't know how to share drives with windows (yet) and I am getting my removable media fixed ie. my iRiver is getting fixed so I can't just pop it into a text file and transfer it across)

interfaces


auto lo
iface lo inet loopback

auto wlan0
iface wlan inet static

address 192.168.0.3
gateway 192.168.0.1
dns-nameserver192.168.0.3
netmask 255.255.255.0

wpa-driver wext
wpa-ssid Megadeth
wpa-ap scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk MY PSK

"dns-nameserver" and "gateway" should both point to your router, hence the IP address should be 192.168.0.3:

auto lo
iface lo inet loopback

auto wlan0
iface wlan inet static

address 192.168.0.3
gateway 192.168.0.1
dns-nameserver 192.168.0.1
netmask 255.255.255.0

wpa-driver wext
wpa-ssid Megadeth
wpa-ap scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk MY PSK
But this might be a typo. Otherwise you would not have been able to browse the web.

Your scripts look actually fine, your network should restart automatically while your system is booting. So it surprises me you need to do another manual restart after logging on to your system. I am running out of ideas here to be honest.

Another thing is that you need to have a chat with your system admin... The reason is that your manually assigned IP address may conflict with other PC clients on your network. DHCP assigns IP address within a certain range e.g. 192.168.0.2 to 192.168.0.10 and the more clients there are, the more likely it is that one client is assigned the same address as you. To avoid this from happening you should pick an IP address outside that range reserved for DHCP.

[waylow]

yeah I found out why I was getting kicked off
the other flatmate also uses the network (which I didn't know) - so when he turns on his laptop - he was getting assigned the .3 address and kicking me off

I have changed it to .200 so I shouldn't have any problems now (I hope - well not so far anyway)

no that wasn't a typo

I know that the DNS and gateway should be the same (192.168.0.1 - but it hasn't been working)

it seems to work when it's the same my my computers IP address - I am confused too

I wiil try and change it again and see how I go


with the startup script - I give up
I have come to the sad realization that I will probably have to restart it manually every time i boot

It doesn't really bother me that much - at least I will be reminded daily of the help you have given me wieman01 :)

Thanks a bunch -
(I know where to find you if I have spoken too soon)

waylow
over

[wieman01]

yeah I found out why I was getting kicked off
the other flatmate also uses the network (which I didn't know) - so when he turns on his laptop - he was getting assigned the .3 address and kicking me off

I have changed it to .200 so I shouldn't have any problems now (I hope - well not so far anyway)

no that wasn't a typo

I know that the DNS and gateway should be the same (192.168.0.1 - but it hasn't been working)

it seems to work when it's the same my my computers IP address - I am confused too

I wiil try and change it again and see how I go


with the startup script - I give up
I have come to the sad realization that I will probably have to restart it manually every time i boot

It doesn't really bother me that much - at least I will be reminded daily of the help you have given me wieman01 :)

Thanks a bunch -
(I know where to find you if I have spoken too soon)

waylow
over
No problem then. Nice talking to you anyway.

One last word concerning the DNS setting... You PC should actually synchronize your interfaces file and this one:

sudo gedit /etc/resolv.conf
Occasinally the system would not update the file for a reason unknown to me, therefore it's worth taking a look at it. It should contain your router's / gateway's IP address i.e. 192.168.0.1. I suspect it does not at the moment.

Good luck, mate!

[waylow]

yeah I managed to fix that one on my lonesome :)



No problem then. Nice talking to you anyway.

ditto!!

I will have another go at the script when I learn more about Linux - been about 4 days so far (proper dual boot - virtual machine about 2 weeks) and my head is about to explode

[gatoruss]

I recently upgrade to ubuntu 7.4. Prior to upgrade, I had wi running fine...and as best I can recall, I got it to run following instructions at the top of this tutorial for wpa1/broadcast.

After installation of 7.4, I no loinger have connection. I tried reconfiguring with the tutorial, but it is not working. I have tried both wlan0 and ra0. IN the case of the former, when I run restart I am told that there is no such device. When I used ra0 I am told it is "sleeping."

Here are some of the settings/results I am getting.

I would greatly appreciate any help.

My iface:


iface auto lo
iface lo inet loopback

auto ra0
iface ra0 inet dhcp
wpa-driver wext
wpa-ssid linksys_SES_4032
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk ***********************

Restart:


* Reconfiguring network interfaces...
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/ra0/00:18:f8:28:ee:bf
Sending on LPF/ra0/00:18:f8:28:ee:bf
Sending on Socket/fallback
DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 4
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

ifconfig:


eth0 Link encap:Ethernet HWaddr 00:01:80:52:62:F9
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:16 Base address:0x6000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:122 errors:0 dropped:0 overruns:0 frame:0
TX packets:122 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:11350 (11.0 KiB) TX bytes:11350 (11.0 KiB)

ra0 Link encap:Ethernet HWaddr 00:18:F8:28:EE:BF
inet6 addr: fe80::218:f8ff:fe28:eebf/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:2586 errors:0 dropped:0 overruns:0 frame:0
TX packets:11159 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:297100 (290.1 KiB) TX bytes:0 (0.0 b)
Interrupt:19

ra0:avahi Link encap:Ethernet HWaddr 00:18:F8:28:EE:BF
inet addr:169.254.9.244 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Interrupt:19

iwlist scan:


lo Interface doesn't support scanning.
eth0 Interface doesn't support scanning.
ra0 Failed to read scan data : Device or resource busy

Someone suggested that since I had a linksys I should try item #6 under "Common stumbling blocks":


6. RTxxx (Ralink) drivers do not support this approach. Either install "ndiswrapper" replacing Serialmonkey's driver or visit this site.

I followed the link and wrote the script, but have no idea what to do with it! :-)

[wieman01]

I followed the link and wrote the script, but have no idea what to do with it! :-)
Ralink is a different story as you have found out. Do this:

sudo gedit /etc/network/interfaces
And probably paste this:

auto ra0
iface ra0 inet dhcp
pre-up iwconfig ra0 essid Blackhole
pre-up iwpriv ra0 set NetworkType=Infra
pre-up iwpriv ra0 set AuthMode=WPA2PSK
pre-up iwpriv ra0 set EncrypType=AES
pre-up iwpriv ra0 set WPAPSK="your_password"
Then restart the network and see how it goes:

sudo /etc/init.d/networking restart
If you can't restart the network successfully reboot the PC please.

I have not tried this myself though...

EDIT:
You'd probably would want to install "ndiswrapper" and use the latest Windows driver for your card. Personally I find the RTxxxx drivers quite troublesome.

[gatoruss]

Alas....that did not work. When I run restart (even after reboot), no wifi.

When I restart I get this:


* Reconfiguring network interfaces...
RTNETLINK answers: No such process
There is already a pid file /var/run/dhclient.ra0.pid with pid 5610
killed old client process,

removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems

Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Listening on LPF/ra0/00:18:f8:28:ee:bf
Sending on LPF/ra0/00:18:f8:28:ee:bf
Sending on Socket/fallback
Interface doesn't accept private ioctl...
set (8BE2): Invalid argument
Failed to bring up ra0.

Strange thing is that before upgrade it worked fine.


You'd probably would want to install "ndiswrapper" and use the latest Windows driver for your card. Personally I find the RTxxxx drivers quite troublesome.

How do I do this? I have no internet connection for my ubuntu box. I suppose I have download ndiswrapper from my xp machine (PC I am using for this post) and copy it over on a thumb drive? I have never loaded anything on my ubuntu machine without using syanaptic?

[wieman01]

How do I do this? I have no internet connection for my ubuntu box. I suppose I have download ndiswrapper from my xp machine (PC I am using for this post) and copy it over on a thumb drive? I have never loaded anything on my ubuntu machine without using syanaptic?
You could use Synaptic to install "ndiswrapper" but you need to tell Synaptic that it is supposed to install from CD, no through the Internet. I am not in front of my own computer right now, so I can't tell you exactly how to do it, but it is possible.

[myidbe]

Hi forum: I'm having a similar problem. Switching to Ubuntu 7.04 has been nice, but I'm still having trouble getting wireless working.

After following the instructions at the beginning of this thread, I still couldn't connect (to the WPA1 network here). I used eth1 instead of wlan0. I use a Sony PCG-V505EX Laptop with an Intel Pro-Wireless 2100 integrated wireless LAN. Here are the outputs from my machine (network cable was unplugged and network-manager was switched off during all this - also after I went through the procedure, my cable internet no longer functioned..):

uname -a


malcolm@malcolm-laptop:~$ uname -a
Linux malcolm-laptop 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux


ifconfig -a


malcolm@malcolm-laptop:~$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 08:00:46:CD:1A:01
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:268898 errors:0 dropped:0 overruns:0 frame:0
TX packets:200518 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:263632148 (251.4 MiB) TX bytes:25486778 (24.3 MiB)

eth1 Link encap:Ethernet HWaddr 00:0E:35:03:2B:01
inet6 addr: fe80::20e:35ff:fe03:2b01/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:4 errors:0 dropped:68 overruns:0 frame:0
TX packets:5 errors:0 dropped:0 overruns:0 carrier:1
collisions:0 txqueuelen:1000
RX bytes:295156 (288.2 KiB) TX bytes:496768 (485.1 KiB)
Interrupt:9 Base address:0x6000 Memory:d0201000-d0201fff

eth0:avah Link encap:Ethernet HWaddr 08:00:46:CD:1A:01
inet addr:169.254.3.97 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1

eth1:avah Link encap:Ethernet HWaddr 00:0E:35:03:2B:01
inet addr:169.254.1.51 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Interrupt:9 Base address:0x6000 Memory:d0201000-d0201fff

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:18733 errors:0 dropped:0 overruns:0 frame:0
TX packets:18733 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1087245 (1.0 MiB) TX bytes:1087245 (1.0 MiB)



route -n


malcolm@malcolm-laptop:~$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1
0.0.0.0 0.0.0.0 0.0.0.0 U 1000 0 0 eth0


iwconfig


malcolm@malcolm-laptop:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

eth1 IEEE 802.11g ESSID:"HieglW"
Mode:Managed Frequency:2.412 GHz Access Point: 00:15:0C:D3:EE:C5
Bit Rate:54 Mb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=67/100 Signal level=-56 dBm Noise level=-87 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:68 Missed beacon:0


ifconfig


malcolm@malcolm-laptop:~$ ifconfigeth0 Link encap:Ethernet HWaddr 08:00:46:CD:1A:01
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:268898 errors:0 dropped:0 overruns:0 frame:0
TX packets:200518 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:263632148 (251.4 MiB) TX bytes:25486778 (24.3 MiB)

eth1 Link encap:Ethernet HWaddr 00:0E:35:03:2B:01
inet6 addr: fe80::20e:35ff:fe03:2b01/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:1 errors:0 dropped:68 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:1
collisions:0 txqueuelen:1000
RX bytes:310637 (303.3 KiB) TX bytes:524762 (512.4 KiB)
Interrupt:9 Base address:0x6000 Memory:d0201000-d0201fff

eth0:avah Link encap:Ethernet HWaddr 08:00:46:CD:1A:01
inet addr:169.254.3.97 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1

eth1:avah Link encap:Ethernet HWaddr 00:0E:35:03:2B:01
inet addr:169.254.1.51 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Interrupt:9 Base address:0x6000 Memory:d0201000-d0201fff

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:18756 errors:0 dropped:0 overruns:0 frame:0
TX packets:18756 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1089284 (1.0 MiB) TX bytes:1089284 (1.0 MiB)


lsmod


malcolm@malcolm-laptop:~$ lsmodModule Size Used by
nls_iso8859_1 5120 0
nls_cp437 6784 0
vfat 14208 0
fat 53916 1 vfat
binfmt_misc 12680 1
rfcomm 40856 0
l2cap 25728 5 rfcomm
bluetooth 55908 4 rfcomm,l2cap
sonypi 23196 0
ppdev 10116 0
radeon 124576 2
drm 81044 3 radeon
speedstep_centrino 9920 0
cpufreq_conservative 8200 0
cpufreq_stats 7360 0
cpufreq_ondemand 9228 1
cpufreq_powersave 2688 0
freq_table 5792 3 speedstep_centrino,cpufreq_stats,cpufreq_ondemand
cpufreq_userspace 5408 0
sony_acpi 6284 0
dev_acpi 12292 0
tc1100_wmi 8068 0
pcc_acpi 13184 0
button 8720 0
container 5248 0
ac 6020 0
video 16388 0
battery 10756 0
asus_acpi 17308 0
backlight 7040 1 asus_acpi
dock 10268 0
sbs 15652 0
i2c_ec 5888 1 sbs
i2c_core 22784 1 i2c_ec
ipv6 268704 8
sbp2 23812 0
parport_pc 36388 0
lp 12452 0
parport 36936 3 ppdev,parport_pc,lp
fuse 46612 0
pcmcia 39212 0
joydev 10816 0
snd_intel8x0 34204 1
snd_ac97_codec 98336 1 snd_intel8x0
ac97_bus 3200 1 snd_ac97_codec
snd_pcm_oss 44544 0
snd_mixer_oss 17408 1 snd_pcm_oss
snd_pcm 79876 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
yenta_socket 27532 1
rsrc_nonstatic 14080 1 yenta_socket
ipw2200 148040 0
snd_seq_dummy 4740 0
snd_seq_oss 32896 0
serio_raw 7940 0
snd_seq_midi 9600 0
snd_rawmidi 25472 1 snd_seq_midi
snd_seq_midi_event 8448 2 snd_seq_oss,snd_seq_midi
ieee80211 34760 1 ipw2200
ieee80211_crypt 7040 1 ieee80211
pcmcia_core 40852 3 pcmcia,yenta_socket,rsrc_nonstatic
snd_seq 52592 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_mid i_event
snd_timer 23684 2 snd_pcm,snd_seq
snd_seq_device 9100 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi ,snd_seq
psmouse 38920 0
snd 54020 12 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_ oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_ti mer,snd_seq_device
soundcore 8672 1 snd
snd_page_alloc 10888 2 snd_intel8x0,snd_pcm
shpchp 34324 0
pci_hotplug 32576 1 shpchp
intel_agp 25116 1
agpgart 35400 2 drm,intel_agp
iTCO_wdt 11812 0
iTCO_vendor_support 4868 1 iTCO_wdt
af_packet 23816 18
evdev 11008 3
tsdev 8768 0
ext3 133128 1
jbd 59816 1 ext3
mbcache 9604 1 ext3
sg 36252 0
sr_mod 17060 0
cdrom 37664 1 sr_mod
sd_mod 23428 3
usb_storage 72256 0
libusual 17936 1 usb_storage
ata_piix 15492 2
ata_generic 9092 0
libata 125720 2 ata_piix,ata_generic
scsi_mod 142348 6 sbp2,sg,sr_mod,sd_mod,usb_storage,libata
e100 36232 0
mii 6528 1 e100
ohci1394 36528 0
ieee1394 299448 2 sbp2,ohci1394
generic 5124 0 [permanent]
ehci_hcd 34188 0
uhci_hcd 25360 0
usbcore 134280 5 usb_storage,libusual,ehci_hcd,uhci_hcd
thermal 14856 0
processor 31048 1 thermal
fan 5636 0
fbcon 42656 0
tileblit 3584 1 fbcon
font 9216 1 fbcon
bitblit 6912 1 fbcon
softcursor 3200 1 bitblit
vesafb 9220 0
capability 5896 0
commoncap 8192 1 capability


iwlist scan


malcolm@malcolm-laptop:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:15:0C:D3:EE:C5
ESSID:"HieglW"
Protocol:IEEE 802.11bg
Mode:Master
Channel:1
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=95/100 Signal level=-30 dBm
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Extra: Last beacon: 2696ms ago
Cell 02 - Address: 00:03:C9:8B:4C:52
ESSID:"WLAN"
Protocol:IEEE 802.11bg
Mode:Master
Channel:11
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=33/100 Signal level=-80 dBm
Extra: Last beacon: 2536ms ago


cat /etc/network/interfaces


malcolm@malcolm-laptop:~$ cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-ssid XXXXXX
wpa-ap-scan 1
wpa-proto WPA RSN
wpa-pairwise TKIP CCMP
wpa-group TKIP CCMP
wpa-key-mgmt WPA-PSK
wpa-psk LotsOfNumbersAndLettersHere0123456789

auto eth2
iface eth2 inet dhcp

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp


cat /etc/modprobe.d/ndiswrapper


malcolm@malcolm-laptop:~$ cat /etc/modprobe.d/ndiswrapper
cat: /etc/modprobe.d/ndiswrapper: No such file or directory


cat /etc/resolv.conf


malcolm@malcolm-laptop:~$ cat /etc/resolv.conf
# generated by NetworkManager, do not edit!



nameserver 192.168.178.1




sudo /etc/init.d/networking restart


malcolm@malcolm-laptop:~$ sudo /etc/init.d/networking restart
* Reconfiguring network interfaces... RTNETLINK answers: No such process
There is already a pid file /var/run/dhclient.eth0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/08:00:46:cd:1a:01
Sending on LPF/eth0/08:00:46:cd:1a:01
Sending on Socket/fallback
DHCPRELEASE on eth0 to 192.168.178.1 port 67
There is already a pid file /var/run/dhclient.eth1.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:0e:35:03:2b:01
Sending on LPF/eth1/00:0e:35:03:2b:01
Sending on Socket/fallback
There is already a pid file /var/run/dhclient.eth0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/08:00:46:cd:1a:01
Sending on LPF/eth0/08:00:46:cd:1a:01
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
There is already a pid file /var/run/dhclient.eth1.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:0e:35:03:2b:01
Sending on LPF/eth1/00:0e:35:03:2b:01
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 12
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
eth2: ERROR while getting interface flags: No such device
There is already a pid file /var/run/dhclient.eth2.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

SIOCSIFADDR: No such device
eth2: ERROR while getting interface flags: No such device
eth2: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up eth2.
ath0: ERROR while getting interface flags: No such device
There is already a pid file /var/run/dhclient.ath0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

SIOCSIFADDR: No such device
ath0: ERROR while getting interface flags: No such device
ath0: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up ath0.
wlan0: ERROR while getting interface flags: No such device
There is already a pid file /var/run/dhclient.wlan0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

SIOCSIFADDR: No such device
wlan0: ERROR while getting interface flags: No such device
wlan0: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up wlan0.


This seems to have gotten pretty long...btw, this is my very first post in the Ubuntu forums....

Best,
Van

[wieman01]

This seems to have gotten pretty long...btw, this is my very first post in the Ubuntu forums....

Best,
Van
No problem. Feisty installs NetworkManager by default. Why don't you use it instead? Unless you uninstall it, this thread won't help you. And if you do not require static IP, stick with NetworkManager for the sake of convenience...

[gatoruss]

You could use Synaptic to install "ndiswrapper" but you need to tell Synaptic that it is supposed to install from CD, no through the Internet. I am not in front of my own computer right now, so I can't tell you exactly how to do it, but it is possible.

I got "ndiswrapper" installed, but cannot find the windows driver....

Followed directions at "ndiswrapper" (http://ndiswrapper.sourceforge.net/joomla/index.php?/component/option,com_openwiki/Itemid,33/id,installation/), and install seems successfule; but I hit a wall with trying to find the drivers. Per this site, I have tried a all the things it suggests...

On my XP box where a similar card is installed: i cannot find the .inf file.

This site has window drivers (http://www.ralinktech.com/ralink/Home/Support/Windows.html) that can be installed, but when you unpack it, it is a setup.exe file (no .sys or .inf files).

This site says it has linux drivers (http://www.ralinktech.com/ralink/Home/Support/Linux.html) but when you unpack it there are 3 bin files. Again, no .sys or .inf files.

This really should not be this hard....it is very frustrating.:(

[wieman01]

I got "ndiswrapper" installed, but cannot find the windows driver....

Followed directions at "ndiswrapper" (http://ndiswrapper.sourceforge.net/joomla/index.php?/component/option,com_openwiki/Itemid,33/id,installation/), and install seems successfule; but I hit a wall with trying to find the drivers. Per this site, I have tried a all the things it suggests...

On my XP box where a similar card is installed: i cannot find the .inf file.

This site has window drivers (http://www.ralinktech.com/ralink/Home/Support/Windows.html) that can be installed, but when you unpack it, it is a setup.exe file (no .sys or .inf files).

This site says it has linux drivers (http://www.ralinktech.com/ralink/Home/Support/Linux.html) but when you unpack it there are 3 bin files. Again, no .sys or .inf files.

This really should not be this hard....it is very frustrating.:(
The .exe file could be a ZIP archive. Try to open it with any ZIP tool that you have got. It is possible that it contains all the files you need.

[gatoruss]

The .exe file could be a ZIP archive. Try to open it with any ZIP tool that you have got. It is possible that it contains all the files you need.


When you unzip the windows file, it is a .exe fiel that is an install application. When you run it on XP, it allempts to install on the machine (which alraedy had functioning wifi). When you try to run it on Ubuntu, you get a message that there is no app that can run it.

I am about to the point of giving up, on this ubuntu experiment and going back to XP. I was really enjoying playing around on ubuntu, but w/out wifi there is not much point. And the search for wifi has become too consuming without results.

Very frustrated....:(

On the plus side, I do appreciate your help.

[wieman01]

When you unzip the windows file, it is a .exe fiel that is an install application. When you run it on XP, it allempts to install on the machine (which alraedy had functioning wifi). When you try to run it on Ubuntu, you get a message that there is no app that can run it.

I am about to the point of giving up, on this ubuntu experiment and going back to XP. I was really enjoying playing around on ubuntu, but w/out wifi there is not much point. And the search for wifi has become too consuming without results.

Very frustrated....:(

On the plus side, I do appreciate your help.
Try to unzip the executable (= install application) then. It should contain more files.

[gerdt]

Hello,
I've been looking, but I can't find the answer, so I thought this might be the correct place to place my question:

I have a (lspci):
05:00.0 Network controller: Broadcom Corporation Dell Wireless 1390 WLAN Mini-PCI Card (rev 01)

I use Feisty on my laptop (Dell Inspiron 1501)

Thanks to your HOWTO, I have wireless internet at my university, but...
Every some minutes, the connections goes down, and I have to restart the network. Most often it's less than 10 minutes, but my max has not been more than 30 minutes.
I was wondering what I could do about this?

Another thing which annoys me is that with my newly adapted /etc/network/interfaces, I can't use my NetworkManager (see image below). Therefore, each time I leave university and go home, I have to restore the original interfaces file in order to get my NetworkManager up and running properly, so that I can use my home-wlan-connection.

/etc/network/interfaces :

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-ssid XXXXXXXXXX
wpa-ap-scan 1
wpa-eap TTLS
wpa-key-mgmt IEEE8021X
wpa-anonymous-identity YYYYYYYYYY
wpa-identity YYYYYYYYYY
wpa-password ZZZZZZZZZZ
wpa-phase2 auth=PAP


This is how my Network-Manager looks like when using the above interfaces-file. As you can see, it doesn't show anything concerning WLAN. Just to be clear, this is the image of my network-manager when I am at university using WLAN.

http://www.graas.org/ubuntu/network-manager.jpg

Conclusion:
I would like to fix:
1) stop the network from going down every few minutes.
2) use my network-manager whithout having the restore the "normal" interfaces every time I leave university.

Note: These two problems I have described, I only encounter when using the above interfaces, i.e. only when I want to use the WLAN at my university. When I restore the original interfaces file, I can use any other "simple" WLAN and i can use my network manager without any problems.

Original /etc/network/interfaces :

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp


Image of my Network-Manager when using the "simple" interfaces-file:
http://www.graas.org/ubuntu/network-manager2.jpg

I hope that some of you can help me out!
Thanx in advace,
Gerdt

[wieman01]

@gerdt:

1) Unless you have admin access to your university's network, I can't help you there, mate.
2) I would think that the latest version of NetworkManager supports TTLS? Unless that isn't possible, there is no way you can avoid it at this stage.

Question: Are you using DHCP both at home and on the campus? I have got something in mind...

EDIT:
If you are willing to help me test a few things, we could try to work it out together. What kind of network are you using back home? WPA, WEP, DHCP, etc.?

[gerdt]

@wieman:

At home I use a WLAN with:
DHCP & WPA Personal & TKIP & MAC address filter
But for that to work I don't adjust the interfaces file, it can be done graphically through Network Manager. I haven't tried Wifi-Radar yet, though I would prefer to try everything first with NetworkManager.

About my university problem:
Isn't there someway to detect that the network has gone down, so that it can automatically restart the network?

About the tests, yes, I am willing to help you. If it can resolve my (and/or other) problems, I would be glad to help you.

EDIT:

Question: Are you using DHCP both at home and on the campus? I have got something in mind...
Yes, at university I also use DHCP.

Thanx,
Gerdt

[wieman01]

@wieman:

At home I use a WLAN with:
DHCP & WPA Personal & TKIP & MAC address filter
But for that to work I don't adjust the interfaces file, it can be done graphically through Network Manager. I haven't tried Wifi-Radar yet, though I would prefer to try everything first with NetworkManager.

About my university problem:
Isn't there someway to detect that the network has gone down, so that it can automatically restart the network?

About the tests, yes, I am willing to help you. If it can resolve my (and/or other) problems, I would be glad to help you.

EDIT:

Yes, at university I also use DHCP.

Thanx,
Gerdt
What I was thinking of is putting both configurations in one single file which - I believe - should work. Would you mind give it a try? You have to configure your interfaces file once, that's it. Your PC would connect to either network as soon as one of them is in range.

Here we go...

auto eth1
iface eth1 inet dhcp
wpa-driver wext
# Home network
wpa-ssid <home_essid>
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <your_hex_key>
# University network
wpa-ssid XXXXXXXXXX
wpa-ap-scan 1
wpa-eap TTLS
wpa-key-mgmt IEEE8021X
wpa-anonymous-identity YYYYYYYYYY
wpa-identity YYYYYYYYYY
wpa-password ZZZZZZZZZZ
wpa-phase2 auth=PAP
Please take a look at the "key generation" section in the HOWTO for your home network. I also assume that ESSID broadcast is enabled ("wpa-ap-scan 1").

This should get you hooked up. No matter where you start your computer from now on, it should connect to the right network immediately. So that's the theory... can you test it for me please?

[gerdt]

@wieman:
Yes, at home the ESSID is also being broadcasted

This the interfaces-file I just tested (without succes :( ):

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp
wpa-driver wext
# Home network
wpa-ssid XXXXXXXXXX
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk ZZZZZZZZZZ
# University network
wpa-ssid XXXXXXXXXX
wpa-ap-scan 1
wpa-eap TTLS
wpa-key-mgmt IEEE8021X
wpa-anonymous-identity YYYYYYYYYY
wpa-identity YYYYYYYYYY
wpa-password ZZZZZZZZZZ
wpa-phase2 auth=PAP

This is the error when I try to restart the network after having modified the settings:

> sudo ./wireless-network.sh
* Reconfiguring network interfaces... /etc/network/interfaces:19: duplicate option
ifdown: couldn't read interfaces file "/etc/network/interfaces"
/etc/network/interfaces:19: duplicate option
ifup: couldn't read interfaces file "/etc/network/interfaces"


Just out of curiosity, what does the lo in interfaces means? Is it some kind of virtual network card?

Another question:
Is it possible to include a certain IF clause into /etc/network/interfaces?
Something like:
IF ("iwlist scan" includes HOME_SSID) THEN intefaces-configuration-home
ELSEIF ("iwlist scan" includes UNIVERSITY_SSID) THEN interfaces-configuration-university
ELSE standard-interfaces-configuration

[wieman01]

@wieman:
Yes, at home the ESSID is also being broadcasted

This the interfaces-file I just tested (without succes :( ):

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp
wpa-driver wext
# Home network
wpa-ssid XXXXXXXXXX
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk ZZZZZZZZZZ
# University network
wpa-ssid XXXXXXXXXX
wpa-ap-scan 1
wpa-eap TTLS
wpa-key-mgmt IEEE8021X
wpa-anonymous-identity YYYYYYYYYY
wpa-identity YYYYYYYYYY
wpa-password ZZZZZZZZZZ
wpa-phase2 auth=PAP

This is the error when I try to restart the network after having modified the settings:

> sudo ./wireless-network.sh
* Reconfiguring network interfaces... /etc/network/interfaces:19: duplicate option
ifdown: couldn't read interfaces file "/etc/network/interfaces"
/etc/network/interfaces:19: duplicate option
ifup: couldn't read interfaces file "/etc/network/interfaces"


Just out of curiosity, what does the lo in interfaces means? Is it some kind of virtual network card?

Another question:
Is it possible to include a certain IF clause into /etc/network/interfaces?
Something like:
IF ("iwlist scan" includes HOME_SSID) THEN intefaces-configuration-home
ELSEIF ("iwlist scan" includes UNIVERSITY_SSID) THEN interfaces-configuration-university
ELSE standard-interfaces-configuration
The first two lines refer to the loopback interface which enables your computer to recognize (e.g. ping) itself.

I don't think you can include any sort of scripting in the file.

What about this then:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp
wpa-driver wext
# Home network
wpa-priority 1
wpa-ssid XXXXXXXXXX
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk ZZZZZZZZZZ
# University network
wpa-priority 2
wpa-ssid XXXXXXXXXX
wpa-ap-scan 1
wpa-eap TTLS
wpa-key-mgmt IEEE8021X
wpa-anonymous-identity YYYYYYYYYY
wpa-identity YYYYYYYYYY
wpa-password ZZZZZZZZZZ
wpa-phase2 auth=PAP


EDIT:
Added "wpa-priority"...

[gerdt]

I'm sorry, I get the same error:

ifdown: couldn't read interfaces file "/etc/network/interfaces"
/etc/network/interfaces:17: duplicate option
ifup: couldn't read interfaces file "/etc/network/interfaces"
[fail]

[yamad]

Hi,

I'm trying to get a Netgear WG121 USB adapter to connect up with a Netgear WGT624 router in Ubuntu 7.04 (Feisty). The router is set for WPA1 and broadcasts the SSID. The set-up works fine in Windows, but won't take in Ubuntu. If I turn off WPA protection it connects fine. I've set aside a static IP for the computer.

The most frustrating part is that it has actually connected up twice for about a minute each. Both times were coincident with installing NetworkManager, but stopped working soon after. I have uninstalled NetworkManager as per the instructions.

My /etc/network/interfaces file:


auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet static
address 192.168.0.200
netmask 255.255.255.0
dns-nameserver 192.168.0.1
gateway 192.168.0.1
wpa-driver wext
wpa-ssid <SSID>
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <phrase_from_wpa_passphrase>


My /etc/wpa_supplicant.conf (I realize that this shouldn't matter):


network={
pairwise=TKIP
group=TKIP
ssid="<SSID>"
proto=WPA
key_mgmt=WPA-PSK
psk=<phrase_from_wpa_passphrase>
}


If there's any other file/log I should provide please let me know. Thanks for your help. I'm really really ready to get this working after two days trying!

[wieman01]

I'm sorry, I get the same error:

ifdown: couldn't read interfaces file "/etc/network/interfaces"
/etc/network/interfaces:17: duplicate option
ifup: couldn't read interfaces file "/etc/network/interfaces"
[fail]

Bad news then... Was worth it anyway.

[wieman01]

My /etc/network/interfaces file:


auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet static
address 192.168.0.200
netmask 255.255.255.0
dns-nameserver 192.168.0.1
gateway 192.168.0.1
wpa-driver wext
wpa-ssid <SSID>
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <phrase_from_wpa_passphrase>

This looks actually quite neat. The results of a few more commands would be helpful indeed:

iwlist scan

route

iwconfig

sudo ifdown -v wlan0

sudo ifup -v wlan0
If your network keeps disconnecting, then this might be due to the "physical" settings of your network. But let's look at that later on.

EDIT;
Indeed you don't require "/etc/wpa_supplicant.conf".

[AZzKikR]

Alright, I've been browsing through this thread for quite some time, trying for some hints about my problem.

I have a nice connection to my router with the following properties:

I have a Linksys Wireless PCI card, which is based on the Ralink Rt2500 chipset;
Router has WPA/PSK TKIP
I am using SerialMonkey's drivers
I used this wiki post (https://help.ubuntu.com/community/WifiDocs/Driver/RalinkRT2500#WPA) to enable WPA/PSK TKIP


I have been noticing however, that sometimes my connection just get very laggy (i.e. pinging my router often results in 40% - 60% packet loss). After a short while, my connection just plain drops. Rebooting does not help and I have to let this effect 'wear out': after some time it works normally.

The other 4 windows based laptops and computers in my house all have a perfect wireless connection, so my router is just functioning fine. I am thinking it's the driver which is just plain crap.

Anyone else has something like this? I am thinking about using ndiswrapper.

[wieman01]

Alright, I've been browsing through this thread for quite some time, trying for some hints about my problem.

I have a nice connection to my router with the following properties:

I have a Linksys Wireless PCI card, which is based on the Ralink Rt2500 chipset;
Router has WPA/PSK TKIP
I am using SerialMonkey's drivers
I used this wiki post (https://help.ubuntu.com/community/WifiDocs/Driver/RalinkRT2500#WPA) to enable WPA/PSK TKIP


I have been noticing however, that sometimes my connection just get very laggy (i.e. pinging my router often results in 40% - 60% packet loss). After a short while, my connection just plain drops. Rebooting does not help and I have to let this effect 'wear out': after some time it works normally.

The other 4 windows based laptops and computers in my house all have a perfect wireless connection, so my router is just functioning fine. I am thinking it's the driver which is just plain crap.

Anyone else has something like this? I am thinking about using ndiswrapper.
I had the same issues (connection dropping) usind "ndiswrapper" and the latest Windows driver (RT2570). Changing a few (wireless) settings did the job for me eventually (beacon interval, etc.). Not sure if this is an option for you, but I would play around with those router settings.

EDIT:
I didn't enjoy Serialmonkey's driver either, believe me. So I dropped it.

[yamad]

Thanks for your help.


If your network keeps disconnecting, then this might be due to the "physical" settings of your network. But let's look at that later on.

I see what you are saying, but I wouldn't characterize the network as disconnecting. Rather, one or twice it connected for a brief period (probably some command got fired while starting up NetworkManager). Also, when I turned off WPA everything worked.

Here are the logs.

iwconfig


lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:"<SSID>"
Mode:Managed Frequency:2.437 GHz Access Point: 00:09:5B:86:B0:B4
Bit Rate=54 Mb/s
RTS thr=2432 B Fragment thr=2432 B
Power Management:off
Link Quality:64/100 Signal level:-55 dBm Noise level:=96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


iwlist scan


lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:09:5B:86:B0:B4
ESSID:"<SSID>"
Protocol:IEEE 802.11b
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:53/100 Signal level:-62 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=1
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 02 - Address: 00:E0:98:D3:D4:4A
ESSID:"<some other guy's SSID>"
Protocol:IEEE 802.11b
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:21/100 Signal level:-82 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=200
Extra:atim=2
Cell 03 - Address: 00:0F:B5:64:A2:3E
ESSID:"<another other guy's SSID>"
Protocol:IEEE 802.11b
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:17/100 Signal level:-85 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=1



route:


Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 wlan0
link-local * 255.255.0.0 U 1000 0 0 wlan0
default 192.168.0.1 0.0.0.0 UG 0 0 0 wlan0



ifdown -v wlan0:


Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/wpasupplicant
route del default gw 192.168.0.1 wlan0
ifconfig wlan0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan0.pid
Stopped /sbin/wpa_supplicant (pid 7120)


ifup -v wlan0


Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan0
wpa_supplicant: wpa-ap-scan 1 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "<SSID>" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise TKIP -- OK
wpa_supplicant: wpa-group TKIP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto WPA -- OK
wpa_supplicant: enabling network block 0 -- OK

ifconfig wlan0 192.168.0.200 netmask 255.255.255.0 up
route add default gw 192.168.0.1 wlan0
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant


a note on MAC addresses... my router uses them and I had to enter the one from
ifconfig wlan0 when I was setting aside the IP (I set aside the IP because I thought it might work better than dhcp after trying it with dhcp for a while). not sure if that it MAC filtering or not. unfortunately, i don't know if i can turn it off if it is (i assume that must be done on the router side).

Thanks for all your help. Seriously.

[wieman01]

@yamad:

What happens if you ping your router:

ping 192.168.0.1
Or Google:

ping www.google.com

[yamad]

yeah, pinging is how i usually check whether i'm connected or not.



ping 162.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
From 192.168.0.200 icmp_seq=2 Destination Host Unreachable
and so on...




ping www.google.com
ping: unknown host www.google.com


thanks!

[wieman01]

Ah... You have changed your second post in the meantime ("ifup -v wlan0") which confirms that authentication is not the issue.

I suspect that this has to do with...

a) either MAC filtering
b) the IP you have chosen.

Could you connect to the network using this very PC when you were running Windows? If that is so, MAC filtering is ruled out. Is the IP address valid? Well, enable DHCP once again and see what IP address you are assigned. That is the IP address you should use for testing Static IP.

We'll get there... we're fairly close. WPA is not our problem. :-)

[yamad]

hmmm... i can't get an ip from dhcp. lots of DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval X errors. this is why i had tried to switch to static ip. the ip i chose was random, but within the range of assignable IPs (i think). the same hardware (same computer) running windows worked fine.

dmesg has these two following errors that may be relevant:


wlan0: no IPv6 routers present
ADDRCONF(NETDEV_UP): wlan0: link is not ready


thanks

[wieman01]

hmmm... i can't get an ip from dhcp. lots of DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval X errors. this is why i had tried to switch to static ip. the ip i chose was random, but within the range of assignable IPs (i think). the same hardware (same computer) running windows worked fine.

dmesg has these two following errors that may be relevant:


wlan0: no IPv6 routers present
ADDRCONF(NETDEV_UP): wlan0: link is not ready


thanks
Wow, a tough one. The driver you are using... Are you sure it supports WPA at all? Is it the one you were using for Windows?

But you can connect to unsecured network, is that right? Please check if there is any information posted on the vendor's web site concerning the driver...

[yamad]

after a lot of playing around, i figured out when it connects ok. NetworkManager has to be installed, and then both static and dhcp IPs work, if WPA is off (i haven't tried with WEP yet). curiously, dhcp continually binds to the static ip i had set before unsetting the static ip... so i'm wondering if dhcp actually works or if the ip is getting saved and rebound each time.

anyway, NetworkManager has to be installed for dhcp AND static ips to work.

i am using ndiswrapper and netwg121 (v2) which is the same driver i was using under windows. since wpa worked fine with this hardware under windows, i am assuming that means that WPA is supported by this driver?

[wieman01]

i am using ndiswrapper and netwg121 (v2) which is the same driver i was using under windows. since wpa worked fine with this hardware under windows, i am assuming that means that WPA is supported by this driver?
Yes, that is right... If the driver is one and the same, it ought to work.

While you are attempting to connect your Ethernet cable is pulled, isn't it?

[yamad]

yeah, there is no ethernet cable plugged in to the comp. in fact, the comp i'm using has a mobo with a ethernet chipset that, from a little googling, appears not to work well with linux (too old, i guess).

[arionus]

Thank-you, thank-you thank-you!!!
Wow, its been a while in the doing, on and off for a couple of weeks now, but finally i have my wireless working!

I didnt realise how important the removal of the network cable really was, until i removed it in frustration and restarted the network.:mad::D

By following http://ubuntuforums.org/showthread.php?t=405990 and then your howto it worked.

so once again Thanks.

I rate your article and the whole How-to thread :KS:KS:KS:KS:KS

Ari.

[wieman01]

yeah, there is no ethernet cable plugged in to the comp. in fact, the comp i'm using has a mobo with a ethernet chipset that, from a little googling, appears not to work well with linux (too old, i guess).
Man, I am at a loss here. I don't think MAC filtering is the issue because you can connect via unsecured mode to the same network. Sorry I cannot help any further.

[yamad]

thanks for your help anyhow. your attention was really appreciated.

any advice on where to proceed/other threads to look at? maybe this card just isn't well enough supported?

[wieman01]

thanks for your help anyhow. your attention was really appreciated.

any advice on where to proceed/other threads to look at? maybe this card just isn't well enough supported?
You should open a new thread and post your stuff there so that you can share it with a broader audience. Simply write a summary and describe your problem once again. If you sent me the link by PM, I will keep an eye on it as well. :-) Maybe I have missed something.

[Shambler2]

Hi,
I'm having a bit of a problem with my Wireless on LEAP here. I followed the very helpful instructions that you've supplied, but unfortunately I haven't been able to get it to work. I can get it to work at home on my standard WEP network though.
When I restart the network, the DHCP client is unable to connect, and ends up repeating 255.255.255.255 port X interval X 4 times, then gives up. I've followed a couple of different guides over the past few weeks, network manager 0.7 managed to find the network, but it cannot connect. I don't have that anymore though because this guide advised me to remove it.
My configuration file is similar to one of the examples, however I have changed it for our network. My card is a Atheros AR5212 in a Thinkpad R51.
Thanks for any help given,
Sam

[akpower]

dear all,

I am the beginner of Linux. May need some help on the PEAP setting for connecting to my school.
Below is the setting on WinXP WinXP (http://www.lib.latrobe.edu.au/help/technical/LTUW-XPSP2.pdf)
How do I convert to Ubuntu?
In deed, I downloaded the wpa supplicant source file, and how do I make it?
I miss the config file.
I am using IBM Thinkpad T43 2668-HH5.
Please help

[wieman01]

dear all,

I am the beginner of Linux. May need some help on the PEAP setting for connecting to my school.
Below is the setting on WinXP WinXP (http://www.lib.latrobe.edu.au/help/technical/LTUW-XPSP2.pdf)
How do I convert to Ubuntu?
In deed, I downloaded the wpa supplicant source file, and how do I make it?
I miss the config file.
I am using IBM Thinkpad T43 2668-HH5.
Please help
Check out the tutorial. It gives clear instruction with regard to various authentication & encryption methods. PEAP is one of them.

[arionus]

Hi,
I'm having a bit of a problem with my Wireless on LEAP here. I followed the very helpful instructions that you've supplied, but unfortunately I haven't been able to get it to work. I can get it to work at home on my standard WEP network though.
When I restart the network, the DHCP client is unable to connect, and ends up repeating 255.255.255.255 port X interval X 4 times, then gives up. I've followed a couple of different guides over the past few weeks, network manager 0.7 managed to find the network, but it cannot connect. I don't have that anymore though because this guide advised me to remove it.
My configuration file is similar to one of the examples, however I have changed it for our network. My card is a Atheros AR5212 in a Thinkpad R51.
Thanks for any help given,
Sam

I had the same issue with DHCP and my D-Link router, i could connect fine with a wired connection and using WEP, however, as soon as i enabled WAP and MAC Filtering, i could no longer get an IP via the DHCP server on my Server (I run a Windows AD network at home :redface:). So i hard coded my IP address on my machine..there was a place, not sure if it was this thread or another, that showed you how to edit your interfaces......(Perhaps someone can help me out here..?please and thank you) and everything now works, although saying that i am having an issue where i have to restart the network once i have logged onto the machine. - i followed the part in this thread with adding the command to a symbolic linked file :) .

Hope that helps.

[Shambler2]

Thanks a lot for your reply!
Being able to edit that configuration file would be excellent.
I remember editing a file a long time ago when I first tried to get it to work, but I've actually forgotten the file, so that might be the one.
Anybody know how to do what arionus described? Or any other solutions?
Thanks guys! :D

[kingleer]

Hello, I'm a noob, but I've been using Ubuntu for some time. I've got it installed on my desktop and on my laptop as my main os. I've gotten my wireless cards working using ndiswrapper, and I've been able to use my home wireless network and the wireless network on my campus.

Recently though, I changed the firmware on my router

http://www.polarcloud.com/tomato

And for security reasons decided to go with a WPA1 & DHCP, ESSID broadcast enabled configuration instead of just wep.

I installed wpa-supplicant and tried to follow the guide here:
http://ubuntuforums.org/showthread.php?t=318539
but didn't have much luck.

I'm running ubuntu 6.10. Here's what I get when I enter the commands iwconfig and iwlist scan.



kinglear@ubuntu:~$ sudo iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:off/any Nickname:"kinglear"
Mode:Managed Frequency:2.437 GHz Access Point: Not-Associated
Bit Rate=2 Mb/s Tx-Power:32 dBm
RTS thr=2347 B Fragment thr=2346 B
Encryption key:796F-6761-3336-3674-6963-3831-34 Security mode:restricted
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

vmnet1 no wireless extensions.

vmnet8 no wireless extensions.

sit0 no wireless extensions.

kinglear@ubuntu:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:19:5B:4B:6B:71
ESSID:"Jung Network"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.447 GHz (Channel 8)
Quality:35/100 Signal level:-73 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=1
Cell 02 - Address: 00:12:17:1A:5C:FA
ESSID:"kinglear"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:32/100 Signal level:-75 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=1
IE: WPA Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK

vmnet1 Interface doesn't support scanning.

vmnet8 Interface doesn't support scanning.

sit0 Interface doesn't support scanning.


I'm trying to connect to kinglear and not jung by the way.

Any help anyone can give me would be appreciated. Thanks in advance.

[wieman01]

Thanks a lot for your reply!
Being able to edit that configuration file would be excellent.
I remember editing a file a long time ago when I first tried to get it to work, but I've actually forgotten the file, so that might be the one.
Anybody know how to do what arionus described? Or any other solutions?
Thanks guys! :D
Aeh... it is mentioned in the tutorial.

sudo gedit /etc/network/interfaces
Check it out.

[wieman01]

Hello, I'm a noob, but I've been using Ubuntu for some time. I've got it installed on my desktop and on my laptop as my main os. I've gotten my wireless cards working using ndiswrapper, and I've been able to use my home wireless network and the wireless network on my campus.

Recently though, I changed the firmware on my router

http://www.polarcloud.com/tomato

And for security reasons decided to go with a WPA1 & DHCP, ESSID broadcast enabled configuration instead of just wep.

I installed wpa-supplicant and tried to follow the guide here:
http://ubuntuforums.org/showthread.php?t=318539
but didn't have much luck.

I'm running ubuntu 6.10. Here's what I get when I enter the commands iwconfig and iwlist scan.



I'm trying to connect to kinglear and not jung by the way.

Any help anyone can give me would be appreciated. Thanks in advance.
Problem might be the Windows driver you have installed. Some drivers (depending on the version) do not support WPA and WPA2, respectively. Please take a look at the vendor's website first before we go ahead.

[akpower]

Check out the tutorial. It gives clear instruction with regard to various authentication & encryption methods. PEAP is one of them.

How about the wpa sipplicant?
I read the readme file, and copy the setting to a configuration file.
However, I use command "make". It gives me a thou. error.

[wieman01]

How about the wpa sipplicant?
I read the readme file, and copy the setting to a configuration file.
However, I use command "make". It gives me a thou. error.
I think the HOWTO is clear enough in that respect. Have you tried it? If you want to follow the instruction of the README file, then I won't be able to help you.

[kingleer]

Problem might be the Windows driver you have installed. Some drivers (depending on the version) do not support WPA and WPA2, respectively. Please take a look at the vendor's website first before we go ahead.


I type in lspci | grep Network and I get

0000:01:01.0 Network Controller: Intersil Corporation ISL3886 [Prism Javelin/Prism Xbow] (rev 01)

I originally found the driver here

http://ndiswrapper.sourceforge.net/joomla/index.php?/component/option,com_openwiki/Itemid,33/id,list_g-l/


And have not been able to find the vendor's site and the only relevant site I did find was

http://prism54.org/punbb/index.php

But even if it doesn't, can't I still use WPA through the wpa_supplicant?

[wieman01]

I type in lspci | grep Network and I get

0000:01:01.0 Network Controller: Intersil Corporation ISL3886 [Prism Javelin/Prism Xbow] (rev 01)

I originally found the driver here

http://ndiswrapper.sourceforge.net/joomla/index.php?/component/option,com_openwiki/Itemid,33/id,list_g-l/


And have not been able to find the vendor's site and the only relevant site I did find was

http://prism54.org/punbb/index.php

But even if it doesn't, can't I still use WPA through the wpa_supplicant?
The problem is that the driver for your adapter must support WPA. Not all drivers do that. Therefore finding out more about your driver is crucial.

What brand is your card? Mine for instance is Linksys which got a Ralink chipset. So Linksys provides the drivers, all related information is found there. What about yours? Possibly D-Link?

wpa-supplicant is only functional if your card can do WPA as well...

[Zoufiax]

Let's configure your PC to use static IP then:

Please replace the blue bits with your networks IP range and desired client IP. If you don't know what I am referring to, please post your router's IP address. I will give you a hand.

Please use upper case for the the hex key (I assume you have generated the key the way I have suggested in my tutorial). Then restart the network:

Post the contents of "interfaces", etc. after that.
OK I configured my laptop to use static IP and changed my /etc/network/interfaces according to your example. I changed my hex key (64 chars) to upper case and restarted the network, but it still didn't work. Neither did it work after rebooting.

My interfaces files is now as follows:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto wlan0
iface wlan0 inet static
address 10.0.0.170
gateway 10.0.0.138
dns-nameservers 10.0.0.138
netmask 255.255.255.0
wpa-driver wext
wpa-ssid SpeedTouch12345
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk 346858C1C5BDD2A19AAB2CD83CD17F697E195C55510BA0A5C6 D867A1896FFBF6

Please note that my gateway is correct, but I don't know about the dns-nameservers so I used the same address as for the gateway. I changed the wirelesss-essid and wpa-psk before posting to this forum for obvious reasons so this is not my actual wpa-psk key.

Should I change the line "iface eth0 inet dhcp" to "iface eth0 inet static" perhaps?

At the moment I changed my settings to WEP again. This just works. My interfaces when using WEP-security is as follows:

iface wlan0 inet dhcp
wireless-essid SpeedTouch12345
wireless-key [some upper case hex key]

auto wlan0

If there's any more information please let me know. Thanks for being so helpful.

[kingleer]

The problem is that the driver for your adapter must support WPA. Not all drivers do that. Therefore finding out more about your driver is crucial.

What brand is your card? Mine for instance is Linksys which got a Ralink chipset. So Linksys provides the drivers, all related information is found there. What about yours? Possibly D-Link?

wpa-supplicant is only functional if your card can do WPA as well...


Intersil is the vendor.

I found this on the vendor site concerning the card.

http://72.14.205.104/search?q=cache:rcGug68TUNkJ:islsm.org/wiki/lib/exe/fetch.php%3Fid%3Dre%253Afirmware_reverse-engeneering_methodology%26cache%3Dcache%26media%3D re:isl3886.pdf+ISL3886&hl=en&ct=clnk&cd=1&gl=ca&client=firefox-a

It mentions an Internal WEP Engine allows 64 or 128 bit Encryption but makes no mention of WPA.

But the link below says it should be possible to use WPA

http://patrick.vande-walle.eu/software/intersil-isl3886-linux/

[kingleer]

If I can't get WPA working on my laptop, I'll buy a PC card slot PCMIA for my laptop that does support WPA. Could you recommand one that's easy to set up on ubuntu (or even works out of the box) and supports WPA1, WPA2, LEAP, etc?

[wieman01]

OK I configured my laptop to use static IP and changed my /etc/network/interfaces according to your example. I changed my hex key (64 chars) to upper case and restarted the network, but it still didn't work. Neither did it work after rebooting.

My interfaces files is now as follows:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto wlan0
iface wlan0 inet static
address 10.0.0.170
gateway 10.0.0.138
dns-nameservers 10.0.0.138
netmask 255.255.255.0
wpa-driver wext
wpa-ssid SpeedTouch12345
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk 346858C1C5BDD2A19AAB2CD83CD17F697E195C55510BA0A5C6 D867A1896FFBF6

Please note that my gateway is correct, but I don't know about the dns-nameservers so I used the same address as for the gateway. I changed the wirelesss-essid and wpa-psk before posting to this forum for obvious reasons so this is not my actual wpa-psk key.

Should I change the line "iface eth0 inet dhcp" to "iface eth0 inet static" perhaps?

At the moment I changed my settings to WEP again. This just works. My interfaces when using WEP-security is as follows:

iface wlan0 inet dhcp
wireless-essid SpeedTouch12345
wireless-key [some upper case hex key]

auto wlan0

If there's any more information please let me know. Thanks for being so helpful.
Hello,

Same question to you... does the current driver support WPA? Please check the vendor's website to get some info on the driver version, etc. Some drivers do support WPA, some don't. The latest version for your adapter might fix it.

"iface eth0 inet static" is correct if you want to use a static IP. Apart from this your set-up looks just fine.

[wieman01]

Intersil is the vendor.

I found this on the vendor site concerning the card.

http://72.14.205.104/search?q=cache:rcGug68TUNkJ:islsm.org/wiki/lib/exe/fetch.php%3Fid%3Dre%253Afirmware_reverse-engeneering_methodology%26cache%3Dcache%26media%3D re:isl3886.pdf+ISL3886&hl=en&ct=clnk&cd=1&gl=ca&client=firefox-a

It mentions an Internal WEP Engine allows 64 or 128 bit Encryption but makes no mention of WPA.

But the link below says it should be possible to use WPA

http://patrick.vande-walle.eu/software/intersil-isl3886-linux/
If there is no mention of WPA, there is a pretty good chance it does not support WPA at all.

I have not got a PCMCIA card but I reckon this is a good starting point:

https://help.ubuntu.com/community/WifiDocs/WirelessCardsSupported?highlight=%28adapters%29%7C %28wireless%29

[Kalisandra]

I'm just posting to say this tutorials has been really helpful in getting my old Latitude CPi on my WLAN using an Asus WL-100GE PCMCIA card (Broadcom 4318 shipset). The only thing is that on startup it wouldn't connect properly, even using your boot script. It turns out that for some reason I have to do a scan before it'll connect. Therefore I added the following to the boot script:


iwlist scan

With this addition it now works perfectly.

[wieman01]

I'm just posting to say this tutorials has been really helpful in getting my old Latitude CPi on my WLAN using an Asus WL-100GE PCMCIA card (Broadcom 4318 shipset). The only thing is that on startup it wouldn't connect properly, even using your boot script. It turns out that for some reason I have to do a scan before it'll connect. Therefore I added the following to the boot script:


iwlist scan

With this addition it now works perfectly.
Perfect. Thanks for the feedback and your finding concerning the scan. Odd, but I'll recommend it to others should anybody else face a similar issue.

[ice60]

>> IMPORTANT NOTE FOR FEISTY FAWN USERS:
This line must be removed as it causes an error message (thanks to user Corax for this one)

wpa-conf managed:

where should that be removed from ??? i really think this is going to be a nightmare trying to get this to work, i've got a headache already and i haven't even started lol.

i don't suppose anyone knows if this driver works with wpa? -
http://ftp.us.dell.com/network/R151517.EXE

it goes with the Broadcom Corporation Dell Wireless 1390 WLAN Mini-PCI Card

i got it from here - http://ubuntuforums.org/showthread.php?t=297092

i think it's called Forcedeth, but i'm not sure :|

i'll go and read through the thread i suppose.

[wieman01]

where should that be removed from ??? i really think this is going to be a nightmare trying to get this to work, i've got a headache already and i haven't even started lol.

i don't suppose anyone knows if this driver works with wpa? -

The section I am mentioning at the beginning of the tutorial refers to upgraders only... if this is your first go at WPA, you can ignore it.

As for WPA and your wireless device, no idea, really. You just need to give it a try I suppose. You will find help here.

[ice60]

thanks, wieman. i just found out it does work with WPA.

i've got to reset my router now because i wanted to use a better PW, but now it won't let me login :D i'm going to see if i can find some more links to read about setting wpa up first so i know abit more about it incase something goes wrong.

[wieman01]

thanks, wieman. i just found out it does work with WPA.

i've got to reset my router now because i wanted to use a better PW, but now it won't let me login :D i'm going to see if i can find some more links to read about setting wpa up first so i know abit more about it incase something goes wrong.
:-) Good idea. You can always hard re-set your router as a fallback.

[rdcmmnst]

You probably get these alot..but i'm trying to configure my Asus wl-138g i have feisty fawn. I have tried wicd but couldn't get it to work it froze at registering DNS servers..i know about computers..just not linux..yet :)

I configured it to the how to for DHCP, WPA 1 PSK but still no connection..

route -n

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 wlan0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth0
0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 0 eth0
0.0.0.0 0.0.0.0 0.0.0.0 U 1000 0 0 wlan0

-iwconfig

wlan0
IEEE 802.11-DS ESSID:"Cliffhome" Nickname:"unknown"
Mode:Managed Bit Rate=54 Mb/s
RTS thr=2346 B Fragment thr:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

-ifconfig

wlan0 Link encap:Ethernet HWaddr 00:11:2F:4F:9C:A9
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

wlan0:ava Link encap:Ethernet HWaddr 00:11:2F:4F:9C:A9
inet addr:169.254.7.26 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1

-iwlist scan

wlan0 Failed to read scan data : No data available

-cat /etc/network/interfaces
auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid cliffhome
wpa-ap-scan 1
wpa-proto WPA RSN
wpa-pairwise TKIP CCMP
wpa-group TKIP CCMP
wpa-key-mgmt WPA-PSK
wpa-psk CJqraQwe135


-cat /etc/modprobe.d/ndiswrapper
alias wlan0 ndiswrapper

-cat /etc/resolv.conf
nameserver 192.168.2.1


Our router is a asus barricade..

I can connect in xp..so yeah..any other information i'll be happy to provide thank you in advance.

[ice60]

i just tried it and it worked for 5 minutes then stopped working and my laptop hung too. i rebooted and the same thing happened again.

it makes me ill thinking about using wireless, that's why i've only just bought a laptop. if i enable the wireless access point in the router along with this setting -
WPA-PSK (Wi-Fi Protected Access Pre-Shared Key)
can any of my neighbours do any kind of attack, like a man-in-the-middle?

[ice60]

hi, i got it working now :D thanks for the howto.

i know this isn't that important because of spoofing, but does anyone know how to get MAC address filtering working? when i turn it on my wireless stops working.

can i reinstall that wifi radar program now? or is there another program i can use instead?

i hope this works again tomorrow :o i can't go through this everyday.

[wieman01]

hi, i got it working now :D thanks for the howto.

i know this isn't that important because of spoofing, but does anyone know how to get MAC address filtering working? when i turn it on my wireless stops working.

can i reinstall that wifi radar program now? or is there another program i can use instead?

i hope this works again tomorrow :o i can't go through this everyday.
Don't worry, once you got it working, it just works. :-)

MAC filtering is a security setting that you need to enable on the router as you know. There is nothing you need to do on the client side. While you enable it, you need to make sure that you enter the correct MAC address of your wireless adapter and allow access to the network. Usually MAC filtering is foolproof albeit no real obstacle for potential crackers as you have highlighted.

You could re-install Wifi-Radar but I doubt it works after manual configuration. But try nonetheless.

There are 3 potential cracking methods:

a, dictionary attack
b, brute-force
c, statistical attack

WEP is particularly susceptible to c, while WPA2 is secure in the sense that is uses a better algorithm (AES) and hence is not vulnerable to this kind of attack.

WPA & WPA2, however, are just as secure as the password you have chosen. A weak password will always compromise your network's security and therefore I recommend choosing a good password with special characters, upper and lower case, etc. Brute-force & dictionary attacks may be used against even WPA, there are dictionaries out there that contain millions of passwords and combinations (e.g. OpenWall).

So I conclude: WPA(2) and a reasonably long & "good" password are the best protection you can get. "Man-in-the-middle-attacks" become very unlikely if you abide by these rules. :-)

[wieman01]

You probably get these alot..but i'm trying to configure my Asus wl-138g i have feisty fawn. I have tried wicd but couldn't get it to work it froze at registering DNS servers..i know about computers..just not linux..yet :)

I configured it to the how to for DHCP, WPA 1 PSK but still no connection..

Our router is a asus barricade..

I can connect in xp..so yeah..any other information i'll be happy to provide thank you in advance.
Does the very driver you are using support WPA?

Second, please do this for me and post the results:

sudo ifdown -v wlan0

sudo ifup -v wlan0
That should tell us what is going on with your network.

[Shambler2]

Aeh... it is mentioned in the tutorial.

Check it out.
Oh, that =P Yeah, I've fiddled with that, I haven't really managed to find anything that works though...
Any other ideas? Would posting the file be useful?

[wieman01]

Oh, that =P Yeah, I've fiddled with that, I haven't really managed to find anything that works though...
Any other ideas? Would posting the file be useful?
Yes, please...

iwlist scan

iwconfig

cat /etc/network/interfaces

route

sudo ifdown -v <your_interface>

sudo ifup -v <your_interface>

[rdcmmnst]

Does the very driver you are using support WPA?

Second, please do this for me and post the results:


That should tell us what is going on with your network.

--sudo ifdown -v wlan0

Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
RTNETLINK answers: No such process
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 6492
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:11:2f:4f:9c:a9
Sending on LPF/wlan0/00:11:2f:4f:9c:a9
Sending on Socket/fallback
ifconfig wlan0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan0.pid
Stopped /sbin/wpa_supplicant (pid 6251).

--sudo ifup -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
SIOCSIFFLAGS: Invalid argument
Error for wireless request "Set Encode" (8B2A) :
invalid argument "CJqraQwe135".
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
SIOCSIFFLAGS: Input/output error
Could not set interface 'wlan0' UP
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan0
wpa_supplicant: wpa-ap-scan 1 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "cliffhome" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise TKIP CCMP -- OK
wpa_supplicant: wpa-group TKIP CCMP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto WPA RSN -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:11:2f:4f:9c:a9
Sending on LPF/wlan0/00:11:2f:4f:9c:a9
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 17
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant

i know the drivers support wpa because that's what i run on my windows boot.

[wieman01]

@rdcmmnst:

This looks suspicious:

invalid argument "CJqraQwe135".
Please post the output of the remaining commands as well. There is something wrong with your configuration.

[rdcmmnst]

@rdcmmnst:

This looks suspicious:

Please post the output of the remaining commands as well. There is something wrong with your configuration.

--route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 wlan0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth0
0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 0 eth0
0.0.0.0 0.0.0.0 0.0.0.0 U 1000 0

--ifconfig
eth0 Link encap:Ethernet HWaddr 00:11:11:53:A4:4B
inet addr:192.168.2.105 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::211:11ff:fe53:a44b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10167 errors:0 dropped:0 overruns:0 frame:0
TX packets:10913 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:7422803 (7.0 MiB) TX bytes:1869660 (1.7 MiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:32 errors:0 dropped:0 overruns:0 frame:0
TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2683 (2.6 KiB) TX bytes:2683 (2.6 KiB)

wlan0 Link encap:Ethernet HWaddr 00:11:2F:4F:9C:A9
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

wlan0:ava Link encap:Ethernet HWaddr 00:11:2F:4F:9C:A9
inet addr:169.254.7.26 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1


---iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Failed to read scan data : No data avai


---cat /etc/network/interfaces
auto lo
iface lo inet loopback


auto eth1
iface eth1 inet dhcp

auto eth2
iface eth2 inet dhcp

auto ath0
iface ath0 inet dhcp


iface eth0 inet dhcp



















auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid cliffhome
wpa-ap-scan 1
wpa-proto WPA RSN
wpa-pairwise TKIP CCMP
wpa-group TKIP CCMP
wpa-key-mgmt WPA-PSK
wpa-psk CJqraQwe135
wireless-essid cliffhome
wireless-key CJqraQwe135


--cat /etc/modprobe.d/ndiswrapper
alias wlan0 ndiswrapper

---cat /etc/resolv.conf
# generated by NetworkManager, do not edit!



nameserver 192.168.2.1


anything else i can do to help let me know

[wieman01]

anything else i can do to help let me know
Ok, your interfaces configuration file is incorrect. Please replace the contents with this:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid cliffhome
wpa-ap-scan 1
wpa-proto WPA RSN
wpa-pairwise TKIP CCMP
wpa-group TKIP CCMP
wpa-key-mgmt WPA-PSK
wpa-psk <wpa_hex_key_see_tutorial_for_key_generation>
I removed the last 2 lines, plus your wpa-key is probably wrong. Have you followed the steps in the how-to concerning the key generation?
Then restart the PC and see what happens. Then also do another scan for me please:

iwlist scan
That should do.

[Shambler2]

Sorry about the extreme length of this post, here are the outputs to the commands you specified



root@sam-laptop:~# iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wifi0 Interface doesn't support scanning.

ath0 Scan completed :
Cell 01 - Address: 00:16:47:4D:F2:D0
ESSID:""
Mode:Master
Frequency:2.412 GHz (Channel 1)
Quality=20/94 Signal level=-75 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:wme_ie=dd180050f2020101010003a4000027a400004 2435e0062322f00
Cell 02 - Address: 00:18:BA:B7:3F:F0
ESSID:""
Mode:Master
Frequency:2.462 GHz (Channel 11)
Quality=9/94 Signal level=-86 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:wme_ie=dd180050f2020101010003a4000027a400004 2435e0062322f00
Cell 03 - Address: 00:13:1A:30:56:40
ESSID:""
Mode:Master
Frequency:2.432 GHz (Channel 5)
Quality=56/94 Signal level=-39 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:wme_ie=dd180050f2020101010003a4000027a400004 2435e0062322f00

irda0 Interface doesn't support scanning.
root@sam-laptop:~# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wifi0 no wireless extensions.

ath0 IEEE 802.11g ESSID:"" Nickname:""
Mode:Managed Frequency:2.437 GHz Access Point: Not-Associated
Bit Rate:0 kb/s Tx-Power:14 dBm Sensitivity=0/3
Retry:off RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=0/94 Signal level=-88 dBm Noise level=-88 dBm
Rx invalid nwid:697 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

irda0 no wireless extensions.
root@sam-laptop:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto eth1
iface eth1 inet dhcp

auto ath0
iface ath0 inet dhcp
wpa-driver madwifi
wpa-ssid <HIDDEN SSID>
wpa-ap-scan 2
wpa-eap LEAP
wpa-key-mgmt IEEE8021X
wpa-identity <USERNAME>
wpa-password <PASSWORD>

root@sam-laptop:~# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.16.32.0 * 255.255.240.0 U 0 0 0 eth0
default 10.16.32.1 0.0.0.0 UG 0 0 0 eth0
root@sam-laptop:~# sudo ifdown -v ath0
ifdown: interface ath0 not configured

root@sam-laptop:~# sudo ifup -v ath0
Configuring interface ath0=ath0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/madwifi
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver madwifi
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.ath0.pid -i ath0 -D madwifi -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/ath0
wpa_supplicant: wpa-ap-scan 2 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "<HIDDEN SSID>" -- OK
wpa_supplicant: wpa-key-mgmt IEEE8021X -- OK
wpa_supplicant: wpa-identity "<USERNAME>" -- OK
wpa_supplicant: wpa-eap LEAP -- OK
wpa_supplicant: wpa-password "<PASSWORD>" -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -pf /var/run/dhclient.ath0.pid -lf /var/lib/dhcp3/dhclient.ath0.leases ath0
There is already a pid file /var/run/dhclient.ath0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:05:4e:4d:fb:99
Sending on LPF/ath0/00:05:4e:4d:fb:99
Sending on Socket/fallback
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 1
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
Logging into ZANESTATE-FS1 as SRIDDEN
Password:
mount.ncpfs: Server not found (0x8847) when trying to find ZANESTATE-FS1
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant


That last part was a bit of a failed attempt to connect to a novell server, but I later worked out it wasn't necessary to do that.
Thanks heaps for looking at this for me,
Sam

[ariel]

Does anyone have this WPA or WPA2 working following this howto on Netgear WG311T??

I couldn't get the card to associate with my openwrt linksys router.

I'm using the native madwifi driver that comes with feisty 7.04. WEP works fine. I tried network manager (does not detect the card) and wifi-radar and gtk-wifi. No way to get wpa to work.

[wieman01]

Sorry about the extreme length of this post, here are the outputs to the commands you specified

[removed]

That last part was a bit of a failed attempt to connect to a novell server, but I later worked out it wasn't necessary to do that.
Thanks heaps for looking at this for me,
Sam
This is not the longest post I have seen so far. :-)

So that's a LEAP network you are trying to connect to. This is a quote from the web site for wpa-supplicant (http://hostap.epitest.fi/wpa_supplicant/):

LEAP (note: requires special support from the driver)
Guess you need to get some information on LEAP support in that case as LEAP is a proprietary protocol.

[wieman01]

Does anyone have this WPA or WPA2 working following this howto on Netgear WG311T??

I couldn't get the card to associate with my openwrt linksys router.

I'm using the native madwifi driver that comes with feisty 7.04. WEP works fine. I tried network manager (does not detect the card) and wifi-radar and gtk-wifi. No way to get wpa to work.
Looks promising... Take a look at this thread:

http://ubuntuforums.org/showthread.php?t=363633&highlight=WG311T&page=3

Ubuntu_Demon seems happy with it and its WPA(2) support.

[ice60]

Don't worry, once you got it working, it just works. :-)

MAC filtering is a security setting that you need to enable on the router as you know. There is nothing you need to do on the client side. While you enable it, you need to make sure that you enter the correct MAC address of your wireless adapter and allow access to the network. Usually MAC filtering is foolproof albeit no real obstacle for potential crackers as you have highlighted.

You could re-install Wifi-Radar but I doubt it works after manual configuration. But try nonetheless.

There are 3 potential cracking methods:

a, dictionary attack
b, brute-force
c, statistical attack

WEP is particularly susceptible to c, while WPA2 is secure in the sense that is uses a better algorithm (AES) and hence is not vulnerable to this kind of attack.

WPA & WPA2, however, are just as secure as the password you have chosen. A weak password will always compromise your network's security and therefore I recommend choosing a good password with special characters, upper and lower case, etc. Brute-force & dictionary attacks may be used against even WPA, there are dictionaries out there that contain millions of passwords and combinations (e.g. OpenWall).

So I conclude: WPA(2) and a reasonably long & "good" password are the best protection you can get. "Man-in-the-middle-attacks" become very unlikely if you abide by these rules. :-)
thanks for the help :D i'm using a key that has over 60 ASCII charactors. i read WEP can be cracked in about one minute now.

i still can't get the MAC filtering to work 100% i just noticed it is working with everything apart from firefox i think. i'm going to try running wireshark to see if i can work out why it's not working. i'll do a search too. is there anything else i can do?

[ice60]

it just started working :|

i'm still abit scared i might have made a mistake somewhere.

does this look OK? i told my router to use WPA-PSK the xxxxx at the end is what was generated when i ran the command with my SSID and WPA key described in post#1

auto lo
iface lo inet loopback

auto eth1
iface eth1 inet dhcp
address 192.168.0.3
gateway 192.168.0.1
dns-nameservers 192.168.0.1
netmask 255.255.255.0
wpa-driver wext
wpa-ssid BTHomeHub-njhg
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxx

[wieman01]

it just started working :|

i'm still abit scared i might have made a mistake somewhere.

does this look OK? i told my router to use WPA-PSK the xxxxx at the end is what was generated when i ran the command with my SSID and WPA key described in post#1

auto lo
iface lo inet loopback

auto eth1
iface eth1 inet dhcp
address 192.168.0.3
gateway 192.168.0.1
dns-nameservers 192.168.0.1
netmask 255.255.255.0
wpa-driver wext
wpa-ssid BTHomeHub-njhg
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxx
Looks quite ok, Ice. "wpa-ap-scan 2" suggests that you are hiding your ESSID, guess that's what you want anyway. Replace "iface eth1 inet dhcp" with "iface eth1 inet static" if you plan to use a static IP.

auto eth1
iface eth1 inet static
address 192.168.0.3
gateway 192.168.0.1
dns-nameservers 192.168.0.1
netmask 255.255.255.0
wpa-driver wext
wpa-ssid BTHomeHub-njhg
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxx

[ice60]

Looks quite ok, Ice. "wpa-ap-scan 2" suggests that you are hiding your ESSID, guess that's what you want anyway. Replace "iface eth1 inet dhcp" with "iface eth1 inet static" if you plan to use a static IP.

yes, in my router i told it not to broadcast my SSID, it that what you mean?

also, my internet connection uses DHCP to get my IP, it's not static. my router gets the IP.

does it look like i've set it up OK?

i'm going to try and get a USB wireless dongle working with my desktop (i don't know anything about it though so i'm not really sure how it's suppose to work :confused: it came with my router) then i can try and break in to my network just so i know it's safe. i've put off everything wireless for a long time because i've been too frightened to use it lol

[Floor19]

I searched te web and this forum but can;t find the solution for my problem.

I have Ubuntu 7.04 (upgraded it last week) with a pmcia linksys wifi ward. I followed this howto for Edgy and after the update i tweaked my interfaces file like in the howto an my wireless is working.

BUT:

Only when i do ifdown wlan0 and ifup wlan0 in root. The trick in post 2 and 32 are not working for me in Feisty. I get no DHCP offers and boot is taking ages!

Also Ubuntu does not automatically renew the DHCP lease.

Can someone help me with a solution (a init script or something)?!

Thanks in advance!

F

[wieman01]

yes, in my router i told it not to broadcast my SSID, it that what you mean?

also, my internet connection uses DHCP to get my IP, it's not static. my router gets the IP.

does it look like i've set it up OK?

i'm going to try and get a USB wireless dongle working with my desktop (i don't know anything about it though so i'm not really sure how it's suppose to work :confused: it came with my router) then i can try and break in to my network just so i know it's safe. i've put off everything wireless for a long time because i've been too frightened to use it lol
If broadcast is disabled, the setting is fine. If DHCP is what you need, then then network section should look a bit different though:

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-ssid BTHomeHub-njhg
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxx
DHCP will do the rest for you, assign an IP and select the correct nameserver, gateway, etc. Time to relax. :-)

That should do given that your device is working (i.e. connects to unsecured networks just fine) and supports WPA.

Don't worry about security in this case. WPA is considered secure by all standards. If you still have concerns configure your router to use WPA2 (= AES) instead which is the best encryption method you can get. As highlighted, with a good password there is nothing you should worry about at all. :-)

[wieman01]

I searched te web and this forum but can;t find the solution for my problem.

I have Ubuntu 7.04 (upgraded it last week) with a pmcia linksys wifi ward. I followed this howto for Edgy and after the update i tweaked my interfaces file like in the howto an my wireless is working.

BUT:

Only when i do ifdown wlan0 and ifup wlan0 in root. The trick in post 2 and 32 are not working for me in Feisty. I get no DHCP offers and boot is taking ages!

Also Ubuntu does not automatically renew the DHCP lease.

Can someone help me with a solution (a init script or something)?!

Thanks in advance!

F
Well... I can't help you unless you provide a bit more information with regard to your set-up, wireless card, etc. First off can you connect to your network/router when all security is turned off? Please see section "Post this if you are stumped".

[Floor19]

loris@floris-NX9010:~$ route -n
Kernel IP routeing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 wlan0
0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 0 wlan0

floris@floris-NX9010:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:"Depeche"
Mode:Managed Frequency:2.472 GHz Access Point: 00:01:E3:C5:C8:A7
Bit Rate=54 Mb/s Tx-Power:25 dBm
RTS thr=2347 B Fragment thr=2346 B
Power Management:off
Link Quality:59/100 Signal level:-58 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

floris@floris-NX9010:~$ ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:79 errors:0 dropped:0 overruns:0 frame:0
TX packets:79 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6923 (6.7 KiB) TX bytes:6923 (6.7 KiB)

wlan0 Link encap:Ethernet HWaddr 00:14:BF:3D:EA:14
inet addr:192.168.2.2 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::214:bfff:fe3d:ea14/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:19521 errors:0 dropped:0 overruns:0 frame:0
TX packets:13961 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:20939025 (19.9 MiB) TX bytes:1715830 (1.6 MiB)
Interrupt:11 Memory:34000000-34002000

floris@floris-NX9010:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:01:E3:C5:C8:A7
ESSID:"Depeche"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.472 GHz (Channel 13)
Quality:71/100 Signal level:-50 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
Preauthentication Supported

floris@floris-NX9010:~$ cat /etc/network/interfaces
auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid xxxx
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk xxxxx

auto lo
iface lo inet loopback

floris@floris-NX9010:~$ cat /etc/modprobe.d/ndiswrapper
cat: /etc/modprobe.d/ndiswrapper: file not found

floris@floris-NX9010:~$ cat /etc/resolv.conf
nameserver 192.168.2.1

Hope this helps....

F

[auisce]

This is all a bit beyond me.
Can any of this fix the apparently common problem where knetwork manager or whatever freezes at 28% or 50 something%?
I'm having that very same, all too common problem where I just can't connect to a wireless network. My internet is via a wireless router so without access to the network I have no internet which has rendered Linux about as useful as Windows 1.
Everything is fine in Windows but Linux is... a bit broken, to put it nicely.

I have a Lynksys/Cisco WAG54GS 54Mbps 802.11g router with built in ADSL modem and ethernet switch.
I'm using WPA-PSK and TKIP (whatever they are). I can't use WPA2 and AES or anything like that at the moment because others on the network get all upety and I'm absolutely not using WEP.

The systems I want to connect with Linux have a Netgear WG311T (Atheros) and onbourd Atheros (Toshiba laptop)

Any help would be gratefully appreciated. In the mean time I'll study this and other threads in more detail.

[wieman01]

Looks fine. I have corrected the "wpa-ap-scan" section as it appears that your router is broadcasting the ESSID instead of hiding it. So "1" is the right value.

auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid xxxx
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk xxxxx
Now please restart the network and possibly post the results if you still can't connect:

sudo ifdown -v wlan0

sudo ifup -v wlan0
Does your Windows driver ("ndiswrapper") support WPA2? And have you generated your passphrase as described in the tutorial?

[frkstein]

wieman01, this is a great howto which you have put together. It made getting my wireless working relatively easy, but I do have one problem. Is there any work around for having to issue the following each time I reboot the system?

sudo ifdown eth1

sudo ifup eth1

If it was just me using this system I suppose I could live with this, but since my wife uses it, I would like wireless to just work when she boots up.

I tried creating a script to be run upon startup which would execute the ifdown/ifup commands for me, but it doesn't seem to work. Can someone please provide some insight why they might not be working? Any help would be greatly appreciated.

[wieman01]

wieman01, this is a great howto which you have put together. It made getting my wireless working relatively easy, but I do have one problem. Is there any work around for having to issue the following each time I reboot the system?

sudo ifdown eth1

sudo ifup eth1

If it was just me using this system I suppose I could live with this, but since my wife uses it, I would like wireless to just work when she boots up.

I tried creating a script to be run upon startup which would execute the ifdown/ifup commands for me, but it doesn't seem to work. Can someone please provide some insight why they might not be working? Any help would be greatly appreciated.
Thanks, mate. :-)

Have you tried out the solution described in the second post? If that fails, I'll work out another solution.

[frkstein]

Yes, I tried that, no luck. :-(

[wieman01]

Yes, I tried that, no luck. :-(
Could you run the following commands for me and post the results please?

gedit /etc/init.d/wireless-network.sh

sudo /etc/rcS.d/S40wireless-network
Does the second line restart the network?

[frkstein]

I am at work currently. I will try your suggestions when I get home and post the results.

[wieman01]

I am at work currently. I will try your suggestions when I get home and post the results.
Alright. Just need to see if you may have missed something. Not that I am suggesting that you have :-) but you never know. See you then.

[Floor19]

Hi Wieman

I tried the different scan option but i could not connect to my AP because it IS hidden. As stated before the restart option is not working. If I do networking stop and then start it works. But it does not renew after leasetime.

As asked the out for:

floris@floris-NX9010:~$ sudo ifdown -v wlan0

Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 10345
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:14:bf:3d:ea:14
Sending on LPF/wlan0/00:14:bf:3d:ea:14
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 192.168.2.1 port 67
ifconfig wlan0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan0.pid
Stopped /sbin/wpa_supplicant (pid 10300).

floris@floris-NX9010:~$ sudo ifup -v wlan0

Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan0
wpa_supplicant: wpa-ap-scan 2 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "Depeche" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise CCMP -- OK
wpa_supplicant: wpa-group CCMP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto RSN -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:14:bf:3d:ea:14
Sending on LPF/wlan0/00:14:bf:3d:ea:14
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPOFFER from 192.168.2.1
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPACK from 192.168.2.1
bound to 192.168.2.2 -- renewal in 77010 seconds.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant
floris@floris-NX9010:~$

I do not understand because on my othe notebook with edgy everything works fine (same linksys wifi card!)

F

[ziggie216]

any idea if the .cer file can be use for PEAP?

[frkstein]

I tried executing your script. It said it restarted the network, but I still had no connection with out having to do ifdown/ifup.

[wieman01]

I tried executing your script. It said it restarted the network, but I still had no connection with out having to do ifdown/ifup.
Weird...

Option A:
We could replace the contents of the script with the commands you are using to restart your network:

sudo gedit /etc/init.d/wireless-network.sh
Just remove "/etc/init.d/networking restart" and add your stuff.

Option B:
Change of boot sequence:

sudo ln -s /etc/init.d/wireless-network.sh /etc/rcS.d/S80wireless-network
Delete old link:

sudo rm /etc/rcS.d/S40wireless-network
This ought to work but there has been at least 1 other user who could not get it to work for a reason unknown to me. If all this fails, we can create a desktop icon for you that will restart the network upon double-click.

[wieman01]

Hi Wieman

I tried the different scan option but i could not connect to my AP because it IS hidden. As stated before the restart option is not working. If I do networking stop and then start it works. But it does not renew after leasetime.

As asked the out for:

Listening on LPF/wlan0/00:14:bf:3d:ea:14
Sending on LPF/wlan0/00:14:bf:3d:ea:14
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPOFFER from 192.168.2.1
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPACK from 192.168.2.1
bound to 192.168.2.2 -- renewal in 77010 seconds.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant
floris@floris-NX9010:~$
But you do establish a connection after restarting the network mantually, right? At least that's what I see from here.

bound to 192.168.2.2 -- renewal in 77010 seconds.
But it fails while the computer boots up? Is that the trouble?

[wieman01]

any idea if the .cer file can be use for PEAP?
It should be possible. Would you mind taking a look at this thread (http://ubuntuforums.org/showthread.php?t=304706)? The very first post suggests a solution, however, no one has confirmed yet whether it works or not. Tester are most welcome, I will try to give you a hand if needed.

[Floor19]

But you do establish a connection after restarting the network mantually, right? At least that's what I see from here.

But it fails while the computer boots up? Is that the trouble?

That is correct!

[wieman01]

That is correct!
Perhaps... but I am only guessing... choosing a different boot sequence number would help. What happens if you use S90 instead for instance? Please try that and let me know how you go. Others seem to face similar problems.

[jbeiter]

It should be possible. Would you mind taking a look at this thread (http://ubuntuforums.org/showthread.php?t=304706)? The very first post suggests a solution, however, no one has confirmed yet whether it works or not. Tester are most welcome, I will try to give you a hand if needed.
Hi wieman01,

I've been struggling to get this work for an embarassingly long time. I'm not even sure if wpa is reading my cert file correctly.

My network admin gave me the cert file that is provided to windows users "acs_server_cert.cer" but I'm not sure if I need to convert this to some other format (pem?). I tried converting it with openssl using some tips from other threads but it either does nothing but change the extension or generates errors depending on the switches.


Any help would be appreciated. If I can get past this cert file, I'd be glad to try your scripting process out.

[wieman01]

Hi wieman01,

I've been struggling to get this work for an embarassingly long time. I'm not even sure if wpa is reading my cert file correctly.

My network admin gave me the cert file that is provided to windows users "acs_server_cert.cer" but I'm not sure if I need to convert this to some other format (pem?). I tried converting it with openssl using some tips from other threads but it either does nothing but change the extension or generates errors depending on the switches.


Any help would be appreciated. If I can get past this cert file, I'd be glad to try your scripting process out.
Would you mind posting your configuration?

gedit /etc/network/interfaces
Where is the file located? Anything else I should know about your network?

Let's see... maybe we find a solution together.

[jbeiter]

my /etc/network/interfaces:
---------------------------------------------------------
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp
pre-up wpa_supplicant -Bw -Dwext -ieth1 -c/etc/wpa_supplicant/wpa_supplicant.conf
post-down killall -q wpa_supplicant
---------------------------------------------------------

my wpa_supplicant.conf file:
---------------------------------------------------------
# blah blah blah

ctrl_interface=/var/run/wpa_supplicant
ap_scan=2

network={
ssid="my work SSID"
scan_ssid=1
stakey=1
proto=RSN
key_mgmt=WPA-EAP
pairwise=CCMP
group=CCMP
#group=TKIP
eap=PEAP
phase1="peapver=1"
phase2="auth=MSCHAPV2"
identity="workADdomain\myMSuid"
password="myMSpassword"
ca_cert="/usr/local/ssl/mycert.pem"
priority=10
}

network={
ssid="obscure home network SSID"
key_mgmt=NONE
priority=1
}

-------------------------------------------------------------------------------------------------------------------

My hope was to have wireless come up automatically then join to the right network, depending if I am at work or at home. It usually joins up at home okay but sometimes thrashes between trying to join at home and looking for a work SSID.

I'm not sure if my approach is flawed, but basically my understanding is that networking would be started by rc?.d/networking and use the interfaces file to kick off wpa_supplicant.. ideally wpa would join the right wireless network, then rc would kick off dhclient after patiently waiting.. it doesn't seem to work like that though.

I've tried playing with kwlan, wicd, and several other gnome/kde network tools without success. Windows PCs join right up to this network with no headaches at all.

[frkstein]

I constructed a script which looks like the following:

ifdown eth1
sleep 2
ifup eth1

I put it in the file /etc/init.d/wireless-network.sh. I also created a symlink like such /etc/rcS.d/S90wireless-network.

No luck running this. If I execute my script once logged in it brings up the network connection just fine. Doing some research I looked in my /ver/log/messages and found this.

Jun 5 19:31:39 ubuntu-frontend kernel: [ 33.390868] ndiswrapper version 1.38 loaded (preempt=no,smp=yes)
Jun 5 19:31:39 ubuntu-frontend kernel: [ 33.511810] ndiswrapper: driver bcmwl5 (Broadcom,02/11/2005, 3.100.64.0) loaded
Jun 5 19:31:39 ubuntu-frontend kernel: [ 33.512210] ACPI: PCI Interrupt 0000:00:0b.0[A] -> GSI 19 (level, low) -> IRQ 20
Jun 5 19:31:39 ubuntu-frontend kernel: [ 33.520419] ndiswrapper: using IRQ 20
Jun 5 19:31:39 ubuntu-frontend kernel: [ 34.206339] wlan0: ethernet device 00:12:17:85:57:99 using NDIS driver: bcmwl5, version: 0x3644000, NDIS version: 0x501, vendor: '', 14E4:4318.5.conf
Jun 5 19:31:39 ubuntu-frontend kernel: [ 34.206384] wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK
Jun 5 19:31:39 ubuntu-frontend kernel: [ 34.208276] usbcore: registered new interface driver ndiswrapper
Jun 5 19:31:39 ubuntu-frontend kernel: [ 34.245141] ndiswrapper: changing interface name from 'wlan0' to 'eth1'
Jun 5 19:31:39 ubuntu-frontend kernel: [ 34.270792] Adding 1510068k swap on /dev/disk/by-uuid/f7868b73-6bbc-40b5-97b6-ae09634e4c89. Priority:-1 extents:1 across:1510068k
Jun 5 19:31:39 ubuntu-frontend kernel: [ 34.367358] NET: Registered protocol family 17
Jun 5 19:31:39 ubuntu-frontend kernel: [ 34.591293] NET: Registered protocol family 10
Jun 5 19:31:39 ubuntu-frontend kernel: [ 34.591439] lo: Disabled Privacy Extensions
Jun 5 19:31:39 ubuntu-frontend kernel: [ 34.591514] ADDRCONF(NETDEV_UP): eth1: link is not ready
Jun 5 19:31:39 ubuntu-frontend kernel: [ 34.756060] EXT3 FS on sda1, internal journal
Jun 5 19:31:39 ubuntu-frontend kernel: [ 37.531645] ADDRCONF(NETDEV_UP): eth1: link is not ready
Jun 5 19:31:39 ubuntu-frontend kernel: [ 37.951735] No dock devices found.
Jun 5 19:31:39 ubuntu-frontend kernel: [ 38.019902] input: Power Button (FF) as /class/input/input4
Jun 5 19:31:39 ubuntu-frontend kernel: [ 38.026025] ACPI: Power Button (FF) [PWRF]
Jun 5 19:31:39 ubuntu-frontend kernel: [ 38.074390] input: Power Button (CM) as /class/input/input5
Jun 5 19:31:39 ubuntu-frontend kernel: [ 38.080432] ACPI: Power Button (CM) [PWRB]
Jun 5 19:31:39 ubuntu-frontend kernel: [ 38.235739] Using specific hotkey driver
Jun 5 19:31:39 ubuntu-frontend kernel: [ 38.397717] pcc_acpi: loading...
Jun 5 19:31:41 ubuntu-frontend kernel: [ 41.152741] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Jun 5 19:31:43 ubuntu-frontend dhcdbd: Started up.

There are lots of messages that the eth1 link is not ready. Could this be the problem?

[ice60]

If broadcast is disabled, the setting is fine. If DHCP is what you need, then then network section should look a bit different though:

DHCP will do the rest for you, assign an IP and select the correct nameserver, gateway, etc. Time to relax. :-)

That should do given that your device is working (i.e. connects to unsecured networks just fine) and supports WPA.

Don't worry about security in this case. WPA is considered secure by all standards. If you still have concerns configure your router to use WPA2 (= AES) instead which is the best encryption method you can get. As highlighted, with a good password there is nothing you should worry about at all. :-)thanks for the help. i can connect to my router fine now, i've no idea about unsecured networks though because i uninstalled all the GUI tools i had lol.

if i can see an unsecured network with iwlist scan, how can i connect using a term?

i wasn't worried about WPA it was more about trusting i got everything right, but i'm not worried now.

also, i was looking at my startups in /etc/rcS.d/ and i already have something starting with S40, do you know if two processes can start with the same s40 value?

[wieman01]

my /etc/network/interfaces:
---------------------------------------------------------
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp
pre-up wpa_supplicant -Bw -Dwext -ieth1 -c/etc/wpa_supplicant/wpa_supplicant.conf
post-down killall -q wpa_supplicant
---------------------------------------------------------

my wpa_supplicant.conf file:
---------------------------------------------------------
# blah blah blah

ctrl_interface=/var/run/wpa_supplicant
ap_scan=2

network={
ssid="my work SSID"
scan_ssid=1
stakey=1
proto=RSN
key_mgmt=WPA-EAP
pairwise=CCMP
group=CCMP
#group=TKIP
eap=PEAP
phase1="peapver=1"
phase2="auth=MSCHAPV2"
identity="workADdomain\myMSuid"
password="myMSpassword"
ca_cert="/usr/local/ssl/mycert.pem"
priority=10
}

network={
ssid="obscure home network SSID"
key_mgmt=NONE
priority=1
}

-------------------------------------------------------------------------------------------------------------------

My hope was to have wireless come up automatically then join to the right network, depending if I am at work or at home. It usually joins up at home okay but sometimes thrashes between trying to join at home and looking for a work SSID.

I'm not sure if my approach is flawed, but basically my understanding is that networking would be started by rc?.d/networking and use the interfaces file to kick off wpa_supplicant.. ideally wpa would join the right wireless network, then rc would kick off dhclient after patiently waiting.. it doesn't seem to work like that though.

I've tried playing with kwlan, wicd, and several other gnome/kde network tools without success. Windows PCs join right up to this network with no headaches at all.
"Using "/etc/wpa_supplicant/wpa_supplicant.conf" is significantly different from my approach, but correct. That said, can you connect to the network at work at all?

[wieman01]

I constructed a script which looks like the following:

ifdown eth1
sleep 2
ifup eth1

I put it in the file /etc/init.d/wireless-network.sh. I also created a symlink like such /etc/rcS.d/S90wireless-network.

No luck running this. If I execute my script once logged in it brings up the network connection just fine. Doing some research I looked in my /ver/log/messages and found this.

Jun 5 19:31:39 ubuntu-frontend kernel: [ 33.390868] ndiswrapper version 1.38 loaded (preempt=no,smp=yes)
Jun 5 19:31:39 ubuntu-frontend kernel: [ 33.511810] ndiswrapper: driver bcmwl5 (Broadcom,02/11/2005, 3.100.64.0) loaded
Jun 5 19:31:39 ubuntu-frontend kernel: [ 33.512210] ACPI: PCI Interrupt 0000:00:0b.0[A] -> GSI 19 (level, low) -> IRQ 20
Jun 5 19:31:39 ubuntu-frontend kernel: [ 33.520419] ndiswrapper: using IRQ 20
Jun 5 19:31:39 ubuntu-frontend kernel: [ 34.206339] wlan0: ethernet device 00:12:17:85:57:99 using NDIS driver: bcmwl5, version: 0x3644000, NDIS version: 0x501, vendor: '', 14E4:4318.5.conf
Jun 5 19:31:39 ubuntu-frontend kernel: [ 34.206384] wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK
Jun 5 19:31:39 ubuntu-frontend kernel: [ 34.208276] usbcore: registered new interface driver ndiswrapper
Jun 5 19:31:39 ubuntu-frontend kernel: [ 34.245141] ndiswrapper: changing interface name from 'wlan0' to 'eth1'
Jun 5 19:31:39 ubuntu-frontend kernel: [ 34.270792] Adding 1510068k swap on /dev/disk/by-uuid/f7868b73-6bbc-40b5-97b6-ae09634e4c89. Priority:-1 extents:1 across:1510068k
Jun 5 19:31:39 ubuntu-frontend kernel: [ 34.367358] NET: Registered protocol family 17
Jun 5 19:31:39 ubuntu-frontend kernel: [ 34.591293] NET: Registered protocol family 10
Jun 5 19:31:39 ubuntu-frontend kernel: [ 34.591439] lo: Disabled Privacy Extensions
Jun 5 19:31:39 ubuntu-frontend kernel: [ 34.591514] ADDRCONF(NETDEV_UP): eth1: link is not ready
Jun 5 19:31:39 ubuntu-frontend kernel: [ 34.756060] EXT3 FS on sda1, internal journal
Jun 5 19:31:39 ubuntu-frontend kernel: [ 37.531645] ADDRCONF(NETDEV_UP): eth1: link is not ready
Jun 5 19:31:39 ubuntu-frontend kernel: [ 37.951735] No dock devices found.
Jun 5 19:31:39 ubuntu-frontend kernel: [ 38.019902] input: Power Button (FF) as /class/input/input4
Jun 5 19:31:39 ubuntu-frontend kernel: [ 38.026025] ACPI: Power Button (FF) [PWRF]
Jun 5 19:31:39 ubuntu-frontend kernel: [ 38.074390] input: Power Button (CM) as /class/input/input5
Jun 5 19:31:39 ubuntu-frontend kernel: [ 38.080432] ACPI: Power Button (CM) [PWRB]
Jun 5 19:31:39 ubuntu-frontend kernel: [ 38.235739] Using specific hotkey driver
Jun 5 19:31:39 ubuntu-frontend kernel: [ 38.397717] pcc_acpi: loading...
Jun 5 19:31:41 ubuntu-frontend kernel: [ 41.152741] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Jun 5 19:31:43 ubuntu-frontend dhcdbd: Started up.

There are lots of messages that the eth1 link is not ready. Could this be the problem?
Strange... the log file seems to suggest that you have installed "ndiswrapper" while your interface name is "wlan0", then later on it changes to "eth1". Which one is right, which one is wrong? What does a scan yield?

iwlist scan
If "eth1" is the right interface, then perhaps "ndiswrapper" (wlan0) is the culprit, could that be? You are definitely right in that the log looks odd. "eth1" comes up too late so I suspect that the adapter is down by the time we start the network.

[wieman01]

also, i was looking at my startups in /etc/rcS.d/ and i already have something starting with S40, do you know if two processes can start with the same s40 value?
Yes, that is no problem at all. Alternatively you could choose S41, but S40 will do as well.

[Floor19]

Perhaps... but I am only guessing... choosing a different boot sequence number would help. What happens if you use S90 instead for instance? Please try that and let me know how you go. Others seem to face similar problems.

This does not solve it. It only works when I do:

sudo /etc/init.d/networking stop
sudo /etc/init.d/networking start

/etc/init.d/networking restart will result in no DHCP lease....

[frkstein]

Would you like to see the results of iwlist scan before or after I bring the network up after a reboot?

[wieman01]

Would you like to see the results of iwlist scan before or after I bring the network up after a reboot?
Before you do, please.

[wieman01]

This does not solve it. It only works when I do:

sudo /etc/init.d/networking stop
sudo /etc/init.d/networking start

/etc/init.d/networking restart will result in no DHCP lease....
Jee... I have no idea what's going on... Anybody else with a good suggestion? Could you open a new thread and ask the community for help? I would like to find a solution since a number of other folks seem to have the same problem as you.

[frkstein]

here is the result of iwlist scan

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:11:50:29:81:12
ESSID:"myessid"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:73/100 Signal level:-49 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 02 - Address: 00:12:88:AA:15:71
ESSID:" "
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.457 GHz (Channel 10)
Quality:12/100 Signal level:-88 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0

[wieman01]

here is the result of iwlist scan

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:11:50:29:81:12
ESSID:"myessid"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:73/100 Signal level:-49 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 02 - Address: 00:12:88:AA:15:71
ESSID:" "
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.457 GHz (Channel 10)
Quality:12/100 Signal level:-88 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Ok, let's try something else and restart the network using another run-level ("# 5 - Multi-user mode, graphical login").

sudo ln -s /etc/init.d/wireless-network.sh /etc/rc5.d/K99wireless-network
Let me know how this goes. It is not quite correct to restart the network here, but if everything fails what options do we have?! :-)

EDIT:
http://www.iodynamics.com/education/runlevel.html

[jbeiter]

"Using "/etc/wpa_supplicant/wpa_supplicant.conf" is significantly different from my approach, but correct. That said, can you connect to the network at work at all?

With Windows, no problem. It joins and stays joined. (Same hardware/diff partition, Cisco ACS, Cisco APs)
With Linux and this SSID with the cert, not at all. (Cisco ACS, Cisco APs)
With Linux and an SSID that supports psk, its flakey and unreliable. Keeps dropping. (Cisco ACS, Cisco APs)
With Linux and my Home SSID (hidden, MAC bound) no problems. (Linksys Wireless router)

Using your method, is there a syntax for supplying a cert (.cer or .pem) file?
Is there a way to support multiple networks (eg: home, work) using your method? I didn't see any hints in examples.
Do you know if there is a special way to convert a Cisco ACS cert file to use on Linux with wpasupplicant?

I would like to try your approach, since I don't seem to be getting anywhere presently.

[wieman01]

Using your method, is there a syntax for supplying a cert (.cer or .pem) file?
All I can offer at this stage is this (http://ubuntuforums.org/showthread.php?t=304706). Try the first script although I have not been able to test it myself.

Is there a way to support multiple networks (eg: home, work) using your method?
Sadly, no. It's stationary.

Do you know if there is a special way to convert a Cisco ACS cert file to use on Linux with wpasupplicant?
Are we talking about PEAP now or any sort of propriotary Cisco protocol?

Sorry I cannot be of more help right now. Guess point 2 (multiple networks) will pose a problem to you anyway, so this approach won't be very useful.

[clegg13]

after trying for a few days using this and many other helpful guides (and making my own post requiring help) i am finally gonna bug you wieman for help =)


i have a dell 1500 -n minicard on my XPS m1210. the same machine connects perfectly through windows. my router is set to use mixed (wep1+2) security. the machine connects fine to (in ubuntu) to an unsecured network that belongs to my neighbor =p, but not to mine, can never associate, i have tried the firmware method, done clean installs used the 'mixed' settings from your guide, used every network manager i could (network-manager, wifi radar, even wicd) some of them dont even connect to the unsecured network i previously talked about. but now as i write this i have no manager installed (just use system>admin>network) and at least i can connect to the other network. iwconfig and iwlist both clearly show (at least) my own network, but no luck on connecting. let me know what outputs i need to give to you for you to help me and we can start from there. really appreciate this =)

[jinsungmin]

Thanks for this awesome tutorial, I got my WPA2 to work for my laptop with IPW2200 , only problem I have is that everytime I boot up the PC , I have to do the following command to get wireless going

sudo ifdown eth0
sudo ifup eth0

and then it will pull a DHCP address off my router, is there anyway to make a script to run each time I boot up ?so that it automatically restart my network ?

[wieman01]

Thanks for this awesome tutorial, I got my WPA2 to work for my laptop with IPW2200 , only problem I have is that everytime I boot up the PC , I have to do the following command to get wireless going

sudo ifdown eth0
sudo ifup eth0

and then it will pull a DHCP address off my router, is there anyway to make a script to run each time I boot up ?so that it automatically restart my network ?
Posts #2 and possiby #584 yield no results at all?

[wieman01]

after trying for a few days using this and many other helpful guides (and making my own post requiring help) i am finally gonna bug you wieman for help =)


i have a dell 1500 -n minicard on my XPS m1210. the same machine connects perfectly through windows. my router is set to use mixed (wep1+2) security. the machine connects fine to (in ubuntu) to an unsecured network that belongs to my neighbor =p, but not to mine, can never associate, i have tried the firmware method, done clean installs used the 'mixed' settings from your guide, used every network manager i could (network-manager, wifi radar, even wicd) some of them dont even connect to the unsecured network i previously talked about. but now as i write this i have no manager installed (just use system>admin>network) and at least i can connect to the other network. iwconfig and iwlist both clearly show (at least) my own network, but no luck on connecting. let me know what outputs i need to give to you for you to help me and we can start from there. really appreciate this =)
Hi Clegg,

When you scan for your own network what is the output?

iwlist scan
I would turn off all security first and see if you can connect to it. It would also be worthwhile taking a glance at:

sudo gedit /etc/network/interfaces
Once you can connect to your own unsecured network, we continue from there. Guess it should be a piece of cake since you can connect to your neighbor's. :-)

[tony_c]

Great HOWTO wieman01 !!

I am new to Linux and I followed your instructions and also the #2 post to get it in the start-up (I used "rcS.d/S41wireless-network", i.e. made it follow just after the S40networking item in the boot sequence) since as your #1 post predicted, it didn't work without that network restart after a boot.

Interestingly, my interface is actually on eth2 not wlan#, which fooled me at first, but once I had the WPA stuff in the auto eth2 section of the interfaces file and removed the wlan# item, it worked like a dream.

Once again -- thank you so much!!

[clegg13]

@ wieman01

iwlist scan

*******************iwlist scan output*************************

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:18:4D:18:62:A2
ESSID:"Clegg Home"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.427 GHz (Channel 4)
Quality:79/100 Signal level:-45 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
************************* iwlist scan output end ******************************


this is right now, i am online from my own network as i write and the default network manager was not able to (it did not get an IP), although i used wifi radar and it connected with no problems. please note that this does not include my neighbor's network because i believe his router is off (can't even see it in windows at the moment). but the good thing for now is im on mine =) now to secure it .........

WPA-PSK (TKIP) + WPA2-PSK (AES)
this above is the only security setting avaialble on my router right now since it set to attain 270mbps (wirelss n ?), if this etting is off it can connect maximum at 130mbps (like right now) preferable these are the securit options i would like on so that i may avail the full potential of the card and the router if possible. if it is not possible then i guess i can swith to `wirelss g` and i have many other security options available, heres the options (if the ones above are not workable)

*************** router security options ****************

Security Options

* None - no data encryption
* WEP (Wired Equivalent Privacy) - use WEP 64 or 128 bit data encryption.This option is only available for the g & b wireless mode.
* WPA-PSK (Wi-Fi Protected Access Pre-Shared Key ) - use WPA-PSK standard encryption. This option is only available for the g & b wireless mode.
* WPA2-PSK (Wi-Fi Protected Access Pre-Shared Key ) - use WPA2-PSK standard encryption. This option is only available for the g & b wireless mode.
* WPA-PSK + WPA2-PSK (Wi-Fi Protected Access Pre-Shared Key ) - use both WPA-PSK and WPA2-PSK standard encryption.A high performance client like the NETGEAR WN511B must connect using WPA2-PSK in order to receive maximum performance. Wireless clients that connect to this router using WPA-PSK will run at no more than 802.11g speed.
*************** wireless security options end **********************

here is my network/interfaces output (now since im un secured)

********************* sudo gedit /etc/network/interfaces **************************
auto lo
iface lo inet loopback

auto eth1
iface eth1 inet dhcp

auto eth2
iface eth2 inet dhcp

iface eth0 inet dhcp

auto wlan0
iface wlan0 inet dhcp
********************** sudo gedit /etc/network/interfaces ******************************

please note that i have tried the 'mixed' settings (and some ohers. as i saw fit) from your sample set of settings. i primarily tried the types with both types on at the same time. now all that is gone since im on dhcp (and no use since they dint work =) ). so i guess you suggest on that end.

also i believe i am not sure what use is the key gneerated from that website you linked (since it does not take any input from me) i just used the hex output as generated from my own network password as i typed it in this command

wpa_passphrase 'your_essid' 'your_ascii_key'

i used my ssid and and typed in my password (as set in my router by me) and used the 'psk=' hex output in the 'wpa-psk <your_hex_key>' field.


well i guess its over to you now =)

[monomaniacpat]

I cannot get this to work and I'm really confused after a number of hours looking at it.

I think my main problem is that I have an RT8180 wireless card, which I understand does not work.

I followed the instructions linked to on the serialmonkey website under stumbling blocks, but I don't understand them fully. I get an error message that "set" is an invalid command.

These instructions are also listed here (http://ubuntuforums.org/showthread.php?t=400236) - don't know if you knew that.

If you could prompt me for the relevant info, I will come and try and make my problem clearer. If the workaround is not a good option, I am prepared to use ndiswrapper, except that I don't know how to stop the open source drivers loading with linux and to switch on ndirwrapper automatically. All the tutorials are rubbish :'(

Sorry if this is difficult to understand.

EDIT: Someone has pointed out to me in the other thread that my card is a Realtek one, not Ralink. What's the correct driver for that? To be precise, it is a Linksys WPC11 v.4 rtl8180 cardbus/PCMCIA card. Would one of the other drivers work for it/can you use rtl8180 with WPA1?

thanks again.

[wieman01]

@ wieman01

iwlist scan

*******************iwlist scan output*************************

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:18:4D:18:62:A2
ESSID:"Clegg Home"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.427 GHz (Channel 4)
Quality:79/100 Signal level:-45 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
************************* iwlist scan output end ******************************


this is right now, i am online from my own network as i write and the default network manager was not able to (it did not get an IP), although i used wifi radar and it connected with no problems. please note that this does not include my neighbor's network because i believe his router is off (can't even see it in windows at the moment). but the good thing for now is im on mine =) now to secure it .........

WPA-PSK (TKIP) + WPA2-PSK (AES)
this above is the only security setting avaialble on my router right now since it set to attain 270mbps (wirelss n ?), if this etting is off it can connect maximum at 130mbps (like right now) preferable these are the securit options i would like on so that i may avail the full potential of the card and the router if possible. if it is not possible then i guess i can swith to `wirelss g` and i have many other security options available, heres the options (if the ones above are not workable)

*************** router security options ****************

Security Options

* None - no data encryption
* WEP (Wired Equivalent Privacy) - use WEP 64 or 128 bit data encryption.This option is only available for the g & b wireless mode.
* WPA-PSK (Wi-Fi Protected Access Pre-Shared Key ) - use WPA-PSK standard encryption. This option is only available for the g & b wireless mode.
* WPA2-PSK (Wi-Fi Protected Access Pre-Shared Key ) - use WPA2-PSK standard encryption. This option is only available for the g & b wireless mode.
* WPA-PSK + WPA2-PSK (Wi-Fi Protected Access Pre-Shared Key ) - use both WPA-PSK and WPA2-PSK standard encryption.A high performance client like the NETGEAR WN511B must connect using WPA2-PSK in order to receive maximum performance. Wireless clients that connect to this router using WPA-PSK will run at no more than 802.11g speed.
*************** wireless security options end **********************

here is my network/interfaces output (now since im un secured)

********************* sudo gedit /etc/network/interfaces **************************
auto lo
iface lo inet loopback

auto eth1
iface eth1 inet dhcp

auto eth2
iface eth2 inet dhcp

iface eth0 inet dhcp

auto wlan0
iface wlan0 inet dhcp
********************** sudo gedit /etc/network/interfaces ******************************

please note that i have tried the 'mixed' settings (and some ohers. as i saw fit) from your sample set of settings. i primarily tried the types with both types on at the same time. now all that is gone since im on dhcp (and no use since they dint work =) ). so i guess you suggest on that end.

also i believe i am not sure what use is the key gneerated from that website you linked (since it does not take any input from me) i just used the hex output as generated from my own network password as i typed it in this command

wpa_passphrase 'your_essid' 'your_ascii_key'

i used my ssid and and typed in my password (as set in my router by me) and used the 'psk=' hex output in the 'wpa-psk <your_hex_key>' field.


well i guess its over to you now =)
Could you set your router to use WPA and TKIP, then post the script you intend to use ("/etc/network/interfaces"):

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid <your_essid>
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <your_hex_key>
Then restart the network (also post the results please):

sudo ifdown -v wlan0

sudo ifup -v wlan0
Does the driver that you have installed via "ndiswrapper" support WPA at all?

Let's not complicate matters and connect via Wireless G first of all. :-)

[wieman01]

I cannot get this to work and I'm really confused after a number of hours looking at it.

I think my main problem is that I have an RT8180 wireless card, which I understand does not work.

I followed the instructions linked to on the serialmonkey website under stumbling blocks, but I don't understand them fully. I get an error message that "set" is an invalid command.

These instructions are also listed here (http://ubuntuforums.org/showthread.php?t=400236) - don't know if you knew that.

If you could prompt me for the relevant info, I will come and try and make my problem clearer. If the workaround is not a good option, I am prepared to use ndiswrapper, except that I don't know how to stop the open source drivers loading with linux and to switch on ndirwrapper automatically. All the tutorials are rubbish :'(

Sorry if this is difficult to understand.

EDIT: Someone has pointed out to me in the other thread that my card is a Realtek one, not Ralink. What's the correct driver for that? To be precise, it is a Linksys WPC11 v.4 rtl8180 cardbus/PCMCIA card. Would one of the other drivers work for it/can you use rtl8180 with WPA1?

thanks again.
I guess "wext" would be the driver which comes closest. But before you go ahead and enable WPA, have you been able to connect to any network while security is turned completely off?

"ndiswrapper" is a good option indeed. But let's try this first:

iwlist scan

[clegg13]

@ wieman01:


no show, ill give you the required outputs soon, but basically it does not associate ..... wexp drivers are on (i think, tell me a way to check kindly) .....


i still feel its in the key .... kindly explain the whole key thing. the link you gave seems dead ended to me as i can not input anything there to convert to hex ?? or am i totally missing something ?

i just use the paskey command, give my essid and netwok password (as i typy into my router) in ascii and use the password's hex input in the key as stated above ..... could you comment on this kindly ?

thanks so much again for your time and support =)

will be posting the ifup and ifdown outputs soon, but basically ifdown goes all ok, then all oks in ifup untill the point it seeks a dhcp response , then nada. makes me think the key did not get accepted.

[monomaniacpat]

I guess "wext" would be the driver which comes closest. But before you go ahead and enable WPA, have you been able to connect to any network while security is turned completely off?

"ndiswrapper" is a good option indeed. But let's try this first:

I have connected with WEP through the rtl8180 driver. Did you want me to try with wext?

Sorry I haven't got the output, I'll get it later.

EDIT, here we go:


patrick@inspiron-8200:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:15:E9:27:09:5E
ESSID:"PolyandorUS"
Protocol:IEEE 802.11bg
Mode:Master
Channel:6
Encryption key:on
Bit Rates:54 Mb/s
Extra: Rates (Mb/s): 1 2 5.5 6 9 11 12 18 22 24 36 48 54
Quality:225 Signal level:0 Noise level:96
Extra: Last beacon: 1474ms ago

sit0 Interface doesn't support scanning.


Here's the contents of my /etc/network/interfaces:


auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet static
address 192.168.1.5
gateway 192.168.1.1
netmask 255.255.255.0
wpa-driver wext
wpa-ssid PolyandorUS
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <64 character string>

My router only supports WPA1.

[wieman01]

@ wieman01:
i still feel its in the key .... kindly explain the whole key thing. the link you gave seems dead ended to me as i can not input anything there to convert to hex ?? or am i totally missing something ?

i just use the paskey command, give my essid and netwok password (as i typy into my router) in ascii and use the password's hex input in the key as stated above ..... could you comment on this kindly ?

thanks so much again for your time and support =)

will be posting the ifup and ifdown outputs soon, but basically ifdown goes all ok, then all oks in ifup untill the point it seeks a dhcp response , then nada. makes me think the key did not get accepted.
The password section was a bit confusing... I have changed it once again. The idea is that you use your router's network password and the ESSID which you convert into encrypted passphrase via "wpa_passphrase". So you are on the right track. So forget about the link I had posted, I have removed that section as it seems to confuse people. It was only meant to help people generate a secure password that is long enough and contains special characters, no more no less.

The "wext" driver is the right one for you. But since you are using the Windows driver for your card, I would also check if that driver supports WPA at all. Some drivers don't and the vendor's web site usually provides information concerning it.

If you have any more questions just let me know. We'll sort them out.

[wieman01]

I have connected with WEP through the rtl8180 driver. Did you want me to try with wext?

Sorry I haven't got the output, I'll get it later.

EDIT, here we go:


patrick@inspiron-8200:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:15:E9:27:09:5E
ESSID:"PolyandorUS"
Protocol:IEEE 802.11bg
Mode:Master
Channel:6
Encryption key:on
Bit Rates:54 Mb/s
Extra: Rates (Mb/s): 1 2 5.5 6 9 11 12 18 22 24 36 48 54
Quality:225 Signal level:0 Noise level:96
Extra: Last beacon: 1474ms ago

sit0 Interface doesn't support scanning.


Here's the contents of my /etc/network/interfaces:


auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet static
address 192.168.1.5
gateway 192.168.1.1
netmask 255.255.255.0
wpa-driver wext
wpa-ssid PolyandorUS
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <64 character string>

My router only supports WPA1.
Looks fine actually. However the scan results do not really confirm that you have enabled WPA on the router. Guess you have disabled it temporarily. :-)

Driver "wext" will be fine, but you could also use any other driver that is available for testing. Won't do any harm. Does the Windows driver that you have installed support WPA? Can you check the documentation or something?

Then please also post the results of (while using "wext"):

sudo ifdown -v wlan0

sudo ifup -v wlan0
Just to see what's going on and if there are any error messages. Once you have restarted the network, also this one:

route

[monomaniacpat]

Looks fine actually. However the scan results do not really confirm that you have enabled WPA on the router. Guess you have disabled it temporarily. :-)

Driver "wext" will be fine, but you could also use any other driver that is available for testing. Won't do any harm. Does the Windows driver that you have installed support WPA? Can you check the documentation or something?

Then please also post the results of (while using "wext"):


Just to see what's going on and if there are any error messages. Once you have restarted the network, also this one:

I have definitely not disabled WPA on the router, if that's what you mean.

If I have wext specified in /etc/network/interfaces, does that mean it's in operation? As opposed to the rtl8180 driver.

I can't get confirmation of whether the windows drivers support WPA, though there are a few that list added support with newer drivers available to download.

EDIT: e.g. http://www.driver100.com/driver/306/3324/Linksys_WPC11_WirelessB_Notebook_Adapter_Version_4 .html

Here's the output, including network restart:


patrick@inspiron-8200:~$ sudo /etc/init.d/networking restart
* Reconfiguring network interfaces... Ignoring unknown interface eth0=eth0.
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - [ ok ]




patrick@inspiron-8200:~$ sudo ifdown -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/wpasupplicant
wpa_supplicant: ctrl_interface=/var/run/wpa_supplicant
route del default gw 192.168.1.1 wlan0
ifconfig wlan0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: ctrl_interface=/var/run/wpa_supplicant
wpa_supplicant: terminating wpa_supplicant daemon
Stopped wpa_supplicant (pid 6106).



patrick@inspiron-8200:~$ sudo ifup -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: ctrl_interface=/var/run/wpa_supplicant
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -C /var/run/wpa_supplicant -D wext
Starting /sbin/wpa_supplicant...
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan0
wpa_supplicant: wpa-ap-scan : OK
wpa_supplicant: configuring new network block "0"wpa_supplicant: wpa-ssid : OK
wpa_supplicant: wpa-psk : OK
wpa_supplicant: wpa-pairwise : OK
wpa_supplicant: wpa-group : OK
wpa_supplicant: wpa-key-mgmt : OK
wpa_supplicant: wpa-proto : OK
wpa_supplicant: enabling network 0 : OK

ifconfig wlan0 192.168.1.5 netmask 255.255.255.0 up
route add default gw 192.168.1.1 wlan0
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
Synchronizing clock to ntp.ubuntu.com...




patrick@inspiron-8200:~$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
192.168.1.0 * 255.255.255.0 U 0 0 0 wlan0
default mygateway.ar7 0.0.0.0 UG 0 0 0 wlan0
default mygateway.ar7 0.0.0.0 UG 0 0 0 eth0
patrick@inspiron-8200:~$

[wieman01]

@monomaniacpat:

That's bad news. Yes, you specify the "wpa-driver" in your "interfaces" file and has nothing to do with your actual device driver ("rtl8180").

Starting /sbin/wpa_supplicant...
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
"wext" is definitely the right "wpa-driver" as "ndiswrapper"requires it. However, the problem seems to be that your Windows driver (deployed via "ndiswrapper") does not support WPA. You could try to get hold of the latest Windows driver for your adapter and reinstall it. The vendor's website should through some light on the issue.

[monomaniacpat]

I haven't got ndiswrapper set up, mind. I'm happy to switch to that, if you like. What I don't understand is how I get it to start on boot, as opposed to the open source driver. Would edit /etc/modules do it?

[wieman01]

I haven't got ndiswrapper set up, mind. I'm happy to switch to that, if you like. What I don't understand is how I get it to start on boot, as opposed to the open source driver. Would edit /etc/modules do it?
What confuses me is that your interface is referred to as "wlan0". That name is usually reserved for wireless adapters that have been installed through "ndiswrapper". That's what made me think that you aren't using native drivers.

Nevertheless, the error message is no good news as it basically says that all wpa-related settings in "interfaces" aren't recognized. So unless you install another driver or possibly "ndiswrapper", you'll have to stick to WEP (which I don't recommend of course).

[monomaniacpat]

That's fine, I'll swap to ndiswrapper - just point me in the right direction, would you please?

[wieman01]

That's fine, I'll swap to ndiswrapper - just point me in the right direction, would you please?
Yes, no problem. Could just open a new thread and send me the link via PM? I'll try to guide you through the process.

Please get hold of the latest(!) Windows driver for your adapter. We will need it later. Basically we will follow these steps, but since you are not that familiar with "ndiswrapper", don't do it on your own.

http://ubuntuforums.org/archive/index.php/t-2681.html
http://www.linuxquestions.org/linux/answers/Networking/NDISwrapper_for_RTL8180_mini_HOWTO

We'll create our own little HOWTO after going through it. :-)

[OttifantSir]

I have searched this thread for the answer to something that I didn't get in the OP: I don't want to generate a new hex-key for my network. I have a pre-set password in the router, and I would like to use that on Ubuntu as well. I don't want to change it, simply because it's so hard to remember such a long password, and I wouldn't be able to log on friends that come to my house as easily as just writing in 8 letters. If I were to use a hex-key, I would have to save it to a USB-pendrive (password protected) and wait for it to install on friends' computers, log in to it, open the file with the password, copy and paste.

So, any info on how to use "normal" password (A-Z(and Scandinavian letters),0-9)?

[wieman01]

I have searched this thread for the answer to something that I didn't get in the OP: I don't want to generate a new hex-key for my network. I have a pre-set password in the router, and I would like to use that on Ubuntu as well. I don't want to change it, simply because it's so hard to remember such a long password, and I wouldn't be able to log on friends that come to my house as easily as just writing in 8 letters. If I were to use a hex-key, I would have to save it to a USB-pendrive (password protected) and wait for it to install on friends' computers, log in to it, open the file with the password, copy and paste.

So, any info on how to use "normal" password (A-Z(and Scandinavian letters),0-9)?
Well, if you read the relevant section in the HOWTO more carefully, you will find an answer to your question. :-) You don't need to generate a new password, you can simply use your 8-character password, then generate the hex key for your Ubuntu box. That is by all means necessary as wpa_supplicant encrypts and thus, protects your password.

So essentially no changes to your password at all. Your friends will be able to log on as usual.

[clegg13]

wieman01, i use the windows drivers via ndiswrapper, i use the smae drivers in my windows and it connects, so i guess that means wep is available on my drivers ?

im really stunted, just can't figure out whats wrong =/

[wieman01]

wieman01, i use the windows drivers via ndiswrapper, i use the smae drivers in my windows and it connects, so i guess that means wep is available on my drivers ?
Correct, good point. One thing I noticed just now... Avoid spaces in your ESSID. That could be an issue.

Would you mind posting the contents of your "interfaces" once again? Please without spaces this time. You will need to change your network ID in that case.

[monomaniacpat]

I've set up the interfaces file as before. I don't know how to tell what's going on when it's connecting.

If I leave my wireless card in when I reboot, the startup hangs on setting up network interfaces. It continues if I remove it. I think it's stuck attempting to connect. I can't really test it, given this.

Is the second post relevant to me?

[clegg13]

wieman01, i am at work right now, but the funny thing is, thats exactly what i thought of a little while ago, space in the essid =) ... one of those little un-explainable bugs that you laugh at later. ill go home and give that a shot and let you know the results.

[wieman01]

I've set up the interfaces file as before. I don't know how to tell what's going on when it's connecting.

If I leave my wireless card in when I reboot, the startup hangs on setting up network interfaces. It continues if I remove it. I think it's stuck attempting to connect. I can't really test it, given this.

Is the second post relevant to me?
Only now do I see your post. Must have missed it.

What happens when you restart the network after boot-up (wpa- and interface-section uncommented!):

sudo ifdown -v wlan0

sudo ifup -v wlan0
Post #2 does not seem to relate to your problem... as far as I can tell at this stage. But it may... I have something in mind, but let's see if you can connect at all using WPA.

Any results?

[clegg13]

ok, no luck with the change of ssid, here are the results

iwconfig

lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:"clegg" Nickname:"clegg"
Mode:Managed Frequency:2.412 GHz Access Point: 00:18:4D:18:62:A2
Bit Rate=130 Mb/s Tx-Power:32 dBm
RTS thr=2347 B Fragment thr=2346 B
Power Management:off
Link Quality:90/100 Signal level:-38 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

vmnet1 no wireless extensions.

vmnet8 no wireless extensions.


iwlist scan

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:18:4D:18:62:A2
ESSID:"clegg"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:84/100 Signal level:-42 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK

vmnet1 Interface doesn't support scanning.

vmnet8 Interface doesn't support scanning.



ifconfig


eth0 Link encap:Ethernet HWaddr 00:15:C5:56:77:0A
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:451 errors:0 dropped:0 overruns:0 frame:0
TX packets:383 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:309721 (302.4 KiB) TX bytes:49935 (48.7 KiB)
Interrupt:17

eth0:avah Link encap:Ethernet HWaddr 00:15:C5:56:77:0A
inet addr:169.254.4.176 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Interrupt:17

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:100 errors:0 dropped:0 overruns:0 frame:0
TX packets:100 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:8208 (8.0 KiB) TX bytes:8208 (8.0 KiB)

vmnet1 Link encap:Ethernet HWaddr 00:50:56:C0:00:01
inet addr:172.16.38.1 Bcast:172.16.38.255 Mask:255.255.255.0
inet6 addr: fe80::250:56ff:fec0:1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

vmnet8 Link encap:Ethernet HWaddr 00:50:56:C0:00:08
inet addr:172.16.187.1 Bcast:172.16.187.255 Mask:255.255.255.0
inet6 addr: fe80::250:56ff:fec0:8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

wlan0 Link encap:Ethernet HWaddr 00:16:CF:95:B3:86
inet6 addr: fe80::216:cfff:fe95:b386/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:443 errors:0 dropped:0 overruns:0 frame:0
TX packets:562 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:50741 (49.5 KiB) TX bytes:71074 (69.4 KiB)
Interrupt:17 Memory:ecffc000-ed000000

wlan0:ava Link encap:Ethernet HWaddr 00:16:CF:95:B3:86
inet addr:169.254.8.222 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Interrupt:17 Memory:ecffc000-ed000000



/etc/network/interfaces


auto lo
iface lo inet loopback


auto eth1
iface eth1 inet dhcp

auto eth2
iface eth2 inet dhcp


auto eth0
iface eth0 inet dhcp


auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid clegg
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk 14ebfea353d56150f70ee95fc1e77161fc11ff9faab1100bab 33eb2a129ff37e




/et/modprobe.d/ndiswrapper


alias wlan0 ndiswrapper

/etc/resolv.conf

# generated by NetworkManager, do not edit!



nameserver 192.168.1.1



today i feel like giving up, tried everything =(

[wieman01]

today i feel like giving up, tried everything =(
Please do this and post the results:

sudo ifdown -v wlan0

sudo ifup -v wlan0
NetworkManager is still installed. That could be an issue. Do you have an WPA option in NetworkManager now after resorting to "ndiswrapper"?

[clegg13]

sorry, here are the results of ifup and if down too.


ifdown wlan0

RTNETLINK answers: No such process
There is already a pid file /var/run/dhclient.wlan0.pid with pid 6313
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:16:cf:95:b3:86
Sending on LPF/wlan0/00:16:cf:95:b3:86
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 192.168.1.1 port 67


ifdown -v wlan0

Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
RTNETLINK answers: No such process
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 9260
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:16:cf:95:b3:86
Sending on LPF/wlan0/00:16:cf:95:b3:86
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 192.168.1.1 port 67
ifconfig wlan0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan0.pid
Stopped /sbin/wpa_supplicant (pid 9211).


ifup -v wlan0


Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan0
wpa_supplicant: wpa-ap-scan 1 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "clegg" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise TKIP CCMP -- OK
wpa_supplicant: wpa-group TKIP CCMP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto WPA RSN -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:16:cf:95:b3:86
Sending on LPF/wlan0/00:16:cf:95:b3:86
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 1
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant

[wieman01]

@Clegg13:

This does not look right:

dhclient3 -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 134993416
It might relate to the fact that NetworkManager is still running. I cannot tell for sure unless you remove it from your system. Everything else looks just fine. Are you running Firestarter by chance?

[clegg13]

well how do i uninstall it ? ive already killed it with 'killall NetworkManager'

[clegg13]

oh and no, im not running firestarter or any other firewall.

[wieman01]

oh and no, im not running firestarter or any other firewall.
While you are restarting your network, no Ethernet connection exists? I.e. the cable is unplugged?

[clegg13]

yes i do the ifup and ifdown while network cable is removed.

[wieman01]

yes i do the ifup and ifdown while network cable is removed.
Jee, we are close. WPA seems no more to be the problem. It's something else, somehow DHCP is tripping us up. I need to think about it, at this moment I am running out of ideas. We ARE close though.

[clegg13]

also i cannot seem to get rid of that PID thing, any ideas ?

[clegg13]

Jee, we are close. WPA seems no more to be the problem. It's something else, somehow DHCP is tripping us up. I need to think about it, at this moment I am running out of ideas. We ARE close though.
thanks a lot for the help man, take your time =)

[wieman01]

also i cannot seem to get rid of that PID thing, any ideas ?
Delete it with 'sudo'? Not sure if that'll help.

sudo rm file...
If we are not making any progress, we could still resort to the forums. Let other contribute. I have seen this happen before.

[clegg13]

i was able to remove network manager completely. so now gonna resatrt and see maybe that PID isnt locked up anymore.

[clegg13]

no luck
this needs to be resolved now i guess ....


dhclient3 -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 134993416



i will look around in the forums. and remember this only happens when trying to connect securely. dhcp works fine w/o security or on eht0 for that matter.

[clegg13]

ok heres some more info, the same already a PID file thing comes up when i connect thourgh ethernet but it works. same happens when i connect to wireless without security, that connects too , although there are all 'OK' in the ifup -v output upt there, it still makes me think something to with security coz thats the only time it happens.

sigh, its been over a week and although i have learnt a lot, i still cant run my wireless securly on ubuntu =/

[wieman01]

ok heres some more info, the same already a PID file thing comes up when i connect thourgh ethernet but it works. same happens when i connect to wireless without security, that connects too , although there are all 'OK' in the ifup -v output upt there, it still makes me think something to with security coz thats the only time it happens.

sigh, its been over a week and although i have learnt a lot, i still cant run my wireless securly on ubuntu =/
Odd... What does this yield after you have restarted your network:

route
Can you ping your router at least?

[monomaniacpat]

Only now do I see your post. Must have missed it.

What happens when you restart the network after boot-up (wpa- and interface-section uncommented!):


Here we go. Did you intend me to restart networking through etc/init.d/networking?

Either way:


patrick@inspiron-8200:~$ sudo ifdown -v wlan0
ifdown: interface wlan0 not configured

patrick@inspiron-8200:~$ sudo ifup -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: ctrl_interface=/var/run/wpa_supplicant
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -C /var/run/wpa_supplicant -D wext
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan0
wpa_supplicant: wpa-ap-scan : OK
wpa_supplicant: configuring new network block "0"wpa_supplicant: wpa-ssid : OK
wpa_supplicant: wpa-psk : OK
wpa_supplicant: wpa-pairwise : OK
wpa_supplicant: wpa-group : OK
wpa_supplicant: wpa-key-mgmt : OK
wpa_supplicant: wpa-proto : OK
wpa_supplicant: enabling network 0 : OK

ifconfig wlan0 192.168.1.5 netmask 255.255.255.0 up
route add default gw 192.168.1.1 wlan0
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
Synchronizing clock to ntp.ubuntu.com...


patrick@inspiron-8200:~$ sudo ifdown -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/wpasupplicant
wpa_supplicant: ctrl_interface=/var/run/wpa_supplicant
route del default gw 192.168.1.1 wlan0
ifconfig wlan0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: ctrl_interface=/var/run/wpa_supplicant
wpa_supplicant: terminating wpa_supplicant daemon
Stopped wpa_supplicant (pid 5596).


patrick@inspiron-8200:~$ sudo ifup -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: ctrl_interface=/var/run/wpa_supplicant
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -C /var/run/wpa_supplicant -D wext
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan0
wpa_supplicant: wpa-ap-scan : OK
wpa_supplicant: configuring new network block "0"wpa_supplicant: wpa-ssid : OK
wpa_supplicant: wpa-psk : OK
wpa_supplicant: wpa-pairwise : OK
wpa_supplicant: wpa-group : OK
wpa_supplicant: wpa-key-mgmt : OK
wpa_supplicant: wpa-proto : OK
wpa_supplicant: enabling network 0 : OK

ifconfig wlan0 192.168.1.5 netmask 255.255.255.0 up
route add default gw 192.168.1.1 wlan0
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
Synchronizing clock to ntp.ubuntu.com...


Thanks for your continuing help - you're very persistent!

mono.

[wieman01]

Here we go. Did you intend me to restart networking through etc/init.d/networking?

Thanks for your continuing help - you're very persistent!

mono.
No problem. I enjoy it somehow. :-)

Now run do this from command line (I used to have the same problem):

sudo gedit /etc/network/if-up.d/ntpdate
Then comment all lines ("put a hash in from of every line - this stops it from working") so that it looks like this:

#!/bin/sh
# Adjust the system clock with ntp whenever a network interface is
# brought up, as it might mean we can contact the server.

#[ "$IFACE" != "lo" ] || exit 0
#
#test -f /usr/sbin/ntpdate || exit 0
#
#if [ -f /etc/default/ntpdate ]; then
# . /etc/default/ntpdate
# test -n "$NTPSERVERS" || exit 0
#else
# NTPSERVERS="ntp.ubuntu.com"
#fi
#
#if [ "$VERBOSITY" = 1 ]; then
# echo "Synchronizing clock to $NTPSERVERS..."
# /usr/sbin/ntpdate -b -s $NTPOPTIONS $NTPSERVERS || true
#else
# /usr/sbin/ntpdate -b -s $NTPOPTIONS $NTPSERVERS >/dev/null 2>&1 || true
#fi
Save the file & reboot the computer. Still the same problem?

[monomaniacpat]

Yep, fraid so. It got past setting up network interfaces, though. No sign of the link light on the card. I had to reboot twice, as one time it hung on "Starting hardware abstraction layer hald".

EDIT: One thing I thought I ought to mention is that no matter whether it's uncommented or commented, wlan0 is not set up when I enter "sudo /etc/init.d/networking restart". It's simply not mentioned. Could it be the bak file interfaces~ interfering, or what?

EDIT2: also, I don't have the dnsnameservers field in my interfaces file - just in case that makes any difference.

[wieman01]

@monomaniacpat:

The "BAK" file won't make any difference. But the DNS server could be an issue. Please add it to "interfaces".

Let's try this:

sudo depmod -a

sudo modprobe ndiswrapper

sudo ndiswrapper -m
Now restart the computer no matter what the output is.

[LeJediGris]

Thanks a lot for the very useful HOWTO !! it works fine...with the bug that force you to restart the net, i've to try with your comment.

So you can add the netgear WG511v2 (china) PCMCIA card to the list of the tested cards, chipset MArvel 88w8335 (Libertas)...WPA-PSK with TKIP (WPA1). Driver wext (ndiswrapper Netgear driver).

One more time thanks a lot from Paris...

[monomaniacpat]

OK, I'm going to restart my comp now.

here's the output, for the sake of completeness (it's all just accepted, essentially)


patrick@inspiron-8200:~$ sudo depmod -a
patrick@inspiron-8200:~$ sudo modprobe ndiswrapper
patrick@inspiron-8200:~$ sudo ndiswrapper -m
modprobe config already contains alias directive



Also, I assume the dns-nameserver is the same as my gateway?! That's what I put in interfaces.

EDIT: Hung up on boot again :'( - Isn't there some kind of diagnostic networking test we can run, so we can tell what's going on?

[wieman01]

OK, I'm going to restart my comp now.

here's the output, for the sake of completeness (it's all just accepted, essentially)


patrick@inspiron-8200:~$ sudo depmod -a
patrick@inspiron-8200:~$ sudo modprobe ndiswrapper
patrick@inspiron-8200:~$ sudo ndiswrapper -m
modprobe config already contains alias directive



Also, I assume the dns-nameserver is the same as my gateway?! That's what I put in interfaces.

EDIT: Hung up on boot again :'( - Isn't there some kind of diagnostic networking test we can run, so we can tell what's going on?
Yes, DNS should be same as the gateway.

You can check the boot log-files for details. There is some kind of weird hardware or driver issue. Could you check them ("/var/boot" or similar) and post the details?

[monomaniacpat]

Contents of /var/log/messages:


Jun 15 14:23:01 localhost kernel: [17180399.336000] pccard: CardBus card inserted into slot 0
Jun 15 14:23:01 localhost kernel: [17180399.384000] ndiswrapper: driver net8180 (Realtek,10/07/2004,5.173.1007.2004) loaded
Jun 15 14:23:01 localhost kernel: [17180399.384000] PCI: Enabling device 0000:03:00.0 (0000 -> 0003)
Jun 15 14:23:01 localhost kernel: [17180399.384000] ACPI: PCI Interrupt 0000:03:00.0[A] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
Jun 15 14:23:01 localhost kernel: [17180399.448000] ndiswrapper: using irq 11
Jun 15 14:23:07 localhost kernel: [17180405.328000] wlan0: vendor: 'Realtek RTL8180 Wireless LAN (Mini-)PCI NIC '
Jun 15 14:23:07 localhost kernel: [17180405.328000] wlan0: ndiswrapper ethernet device 00:0c:41:b2:10:21 using driver net8180, 10EC:8180.5.conf
Jun 15 14:23:07 localhost kernel: [17180405.328000] wlan0: encryption modes supported: WEP; TKIP with WPA; AES/CCMP with WPA
Jun 15 14:23:27 localhost gconfd (patrick-5012): Exiting
Jun 15 14:23:27 localhost gconfd (patrick-5668): starting (version 2.14.0), pid 5668 user 'patrick'
Jun 15 14:23:27 localhost gconfd (patrick-5668): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Jun 15 14:23:27 localhost gconfd (patrick-5668): Resolved address "xml:readwrite:/home/patrick/.gconf" to a writable configuration source at position 1
Jun 15 14:23:27 localhost gconfd (patrick-5668): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Jun 15 14:23:27 localhost gconfd (patrick-5668): Resolved address "xml:readonly:/var/lib/gconf/debian.defaults" to a read-only configuration source at position 3
Jun 15 14:23:27 localhost gconfd (patrick-5668): Resolved address "xml:readonly:/var/lib/gconf/defaults" to a read-only configuration source at position 4
Jun 15 14:23:29 localhost shutdown[4394]: shutting down for system reboot
Jun 15 14:23:34 localhost kernel: [17180433.088000] apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
Jun 15 14:23:34 localhost kernel: [17180433.088000] apm: disabled on user request.
Jun 15 14:23:35 localhost dhcdbd: Shut down.
Jun 15 14:23:36 localhost kernel: [17180434.172000] ip_tables: (C) 2000-2002 Netfilter core team
Jun 15 14:23:36 localhost kernel: [17180434.336000] Netfilter messages via NETLINK v0.30.
Jun 15 14:23:36 localhost kernel: [17180434.352000] ip_conntrack version 2.4 (8191 buckets, 65528 max) - 232 bytes per conntrack
Jun 15 14:23:43 localhost kernel: [17180441.980000] nfsd: last server has exited
Jun 15 14:23:43 localhost kernel: [17180441.980000] nfsd: unexporting all filesystems
Jun 15 14:23:43 localhost kernel: [17180441.980000] RPC: failed to contact portmap (errno -5).
Jun 15 14:23:44 localhost kernel: Kernel logging (proc) stopped.
Jun 15 14:23:44 localhost kernel: Kernel log daemon terminating.
Jun 15 14:23:44 localhost exiting on signal 15


That was the first time where it hung and I was forced to turn off the computer. I think it might be from just after I interrupted by removing and reinserting the card.

Here's the second attempt, where it made it past networking:



Jun 15 14:28:10 localhost kernel: [17179592.268000] ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11
Jun 15 14:28:10 localhost kernel: [17179592.704000] lp0: using parport0 (interrupt-driven).
Jun 15 14:28:10 localhost kernel: [17179592.744000] sbp2: $Rev: 1306 $ Ben Collins <bcollins@debian.org>
Jun 15 14:28:10 localhost kernel: [17179592.744000] ieee1394: sbp2: Driver forced to serialize I/O (serialize_io=1)
Jun 15 14:28:10 localhost kernel: [17179592.744000] ieee1394: sbp2: Try serialize_io=0 for better performance
Jun 15 14:28:10 localhost kernel: [17179592.840000] Adding 2048248k swap on /dev/hda2. Priority:-1 extents:1 across:2048248k
Jun 15 14:28:10 localhost kernel: [17179593.052000] EXT3 FS on hda1, internal journal
Jun 15 14:28:10 localhost kernel: [17179593.240000] md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
Jun 15 14:28:10 localhost kernel: [17179593.240000] md: bitmap version 4.39
Jun 15 14:28:10 localhost kernel: [17179593.416000] NET: Registered protocol family 17
Jun 15 14:28:10 localhost kernel: [17179593.824000] device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@redhat.com
Jun 15 14:28:10 localhost kernel: [17179594.520000] cdrom: open failed.
Jun 15 14:28:10 localhost kernel: [17179595.588000] Vendor: Model: USB DISK 2.0 Rev: PMAP
Jun 15 14:28:10 localhost kernel: [17179595.588000] Type: Direct-Access ANSI SCSI revision: 00
Jun 15 14:28:10 localhost kernel: [17179596.136000] Driver 'sd' needs updating - please use bus_type methods
Jun 15 14:28:10 localhost kernel: [17179596.720000] SCSI device sda: 2015232 512-byte hdwr sectors (1032 MB)
Jun 15 14:28:10 localhost kernel: [17179596.720000] sda: Write Protect is off
Jun 15 14:28:10 localhost kernel: [17179596.736000] SCSI device sda: 2015232 512-byte hdwr sectors (1032 MB)
Jun 15 14:28:10 localhost kernel: [17179596.740000] sda: Write Protect is off
Jun 15 14:28:10 localhost kernel: [17179596.740000] sda: sda1
Jun 15 14:28:10 localhost kernel: [17179596.748000] sd 0:0:0:0: Attached scsi removable disk sda
Jun 15 14:28:10 localhost kernel: [17179596.780000] sd 0:0:0:0: Attached scsi generic sg0 type 0
Jun 15 14:28:10 localhost kernel: [17179628.332000] pccard: card ejected from slot 0
Jun 15 14:28:10 localhost kernel: [17179652.952000] pccard: CardBus card inserted into slot 0
Jun 15 14:28:10 localhost kernel: [17179655.268000] eth0: Setting full-duplex based on MII #24 link partner capability of 05e1.
Jun 15 14:28:10 localhost kernel: [17179698.636000] ndiswrapper version 1.8 loaded (preempt=yes,smp=no)
Jun 15 14:28:10 localhost kernel: [17179698.744000] ndiswrapper: driver net8180 (Realtek,10/07/2004,5.173.1007.2004) loaded
Jun 15 14:28:10 localhost kernel: [17179698.744000] PCI: Enabling device 0000:03:00.0 (0000 -> 0003)
Jun 15 14:28:10 localhost kernel: [17179698.744000] ACPI: PCI Interrupt 0000:03:00.0[A] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
Jun 15 14:28:10 localhost kernel: [17179698.804000] ndiswrapper: using irq 11
Jun 15 14:28:10 localhost kernel: [17179704.676000] wlan0: vendor: 'Realtek RTL8180 Wireless LAN (Mini-)PCI NIC '
Jun 15 14:28:10 localhost kernel: [17179704.676000] wlan0: ndiswrapper ethernet device 00:0c:41:b2:10:21 using driver net8180, 10EC:8180.5.conf
Jun 15 14:28:10 localhost kernel: [17179704.676000] wlan0: encryption modes supported: WEP; TKIP with WPA; AES/CCMP with WPA
Jun 15 14:28:10 localhost kernel: [17179707.352000] ACPI: AC Adapter [AC] (on-line)
Jun 15 14:28:10 localhost kernel: [17179707.352000] ACPI: Battery Slot [BAT0] (battery absent)
Jun 15 14:28:10 localhost kernel: [17179707.468000] ACPI: Battery Slot [BAT1] (battery present)
Jun 15 14:28:10 localhost kernel: [17179707.584000] ACPI: Lid Switch [LID]
Jun 15 14:28:10 localhost kernel: [17179707.584000] ACPI: Power Button (CM) [PBTN]
Jun 15 14:28:10 localhost kernel: [17179707.584000] ACPI: Sleep Button (CM) [SBTN]
Jun 15 14:28:10 localhost kernel: [17179707.808000] pcc_acpi: loading...
Jun 15 14:28:10 localhost kernel: [17179707.956000] ACPI: Video Device [VID] (multi-head: yes rom: no post: no)
Jun 15 14:28:13 localhost dhcdbd: Started up.
Jun 15 14:28:15 localhost hpiod: 0.9.7 accepting connections at 56839...
Jun 15 14:28:16 localhost kernel: [17179714.884000] agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Jun 15 14:28:16 localhost kernel: [17179714.884000] agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode
Jun 15 14:28:16 localhost kernel: [17179714.884000] agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode
Jun 15 14:28:17 localhost kernel: [17179716.188000] ppdev: user-space parallel port driver
Jun 15 14:28:18 localhost kernel: [17179716.744000] apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
Jun 15 14:28:18 localhost kernel: [17179716.744000] apm: overridden by ACPI.
Jun 15 14:28:18 localhost kernel: [17179716.944000] ip_tables: (C) 2000-2002 Netfilter core team
Jun 15 14:28:18 localhost kernel: [17179717.032000] Netfilter messages via NETLINK v0.30.
Jun 15 14:28:18 localhost kernel: [17179717.048000] ip_conntrack version 2.4 (8191 buckets, 65528 max) - 232 bytes per conntrack
Jun 15 14:28:18 localhost kernel: [17179717.260000] video bus notify
Jun 15 14:28:20 localhost kernel: [17179718.804000] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Jun 15 14:28:20 localhost kernel: [17179719.012000] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
Jun 15 14:28:20 localhost kernel: [17179719.012000] NFSD: recovery directory /var/lib/nfs/v4recovery doesn't exist
Jun 15 14:28:20 localhost kernel: [17179719.012000] NFSD: starting 90-second grace period
Jun 15 14:28:23 localhost kernel: [17179721.272000] NET: Registered protocol family 10
Jun 15 14:28:23 localhost kernel: [17179721.272000] lo: Disabled Privacy Extensions
Jun 15 14:28:23 localhost kernel: [17179721.276000] IPv6 over IPv4 tunneling driver
Jun 15 14:28:25 localhost kernel: [17179723.804000] Bluetooth: Core ver 2.8
Jun 15 14:28:25 localhost kernel: [17179723.804000] NET: Registered protocol family 31
Jun 15 14:28:25 localhost kernel: [17179723.804000] Bluetooth: HCI device and connection manager initialized
Jun 15 14:28:25 localhost kernel: [17179723.804000] Bluetooth: HCI socket layer initialized
Jun 15 14:28:25 localhost kernel: [17179723.852000] Bluetooth: L2CAP ver 2.8
Jun 15 14:28:25 localhost kernel: [17179723.852000] Bluetooth: L2CAP socket layer initialized
Jun 15 14:28:25 localhost kernel: [17179723.860000] Bluetooth: RFCOMM socket layer initialized
Jun 15 14:28:25 localhost kernel: [17179723.860000] Bluetooth: RFCOMM TTY layer initialized
Jun 15 14:28:25 localhost kernel: [17179723.860000] Bluetooth: RFCOMM ver 1.7
Jun 15 14:28:25 localhost dhcpd: Internet Systems Consortium DHCP Server V3.0.3
Jun 15 14:28:25 localhost dhcpd: Copyright 2004-2005 Internet Systems Consortium.
Jun 15 14:28:25 localhost dhcpd: All rights reserved.
Jun 15 14:28:25 localhost dhcpd: For info, please visit http://www.isc.org/sw/dhcp/
Jun 15 14:28:25 localhost dhcpd: Internet Systems Consortium DHCP Server V3.0.3
Jun 15 14:28:25 localhost dhcpd: Copyright 2004-2005 Internet Systems Consortium.
Jun 15 14:28:25 localhost dhcpd: All rights reserved.
Jun 15 14:28:25 localhost dhcpd: For info, please visit http://www.isc.org/sw/dhcp/
Jun 15 14:28:25 localhost dhcpd: Wrote 0 leases to leases file.
Jun 15 14:28:25 localhost dhcpd:
Jun 15 14:28:31 localhost gconfd (patrick-5097): starting (version 2.14.0), pid 5097 user 'patrick'
Jun 15 14:28:31 localhost gconfd (patrick-5097): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Jun 15 14:28:31 localhost gconfd (patrick-5097): Resolved address "xml:readwrite:/home/patrick/.gconf" to a writable configuration source at position 1
Jun 15 14:28:31 localhost gconfd (patrick-5097): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Jun 15 14:28:31 localhost gconfd (patrick-5097): Resolved address "xml:readonly:/var/lib/gconf/debian.defaults" to a read-only configuration source at position 3
Jun 15 14:28:31 localhost gconfd (patrick-5097): Resolved address "xml:readonly:/var/lib/gconf/defaults" to a read-only configuration source at position 4
Jun 15 14:28:38 localhost gconfd (patrick-5097): Resolved address "xml:readwrite:/home/patrick/.gconf" to a writable configuration source at position 0
Jun 15 14:29:16 localhost gconfd (root-5283): starting (version 2.14.0), pid 5283 user 'root'
Jun 15 14:29:16 localhost gconfd (root-5283): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Jun 15 14:29:16 localhost gconfd (root-5283): Resolved address "xml:readwrite:/root/.gconf" to a writable configuration source at position 1
Jun 15 14:29:16 localhost gconfd (root-5283): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Jun 15 14:29:16 localhost gconfd (root-5283): Resolved address "xml:readonly:/var/lib/gconf/debian.defaults" to a read-only configuration source at position 3
Jun 15 14:29:16 localhost gconfd (root-5283): Resolved address "xml:readonly:/var/lib/gconf/defaults" to a read-only configuration source at position 4

[drew_2000]

Great thread, this helped me get WPA2 working on Dapper Drake using my Linksys WPC54G v 7.1.

Thanks again--I also had the problem where I had to restart /etc/init.d/networking after each reboot. Fixed now.

Drew

[wieman01]

Contents of /var/log/messages:
I really think this is a problem concerning your version of "ndiswrapper". The log files confirms that your card supports WPA and even WPA2.

Are you on Dapper? What version of "ndiswrapper" are you currently running?

[monomaniacpat]

Yes, it's the one from the Dapper repositories. According to synaptic, it is ndiswrapper-utils version 1.8-0ubuntu2

However, this doesn't comply with the version numbers on the ndiswrapper website, which is now 1.47

There's no option listed in the manual, so I don't know how to find out the equivalent number.

[wieman01]

Yes, it's the one from the Dapper repositories. According to synaptic, it is ndiswrapper-utils version 1.8-0ubuntu2

However, this doesn't comply with the version numbers on the ndiswrapper website, which is now 1.47

There's no option listed in the manual, so I don't know how to find out the equivalent number.
I had a similar issue on Dapper until I upgraded to the latest version of "ndiswrapper". I can't promise it will help in your case, but I used to face random freezes as well and an upgrade did the job for me. I know it's tough as we are close but compiling from source isn't rocket science. Want to try? Then just open another thread and send me the link by PM. :-) We are getting there.

[monomaniacpat]

If you remember, I tried to install from source initially, and got an error. I've just tried again, using a fresh download, having read the INSTALL file and get the same error as before.

I've started a thread:

http://ubuntuforums.org/showthread.php?p=2861206

[wieman01]

If you remember, I tried to install from source initially, and got an error. I've just tried again, using a fresh download, having read the INSTALL file and get the same error as before.

I've started a thread:

http://ubuntuforums.org/showthread.php?p=2861206
Yes, I remember. But I guess that's the only option that is left now... Hate to say it though.

[clegg13]

route gives this

Destination Gateway Genmask Flags Metric Ref Use Iface
172.16.38.0 * 255.255.255.0 U 0 0 0 vmnet1
172.16.187.0 * 255.255.255.0 U 0 0 0 vmnet8
link-local * 255.255.0.0 U 0 0 0 wlan0
default * 0.0.0.0 U 1000 0 0 wlan0



needless to say, it foesnt ping the router.

[wieman01]

route gives this

needless to say, it foesnt ping the router.
Quick question... do you know what "vmnet1" and "vmnet8" is?

[clegg13]

not exactly, but i think they are for vmware since they started appearing only two days ago after i installed vmware. prolly for using the network through a windows vm or vm'ed windows apps.

[wieman01]

not exactly, but i think they are for vmware since they started appearing only two days ago after i installed vmware. prolly for using the network through a windows vm or vm'ed windows apps.
Alright, virtual Ethernet connections I assume. I have sent you a PM.

[monomaniacpat]

Mine appears to be all working now. Had a bit of a wobble a minute ago, but it seems it was the router and not my box.

So I can confirm the Linksys WPC11 v.4 or RT8180L realtek chipset works with the latest windows drivers from the realtek website (http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=5&PFid=5&Level=6&Conn=5&DownTypeID=3&GetDown=false&Downloads=true#RTL8180L) with ndiswrapper 1.47 on WPA1.

I'd be happy to add any other info required.

[mahasmb]

OMG THIS WORKED!! IT REALLY WORKED!

Thank you.

Thank you.

Thank you!

I've had so much trouble with wireless.

At first when I was with Dapper Drake it was months before I could configure wireless to work with my Broadcam 4318 Wireless Card. After I finally got that working, I decided to upgrade to Feisty. Wireless worked for a while, but then stopped all of a sudden. I was one of those many people who could even see all the networks being broadcasted but just couldn't connect. It was always at 0%. So I tried downgrading Network Manager as suggested with others. That still didn't work. Then I tried this How to for WPA1, and that still didn't work. (I'm pretty sure I'm using WPA1. As far as I know though my router allows me to set it to WPA-PSK with the TKIP option. Maybe I'm wrong, I don't know). Finally, I tried the "Sample configuration mixed mode (WPA1, WPA2) & DHCP, ESSID broadcast" and IT'S WORKING! I'm on it right now.

Seriously, much thanks. I hope I have no more problems after this.

Just one question though. I'm on a laptop and I often take it with me to my university (with no security other than having to login in to my school account through a browser with a user name and password), how would I set it to connect to that when I need to?

[wieman01]

Just one question though. I'm on a laptop and I often take it with me to my university (with no security other than having to login in to my school account through a browser with a user name and password), how would I set it to connect to that when I need to?
You won't be able to switch using this method... :-(

What wireless adapter have you got if I may ask?

[weinju]

Hi, thank you for this great HowTo.
I was successful in setting up my home wifi with WEP2 instructions from this post.

However, my college LEAP network does not want to "surrender" to your configuration instructions.
I know all details necessary for connection (network SSID, username/password), but still can't get in.
Please help! I hate switching to Windows just to check my college e-mail.... :(

Thanks in advance.

[wieman01]

Hi, thank you for this great HowTo.
I was successful in setting up my home wifi with WEP2 instructions from this post.

However, my college LEAP network does not want to "surrender" to your configuration instructions.
I know all details necessary for connection (network SSID, username/password), but still can't get in.
Please help! I hate switching to Windows just to check my college e-mail.... :(

Thanks in advance.
Could you post your script please? Would be a good start...

[weinju]

Here you go:

auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp

auto eth2
iface eth2 inet dhcp

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid wmclleap
wpa-ap-scan 1
wpa-eap LEAP
wpa-key-mgmt IEEE8021X
wpa-identity my.login
wpa-password my_password

[wieman01]

Here you go:

auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp

auto eth2
iface eth2 inet dhcp

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid wmclleap
wpa-ap-scan 1
wpa-eap LEAP
wpa-key-mgmt IEEE8021X
wpa-identity my.login
wpa-password my_password
Not surprisingly that looks ok. I am not sure if your driver really supports PEAP, I cannot tell from here. Nevertheless, please also post the output of these while you are close to the network>

sudo iwlist scan

sudo ifdown -v wlan0

sudo ifup -v wlan0

[Master200]

route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
0.0.0.0 0.0.0.0 0.0.0.0 U 1000 0 0 eth0

iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

eth1 IEEE 802.11g ESSID:off/any Nickname:"Rugv?nget27"
Mode:Managed Frequency:2.462 GHz Access Point: Not-Associated
Bit Rate=54 Mb/s Tx-Power:32 dBm
RTS thr=2347 B Fragment thr=2346 B
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

The ? is supposed to be æ, which is a dansih letter.

ifconfig
eth0 Link encap:Ethernet HWaddr 00:C0:9F:B4:BC:AD
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:16 Base address:0x1800

eth1 Link encap:Ethernet HWaddr 00:14:A4:1A:F5:CF
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:22 Memory:e2000000-e2002000

eth0: avah Link encap:Ethernet HWaddr 00:C0:9F:B4:BC:AD
inet addr:169.254.10.108 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Interrupt:16 Base address:0x1800

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
X packets:14 errors:0 dropped:0 overruns:0 frame:0
TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1120 (1.0 KiB) TX bytes:1120 (1.0 KiB)

iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:14:6C:D2:54:96
ESSID:"Rugv�nget27"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:50/100 Signal level:-64 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates: 1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 02 - Address: 00:18:4D:4F:1D:BC
ESSID:"rug56"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:14/100 Signal level:-87 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates: 1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 03 - Address: 00:15:F2:B2:94:D9
ESSID:"hertzberg"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.432 GHz (Channel 5)
Quality:7/100 Signal level:-91 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates: 1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0

The other networks (cell 02 and 03), show up when I left click the network icon at the clock, but mine (cell 01) does not.

cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp

auto eth2
iface eth2 inet dhcp

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp
address 192.168.1.4
gateway 192.168.1.1
dns-nameservers 192.168.1.1
netmask 255.255.255.0
wpa-driver wext
wpa-ssid Rugvænget27
wpa-ap-scan 2
wpa-pronto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk *******

******* is my network passphrase in the right way, not converted using: wpa_passphrase 'Rugvænget27' 'your_ascii_key'

cat /etc/modprobe.d/ndiswrapper
alias wlan0 ndiswrapper

cat /etc/resolv.conf
# generated by NetworkManager, do not edit!



nameserver 192.168.1.1


I have read somewhere in the posts that it is not smart to have Network Manager and Wifi-radar, installed. I have. The only thing that confuses me is that the network stuff by the clock does not register my network, but Wifi-radar does (although it requires a driver, I have tried wext, but it doesn't work)

[wieman01]

@Master200:

Watch out, there is a typo:

auto wlan0
iface wlan0 inet static
address 192.168.1.4
gateway 192.168.1.1
dns-nameservers 192.168.1.1
netmask 255.255.255.0
wpa-driver wext
wpa-ssid Rugvænget27
wpa-ap-scan 2
wpa-pronto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk *******
And remove any special characters for the time being. They might confuse the system.

[Master200]

Thanks, it worked

[mahasmb]

You won't be able to switch using this method... :-(

What wireless adapter have you got if I may ask?

One of those lovely BCM4318 wireless cards.

[Julolidine]

I have a problem with my wireless. Every once in a while it won't work - I'll be connected for a while and then it would drop never to return, even doing ifdown/ifup and /etc/init.d/networking restart. Only a hard restart would get it going like 50% of the time.

Anyways, I tried restarting wireless through init.d, and I get the same message about there being already a pid for wlan0.

Remarkably if I do


sudo ifdown wlan0
sudo rm /var/run/dhclient.wlan0.pid
sudo ifup wlan0

Everything works. I do not have networkmanager installed, and this seems to solve my problems.

[bluezio]

Thanks! I finally got my IPN2220 working thanks to this guide.

[wieman01]

I have a problem with my wireless. Every once in a while it won't work - I'll be connected for a while and then it would drop never to return, even doing ifdown/ifup and /etc/init.d/networking restart. Only a hard restart would get it going like 50% of the time.

Anyways, I tried restarting wireless through init.d, and I get the same message about there being already a pid for wlan0.

Remarkably if I do


sudo ifdown wlan0
sudo rm /var/run/dhclient.wlan0.pid
sudo ifup wlan0

Everything works. I do not have networkmanager installed, and this seems to solve my problems.
It's a problem with the physical network settings. You should adjust a few settings and see if it gets any better. What router have you got?

[bluezio]

I forgot mentioning the configuration I was using.

Device: IPN2220 (in particular, it's from an Acer Travelmate 2700)
Driver: neti2220 under ndiswrapper (last one from Inprocomm, not the Acer one: http://www.laptopvideo2go.com/forum/index.php?showtopic=7172)

wpa-driver: wext

Works fine with WPA1 and TKIP. Neither WPA2 nor CCMP seem to work. DHCP should work, but I suspect that's my router's fault, and not the card's.

[mahasmb]

What's my alternative if I can't switch networks if I'm moving around with a laptop?

I'm using a BCM 4318 Wireless card on my laptop.

[Julolidine]

It's a problem with the physical network settings. You should adjust a few settings and see if it gets any better. What router have you got?

I have a SpeedTouch 716 WL. When you say physical network settings, you mean with the router itself?

I have another computer running Sabayon, and I never have the same problem with that computer on that same router.

[wieman01]

What's my alternative if I can't switch networks if I'm moving around with a laptop?

I'm using a BCM 4318 Wireless card on my laptop.
Using a "wpa_supplicant.conf" file. There are HOWTO in the forums. That should do for you since you can add as many networks as you want.

[wieman01]

I have a SpeedTouch 716 WL. When you say physical network settings, you mean with the router itself?

I have another computer running Sabayon, and I never have the same problem with that computer on that same router.
Yes, the router. It has certain network settings you can change. Give it a go.

[scholzilla]

I'm a total newbie, and I'm stuck at the beginning of this thread. I can get WEP to work fine using my RTL8187 wireless card on ubuntu 7.04, and I've followed the routine posted at https://help.ubuntu.com/community/WifiDocs/WPAHowTo
but when I follow your commands I get the following output:

laptop:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 IEEE 802.11g Frequency:2.412 GHz
RTS thr:off Fragment thr=2346 B

wlan0 IEEE 802.11g ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
RTS thr:off Fragment thr=2346 B
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

laptop:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wmaster0 Failed to read scan data : Operation not supported

wlan0 No scan results


I don't even know where to begin with this. Your patience is greatly appreciated.

Matt

[Clockware]

Using a "wpa_supplicant.conf" file. There are HOWTO in the forums. That should do for you since you can add as many networks as you want.

So, if I need more networks to be managed by wpa_supplicant.conf the configuration in network/interfaces must be removed?

Just another thing, the workaround script for the "networking restart" is useful also in Feisty?

Thanks,
Clock

[wieman01]

I'm a total newbie, and I'm stuck at the beginning of this thread. I can get WEP to work fine using my RTL8187 wireless card on ubuntu 7.04, and I've followed the routine posted at https://help.ubuntu.com/community/WifiDocs/WPAHowTo
but when I follow your commands I get the following output:

laptop:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 IEEE 802.11g Frequency:2.412 GHz
RTS thr:off Fragment thr=2346 B

wlan0 IEEE 802.11g ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
RTS thr:off Fragment thr=2346 B
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

laptop:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wmaster0 Failed to read scan data : Operation not supported

wlan0 No scan results


I don't even know where to begin with this. Your patience is greatly appreciated.

Matt
You card isn't working so you need to fix that first. What kind of card (model, chipset) have you got and what tutorials have you followed?

[wieman01]

So, if I need more networks to be managed by wpa_supplicant.conf the configuration in network/interfaces must be removed?

Just another thing, the workaround script for the "networking restart" is useful also in Feisty?

Thanks,
Clock
Yes, that configuration in "/etc/network/interfaces" must be removed.

The workaround script described in post #2 should also work in Feisty... Have not tried it yet though.

[ORF1000]

I have an RTL8087 built into a Gateway laptop. I can get WEP to work OK without needing ndiswrapper. But I couldn't get the WPA-PSK to work with the modified networks file from the tutorial. What driver should I be using? Is wext the right one?

Thanks.

[ORF1000]

Good grief. That's an RTL8187 and my interfaces file.

Sorry.

[weinju]

@wieman01


Not surprisingly that looks ok. I am not sure if your driver really supports PEAP, I cannot tell from here. Nevertheless, please also post the output of these while you are close to the network>

Here's the output of the commands:

Sudo iwlist scan

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:0D:BD:DA:B1:76
ESSID:"<hidden>"
Protocol:IEEE 802.11b
Mode:Master
Channel:6
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Quality=59/100 Signal level=-72 dBm Noise level=-72 dBm
Extra: Last beacon: 1168ms ago
(further, gives a list of all Cells found)

sudo ifdown -v wlan0

ifdown: interface wlan0 not configured

sudo ifup -v wlan0

Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
wlan0: ERROR while getting interface flags: No such device
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
ioctl[SIOCSIWPMKSA]: No such device
ioctl[SIOCSIWMODE]: No such device
Could not configure driver to use managed mode
ioctl[SIOCGIFFLAGS]: No such device
Could not set interface 'wlan0' UP
ioctl[SIOCGIWRANGE]: No such device
ioctl[SIOCGIFINDEX]: No such device
Segmentation fault (core dumped)
wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1

dhclient3 -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

SIOCSIFADDR: No such device
wlan0: ERROR while getting interface flags: No such device
wlan0: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up wlan0.

Thanks for checking into this.

[wieman01]

I have an RTL8087 built into a Gateway laptop. I can get WEP to work OK without needing ndiswrapper. But I couldn't get the WPA-PSK to work with the modified networks file from the tutorial. What driver should I be using? Is wext the right one?

Thanks.
"ndiswrapper" requires "wext". But check the change log of the Windows driver... the current version might not support WPA. Try to get hold of the last version.

[wieman01]

Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
wlan0: ERROR while getting interface flags: No such device
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
ioctl[SIOCSIWPMKSA]: No such device
ioctl[SIOCSIWMODE]: No such device
Could not configure driver to use managed mode
ioctl[SIOCGIFFLAGS]: No such device
Could not set interface 'wlan0' UP
ioctl[SIOCGIWRANGE]: No such device
ioctl[SIOCGIFINDEX]: No such device
Segmentation fault (core dumped)
wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1
Ah... that looks pretty bad indeed. Are you sure that driver supports PEAP at all? The vendor's website should shed some light on this... Replacing the current driver with the latest version could help.

[Clockware]

Yes, that configuration in "/etc/network/interfaces" must be removed.

The workaround script described in post #2 should also work in Feisty... Have not tried it yet though.

It's run! The script works as well as other releases! :)

If we move the script from the init sequence to if-pre-up (or something similar) it could work like now?

Thanks,
Valerio

[fmbugdadi]

Wow, I followed the instructions, and this, totally worked for me. My wireless connection stays connected permanently now. thanks a million...

Now, can you explain to me, how to keep from entering my keyring password every time the machine boots up or restarts? thanks again.

Martin

[wieman01]

It's run! The script works as well as other releases! :)

If we move the script from the init sequence to if-pre-up (or something similar) it could work like now?

Thanks,
Valerio
Not sure, mate. Why don't you test it and drop us a message if it works? :-)

[wieman01]

Wow, I followed the instructions, and this, totally worked for me. My wireless connection stays connected permanently now. thanks a million...

Now, can you explain to me, how to keep from entering my keyring password every time the machine boots up or restarts? thanks again.

Martin
Keyring password? Network Manager? Not sure how I can help you there.

[ORF1000]

"ndiswrapper" requires "wext". But check the change log of the Windows driver... the current version might not support WPA. Try to get hold of the last version.

I guess my real question is -- since my RTL8187 works OK with the native driver and WEP, do I really need to go to ndiswrapper to use WPA with WEXT? Or is there another driver I can call without going to ndiswrapper?

Thanks.

[ORF1000]

I guess my real question is -- since my RTL8187 works OK with the native driver and WEP, do I really need to go to ndiswrapper to use WPA with WEXT? Or is there another driver I can call without going to ndiswrapper?


So maybe I should be calling rtl8187 since there's an rtl8187.ko module. But I'm still not having luck.

The wireless section of my interfaces file looks like this:

auto wlan0
iface wlan0 inet static
address 192.168.1.33
gateway 192.168.1.1
dns-nameservers 204.118.6.14
netmask 255.255.255.0
wpa-driver rtl8187
wpa-ssid FIDONET
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk 851ea92e4 etc.

When I restart networking I get this:

wmaster0: unknown hardware address type 801
SIOCSIFADDR: No such device
ath0: ERROR while getting interface flags: No such device
ath0: ERROR while getting interface flags: No such device
wmaster0: unknown hardware address type 801
Bind socket to interface: No such device
Failed to bring up ath0.
Unsupported driver 'rtl8187'.

wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1
[ OK ]

I think it's laughing at me with that last [OK].

And where did ath0 come from?

Thanks for any help on this.

[wieman01]

So maybe I should be calling rtl8187 since there's an rtl8187.ko module. But I'm still not having luck.

The wireless section of my interfaces file looks like this:

auto wlan0
iface wlan0 inet static
address 192.168.1.33
gateway 192.168.1.1
dns-nameservers 204.118.6.14
netmask 255.255.255.0
wpa-driver rtl8187
wpa-ssid FIDONET
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk 851ea92e4 etc.

When I restart networking I get this:

wmaster0: unknown hardware address type 801
SIOCSIFADDR: No such device
ath0: ERROR while getting interface flags: No such device
ath0: ERROR while getting interface flags: No such device
wmaster0: unknown hardware address type 801
Bind socket to interface: No such device
Failed to bring up ath0.
Unsupported driver 'rtl8187'.

wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1
[ OK ]

I think it's laughing at me with that last [OK].

And where did ath0 come from?

Thanks for any help on this.
Could you try this driver instead?

wpa-driver wext

[ORF1000]

Could you try this driver instead?

Yes, but I don't get any better results. Is wext specific to ndiswrapper? I'm not using ndiswrapper because the native driver works OK with WEP. But I want to use WPA.

WPA-PSK worked first time on my suse laptop, using an easy graphical interface. But that was with ndiswrapper.

Here's what I get with wext:

wmaster0: unknown hardware address type 801
SIOCSIFADDR: No such device
ath0: ERROR while getting interface flags: No such device
ath0: ERROR while getting interface flags: No such device
wmaster0: unknown hardware address type 801
Bind socket to interface: No such device
Failed to bring up ath0.
ioctl[SIOCSIWMODE]: Device or resource busy
Could not configure driver to use managed mode
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - [ OK ]

[Zoufiax]

Hello,

Same question to you... does the current driver support WPA? Please check the vendor's website to get some info on the driver version, etc. Some drivers do support WPA, some don't. The latest version for your adapter might fix it.

"iface eth0 inet static" is correct if you want to use a static IP. Apart from this your set-up looks just fine.
Hello,

Sorry for not responding for such a long time. I'm using a Windows driver in conjunction with ndiswrapper. When using the driver on the Windows platform I was able to use WPA. So I guess the driver is good for Windows at least. Some time ago an ex collegue told me that it might be ndiswrapper which does not support WPA when using this specific Windows driver under Ubuntu, and that in the next version of Ubuntu the support for WPA will be better. So for the time being I just stick to WEP, which works just fine, and then I'll give it another try when the next version of Ubuntu is being released. Maybe a native Linux driver will be released for my SpeedTouch 121g. Thanks for your help anyway.

[tedrogers]

Hi Wieman,

Wondering if you know what's going on here...since I upgraded from Edgy to Fesity I have to restart my wireless network manually after booting into X.

During the boot I can see that the wireless card is trying to bind to my router using DHCP (the script is running)..FYI it looks like an fsck check and changes to verbose mode during boot.

Sometimes if succeeds and most of the time it fails....so that when I eventually log in I have to manually run /etc/init.d/networking restart in order to get it to connect and bind to my router properly using DHCP.

Any ideas why this is happening and how can I sort it out...it's becoming a pain in the butt now.

Cheers, and wow, what a thread you have sir! ;)

[Clockware]

Not sure, mate. Why don't you test it and drop us a message if it works? :-)

Good idea...

However testing the normal configuration (the one suggested in this thread, in case of WPA-protected wlan with static ip) I found out a problem...

When Ubuntu starts and the AP is ON all works fine, instead, when it starts and the AP is OFF or out of range the Gnome startup is blocked...

That's amazing for a laptop, how can I fix?

Clock

[LazyBoy]

Stumped.
Feisty on a T61 with Thinkpad (Atheros) a/b/g/n card.
ifconfig and iwconfig look OK to me, but I can't ping anything, even my local gateway.

THANKS,
LB


lb@ubuntu:~$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.12.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 wlan0
0.0.0.0 192.168.12.13 0.0.0.0 UG 0 0 0 wlan0
lb@ubuntu:~$ iwconfig
lo no wireless extensions.

wlan0 IEEE 802.11g ESSID:"secured2"
Mode:Managed Frequency:2.462 GHz Access Point: 00:16:B6:19:B2:CD
Bit Rate=54 Mb/s
Power Management:off
Link Quality:78/100 Signal level:-46 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

eth0 no wireless extensions.

lb@ubuntu:~$ ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:200 errors:0 dropped:0 overruns:0 frame:0
TX packets:200 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:19945 (19.4 KiB) TX bytes:19945 (19.4 KiB)

wlan0 Link encap:Ethernet HWaddr 00:19:7E:91:0B:2B
inet addr:192.168.12.92 Bcast:192.168.12.255 Mask:255.255.255.0
inet6 addr: fe80::219:7eff:fe91:b2b/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:218 errors:0 dropped:0 overruns:0 frame:0
TX packets:362 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:24634 (24.0 KiB) TX bytes:43579 (42.5 KiB)
Interrupt:21 Memory:df3f0000-df400000

lb@ubuntu:~$ iwlist scan
lo Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:16:B6:19:B2:CD
ESSID:"secured2"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:79/100 Signal level:-45 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK

eth0 Interface doesn't support scanning.

lb@ubuntu:~$
lb@ubuntu:~$
lb@ubuntu:~$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0


iface eth0 inet dhcp


auto wlan0
# iface wlan0 inet dhcp
iface wlan0 inet static
wpa-driver wext
wpa-ssid secured2
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk acd8c3f5d4759cd4c7102cb21622b3e1bb0e3443ce91c3def2 de4bd05e951061
address 192.168.12.92
netmask 255.255.255.0
gateway 192.168.12.13
dns-nameservers 167.206.245.8
# nameserver 167.206.245.7
# nameserver 167.206.245

lb@ubuntu:~$
lb@ubuntu:~$ cat /etc/modprobe.d/ndiswrapper
alias wlan0 ndiswrapper
lb@ubuntu:~$ cat /etc/resolv.conf
nameserver 167.206.245.8
nameserver 167.206.245.7
nameserver 167.206.245.72

[houms]

I recently installed Fiest fawn (7.04) on a inspiron 8600, which is has an internal intel 2100 b card....From a fresh install the following is the only steps I followed after installation to get the wireless working. From what i understand, and please correct me if I'm wrong, if your going to use wpa encryption whether its version 1 or 2, you must configure /etc/wpa_supplicant.conf. In my setup the ipw2100 linux driver does not support wpa encryption natively.. Instead it uses the wpa_supplicant as a back-end to achieve wpa1/2 encryption abilities. I have yet to modify the /etc/network/interfaces, which i say only to point out that it was not necessary to get wireless working... I began with my ssid broadcasting and when I got that working, I turned broadcasting off on the router and its still connecting.. So please if you follow this START with the ssid broadcasting on the router, if ya need help let me know, but you can get it working I think with whatever card you have, as long as it recognizes your card... A quick way is to iwconfig and see the output... the driver is listed
Here goes
first edit /etc/wpa_supplicant.conf, here is how mine looks..
__________________________________________________ _____________________________________________
# WPA 2
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1

network={
ssid="yournetworkname"(leave the quotes)
scan_ssid=1
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP
group=CCMP
psk=yourhexkey
}
__________________________________________________ ___________________________________
If any of it doesn't make sense let me know
save this file
then
$ sudo ifconfig eth1 down (If replace eth1 with your interface if different)
$ sudo killall dhclient
$ sudo ifconfig eth1 up 0.0.0.0(same as above about eth1)
then
$sudo wpa_supplicant -Dipw -ieth1 -dd -c/etc/wpa_supplicant.conf
but here I got an error, however I went into Network Manager and choose the "Connect to Other Wireless Network", choose the appropriate settings for your setup and it should start
trying to connect.. Now as funny as this sounds, I suggest you minimize all your windows... You will know when the connection is working because the Keyring manager pops up and asks to enter a default password, this is assuming that you have not setup Keyring manager. The Keyring manager sometimes will not appear if you have other windows active. Now this is not a problem at login but disabling networkmanager and re-enabling it can be problematic.

...If the first attempt at connecting fails, look in NetworkManager and see if you see your network listed, try and connect again that way. The wireless seems kinda flaky, but its really at least from my experience to tell if it can get better.. Now in terms of performance its excellent even for a b card, the connection is always good, but getting connected is tricky. Now every time I log in I get the Keyring Manager askin' me for a password, once you put it in your set, if your a user who doesnt like restarting their machine just hit ctrl+alt+backspace and log back in..

The best advice in this whole post is: skim through the examples (they should be in /usr/share/doc/wpasupplicant/examples/wpa_supplicant.conf.gz, that path might vary). I wasted hours on google before resorting to reading that file, and it’s probably all you’ll need. I hope this helps.. If anyone has any questions I'm here to help and learn.

[rmontyq]

Just a short note that this posting is awesome and should be a friggin' sticky in GOOGLE.

Thanks for the HowTo!!!

rq

[max_croft]

After 3 days of tweaking, I'm now able to ping other computers on the network!! Woooo!!! -- Unfortunately, I've hit the wall again as I can't get outside to access the net. :(

I've got a feeling it has something to do with the 'network' and 'broadcast' options that i've seen in other people's /etc/network/interfaces , but I don't have them in mine as I'm not entirely sure on how they should be set or if I even need them.

Here is my current /etc/network/interfaces :

auto eth1
iface eth1 inet static
address 192.168.0.4
gateway 192.168.0.200
dns-nameservers 192.168.0.200
netmask 255.255.255.0
wpa-driver wext
wpa-ssid SoapyAir
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk <a lot of numbers and letters>

Just a little confused as to why I can't access the net as it appears everything is correct. Hope someone can help me soon as I feel I'm soooo close to having this wireless saga over and done with!!

[houms]

what does your wpa_supplicant file look like?

[John Wiersba]

I had WEP working with Network Manager in feisty. Then I tried many different how-to's in an attempt to get WPA working and I ended up unable to get anything working, including WEP. But your instructions worked for me and I am very thankful to have wireless back working again!

Linux wireless will have to get easier for Mom&Pop to use it (I spent about 10 hours today), especially when it works out of the box in WinXP. But I'm glad progress is being made. Maybe Network Manager will be able to handle WPA in gutsy.

[max_croft]

what does your wpa_supplicant file look like?

I don't think I have one. /etc/wpa_supplicant.conf doesn't exist and inside /etc/wpa_supplicant/ are only two files, functions.sh and ifupdown.sh

[LazyBoy]

It seems I was wrong about the iwconfig being OK. Every few seconds It bounces between associated and non-associated. Here's the output from iwevent.

$ iwevent
Waiting for Wireless Events from interfaces...
23:21:37.855045 wlan0 New Access Point/Cell address:Not-Associated
23:21:40.890315 wlan0 Set Mode:Managed
23:21:40.890354 wlan0 Set Frequency:2.462 GHz (Channel 11)
23:21:40.890456 wlan0 Set ESSID:"secured2"
23:21:40.897215 wlan0 Association Request IEs:00087365637572656432010802040B162430486C32040C 121860DD160050F20101000050F20201000050F20201000050 F202
23:21:40.897698 wlan0 Association Response IEs:010882848B962430486C32040C121860DD060010180201 04
23:21:40.897922 wlan0 New Access Point/Cell address:00:16:B6:19:B2:CD
23:21:50.913241 wlan0 New Access Point/Cell address:Not-Associated
23:21:53.961575 wlan0 Set Mode:Managed
23:21:53.961613 wlan0 Set Frequency:2.462 GHz (Channel 11)
23:21:53.962329 wlan0 Set ESSID:"secured2"
23:21:53.973444 wlan0 Association Request IEs:00087365637572656432010802040B162430486C32040C 121860DD160050F20101000050F20201000050F20201000050 F202
23:21:53.973519 wlan0 Association Response IEs:010882848B962430486C32040C121860DD060010180201 04
23:21:53.973548 wlan0 New Access Point/Cell address:00:16:B6:19:B2:CD
23:22:03.986706 wlan0 New Access Point/Cell address:Not-Associated
23:22:07.030501 wlan0 Set Mode:Managed
...


Any ideas?
LB



Stumped.
Feisty on a T61 with Thinkpad (Atheros) a/b/g/n card.
ifconfig and iwconfig look OK to me, but I can't ping anything, even my local gateway.

THANKS,
LB


lb@ubuntu:~$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.12.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 wlan0
0.0.0.0 192.168.12.13 0.0.0.0 UG 0 0 0 wlan0
lb@ubuntu:~$ iwconfig
lo no wireless extensions.

wlan0 IEEE 802.11g ESSID:"secured2"
Mode:Managed Frequency:2.462 GHz Access Point: 00:16:B6:19:B2:CD
Bit Rate=54 Mb/s
Power Management:off
Link Quality:78/100 Signal level:-46 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

eth0 no wireless extensions.

lb@ubuntu:~$ ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:200 errors:0 dropped:0 overruns:0 frame:0
TX packets:200 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:19945 (19.4 KiB) TX bytes:19945 (19.4 KiB)

wlan0 Link encap:Ethernet HWaddr 00:19:7E:91:0B:2B
inet addr:192.168.12.92 Bcast:192.168.12.255 Mask:255.255.255.0
inet6 addr: fe80::219:7eff:fe91:b2b/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:218 errors:0 dropped:0 overruns:0 frame:0
TX packets:362 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:24634 (24.0 KiB) TX bytes:43579 (42.5 KiB)
Interrupt:21 Memory:df3f0000-df400000

lb@ubuntu:~$ iwlist scan
lo Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:16:B6:19:B2:CD
ESSID:"secured2"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:79/100 Signal level:-45 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK

eth0 Interface doesn't support scanning.

lb@ubuntu:~$
lb@ubuntu:~$
lb@ubuntu:~$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0


iface eth0 inet dhcp


auto wlan0
# iface wlan0 inet dhcp
iface wlan0 inet static
wpa-driver wext
wpa-ssid secured2
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk acd8c3f5d4759cd4c7102cb21622b3e1bb0e3443ce91c3def2 de4bd05e951061
address 192.168.12.92
netmask 255.255.255.0
gateway 192.168.12.13
dns-nameservers 167.206.245.8
# nameserver 167.206.245.7
# nameserver 167.206.245

lb@ubuntu:~$
lb@ubuntu:~$ cat /etc/modprobe.d/ndiswrapper
alias wlan0 ndiswrapper
lb@ubuntu:~$ cat /etc/resolv.conf
nameserver 167.206.245.8
nameserver 167.206.245.7
nameserver 167.206.245.72

[sc00ter]

Hi, I've had similar problems with the Realtek RT8187 driver and getting WPA-PSK working.

I've found by moving the ESSID after the PSK-KEY did the trick, here's a copy of my /etc/network/interfaces for reference:



auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto wlan0
iface wlan0 inet dhcp
pre-up ifconfig wlan0 up
pre-up ifconfig wlan0 down
pre-up ifconfig wlan0 up
pre-up ifconfig wlan0 down
wpa-driver wext
wpa-ap-scan 1
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <hex pass key - no quotes>
wpa-ssid <your ssid goes here - no quotes>
pre-up ifconfig wlan0 up

[alexz1011]

Hi,

I just switched from Windows XP to Kubuntu 6.06 2 weeks ago. I have been having trouble in setting up my wireless since then. I am using WPA1, TKIP, and hidden ssid. I have followed the steps exactly described in the first post of this thread and several follow up posts, but still no luck. I am fairly new to linux and not really a technical guy, so please really pardon my ignorance. Hope someone can help me. Thanks.

Below is the output of route -n:


Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface


iwconfig:


lo no wireless extensions.

eth1 IEEE 802.11b ESSID:"NETNOVA" Nickname:"Broadcom 4301"
Mode:Managed Frequency=2.484 GHz Access Point: Invalid
Bit Rate=11 Mb/s Tx-Power=16 dBm
RTS thr:off Fragment thr:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

eth0 no wireless extensions.

sit0 no wireless extensions


ifconfig:


eth0 Link encap:Ethernet HWaddr 00:02:3F:21:93:18
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:3058 errors:0 dropped:0 overruns:0 frame:0
TX packets:2744 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2745052 (2.6 MiB) TX bytes:342600 (334.5 KiB)
Interrupt:201 Base address:0xc800

eth1 Link encap:Ethernet HWaddr 00:90:4B:51:AC:6C
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:3514 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:124600 (121.6 KiB)
Interrupt:5 Base address:0x8000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:65 errors:0 dropped:0 overruns:0 frame:0
TX packets:65 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:5500 (5.3 KiB) TX bytes:5500 (5.3 KiB)


iwlist scan (mine is the one with hidden ssid):


lo Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:19:5B:1E:7F:E0
ESSID:"PaioLynn"
Protocol:IEEE 802.11bg
Mode:Master
Channel:6
Encryption key:on
Bit Rates:54 Mb/s
Extra: Rates (Mb/s): 1 2 5.5 6 9 11 12 18 22 24 36 48 54
Quality=100/100 Signal level=-174 dBm
Extra: Last beacon: 244ms ago
Cell 02 - Address: 00:14:6C:ED:C3:D4
ESSID:"<hidden>"
Protocol:IEEE 802.11bg
Mode:Master
Channel:11
Encryption key:on
Bit Rates:54 Mb/s
Extra: Rates (Mb/s): 1 2 5.5 6 9 11 12 18 22 24 36 48 54
Quality=100/100 Signal level=-145 dBm
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Extra: Last beacon: 154ms ago

eth0 Interface doesn't support scanning.

sit0 Interface doesn't support scanning.


cat /etc/network/interfaces:


auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid NETNOVA
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk bff572de540a2fa9d760b8e497a357c172613c604ac0192363 574f969b946abf


cat /etc/modprobe.d/ndiswrapper:


cat: /etc/modprobe.d/ndiswrapper: No such file or directory


cat /etc/resolv.conf:


nameserver 203.0.178.191
nameserver 203.0.178.191


sudo /etc/init.d/networking restart:


* Reconfiguring network interfaces... Internet Systems Consortium DHCP Client V3.0.3
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

Listening on LPF/eth0/00:02:3f:21:93:18
Sending on LPF/eth0/00:02:3f:21:93:18
Sending on Socket/fallback
DHCPRELEASE on eth0 to 192.168.1.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
Internet Systems Consortium DHCP Client V3.0.3
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

Listening on LPF/eth1/00:90:4b:51:ac:6c
Sending on LPF/eth1/00:90:4b:51:ac:6c
Sending on Socket/fallback
Internet Systems Consortium DHCP Client V3.0.3
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

Listening on LPF/eth0/00:02:3f:21:93:18
Sending on LPF/eth0/00:02:3f:21:93:18
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 2
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
Internet Systems Consortium DHCP Client V3.0.3
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

Listening on LPF/eth1/00:90:4b:51:ac:6c
Sending on LPF/eth1/00:90:4b:51:ac:6c
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 16
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 3
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
[ ok ]

[celloyd]

I have gotten my desktop card (eHome EH102) to work successfully but am still trying to work out the kinks regarding setting up security. Below is some of the info you requested if I were stumped. I'm using a Buffalo Router WHR-HP-G54 that has been flashed with DD-WRT v23 SP2 (09/15/06) std.

chad@chad-desktop:~$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth0
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0


chad@chad-desktop:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11FH ESSID:off/any
Mode:Managed Channel:0 Access Point: Not-Associated
Bit Rate=1 Mb/s Sensitivity=-200 dBm
RTS thr=2346 B Fragment thr=2346 B
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


chad@chad-desktop:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:50:8D:66:54:FB
inet addr:192.168.1.144 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::250:8dff:fe66:54fb/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:26139 errors:0 dropped:0 overruns:0 frame:0
TX packets:24482 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:5269046 (5.0 MiB) TX bytes:1980970 (1.8 MiB)
Interrupt:18 Base address:0xb000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:400 (400.0 b) TX bytes:400 (400.0 b)

wlan0 Link encap:Ethernet HWaddr 00:19:5B:04:96:6B
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:21 Memory:e8010000-e8020000

chad@chad-desktop:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:18:4D:55:0C:82
ESSID:"CA1214"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:18/100 Signal level:-84 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 02 - Address: 00:0C:41:C3:03:59
ESSID:"dana"
Protocol:IEEE 802.11b
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:7/100 Signal level:-91 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 03 - Address: 00:18:4D:84:A2:3E
ESSID:"NETGEAR"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:7/100 Signal level:-91 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 04 - Address: 00:16:01:7F:FC:62
ESSID:"dd-wrt"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:43/100 Signal level:-68 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
Cell 05 - Address: 00:18:F8:42:3F:38
ESSID:"linksys"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:7/100 Signal level:-91 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 06 - Address: 00:11:95:4D:AD:41
ESSID:"diamond"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:7/100 Signal level:-91 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0


chad@chad-desktop:~$ cat /etc/network/interfaces
auto lo
iface lo inet loopback


iface wlan0 inet dhcp
address 192.168.1.1
gateway 0.0.0.0
dns-nameservers 0.0.0.
netmask 255.255.255.0
wpa-driver wext
wpa-ssid dd-wrt
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxx
wireless-essid dd-wrt


iface eth0 inet dhcp

auto eth0


chad@chad-desktop:~$ cat /etc/modprobe.d/ndiswrapper
alias wlan0 ndiswrapper


chad@chad-desktop:~$ cat /etc/resolv.conf
# generated by NetworkManager, do not edit!



nameserver 192.168.1.1

[iamadam]

Hi. Just tried setting up my wireless and all seemed ok but when I try restarting the network i get this:



adam@adamslaptop-ubu:~$ sudo /etc/init.d/networking restart
* Reconfiguring network interfaces...There is already a pid file
/var/run/dhclient.eth1.pid with pid 6256
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:14:a5:7a:72:15
Sending on LPF/eth1/00:14:a5:7a:72:15
Sending on Socket/fallback
DHCPRELEASE on eth1 to 192.168.1.1 port 67
There is already a pid file /var/run/dhclient.eth1.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:14:a5:7a:72:15
Sending on LPF/eth1/00:14:a5:7a:72:15
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 10
No DHCPOFFERS received.
No working leases in persistent database - sleeping.


Here's the other info you might need:



adam@adamslaptop-ubu:~$ route -n
Kernel IP routeing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth1
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth1
adam@adamslaptop-ubu:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

eth1 IEEE 802.11g ESSID:"homenet"
Mode:Managed Frequency:2.442 GHz Access Point: 00:18:39:2C:02:AF
Bit Rate=54 Mb/s Tx-Power:25 dBm
RTS thr=2347 B Fragment thr=2346 B
Power Management:off
Link Quality:54/100 Signal level:-61 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

adam@adamslaptop-ubu:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:0F:B0:FA:8F:EC
inet addr:192.168.1.101 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::20f:b0ff:fefa:8fec/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:15 errors:0 dropped:0 overruns:0 frame:0
TX packets:49 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3146 (3.0 KiB) TX bytes:5868 (5.7 KiB)
Interrupt:20

eth1 Link encap:Ethernet HWaddr 00:14:A5:7A:72:15
inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::214:a5ff:fe7a:7215/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:557 errors:0 dropped:0 overruns:0 frame:0
TX packets:121 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:75430 (73.6 KiB) TX bytes:15429 (15.0 KiB)
Interrupt:22 Memory:d0010000-d0012000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:38 errors:0 dropped:0 overruns:0 frame:0
TX packets:38 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3206 (3.1 KiB) TX bytes:3206 (3.1 KiB)

adam@adamslaptop-ubu:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:14:7F:BD:B9:B2
ESSID:"BTHomeHub-52EE"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:4/100 Signal level:-93 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 02 - Address: 00:1B:2F:41:45:24
ESSID:"Bom chicka wa wa"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:46/100 Signal level:-66 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 03 - Address: 00:16:CE:69:A8:A1
ESSID:"Livebox-5BB8"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:21/100 Signal level:-82 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 04 - Address: 00:11:50:E8:69:8D
ESSID:"CheekyMonkey"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.422 GHz (Channel 3)
Quality:15/100 Signal level:-86 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 05 - Address: 00:0D:72:57:49:59
ESSID:"2WIRE034"
Protocol:IEEE 802.11b
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:15/100 Signal level:-86 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 06 - Address: 00:14:7F:A1:A6:96
ESSID:"gwatty"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:12/100 Signal level:-88 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 07 - Address: 00:18:39:2C:02:AF
ESSID:"homenet"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.442 GHz (Channel 7)
Quality:54/100 Signal level:-61 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK

adam@adamslaptop-ubu:~$ cat /etc/network/interfaces
auto lo
iface lo inet loopback

##auto eth0
##iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-ssid homenet
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk f7dd252bf4a2dcd8a1c7ba3cedb543f3a50cf77fe2eaf6cc56 7520b2ac5572c2

##auto eth2
##iface eth2 inet dhcp

##auto ath0
##iface ath0 inet dhcp

##auto wlan0
##iface wlan0 inet dhcp

adam@adamslaptop-ubu:~$ cat /etc/modprobe.d/ndiswrapper
cat: /etc/modprobe.d/ndiswrapper: No such file or directory
adam@adamslaptop-ubu:~$ cat /etc/resolv.conf
# generated by NetworkManager, do not edit!

search WAG54GS


nameserver 83.146.21.6
nameserver 212.158.248.5


This is the only thing keeping Vista on my hard drive at the moment so any help would be much appreciated.

[dcstar]

Hi. Just tried setting up my wireless and all seemed ok but when I try restarting the network i get this:
...........
This is the only thing keeping Vista on my hard drive at the moment so any help would be much appreciated.

What does iwconfig report?

[JeSTeR7]

My card works perfectly using WPA on two separate networks, but oddly enough, I can't get it to connect to any WEP networks, either by changing the /etc/network/interfaces or by attempting to use Network Manager.

My card is a Dell Truemoble 1450 minipci.

[wieman01]

After 3 weeks of vacation I am finally back. Reading all these messages that have been posted in the meantime, I'll refrain from answering each one of them because I don't which one of them is still relevant.

So if you still have problems you are free to post now. I'll be here to help.

[JeSTeR7]

My card works perfectly using WPA on two separate networks, but oddly enough, I can't get it to connect to any WEP networks, either by changing the /etc/network/interfaces or by attempting to use Network Manager.

My card is a Dell Truemoble 1450 minipci.

[wieman01]

My card works perfectly using WPA on two separate networks, but oddly enough, I can't get it to connect to any WEP networks, either by changing the /etc/network/interfaces or by attempting to use Network Manager.

My card is a Dell Truemoble 1450 minipci.
Could you post your interfaces file? I'll set it up for you if there are any obvious mistakes.

[JeSTeR7]

auto lo
iface lo inet loopback

#auto eth0
#iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp
wpa-driver wext
#wpa-ssid **********
wpa-ssid *********
wpa-ap-scan 1
wpa-proto WPA RSN
wpa-pairwise TKIP CCMP
wpa-group TKIP CCMP
wpa-key-mgmt WPA-PSK
##Home
#wpa-psk [edited for security]
##Work
wpa-psk [edited for security]

I don't have any settings in there right now for the couple of WEP networks i've tried, but basically what I've done is deleted EVERYTHING except the first two lines so it looks like this:

auto lo
iface lo inet loopback

#auto eth0
#iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp
wireless-essid wepnetwork
wireless-key wepnetworkskey

[wieman01]

@JeSTeR7:

Try this instead:


auto lo
iface lo inet loopback

auto eth1
iface eth1 inet dhcp
wireless-essid wepnetwork
wireless-key s:your_ascii_wep_key
Note the small "s:" in front of the ascii key. Drop it if you use the HEX key instead.

Do you happen to use a 64-bit WEP key? If so also give 128-bit a go. That could make a difference. Let me know how you go.

[JeSTeR7]

Awesome, I'll give that a shot.

As for being 64 or 128, it could be either. Both of the networks that I manage (work and home), and use most often are using WPA of course. I'd just like the ability to connect to any network at any time, know what I mean?

Thanks for the help. Not 1 day back from your vacation and you're already being pestered by teh noob ;)

I'll let you know how it goes.

[wieman01]

Awesome, I'll give that a shot.

As for being 64 or 128, it could be either. Both of the networks that I manage (work and home), and use most often are using WPA of course. I'd just like the ability to connect to any network at any time, know what I mean?
Yeah, I know what you mean... my approach does not really support that, however, Luca_linux may have advice. See this:

http://ubuntuforums.org/showthread.php?t=263136

His approach is similar despite the fact that you do all your security configuration in a separate file. But it does exactly what you have asked for.

[Mantrasong]

Ok, so my network uses WEP (I don't have a choice in the matter, my dad runs it), but how do I tell if I use LEAP or PEAP or anything else? Or otherwise, using this method:


auto eth1
iface eth1 inet dhcp
wireless-essid wepnetwork
wireless-key wepnetworkskey

can I add support for hidden essid?

[wieman01]

Ok, so my network uses WEP (I don't have a choice in the matter, my dad runs it), but how do I tell if I use LEAP or PEAP or anything else? Or otherwise, using this method:

can I add support for hidden essid?
Not sure what your requirements are, but WEP is fairly simple even with hidden ESSID. Why don't you use the standard Gnome applet to configure your network? That's the shortest route.

[gukn]

I just came here to say thank you very much.

[celloyd]

I assume that the wireless card needs to be working first? I had it working until I tried this process and now I cannot get the card to pick up again. I am not broadcasting my SSID and roaming is turned off so I'm just filling in the SSID but it does not want to take...

Ok, working now after I turned on broadcasting for my router. I'm confused on where you say to shut down the network manager initially? How does one do that? Right now I have the little blue meter icon in upper right telling me my signal strength. Is that part of the network manager app?

[wieman01]

I assume that the wireless card needs to be working first? I had it working until I tried this process and now I cannot get the card to pick up again. I am not broadcasting my SSID and roaming is turned off so I'm just filling in the SSID but it does not want to take...

Ok, working now after I turned on broadcasting for my router. I'm confused on where you say to shut down the network manager initially? How does one do that? Right now I have the little blue meter icon in upper right telling me my signal strength. Is that part of the network manager app?
Right... your card needs to be working first of all. I would be helpful if you posted the contents of:

gedit /etc/network/interfaces
Plus please do this for me:

iwlist scan
Then also tell us something about your network (e.g. encryption type, DHCP, etc.) so that I can help you. And there is no need to disable NetworkManager right now. We'll get to that later. The blue meter is part of the application, but ignore it for the time being.

[celloyd]

Right... your card needs to be working first of all. I would be helpful if you posted the contents of:

gedit /etc/network/interfaces
----------------------------------
auto lo
iface lo inet loopback
----------------------------------

Plus please do this for me:

iwlist scan
--------------------------------------------------------
chad@chad-desktop:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:16:01:7F:FC:62
ESSID:"dd-wrt"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:51/100 Signal level:-63 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 02 - Address: 00:18:4D:55:0C:82
ESSID:"CA1214"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:14/100 Signal level:-87 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 03 - Address: 00:11:95:4D:AD:41
ESSID:"diamond"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:7/100 Signal level:-91 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 04 - Address: 00:18:F8:42:3F:38
ESSID:"linksys"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:7/100 Signal level:-91 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
-------------------------------------------------------------------------------------------

Then also tell us something about your network (e.g. encryption type, DHCP, etc.) so that I can help you. And there is no need to disable NetworkManager right now. We'll get to that later. The blue meter is part of the application, but ignore it for the time being.


I'm using dhcp but i'm also telling it to assign static IP's to other pc's on my netowrk based on the MAC address. Right now I'm flying without any security. I have broadcasting enabled since it won't seem to work without that. I'm also certain that my wireless cards can you the same security scheme that you mention in your post.

As you can see I'm starting from scratch. I have not entered any of the stuff from your post yet. Here's my setup page from dd-wrt.

http://www.4shared.com/file/21094976/9e2973e7/Screenshot-DD-WRT_-_Setup_-_Mozilla_Firefox.html?cau2=403tNull

[wieman01]

@celloyd:

Could you upload the DD-WRT setup page here? I cannot access the link you have given from here (security).

What kind of WPA security do you intend to set up (1 or 2)? The scan shows that your wireless adapter recognizes WPA networks as such... in your case WPA-TKIP which is good news. Let start with WPA-TKIP (WPA1) then.

You need to configure both router and your PC and then restart the network. Have you tried that yet?

[celloyd]

@celloyd:

Could you upload the DD-WRT setup page here? I cannot access the link you have given from here (security).

What kind of WPA security do you intend to set up (1 or 2)? The scan shows that your wireless adapter recognizes WPA networks as such... in your case WPA-TKIP which is good news. Let start with WPA-TKIP (WPA1) then.

You need to configure both router and your PC and then restart the network. Have you tried that yet?

I hope you can access this. I don't know how to upload a screen print to this forum?

http://c.lloyd.home.mchsi.com/Screenshot-DD-WRT-Setup.png

Ok, on my setup, I'm not sure why but my gateway is all zeros and I am using open DNS for my domain so those are static on the bottom of the setup page I linked to. So I'm not sure about the modifications of the interface file. Do I need to change my setup to static so that if I lose connection, it will come back with the same IP? Thanks for your patience.

http://c.lloyd.home.mchsi.com/Screenshot-DD-WRT-Setup.png

[wieman01]

I hope you can access this. I don't know how to upload a screen print to this forum?

http://c.lloyd.home.mchsi.com/Screenshot-DD-WRT-Setup.png

Ok, on my setup, I'm not sure why but my gateway is all zeros and I am using open DNS for my domain so those are static on the bottom of the setup page I linked to. So I'm not sure about the modifications of the interface file. Do I need to change my setup to static so that if I lose connection, it will come back with the same IP? Thanks for your patience.

http://c.lloyd.home.mchsi.com/Screenshot-DD-WRT-Setup.png
Hello,

I could finally take a glance at your screen. Don't worry about the gateway, that's not relevant. Your router has got an IP (192.168.1.1), that's most important.

DHCP is always a bit of a risk in terms of changing IP addresses. That's why I usually prefer a static IP (in your case an IP between 192.168.1.2 and 192.168.1.99). Your interfaces file should look like this if you go for a static IP:

auto wlan0
iface wlan0 inet static
address 192.168.1.2
gateway 192.168.1.1
dns-nameservers 192.168.1.1
netmask 255.255.255.0
As for WPA configuration, I would try WPA1 (i.e. WPA) first, because we don't know if your wireless card & driver support WPA2. Do you know how to configure that in the router? There is a wireless security section that lets you set it up.

[celloyd]

Hello,

I could finally take a glance at your screen. Don't worry about the gateway, that's not relevant. Your router has got an IP (192.168.1.1), that's most important.

DHCP is always a bit of a risk in terms of changing IP addresses. That's why I usually prefer a static IP (in your case an IP between 192.168.1.2 and 192.168.1.99). Your interfaces file should look like this if you go for a static IP:

As for WPA configuration, I would try WPA1 (i.e. WPA) first, because we don't know if your wireless card & driver support WPA2. Do you know how to configure that in the router? There is a wireless security section that lets you set it up.

I'm confused yet again. My provider, Mediacom, does not give out static IP's to it's residential customers. Is that the address we are talking about? How do you have your static IP set up, specifically as it relates to dd-wrt? Could you give me an example of how my setup on dd-wrt should look?

Here's what the manual for my card says for WPA:

http://c.lloyd.home.mchsi.com/security.png

[wieman01]

I'm confused yet again. My provider, Mediacom, does not give out static IP's to it's residential customers. Is that the address we are talking about? How do you have your static IP set up, specifically as it relates to dd-wrt? Could you give me an example of how my setup on dd-wrt should look?

Here's what the manual for my card says for WPA:

http://c.lloyd.home.mchsi.com/security.png
Tell you what... I am not at home right now, but I'll post a screenshot when I get back home on Monday or so. There are 2 parts of the network that we are talking about:

a. WAN (Internet)
b. LAN

You provider might hand out static IPs but that has nothing to do with your local network which has its own set of IPs, etc. The router is assigned a static IP by your provder whereas your PCs need to establish a connection with your router, be it via DHCP or static IPs.

WPA2-PSK is what we need to configure next. Don't worry about the network settings right now, you don't seem to have a problem connecting. :-) Let's focus on WPA2 and see how we go.

I'll post my screenshots Monday at the latest.

[celloyd]

Tell you what... I am not at home right now, but I'll post a screenshot when I get back home on Monday or so. There are 2 parts of the network that we are talking about:

a. WAN (Internet)
b. LAN

You provider might hand out static IPs but that has nothing to do with your local network which has its own set of IPs, etc. The router is assigned a static IP by your provder whereas your PCs need to establish a connection with your router, be it via DHCP or static IPs.

WPA2-PSK is what we need to configure next. Don't worry about the network settings right now, you don't seem to have a problem connecting. :-) Let's focus on WPA2 and see how we go.

I'll post my screenshots Monday at the latest.

Sounds good. Here's what I'm using on my LAN side and it seems to be working ok.

http://c.lloyd.home.mchsi.com/static-dhcp.png

[wieman01]

Sounds good. Here's what I'm using on my LAN side and it seems to be working ok.

http://c.lloyd.home.mchsi.com/static-dhcp.png
Excellent. DHCP it is. Now assuming that you have enabled WPA (WPA, not WPA2... I don't know if your card supports the latter yet), this would be the right script for you:

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid <your_essid>
wpa-ap-scan 1
wpa-proto WPA RSN
wpa-pairwise TKIP CCMP
wpa-group TKIP CCMP
wpa-key-mgmt WPA-PSK
wpa-psk <your_hex_key>
Replace <your_essid> with your wireless network's name and <your_hex_key> with the key you have generated as mentioned in the guide.

Once you enable WPA on the router, your PC won't be able to reconnect unless you get the script right. To disable WPA in case you fail to reconnect, just use an Ethernet cable to do so.

Do you feel comfortable to continue from here? Everything seems set so far.

[soce_32]

I've got a Netgear WG311T PCI card in my workstation running 7.04.

My WAP is a Westell that came with my Verizon DSL service, and is setup for DHCP on 192.168.1.0, WPA1-PSK, b/g mixed mode, hidden SSID, channel 1, and TKIP encryption.

I have tried going back to WEP, broadcasting the SSID, and an open setup on the WAP, but no matter what I can't pick up a DHCP address. If I config ath0 for a static IP, I can't pass traffic on the network, so I'm doing something wrong, but I can't figure it out. When I boot, ath0 doesn't pick up the SSID, but if I restart /etc/init.d/networking, it shows up. I'm not sure what the wifi0 or *:avah interfaces are that are showing up or how they affect this whole process.

I tried the Network Manager, but it didn't help, so I killed it and took it out of my session setup, so it's not starting when I log in.

I have a Belkin WAP, and I tried setting it up as a WAP only and disable wireless on the Westell, but I can't connect to either one.

I hope another set of eyes can find what I'm missing, I've been at this for a couple days and just can't get it going.

Here's my relevant info:



> route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 ath0
0.0.0.0 0.0.0.0 0.0.0.0 U 1000 0 0 ath0

> iwconfig
ath0 IEEE 802.11b ESSID:"Go PSU" Nickname:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Bit Rate:0 kb/s Tx-Power:18 dBm Sensitivity=0/3
Retry:off RTS thr:off Fragment thr:off
Power Management:off
Link Quality=0/94 Signal level=-98 dBm Noise level=-98 dBm
Rx invalid nwid:9093 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

> ifconfig
ath0 Link encap:Ethernet HWaddr 00:18:4D:78:D8:CD
inet6 addr: fe80::218:4dff:fe78:d8cd/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

ath0:avah Link encap:Ethernet HWaddr 00:18:4D:78:D8:CD
inet addr:169.254.9.124 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1

eth0 Link encap:Ethernet HWaddr 00:0A:48:02:69:EE
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:20 Base address:0xc000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:111 errors:0 dropped:0 overruns:0 frame:0
TX packets:111 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:9971 (9.7 KiB) TX bytes:9971 (9.7 KiB)

wifi0 Link encap:UNSPEC HWaddr 00-18-4D-78-D8-CD-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9266 errors:0 dropped:0 overruns:0 frame:48
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:199
RX bytes:954398 (932.0 KiB) TX bytes:0 (0.0 b)
Interrupt:18

> cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto ath0
iface ath0 inet dhcp
wpa-ssid Go PSU
wpa-driver madwifi
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk biglonghexkey

> cat /etc/resolv.conf
# generated by NetworkManager, do not edit!
search myhome.westell.com

nameserver 192.168.1.1
nameserver 192.168.1.1

> iwlist scan
ath0 No scan results

> sudo lspci -v
02:07.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)
Subsystem: Netgear Unknown device 5a00
Flags: bus master, medium devsel, latency 168, IRQ 18
Memory at ee020000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [44] Power Management version 2

> sudo lsmod | grep ath
ath_rate_sample 14080 1
ath_pci 97312 0
wlan 204868 3 ath_rate_sample,ath_pci
ath_hal 192592 3 ath_rate_sample,ath_pci

[wieman01]

I've got a Netgear WG311T PCI card in my workstation running 7.04.

My WAP is a Westell that came with my Verizon DSL service, and is setup for DHCP on 192.168.1.0, WPA1-PSK, b/g mixed mode, hidden SSID, channel 1, and TKIP encryption.

I have tried going back to WEP, broadcasting the SSID, and an open setup on the WAP, but no matter what I can't pick up a DHCP address. If I config ath0 for a static IP, I can't pass traffic on the network, so I'm doing something wrong, but I can't figure it out. When I boot, ath0 doesn't pick up the SSID, but if I restart /etc/init.d/networking, it shows up. I'm not sure what the wifi0 or *:avah interfaces are that are showing up or how they affect this whole process.

I tried the Network Manager, but it didn't help, so I killed it and took it out of my session setup, so it's not starting when I log in.

I have a Belkin WAP, and I tried setting it up as a WAP only and disable wireless on the Westell, but I can't connect to either one.

I hope another set of eyes can find what I'm missing, I've been at this for a couple days and just can't get it going.
Before we go ahead... a few questions: Is "Go PSU" your SSID? Try another one that does not contain spaces (e.g. "GoPSU").

Second could you connect with all security turned off?

[soce_32]

wieman01,

It's awesome that you've stuck with this thread so long, and thanks for replying. I finally figured out what happened. Just for the record, you can do spaces in the SSID, and use single quotes if your passphrase has shell chars in it command like so:

wpa_passphrase "Some SSID" 'Some Complex PW!$'

Anyway, here's the scoop,

I borrowed a wireless USB adapter that required the rt73 cvs driver from serialmonkey, that was supposed to keep me going while the PCI card shipped, but it never did work quite right. Well, the rt73 stuff hosed my wlan_scan_* modules, and when I uninstalled the rt73 stuff, the wlan mods wouldn't load anymore.

I finally got a cable long enough to plug into my router and did a bunch of reinstallation of restricted drivers and such, and now that the wlan_scan modules are loading, as long as I do /etc/init.d/networking restart twice, I am back in business.

Thanks again

[toosweetnitemare]

the guide was quite excellent! thank you guys for creating this. i however still have an issue with WPA i followed your steps to the letter and somehow i seem to have completely fried my config and i had a do a clean install of fiesty so im back at square one. i have a ell latitude C400 and i have a TrueMobile 1150 series PC card for my wireless. and for some reason i cant get it to work, i may have to reinstall windows one here and i dont wanna do that cause i just got this person to switch to ubuntu. any help would be wonderful! thanks in advance

[wieman01]

the guide was quite excellent! thank you guys for creating this. i however still have an issue with WPA i followed your steps to the letter and somehow i seem to have completely fried my config and i had a do a clean install of fiesty so im back at square one. i have a ell latitude C400 and i have a TrueMobile 1150 series PC card for my wireless. and for some reason i cant get it to work, i may have to reinstall windows one here and i dont wanna do that cause i just got this person to switch to ubuntu. any help would be wonderful! thanks in advance
Does your card work at all and can you connect to unsecured networks? Please see section "Post this if you are stumped" and post whatever results you have. That would help a lot.

[paulok64]

Im Sorry to post here maybe a bit off topic but you folks seem concerned about wireless security and thats the issue im trying to deal with. I got a wireless router so I didn't have to be tied to my desk all day and still be able to use my laptop. I went through all the wireless security checks I found here and elsewhere. Changed admin password, enabled Wep with a difficult password, enabled mac filtering with my laptop as the only wireless machine allowed to use router, router only passes out 2 dhcp handles, 1 for laptop and 1 for desktop thats connected to it. Here is my issue everywhere i have read that you don't want to broadcast your essid or ssid (not sure what to call it). If I disable broadcasting my laptop can't connect. I know im missing something because if i disable roaming and try to connect manually I can't connect either doesn't matter if Im broadcasting or not. The 2 issues maybe related. I don't know. I think as it is i am pretty safe but i would like to quit broadcasting any help would be appreciated. Ill keep an eye on board and if i need to supply more information will do so promptly

Thanks in advance
Paul D.

[wieman01]

Im Sorry to post here maybe a bit off topic but you folks seem concerned about wireless security and thats the issue im trying to deal with. I got a wireless router so I didn't have to be tied to my desk all day and still be able to use my laptop. I went through all the wireless security checks I found here and elsewhere. Changed admin password, enabled Wep with a difficult password, enabled mac filtering with my laptop as the only wireless machine allowed to use router, router only passes out 2 dhcp handles, 1 for laptop and 1 for desktop thats connected to it. Here is my issue everywhere i have read that you don't want to broadcast your essid or ssid (not sure what to call it). If I disable broadcasting my laptop can't connect. I know im missing something because if i disable roaming and try to connect manually I can't connect either doesn't matter if Im broadcasting or not. The 2 issues maybe related. I don't know. I think as it is i am pretty safe but i would like to quit broadcasting any help would be appreciated. Ill keep an eye on board and if i need to supply more information will do so promptly

Thanks in advance
Paul D.
First off, turning off broadcasting does not really add any extra security. As soon as your PC tries to connect to the network, it transmits the ESSID anyway.

Second, WEP is a higly flawed security protocol and thus very unsecure. One can crack even a secure (long) password in less than one hour. I could break into my own WEP secured network in less than 20 minutes so I'd rather refrain from using it. Try WPA instead.

EDIT:
And no, it's not off-topic at all. :-)

[spoonernash]

First, I would like to thank wieman01 for this thread. It was very helpful for me.

paulok64, up until yesterday I firmly believed that turning off beaconing was good wireless security. But in trying to get my wireless going, I ran across an Ubuntu page (in Launchpad?) that stated, like wieman01 replied, that not beaconing was basically worthless as a security measure. That led me to google it and I read further pages explaining why. This convinced me, I turned on the beacon, and my wireless started working.

The same regarding MAC filtering and dhcp restrictions. Security value not worth the trouble. Just use WPA with a very good passphase.

[wieman01]

First, I would like to thank wieman01 for this thread. It was very helpful for me.

paulok64, up until yesterday I firmly believed that turning off beaconing was good wireless security. But in trying to get my wireless going, I ran across an Ubuntu page (in Launchpad?) that stated, like wieman01 replied, that not beaconing was basically worthless as a security measure. That led me to google it and I read further pages explaining why. This convinced me, I turned on the beacon, and my wireless started working.

The same regarding MAC filtering and dhcp restrictions. Security value not worth the trouble. Just use WPA with a very good passphase.
You are welcome.

This might be a good read for you as well:

http://www.renderlab.net/projects/WPA-tables/

It basically says that choosing the right ESSID (network name) does play a role in terms of security as well. So it's both the password and the network's name. Turning broadcast adds no value, however, choosing a name that is NOT in "the top 1000 SSID list on wigle.net" should be taken into consideration.

[emmir]

Hi there,

For the last 3 days I try to figure out how to cofigure my wireless network but had no success whatsoever. I'm completely new to Linux and being an IT pro for the last 10 years didn't helped me at all :(
I managed to come to the point where Network Manager connects me to my wifi only when roaming is anabled. But I want to give it a static IP.
I tried to follow instructions and modify /etc/network/interfaces but didn't worked out. I need some serious help here.
I don't know if it helps but here are some clues:

iwlist scan:

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:14:C1:20:1C:CF
ESSID:"MMSDH"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.447 GHz (Channel 8 )
Quality:85/100 Signal level:-41 dBm Noise level:-96 dBm
Encryption key: on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK

/etc/network/interfaces (after modifying):

iface eth1 inet static
address 192.168.72.70
netmask 255.255.255.0
broadcast 192.168.72.255
gateway 192.168.72.68
dns-nameservers 192.168.72.68
wpa-driver wext
wpa-ssid <My_Net>
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk <My_Hex_key>


I even tried to remove network manager but :(

Thats the only issue i have to solve with my Feisty installation so I can get to the eye of my MS-addicted collegues in the office so I'd aprecciate any given help

Thank you in advance

[wieman01]

Hi there,

For the last 3 days I try to figure out how to cofigure my wireless network but had no success whatsoever. I'm completely new to Linux and being an IT pro for the last 10 years didn't helped me at all :(
I managed to come to the point where Network Manager connects me to my wifi only when roaming is anabled. But I want to give it a static IP.
I tried to follow instructions and modify /etc/network/interfaces but didn't worked out. I need some serious help here.
I don't know if it helps but here are some clues:

[removed]

Thank you in advance
Could you try this one instead:

auto eth1
iface eth1 inet static
address 192.168.72.70
netmask 255.255.255.0
broadcast 192.168.72.255
gateway 192.168.72.68
dns-nameservers 192.168.72.68
wpa-driver wext
wpa-ssid <My_Net>
wpa-ap-scan 1
wpa-proto RSN WPA
wpa-pairwise CCMP TKIP
wpa-group CCMP TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <My_Hex_key>
Then please restart the network and post the results:

sudo ifdown -v eth1

sudo ifup -v eth1

[emmir]

As soon as I get back home from work, I'll give it a try....

I'll get back to you with the results.

Thnank you very much

[wieman01]

As soon as I get back home from work, I'll give it a try....

I'll get back to you with the results.

Thank you very much
No problem, we'll get there. :-)

[emmir]

Well here I am... I try what you suggested, but still somehow the wireless get an IP automatic here are the results of the commands you posted:

myron@archlux:~$ sudo ifdown -v eth1
/etc/network/interfaces:16: interface eth1 declared allow-auto twice
ifdown: couldn't read interfaces file "/etc/network/interfaces"

myron@archlux:~$ sudo ifup -v eth1
/etc/network/interfaces:16: interface eth1 declared allow-auto twice
ifup: couldn't read interfaces file "/etc/network/interfaces"

I dont know what went wrong...

Any Ideas?

[wieman01]

Well here I am... I try what you suggested, but still somehow the wireless get an IP automatic here are the results of the commands you posted:

myron@archlux:~$ sudo ifdown -v eth1
/etc/network/interfaces:16: interface eth1 declared allow-auto twice
ifdown: couldn't read interfaces file "/etc/network/interfaces"

myron@archlux:~$ sudo ifup -v eth1
/etc/network/interfaces:16: interface eth1 declared allow-auto twice
ifup: couldn't read interfaces file "/etc/network/interfaces"

I dont know what went wrong...

Any Ideas?
Could you post the whole contents of "/etc/network/interfaces"?

[Megatog615]

I have a Linksys WPC11v4. I'm trying to access the network here at my rented vacation house(I don't have an ethernet cord handy). I have to use the (rather restricted)computer here to type this(by hand).

Here's the info(from iwlist wlan0 scan):

Cell 02 - Address: 00:0D:0B:FB:94:F1
ESSID:"Triple T"
Protocol:IEEE 802.11b
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:blah blah blah
Encryption key: on
Bit Rates:1 MB/s; 2MB/s; 5.5 Mb/s; 11 MB/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK

I know the passkey and the passphrase. If anyone is using a Linksys WPC11v4 and using WPA settings with a similar setup, please post your /etc/network/interfaces.

[wieman01]

I have a Linksys WPC11v4. I'm trying to access the network here at my rented vacation house(I don't have an ethernet cord handy). I have to use the (rather restricted)computer here to type this(by hand).

Here's the info(from iwlist wlan0 scan):

Cell 02 - Address: 00:0D:0B:FB:94:F1
ESSID:"Triple T"
Protocol:IEEE 802.11b
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:blah blah blah
Encryption key: on
Bit Rates:1 MB/s; 2MB/s; 5.5 Mb/s; 11 MB/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK

I know the passkey and the passphrase. If anyone is using a Linksys WPC11v4 and using WPA settings with a similar setup, please post your /etc/network/interfaces.
There should be stuff on the first page. Use the script for WPA1 and DHCP, that should be ok.

What chipset have you got? Ralink by chance?

[emmir]

Could you post the whole contents of "/etc/network/interfaces"?

I found out that there are two entries for "eth1" in "interfaces".

I tried to edit the file and get rid of the 2nd entry which caused the problem but "sudo gedit /etc/network/interfaces" didn't respond. So I thought " lets log as root in console mode and nano it".
Alas, I typed by mistake "sudo init 3" and when nothing happened I remembered that I should type "sudo init 1" (or at least I thought I should ](*,) ).
I don't know why (I know now...Murphy's law ) but nano didn't worked out either so I thought " ok lets go back to graphical interface" typed "exit" and...bam!!! Al I see since is a light brown screen with a mouse pointer in it.
Apparently I some how managed to screw up my system.
Funny thing is I cant just give up using the "It's all Greek to me" excuse,
because I AM GREEK and thus I should be able to figure it out :mad:

We have a saying here that freely translated goes: "Twise the same sin isn't a wise mans manner". Thinking I might have to reinstall for the third time... here goes my wisdom...

Any thoughts about that?

[wieman01]

I found out that there are two entries for "eth1" in "interfaces".

I tried to edit the file and get rid of the 2nd entry which caused the problem but "sudo gedit /etc/network/interfaces" didn't respond. So I thought " lets log as root in console mode and nano it".
Alas, I typed by mistake "sudo init 3" and when nothing happened I remembered that I should type "sudo init 1" (or at least I thought I should ](*,) ).
I don't know why (I know now...Murphy's law ) but nano didn't worked out either so I thought " ok lets go back to graphical interface" typed "exit" and...bam!!! Al I see since is a light brown screen with a mouse pointer in it.
Apparently I some how managed to screw up my system.
Funny thing is I cant just give up using the "It's all Greek to me" excuse,
because I AM GREEK and thus I should be able to figure it out :mad:

We have a saying here that freely translated goes: "Twise the same sin isn't a wise mans manner". Thinking I might have to reinstall for the third time... here goes my wisdom...

Any thoughts about that?
:-) Sorry for saying it but your post made me laugh. Yeah, I have gone through similar situations, it's like domino, you try to fix one thing and by doing so break a couple of other things that make the whole situation deteriorate.

All I can say here is that you should open up a new thread and post your problem there. I guess it can be fixed so don't reinstall just yet. People will tell you where to find the right log files, how to interpret and ultimately how to fix the issue.

Nevertheless if you have a problem with your wireless network, you know where you find me. :-)

[Megatog615]

There should be stuff on the first page. Use the script for WPA1 and DHCP, that should be ok.

What chipset have you got? Ralink by chance?

RTL8180(I do use ndiswrapper, however). I'll try the script provided.

I am running Gutsy as well. Also, the ESSID contains a space. What is the correct syntax for entering it in the interfaces file?

[wieman01]

RTL8180(I do use ndiswrapper, however). I'll try the script provided.

I am running Gutsy as well.
Try this WPA1 script and let me know if you run into problems.

[Megatog615]

I get something similar to this problem:
http://ubuntuforums.org/showthread.php?p=2828588#post2828588

I am using the latest drivers on the Realtek website for rtl8180(roughly 3 years old now).

[emmir]

:-) Sorry for saying it but your post made me laugh. Yeah, I have gone through similar situations, it's like domino, you try to fix one thing and by doing so break a couple of other things that make the whole situation deteriorate.

All I can say here is that you should open up a new thread and post your problem there. I guess it can be fixed so don't reinstall just yet. People will tell you where to find the right log files, how to interpret and ultimately how to fix the issue.

Nevertheless if you have a problem with your wireless network, you know where you find me. :-)

I intended to do so :) After all I needed it too.
"Always look on the bright side of life" as Monty Pythons sang!!! As what the re- installation part concerns: I might have many virtues, but patience isn't one of them so I'd rather start over from scratch (repetition is the mother of learning...) than asking around how to shape up xorg.conf or what ever file I've managed to accomplish "carnal knowledge" with (I hope you're catching my drift;) )

I guess I'll "see" you in a couple of days again. Meanwhile, have fun..

[Maelgwyn]

Does anyone know how to setup wireless networking via WPA Pre-Shared Key in a command-line fashion? I've got a server-install with Fluxbox running on top, so I don't have all the bells & whistles that one gets with a GNOME install... If I can be pointed in the right direction (or even told how to do it!), I can unsecure the network to install files if necessary, and then re-secure and go from there!

Cheers ^_^

[wieman01]

Does anyone know how to setup wireless networking via WPA Pre-Shared Key in a command-line fashion? I've got a server-install with Fluxbox running on top, so I don't have all the bells & whistles that one gets with a GNOME install... If I can be pointed in the right direction (or even told how to do it!), I can unsecure the network to install files if necessary, and then re-secure and go from there!

Cheers ^_^
This HOWTO is basically command line only. Simply replace "gksu gedit" with "sudo nano" and you are there.

[emmir]

I'm back!!!
Took me about 2 hours to set the whole thing up but now I'm the proud owner of a working Wifi with static IP.:):):) Thank you, thank you very much.

A last question: is it normal for "network manager" to give me only the "manual configuration" option and no wifi indication at all (you know those vertical increasing in size blue lines) ? And if so, is there a way to have a graphical indication for it?

Again, thank you

[Megatog615]

Can someone point me towards some drivers for RTL8180L that actually supports WPA?

[wieman01]

Can someone point me towards some drivers for RTL8180L that actually supports WPA?
As far as I can tell the latest version for Windows (v1.73... is that the latest version?) does not support WPA at all, only WEP.

http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=26&PFid=5&Level=6&Conn=5&DownTypeID=3&GetDown=false&Downloads=true
http://drivers.softpedia.com/get/NETWORK-CARD/REALTEK/Realtek-RTL8180L-173.shtml

Not sure about Linux drivers though, but bad news if you were thinking about using "ndiswrapper".

[Megatog615]

Oh well. Can anyone tell me the best-working wireless card(for laptops) that supports WPA1/WPA2? I'm thinking of switching my home network over to WPA anyway. Everything else besides my laptop's wireless card supports WPA(as advertised...).

[wieman01]

Oh well. Can anyone tell me the best-working wireless card(for laptops) that supports WPA1/WPA2? I'm thinking of switching my home network over to WPA anyway. Everything else besides my laptop's wireless card supports WPA(as advertised...).
Based on what I have learned from ubuntu_demon you should get yourself a WG311T. You find the whole discussion here:

http://ubuntuforums.org/showthread.php?t=363633

This card seems to work without much hassle and has full WPA2 support.

[Megatog615]

Any good cardbus cards?

[wieman01]

Any good cardbus cards?
None that I know of. But you could check here:

https://help.ubuntu.com/community/WifiDocs/WirelessCardsSupported

[emmir]

I'm back!!!
Took me about 2 hours to set the whole thing up but now I'm the proud owner of a working Wifi with static IP.:):):) Thank you, thank you very much.

A last question: is it normal for "network manager" to give me only the "manual configuration" option and no wifi indication at all (you know those vertical increasing in size blue lines) ? And if so, is there a way to have a graphical indication for it?

Again, thank you

Besides that why must I give " sudo ifdown -v eth1" and "sudo ifup -v eth1" every time I turn my pc on? Isn't there a way to avoid this?

[wieman01]

Besides that why must I give " sudo ifdown -v eth1" and "sudo ifup -v eth1" every time I turn my pc on? Isn't there a way to avoid this?
This is a bug that others have confirmed as well. See post #2 for a workaround.

[airstrike]

this is an awesome guide. it worked perfectly well. congrats and thanks on writing such a good how-to!

[Maelgwyn]

route -n
Destination Gateway Genmask Flags Metric Ref Use Iface
10.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 ra0
0.0.0.0 10.1.1.1 0.0.0.0 UG 0 0 0 ra0

iwconfig

ra0 RT2500 Wireless ESSID "DLINK_WIRELESS" //This is wrong - should be "This Binary Universe"



cat /etc/network/interfaces
// usual stuff here

# The primary network interface
auto ra0
iface ra0 inet static
address 10.1.1.12
gateway 10.1.1.1
dns-nameservers 10.1.1.1
netmask 255.0.0.0
wpa-driver wext
wpa-ssid This Binary Universe
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk bf0d97141d75a8bda5a4f307d766547c2dbeec388401f08fa8 54db8d13d85c2c


cat /etc/modprobe.d/ndiswrapper
cat: /etc/modprobe.d/ndiswrapper: No such file or directory


cat /etc/resolv.conf
nameserver 10.1.1.1

If it's of any use - the wireless router is 10.1.1.2 and it's connected via cat6 to the broadband router which is 10.1.1.1. I can get this going on my boyfriends' XP laptop, but I can't get it going on my Ubuntu server + fluxbox desktop =(

I want my computer to have interweb capabilities!!! *cry*

[wieman01]

route -n
Destination Gateway Genmask Flags Metric Ref Use Iface
10.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 ra0
0.0.0.0 10.1.1.1 0.0.0.0 UG 0 0 0 ra0

iwconfig

ra0 RT2500 Wireless ESSID "DLINK_WIRELESS" //This is wrong - should be "This Binary Universe"



cat /etc/network/interfaces
// usual stuff here

# The primary network interface
auto ra0
iface ra0 inet static
address 10.1.1.12
gateway 10.1.1.1
dns-nameservers 10.1.1.1
netmask 255.0.0.0
wpa-driver wext
wpa-ssid This Binary Universe
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk bf0d97141d75a8bda5a4f307d766547c2dbeec388401f08fa8 54db8d13d85c2c


cat /etc/modprobe.d/ndiswrapper
cat: /etc/modprobe.d/ndiswrapper: No such file or directory


cat /etc/resolv.conf
nameserver 10.1.1.1

If it's of any use - the wireless router is 10.1.1.2 and it's connected via cat6 to the broadband router which is 10.1.1.1. I can get this going on my boyfriends' XP laptop, but I can't get it going on my Ubuntu server + fluxbox desktop =(

I want my computer to have interweb capabilities!!! *cry*
Sorry, it's a Ralink. Mentioned in post #1, you'll have to replace the driver with "ndiswrapper" if you want to follow thiw HOWTO. Ralink does not work.

[Maelgwyn]

cat: /etc/modprobe.d/ndiswrapper: No such file or directory

This means I don't have ndiswrapper installed eh? Is it as simple as apt-get install ndiswrapper?

[wieman01]

cat: /etc/modprobe.d/ndiswrapper: No such file or directory

This means I don't have ndiswrapper installed eh? Is it as simple as apt-get install ndiswrapper?
It's not as simple, but you find tons of HOWTOs around here. If you need help, post your issues and send me the link by PM. :-)

[Megatog615]

How can I get this manual connection to show network status such as signal strength with knetworkmanager?

I got a new card by the way. It's a Ralink chipset but how am I to know(damn vendors don't supply chipset info on the box)?

Using ndiswrapper for now until open source drivers for it can handle WPA2 without locking the system.

[wieman01]

How can I get this manual connection to show network status such as signal strength with knetworkmanager?
You can't.

Enable DHCP on the router and use KNetworkManager instead. Only follow this tutorial if you need a static IP. I also recommend the use of "ndiswrapper" as the Ralink driver for Linux is a hassle.

[foxy123]

Hi, thanks a lot for the howto. It is great. However I still has a problem. Even after creating a script for network restart I still have to do it manually again (without the script I had to do it twice). I tried to add the same line in the script but it does not seem to work. Any advice?


$ sudo /etc/init.d/networking restart
Password:
* Reconfiguring network interfaces... RTNETLINK answers: File exists
run-parts: /etc/network/if-up.d/avahi-autoipd exited with return code 2
[ OK ]

[wieman01]

Hi, thanks a lot for the howto. It is great. However I still has a problem. Even after creating a script for network restart I still have to do it manually again (without the script I had to do it twice). I tried to add the same line in the script but it does not seem to work. Any advice?


$ sudo /etc/init.d/networking restart
Password:
* Reconfiguring network interfaces... RTNETLINK answers: File exists
run-parts: /etc/network/if-up.d/avahi-autoipd exited with return code 2
[ OK ]

What wireless adapter have you got? An are you running Firestarter?

No idea yet... Let's see if we find a solution together.

[foxy123]

What wireless adapter have you got? An are you running Firestarter?

No idea yet... Let's see if we find a solution together.

I am running BCM4306 chip with ndiswrapper. No I am not running Firestarter.

[Paris Heng]

Can I do like this in my Linux Atheros Wifi? I want to have both AP mode and Ad-hoc mode in my laptop. It is possible?

#wlanconfig ath0 create wlandev wifi0 wlanmode ap
#wlanconfig ath1 create wlandev wifi0 wlanmode adhoc

Please assist. Thank you.

[wieman01]

I am running BCM4306 chip with ndiswrapper. No I am not running Firestarter.
There was another user with a similar problem. Tried to find the relevant posts but in vain. I remember that we had no success in the end and a manual restart was still necessary. Sorry I cannot say more.

[wieman01]

Can I do like this in my Linux Atheros Wifi? I want to have both AP mode and Ad-hoc mode in my laptop. It is possible?

#wlanconfig ath0 create wlandev wifi0 wlanmode ap
#wlanconfig ath1 create wlandev wifi0 wlanmode adhoc

Please assist. Thank you.
I am afraid I cannot follow you. Can you explain what this is about? I may have nothing to do with this thread... Anyway, let us know.

[Paris Heng]

I am afraid I cannot follow you. Can you explain what this is about? I may have nothing to do with this thread... Anyway, let us know.

You are using Madwifi _ Madwifi-tools rights? I believe you have encounter this type of configuration to make the Wifi card become station, ad-hoc, and AP ..etc.

[wieman01]

You are using Madwifi _ Madwifi-tools rights? I believe you have encounter this type of configuration to make the Wifi card become station, ad-hoc, and AP ..etc.
I see... No, I don't use Madwifi right now. Somehow yes, there is mention of a Madwifi driver in the HOWTO, but I have never heard of such a tool.

[Paris Heng]

I see... No, I don't use Madwifi right now. Somehow yes, there is mention of a Madwifi driver in the HOWTO, but I have never heard of such a tool.

Anyway thanx, are you 'Zhong guo Ren'? Your side is very useful.

[emmir]

What wireless adapter have you got? An are you running Firestarter?


I have the same problem. Even though I followed your 2nd post so I don't have to restart networking after reboot it didn't work. What about Firestarter? Is there something you have to configure in order to have wifi upon restart?

[wieman01]

I have the same problem. Even though I followed your 2nd post so I don't have to restart networking after reboot it didn't work. What about Firestarter? Is there something you have to configure in order to have wifi upon restart?
Actually no. It just happens that occasionally there is an issue with DHCP and Firestarter. So that's why I thought turning it off would be a remedy. Just to test it.

What adapter have you got?

[foxy123]

There was another user with a similar problem. Tried to find the relevant posts but in vain. I remember that we had no success in the end and a manual restart was still necessary. Sorry I cannot say more.

Thanks anyway. Possibly it's a bug in Ubuntu's basic networking script. It is really quite inconvenient that it cannot be done automatic.

[wieman01]

Thanks anyway. Possibly it's a bug in Ubuntu's basic networking script. It is really quite inconvenient that it cannot be done automatic.
All we can do it file bug reports at Launchpad...

[foxy123]

All we can do it file bug reports at Launchpad...

yes, but I do not know against what package. And also it is not clear what is wrong.

[Dark Star]

Very nice How to will help me soon :)

[emmir]

Actually no. It just happens that occasionally there is an issue with DHCP and Firestarter. So that's why I thought turning it off would be a remedy. Just to test it.

What adapter have you got?

USR Maxg 5417A, and a USR 9108 wifi Router.

I don't use DHCP. How can I be sure its disabled?

[wieman01]

yes, but I do not know against what package. And also it is not clear what is wrong.
Ok, I'll see what I can do. Should have done that long ago. I'll report back.

[wieman01]

USR Maxg 5417A, and a USR 9108 wifi Router.

I don't use DHCP. How can I be sure its disabled?
Firestarter is not installed by default so don't worry about it if you have not installed it yourself.

As for the reconnection issue... Launchpad is all I can suggest.

[emmir]

Firestarter is not installed by default so don't worry about it if you have not installed it yourself.

As for the reconnection issue... Launchpad is all I can suggest.

ok thank you...
For the record:
I have installed Firestarter, (since I'm using Azureus). I also have kind of "reverse" followed your second post in order to get rid of the initially created files and links, and create them again. Since then wifi connection (or re-connection if you like) at startup works at will!!! Imagine my surprise when immediatly after reboot I opened Firefox and I saw my start page loading rapidly, (and not from the cache since I configured firefox to delete everything when I close the program) and then when I tried to load another page... there was no connection!!
Anyway I'm still trying to figure thinks out. When I have any news I'll get back to you.
Thank you again for your valuable help...

[wieman01]

ok thank you...
For the record:
I have installed Firestarter, (since I'm using Azureus). I also have kind of "reverse" followed your second post in order to get rid of the initially created files and links, and create them again. Since then wifi connection (or re-connection if you like) at startup works at will!!! Imagine my surprise when immediatly after reboot I opened Firefox and I saw my start page loading rapidly, (and not from the cache since I configured firefox to delete everything when I close the program) and then when I tried to load another page... there was no connection!!
Anyway I'm still trying to figure thinks out. When I have any news I'll get back to you.
Thank you again for your valuable help...
Interesting finding, mate.

You use the 'madwifi' driver as part of your script. Does replacing it with 'wext' make a difference?

[Trash_Gordon]

Hi,
I've been trying to bring up Wireless Lan on my Ubuntu system for months now, and I finally have the feeling that I'm *that* close to succeeding. However, there is an obstacle left which I couldn't figure out.
I'm using a Fritz! WLAN USB Stick with native Linux drivers which is working fine. I've set up wpa_supplicant according to your howto, but then I get this:


RTNETLINK answers: File exists
run-parts: /etc/network/if-up.d/avahi-autoipd exited with return code 2

full ifup -v wlan0 (http://pastebin.com/f6d254f04)
I've been looking around and couldn't find relief. Hope you can help me. Here some additional information:

root@adrian:/home/adrian# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid FRITZ!Box Fon WLAN 7141
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <censored>



root@adrian:/home/adrian# iwonfig
bash: iwonfig: command not found
root@adrian:/home/adrian# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11b/g ESSID:"FRITZ!Box Fon WLAN 7141"
Mode:Managed Channel:6 Access Point: 00:04:0E:F8:9D:E6
Encryption key:3131-3131-3131-3131-3131-3131-31 Security mode:open
Link Signal level=-62 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0



root@adrian:/home/adrian# ifconfig wlan0
wlan0 Protokoll:Ethernet Hardware Adresse 00:04:0E:CB:81:CE
inet Adresse:192.168.178.20 Bcast:192.168.178.255 Maske:255.255.255.0
inet6 Adresse: fe80::204:eff:fecb:81ce/64 Gültigkeitsbereich:Verbindung
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:267 errors:0 dropped:0 overruns:0 frame:0
TX packets:182 errors:12 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:1000
RX bytes:48598 (47.4 KiB) TX bytes:19272 (18.8 KiB)

[wieman01]

full ifup -v wlan0
It looks like the adapter has been able to connect. What happens when you do this (please post the output):

route

ping 192.168.178.1

[Trash_Gordon]

Well, the problem solved itself. After rebooting, it works fine. Thanks for your awesome walkthrough.

[Ken101]

I can connect with my WG111 (no encryption) and have tried to set up WPA-PSK. I must have some wrong setting but I don't know how to proceed. Xubuntu 6.06 - assistance is appreciated - thx

wlan0 Scan completed :
Cell 01 - Address: 00:09:5B:71:3D:B8
ESSID:"PCD"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.457 GHz (Channel 10)
Quality:0/100 Signal level:-78 dBm Noise level:-256 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=1
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK

[wieman01]

I can connect with my WG111 (no encryption) and have tried to set up WPA-PSK. I must have some wrong setting but I don't know how to proceed. Xubuntu 6.06 - assistance is appreciated - thx

wlan0 Scan completed :
Cell 01 - Address: 00:09:5B:71:3D:B8
ESSID:"PCD"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.457 GHz (Channel 10)
Quality:0/100 Signal level:-78 dBm Noise level:-256 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=1
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Please also post the contents of "/etc/network/interfaces".

[Ken101]

Thx for quick reply!
Here is /etc/network/interfaces - i'm sure it's wrong but i'm clueless

auto lo
iface lo inet loopback


iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp


iface eth2 inet dhcp
wireless-essid PCD
wireless-key randburg

auto ath0
iface ath0 inet dhcp
wpa-driver wext
wpa-ssid "PCD"
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk "c0fc780681eda01aa2dc10dc39cda62373e7cc25cc43bc639d ec5f69ab41d203"






auto eth2





iface wlan0 inet dhcp
wireless-essid PCD
wireless-key s:













auto wlan0

auto eth0

[wieman01]

Thx for quick reply!
Here is /etc/network/interfaces - i'm sure it's wrong but i'm clueless

auto lo
iface lo inet loopback

iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp

iface eth2 inet dhcp
wireless-essid PCD
wireless-key randburg

auto ath0
iface ath0 inet dhcp
wpa-driver wext
wpa-ssid "PCD"
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk "c0fc780681eda01aa2dc10dc39cda62373e7cc25cc43bc639d ec5f69ab41d203"

auto eth2

iface wlan0 inet dhcp
wireless-essid PCD
wireless-key s:

auto wlan0

auto eth0
Ok, let's try this instead. Please replace the contents with this (no "" please):

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid PCD
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk c0fc780681eda01aa2dc10dc39cda62373e7cc25cc43bc639 dec5f69ab41d203
Then restart the computer. That done, restart the network manually and post the output:

sudo ifdown -v wlan0

sudo ifup -v wlan0

route

[Ken101]

ken@ken-laptop:~$ sudo ifdown -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 4803
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:0f:b5:dc:74:be
Sending on LPF/wlan0/00:0f:b5:dc:74:be
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 192.168.0.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
ifconfig wlan0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan0.pid
Stopped /sbin/wpa_supplicant (pid 4779).
ken@ken-laptop:~$ sudo ifup -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan0
wpa_supplicant: wpa-ap-scan 1 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "PCD" -- OK
wpa_supplicant: wpa-psk ***** -- FAIL
wpa_supplicant: wpa-pairwise TKIP -- OK
wpa_supplicant: wpa-group TKIP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto WPA -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:0f:b5:dc:74:be
Sending on LPF/wlan0/00:0f:b5:dc:74:be
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
Synchronizing clock to ntp.ubuntu.com...
Error : Temporary failure in name resolution
ken@ken-laptop:~$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
ken@ken-laptop:~$

[wieman01]

It's obvious... you have not generated the PSK correctly:

wpa_supplicant: wpa-psk ***** -- FAIL
How did you do it? Please remove all apostrophes ("") when you generate it? There should not be any "" in /etc/network/interfaces.

[Ken101]

I entered it & wireless worked briefly.
Is there any application that can do the wireless configuration job instead of manually entering it?

[wieman01]

I entered it & wireless worked briefly.
Is there any application that can do the wireless configuration job instead of manually entering it?
There is. Network Manager which comes with the default install of Feisty Fawn. What version of Ubuntu are you on?

[Ken101]

:guitar:I'm connected!
I installed Wicd (http://wicd.sourceforge.net/) and got it working with not too much trouble.

I recommend anyone to use this program - it worked for me!

[tech9]

sweet... I will check this out

[delta2]

wieman01 thank you success!

[prosonik]

After many hours of frustration, I have the WL-138g and a dell gx280 working with the console based instructions..
I'm using the latest and greatest Ndiswrapper.. I had to uninstall all network managers..
WICD did not 'see' my card. even when i configured it (wlan0).. I'm not sure why. I have used wicd before, and it seemed to work well...

If people are having problems not getting a dhcp offer, go back and check your essid and wpa password.. That was part of my problem.. as well ensure your ndis is working.. (ndiswrapper -v) and (ndisrwrapper -l)

pro

[merlin666]

Thank you, I managed to get my router connected on the first try even with ESSID disabled and MAC filtering in place. However, after a few minutes I lost the connection and I don't know how to re-connect. My router still shows up when I type iwlist scan.

How do I re-establish the connection?

Update: I restarted the network connection. Now there is wlan0 without Interface information in Network Tools, and also wlan0:avahi that shows the correct MAC address - this is also listed in the router log. It looks like wlan0:avahi is not doing anything.

[wieman01]

Thank you, I managed to get my router connected on the first try even with ESSID disabled and MAC filtering in place. However, after a few minutes I lost the connection and I don't know how to re-connect. My router still shows up when I type iwlist scan.

How do I re-establish the connection?

Update: I restarted the network connection. Now there is wlan0 without Interface information in Network Tools, and also wlan0:avahi that shows the correct MAC address - this is also listed in the router log. It looks like wlan0:avahi is not doing anything.
No idea what "wlan0:avahi" is. Could you post the output?

As for the issue with the dropping connection, that must have something to do with the router & the wireless adapter. Is the router on "mixed mode"?

[merlin666]

Thank you for the response and how-to. The connection was re-established after I did a re-boot.

A re-boot seems to solve about 85% of the problems I may have had when changing something in Ubuntu.

[wieman01]

Thank you for the response and how-to. The connection was re-established after I did a re-boot.

A re-boot seems to solve about 85% of the problems I may have had when changing something in Ubuntu.
Haha... Yes, indeed. :-)

[merlin666]

No idea what "wlan0:avahi" is. Could you post the output?

As for the issue with the dropping connection, that must have something to do with the router & the wireless adapter. Is the router on "mixed mode"?

I started up ubuntu again today and faced the same problem. What kind of diagnostic output would be useful here?

Oh and another question: I finally managed to get network manager into the notification area and it is dead - only works with the wired connection. Is this a result of the security configuration?

[wieman01]

I started up ubuntu again today and faced the same problem. What kind of diagnostic output would be useful here?
You could try post #2 in the thread. If that doesn't help, you need to post the contents of your boot log files. The most relevant one is this one:

gedit /var/log/boot

Oh and another question: I finally managed to get network manager into the notification area and it is dead - only works with the wired connection. Is this a result of the security configuration?
Yes, it is.

[emmir]

Hi again...

I had to reinstall and decided to upgrade to 2.6.22.11 (it suppose to solve the "harsh" shutdown problem). Trying to apply your method I get this:
myron@Pelion:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

Warning: Driver for device eth1 has been compiled with version 22
of Wireless Extension, while this program supports up to version 20.
Some things may be broken...

eth1 No scan results


Ignoring this and proceeding with the next steps I get this:

myron@Pelion:~$ sudo ifup -v eth1
Configuring interface eth1=eth1 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
SIOCSIFFLAGS: No such file or directory
Error for wireless request "Set Encode" (8B2A) :
invalid argument "935818082004%%".
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.eth1.pid
Stopped /sbin/wpa_supplicant (pid 8687).
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.eth1.pid -i eth1 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
SIOCSIFFLAGS: No such file or directory
Could not set interface 'eth1' UP
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/eth1
wpa_supplicant: wpa-ap-scan 1 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "MMSDH" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise CCMP TKIP -- OK
wpa_supplicant: wpa-group CCMP TKIP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto RSN WPA -- OK
wpa_supplicant: enabling network block 0 -- OK

ifconfig eth1 192.168.72.70 netmask 255.255.255.0 broadcast 192.168.72.255 up
SIOCSIFFLAGS: No such file or directory
SIOCSIFFLAGS: No such file or directory
Failed to bring up eth1.

Is there a way to work around this?

[wieman01]

@emmir:

Oh, man. Beats me. The only thing I could suggest is that you upgrade to the latest version of "ndiswrapper" as well.

If that does not work, I could help you with the shutdown issue. This is what fixed it for me after I had installed Feisty:

http://ubuntuforums.org/showthread.php?t=420999

[exz]

thanks worked like a charm. tried the wpa-driver ipw3945 at first (got it from some random internet forum) but without success.. it worked with the wext driver thought.. thanks!

[wieman01]

thanks worked like a charm. tried the wpa-driver ipw3945 at first (got it from some random internet forum) but without success.. it worked with the wext driver thought.. thanks!
Did Network Manager not work for you? Just curious.

[Depressed Man]

Do you have any idea why it would stop working? I have a laptop with ipw3945. I didn't have to download any additional drivers or do anything that you described in your guide. It just worked after my install with my wireless settings after I inputed them in (WPA Personal, passphrase, and cipher type).

However, recently it doesn't work anymore. It can't connect to my wireless network unless I turn off the protection (it works fine in Vista with the protection as well).

Any idea why this changed recently? And how to fix it?

[wieman01]

Do you have any idea why it would stop working? I have a laptop with ipw3945. I didn't have to download any additional drivers or do anything that you described in your guide. It just worked after my install with my wireless settings after I inputed them in (WPA Personal, passphrase, and cipher type).

However, recently it doesn't work anymore. It can't connect to my wireless network unless I turn off the protection (it works fine in Vista with the protection as well).

Any idea why this changed recently? And how to fix it?
Beats me. I have not noticed any change at all, but that is because I have turned off automatic updates (with security updates being the exception).

[Depressed Man]

And now it works again.. ugh.

[mail5253680]

OK -- DId the stuff in the parent post, but problems remain:

I have Dlink wireless PCI card in a desktop system. When I first boot up, the system brings up the card and connects to the wireless router, then asks for an IP address via DHCP. This last step fails and continues to fail.

After bootup however, I go to the command line and issue the commands:

sudo ifdown ath0
sudo ifup ath0

At the last command, I see the interface starting up again, DHCP asking for an IP address, which works!

What could be the problem with bringing up the interface the first time?

Why would a simple ifdown/ifup make it work?

What can I do to make it work automatically at boot?

[wieman01]

OK -- DId the stuff in the parent post, but problems remain:

I have Dlink wireless PCI card in a desktop system. When I first boot up, the system brings up the card and connects to the wireless router, then asks for an IP address via DHCP. This last step fails and continues to fail.

After bootup however, I go to the command line and issue the commands:

sudo ifdown ath0
sudo ifup ath0

At the last command, I see the interface starting up again, DHCP asking for an IP address, which works!

What could be the problem with bringing up the interface the first time?

Why would a simple ifdown/ifup make it work?

What can I do to make it work automatically at boot?
It's a known bug (nature knows where). Please see post #2 for a workaround.

[neptho]

This has been a bit of a pain, but it actually works for mapping multiple 'known' points in your /etc/network/interfaces file. I've got some ideas from here (http://www.lazy8.nu/delld180/DebianLinuxOnDellLattitude810laptop.html), which helped me fix the mapping problems I was having when I was using my own script. His information is for WEP, but this will also work for WPA, as you will see below.

First, you'll want to create /etc/network/wlan-scanning.sh:

#!/bin/sh
#
# Written by Thomas Dilts 20060719, Trivial fixups by Shawn Holwegner.
# This script is designed to be run by the "interfaces" system to find which
# wireless networks are present and return the first found interface.
#
#We must run as root (id -u returns then 0) and we must have the interface name as input
if [ `id -u` -ne "0" ] || [ "$1" = "" ]; then exit 1; fi

iface="$1"
which=""
# With this method, You only need one scan, instead of scanning for each SSID until you find the AP.
FOUNDAPS=`/sbin/iwlist "$iface" scanning | grep ESSID`
while read searchstring returnvalue ; do
if [ "$which" ]; then continue; fi
echo " Trying to find wlan $searchstring" >&2
if echo "$FOUNDAPS" | /bin/grep -c "$searchstring" >/dev/null2>&1
then
which="$returnvalue" ;
echo " found $searchstring and now starting $which" >&2
fi
done

if [ "$which" ]; then echo $which; exit 0; fi
exit 1

Remember to chmod it 775 so it can run.

Now, edit your mappings in /etc/network/interfaces as so:


auto eth1
mapping eth1
script /etc/network/wlan-scanning.sh
map HomeSSID HOME
map WorkSSID WORK
map key:off TRAVELING

iface HOME inet dhcp
wpa-ssid HomeSSID
wpa-psk wpa_key_generated_with_wpa_passphrase_here
...

iface WORK inet dhcp
wpa-ssid WorkSSID
wpa-psk wpa_key_generated_with_wpa_passphrase_here
...

#This is the open system setup that works at hotels and airports.
iface TRAVELING inet dhcp
iface eth1 inet dhcp

It's actually pretty simple to use, once you have it setup. It will scan for any of the 'known' SSIDs in your mapping, and execute wpa_supplicant with the correct data. Priorly, I had been using a custom ifup interface and a cobbled together wpa_supplicant.conf that set priorities for different SSIDs. It also took about 5 seconds to bring the interface up. Now? About 2.

I hope this helps others, many thanks to Thomas Dilts for a functional mapping script.

If you run it manually, it will tell you what it's looking for, and what it finds. Using the '-v' flag coupled with ifup will give useful debugging information.


%sudo ifup eth1
Trying to find wlan HomeSSID
Trying to find wlan WorkSSID
Found WorkSSID and now starting WORK

[st33med]

I am having problems with my wireless on startup. It does not always connect on startup, it drops connections randomly, and Network Manager does not cooperate with my setup.

route -n:

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 wlan0
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 wlan0
iwconfig:

lo no wireless extensions.

eth0 no wireless extensions.

Warning: Driver for device wlan0 has been compiled with version 22
of Wireless Extension, while this program supports up to version 20.
Some things may be broken...

wlan0 IEEE 802.11g ESSID:"mason"
Mode:Managed Frequency:2.422 GHz Access Point: 00:13:10:C8:97:8D
Bit Rate=36 Mb/s Tx-Power:32 dBm
RTS thr=2347 B Fragment thr=2346 B
Power Management:off
Link Quality:62/100 Signal level:-56 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

ifconfig:

eth0 Link encap:Ethernet HWaddr 00:15:C5:B7:17:A9
inet addr:192.168.2.1 Bcast:192.168.2.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:22

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:516 (516.0 b) TX bytes:516 (516.0 b)

wlan0 Link encap:Ethernet HWaddr 00:18:F3:57:D5:3D
inet addr:192.168.1.102 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::218:f3ff:fe57:d53d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3320 errors:0 dropped:0 overruns:0 frame:0
TX packets:2334 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2547642 (2.4 MiB) TX bytes:331565 (323.7 KiB)
Interrupt:16 Memory:efdfc000-efe00000

route:

Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 * 255.255.255.0 U 0 0 0 eth0
192.168.1.0 * 255.255.255.0 U 0 0 0 wlan0
link-local * 255.255.0.0 U 1000 0 0 wlan0
default 192.168.1.1 0.0.0.0 UG 0 0 0 wlan0

cat /etc/network/interfaces:

#auto eth0
#iface eth0 inet dhcp

#auto eth1
#iface eth1 inet dhcp

#auto eth2
#iface eth2 inet dhcp

#auto ath0
#iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid ***** #censored!
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk 1072992ef365767275eb91331246b79ceb8175e359df3dfbc1 8f01704ac001fe

cat /etc/modprobe.d/ndiswrapper:

alias wlan0 ndiswrapper
cat /etc/resolv.conf:

nameserver 68.87.73.242
nameserver 68.87.71.226

[wieman01]

I am having problems with my wireless on startup. It does not always connect on startup, it drops connections randomly, and Network Manager does not cooperate with my setup.
It's close to impossible to judge from here what could be going on. Network Manager usually does a better job at reconnecting, however, under the circumstances it is no option I guess.

What wireless adapter have you got?

WICD might be an alternative for you if everything else fails. If reconnecting after boot is the issue, then see post #2.

[gladstone]

I followed these steps (after trying ALOT of other methods) but couldnt get it to work. I decided to test if it would work after a reboot, instead I was given the gnome-settings-daemon error.

Initially having no idea what had happened (I couldn't login), I managed to pin-point it back to the /etc/network/interfaces file I just edited.

The bug has been discussed here:

https://bugs.launchpad.net/ubuntu/+source/control-center/+bug/61381

and more specifically:

https://bugs.launchpad.net/ubuntu/+source/control-center/+bug/61381/comments/43

https://bugs.launchpad.net/ubuntu/+source/control-center/+bug/61381/comments/23

However, during that time, my wireless was working!

Is there anything I can try? I can remember another guide adding something like DISABLED=1 to /etc/wpa_supplicant.conf (I saw it mentioned in the Launchpad thread)... Is that the correct command?

[Target2019]

I have a Belkin 54g PC card, and it is connected to a Netgear WGR614v7 using WEP. I have SSID broadcast OFF, and the key is 128bit Hex.

I'm using WEP for now, as I have another notebook with a wireless B card. In time I'll find another great deal on a G card, and go to WPA-PSK.

Until then, I'm using WEP, and securing it as best I can. I start the notebook (or after it wakes from hibernate) and then have to enter the network manager > connect to other wireless manager. I enter the information, and connect. Can I save this information in some way, and streamline the process. I'd like to keep things simple, as I take this notebook to other locations, and do not want to complicate things going forward.

Here is iwconfig


iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:"STATIONID"
Mode:Managed Frequency:2.427 GHz Access Point: 00:1B:2F:55:C0:32
Bit Rate=54 Mb/s Tx-Power:32 dBm
RTS thr=2347 B Fragment thr=2346 B
Power Management:off
Link Quality:48/100 Signal level:-65 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

Iwlist scan:


iwlist scan

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:1B:2F:55:C0:32
ESSID:"STATIONID"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.427 GHz (Channel 4)
Quality:51/100 Signal level:-63 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0

Finally, my network interface config:


sudo gedit /etc/network/interfaces

auto lo
iface lo inet loopback


I've read some posts in this thread, and I'm looking for some help to alter my config, so that I can connect to my home wireless with as few steps as possible.

Thanks.

[lorenmcc]

I have experienced that I have to restart networking multiple times to get connected. Is there a more reliable method to get connected?

[wieman01]

I followed these steps (after trying ALOT of other methods) but couldnt get it to work. I decided to test if it would work after a reboot, instead I was given the gnome-settings-daemon error.

Initially having no idea what had happened (I couldn't login), I managed to pin-point it back to the /etc/network/interfaces file I just edited.

The bug has been discussed here:

https://bugs.launchpad.net/ubuntu/+source/control-center/+bug/61381

and more specifically:

https://bugs.launchpad.net/ubuntu/+source/control-center/+bug/61381/comments/43

https://bugs.launchpad.net/ubuntu/+source/control-center/+bug/61381/comments/23

However, during that time, my wireless was working!

Is there anything I can try? I can remember another guide adding something like DISABLED=1 to /etc/wpa_supplicant.conf (I saw it mentioned in the Launchpad thread)... Is that the correct command?
If you posted the contents of "/etc/network/interfaces" it would help a lot. I don't know if "DISABLED=1" is the right command at the moment.

[wieman01]

I have experienced that I have to restart networking multiple times to get connected. Is there a more reliable method to get connected?
Have you noticed post #2? It might be the solution.

[wieman01]

I have a Belkin 54g PC card, and it is connected to a Netgear WGR614v7 using WEP. I have SSID broadcast OFF, and the key is 128bit Hex.

I'm using WEP for now, as I have another notebook with a wireless B card. In time I'll find another great deal on a G card, and go to WPA-PSK.

Until then, I'm using WEP, and securing it as best I can. I start the notebook (or after it wakes from hibernate) and then have to enter the network manager > connect to other wireless manager. I enter the information, and connect. Can I save this information in some way, and streamline the process. I'd like to keep things simple, as I take this notebook to other locations, and do not want to complicate things going forward.

Here is iwconfig


iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:"STATIONID"
Mode:Managed Frequency:2.427 GHz Access Point: 00:1B:2F:55:C0:32
Bit Rate=54 Mb/s Tx-Power:32 dBm
RTS thr=2347 B Fragment thr=2346 B
Power Management:off
Link Quality:48/100 Signal level:-65 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

Iwlist scan:


iwlist scan

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:1B:2F:55:C0:32
ESSID:"STATIONID"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.427 GHz (Channel 4)
Quality:51/100 Signal level:-63 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0

Finally, my network interface config:


sudo gedit /etc/network/interfaces

auto lo
iface lo inet loopback


I've read some posts in this thread, and I'm looking for some help to alter my config, so that I can connect to my home wireless with as few steps as possible.

Thanks.
Well, you could follow this tutorial which should make it as simple as possible for you. If you encounter problems you could just post here.

Another solution for you might be WICD:

http://wicd.sourceforge.net/

[Target2019]

Well, you could follow this tutorial which should make it as simple as possible for you. If you encounter problems you could just post here.

Another solution for you might be WICD:

http://wicd.sourceforge.net/

Thanks for the link to WICD. I'll check that out.

Assuming by tutorial, you mean the first post or two, I have read that. I did not find WEP mentioned, so I searched the thread with google. I found some posts tht tried to address WEP specifically, read them, and was confused. So I posted the results of what I have in configuration, as I had seen done many times in this thread.

Thanks again for the reference to WICD.

[lorenmcc]

Have you noticed post #2? It might be the solution.

I have written a script based on Post #2 (before I asked the question). This script has a loop in it abd will continue until the connection is made. I actually had to limit the looping since the laptop took a long time to connect. Connection is very intermittent, I am currently running the script for the second time (with a loop limit of 100) and it has still not connected.

[Target2019]

Tried Wicd. It wouldn't find the hidden network using any of the supplicant modes, unfortunately. I found on Wicd forum that when ndiswrapper is used, there are additional problems. I re-installed network manager, and I'm back on. I'll try to keep it simple by using network manager.

I'll keep searching for what I need to do to get a hidden network listed, and maybe there'll be a way to store the WEP key too.

[wieman01]

Tried Wicd. It wouldn't find the hidden network using any of the supplicant modes, unfortunately. I found on Wicd forum that when ndiswrapper is used, there are additional problems. I re-installed network manager, and I'm back on. I'll try to keep it simple by using network manager.

I'll keep searching for what I need to do to get a hidden network listed, and maybe there'll be a way to store the WEP key too.
Hidden networks should not be an issue any longer in Feisty. You need to select "Connect to other wireless network..." however. Then type in the name and you are ready to roll.

[lorenmcc]

I have written a script based on Post #2 (before I asked the question). This script has a loop in it abd will continue until the connection is made. I actually had to limit the looping since the laptop took a long time to connect. Connection is very intermittent, I am currently running the script for the second time (with a loop limit of 100) and it has still not connected.

I have gotten this to work more reliably, but it begs the question as to why this is occurring, possibly some startup sequence issue?

I had to add the following to the loop in my script



killall dhclient wpa_supplicant dhclient3
rm /var/run/dhclient.*


and now I can connect almost every time on the first loop (but not always).

Any ideas?

BTW, I have never gotten wicd to connect, this is the only method I have gotten to work (as in posts #1 and #2)

[Target2019]

Hidden networks should not be an issue any longer in Feisty. You need to select "Connect to other wireless network..." however. Then type in the name and you are ready to roll.
I installed Wicd as you suggested. This uninstalled network manager. With Wicd I could not connect to hidden network using any of the supplicant modes.

I re-installed network manager, which uninstalled Wicd. Now I have the "connect to other networks" item, and can manually enter SSID and WEP key.

I am back to network manager, and wondering if there is a way to configure the hidden network and WEP key, so that I don't have to re-enter them each time I boot (or awake).

Thank you very much.

[wieman01]

I installed Wicd as you suggested. This uninstalled network manager. With Wicd I could not connect to hidden network using any of the supplicant modes.

I re-installed network manager, which uninstalled Wicd. Now I have the "connect to other networks" item, and can manually enter SSID and WEP key.

I am back to network manager, and wondering if there is a way to configure the hidden network and WEP key, so that I don't have to re-enter them each time I boot (or awake).

Thank you very much.
I think you are looking for a tool called "GNOME Keyring Manager". There are a number of tutorials for it.

[Target2019]

I think you are looking for a tool called "GNOME Keyring Manager". There are a number of tutorials for it.
Thanks for that tip. Keyring Manager come into play after I open Network Manager and enter the hidden SSID and WEP key.

Just tried something different. I re-booted, then opened keyring. Open network manager and enter the SSID and WEP. I was thinking that the WEP key, properly stored in keyring would auto-connect, but it doesn't seem to matter.

I guess I'll have to search further for a way to configure this, or just wait for some improvements to ubuntu, or maybe a better wifi management app.

I'll have to accept that there is no way to enter the required information to a network config file.

[wieman01]

Thanks for that tip. Keyring Manager come into play after I open Network Manager and enter the hidden SSID and WEP key.

Just tried something different. I re-booted, then opened keyring. Open network manager and enter the SSID and WEP. I was thinking that the WEP key, properly stored in keyring would auto-connect, but it doesn't seem to matter.

I guess I'll have to search further for a way to configure this, or just wait for some improvements to ubuntu, or maybe a better wifi management app.

I'll have to accept that there is no way to enter the required information to a network config file.
You did not find anything on the forums? I am sure I have seen something concerning it a while ago. I'll post if I find something tomorrow.

[Target2019]

You did not find anything on the forums? I am sure I have seen something concerning it a while ago. I'll post if I find something tomorrow.
I searched SSID + hidden + WEP, and found a few threads that confirm the problem.

Finally cleared up the keyring problem by installing pam-keyring, so that my user login pass gets passed to keyring manager.

[gladstone]

If you posted the contents of "/etc/network/interfaces" it would help a lot. I don't know if "DISABLED=1" is the right command at the moment.

Hi, my etc/network/interfaces looked like this:



auto lo
iface lo inet loopback

auto eth1
iface eth1 inet static
address 192.168.1.2
gateway 192.168.1.1
dns-nameservers 192.168.1.1
netmask 255.255.255.0
wpa-driver wext
wpa-ssid Toupe
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk [MY HASHED PSK]


I have a laptop and my wireless adaptor is an Intel pro 2200BG

[wieman01]

Hi, my etc/network/interfaces looked like this:



auto lo
iface lo inet loopback

auto eth1
iface eth1 inet static
address 192.168.1.2
gateway 192.168.1.1
dns-nameservers 192.168.1.1
netmask 255.255.255.0
wpa-driver wext
wpa-ssid Toupe
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk [MY HASHED PSK]


I have a laptop and my wireless adaptor is an Intel pro 2200BG
Looks fine actually. You have disabled SSID broadcast and use WPA-TKIP. What does a scan yield?

sudo iwlist scan

[jabberwauki]

In my experience, the following instruction from the main thread

<quote>
VERY IMPORTANT:
Now convert your WPA ASCII password using the following command (' ' single quotes required):

wpa_passphrase 'ssid' 'ascii_key'
</quote>

did not actually require single quotes. wpa_passphrase generated a different key when single quotes were used which was rejected by my router. removing the single quotes and generating the key again solved this for me.

i am using a netgear wgr614v5 wireless router with a netgear wg511 (version 1 made in taiwan) pcmcia card on an acer laptop.

[wieman01]

In my experience, the following instruction from the main thread

<quote>
VERY IMPORTANT:
Now convert your WPA ASCII password using the following command (' ' single quotes required):

wpa_passphrase 'ssid' 'ascii_key'
</quote>

did not actually require single quotes. wpa_passphrase generated a different key when single quotes were used which was rejected by my router. removing the single quotes and generating the key again solved this for me.

i am using a netgear wgr614v5 wireless router with a netgear wg511 (version 1 made in taiwan) pcmcia card on an acer laptop.
Thanks for highlighting that. I have corrected the tutorial accordingly. :-)

[gladstone]

Looks fine actually. You have disabled SSID broadcast and use WPA-TKIP. What does a scan yield?

It gives me:


sudo iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:14:7F:58:E8:19
ESSID:"BTHomeHub-4543"
Protocol:IEEE 802.11bg
Mode:Master
Channel:6
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=29/100 Signal level=-82 dBm
Extra: Last beacon: 272ms ago
Cell 02 - Address: 00:03:2F:2B:71:6B
ESSID:"<hidden>"
Protocol:IEEE 802.11bg
Mode:Master
Channel:11
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 9 Mb/s; 11 Mb/s
6 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=71/100 Signal level=-57 dBm
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Extra: Last beacon: 520ms ago


My router is "Cell 02" in that list. I also use MAC filters, would that make an effect?

I also managed to enable the front LED and when I used my earlier /etc/network/interfaces and rebooted, Ubuntu slowed at 3/4 of the way and resulted in the GNOME.DESKTOP error I mention, but the LED was solid i.e. connected :confused:

[wieman01]

@Gladstone:

Everything looks fine to me. But beats me, I don't know what's going on. MAC filtering could be an issue but only if the registered MAC isn't the same as the one listed above (00:03:2F:2B:71:6B).

Have you turned roaming off?

[vandetta]

I have a problem. I installed ubuntu in my machine and there's one problem. Wireless problem. The OS detect all the hardware perfectly and everything runs fine except for the wireless. The OS can detect wireless networks but could not connect to it. I attach together the screenshot and hopefully anyone can try to give me solution for this. Oh yes, the wireless was Realtek RTL8187. Thanks.

http://i16.photobucket.com/albums/b34/lazrus/ubuntuerrorscreenshot.png

[wieman01]

I have a problem. I installed ubuntu in my machine and there's one problem. Wireless problem. The OS detect all the hardware perfectly and everything runs fine except for the wireless. The OS can detect wireless networks but could not connect to it. I attach together the screenshot and hopefully anyone can try to give me solution for this. Oh yes, the wireless was Realtek RTL8187. Thanks.

http://i16.photobucket.com/albums/b34/lazrus/ubuntuerrorscreenshot.png
Please open a new separate thread for your this issue. It has not really anything do to with this one. But feel free to send me the link by PM.

[vandetta]

Oh, I'm sorry I will open new thread for this :)

[houms]

I followed these steps (after trying ALOT of other methods) but couldnt get it to work. I decided to test if it would work after a reboot, instead I was given the gnome-settings-daemon error.

Initially having no idea what had happened (I couldn't login), I managed to pin-point it back to the /etc/network/interfaces file I just edited.

The bug has been discussed here:

https://bugs.launchpad.net/ubuntu/+source/control-center/+bug/61381

and more specifically:

https://bugs.launchpad.net/ubuntu/+source/control-center/+bug/61381/comments/43

https://bugs.launchpad.net/ubuntu/+source/control-center/+bug/61381/comments/23

However, during that time, my wireless was working!

Is there anything I can try? I can remember another guide adding something like DISABLED=1 to /etc/wpa_supplicant.conf (I saw it mentioned in the Launchpad thread)... Is that the correct command?

what does your /etc/network/interfaces look like..? what wireless card and driver are you using? A quick glance at your earlier post show you have a
dns-nameserver
in your interfaces file?

[gladstone]

Horrrayy!

Thanks houms, it was that rogue dns-nameservers that was causing all the problems. I'm not sure where I picked that up from, but I've been adding bits of things from all over the place over the last 2 weeks to get this working :( I hope it's not just all part of the learning curve!

I also have to use the network restart script for it to work (as described in post 2 here (http://ubuntuforums.org/showpost.php?p=1351902&postcount=2))

[houms]

Horrrayy!

Thanks houms, it was that rogue dns-nameservers that was causing all the problems. I'm not sure where I picked that up from, but I've been adding bits of things from all over the place over the last 2 weeks to get this working I hope it's not just all part of the learning curve!

I also have to use the network restart script for it to work (as described in post 2 here)
I'm glad I could help...don't worry, you'll learn quickly because the community here is great...really first rate. Just a quick suggestion... if you're having problems with the wireless starting up every time you boot up add the following using the post-up command and see if it helps...
in your etc/network/interfaces file... say your wireless interface is eth1....currently your last line at the end of the configuration setting for eth1 is

wpa-psk yourhexkeyhere

what you want to do add these two lines to the end

post-up iface down
post-up iface up

this works like a charm for me.... I just boot up and my wireless "just works".....Let me know if ya need help.

[latino.negro]

gracias hombre por tu ayuda

[latino.negro]

pero puedes hacer un en espanol para mi amigos

[wieman01]

pero puedes hacer un en espanol para mi amigos
In Spanish? No pienso tan.

[gladstone]

I've just upgraded to Gutsy and thankfully this method still works (although now I can select WPA in Network Managers Manual settings).

As a note, I left my etc/network/interfaces intact after the upgrade. On every subsequent boot, the IPW2200 driver would have 80 - near 100% CPU usage. I removed the network restart script (as described in post 2 of this thead) and replaced it with the

post-up iface down
post-up iface up

as described by Houms above. The problem seems to have gone away! Perhaps the original bug has been fixed, but I'll leave the post-up commands in for now.

[wieman01]

I've just upgraded to Gutsy and thankfully this method still works (although now I can select WPA in Network Managers Manual settings).

As a note, I left my etc/network/interfaces intact after the upgrade. On every subsequent boot, the IPW2200 driver would have 80 - near 100% CPU usage. I removed the network restart script (as described in post 2 of this thead) and replaced it with the

post-up iface down
post-up iface up

as described by Houms above. The problem seems to have gone away! Perhaps the original bug has been fixed, but I'll leave the post-up commands in for now.
Could you post your interfaces file? I will update the tutorial and post your method instead. Seems a lot simpler. Thanks.

[gladstone]

Just simply adding

post-up iface down
post-up iface up

to the end, like:


auto lo
iface lo inet loopback

auto eth1
iface eth1 inet static
address 192.168.1.2
gateway 192.168.1.1
dns-nameservers 192.168.1.1
netmask 255.255.255.0
wpa-driver wext
wpa-ssid Toupe
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk [MY HASHED PSK]
post-up iface down
post-up iface up

Connecting works fine, although the problem with the IPW2200 driver nearing 100% CPU usage is inconclusive as it's happening randomly (when I reboot, it's fine)

[Tex-Twil]

Hello,
I have problems with using wpa_supplicant with my R8187 card:



root@xx:~# wpa_supplicant -Dipw -iwlan0 -c/etc/wpa_supplicant.conf
Trying to associate with 00:13:f7:01:b9:e1 (SSID='SMC_Chaloupka' freq=0 MHz)
ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Authentication with 00:00:00:00:00:00 timed out.
Trying to associate with 00:13:f7:01:b9:e1 (SSID='SMC_Chaloupka' freq=0 MHz)
ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Authentication with 00:00:00:00:00:00 timed out.
Trying to associate with 00:13:f7:01:b9:e1 (SSID='SMC_Chaloupka' freq=0 MHz)
ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys


any ideas ?

[wieman01]

Hello,
I have problems with using wpa_supplicant with my R8187 card:



root@xx:~# wpa_supplicant -Dipw -iwlan0 -c/etc/wpa_supplicant.conf
Trying to associate with 00:13:f7:01:b9:e1 (SSID='SMC_Chaloupka' freq=0 MHz)
ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Authentication with 00:00:00:00:00:00 timed out.
Trying to associate with 00:13:f7:01:b9:e1 (SSID='SMC_Chaloupka' freq=0 MHz)
ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Authentication with 00:00:00:00:00:00 timed out.
Trying to associate with 00:13:f7:01:b9:e1 (SSID='SMC_Chaloupka' freq=0 MHz)
ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys


any ideas ?
This has nothing to do with this tutorial, hence I cannot help much. But one thing I have noticed:

ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
That normally means that your hardware does not support WPA or the use of wpa_supplicant. Now use another driver as "ipw" has been deprecated:

wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf
"wext" will do for "ndiswrapper".

[Tex-Twil]

Hello,


This has nothing to do with this tutorial, hence I cannot help much.

Sorry, I thought this was the right thread for this question.



"wext" will do for "ndiswrapper".


I've allready tried this before and here is the output:



root@xx:~# wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 -



Btw, my card is and Alfa Awus36H.

Thanks for you help.

[wieman01]

Hello,


Sorry, I thought this was the right thread for this question.



I've allready tried this before and here is the output:



root@xx:~# wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 -



Btw, my card is and Alfa Awus36H.

Thanks for you help.
No problem.

I have seen this error message before. Does the Windows driver that you are using really support WPA? Could you check the change-log please?

[Tex-Twil]

No problem.
I have seen this error message before. Does the Windows driver that you are using really support WPA? Could you check the change-log please?

Hi,
Yes, on Windows XP/Vista WPA is ok. FYI, I'm using patched drivers from aircrack :

http://www.aircrack-ng.org/doku.php?id=r8187

The readme of the original drivers says that WPA is supported



- Support WEP and WPAPSK connection]


Maybe I can try to recompile the drivers, without patching them and see what will happen.

see ya.

[wieman01]

Hi,
Yes, on Windows XP/Vista WPA is ok. FYI, I'm using patched drivers from aircrack :

http://www.aircrack-ng.org/doku.php?id=r8187

The readme of the original drivers says that WPA is supported



Maybe I can try to recompile the drivers, without patching them and see what will happen.

see ya.
Do you use "ndiswrapper" at all? The drivers shows as "wlan0". Weird.

[Tex-Twil]

Do you use "ndiswrapper" at all? The drivers shows as "wlan0". Weird.

Not as far as I know ... :confused:

[wieman01]

Not as far as I know ... :confused:
Did you check out TKIP (WPA1) as well? Might be an option. If that does not work, you will need to recompile... :-(

[Tex-Twil]

Did you check out TKIP (WPA1) as well? Might be an option.
What do you mean ?

[wieman01]

What do you mean ?
Rather than using WPA2 (AES) you could also configure the router and card to use WPA (TKIP). Sometimes that makes a difference. Some cards & drivers can do WPA (TKIP) but not WPA2.

There is an example for WPA given in the tutorial.

[Tex-Twil]

Rather than using WPA2 (AES) you could also configure the router and card to use WPA (TKIP). Sometimes that makes a difference. Some cards & drivers can do WPA (TKIP) but not WPA2.

There is an example for WPA given in the tutorial.
ok. The router is configured to "'TKIP+AES(WPA/WPA2)". The other option is "WPA2 only" so I presume it is on WPA now.

[wieman01]

ok. The router is configured to "'TKIP+AES(WPA/WPA2)". The other option is "WPA2 only" so I presume it is on WPA now.
That should do. Now you can try this script - assuming that SSID broadcast it turned on:

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid <your_essid>
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <your_hex_key>

[Tex-Twil]

That should do. Now you can try this script - assuming that SSID broadcast it turned on:
Hi,
I think there is something I missed cos I don't have the commands "auto wlan0" , "wpa-ssid" ...

[wieman01]

Hi,
I think there is something I missed cos I don't have the commands "auto wlan0" , "wpa-ssid" ...
Oh oh... Then could you post your stuff instead? Let's see what's going on.

[Tex-Twil]

Oh oh... Then could you post your stuff instead? Let's see what's going on.
My stuff ??

[wieman01]

My stuff ??
This file:

sudo gedit /etc/network/interfaces
There must be something wrong I suppose.

[Tex-Twil]

This file:

There must be something wrong I suppose.
Ah sorry. I was triyng to run those commands in a sheel instead of writing them to the /etc/network/interfaces file. Well here is the result of your script. I commented all other interfaces and let only wlan0 :



root@xx:~# sudo /etc/init.d/networking restart
* Reconfiguring network interfaces... ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - There is already a pid file /var/run/dhclient.wlan0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.


then dhclient keeps on trying to get something but obviously something went wrong before ...

[wieman01]

Please post the contents as well:

sudo gedit /etc/network/interfaces
This does not look promising at the moment.

[Tex-Twil]

Hi,
well the content is what you told me to write inside ;) i.e. :



auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid mySSID
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk myHexKeyWhichIsVeryLong



I commented all the other interfaces except the loopback


auto lo
iface lo inet loopback

#auto eth0
#iface eth0 inet dhcp

The error is the same when I use wpa_supplicant:



ioctl[SIOCSIWENCODEEXT]: Operation not supported

[wieman01]

Hi,
well the content is what you told me to write inside ;) i.e. :



auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid mySSID
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk myHexKeyWhichIsVeryLong



I commented all the other interfaces except the loopback


auto lo
iface lo inet loopback

#auto eth0
#iface eth0 inet dhcp

The error is the same when I use wpa_supplicant:



ioctl[SIOCSIWENCODEEXT]: Operation not supported


Alright then. :-) It now appears that the Windows driver does not support WPA or does not really work well together with "ndiswrapper". Sorry about that... :-(

[Tex-Twil]

Alright then. :-) It now appears that the Windows driver does not support WPA
But why are you talkning about the windows driver ? I'm using the RTL8187 Linux driver version 1.1

[wieman01]

But why are you talkning about the windows driver ? I'm using the RTL8187 Linux driver version 1.1
Sorry, confused it with another thread. Yes, your current driver I mean.

What chipset has it got by the way?

[Tex-Twil]

well .. my card (Alfa Awus036H) has a Realtek chipset ... rtl8187 :)

[wieman01]

well .. my card (Alfa Awus036H) has a Realtek chipset ... rtl8187 :)
Tough luck. I don't think it supports WPA at all... WEP is ok, isn't it?

[Tex-Twil]

Tough luck. I don't think it supports WPA at all... WEP is ok, isn't it?

Yep, WEP is ok. But as I said in a previous post, according to the readme file of the drivers, WPA should be supported. Strange.

[wieman01]

Yep, WEP is ok. But as I said in a previous post, according to the readme file of the drivers, WPA should be supported. Strange.
This might call for "ndiswrapper" perhaps. I could not find anything relating to Reaktek & WPA on Google either.

[mart78]

hello everyone ;)

like most other people in this thread i need some help and advice with my wlan setup.
i have an ibm x30 with a intersil prism II 2.5 wavelan mini-pci card running gutsy that i want to get running with wpa if possible.
i know that the prism 2.5 doesn't support wpa by itself so i flashed it with new primary and station firmware as i read that many people got these cards to work with wpa after the update.

the update went all good, the card is running find in unsecured wlan s but wpa is still giving me a hard time.

at first i tried with the network manager, then with a wpa_supplicant.conf and finally i found the howto on here, but none of it worked so far.

here is the wlan part of my /etc/network/interfaces


auto wlan0
iface wlan0 inet static
address 192.168.0.25
gateway 192.168.0.1
dns-nameservers 192.168.0.1
netmask 255.255.255.0
wpa-driver hostap
wpa-ssid OpenWRT
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk 00csa0d0aw0asd0a9sd09as0 (the scrambled version of my key)

i noticed that iwlist scan reports the Group Cipher to be WEP-40 no matter what i set in my wrt. i saw someone reported this earlier in this thread but i couldn't find any additional info. might this (= gutsy) be the source of my wpa problems?

my main concern is to find out whether there is a chance that i'll succeed getting the prism card to run with wpa or if i'd be better off buying a new one as wlan without wpa is of no use for me. but by now i couldn't even locate the source of my wpa problem so I'd be greatful for any support ....

[wieman01]

hello everyone ;)

like most other people in this thread i need some help and advice with my wlan setup.
i have an ibm x30 with a intersil prism II 2.5 wavelan mini-pci card running gutsy that i want to get running with wpa if possible.
i know that the prism 2.5 doesn't support wpa by itself so i flashed it with new primary and station firmware as i read that many people got these cards to work with wpa after the update.

the update went all good, the card is running find in unsecured wlan s but wpa is still giving me a hard time.

at first i tried with the network manager, then with a wpa_supplicant.conf and finally i found the howto on here, but none of it worked so far.

here is the wlan part of my /etc/network/interfaces

i noticed that iwlist scan reports the Group Cipher to be WEP-40 no matter what i set in my wrt. i saw someone reported this earlier in this thread but i couldn't find any additional info. might this (= gutsy) be the source of my wpa problems?

my main concern is to find out whether there is a chance that i'll succeed getting the prism card to run with wpa or if i'd be better off buying a new one as wlan without wpa is of no use for me. but by now i couldn't even locate the source of my wpa problem so I'd be greatful for any support ....
Hello,

If your card does not recognize your WPA settings as such, there is a pretty good chance that it does not support it. Your interfaces is referred to as "wlan0"... Am I right in that you have installed it using "ndiswrapper"? If so, replacing the most recent Windows driver with the latest one (check the vendor's web site for details) would be a sensible thing to do. As it appears the current driver is flawed. That could be the source of your problems.

Post here if you need further support.

[Marcellus]

Hi -- another stumped newbie here.

With the search I've not succeeded in finding it in the 50+ pages of this topic; If I overlooked it, my sincerest apologies.

I have a practical problem in that wifi is my ONLY connection to the outside world --- I have a 1997 laptop with telephone-port (but no telephone internet in sight) and my wifi is WPA2. So, getting files off the 'net onto the lappy is a struggle.

I've followed the recipe I think -- dhcp because my functioning laptop has that setting --- cat /etc/network/interfaces gives me

auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid radiogauguin
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 4a37-----deleted-password-in-hex------------e728

But the <restart> just gives failures. Is the problem that

cat /etc/modprobe.d/ndiswrapper
cat: /etc/modprobe.d/ndiswrapper: No such file or directory

possibly? Is it uninstalled? How do I install it (add/remove programmes ---> that seems to only talk about a GUI on top of it or am I wrong?)
Once I know what I'm doing I can go find a WEP or passwordless access point (but I have to ask nicely -- no battery in old laptop, so wardriving not an option outside of its illegality). This takes time, so I want to have a reasonable chance of success before I go.

[wieman01]

Hi -- another stumped newbie here.

With the search I've not succeeded in finding it in the 50+ pages of this topic; If I overlooked it, my sincerest apologies.

I have a practical problem in that wifi is my ONLY connection to the outside world --- I have a 1997 laptop with telephone-port (but no telephone internet in sight) and my wifi is WPA2. So, getting files off the 'net onto the lappy is a struggle.

I've followed the recipe I think -- dhcp because my functioning laptop has that setting --- cat /etc/network/interfaces gives me


But the <restart> just gives failures. Is the problem that

possibly? Is it uninstalled? How do I install it (add/remove programmes ---> that seems to only talk about a GUI on top of it or am I wrong?)
Once I know what I'm doing I can go find a WEP or passwordless access point (but I have to ask nicely -- no battery in old laptop, so wardriving not an option outside of its illegality). This takes time, so I want to have a reasonable chance of success before I go.
"wlan0" may not be the right interface name. "wlan0" is usually used by "ndiswrapper" (if you don't know what it is, ignore the comment), hence I doubt it is the right one.

Please do a scan for me and let me know which interfaces (e.g. eth1) return scan results (i.e. networks around you):

sudo iwlist scan
What wireless adapter have you got?

[ebozzz]

I just wanted to say thank you to the OP. As a first time laptop user and also the first time that I have had wireless as a part of my network configuration, I just knew that I would have to use the info inside this thread. Well, I am happy to say that it wasn't needed! I am posting via my WLAN connection now. No configuration was required but I am glad that this resource was available if needed. =D>

My Setup:

Dell Vostro 1500
Intel 3945a/b/g
Ubuntu Studio 7.10 Gutsy Gibbons
Netgear WNR834B RangeMax NEXT Wireless-N Router
WPA2


eth1 Scan completed :
Cell 01 - Address:**:**:**:**:**:**
ESSID:"<hidden>"
Protocol:IEEE 802.11bg
Mode:Master
Channel:6
Frequency:2.437 GHz (Channel 6)
Encryption key: on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=96/100 Signal level=-31 dBm Noise level=-31 dBm
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Extra: Last beacon: 28ms ago

[houms]

Hi -- another stumped newbie here.

With the search I've not succeeded in finding it in the 50+ pages of this topic; If I overlooked it, my sincerest apologies.

I have a practical problem in that wifi is my ONLY connection to the outside world --- I have a 1997 laptop with telephone-port (but no telephone internet in sight) and my wifi is WPA2. So, getting files off the 'net onto the lappy is a struggle.

I've followed the recipe I think -- dhcp because my functioning laptop has that setting --- cat /etc/network/interfaces gives me


But the <restart> just gives failures. Is the problem that

possibly? Is it uninstalled? How do I install it (add/remove programmes ---> that seems to only talk about a GUI on top of it or am I wrong?)
Once I know what I'm doing I can go find a WEP or passwordless access point (but I have to ask nicely -- no battery in old laptop, so wardriving not an option outside of its illegality). This takes time, so I want to have a reasonable chance of success before I go.

The first thing I notice is that you have dhcp instead of static..... are you trying to set a static ip for your laptop ? Based on my experience your line should look like this
auto wlan0 iface
wlan0 inet static
Also is your router set to broadcast its ssid, if not you should also change ap scan to 2

I would try this for you interface....if its wlan0
auto wlan0 iface
wlan0 inet static
address yourip
netmask 255.255.255.0
gateway yourgateway
wireless-essid yourssid
wpa-driver wext
wpa-ssid yourssid
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk yourhexkeyhere

please post your output for these two commands
ifconfig
iwconfig

Also what kind of wireless card are you using?

[mart78]

Hello,

If your card does not recognize your WPA settings as such, there is a pretty good chance that it does not support it. Your interfaces is referred to as "wlan0"... Am I right in that you have installed it using "ndiswrapper"? If so, replacing the most recent Windows driver with the latest one (check the vendor's web site for details) would be a sensible thing to do. As it appears the current driver is flawed. That could be the source of your problems.

Post here if you need further support.

Hi, I'm not using ndiswrapper as the Prism 2.5 card is supported by the hostap driver and this gives me a wlan0 and a wifi0 interface.
Here's the output of iwlist scan (i omitted the non wlan parts):


wifi0 Scan completed :
Cell 01 - Address: 00:16:B8:40:D3:C5
ESSID:"OpenWrtWLAN"
Mode:Master
Frequency:2.412 GHz (Channel 1)
Encryption key:on
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (2) : TKIP WEP-40
Authentication Suites (1) : PSK

wlan0 Scan completed :
Cell 01 - Address: 00:16:B8:40:D3:C5
ESSID:"OpenWrtWLAN"
Mode:Master
Frequency:2.412 GHz (Channel 1)
Encryption key:on
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (2) : TKIP WEP-40
Authentication Suites (1) : PSK

it seems that gutsy still reports the Group Cipher to be always WEP-40 eventhough OpenWRT usually sets the Group Cipher to the same as the configured Pairwise Cipher.

As of now i have read about several other people who got WPA running with the Prism 2.5 Chipset following the instructions on http://linux.junsun.net/intersil-prism/ and i see no reason why it shouldn't work for me besides the wrong Group Cipher mentioned above.
Is there a way I can set the Group Cipher manually or a method how I can track down my problem?

[ToohTaah]

My wifi connection at home is using WEP, but it is WPA2 at my friend's place. I am wondering if there is a command line to connect WPA2 network at my friend's.

Thanks

[mart78]

My wifi connection at home is using WEP, but it is WPA2 at my friend's place. I am wondering if there is a command line to connect WPA2 network at my friend's.

Thanks

I'm relatively new to the whole wlan stuff but I wouldn't know of a simple command line that would do that. Afaik you have to either enter the parameters of your friends network into /etc/network/interfaces or create a wpa_supplicant.conf file which is basically the same as i see it.

Why don't you use the Network Manager? It supports network profiles, so you can configure your box for different networks and just select the one you want to use. Besides my wpa problems mentioned in my last post the Network Manager works really good for me....

[ToohTaah]

The thing is, as I said before, I am usually connect to wep network, and sometimes (once a week) I will connect to wpa2 network. Will putting wpa2 parameters in /etc/network/interfaces or wpa_supplicant.conf have no problem even I start my laptop in my home network (wep)?

[ToohTaah]

I just found that I can use "sudo wpa_supplicant -iath0 -c/etc/wpa_supplicant.conf -Dmadwifi " to connect to wpa2 network, so my problem has been solved...

[wieman01]

I just found that I can use "sudo wpa_supplicant -iath0 -c/etc/wpa_supplicant.conf -Dmadwifi " to connect to wpa2 network, so my problem has been solved...
I recommend Network Manager to all Laptop (mobile) users. But good to hear the mentioned method works for you. Network Manager might make things even simpler.

[afterburnerbg]

I recommend Network Manager to all Laptop (mobile) users. But good to hear the mentioned method works for you. Network Manager might make things even simpler.

I am using Network Manager on Gutsy with a Dell Inspiron 6400. It's with the firmware that comes for the bcm43xx card within the Gutsy distribution from the Restricted Drivers Manager. It works OK @ home (Linksys WRT54gl) but the speed is somewhat low - about 8-10Mbit/s, when the card is working in 24Mbit/s mode. Also, very often when I try to connect to some other network, when I choose the network, the manager tries to connect, but after some time (if the network for exemple only authorises by MAC address, so it does not return a dhcp offer) the network manager causes the bcm43xx module to stop functioning - the light representing the wireless on the laptop stops. Even if I do rmmod bcm43xx and then modprobe bcm43xx there is no difference - I have to restart the whole machine to make it work again. It would be nice if that does not happen. Is this the usual behaviour of network manager, or should I report a bug?

I'd be very grateful if someone answers, cuz I'm somewhat new to Ubuntu and linux.

[wieman01]

I am using Network Manager on Gutsy with a Dell Inspiron 6400. It's with the firmware that comes for the bcm43xx card within the Gutsy distribution from the Restricted Drivers Manager. It works OK @ home (Linksys WRT54gl) but the speed is somewhat low - about 8-10Mbit/s, when the card is working in 24Mbit/s mode. Also, very often when I try to connect to some other network, when I choose the network, the manager tries to connect, but after some time (if the network for exemple only authorises by MAC address, so it does not return a dhcp offer) the network manager causes the bcm43xx module to stop functioning - the light representing the wireless on the laptop stops. Even if I do rmmod bcm43xx and then modprobe bcm43xx there is no difference - I have to restart the whole machine to make it work again. It would be nice if that does not happen. Is this the usual behaviour of network manager, or should I report a bug?

I'd be very grateful if someone answers, cuz I'm somewhat new to Ubuntu and linux.
No, how could that be normal? I would file a bug immediately if I were you.

[afterburnerbg]

No, how could that be normal? I would file a bug immediately if I were you.

When I said normal, I meant that this may be a known bug ;) It doesn't matter, I just submitted a bug report, thanks again! :)

[LordMau]

Some users reported (including myself) that the network has to be restarted every time after startup... Apparently this is a bug.

Here is a workaround that helps restart the network during boot so that one does not have to do it manually after logging on to the system.

Create startup script:

Add this line & save file:

Change permission (executable):

Create symbolic link:

[Note: You may have to choose a boot sequence other than S40.]

Restart...

I have the same issue under 7.10 with an airlink101 / RT61 wifi pci card. In lieu of that script I experimented with adding a pre-up command in the /etc/network/interface file itself as so:


auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid ##########
wpa-ap-scan 1
wpa-proto WPA RSN
wpa-pairwise TKIP CCMP
wpa-group TKIP CCMP
wpa-key-mgmt WPA-PSK
wpa-psk #############3
pre-up dhclient wlan0

Pretty consistent so far, if for any reason though if you manually restart the network it will take a bit longer as the dhcp server seems to go twice before accepting a new lease (I use a static dhcp server).

[wieman01]

@LordMau:

Thanks for letting us know. This has been highlighted by another user as well, so I should really update the guide. Will do so soon, have not had the time so far.

[adbrown]

Following this guide is the only way I have managed to get WPA2 working with static ip. However I seem to have hampered my laptop so that it only works properly when the network is turned on. With it turned off the network card seems to be scanning all the time for the non existent network. Going through all of the posts I have seen a suggestion that I should try configuring using network-manager. Does anyone have a good guide for this - I have tried the wiki entry (https://help.ubuntu.com/community/WifiDocs/WPAHowTo?highlight=%28wpa%29) with little success.

ta

a

[wieman01]

Following this guide is the only way I have managed to get WPA2 working with static ip. However I seem to have hampered my laptop so that it only works properly when the network is turned on. With it turned off the network card seems to be scanning all the time for the non existent network. Going through all of the posts I have seen a suggestion that I should try configuring using network-manager. Does anyone have a good guide for this - I have tried the wiki entry (https://help.ubuntu.com/community/WifiDocs/WPAHowTo?highlight=%28wpa%29) with little success.

ta

a
No idea if Network Manager supports the use of static IP yet. I seriously doubt it.

WICD might be an option for you:

http://wicd.sourceforge.net/

[jcsaintpo]

I try installing wpa on my laptop!
i use xubuntu 6.06.1 because only 64ram

i tried the gedit commands, but it didn't work!
is there an other way i must handle?

[wieman01]

I try installing wpa on my laptop!
i use xubuntu 6.06.1 because only 64ram

i tried the gedit commands, but it didn't work!
is there an other way i must handle?
Good question... you can try...

sudo nano /etc/network/interfaces
...instead. "gedit" is Gnome's text editor. Since you are running Xubuntu, it is not available. Sorry for not having mentioned that.

[adbrown]

No idea if Network Manager supports the use of static IP yet. I seriously doubt it.

WICD might be an option for you:

http://wicd.sourceforge.net/

Thanks very much, WICD did work for me - it enabled me to remove the line
auto eth1
from my interfaces file and I can now use WICD to switch the network on and off - so can other users without the root password

[jcsaintpo]

Good question... you can try...

...instead. "gedit" is Gnome's text editor. Since you are running Xubuntu, it is not available. Sorry for not having mentioned that.

It worked!

But i used a simpler way to programme wpa (found here (http://forum.ubuntu-nl.org/message/123169#p123169))




iface ra0 inet dhcp
pre-up ifconfig ra0 up
pre-up ifconfig ra0 down
pre-up ifconfig ra0 up
pre-up ifconfig ra0 down
pre-up iwconfig ra0 essid “Naam_van_je_netwerk�
pre-up iwconfig ra0 mode Managed
pre-up iwpriv ra0 set AuthMode=WPAPSK
pre-up iwpriv ra0 set EncrypType=TKIP
pre-up iwpriv ra0 set WPAPSK=� Wachtwoord_van_je_netwerk�
pre-up ifconfig ra0 up
auto ra0




after restarting i was immediately online

[wieman01]

It worked!

But i used a simpler way to programme wpa (found here (http://forum.ubuntu-nl.org/message/123169#p123169))




iface ra0 inet dhcp
pre-up ifconfig ra0 up
pre-up ifconfig ra0 down
pre-up ifconfig ra0 up
pre-up ifconfig ra0 down
pre-up iwconfig ra0 essid “Naam_van_je_netwerk�
pre-up iwconfig ra0 mode Managed
pre-up iwpriv ra0 set AuthMode=WPAPSK
pre-up iwpriv ra0 set EncrypType=TKIP
pre-up iwpriv ra0 set WPAPSK=� Wachtwoord_van_je_netwerk�
pre-up ifconfig ra0 up
auto ra0




after restarting i was immediately online
You have a Ralink wireless adapter. My approach wouldn't work for you anyway...

[jimisdead]

I have an old laptop that I use as a file/printer/everything server, that is currently connected via ethernet by a large ugly cable trailled through my apartment.

I want to change it to use a spare netgear wireless usb card, which after updating to gutsy I now see is supported - and is automatically shown as wlan0 when plugged in.

without further ado here is my /etc/network/interfaces


# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
address 192.168.2.2
netmask 255.255.255.0
network 192.168.2.0
broadcast 192.168.2.255
dns-nameservers 192.168.2.1

gateway 192.168.2.1

auto wlan0
iface wlan0 inet static
address 192.168.2.10
gateway 192.168.2.1
dns-nameservers 192.168.2.1
netmask 255.255.255.0
wpa-driver wext
wpa-ssid MYNETWORKSSID
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk MYNETWORKKEYKEYKEY




if I boot this this config I can ping and ssh into either 192.168.2.2 or 192.168.2.10 and everything is great. If I then unplug the ethernet cable I can not ping 192.168.2.2 anymore (obviously), but nor can I ping 192.168.2.10 - and I can't get any network connection from the serverside either..

... Does anyone have any idea what is going on?


*this was all down while the ethernet cable was still plugged in*
*SSIDNAME* is my SSID

user@server:~$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth0
0.0.0.0 192.168.2.1 0.0.0.0 UG 100 0 0 wlan0
0.0.0.0 192.168.2.1 0.0.0.0 UG 100 0 0 eth0
user@server:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

user@server:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:02:A5:B5:76:CA
inet addr:192.168.2.2 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::202:a5ff:feb5:76ca/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:331 errors:0 dropped:0 overruns:0 frame:0
TX packets:424 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:30499 (29.7 KB) TX bytes:65646 (64.1 KB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

wlan0 Link encap:Ethernet HWaddr 00:0F:B5:90:B6:E6
inet addr:192.168.2.10 Bcast:192.168.2.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

wmaster0 Link encap:UNSPEC HWaddr 00-0F-B5-90-B6-E6-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

user@server:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wmaster0 Interface doesn't support scanning.

wlan0 No scan results

user@server:~$ iwlist scanning
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wmaster0 Interface doesn't support scanning.

wlan0 No scan results

user@server:~$ sudo iwlist wlan0 scanning
[sudo] password for user:
wlan0 Scan completed :
Cell 01 - Address: 00:1C:4A:D0:F2:8A
ESSID:"FRITZ!Box Fon WLAN 7141"
Mode:Master
Channel:6
Frequency:2.437 GHz
Signal level=25/100
Encryption key:on
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : PSK
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=000001a7444d8206
Cell 02 - Address: 00:12:BF:5F:15:B3
ESSID:"SSIDNAME"
Mode:Master
Channel:11
Frequency:2.462 GHz
Signal level=57/100
Encryption key:on
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (2) : WEP-40 TKIP
Authentication Suites (1) : PSK
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Preauthentication Supported
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:tsf=000000302c561427

user@server:/etc$ more resolv.conf
nameserver 192.168.2.1

[wieman01]

@jimisdead:

What happens when you reboot with the Ethernet cable unplugged? Please do so and post the results of (after you have rebooted):

sudo ifdown -v wlan0

sudo ifup -v wlan0

[jimisdead]

@jimisdead:

What happens when you reboot with the Ethernet cable unplugged? Please do so and post the results of (after you have rebooted):

After reboot it still has not network access.

ifdown wlan0 -v (i had to redirect stdout and stderr since it had no net access)


ryan@orwell:~$ more wlandown
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan0.pid
Stopped /sbin/wpa_supplicant (pid 5273).
ryan@orwell:~$ more wlandownerr
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/wpasupplicant
route del default gw 192.168.2.1 metric 100 wlan0
ifconfig wlan0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant

ifup wlan0 -v

ryan@orwell:~$ more wlanup
OK
ryan@orwell:~$ more wlanuperr
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 -
ifconfig wlan0 192.168.2.10 netmask 255.255.255.0 up
route add default gw 192.168.2.1 metric 100 wlan0
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/openssh-server
run-parts: executing /etc/network/if-up.d/wpasupplicant

[dannytherocker]

It worked!

But i used a simpler way to programme wpa (found here (http://forum.ubuntu-nl.org/message/123169#p123169))




iface ra0 inet dhcp
pre-up iwconfig ra0 essid “Naam_van_je_netwerk�
pre-up iwconfig ra0 mode Managed
pre-up iwpriv ra0 set AuthMode=WPAPSK
pre-up iwpriv ra0 set EncrypType=TKIP
pre-up iwpriv ra0 set WPAPSK=� Wachtwoord_van_je_netwerk�
pre-up ifconfig ra0 up
auto ra0




after restarting i was immediately online


Does this approach work on Gutsy ??? It does on Feisty....yesterady I had to get back to feisty after an upgrading because wless did not work and I forgot to try this approach....

[wieman01]

@jimisdead:


ioctl[SIOCSIWAUTH]: Operation not supported
You card does not seem to support WPA2. Please try WPA1 (WPA, TKIP) instead. That might do.

[wieman01]

Does this approach work on Gutsy ??? It does on Feisty....yesterady I had to get back to feisty after an upgrading because wless did not work and I forgot to try this approach....
It should as far as I know. But frankly I never got WPA to work using this method.

[dannytherocker]

It should as far as I know. But frankly I never got WPA to work using this method.


I can guarantee WPA does work using the approach above....I'm only afraid to install Gutsy again without having wless working....

[jimisdead]

@jimisdead:


You card does not seem to support WPA2. Please try WPA1 (WPA, TKIP) instead. That might do.

thanks for the reply.

but I get the same deal as before. :(

[wieman01]

thanks for the reply.

but I get the same deal as before. :(
Can you tell me more about your hardware & driver? Perhaps the driver is the culprit.

[jimisdead]

It's a netgear WG111 (http://www.netgear.com/Products/Adapters/GWirelessAdapters/WG111.aspx) 54Mbps USB dongle. plugged into an old compaq evo laptop running fully updated gutsy.

I've tried the wext and the madwifi driver, neither has worked.

[wieman01]

It's a netgear WG111 (http://www.netgear.com/Products/Adapters/GWirelessAdapters/WG111.aspx) 54Mbps USB dongle. plugged into an old compaq evo laptop running fully updated gutsy.

I've tried the wext and the madwifi driver, neither has worked.
I guess you will have to do some googling on the web and try to find out if others have been able to set it up using WPA. I'll try to find something useful as well.

[AZzKikR]

Recently upgraded to Gutsy. I have a Linksys card, RT2500 chipset. My previous /etc/network/interfaces could not be used to authenticate myself using this type of scheme:

iface ra0 inet dhcp
pre-up iwconfig ra0 essid "networkname"
pre-up iwconfig ra0 mode Managed
pre-up iwpriv ra0 set AuthMode=WPAPSK
pre-up iwpriv ra0 set EncrypType=TKIP
pre-up iwpriv ra0 set WPAPSK="unencryptedpw"
pre-up ifconfig ra0 up
auto ra0

I tried using Ubuntu's network manager which now has a choice to pick WPA1/2 encryption. After doing that, it wrote something different to the /etc/network/interfaces file. It uses the 'wext' driver for instance, and it writes an encrypted WPA password to the file.

After executing `sudo ifup ra0`, I got a few errors ([SIOCSAUTH]: Operation not supported or something like that), but the internet connection was established. After adding `auto ra0` to the file, it even fails to establish a connection during startup. And I think it is because of those errors.

I am going to reinstall Gutsy tonight, perhaps something else was corrupted or the like.

Anyone else had the same thing? I am sorry I cannot post any real samples of the files yet (at work at this moment).

[oobuntu]

Hi,

Just thought it might be helpful to post my experience with setting this up.

I've got an Acer Aspire 5630 laptop and have managed to get the wireless working to my d-com router using WPA2 with the following configuration:


root@our-laptop:/etc/network# cat interfaces
auto lo
iface lo inet loopback

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-ssid <your-ssid>
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <get this using the wpa_passphrase utility>

#auto eth0

Then after restarting the networking this worked great. Thanks for a great OS and a great forum.

[wieman01]

Hi,

Just thought it might be helpful to post my experience with setting this up.

I've got an Acer Aspire 5630 laptop and have managed to get the wireless working to my d-com router using WPA2 with the following configuration:


root@our-laptop:/etc/network# cat interfaces
auto lo
iface lo inet loopback

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-ssid <your-ssid>
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <get this using the wpa_passphrase utility>

#auto eth0

Then after restarting the networking this worked great. Thanks for a great OS and a great forum.
TKIP is WPA1 actually. Try AES instead which is the latest WPA(2) standard encryption. But I don't know if your adapter supports it.

[ericderace]

Hi,

I am trying to connect to a University network which is WPA, PEAP, TKIP and PAP/MSCHAPv2. I've tried networkmanager, I've tried editing /etc/network/interfaces... Does not seem to work.

What I believe happens is that it does not authenticate my username and password. It looks like it connects, gives me an IP, the wireless Icon on the laptop keeps flashing, then it disconnects.

Is there any log file or any way to check for authentication problems ?

Thanks,

Eric

[wieman01]

Hi,

I am trying to connect to a University network which is WPA, PEAP, TKIP and PAP/MSCHAPv2. I've tried networkmanager, I've tried editing /etc/network/interfaces... Does not seem to work.

What I believe happens is that it does not authenticate my username and password. It looks like it connects, gives me an IP, the wireless Icon on the laptop keeps flashing, then it disconnects.

Is there any log file or any way to check for authentication problems ?

Thanks,

Eric
Yes, you could do:

sudo ifdown -v <your_interface>

sudo ifup -v <your_interface>

[ericderace]

That doesn't print any information about authentication.

[AZzKikR]

Alright, I installed Gutsy. Everything is working fine I guess, but internet is working flaky.

I have a Linksys PCI card, with Ralink RT2500 chipset. Using the Network Setup utility (System -> Administration -> Network) I was able to get a network connection. WPA1/TKIP. Browsing works fine.

This is my /etc/network/interfaces:

auto lo
iface lo inet loopback


iface wlan0 inet static
address 192.168.1.7
netmask 255.255.255.0
gateway 192.168.1.1
wpa-psk 2c...<my WPA key>... c52
wpa-driver wext
wpa-key-mgmt WPA-PSK
wpa-proto WPA
wpa-ssid porrus

auto wlan0


What I notice is:

I no longer have ra0 as interface, but wlan0
It computes a WPA passphrase. Before I had to just put it in plaintext here
It uses wext as a driver here


So what am I complaining about? Well, when I do a manual ifdown/ifup, this is what I see:


krpors@krpors-desktop:~$ sudo ifdown wlan0
[sudo] password for krpors:
krpors@krpors-desktop:~$ sudo ifup wlan0
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - krpors@krpors-desktop:~$

Connection is working nicely though :S At booting the internet connection won't be established and I think this is causing it.

Any ideas? I'm puzzled.

[MartenH]

HI,

I followed this guide to the letter (WPA TKIP-PSK variant) on my linksys WPC54g v2 card. The result? I get several "operation not supported" errors cast by wext and then my computer freezes completely.

Any suggestion? What kind of information/logs should i supply?

//MartenH

[wieman01]

Alright, I installed Gutsy. Everything is working fine I guess, but internet is working flaky.

I have a Linksys PCI card, with Ralink RT2500 chipset. Using the Network Setup utility (System -> Administration -> Network) I was able to get a network connection. WPA1/TKIP. Browsing works fine.

This is my /etc/network/interfaces:

auto lo
iface lo inet loopback


iface wlan0 inet static
address 192.168.1.7
netmask 255.255.255.0
gateway 192.168.1.1
wpa-psk 2c...<my WPA key>... c52
wpa-driver wext
wpa-key-mgmt WPA-PSK
wpa-proto WPA
wpa-ssid porrus

auto wlan0


What I notice is:

I no longer have ra0 as interface, but wlan0
It computes a WPA passphrase. Before I had to just put it in plaintext here
It uses wext as a driver here


So what am I complaining about? Well, when I do a manual ifdown/ifup, this is what I see:


krpors@krpors-desktop:~$ sudo ifdown wlan0
[sudo] password for krpors:
krpors@krpors-desktop:~$ sudo ifup wlan0
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - krpors@krpors-desktop:~$

Connection is working nicely though :S At booting the internet connection won't be established and I think this is causing it.

Any ideas? I'm puzzled.
Actually I believe that something is definitely wrong. The Ralink apapter should not work at all using this approach (as highlighted in the tutorial).

When you restart the network (putting the error messages aside for now), is then that you get a working (WPA) connection?

You can get a working connection upon restart if you follow the instructions given in post #2.

[wieman01]

HI,

I followed this guide to the letter (WPA TKIP-PSK variant) on my linksys WPC54g v2 card. The result? I get several "operation not supported" errors cast by wext and then my computer freezes completely.

Any suggestion? What kind of information/logs should i supply?

//MartenH
Well, what chipset has your card got? Broadcom?

That error message usually means that your card does not support WPA i.e. "wext". You could - of course - try other WPA-drivers as well.

You could post this:

sudo ifdown -v <your_interface>

sudo ifup -v <your_interface>
Please also the contents of:

sudo gedit /etc/network/interfaces

[McDuff]

actually, ralink drivers should work in gutsy, since after acception of the new wireless stack in linux, the drivers' maintainers worked hard to get the rt2x00 to work with it. new driver is included in gutsy and works very well for me (wpa driver being wext)
cheers
georg

[wieman01]

actually, ralink drivers should work in gutsy, since after acception of the new wireless stack in linux, the drivers' maintainers worked hard to get the rt2x00 to work with it. new driver is included in gutsy and works very well for me (wpa driver being wext)
cheers
georg
First time I hear of it. Thought the current version in Gutsy is broken. Lots of other forum members can confirm the issue.

Good to hear they are making progress.

[Chuckels550]

This how-to thread didn't just set out how to set up wireless security, it showed how to set up a wireless connection. Can the name of the permanent thread be changed from HOWTO: Wireless Security - WPA1, WPA2, LEAP, etc. to HOW TO: Set UP Wireless Connections?

Looking at the list of people having problems with Network Manager - an application that should have been dropped from the distro - your what I regard as essential HOWTO might cut down on the pounding the forum is taking if people realized that it was not just about secure connections.

And by the way thanks for the HOWTO

[monomaniacpat]

Hello again wieman.

I foolishly decided to upgrade all my packages last night and it has resulted in no more wireless connections for me.

The problem appears to be that the ndiswrapper module is not inserted at boot. It's not listed with lsmod, anyway.

Therefore I have been trying to modprobe ndiswrapper. The first time I tried I got "invalid argument". I searched google for this and someone said they'd got it to work by installing ndiswrapper-common and ndiswrapper-utils. I couldn't find -common in my repos, but I managed to install -utils.

With -utils installed I now get:


Setting up ndiswrapper-utils (1.8-0ubuntu2) ...

patrick@inspiron-8200:~$ sudo modprobe ndiswrapper
Segmentation fault
patrick@inspiron-8200:~$


Do you have any idea what I can do to get it working again?

Thanks for your help prior to today and any adivce - I had it working for several months!

mono.

EDIT: I just looked at lsmod again and ndiswrapper is now listed. Presumably because of the previous terminal command I mentioned where I got the segmentation fault... Still no wireless devices, though.

[monomaniacpat]

EDIT: Don't worry yourself for now. I've just tried using ndiswrapper on the liveCD and it seems to work, so I'll probably just use a fresh install.

Just found this in /var/log/messages:


Oct 27 10:04:45 localhost kernel: [17179611.860000] apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
Oct 27 10:04:45 localhost kernel: [17179611.860000] apm: overridden by ACPI.
Oct 27 10:04:45 localhost loadndisdriver: loadndisdriver: main(544): version 1.9 doesn't match driver version 1.7
Oct 27 10:04:45 localhost kernel: [17179611.980000] ndiswrapper version 1.8 loaded (preempt=yes,smp=no)
Oct 27 10:04:45 localhost loadndisdriver: loadndisdriver: main(544): version 1.9 doesn't match driver version 1.7
Oct 27 10:04:45 localhost kernel: [17179612.016000] ndiswrapper version 1.8 loaded (preempt=yes,smp=no)
Oct 27 10:04:45 localhost loadndisdriver: loadndisdriver: main(544): version 1.9 doesn't match driver version 1.7
Oct 27 10:04:45 localhost kernel: [17179612.052000] ndiswrapper version 1.8 loaded (preempt=yes,smp=no)
Oct 27 10:04:46 localhost kernel: [17179612.380000] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).

[Startacus]

Ok, I am going good on this until the very end. When I run the "wpa_passprhase <myessid> <passphrase>" command I get.


bash: <My ssid>: event not found


Is there something you have to do first for it to work?

I am trying to connect to my router which is WPA, TKIP, SSID No broadcast, DHCP.

Is there anything I'm missing? Thanks.

[monomaniacpat]

Please ignore my earlier posts. I have now reformatted and installed a fresh Gutsy Gibbon. On wireless now! :)

So that's the Linksys WPC11 V.4 working on Gutsy with Ndiswrapper and latest windows NET8180.inf driver. WPA-PSK. :guitar:

[wieman01]

This how-to thread didn't just set out how to set up wireless security, it showed how to set up a wireless connection. Can the name of the permanent thread be changed from HOWTO: Wireless Security - WPA1, WPA2, LEAP, etc. to HOW TO: Set UP Wireless Connections?

Looking at the list of people having problems with Network Manager - an application that should have been dropped from the distro - your what I regard as essential HOWTO might cut down on the pounding the forum is taking if people realized that it was not just about secure connections.

And by the way thanks for the HOWTO
It is about wireless security, nothing else. Or isn't it? I don't really explain how you set up your network & wireless adapter, just how you add security. That's it.

[wieman01]

Ok, I am going good on this until the very end. When I run the "wpa_passprhase <myessid> <passphrase>" command I get.




Is there something you have to do first for it to work?

I am trying to connect to my router which is WPA, TKIP, SSID No broadcast, DHCP.

Is there anything I'm missing? Thanks.
Well, what is your ESSID (wireless network name)? The replace <myessid> with that and it ought to work. :-)

E.g.:

wpa_passprhase default 123456

[wieman01]

Please ignore my earlier posts. I have now reformatted and installed a fresh Gutsy Gibbon. On wireless now! :)

So that's the Linksys WPC11 V.4 working on Gutsy with Ndiswrapper and latest windows NET8180.inf driver. WPA-PSK. :guitar:
Sorry for the late reply. Glad you got it working. Gutsy's Ralink drivers did not work for you I reckon.

[Startacus]

Well, what is your ESSID (wireless network name)? The replace <myessid> with that and it ought to work. :-)

E.g.:

I do, I put my networks SSID instead of <myessid> and I get that error.

If I run the command "iwlist scan" The result under wlan1 is "No scan results."


If I set the Wireless Connection to "roaming" and then go to "Connect to other network" and enter in my information there. The icon switches to bars to show the signal strength but they are all empty and the "wpa_passphrase" command still doesn't work. I am really lost now.

I know the network works because I am typing this message on my XP laptop connected to the same network.

[RandomUsr]

I have two rather weighted questions. First this how-to answered about as many questions as it inpired from myself.

Right now I'm using the Intel iwl4965 on my home network with WPA2 and it's shaky at best. Also I have to re-enter the PSK and restart the driver evey time I start the computer. Is there a way around this?
Keep in mind that I installed no additional software for my network card to work. Using GUTSY

Further, I want to use LEAP w/ 802.11 WEP.

Essentially I want to continue using WPA2 on my home network, and I want to enter Credentials (LEAP) everytime I log on at work using WEP802.11

I'm guessing this might be a hassle have two networks and switching between them?

What options do i have, and which do you recommend?
Looking forward to your thoughts.

[wieman01]

Right now I'm using the Intel iwl4965 on my home network with WPA2 and it's shaky at best. Also I have to re-enter the PSK and restart the driver evey time I start the computer. Is there a way around this?

See post #2.

Further, I want to use LEAP w/ 802.11
WEP.

I'm guessing this might be a hassle have two networks and switching between them?

Best option for you is to use Network Manager or WICD (google for it) which both support LEAP and network profiles (for switching between networks). It should work for you as well.

[RandomUsr]

So, would this only entail installing on of those programs? and Would I need to compile from source or would synaptic do the job?

[wieman01]

Network Manager is part of the default installation.

Instructions for WICD can be found here:

http://wicd.sourceforge.net/download.php

You don't have to compile from source of course.

[RandomUsr]

Any recomendations as far as the shaky behaviour?

PS, How do I start Network manager if it's already installed...

I'm fairly certain that it's not that silly thing running up in the corner that has no support for wireless profiles.

[wieman01]

Any recomendations as far as the shaky behaviour?
Could be due to a number of things. I generally recommend that you adjust & tune the physical settings of your wireless networks. This has worked for me on a number of occasions while I was facing random dropouts. Start off with the default bacon interval and reduce the value. I cannot tell what the culprit is in your case, but you get my point...

[RandomUsr]

Come to think of it I think I know what's going on but I won't be able to test it until a bit later.


Could be due to a number of things. I generally recommend that you adjust & tune the physical settings of your wireless networks. This has worked for me on a number of occasions while I was facing random dropouts. Start off with the default bacon interval and reduce the value. I cannot tell what the culprit is in your case, but you get my point...



Default Bacon? I've always liked a good BLT

[wieman01]

Come to think of it I think I know what's going on but I won't be able to test it until a bit later.

Default Bacon? I've always liked a good BLT
With a bit of Chili & Pepper, definitely!

Beacon interval of course. Let us know what your findings are.

[RandomUsr]

Re: HOWTO: Wireless Security - WPA1, WPA2, LEAP, etc.

--------------------------------------------------------------------------------

Quote:
Originally Posted by wieman01
Well, what is your ESSID (wireless network name)? The replace <myessid> with that and it ought to work.

E.g.:

I do, I put my networks SSID instead of <myessid> and I get that error.

If I run the command "iwlist scan" The result under wlan1 is "No scan results."


If I set the Wireless Connection to "roaming" and then go to "Connect to other network" and enter in my information there. The icon switches to bars to show the signal strength but they are all empty and the "wpa_passphrase" command still doesn't work. I am really lost now.

I know the network works because I am typing this message on my XP laptop connected to the same network.

Startacus, what are the chances you have an AN Intel wi-fi card?

[Startacus]

Startacus, what are the chances you have an AN Intel wi-fi card?

Not very good I'm afraid. I have the Belkin 54g Wireless USB. I think it's F5D7050.

[RandomUsr]

wieman01,

I´m still working on my wireless issues/connectivity etc. I would like some further input if possible.

I want to use the knetwork manager (front end) for gnome, which synaptic states will work with gnome. The issue is that knetwork manager isn´t pulling any data from network manager itself. How can one make knetwork manager play well with gnome and networkmanager so they communicate to one another?


This would be extremely helpful

[helpdeskdan]

GAH! I don't get it! What did I do WRONG? I spent hours trying to get it to work, followed the instruction exactly. Finally, in desperation, I commented out everything and put in:

auto eth0
iface eth0 inet dhcp
wpa-conf /etc/wpa_supplicant.conf

with the simplest wpa_supplicant you can imagine - just an ssid and a psk. Worked great! I just don't get it, I didn't even specify a driver!

Any ideas?

I guess if you are having problems, I suggest trying it.

I DID have to create a init.d script (see second post). I did NOT restart networking - too slow. I just did a ifdown etho and an ifup eth0. Works great. Also, use sysvconfig to enable it - that way you don't have to guess the boot sequence. (Wonderful little obscure tool)

[saltydog]

I have an ipw2100 Intel card, and I can't get connected to a WPA-PSK (FKID) wireless router. I have tried with NetworkManager and Wicd either, no way to get thru. The card is perfectly working on Windows, but on Gutsy I have a lot of messages in log, such as this:
"ipw2100: Fatal interrupt. Scheduling firmware restart."

Any suggestion?

[helpdeskdan]

Well, yeah, you and half the internet - try googling it. It's a bug, apparently - you'll have to wait till it's fixed or see if somebody has found a work around.

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/24776

[saltydog]

Well, yeah, you and half the internet - try googling it. It's a bug, apparently - you'll have to wait till it's fixed or see if somebody has found a work around.

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/24776

I have seen the bug before posting here, but as it is there since october 2005 I gave up with the hope to have it fixed. I'm just looking for a workaround, if any...

This is sad. My Windows collegues are laughing. :-(

[wieman01]

GAH! I don't get it! What did I do WRONG? I spent hours trying to get it to work, followed the instruction exactly. Finally, in desperation, I commented out everything and put in:

auto eth0
iface eth0 inet dhcp
wpa-conf /etc/wpa_supplicant.conf

with the simplest wpa_supplicant you can imagine - just an ssid and a psk. Worked great! I just don't get it, I didn't even specify a driver!

Any ideas?

I guess if you are having problems, I suggest trying it.

I DID have to create a init.d script (see second post). I did NOT restart networking - too slow. I just did a ifdown etho and an ifup eth0. Works great. Also, use sysvconfig to enable it - that way you don't have to guess the boot sequence. (Wonderful little obscure tool)
What hardware have you got? Does it support WPA at all?

What does a scan yield:

sudo iwlist scan

[wieman01]

I have an ipw2100 Intel card, and I can't get connected to a WPA-PSK (FKID) wireless router. I have tried with NetworkManager and Wicd either, no way to get thru. The card is perfectly working on Windows, but on Gutsy I have a lot of messages in log, such as this:
"ipw2100: Fatal interrupt. Scheduling firmware restart."

Any suggestion?
Mmm... really beats me. What version of Ubuntu are you on? It used to work with the IPW2100.

[wieman01]

I have seen the bug before posting here, but as it is there since october 2005 I gave up with the hope to have it fixed. I'm just looking for a workaround, if any...

This is sad. My Windows collegues are laughing. :-(
What version of Ubuntu are you on?

Does your card recognize the WPA network as such? Do:

sudo iwlist scan

[saltydog]

Mmm... really beats me. What version of Ubuntu are you on? It used to work with the IPW2100.

7.10 Gutsy.

uname -a
Linux Plato 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux


I have also made a complete fresh system reinstall.

[saltydog]

What version of Ubuntu are you on?

Does your card recognize the WPA network as such? Do:

The card recognizes the WPA network, iwlist scan is fine, but it will never get associated. Doesn't get the ip from the dhcp server.

On another WPA-PSK (FKIP) network I can happily get connected, but after booting the laptop I am experiencing this other bug (https://bugs.edge.launchpad.net/ubuntu/+source/wpasupplicant/+bug/160457).

[wieman01]

Could you also post:

sudo gedit /etc/network/interfaces
And this one:

sudo ifdown -v <wireless_interface>

sudo ifup -v <wireless_interface>
Need to go for now. Will check later again.

[saltydog]

Need to go for now. Will check later again.


Strange things happen...


cat /etc/network/interfaces

auto lo
iface lo inet loopback


sudo ifdown -v eth1
ifdown: interface eth1 not configured


sudo ifup -v eth1
Ignoring unknown interface eth1=eth1.

But this is my iwconfig (at the moment the wireless is connected to another network):

iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

irda0 no wireless extensions.

eth1 IEEE 802.11b ESSID:"Saltydog_FM" Nickname:"ipw2100"
Mode:Managed Frequency:2.462 GHz Access Point: 00:14:C1:19:3E:54
Bit Rate=11 Mb/s Tx-Power:16 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=100/100 Signal level=-43 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:1 Missed beacon:0

[helpdeskdan]

Are you using the latest firmware? I've heard that helps.
http://ipw2100.sourceforge.net/

[saltydog]

Are you using the latest firmware? I've heard that helps.
http://ipw2100.sourceforge.net/

I am using Gutsy's firmware ipw2100-1.3-p.fw

[wieman01]

Strange things happen...


cat /etc/network/interfaces

auto lo
iface lo inet loopback


sudo ifdown -v eth1
ifdown: interface eth1 not configured


sudo ifup -v eth1
Ignoring unknown interface eth1=eth1.

But this is my iwconfig (at the moment the wireless is connected to another network):

iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

irda0 no wireless extensions.

eth1 IEEE 802.11b ESSID:"Saltydog_FM" Nickname:"ipw2100"
Mode:Managed Frequency:2.462 GHz Access Point: 00:14:C1:19:3E:54
Bit Rate=11 Mb/s Tx-Power:16 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=100/100 Signal level=-43 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:1 Missed beacon:0
Let's see... If you add these to lines to "/etc/network/interfaces" and reboot, are you able to connect?

auto eth1
iface eth1 inet dhcp

I know that NM requires you to remove your interface information, but somehow sometimes it helps to add it. An unpleasant experience I made recently.

So what happens after a restart?

[saltydog]

Let's see... If you add these to lines to "/etc/network/interfaces" and reboot, are you able to connect?

I know that NM requires you to remove your interface information, but somehow sometimes it helps to add it. An unpleasant experience I made recently.

So what happens after a restart?

Mmmh... nothing good happens. NM gets angry, and after a networking restart this is the output:

Listening on LPF/eth1/00:0c:f1:2b:cc:b9
Sending on LPF/eth1/00:0c:f1:2b:cc:b9
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 15

[wieman01]

Odd... Could you do another network restart please? After having added those 2 lines:

sudo ifdown -v eth1

sudo ifup -v eth1
And another scan:

sudo iwlist scan

[saltydog]

Odd... Could you do another network restart please? After having added those 2 lines:
And another scan:

Here it is. After having added thos two lines:

sudo ifdown -v eth1

Configuring interface eth1=eth1 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.eth1.pid -lf /var/lib/dhcp3/dhclient.eth1.leases eth1
There is already a pid file /var/run/dhclient.eth1.pid with pid 5350
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:0c:f1:2b:cc:b9
Sending on LPF/eth1/00:0c:f1:2b:cc:b9
Sending on Socket/fallback
DHCPRELEASE on eth1 to 192.168.1.1 port 67
ifconfig eth1 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant




sudo ifup -v eth1
Configuring interface eth1=eth1 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant

dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.eth1.pid -lf /var/lib/dhcp3/dhclient.eth1.leases eth1
There is already a pid file /var/run/dhclient.eth1.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:0c:f1:2b:cc:b9
Sending on LPF/eth1/00:0c:f1:2b:cc:b9
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant



sudo iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:14:C1:19:3E:54
ESSID:"Saltydog_FM"
Protocol:IEEE 802.11bg
Mode:Master
Channel:11
Frequency:2.462 GHz (Channel 11)
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality:95 Signal level:0 Noise level:0
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (2) : TKIP WEP-40
Authentication Suites (1) : PSK
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-40
Pairwise Ciphers (2) : TKIP WEP-40
Authentication Suites (1) : PSK
Extra: Last beacon: 3932ms ago

irda0 Interface doesn't support scanning.



iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

eth1 unassociated ESSID:off/any Nickname:"ipw2100"
Mode:Managed Channel=0 Access Point: Not-Associated
Bit Rate:0 kb/s Tx-Power:16 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

irda0 no wireless extensions.

[wieman01]

@Saltydog:

I believe your card is fine. I cannot explain why NM does not pick it up i.e. is able to connect to your WPA network, however, have you tried this tutorial yet?

You could remove NM entirely and configure your WPA network manually. Use WPA-TKIP and make sure the router is set to WPA-TKIP as well (not WPA2). Then restart the network as described above (verbose) and post the results along with "/etc/network/interfaces".

I think that's the only way we could get it up & running right now...

[saltydog]

@Saltydog:

I believe your card is fine. I cannot explain why NM does not pick it up i.e. is able to connect to your WPA network, however, have you tried this tutorial yet?

..

I didn't try yet without NM as I am often moving with my lap from one location to others and I need several different configurations active. 2 or 3 of my locations are WEP, and other 2 are WPA-PSK. I don't know how to handle multiple locations without NM.

[wieman01]

I didn't try yet without NM as I am often moving with my lap from one location to others and I need several different configurations active. 2 or 3 of my locations are WEP, and other 2 are WPA-PSK. I don't know how to handle multiple locations without NM.
I see... then that's not an option either.

What are the exact symptoms when you say NM refuses to connect? And what are the exact router settings? WPA or WPA2?

Please make sure the router is set to WPA(1) and TKIP, then try to connect once again. Please whatever findings you have here.

Another tool I can recommend is Wifi-Radar which is also in the repositories.

[saltydog]

The most critical access point is the one I have at work. It is a LinkSys (don't remember the model) and it is set to WPA2-PSK and TKIP. NM tries to connect and then ask for password. I enter the right password then NM's icon starts looking for connection, then it asks again for password and so on.

In that case I have several of this lines in dmesg:
ipw2100: Fatal interrupt. Scheduling firmware restart

[wieman01]

WPA2-TKIP is a rather unusual setting, because TKIP is actually part of the WPA1 suite, although WPA2 is downwards compatible. That might explain why NM does not like it.

That said it could also relate to a bug as mentioned earlier. I found this as well:

http://bughost.org/bugzilla/show_bug.cgi?id=329

Have you been able to connect with any WPA network yet? Or is this the first attempt?

[saltydog]

Fisrt of all, thank you for your great patience!


/show_bug.cgi?id=329[/URL]

Have you been able to connect with any WPA network yet? Or is this the first attempt?

Not really... Here at home I have an USR router ad wireless security is set as:

Network authentication: WPA2 and WPA (recommended)
WPA encyiption: TKIP


On this router I have another strange behaviour. When I boot the laptop, it tries to connect to the network, without success. dmesg says that eth1 is not ready. If I clear the gconf key related to my network, then NM asks me for the password and get connected. The same if I simply restart dbus with:


sudo /etc/init.d/dbus restart


Anyway, at the end I get connected, but I have to do one of those 2 actions when I reboot the pc.

[wieman01]

Fisrt of all, thank you for your great patience!

Anyway, at the end I get connected, but I have to do one of those 2 actions when I reboot the pc.
No problem at all.

Are you sure your company's network is a WPA-PSK one and not WPA-EAP with a user name & a password?

That said, I need to think about it for a while. I'll get back to you tomorrow if I have another idea.

[saltydog]

No problem at all.

Are you sure your company's network is a WPA-PSK one and not WPA-EAP with a user name & a password?

That said, I need to think about it for a while. I'll get back to you tomorrow if I have another idea.

No. It is WPA-PSK, with just one key. With windows I connect immediately.

[wieman01]

No. It is WPA-PSK, with just one key. With windows I connect immediately.
Alright then.

You said you are using WPA-TKIP both at home & at work... What could be the difference between one and the other? At home you can connect immediately (despite a few difficulties after a restart) but at work you can't. What different settings could there be?

[saltydog]

Alright then.

You said you are using WPA-TKIP both at home & at work... What could be the difference between one and the other? At home you can connect immediately (despite a few difficulties after a restart) but at work you can't. What different settings could there be?

The problem is that I cannot access to the office's AP configuration. I can connect to it only from windows..

[saltydog]

@wieman:

This morning I finally could get connected in office!
This is what I did:

/etc/network/interfaces:

auto lo
iface lo inet loopback


iface eth1 inet dhcp
wpa-psk <crypted-key>
wpa-driver wext
wpa-key-mgmt WPA-PSK
wpa-proto WPA
wpa-ssid evb
wpa-pairwise TKIP
wpa-group TKIP
auto eth1

then:


sudo ifdown eth1
sudo ifup eth1


I got the connection, but no way to let NM working on this AP...

[wieman01]

@wieman:

This morning I finally could get connected in office!
This is what I did:

/etc/network/interfaces:

auto lo
iface lo inet loopback


iface eth1 inet dhcp
wpa-psk <crypted-key>
wpa-driver wext
wpa-key-mgmt WPA-PSK
wpa-proto WPA
wpa-ssid evb
wpa-pairwise TKIP
wpa-group TKIP
auto eth1

then:


sudo ifdown eth1
sudo ifup eth1


I got the connection, but no way to let NM working on this AP...
That's weird. It does not surprise me that works, however, the fact that NM fails to do the job is really strange.

Frankly I am running out of ideas here...

[_sluimers_]

Hi there,

My router aperently supports Pre-shared key WPA with AES.
I've tried setting this up but now
my network manager applet crashes with a segmentation fault when I select my SSID.

Here's my 'cat /etc/network/interfaces' output:



auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp

auto eth2
iface eth2 inet dhcp

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet static
address 192.168.2.100
gateway 192.168.2.1
dns-nameservers 192.168.2.1
netmask 255.255.255.0
wpa-driver wext
wpa-ssid sluimers
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 7a55779fd6a53b83d3d2582216d80ac4a01178a759f45185e9 bf8118617cc9c9



Another problem is that 'cat resolv.conf' output returns:



# generated by NetworkManager, do not edit!


and it should have a line added with 'nameserver 192.168.x.x', right?

[wieman01]

Another problem is that 'cat resolv.conf' output returns:



# generated by NetworkManager, do not edit!


and it should be nameserver 192.168.2.1., right?
Can you connect using this configuration via "interfaces"? If not please post:

sudo ifdown -v wlan0

sudo ifup -v wlan0
"resolv.conf" only lists your name server once you have successfully connected to the router. Yes, it should list your router's IP address.

[_sluimers_]

rogier@rogier-laptop:/$ sudo ifdown -v wlan0
ifdown: interface wlan0 not configured




rogier@rogier-laptop:/$ sudo ifup -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
wlan0: ERROR while getting interface flags: No such device
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
ioctl[SIOCSIWPMKSA]: No such device
ioctl[SIOCSIWMODE]: No such device
Could not configure driver to use managed mode
ioctl[SIOCGIFFLAGS]: No such device
Could not set interface 'wlan0' UP
ioctl[SIOCGIWRANGE]: No such device
ioctl[SIOCGIFINDEX]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWAUTH]: No such device
WEXT auth param 7 value 0x0 - Failed to disable WPA in the driver.
ioctl[SIOCSIWAUTH]: No such device
WEXT auth param 5 value 0x0 - ioctl[SIOCSIWAUTH]: No such device
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAP]: No such device
ioctl[SIOCGIFFLAGS]: No such device
wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1

ifconfig wlan0 192.168.2.100 netmask 255.255.255.0 up
SIOCSIFADDR: No such device
wlan0: ERROR while getting interface flags: No such device
SIOCSIFNETMASK: No such device
wlan0: ERROR while getting interface flags: No such device
Failed to bring up wlan0.

[wieman01]

rogier@rogier-laptop:/$ sudo ifdown -v wlan0
ifdown: interface wlan0 not configured




rogier@rogier-laptop:/$ sudo ifup -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
wlan0: ERROR while getting interface flags: No such device
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
ioctl[SIOCSIWPMKSA]: No such device
ioctl[SIOCSIWMODE]: No such device
Could not configure driver to use managed mode
ioctl[SIOCGIFFLAGS]: No such device
Could not set interface 'wlan0' UP
ioctl[SIOCGIWRANGE]: No such device
ioctl[SIOCGIFINDEX]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWAUTH]: No such device
WEXT auth param 7 value 0x0 - Failed to disable WPA in the driver.
ioctl[SIOCSIWAUTH]: No such device
WEXT auth param 5 value 0x0 - ioctl[SIOCSIWAUTH]: No such device
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAP]: No such device
ioctl[SIOCGIFFLAGS]: No such device
wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1

ifconfig wlan0 192.168.2.100 netmask 255.255.255.0 up
SIOCSIFADDR: No such device
wlan0: ERROR while getting interface flags: No such device
SIOCSIFNETMASK: No such device
wlan0: ERROR while getting interface flags: No such device
Failed to bring up wlan0.

I am pretty sure the interface name ("wlan0") is incorrect. What does a scan yield:

sudo iwlist scan

[_sluimers_]

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wifi0 Interface doesn't support scanning.

ath0 Scan completed :
Cell 01 - Address: 00:13:10:92:70:62
ESSID:"BeukWIFI"
Mode:Master
Frequency:2.462 GHz (Channel 11)
Quality=14/94 Signal level=-81 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Cell 02 - Address: 00:50:FC:F3:1F:66
ESSID:"sluimers"
Mode:Master
Frequency:2.462 GHz (Channel 11)
Quality=45/94 Signal level=-50 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 54 Mb/s; 9 Mb/s; 18 Mb/s
36 Mb/s; 48 Mb/s
Extra:bcn_int=100
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 03 - Address: 00:13:49:53:14:40
ESSID:"Mireille"
Mode:Master
Frequency:2.422 GHz (Channel 3)
Quality=19/94 Signal level=-76 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:bcn_int=200
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : PSK
Cell 04 - Address: 00:50:18:4D:20:A4
ESSID:"Area51"
Mode:Master
Frequency:2.432 GHz (Channel 5)
Quality=9/94 Signal level=-86 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : PSK
Cell 05 - Address: 00:90:4C:7E:00:6E
ESSID:"@Home51040"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=3/94 Signal level=-92 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : PSK

vmnet1 Interface doesn't support scanning.

vmnet8 Interface doesn't support scanning.

[wieman01]

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wifi0 Interface doesn't support scanning.

ath0 Scan completed :
Cell 01 - Address: 00:13:10:92:70:62
ESSID:"BeukWIFI"
Mode:Master
Frequency:2.462 GHz (Channel 11)
Quality=14/94 Signal level=-81 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100

Alright. The interface name was wrong. Now edit your "interfaces" configuration file once again and restart the network:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto ath0
iface ath0 inet dhcp
address 192.168.2.100
gateway 192.168.2.1
dns-nameservers 192.168.2.1
netmask 255.255.255.0
wpa-driver madwifi
wpa-ssid sluimers
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 7a55779fd6a53b83d3d2582216d80ac4a01178a759f45185e9 bf8118617cc9c9
Then restart:

sudo ifdown -v ath0

sudo ifup -v ath0
SSID broadcast is disabled ("wpa-ap-scan 2")?

[_sluimers_]

This looks a lot better, but nm-applet still crashes when I select my SSID

sudo ifdown -v ath0



Configuring interface ath0=ath0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/postfix
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.ath0.pid -lf /var/lib/dhcp3/dhclient.ath0.leases ath0
There is already a pid file /var/run/dhclient.ath0.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:14:a4:85:e4:6a
Sending on LPF/ath0/00:14:a4:85:e4:6a
Sending on Socket/fallback
DHCPRELEASE on ath0 to 192.168.2.1 port 67
ifconfig ath0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.ath0.pid
Stopped /sbin/wpa_supplicant (pid 23186).



sudo ifup -v ath0



Configuring interface ath0=ath0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver madwifi
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.ath0.pid -i ath0 -D madwifi -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/ath0
wpa_supplicant: wpa-ap-scan 2 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "sluimers" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise CCMP -- OK
wpa_supplicant: wpa-group CCMP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto RSN -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.ath0.pid -lf /var/lib/dhcp3/dhclient.ath0.leases ath0
There is already a pid file /var/run/dhclient.ath0.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:14:a4:85:e4:6a
Sending on LPF/ath0/00:14:a4:85:e4:6a
Sending on Socket/fallback
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 4
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/openssh-server
run-parts: executing /etc/network/if-up.d/postfix
run-parts: executing /etc/network/if-up.d/wpasupplicant

[wieman01]

Ok, WPA support is there, looks fine.

Now please turn on SSID broadcast on the router, then edit "interfaces" again and make it look exactly like this (yes, I removed all data):

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp
Then restart the PC and see if NM connects.

[_sluimers_]

At least this time I allowed to enter the key.
NM crashed after a minute of trying to connect and on second attempt is back to the old crashing when choosing the SSID again.

[wieman01]

At least this time I allowed to enter the key.
NM crashed after a minute of trying to connect and on second attempt is back to the old crashing when choosing the SSID again.
Ok, the last option is that we remove NM completely and do everything manually as described in this tutorial. I don't know if you can live with it, but that's all I can offer right now...

[_sluimers_]

You mean doing everything written in post #2?

I did that without removing nm and I have a connection, yay! \o/

Thanks!

Now I've got one more network problem left. Nothing to do with security, but
every time I connect to my router, not any other router, the line 'nameserver 192.168.2.1' in /etc/resolv.conf disappears. How can I fix that?

[wieman01]

You mean doing everything written in post #2?

I did that without removing nm and I have a connection, yay! \o/

Thanks!

Now I've got one more network problem left. Nothing to do with security, but
every time I connect to my router, not any other router, the line 'nameserver 192.168.2.1' in /etc/resolv.conf disappears. How can I fix that?
Cool.

Question: Do you need the entry in "/etc/resolv.conf" or does it have an impact on your connectivity? I never edit that file or pay attention to it at all.

[_sluimers_]

Yes, it prevented me from certain ports, including 80. I dunno why. Anyway, I got it solved. Hurray! Thank you wieman01. :KS You're the best! :KS

[flaviusc]

Hi everyone! I’ve been trying lately to get online but so far the success was rather limited, I was unable to get WPA to work.

On Ubuntu 7.10, I am using a WLAN card with a Texas Instruments chipset and ndiswrapper instead of the native acx driver.


flavius@mbo:~$ sudo lspci -nn

01:09.0 Network controller [0280]: Texas Instruments ACX 100 22Mbps Wireless Interface [104c:8400]


The card and driver are working, I was able to connect to open networks as well as to WEP enabled networks (using Network Manager).

I removed Network Manager and tried to get WPA, following this guide. Unfortunately I think that the card is unable to get an IP address as I can see from the following:


flavius@mbo:~$ sudo /etc/init.d/networking restart
* Reconfiguring network interfaces...
There is already a pid file /var/run/dhclient.wlan0.pid with pid 5800
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:03:2f:18:8d:cb
Sending on LPF/wlan0/00:03:2f:18:8d:cb
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 192.168.2.1 port 67
There is already a pid file /var/run/dhclient.wlan0.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:03:2f:18:8d:cb
Sending on LPF/wlan0/00:03:2f:18:8d:cb
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
[ OK ]


The network uses WPA2 with PSK, there are several computers using it without a problem. The router has no restrictions regarding DHCP.

Below is the info required for debug. Thanks for your help!



flavius@mbo:~$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 wlan0
0.0.0.0 0.0.0.0 0.0.0.0 U 1000 0 0 wlan0

flavius@mbo:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11b ESSID:off/any
Mode:Managed Channel:0 Access Point: Not-Associated
Bit Rate:22 Mb/s Tx-Power:0 dBm Sensitivity=0/3
RTS thr:off Fragment thr:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

flavius@mbo:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:0C:6E:9B:CB:19
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:17 Base address:0xa000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:18 errors:0 dropped:0 overruns:0 frame:0
TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1596 (1.5 KB) TX bytes:1596 (1.5 KB)

wlan0 Link encap:Ethernet HWaddr 00:03:2F:18:8D:CB
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:20 Memory:e2014000-e2015000

wlan0:ava Link encap:Ethernet HWaddr 00:03:2F:18:8D:CB
inet addr:169.254.6.213 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Interrupt:20 Memory:e2014000-e2015000

flavius@mbo:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :

Cell 04 - Address: 00:16:38:E7:02:21
ESSID:"My_ESSID"
Protocol:IEEE 802.11FH
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:100/100 Signal level:90/154 Noise level:160/154
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0

flavius@mbo:~$ cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid My_ESSID
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk My__hex_key

flavius@mbo:~$ cat /etc/modprobe.d/ndiswrapper
alias wlan0 ndiswrapper

flavius@mbo:~$ cat /etc/resolv.conf
# generated by NetworkManager, do not edit!

nameserver 192.168.2.1

[wieman01]

@flaviusc:

Can you confirm that you have got the right Windows driver? Does it really support WPA?

The scan does not really list any WPA networks so I was wondering why...

[flaviusc]

Hi,

thanks for the prompt answer.


Can you confirm that you have got the right Windows driver?

It all depends on do you understand by "right". The Ubuntu "Device Manager" gives me the data mentioned below, but as far as I was able to understand, the card is actually a D-Link AirPlus DWL-520+ sold under another name here in Germany.



Vendor - Texas Instruments
Product - ACX 100 22Mbps Wireless Interface
OEM Vendor - Global Sun Technology Inc
OEM Product - WL-8305 IEEE802.11b+ Wireless LAN PCI Adapter


The PCI ID matches as well, so I downloaded the D-Link driver specified on the ndiswrapper web page and I was able to successfully install and use the card without a glitch.



Does it really support WPA?


Well, the Windows driver does NOT support WPA, it only supports WEP. But as far as I was able to understand it is the task of wpasupplicant to add WPA capabilities to a wireless card that lacks them (like the one I'm using).

This is what dmesg tells me about the driver:



flavius@mbo:~$ dmesg |grep ndis
[ 39.344994] ndiswrapper version 1.45 loaded (smp=yes)
[ 39.424256] ndiswrapper: driver airplus (D-Link,09/08/2003,4.15.5.1) loaded
[ 39.425251] ndiswrapper: using IRQ 20
[ 40.023332] ndiswrapper (set_encr_mode:673): setting encryption mode to 6 failed (C00000BB)
[ 40.026065] usbcore: registered new interface driver ndiswrapper


Is there any change on getting WPA to work on this card? Or should I start shopping for a new one?

[wieman01]

Well, the Windows driver does NOT support WPA, it only supports WEP. But as far as I was able to understand it is the task of wpasupplicant to add WPA capabilities to a wireless card that lacks them (like the one I'm using).
That's exactly your problem, mate. As the driver does not really support WPA, it won't work. wpa-supplicant will help you only if the wireless adapter understands the protocol.

The last resort is to buy another card as WEP is highly insecure. But that's up to you of course.

[flaviusc]

Hi,

This page http://www.seattlewireless.net/DlinkDwl520plus claims that the card supports WPA on Windows XP using driver version 3.07. That's exactly the driver I'm using with ndiswrapper, but it looks that the info might not be true :(

I am really at a lost here. Especially since the card properly identifies the IP address of the router and it actually asks for an IP address ...

And I am sure that I've seen somewere a mention of another Windows driver for an acx 100 based card also supporting WPA. Maybe I can dig up a driver like that. Is there a way to find out if a driver supports WPA or not?

[wieman01]

And I am sure that I've seen somewere a mention of another Windows driver for an acx 100 based card also supporting WPA. Maybe I can dig up a driver like that. Is there a way to find out if a driver supports WPA or not?
Yes, the change log. Every driver should come with a change log or README. It should state whether it supports WPA or not.

[myharshdesigner]

cooooooooooolllllllllllllllllllllllll :)

[.zoXan.]

Hi all,

I'm having trouble with my wireless connection. My SSID is set to broadcast, but Ubuntu doesn't pick it up. It picks up my neighbor's ["Tamago"] but not mine. I'm using the ipw3945 driver AFAIK.

I'm using WPA2 and I don't know how to set it up. Here's everything that I can provide to help you:

http://rafb.net/p/BtupXn50.html

Can you please help me?

[wieman01]

Hi all,

I'm having trouble with my wireless connection. My SSID is set to broadcast, but Ubuntu doesn't pick it up. It picks up my neighbor's ["Tamago"] but not mine. I'm using the ipw3945 driver AFAIK.

I'm using WPA2 and I don't know how to set it up. Here's everything that I can provide to help you:

http://rafb.net/p/BtupXn50.html

Can you please help me?
Please also provide:

sudo cat /etc/network/interfaces
Does network manager list any other networks around you?

[FokkerCharlie]

Hi All-

Any chance of a hand with my wifi? I've had it working fine on WinXP, using WPA-PSK/TKIP, which is all fine.

Network manager doesn't want to play the WPA game (I don't think this is news to anyone!), and worse, often when I try to tweak the settings, the system crashes, and won't re-start, see : http://ubuntuforums.org/showthread.php?t=613133 I'm not alone!

My network/interfaces currently only contains:

auto lo
iface lo inet loopback

Device manager reports that the card is:
Texas Instruments
ACX 111 54Mbps Wireless Interface
Bus type PCI
Device Type / Capabilities unknown

OK- I know this doesn't look right, but I am afraid to fiddle in case I get the crash, and then have to re-install (for the 9th time) when Ubuntu won't re-start.

Please help a noob!

Charlie

[wieman01]

Hi All-

Any chance of a hand with my wifi? I've had it working fine on WinXP, using WPA-PSK/TKIP, which is all fine.

Network manager doesn't want to play the WPA game (I don't think this is news to anyone!), and worse, often when I try to tweak the settings, the system crashes, and won't re-start, see : http://ubuntuforums.org/showthread.php?t=613133 I'm not alone!

My network/interfaces currently only contains:

auto lo
iface lo inet loopback

Device manager reports that the card is:
Texas Instruments
ACX 111 54Mbps Wireless Interface
Bus type PCI
Device Type / Capabilities unknown

OK- I know this doesn't look right, but I am afraid to fiddle in case I get the crash, and then have to re-install (for the 9th time) when Ubuntu won't re-start.

Please help a noob!

Charlie
Ok, let's do a scan first (post the results please):

sudo iwlist scan
What driver do you use? Did the adapter work out of the box?

[FokkerCharlie]

Hi wieman

Here's the results of the scan:


ca@ca-laptop:~$ sudo iwlist scan
[sudo] password for ca:
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:16:E3:13:30:B9
ESSID:"CharlesNet"
Mode:Master
Frequency:2.412 GHz (Channel 1)
Quality=52/100 Signal level=33/100 Noise level=0/100
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Cell 02 - Address: 00:19:E4:12:88:89
ESSID:"2WIRE605"
Mode:Master
Frequency:2.422 GHz (Channel 3)
Quality=36/100 Signal level=10/100 Noise level=0/100
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Cell 03 - Address: 00:19:E4:12:88:8B
ESSID:"BT Fusion-8605"
Mode:Master
Frequency:2.422 GHz (Channel 3)
Quality=36/100 Signal level=10/100 Noise level=0/100
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Cell 04 - Address: 00:16:0A:09:13:DB
ESSID:""
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=37/100 Signal level=12/100 Noise level=0/100
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 22 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Cell 05 - Address: 00:18:4D:3E:DC:CA
ESSID:"NETGEAR"
Mode:Master
Frequency:2.462 GHz (Channel 11)
Quality=31/100 Signal level=3/100 Noise level=0/100
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 22 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Cell 06 - Address: 00:0F:B5:CE:AB:FA
ESSID:"PRIV_WIFI2"
Mode:Master
Frequency:2.412 GHz (Channel 1)
Quality=31/100 Signal level=3/100 Noise level=0/100
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 22 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s


I'm afraid that I am not sure what drive I'm using- a complete Linux noob. Network manager sees the wifi adapter, and lists a handful of networks, which is what I would expect. Unfortunately, after trying some settings, the crashes and problems start. So I suppose that means that the driver isn't working correctly?!

Cheers
Charlie

[ubulap]

FokkerCharlie,

if I'm not mistaken Texas Instruments
ACX 111 54Mbps linux driver does not yet support WPA.
(The module should be called acx)

I guess you need to try ndiswrapper, and make use of the windows driver with it.

[juje]

Ok, this maybe sound like i'm quite lazy and didn't try it harder, but that's not riught...i really follow the original threat and only get this...i can configure my network only with wpa and broadcast essid. It works fine, but every time i restart my pc it's has some trouble to connect...on the other hand, i want to get the wpa2 secure connection, any clue?

This is what i've tried and works (any change to this it doesn't works:
auto wlan0
iface wlan0 inet static
address 192.168.1.100
gateway 192.168.1.1
dns-nameservers 200.69.32.5
netmask 255.255.255.0
wpa-driver wext
wpa-ssid xxxxxxxxxxxxx
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk c53ad64bde66e72384da57fe1536917e994ca4bfdc79bd7c30 9c76ca02aa9afe

I'm a gutsy user with d-link DWL-G510 Rev C and a wrt54g linksys router

Thanks and sorry for my lousy english...

[wieman01]

FokkerCharlie,

if I'm not mistaken Texas Instruments
ACX 111 54Mbps linux driver does not yet support WPA.
(The module should be called acx)

I guess you need to try ndiswrapper, and make use of the windows driver with it.
I am afraid you are right. Scanning lists a number of networks, but there is no mention of WPA secured ones. That generally means that the driver does not recognize them as such... bad news.

[wieman01]

Ok, this maybe sound like i'm quite lazy and didn't try it harder, but that's not riught...i really follow the original threat and only get this...i can configure my network only with wpa and broadcast essid. It works fine, but every time i restart my pc it's has some trouble to connect...on the other hand, i want to get the wpa2 secure connection, any clue?

This is what i've tried and works (any change to this it doesn't works:
auto wlan0
iface wlan0 inet static
address 192.168.1.100
gateway 192.168.1.1
dns-nameservers 200.69.32.5
netmask 255.255.255.0
wpa-driver wext
wpa-ssid xxxxxxxxxxxxx
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk c53ad64bde66e72384da57fe1536917e994ca4bfdc79bd7c30 9c76ca02aa9afe

I'm a gutsy user with d-link DWL-G510 Rev C and a wrt54g linksys router

Thanks and sorry for my lousy english...
So you are saying that you need to restart the network after a reboot? Please see post #2 of this thread for a workaround/solution.

Have you tried WPA2 as well (RSN)? Were you any successful or did you have trouble connecting in that case?

[FokkerCharlie]

Wieman, ubalap, thanks for your help.

I'll have a go with NDISWRAPPER.

Charlie

[FokkerCharlie]

Hi again

Just in case you're interested- I had a go with Ndiswrapper.

It worked a treat, until I'd re-booted a couple of times, and then it stopped. I have no idea why. I am completely sure that I had not changed any configuration in the meantime- in fact I was starting and stopping the computer just to see if the WLAN would stay working! Same results with WICD and Network Manager.

Anyway, maybe I'll ask in the Ndiswrapper forums for help there.

Cheerio!
Charlie

[wieman01]

Hi again

Just in case you're interested- I had a go with Ndiswrapper.

It worked a treat, until I'd re-booted a couple of times, and then it stopped. I have no idea why. I am completely sure that I had not changed any configuration in the meantime- in fact I was starting and stopping the computer just to see if the WLAN would stay working! Same results with WICD and Network Manager.

Anyway, maybe I'll ask in the Ndiswrapper forums for help there.

Cheerio!
Charlie
I can help you with it if you don't mind. Please send me the link by PM and I'll support you. Please check out my own 'ndiswrapper' HOWTO (see signature) as well... perhaps you have missed a step or two.

What tutorial have you used?

[ubulap]

FokkerCharlie,

one of the things that I found of need to do, when I was using ndiswrapper (I've now moved to rt73 driver) to have it working, was that I needed to restart the network at each boot, to have it working.
Maybe this is why after rebooting it stopped working for you?

I had to run the following command:

sudo /etc/init.d/networking restart

[wieman01]

FokkerCharlie,

one of the things that I found of need to do, when I was using ndiswrapper (I've now moved to rt73 driver) to have it working, was that I needed to restart the network at each boot, to have it working.
Maybe this is why after rebooting it stopped working for you?

I had to run the following command:

sudo /etc/init.d/networking restart
Post #2 of this thread tries to fix that. Check it out.

[FokkerCharlie]

Hi Ubulap

The problem I am facing is that the connection needs to be re-set every couple of minutes while the computer is running- ie it does not need to be re-booted to need to wake-up.

See the new thread:
http://ubuntuforums.org/showthread.php?p=3842134#post3842134

Nice try, tho, thanks!
Charlie

[markw365]

Ok, I've been playing with this for a couple of days. Our network guys tell me the setup is PEAP-TLS. I've tried every combination in the network-manager, wpa-enterprise, wpa2-enterprise, etc. It seems to connect then drop the connection, like something is wrong with the authentication handshake.

Here's my settings for wireless in XP:

Under the network properties "Association Tab".

Network Authentication is set to "Open"
Data Encryption is set to "WEP"

Under the Authentication Tab:

"Enable IEEE 802.1x authentication for this network" checked
EAP Type: Protected EAP(PEAP)
Authenticate as a computer when computer information is available. Checked.

Under PEAP Properties, the
"Validate server certificate" is checked along with our company certificate.

Then in the Select authentication pull down it has "Secured Password (EAP-MSCHAPv2) selected, which uses my domain/user creditentials.

Under the Connection tab it has "connect when in range".

This all works fine under XP, but when I boot into Linux, and select WPA or WPA2 enterprise, mschapv2, etc. it doesn't work. I've got the certificate on the machine in both .p7b and .pem formats. It looks like it gets close, but it doesn't come up. In the username/password dialog I give the domain/username and my domain login.

Any help would be appriciated.

Card is built in laptop with the intel 2200 chipset, works fine at home and everywhere else. I also have a drawer full of USB wireless adapters I can try.

Thanks,
Mark

[wieman01]

Ok, I've been playing with this for a couple of days. Our network guys tell me the setup is PEAP-TLS. I've tried every combination in the network-manager, wpa-enterprise, wpa2-enterprise, etc. It seems to connect then drop the connection, like something is wrong with the authentication handshake.

Here's my settings for wireless in XP:

Under the network properties "Association Tab".

Network Authentication is set to "Open"
Data Encryption is set to "WEP"

Under the Authentication Tab:

"Enable IEEE 802.1x authentication for this network" checked
EAP Type: Protected EAP(PEAP)
Authenticate as a computer when computer information is available. Checked.

Under PEAP Properties, the
"Validate server certificate" is checked along with our company certificate.

Then in the Select authentication pull down it has "Secured Password (EAP-MSCHAPv2) selected, which uses my domain/user creditentials.

Under the Connection tab it has "connect when in range".

This all works fine under XP, but when I boot into Linux, and select WPA or WPA2 enterprise, mschapv2, etc. it doesn't work. I've got the certificate on the machine in both .p7b and .pem formats. It looks like it gets close, but it doesn't come up. In the username/password dialog I give the domain/username and my domain login.

Any help would be appriciated.

Card is built in laptop with the intel 2200 chipset, works fine at home and everywhere else. I also have a drawer full of USB wireless adapters I can try.

Thanks,
Mark
Tough one... I don't user Network Manager much. But the IPW2200 driver is definitely capable of PEAP. Could you post screenshots of your NM settings?

Perhaps 'dmesg" (command line) tells us more:

dmseg

[Marcellus]

A follow-up on my newbie-post from long ago: (search on username)

I didn't succeed in getting WPA to work on two pcmcia wifi cards while the cards were known to work perfectly with WEP: one was Linksys WPC11 (I don't remember which version), the other a Senao NL-2511CD. In the end it was the cards' fault: they were pretty old 802.11b-only cards that turned out not to support WPA.

I replaced them with a new usb dongle --- Azurewave AW-GU210 --- which immediately worked under 7.04 and 7.10. However, after an hour (or sometimes 3) or so it would overheat, I think, and fail to connect for several minutes. Possibly because it tries to move fast broadband over USB1.1?

This I replaced with a similar Belkin usb dongle that has been working perfectly with the same setups --- USB1.1 on a 2.2ghz celeron desktop and on a celeron 1.1ghz laptop.

[tnunamak]

Hi,

I have a working wireless connection when it it unencrypted, but I've tried following your guide to connect to my university's LEAP network and when I restart the networking service I get the following:


sudo /etc/init.d/networking restart
* Reconfiguring network interfaces... * Stopping the Firestarter firewall...
...done.
* Starting the Firestarter firewall...
...fail!
run-parts: /etc/network/if-down.d/50firestarter exited with return code 2
There is already a pid file /var/run/dhclient.eth0.pid with pid 6102
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:19:7d:8c:cd:22
Sending on LPF/eth0/00:19:7d:8c:cd:22
Sending on Socket/fallback
DHCPRELEASE on eth0 to 1.1.1.1 port 67
There is already a pid file /var/run/dhclient.eth0.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:19:7d:8c:cd:22
Sending on LPF/eth0/00:19:7d:8c:cd:22
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
oDHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 19
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
* Stopping the Firestarter firewall...
...done.
* Starting the Firestarter firewall...
...fail!
run-parts: /etc/network/if-up.d/50firestarter exited with return code 2


My interfaces file reads as follows:


# The loopback network interface
auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0

# The primary network interface
iface eth1 inet dhcp

#iface eth0 inet dhcp
#wireless-essid TUGuest
#auto eth0

auto eth0
iface eth0 inet dhcp
wpa-driver wext
wpa-ssid TUSecure
wpa-ap-scan 1
wpa-eap LEAP
wpa-key-mgmt IEEE8021X
wpa-identity tnunamak
wpa-password mypassword


Any ideas?

[wieman01]

@tnunamak:

Please post the output of (while your are near the network:

sudo iwlist scan
Then also let me know what wireless adapter you have got & what chipset it uses. Not all adapters are PEAP-capable.

[buccaneere]

2. No firewall & configuration tool is running (e.g. Firestarter).

How do I ascertain this?

[wieman01]

How do I ascertain this?
If you haven't installed anything like that, you don't have it. :-) You could also check through Synaptic, the package manager.

[buccaneere]

If you haven't installed anything like that, you don't have it. :-) You could also check through Synaptic, the package manager.

Excellent - thanks.

At what point in your sequence must I unplug the ethernet hardwire? (so that I can cut and paste current configurations, instead of using another machine's connection)

[buccaneere]

Is mac filtering a function of my router, or of my laptop? Or both?

EDIT: Mac filtering is off, on the router. Is there filtering of this type on the laptop?

[wieman01]

Is mac filtering a function of my router, or of my laptop? Or both?

EDIT: Mac filtering is off, on the router. Is there filtering of this type on the laptop?
No, there isn't. It's entirely a router function.

Unplug the (Ethernet) cable as soon as your reboot the PC or restart the network. That's enough.

[buccaneere]

Wireless configuration tools??? Where are they to disable?

[wieman01]

Wireless configuration tools??? Where are they to disable?
You mean Network Manager or what? Are you referring to my comments on the first page? Just turn NM off (right-click, close) and continue.

[buccaneere]

Are you referring to my comments on the first page?

Yes.

I am attempting to follow the instructions explicitly...

Where is roaming to disable?

[wieman01]

Yes.

I am attempting to follow the instructions explicitly...

Where is roaming to disable?
Somewhere in NM or the other network applet... not sure, really. Because I don't use NM very often. But that's what people have told me... sorry, mate.

[buccaneere]

Somewhere in NM or the other network applet... not sure, really. Because I don't use NM very often. But that's what people have told me... sorry, mate.

I cannot enable hidden wireless. (My windows vistabox loses its connection.) Does this preclude connecting linux and windows at the same time?

[wieman01]

I cannot enable hidden wireless. (My windows vistabox loses its connection.) Does this preclude connecting linux and windows at the same time?
No, it does not. You can connect any sort of client, no matter what OS they run.

Then enable SSID broadcast. It adds no extra security anyway (at least not much).

[buccaneere]

Supplicant installed.

Return of iwconfig : (no extensions except for this)

[ ath0 IEEE 802.11g ESSID:"cobweb" ]
[ Mode:Managed Frequency:2.417 GHz Access Point: Not-Associated ]
[ Bit Rate:0 kb/s Tx-Power:9 dBm Sensitivity=0/3 ]
[ Retry:off RTS thr:off Fragment thr:off]
[ Power Management:off]
[ Link Quality=0/94 Signal level=-95 dBm Noise level=-95 dBm]
[ Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0]
[ Tx excessive retries:0 Invalid misc:0 Missed beacon:0]

In order?

[wieman01]

Supplicant installed.

Return of iwconfig : (no extensions except for this)

[ ath0 IEEE 802.11g ESSID:"cobweb" ]
[ Mode:Managed Frequency:2.417 GHz Access Point: Not-Associated ]
[ Bit Rate:0 kb/s Tx-Power:9 dBm Sensitivity=0/3 ]
[ Retry:off RTS thr:off Fragment thr:off]
[ Power Management:off]
[ Link Quality=0/94 Signal level=-95 dBm Noise level=-95 dBm]
[ Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0]
[ Tx excessive retries:0 Invalid misc:0 Missed beacon:0]

In order?
Looks ok. What does this yield:

sudo ifdown ath0

sudo ifup ath0

sudo iwlist ath0

[buccaneere]

Looks ok. What does this yield:


chuckb@chuckb-laptop:~$ sudo ifdown ath0
Password:
There is already a pid file /var/run/dhclient.ath0.pid with pid 4516
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:19:7d:29:74:13
Sending on LPF/ath0/00:19:7d:29:74:13
Sending on Socket/fallback

----------------------------------------------------------------------------------------
chuckb@chuckb-laptop:~$ sudo ifup ath0
Error for wireless request "Set Encode" (8B2A) :
invalid argument "passcobwebcobwebphrase".
There is already a pid file /var/run/dhclient.ath0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:19:7d:29:74:13
Sending on LPF/ath0/00:19:7d:29:74:13
Sending on Socket/fallback
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 20
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 11
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
-------------------------------------------------------------------------------------------------------------------


chuckb@chuckb-laptop:~$ sudo iwlist ath0
iwlist: unknown command `ath0'

Ethernet hardwire is still on.
Roaming mode unknown.
Hidden broadcast disabled.

[wieman01]

Ok, try this again:

sudo iwlist scan
Please also post the contents of:

sudo gedit /etc/network/interfaces

[buccaneere]

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wifi0 Interface doesn't support scanning.

ath0 Scan completed :
Cell 01 - Address: 00:18:39:DF:0E:BD
ESSID:"linksys"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=1/94 Signal level=-94 dBm Noise level=-95 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Cell 02 - Address: 00:14:95:A6:47:89
ESSID:"2WIRE493"
Mode:Master
Frequency:2.462 GHz (Channel 11)
Quality=17/94 Signal level=-78 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Cell 03 - Address: 00:14:95:BA:79:91
ESSID:"2WIRE272"
Mode:Master
Frequency:2.462 GHz (Channel 11)
Quality=18/94 Signal level=-77 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Cell 04 - Address: 00:19:5B:05:F0:12
ESSID:"cobweb"
Mode:Master
Frequency:2.412 GHz (Channel 1)
Quality=53/94 Signal level=-42 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK

sit0 Interface doesn't support scanning.



Network device: ath0
Hardware address: not available
IP address: not available
Netmask: not available
Broadcast: not available
Multicast: not available
MTU: not available
Link speed: not available
State: not available
Transmitted packets: 0
Transmission errors: 0
Received packets: 0
Reception errors: 0
Collisions: 0


Huh?

[buccaneere]

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp

auto eth2
iface eth2 inet dhcp

auto wlan0
iface wlan0 inet dhcp


iface ath0 inet dhcp
wireless-essid cobweb
wireless-key p...e

auto ath0


I am cobweb

[wieman01]

Hang on a minute... you have not configured it yet, have you? Everything looks set, so I think you can continue with the WPA section ("/etc/network/interfaces").

[buccaneere]

Hang on a minute... you have not configured it yet, have you? Everything looks set, so I think you can continue with the WPA section ("/etc/network/interfaces").

I do not know if I have completely configured for wireless, or not. You have skipped me forward I think, through configuration steps...

I'm now at #3???

EDIT: I now see notes........................



auto wlan0
iface wlan0 inet static
address 192.168.168.40
gateway 192.168.168.230
dns-nameservers 192.168.168.230
netmask 255.255.255.0
wpa-driver wext
wpa-ssid <your_essid>
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk <your_hex_key> [IMPORTANT: See "WPA-PSK key generation"]

[wieman01]

I do not know if I have completely configured for wireless, or not. You have skipped me forward I think, through configuration steps...

I'm now at #3???



auto wlan0............................................. ..........this will be ath0 ?
iface wlan0 inet static.........................................ifa ce ath0 inet dynamic?
address 192.168.168.40.................................... .address of router?
gateway 192.168.168.230..................................d efault gateway? from router?
dns-nameservers 192.168.168.230...................?
netmask 255.255.255.0..................................... .subnet mask?
wpa-driver wext
wpa-ssid <your_essid>
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk <your_hex_key> [IMPORTANT: See "WPA-PSK key generation"]
Alright.

Watch out tough... The scan says that you use WPA-TKIP. That is WPA1 rather than WPA2. An example is provided as well.

[buccaneere]

How do you exit after saving edited file?


This look good?

auto eth1
iface eth1 inet dhcp

auto eth2
iface eth2 inet dhcp

auto wlan0
iface wlan0 inet dhcp


iface ath0 inet dhcp
wireless-essid cobweb
wireless-key p...e

auto ath0
iface ath0 inet dhcp
00:19:5B:05:F0:12
192.168.0.1
192.168.0.1
255.255.255.0
wpa-driver wext
wpa-ssid cobweb
wpa-ap-scan 1
wpa-proto wpa
wpa-pairwise tkip
wpa-group tkip
wpa-key-mgmt wpa-psk
wpa-psk 2057043c4c9c2e031ac0ba3c960f4c5b3b8c8a5b319cbaab4a 93445f429f0727

[buccaneere]

route -n
kernel ip routing table
destination gateway genmask flags metric ref use iface


iwconfig
ath0
ieee 802.11b essid : " "
mode:managed channel 0 access point not associated
bit rate 0 kbs tx power 0dbm sensitivity 0/3
retry off rts thr:off fragment thr:off
power management off
link quality 0 sig level 0 noise 0
rx invalid nwid 0 crypt 0 frag 0
tx retries 0 invalid misc 0 missed beacon 0

no other wireless extensions



ifconfig
no items returned



iwlist scan
ath0 no scan results
all other interfaces do not support scanning



cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp

auto eth2
iface eth2 inet dhcp

auto wlan0
iface wlan0 inet dhcp


iface ath0 inet dhcp
wireless-essid cobweb
wireless-key p...e

auto ath0
iface ath0 inet dhcp
00:19:5B:05:F0:12
192.168.0.1
192.168.0.1
255.255.255.0
wpa-driver wext
wpa-ssid cobweb
wpa-ap-scan 1
wpa-proto wpa
wpa-pairwise tkip
wpa-group tkip
wpa-key-mgmt wpa-psk
wpa-psk 2057043c4c9c2e031ac0ba3c960f4c5b3b8c8a5b319cbaab4a 93445f429f0727



cat /etc/modprobe.d/ndiswrapper
no file or directory



cat /etc/resolve.conf
no file or directory

[wieman01]

@buccaneere:

Ok, edit your "interfaces" file and post this (replacing all contents):

auto lo
iface lo inet loopback

auto ath0
iface ath0 inet dhcp
wpa-driver madwifi
wpa-ssid cobweb
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk 2057043c4c9c2e031ac0ba3c960f4c5b3b8c8a5b319cbaab4a 93445f429f0727
The restart the network and post the output:

sudo ifdown ath0

sudo ifup ath0
By the way... why do you not use Network Manager? Do you need a static IP? The script above is for DHCP.

[buccaneere]

@buccaneere:

Ok, edit your "interfaces" file and post this (replacing all contents):.

I did edit the interfaces file.

Did I put in incorrect values?



By the way... why do you not use Network Manager?
You mean the GUI? I don't know the values there to enter any more than with CLI.


Do you need a static IP?
I don't know. Do I?

[wieman01]

I did edit the interfaces file.

Did I put in incorrect values?



You mean the GUI? I don't know the values there to enter any more than with CLI.


I don't know. Do I?
The value weren't quite correct. So I corrected them for you. Please use the latest script that I have posted.

Yes, I was referring to NM, the networking GUI.

Let's try DHCP first of all. The script should be fine. You probably don't need static IP.

[buccaneere]

@buccaneere:

Ok, edit your "interfaces" file and post this (replacing all contents):

The restart the network and post the output:


By the way... why do you not use Network Manager? Do you need a static IP? The script above is for DHCP.

Done.

After edit, restart, sudo ifdown, and sudo ifup, functions executed, I plugged in the ethernet hardwire to copy and paste, instead of typing in another machine. No problem?

ifdown return:

chuckb@chuckb-laptop:~$ sudo ifdown ath0
There is already a pid file /var/run/dhclient.ath0.pid with pid 9592
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:19:7d:29:74:13
Sending on LPF/ath0/00:19:7d:29:74:13
Sending on Socket/fallback
DHCPRELEASE on ath0 to 192.168.0.1 port 67


chuckb@chuckb-laptop:~$ sudo ifup ath0
There is already a pid file /var/run/dhclient.ath0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:19:7d:29:74:13
Sending on LPF/ath0/00:19:7d:29:74:13
Sending on Socket/fallback
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 7
DHCPOFFER from 192.168.0.1
DHCPREQUEST on ath0 to 255.255.255.255 port 67
DHCPACK from 192.168.0.1
bound to 192.168.0.101 -- renewal in 4885 seconds.
chuckb@chuckb-laptop:~$

Thanks again for help............

[buccaneere]

GUI windows are now not responding for network configuration.

Wireless icon for signal strength has appeared at 86% - 18 inches from router???

System/administration/networking tools/network settings: wireless, wired, and modem connections are not enabled, nor are they configured. ?

How am I now browsing? Eth hardwire is plugged in...

[buccaneere]

This post is with hardwire unplugged; all connections still not enabled or configured............

[wieman01]

This post is with hardwire unplugged; all connections still not enabled or configured............
Unplugged or plugged?

DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 7
DHCPOFFER from 192.168.0.1
DHCPREQUEST on ath0 to 255.255.255.255 port 67
DHCPACK from 192.168.0.1
bound to 192.168.0.101 -- renewal in 4885 seconds.
This tells me you are connected... Please restart the network once again and post:

route
You should be able to ping Google:

ping www.google.com

[MarceloPereira]

Hi everyone,

I´m facing a problem, if anyone could help i will thank.

My notebook is a FE770G Sony Vaio, 3945ABG wireless card, using Ubuntu 7.10, updated.

I´m trying to use it with a D-Link DI-524 Wireless router.

I´m trying to use WPA2, but I only get it working with WPA.

My .../interfaces file is the default one, static IP.

Is there any problem with this configuration and WPA2 ?

thanks

[wieman01]

Hi everyone,

I´m facing a problem, if anyone could help i will thank.

My notebook is a FE770G Sony Vaio, 3945ABG wireless card, using Ubuntu 7.10, updated.

I´m trying to use it with a D-Link DI-524 Wireless router.

I´m trying to use WPA2, but I only get it working with WPA.

My .../interfaces file is the default one, static IP.

Is there any problem with this configuration and WPA2 ?

thanks
There shouldn't be a problem. Just use the standard networking applet called Network Manager to configure it. No issues I would think.

[buccaneere]

Post # 1037 was with hardwire UNplugged. Wireless was functional (with wireless, wired, and modem connections NOT enabled, OR configured).

I've re-started the machine, and the server (router) connection was lost. I opened gui for wireless configgin', enabled, put in ssid and passkey, and wireless is enabled.

If I make a backup for etc/network/interfaces, I can adjust wired settings, to restore hardwire connection???

[wieman01]

Post # 1037 was with hardwire UNplugged. Wireless was functional (with wireless, wired, and modem connections NOT enabled, OR configured).

I've re-started the machine, and the server (router) connection was lost. I opened gui for wireless configgin', enabled, put in ssid and passkey, and wireless is enabled.

If I make a backup for etc/network/interfaces, I can adjust wired settings, to restore hardwire connection???
For both wireless and wired please use this one:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto ath0
iface ath0 inet dhcp
wpa-driver madwifi
wpa-ssid cobweb
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk 2057043c4c9c2e031ac0ba3c960f4c5b3b8c8a5b319cbaab4a 93445f429f0727
VERY IMPORTANT: Please follow post #2 of this thread if you lose connection after a restart. That's a known bug and I posted a workaround there.

[kboykowboy]

I'm using my other computer at my girlfriends house. She has wpa-psk encryption. i have a USB - TEW-424UB 3.0 card. i have 7.10 ubuntu. I can't get online with my ubuntu machine via wire or wireless so i cant really install wpa supplicant on my ubuntnu - but could i somehow how download it and put it on my usb disk and then stick that into my ubuntu?!

my second question is - how do i make the USB - TEW-424UB 3.0 work via wpa supplicant?! should i run some commands so you know how my laptop is setup etc?!

[buccaneere]

I'm using my other computer at my girlfriends house. She has wpa-psk encryption. i have a USB - TEW-424UB 3.0 card. i have 7.10 ubuntu. I can't get online with my ubuntu machine via wire or wireless so i cant really install wpa supplicant on my ubuntnu - but could i somehow how download it and put it on my usb disk and then stick that into my ubuntu?!

Yes.

I burned some driver packages to a CD with a windows box, and then loaded it onto a ubuntu machine successfully.


my second question is - how do i make the USB - TEW-424UB 3.0 work via wpa supplicant?! should i run some commands so you know how my laptop is setup etc?!


There might be info in this thread that's helpful:
http://ubuntuforums.org/showthread.php?t=619955&page=4
The OP's wireless device address is a USB controller; not a PCI controller. The driver had to be manually configured for the USB address. See post # 40 of that thread. I'd like to know if that works for ya'.

I can help no further - I'm still a rookie, but know what to look for...

[tnunamak]

@tnunamak:

Please post the output of (while your are near the network:

Then also let me know what wireless adapter you have got & what chipset it uses. Not all adapters are PEAP-capable.

This is really long because I think there are multiple routers throughout the building. The network I'm trying to connect to is TUSecure.


tnunamak@atlas:~$ sudo iwlist scanning
[sudo] password for tnunamak:
lo Interface doesn't support scanning.

eth1 Interface doesn't support scanning.

eth0 Scan completed :
Cell 01 - Address: 00:14:6A:F0:BF:E0
ESSID:"TrinityAP"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:9/100 Signal level:-90 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 02 - Address: 00:14:6A:F0:BF:E1
ESSID:"TUGuest"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:7/100 Signal level:-91 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 03 - Address: 00:14:6A:F0:BF:E4
ESSID:"TUSecure"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:7/100 Signal level:-91 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-40
Pairwise Ciphers (2) : WEP-40 TKIP
Authentication Suites (1) : 802.1x
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (2) : WEP-40 TKIP
Authentication Suites (1) : 802.1x
Cell 04 - Address: 00:0F:8F:46:B9:50
ESSID:"TrinityAP"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:17/100 Signal level:-85 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 05 - Address: 00:0F:8F:46:B9:D0
ESSID:"TrinityAP"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:23/100 Signal level:-81 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 06 - Address: 00:0F:8F:4C:39:90
ESSID:"TrinityAP"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:9/100 Signal level:-90 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 07 - Address: 00:0F:8F:4C:39:91
ESSID:"TUGuest"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:17/100 Signal level:-85 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 08 - Address: 00:0F:8F:4C:39:94
ESSID:"TUSecure"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:17/100 Signal level:-85 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-40
Pairwise Ciphers (2) : WEP-40 TKIP
Authentication Suites (1) : 802.1x
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (2) : WEP-40 TKIP
Authentication Suites (1) : 802.1x
Cell 09 - Address: 00:0F:8F:46:B9:D1
ESSID:"TUGuest"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:26/100 Signal level:-79 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 10 - Address: 00:0F:8F:46:B9:D4
ESSID:"TUSecure"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:21/100 Signal level:-82 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-40
Pairwise Ciphers (2) : WEP-40 TKIP
Authentication Suites (1) : 802.1x
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (2) : WEP-40 TKIP
Authentication Suites (1) : 802.1x
Cell 11 - Address: 00:0F:8F:46:C1:24
ESSID:"TUSecure"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:3/100 Signal level:-94 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-40
Pairwise Ciphers (2) : WEP-40 TKIP
Authentication Suites (1) : 802.1x
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (2) : WEP-40 TKIP
Authentication Suites (1) : 802.1x
Cell 12 - Address: 00:0F:8F:49:FD:30
ESSID:"TrinityAP"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:4/100 Signal level:-93 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 13 - Address: 00:0F:8F:49:FD:31
ESSID:"TUGuest"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:4/100 Signal level:-93 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 14 - Address: 00:0F:8F:49:FD:34
ESSID:"TUSecure"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:0/100 Signal level:-96 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-40
Pairwise Ciphers (2) : WEP-40 TKIP
Authentication Suites (1) : 802.1x
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (2) : WEP-40 TKIP
Authentication Suites (1) : 802.1x


Running lspci gives "Broadcom Corporation BCM94311MCG wlan mini-PCI (rev 01)"

Thanks for the help!

[wieman01]

This is really long because I think there are multiple routers throughout the building. The network I'm trying to connect to is TUSecure.


tnunamak@atlas:~$ sudo iwlist scanning
[sudo] password for tnunamak:
lo Interface doesn't support scanning.

eth1 Interface doesn't support scanning.

eth0 Scan completed :
Cell 14 - Address: 00:0F:8F:49:FD:34
ESSID:"TUSecure"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:0/100 Signal level:-96 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-40
Pairwise Ciphers (2) : WEP-40 TKIP
Authentication Suites (1) : 802.1x
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (2) : WEP-40 TKIP
Authentication Suites (1) : 802.1x


Running lspci gives "Broadcom Corporation BCM94311MCG wlan mini-PCI (rev 01)".
Looks quite promising in fact, although there is no mention of PEAP. At least your card recognized the cipher correctly and also detects the right (although generic) authenticaion suite.

Question... the latest (CVS) version of Network Manager apparently supports PEAP. Would it not be easier to compile it from source if this does not work for you? You could open a new thread, send me the link by PM and we try to work it out together.

[wieman01]

I'm using my other computer at my girlfriends house. She has wpa-psk encryption. i have a USB - TEW-424UB 3.0 card. i have 7.10 ubuntu. I can't get online with my ubuntu machine via wire or wireless so i cant really install wpa supplicant on my ubuntnu - but could i somehow how download it and put it on my usb disk and then stick that into my ubuntu?!

my second question is - how do i make the USB - TEW-424UB 3.0 work via wpa supplicant?! should i run some commands so you know how my laptop is setup etc?!
If you are on Ubuntu 7.10 "wpa-supplicant" is already installed. It comes with the default install.

Have you tried the default networking applet called Network Manager? It should let you connect to various types of networks, including secured wireless ones. Try it first and see if it works for you. In that case you can avoid messing around with command line.

[kboykowboy]

If you are on Ubuntu 7.10 "wpa-supplicant" is already installed. It comes with the default install.

Ok nice - what should i look for!?


Have you tried the default networking applet called Network Manager? It should let you connect to various types of networks, including secured wireless ones. Try it first and see if it works for you. In that case you can avoid messing around with command line.

I tryed it, and it finds the network, and when i click connect and type in the password for it it also "loads" and sais acquiering ip adress or something like that.. but after that there is no connection... even though it looks like it should have worked... my network card also sais (on the package) that it supports WPA encryption... so i'm kinda confused!

Thanks to both of you for replying by the way!

[wieman01]

Ok nice - what should i look for!?



I tryed it, and it finds the network, and when i click connect and type in the password for it it also "loads" and sais acquiering ip adress or something like that.. but after that there is no connection... even though it looks like it should have worked... my network card also sais (on the package) that it supports WPA encryption... so i'm kinda confused!

Thanks to both of you for replying by the way!
Do you have a WPA option? And how do you type in the password, what format, etc. Could you post a screenshot of the applet while you enter all the required information?

You can configure WPA manually, but that a lot more hassle.

[buccaneere]

For both wireless and wired please use this one:

VERY IMPORTANT: Please follow post #2 of this thread if you lose connection after a restart. That's a known bug and I posted a workaround there.

I have not lost wireless connectivity after re-start on another occasion.

Thanks much for the help!!!. Your personal help was slightly better than the step by step at the beginning of the thread. One reason: knowing what the equivalent values are to edit into /etc/network/interfaces file. I noticed by the third page, that someone else had asked this question (I read just a little further of the 100+ pages, and am not knowing how many others are wondering the same ).

I have two other laptops to get configured, so I got my fingers crossed (and my little piggies, my eyes, my teeth, etc., ...). Just watch for the cloud toward the west:biggrin:

[wieman01]

I have not lost wireless connectivity after re-start on another occasion.

Thanks much for the help!!!. Your personal help was slightly better than the step by step at the beginning of the thread. One reason: knowing what the equivalent values are to edit into /etc/network/interfaces file. I noticed by the third page, that someone else had asked this question (I read just a little further of the 100+ pages, and am not knowing how many others are wondering the same ).

I have two other laptops to get configured, so I got my fingers crossed (and my little piggies, my eyes, my teeth, etc., ...). Just watch for the cloud toward the west:biggrin:
Waiting then, buddy. :-)

[MarceloPereira]

There shouldn't be a problem. Just use the standard networking applet called Network Manager to configure it. No issues I would think.

Hi Wieman01,

I´ve start using ../interfaces approaching cause NetworkManager didn´t work.

Is there any limitation in the WPA passphrase ? special characters ? If I can remember, the error was concerned to the key.

[wieman01]

Hi Wieman01,

I´ve start using ../interfaces approaching cause NetworkManager didn´t work.

Is there any limitation in the WPA passphrase ? special characters ? If I can remember, the error was concerned to the key.
Some special characters cause problems, however, if you avoid single quotes ' and double quote " you should be ok. Try alphanumeric characters first perhaps.

[tnunamak]

Looks quite promising in fact, although there is no mention of PEAP. At least your card recognized the cipher correctly and also detects the right (although generic) authenticaion suite.

Question... the latest (CVS) version of Network Manager apparently supports PEAP. Would it not be easier to compile it from source if this does not work for you? You could open a new thread, send me the link by PM and we try to work it out together.

Well...

I compiled NetworkManager from source after getting past a few stumbling blocks (dependencies mostly), and installed it, but for some reason it still said the stable version was installed in Synaptic, and when I uninstalled that version, it said NetworkManager was not installed at all, as if the source installation had no effect. I'm not sure what was going on with that.

Anyway, I got it to work using the native drivers...

I uninstalled ndiswrapper, installed fwcutter and bcm43xx through the restricted manager, but I had a wierd issue with some ieee80211 modules not existing with my kernel. I reinstalled the kernel modules package and they appeared, so I used wpa supplicant and it finally authenticated.

This whole thing has been a pretty big headache but it finally works. I'm hopeful that when NetworkManager 0.7 is released it will make all of these problems go away...

Thanks for the help

[wieman01]

Well...

I compiled NetworkManager from source after getting past a few stumbling blocks (dependencies mostly), and installed it, but for some reason it still said the stable version was installed in Synaptic, and when I uninstalled that version, it said NetworkManager was not installed at all, as if the source installation had no effect. I'm not sure what was going on with that.

Anyway, I got it to work using the native drivers...

I uninstalled ndiswrapper, installed fwcutter and bcm43xx through the restricted manager, but I had a wierd issue with some ieee80211 modules not existing with my kernel. I reinstalled the kernel modules package and they appeared, so I used wpa supplicant and it finally authenticated.

This whole thing has been a pretty big headache but it finally works. I'm hopeful that when NetworkManager 0.7 is released it will make all of these problems go away...

Thanks for the help
No problem. Would you do me a favor and post:

sudo iwlist scan

sudo gedit /etc/network/interfaces
Just so that I know what it is supposed to look like when you scan for PEAP networks, etc. That information might help others. Thanks, buddy.

[boob11]

Thanx man

[tnunamak]

No problem. Would you do me a favor and post:


Just so that I know what it is supposed to look like when you scan for PEAP networks, etc. That information might help others. Thanks, buddy.

Sure thing, here they are:

sudo iwlist scan


lo Interface doesn't support scanning.

eth1 Interface doesn't support scanning.

eth0 Scan completed :
Cell 04 - Address: 00:0F:8F:44:30:86
ESSID:"TUSecure"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:68/100 Signal level:-52 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-40
Pairwise Ciphers (2) : WEP-40 TKIP
Authentication Suites (1) : 802.1x
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (2) : WEP-40 TKIP
Authentication Suites (1) : 802.1x


My /etc/network/interfaces file

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0

# The primary network interface
iface eth1 inet dhcp

# Guest network
iface eth0 inet dhcp
wireless-essid TUGuest

# Secure network
#auto eth0
#iface eth0 inet dhcp
#wpa-driver wext
#wpa-ssid TUSecure
#wpa-ap-scan 1
#wpa-eap LEAP
#wpa-key-mgmt IEEE8021X
#wpa-identity tnunamak
#wpa-password password

auto eth1
auto eth0


I am using wpa_supplicant to authenticate, however. If I get a chance I might try network manager again and uncomment those lines in my interfaces file, but for now, here's my wpa_supplicant.conf file:


ctrl_interface=/var/run/wpa_supplicant

network={
ssid="TUSecure"
key_mgmt=WPA-EAP
scan_ssid=1
proto=WPA2
eap=LEAP
identity="tnunamak"
password="password"
}

In case anyone is wondering how to use wpa_supplicant, create the file and load it with the following command:

sudo wpa_supplicant -Dwext -ieth0 -c wpa_supplicant.conf

Where eth0 is your wireless network device (if you're using ndiswrapper replace Dwext with Dndiswrapper).

[salefish]

Help!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
My wireless will not connect on restart, and I have to manually restart it twice to get it to connect each time. My service provider also drops my connection repeatidly in an hour which requires restart, only one.
I followed your tutorial and got my Atheros chipset to work, when I manually restart the connection twice.
I tried to follow your post 2 but when I enter the command
"sudo chmod +x wireless-network.sh" I get
"chmod: cannot access `wireless-network.sh': No such file or directory" in return.
I then went to your post with member pfs01089 (http://ubuntuforums.org/showthread.php?t=225290&page=11) and followed your instructions on page 11,
cd /etc/init.d/
sudo gedit wireless-network.sh
sudo chmod +x wireless-network.sh then
/etc/init.d/networking restart and finally
cd /etc/rcS.d/
sudo ln -s /etc/init.d/wireless-network.sh S35wireless-network
This seemed to work, now I only have to restart the network manually once (sometimes) after I start the computer.
Can you help me to get this thing to connect on restart, and to stay connected?
Thank you for the excellent tutorial, my wireless configuration is now

auto ath0
iface ath0 inet dhcp
wpa-driver madwifi
wpa-ssid BarrynTheresaDeux
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <my key here>

This set up seems to be working perfectly

[wieman01]

Help!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
My wireless will not connect on restart, and I have to manually restart it twice to get it to connect each time. My service provider also drops my connection repeatidly in an hour which requires restart, only one.
You have to restart it twice? Man, out of the frying pan and into the fire. ;-)

Please do this as well:

sudo ln -s /etc/init.d/wireless-network.sh /etc/rcS.d/S41wireless-network
Now your network will be restart twice during the boot process. That ought to work.

And thanks for the note on...

"chmod: cannot access `wireless-network.sh': No such file or directory"
The command that I had posted were ambiguous and rather confusing, so I have changed them accordingly.

[salefish]

First thank you for the prompt response.
I tried that and I am still having to restart the network twice. The first time the laptop is getting no response from the router. The second time it gets a response on the first request and then connects on the second.
I assume that reconnecting after a dropped connection is a seperate issue. Is this true?
I do want to apologize, I am a complete novice at linux, but I am trying very hard. Thanks for your help.

[wieman01]

First thank you for the prompt response.
I tried that and I am still having to restart the network twice. The first time the laptop is getting no response from the router. The second time it gets a response on the first request and then connects on the second.
I assume that reconnecting after a dropped connection is a seperate issue. Is this true?
I do want to apologize, I am a complete novice at linux, but I am trying very hard. Thanks for your help.
Have you installed Firestarter (GUI for IP tables)?

[salefish]

Um, have I done what with what?
I guess that would be a no. I will work on that right now, let me read up on what it is.
Oh, no firewall of any kind. At least nothing but what comes preinstalled.

* Reconfiguring network interfaces...
There is already a pid file /var/run/dhclient.ath0.pid with pid 5419
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:16:e3:e9:dd:fd
Sending on LPF/ath0/00:16:e3:e9:dd:fd
Sending on Socket/fallback
DHCPRELEASE on ath0 to 192.168.1.1 port 67
Ignoring unknown interface eth0=eth0.
There is already a pid file /var/run/dhclient.ath0.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:16:e3:e9:dd:fd
Sending on LPF/ath0/00:16:e3:e9:dd:fd
Sending on Socket/fallback
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 6
DHCPOFFER from 192.168.1.1
DHCPREQUEST on ath0 to 255.255.255.255 port 67
DHCPACK from 192.168.1.1
bound to 192.168.1.104 -- renewal in 33536 seconds.
[ OK ]

I changed my settings to enable ssid broadcast, and now it only requires one restart every time.
You have to remember I am very new to Ubuntu and Linux in general, so this is taking me a while to read up on what you are saying.

[wieman01]

Um, have I done what with what?
I guess that would be a no. I will work on that right now, let me read up on what it is.
Oh, no firewall of any kind. At least nothing but what comes preinstalled.

I changed my settings to enable ssid broadcast, and now it only requires one restart every time.
You have to remember I am very new to Ubuntu and Linux in general, so this is taking me a while to read up on what you are saying.
I am sorry if I confuse you. But you are learning quite a number of new things here, which I think are very useful. :-) So I hope you enjoy it.

Having said that, you are right, you don't use Firestarter if you have not installed it yourself. But frankly I am running out of ideas here. Let me do some more thinking & perhaps a little research. No clue as to what we should try next right now.

[salefish]

Well, thanks for sticking with me on this. The biggest reason that I am so adamant about this working is, I own four computers and all of them are wireless. Two desktops and two laptops. I would like to upgrade all but one to Ubuntu, the one being the gaming rig.
Plus the first few lines of the restart state that it is disabling an existing program. Is that something that I should do in terminal, on a permanent basis?
I have just begun reading about the wireless manager WICD. Any thoughts?

[wieman01]

Plus the first few lines of the restart state that it is disabling an existing program. Is that something that I should do in terminal, on a permanent basis?
On a permanent basis, meaning that you should remove it using the package manager (Synaptic).

I have just begun reading about the wireless manager WICD. Any thoughts?
Yes, it is reportedly a fairly good substitute for Network Manager. I would check it out on the 2 laptops perhaps if NM does not do the job. WICD supports the use of Static IP which NM does not.

[salefish]

Yes, is that something that I should disable in synaptic or is that something that I should ignore?

[wieman01]

Yes, is that something that I should disable in synaptic or is that something that I should ignore?
You find Gnome Network Manager in Synaptic. It's better to remove it entirely if you don't use it. Use Synaptic to do so.

[salefish]

Well, the real question is, should I?
And if I should, what should I remove and more specifically how?
gnome-nettool?

[salefish]

Ah-ha a break through! I followed your instructions on post number 64 of this thread and VIOLA it connects. Which obviously means I neglected to do a step you had given.
Now I am going to attempt to strengthen my security.

[wieman01]

Ah-ha a break through! I followed your instructions on post number 64 of this thread and VIOLA it connects. Which obviously means I neglected to do a step you had given.
Now I am going to attempt to strengthen my security.
Great!

If you want to remove Network Manager by the way (which is totally safe as you can reinstall it anytime) you have to do:

sudo apt-get remove network-manager-gnome
You install it issuing:

sudo apt-get install network-manager-gnome

[phekdra]

Hello - I've just moved to Ubuntu from Gentoo and having been having problems with my rt61 card. As many here I've had to follow the instructions of post #2 in order to get my wireless network to appear on startup. I've trawled through most of the pages in this thread but I haven't seen any explanation of why this works and what is the bug that's causing it. Does anyone know? Is there a link to the related bug as I was unable to find it?

Additionally I had the card working reliably under Gentoo with the latest CVS rt2x00 drivers merged into the kernel, but with Ubuntu the network keeps stalling sporadically, requiring a restart. I presume this is due to Ubuntu using older versions of the drivers. Can anyone give me any idea how often the ubuntu kernel is generally updated as I believe that the rt2x00 drivers are included as part of vanilla 2.6.24.

Don't worry - I'm not thinking of going back to Gentoo yet :p but it is a little frustrating...

Andrew

[wieman01]

Hello - I've just moved to Ubuntu from Gentoo and having been having problems with my rt61 card. As many here I've had to follow the instructions of post #2 in order to get my wireless network to appear on startup. I've trawled through most of the pages in this thread but I haven't seen any explanation of why this works and what is the bug that's causing it. Does anyone know? Is there a link to the related bug as I was unable to find it?
So far I have not put much effort into it, so I cannot answer your question... All I know is that it is necessary in quite a number of cases.

Additionally I had the card working reliably under Gentoo with the latest CVS rt2x00 drivers merged into the kernel, but with Ubuntu the network keeps stalling sporadically, requiring a restart. I presume this is due to Ubuntu using older versions of the drivers. Can anyone give me any idea how often the ubuntu kernel is generally updated as I believe that the rt2x00 drivers are included as part of vanilla 2.6.24.
I don't know when the new Ralink drivers will be available. If you have stability problems, you might want to consider my "ndiswrapper" tutorial or compile Serialmonkey's driver from source. I prefer the use of "ndiswrapper" since it works great and lets you use Network Manager for WPA(2) security.

[phekdra]

So far I have not put much effort into it, so I cannot answer your question... All I know is that it is necessary in quite a number of cases.

Ah. Perhaps I will look into it myself!


I don't know when the new Ralink drivers will be available. If you have stability problems, you might want to consider my "ndiswrapper" tutorial or compile Serialmonkey's driver from source. I prefer the use of "ndiswrapper" since it works great and lets you use Network Manager for WPA(2) security.

I might try ndiswrapper, although I've been trying to avoid that up until now! Under Gentoo I had the most problems with the Ralink drivers (and the Serialmonkey enhanced versions) which prompted my switch to the beta rt2x00 drivers which worked perfectly, and which according to lsmod I'm using at the moment, so I can only assume that the ones provided by Ubuntu are an older, more bugged version. As you say, building them from source might be a solution until the developers (Linux and Ubuntu) release the new kernel with included rt2x00 drivers. Hopefully it won't be too long... :neutral:

Andrew

[kboykowboy]

Do you have a WPA option? And how do you type in the password, what format, etc. Could you post a screenshot of the applet while you enter all the required information?

You can configure WPA manually, but that a lot more hassle.

I just type in the word its like "jeggadgodtdetlortvirkede" just type it ind like that... like it's a normal word. I may be able to take a screenshot tonight. I've been really busy.

once again thanks alot to all of you for helping!

[kboykowboy]

Do you have a WPA option? And how do you type in the password, what format, etc. Could you post a screenshot of the applet while you enter all the required information?

You can configure WPA manually, but that a lot more hassle.

Hi Wieman01
now i finaly got the screen shots taken. hope they help out?!

http://picasaweb.google.com/KboyKowboy/Ubuntu

the General-, DNS-, and Host-tabs are completely blank.

Just to sum up. This networkcard works WITH the xubuntu on my wpe encryptet network, so i ASSUME the network card is installed correctly.

thanks to all!

K

[wieman01]

Hi Wieman01
now i finaly got the screen shots taken. hope they help out?!

http://picasaweb.google.com/KboyKowboy/Ubuntu

the General-, DNS-, and Host-tabs are completely blank.

Just to sum up. This networkcard works WITH the xubuntu on my wpe encryptet network, so i ASSUME the network card is installed correctly.

thanks to all!

K
Just a shot in the dark, but would changing the network name to one that does not contain spaces (blanks) help?

[kboykowboy]

Just a shot in the dark, but would changing the network name to one that does not contain spaces (blanks) help?

it might, but it is not my network ... my girfriend lives in a place where she kinda just rents the network.... and i can't change any settings on it! sooo... all i can do is change settings on the computer!

[buccaneere]

@buccaneere:

Ok, edit your "interfaces" file and post this (replacing all contents):

The restart the network and post the output:


By the way... why do you not use Network Manager? Do you need a static IP? The script above is for DHCP.

Where's that wireless swami guru???

I had the disk out of the machine, to copy all contents onto the original Acer HDD. All went perfect, including settings. Almost.

Wireless did not auto connect this time, as it had, after you first got me linked.

I brought up 'interfaces' file, and found some extras tagged onto the end of the interfaces list:


auto lo
iface lo inet loopback

auto ath0
iface ath0 inet dhcp
wpa-driver madwifi
wpa-ssid cobweb
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk 2057043c4c9c2e031ac0ba3c960f4c5b3b8c8a5b319cbaab4a 93445f429f0727
wireless-essid cobweb
wireless-key passcobwebcobwebphrase

iface eth0 inet dhcp

So I made a back-up, deleted the vagrant electrons (in red), restarted the network, and I got the auto connect.

Is this the same bug described in post #2?

[wieman01]

@buccaneere:

You definitely need to remove those lines in red as you have done, because you cannot have 2 different setups at the time using this approach.

The reconnection issue could relate to what is outlined in post #2, yes. Check it out. Do you have other issues apart from this?

[buccaneere]

@buccaneere:

You definitely need to remove those lines in red as you have done, because you cannot have 2 different setups at the time using this approach.

The reconnection issue could relate to what is outlined in post #2, yes. Check it out. Do you have other issues apart from this?

No, no other issues. Everything that you said was spot on.

Now, on to the other three wireless machines...

[hobojjr]

so this is only for wpa? How about wep?

[wieman01]

so this is only for wpa? How about wep?
Only WEP I am afraid. Why do you not use Network Manager for WEP? Or do you need a static IP? In that case I could help. Please explain what the exact issue is and I'll try to help you out with a script.

[hobojjr]

I found http://mediakey.dk/~cc/howto-use-wep-encryption-with-ubuntu-linux/

I was setting up ubuntu server 7.10 without desktop and I didn't want to change my network setting from wep to wap because other people where using it already.

[Sordelka]

4. NetworkManager, Wifi-Radar & similar wireless configuration tools are disabled/turned off and not in use.

How to actually turn off the Network Manager?

[wieman01]

How to actually turn off the Network Manager?
Simply remove it using Synaptic. You can reinstall it later on if you would like to:

sudo apt-get remove network-manager-gnome

[din]

Hi.
after i type :
sudo gedit /etc/network/interfaces

I get :
auto lo
iface lo inet loopback

iwlist scan
lo Interface doesn't support scanning.
eth0 Interface doesn't support scanning.
eth1 No scan results
irda0 Interface doesn't support scanning.

when: iwconfig
i get info about eth1 wireless.

What i missed?
It meens i dont have wireless installed?

thanks.

[wieman01]

iwlist scan
lo Interface doesn't support scanning.
eth0 Interface doesn't support scanning.
eth1 No scan results
irda0 Interface doesn't support scanning.
No scan results generally means bad news. What hardware have you got?

Please post:

sudo lshw -C network

[din]

No scan results generally means bad news. What hardware have you got?

Please post:

Hi

A use laptop : Acer Extenza 5620Z

results:

sudo lshw -C network
*-network
description: Ethernet interface
product: NetLink BCM5787M Gigabit Ethernet PCI Express
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:02:00.0
logical name: eth0
version: 02
serial: 00:1d:72:05:08:c0
capacity: 1GB/s
width: 64 bits
clock: 33MHz
capabilities: pm vpd msi pciexpress bus_master cap_list ethernet physical mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=tg3 driverversion=3.77 firmware=5787m-v3.23 latency=0 link=no module=tg3 multicast=yes port=twisted pair
*-network DISABLED
description: Wireless interface
product: BCM94311MCG wlan mini-PCI
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:04:00.0
logical name: eth1
version: 01
serial: 00:1d:d9:68:fd:7a
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=bcm43xx driverversion=2.6.22-14-generic latency=0 link=no module=bcm43xx multicast=yes wireless=IEEE 802.11b/g

[wieman01]

@din:

Oh, broadcom. A notorious troublemaker. Look for tutorials for the bcm43xx chipset. There are a few in the forums. I am sorry I cannot advise more than that.

[DasCrushinator]

https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx/Feisty_No-Fluff

That works fine for me on both FF and GG.

[wieman01]

https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx/Feisty_No-Fluff

That works fine for me on both FF and GG.
Cool, Thanks, dude.

[din]

OK
Thanks

[DasCrushinator]

@ wieman01 and @din: No problem :)

[buccaneere]

Hey sensai Wieman...

EDITED!!!

Got it.

2 down; 2 to go.

'interfaces' file modified from '
wpa-driver madwifi', to
wpa-driver wext . Machine is a Gateway MX6xxx/broadcom 4318

Connection!:guitar:

Now, onto the new desktop build w/TP-Link wireless card (atheros), then the HPdv9xxx (???).

[wieman01]

Hey sensai Wieman...

EDITED!!!

Got it.

2 down; 2 to go.

Now, onto the new desktop build w/TP-Link wireless card (atheros), then the HPdv9xxx (???).
Cool. Keep me in the loop, dude!

[gizmom]

Hi, I am rather a beginner with Linuw and cannot connect to my wireless network. I know that it is because my network uses wpa-psk and i need to set up support for this in Linux, but have no idea how to start. I have read lots of posts on the subject on the forums but they all just confuse me further. Is there a simple method to allow Linux to communicate via WPA?
Linux can see my network and wireless card without problems but cannot pass security to actually connect.

[gizmom]

Hi, I am rather a beginner with Linuw and cannot connect to my wireless network. I know that it is because my network uses wpa-psk and i need to set up support for this in Linux, but have no idea how to start. I have read lots of posts on the subject on the forums but they all just confuse me further. Is there a simple method to allow Linux to communicate via WPA?
Linux can see my network and wireless card without problems but cannot pass security to actually connect

[Schiz0]

I can't seem to get connected to my router. I'm using a DLink WBR-1310 using WPA2 and AES on a hidden network.

The following information as requested:

# route -n

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
(There aren't any routing entries)

# iwconfig

lo no wireless extensions.

eth0 no wireless extensions.

wlan0 802.11b/g Mode:Managed Frequency=2.462 GHz
Access Point: Not-Associated Bit Rate:11 Mb/s
Retry:on Fragment thr:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

# ifconfig

eth0 Link encap:Ethernet HWaddr 00:03:25:45:0E:68
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:17

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

wlan0 Link encap:Ethernet HWaddr 00:C0:A8:DF:FB:81
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:153 dropped:189 overruns:0 frame:0
TX packets:2040 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:85680 (83.6 KB)
Interrupt:18 Memory:f886a000-f886a100

# iwlist scan

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:1B:11:54:1B:9D
ESSID:"<hidden>"
Protocol:IEEE 802.11g
Mode:Master
Channel:1
Encryption key:on
Bit Rates:54 Mb/s
Extra: Rates (Mb/s): 1 2 5.5 9 11 6 12 18 24 36 48 54
Quality:0 Signal level:0 Noise level:158
Extra: Last beacon: 64ms ago

# cat /etc/network/interfaces

auto lo
iface lo inet loopback

audo wlan0

iface wlan0 inet static
address 192.168.1.211
gateway 192.168.1.1
dns-nameservers 192.168.1.1
netmask 255.255.255.0
wpa-driver wext
wpa-ssid TheFearsomeRouter
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk fb653bab0e272741bfe3762a4a805424003c36d9c598a946f6 5bf31b472c3db6

#iface eth0 inet dhcp

# cat /etc/modprobe.d/ndiswrapper
(File not found)

# cat /etc/resolv.conf

nameserver 192.168.1.1
nameserver 4.2.2.1

I did get it working at one point with help from a guy on IRC (So I know the hardware works). However, I'm completely stuck now. Thanks for any help.

[wieman01]

Hi, I am rather a beginner with Linuw and cannot connect to my wireless network. I know that it is because my network uses wpa-psk and i need to set up support for this in Linux, but have no idea how to start. I have read lots of posts on the subject on the forums but they all just confuse me further. Is there a simple method to allow Linux to communicate via WPA?
Linux can see my network and wireless card without problems but cannot pass security to actually connect
The easiest option is Network Manager which happens to be the default network application that you see in the upper right corner. It should let you connect to all sorts of wireless networks including WPA secured ones. If you don't have a WPA option, then your wireless adapter does not support it because...

A. the current driver cannot handle WPA,
B. the hardware is not capable of WPA.

To begin with, what hardware have you got? Please also post the results of this:

sudo iwlist scan
From command line please. Enter your password when prompted for it.

[wieman01]

I can't seem to get connected to my router. I'm using a DLink WBR-1310 using WPA2 and AES on a hidden network.

The following information as requested:

# iwlist scan

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:1B:11:54:1B:9D
ESSID:"<hidden>"
Protocol:IEEE 802.11g
Mode:Master
Channel:1
Encryption key:on
Bit Rates:54 Mb/s
Extra: Rates (Mb/s): 1 2 5.5 9 11 6 12 18 24 36 48 54
Quality:0 Signal level:0 Noise level:158
Extra: Last beacon: 64ms ago

I did get it working at one point with help from a guy on IRC (So I know the hardware works). However, I'm completely stuck now. Thanks for any help.
The script looks fine, however, the scan is not too promising. The scan should recognize the WPA network as such and should mention that is a WPA secured one. In your card it doesn't so I suspect that the kernel driver cannot handle it.

What chipset is your card and what driver are you using in case you know?

[Schiz0]

The script looks fine, however, the scan is not too promising. The scan should recognize the WPA network as such and should mention that is a WPA secured one. In your card it doesn't so I suspect that the kernel driver cannot handle it.

What chipset is your card and what driver are you using in case you know?

The output for lshw for the wireless adapter:

*-network
description: Wireless interface
product: RTL-8185 IEEE 802.11a/b/g Wireless LAN Controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 9
bus info: pci@0000:08:09.0
logical name: wlan0
version: 20
serial: 00:c0:a8:df:fb:81
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=rtl8180 ip=192.168.1.211 latency=64 maxlatency=64 mingnt=32 module=r8180 multicast=yes wireless=802.11b/g


Thanks for the help, I appreciate the time.

[wieman01]

The output for lshw for the wireless adapter:

*-network
description: Wireless interface
product: RTL-8185 IEEE 802.11a/b/g Wireless LAN Controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 9
bus info: pci@0000:08:09.0
logical name: wlan0
version: 20
serial: 00:c0:a8:df:fb:81
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=rtl8180 ip=192.168.1.211 latency=64 maxlatency=64 mingnt=32 module=r8180 multicast=yes wireless=802.11b/g


Thanks for the help, I appreciate the time.
Ah... bad news. I don't think the rtl8180 supports WPA... You need to do some further research, but I have not heard much good stuff about it (at least in that respect).

[kboykowboy]

Hey All -
so i assume there is no way of getting on the wpa network onless you have admin rights on it and can change the settings of the router?!

wish all a nice december!

[loopiv]

Thanks for the howto. It worked for me, but I needed to do the below:

-
apt-get remove network-manager
apt-get install ndiswrapper-utils-1.9 ndiswrapper-common
download the driver file from linksys. It's an EXE file, but you can unzip it and find the driver for version 4.
depmod -a
modprobe ndiswrapper
ndiswrapper -i <version 4 .inf file>
blacklist the included rt2x00 and rt2500 drivers. Edited /etc/modprobe.d/blacklist and added the following at the end of the file:



blacklist rt2500usb
blacklist rt2x00usb
blacklist rt2x00lib

- add ndiswrapper to /etc/modules
- add the following to /etc/init.d/rc.local


/etc/init.d/networking restart
- reboot

[wieman01]

Hey All -
so i assume there is no way of getting on the wpa network onless you have admin rights on it and can change the settings of the router?!

wish all a nice december!
Yes, that's pretty much it. You need to know the network key or have access to the router. Two options in fact.

[kboykowboy]

Yes, that's pretty much it. You need to know the network key ...

What's the network key? i know pretty much everything about the network, but can't change any of the settings !

[wieman01]

What's the network key? i know pretty much everything about the network, but can't change any of the settings !
The network key is the secret WPA passphrase if you know what I mean. A password that lets you access the wireless network. Have you got it?

[merlin666]

Wow this howto is getting long. Anyway, I got the wpa going a few months ago but it was not consistent. I tried again with new ndiswrapper, but have no success. iwlist -scan shows all sorts of networks around on eth1, just not mine. I changed wlan0 to eth1 in the interfaces file, but that did not help. Are there any other diagnostics that I could try?

[wieman01]

Wow this howto is getting long. Anyway, I got the wpa going a few months ago but it was not consistent. I tried again with new ndiswrapper, but have no success. iwlist -scan shows all sorts of networks around on eth1, just not mine. I changed wlan0 to eth1 in the interfaces file, but that did not help. Are there any other diagnostics that I could try?
Man, that's sort of strange. You have the ability to see other networks but not your own? How odd is that?! Would you mind posting the results of:

sudo iwlist scan
Let's see what is going on... What hardware have you got?

[merlin666]

Man, that's sort of strange. You have the ability to see other networks but not your own? How odd is that?! Would you mind posting the results of:

Let's see what is going on... What hardware have you got?

I have an emachines laptop running 64-bit Gutsy (netbc564 driver), dlink 524 router. I rebooted the router and now I can see my MAC address listed, also the iwlist scan shows my network, though as cell 05 and not on top as I would expect. strange thing is that there's also an eth1:avahi. I had this before and it seems to be an indicator of some dysfunction. So although I seem to be connected, there is no transmission of data once I unplug the network cable and disable eth0.

rolf@ubuntu:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:14:D1:35:36:62
ESSID:"TRENDnet"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:40/100 Signal level:-70 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 02 - Address: 00:14:BF:8D:FB:97
ESSID:"linksys"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:87/100 Signal level:-40 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 03 - Address: 00:40:96:A1:01:18
ESSID:"TELUS"
Protocol:IEEE 802.11b
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:17/100 Signal level:-85 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 04 - Address: 00:16:B6:6B:AA:69
ESSID:"Above0"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.432 GHz (Channel 5)
Quality:12/100 Signal level:-88 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : PSK
Cell 05 - Address: 00:11:95:37:5D:CD
ESSID:"aldersbrook"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:87/100 Signal level:-40 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : PSK

rolf@ubuntu:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:03:25:15:5F:EB
inet addr:192.168.0.101 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::203:25ff:fe15:5feb/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4868 errors:0 dropped:0 overruns:0 frame:0
TX packets:3960 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:5453931 (5.2 MB) TX bytes:361309 (352.8 KB)
Interrupt:23 Base address:0x1800

eth1 Link encap:Ethernet HWaddr 00:90:4B:8C:F9:E7
inet6 addr: fe80::290:4bff:fe8c:f9e7/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:974 errors:0 dropped:0 overruns:0 frame:0
TX packets:991 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:110062 (107.4 KB) TX bytes:138388 (135.1 KB)
Interrupt:18 Memory:d0000000-d0002000

eth1:avah Link encap:Ethernet HWaddr 00:90:4B:8C:F9:E7
inet addr:169.254.11.50 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Interrupt:18 Memory:d0000000-d0002000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:35 errors:0 dropped:0 overruns:0 frame:0
TX packets:35 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3391 (3.3 KB) TX bytes:3391 (3.3 KB)

rolf@ubuntu:~$

[wieman01]

I have an emachines laptop running 64-bit Gutsy (netbc564 driver), dlink 524 router. I rebooted the router and now I can see my MAC address listed, also the iwlist scan shows my network, though as cell 05 and not on top as I would expect. strange thing is that there's also an eth1:avahi. I had this before and it seems to be an indicator of some dysfunction. So although I seem to be connected, there is no transmission of data once I unplug the network cable and disable eth0.
Sorry... I have not smart advice to offer, really. Beats me.

[parameter]

This post is from a year and a half ago. Three new versions of Ubuntu been released since the post was made. Is this post still relevant?

[wieman01]

This post is from a year and a half ago. Three new versions of Ubuntu been released since the post was made. Is this post still relevant?
According to the poll (which I keep an eye on), yes, it is. There is a support thread where you should have posted your question... see post #2. There you see it is still relevant (hope this changes though after the next release).

[kboykowboy]

The network key is the secret WPA passphrase if you know what I mean. A password that lets you access the wireless network. Have you got it?

YEs - i have all info about the network, but i just can't change it (since it is not my network to administrate). as i wrote earlyer the network is called "lykkes Net" and i think you asked if i could change the name so there was no blank spaces in it... and that's a "no"

Marry chrismas !!

[buccaneere]

Some users reported (including myself) that the network has to be restarted every time after startup... Apparently this is a bug.

Here is a workaround that helps restart the network during boot so that one does not have to do it manually after logging on to the system.

Create startup script:

Add this line & save file:

Change permission (executable):

Create symbolic link:

[Note: You may have to choose a boot sequence other than S40.]

Restart...

Oookay... Where's wieman01WKB (wireless knowledge base)

How do I determine the value for 'boot sequence'; i. e., S40

2 of my 4 boxes have atheros wireless, and need the 'post-boot restart fix'.

Thanks again!!!

[wieman01]

Oookay... Where's wieman01WKB (wireless knowledge base)

How do I determine the value for 'boot sequence'; i. e., S40

2 of my 4 boxes have atheros wireless, and need the 'post-boot restart fix'.

Thanks again!!!
Hey there, buddy!

Use S40 to begin with. Change it to another value (e.g. S50) if that does not work for you. But S40 should really do.

[ebutton]

Wow! This thread certainly IS STILL VALID! I just got Gutsy/ Intel 3945ABG working with a "full up" WPA2 Enterprise network in my wireless lab at work.

That might have happened a few days sooner, but I thought something was missing from this HowTo - how to install the client certificate from my CA.

Why is that step, required with XP, not needed? I don't understand how the client can authenticate my RADIUS server's Certificate, since it's from a local/private CA.

By the way, I'm using a Cisco router for DHCP service and a ZeroShell virtual appliance (inside VM Player on an XP host) as my CA and RADIUS servers. ZeroShell also can be a DHCP server.

[ebutton]

Hi.
If you are still having problems, go back to the beginning of this thread and find the variations of WPA, PSK, PEAP, and so forth that have been edited in. (Note also the Change Log a little further down that first page.) Read a little more about WEP, WPA, and WPA2 (Google) if you need to better understand the very confusing and huge quantity of acronyms and options in wireless security. Then you should be able to quickly choose which method you need.

For me, I needed to read the caveat about not putting quotation marks around the SSID and that I could substitute eth1 for wlan0 in the /etc/networks/interfaces file. Other than that, I just did a copy/paste of the section "***Sample conf. PEAP, AES, DHCP, ESSID broadcast***" to my interfaces file, and a copy/paste of the network restart command to a shell window. It worked immediately.

In fact, it was anticlimactic after all the research/learning curve activity. Still I was very amazed and happy - and very thankful to wieman01 for doing the "heavy lifting" for us.

Warm Regards,
EdB

[wieman01]

In fact, it was anticlimactic after all the research/learning curve activity. Still I was very amazed and happy - and very thankful to wieman01 for doing the "heavy lifting" for us.
And you are very welcome. Thanks for letting me know this still works. :-)

[jago25_98]

This is a very long thread and I've been keeping off replying for as long as I can.

But now the question.

What else do you guys use for network configuration? I use knetworkmanager so I don't have to go through all the guff you guys are going through on this thread... only it could be working better.


I've been using NetworkManager via knetworkmanager, and the problem is it often doesn't allow me to select the correct encryption (WPA), listing only WEP. I then have to use `Connect to other wireless network` to then successfully connect via WPA.

Also, it doesn't connect on it's own. The connect button is greyed out until I change an option and put it back again.

Try out these helping tools. You may need them if you travel to new networks. Perhaps there is a better network config aide available? Command line perhaps?

[wieman01]

This is a very long thread and I've been keeping off replying for as long as I can.

But now the question.

What else do you guys use for network configuration? I use knetworkmanager so I don't have to go through all the guff you guys are going through on this thread... only it could be working better.


I've been using NetworkManager via knetworkmanager, and the problem is it often doesn't allow me to select the correct encryption (WPA), listing only WEP. I then have to use `Connect to other wireless network` to then successfully connect via WPA.

Also, it doesn't connect on it's own. The connect button is greyed out until I change an option and put it back again.

Try out these helping tools. You may need them if you travel to new networks. Perhaps there is a better network config aide available? Command line perhaps?
Personally I use KNetworkManager (Kubuntu), but as it does not support static IP addresses, it is of limited use as far as my local network is concerned. Hence this thread. Also there is no reconnection issue, this version lets you connect at boot. So therefore the thread is still valid, although I wished it wasn't.

[buccaneere]

Hey there, buddy!

Use S40 to begin with. Change it to another value (e.g. S50) if that does not work for you. But S40 should really do.

Both atheros chipset-equipped boxes took boot sequence value S40. Good job!

Why S40 tho'?

And what DID we do? Add a totally new startup process? Why could not the restart command be added to an existing process?

[buccaneere]

I've been using NetworkManager via knetworkmanager, and the problem is it often doesn't allow me to select the correct encryption (WPA), listing only WEP.



I had this problem.

The Broadcom-equipped machine ( 4318 ) was properly configured, thanks to wieman. Then, I updated from Edgy, to 7.04, and lost configuration, and all clues to resolve again. The GUI encryption option was as yours - only WEP. :confused:

I could not re-configure. It was a new install; I had to re-install.

I know only that it was a driver conflict gig.

[wieman01]

Both atheros chipset-equipped boxes took boot sequence value S40. Good job!

Why S40 tho'?

And what DID we do? Add a totally new startup process? Why could not the restart command be added to an existing process?
S40 is sort of reserved for networking. Each boot range is reserved for certain processes, although I cannot remember all of them. S40 is networking, but of course you could change that.

What we did is we simply restarted the network b/c wpa-supplicant requires you to do so. So no new processes has been added, we merely "killed" the old one and started a new one. As simple as that.

Google for "boot sequence, linux, run levels" to learn more about it. :-)

[SonWon]

Help! :(

Can't get wireless working using wpa-1, works fine with WEP. Using Ubuntu 6.10 Edgy Eft. Here is the information:


route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.128.0 * 255.255.255.0 U 0 0 0 vmnet1
192.168.99.0 * 255.255.255.0 U 0 0 0 vmnet8



iwconfig
lo no wireless extensions.

eth1 unassociated ESSID:"RDC"
Mode:Managed Frequency=2.412 GHz Access Point: 00:18:F8:75:D3:5B
Bit Rate:0 kb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:710 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

eth0 no wireless extensions.

vmnet1 no wireless extensions.

vmnet8 no wireless extensions.



sudo iwlist scan
lo Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:18:F8:75:D3:5B
ESSID:"RDC"
Protocol:IEEE 802.11bg
Mode:Master
Channel:1
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=73/100 Signal level=-54 dBm
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Extra: Last beacon: 2980ms ago
Cell 02 - Address: 00:0F:B5:E5:7D:CE
ESSID:"Cutco"
Protocol:IEEE 802.11bg
Mode:Master
Channel:11
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=59/100 Signal level=-65 dBm
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Extra: Last beacon: 3004ms ago
Cell 03 - Address: 00:1C:58:6D:A5:70
ESSID:"<hidden>"
Protocol:IEEE 802.11bg
Mode:Master
Channel:11
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=48/100 Signal level=-72 dBm
Extra: Last beacon: 3004ms ago
Cell 04 - Address: 00:50:F2:CD:A9:4A
ESSID:"MSHOME"
Protocol:IEEE 802.11b
Mode:Master
Channel:6
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Quality=31/100 Signal level=-81 dBm
Extra: Last beacon: 3108ms ago
Cell 05 - Address: 00:0D:72:B6:39:01
ESSID:"2WIRE663"
Protocol:IEEE 802.11b
Mode:Master
Channel:6
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
Quality=33/100 Signal level=-80 dBm
Extra: Last beacon: 3124ms ago
Cell 06 - Address: 00:15:62:8C:B5:F0
ESSID:"<hidden>"
Protocol:IEEE 802.11bg
Mode:Master
Channel:1
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=37/100 Signal level=-78 dBm
Extra: Last beacon: 3240ms ago
Cell 07 - Address: 00:1B:5B:F3:5F:09
ESSID:"2WIRE162"
Protocol:IEEE 802.11bg
Mode:Master
Channel:2
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=31/100 Signal level=-81 dBm
Extra: Last beacon: 7868ms ago

eth0 Interface doesn't support scanning.

vmnet1 Interface doesn't support scanning.

vmnet8 Interface doesn't support scanning.



sudo lshw -C network
*-network:0
description: Wireless interface
product: PRO/Wireless 2200BG Network Connection
vendor: Intel Corporation
physical id: a
bus info: pci@00:0a.0
logical name: eth1
version: 05
serial: 00:0e:35:0c:1b:85
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ipw2200 driverversion=1.1.2kmprq firmware=ABG:9.0.2.6 (Mar 22 2005) link=yes multicast=yes wireless=IEEE 802.11g
resources: iomemory:f0000000-f0000fff irq:201
*-network:1
description: Ethernet interface
product: VT6102 [Rhine-II]
vendor: VIA Technologies, Inc.
physical id: 12
bus info: pci@00:12.0
logical name: eth0
version: 74
serial: 00:40:d0:53:3d:af
size: 10MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegociation
configuration: autonegociation=on broadcast=yes driver=via-rhine driverversion=1.2.0-2.6 duplex=half link=no multicast=yes port=MII speed=10MB/s
resources: ioport:e300-e3ff iomemory:f0001900-f00019ff irq:209



/etc/network/interfaces
auto lo
iface lo inet loopback


iface eth0 inet dhcp

auto eth2
iface eth2 inet dhcp

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp



auto eth0

iface eth1 inet dhcp
wpa-driver wext
wpa-ssid RDC
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <my_hex_key>




auto eth1

[graysn05]

I'm connecting to a network that uses wpa, tkip, and peap

my /etc/network/interfaces is


iface eth1 inet dhcp
wpa-driver wext
wpa-ssid UNI-Wireless
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-eap PEAP
wpa-key-mgmt WPA-EAP
wpa-identity ad-its\compsci
wpa-password **********

I've also set up the startup script from post #2

This all works but the startup is amazingly slow. is there a way to have the script just restart the wireless connection and not the ethernet connection? (Eth0) in my case.

[SonWon]

Shameless bump.

[buccaneere]

I'm connecting to a network that uses wpa, tkip, and peap

my /etc/network/interfaces is


iface eth1 inet dhcp
wpa-driver wext
wpa-ssid UNI-Wireless
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-eap PEAP
wpa-key-mgmt WPA-EAP
wpa-identity ad-its\compsci
wpa-password **********

I've also set up the startup script from post #2

This all works but the startup is amazingly slow. is there a way to have the script just restart the wireless connection and not the ethernet connection? (Eth0) in my case.

You say your startup is slow.

???

Do you mean connection speed maybe?

I found a thread for configurin' wireless, which said that of two ways to configure wireless [broadcom, I think]. one of the two supports only 11megs, and the other supports 54megs connection speed.

Just a thought........

[wieman01]

Help! :(

Can't get wireless working using wpa-1, works fine with WEP. Using Ubuntu 6.10 Edgy Eft. Here is the information:


/etc/network/interfaces
auto lo
iface lo inet loopback


iface eth0 inet dhcp

auto eth2
iface eth2 inet dhcp

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp



auto eth0

iface eth1 inet dhcp
wpa-driver wext
wpa-ssid RDC
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <my_hex_key>

auto eth1

You script looks fine in fact. Please do this for me and post the results:

sudo ifdown -v eth1

sudo ifup -v eth1
In the meantime please check if you have somehow made a mistake while generating the pass phrase. Please also check post #2 of this thread. You might have to restart the network.

[wieman01]

I'm connecting to a network that uses wpa, tkip, and peap

my /etc/network/interfaces is


iface eth1 inet dhcp
wpa-driver wext
wpa-ssid UNI-Wireless
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-eap PEAP
wpa-key-mgmt WPA-EAP
wpa-identity ad-its\compsci
wpa-password **********

I've also set up the startup script from post #2

This all works but the startup is amazingly slow. is there a way to have the script just restart the wireless connection and not the ethernet connection? (Eth0) in my case.
Reverting to a static IP address instead of DHCP will definitely speed things up. That's the only option I can offer.

[SonWon]

You script looks fine in fact. Please do this for me and post the results:

Quote:
sudo ifdown -v eth1

Quote:
sudo ifup -v eth1

sudo ifdown -v eth1

Configuring interface eth1=eth1 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.eth1.pid -lf /var/lib/dhcp3/dhclient.eth1.leases eth1
There is already a pid file /var/run/dhclient.eth1.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:0e:35:0c:1b:85
Sending on LPF/eth1/00:0e:35:0c:1b:85
Sending on Socket/fallback
DHCPRELEASE on eth1 to 192.168.1.1 port 67
ifconfig eth1 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.eth1.pid
Stopped /sbin/wpa_supplicant (pid 8621).

sudo ifup -v eth1

ifup: interface eth1 already configured

[wieman01]

sudo ifdown -v eth1

Configuring interface eth1=eth1 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.eth1.pid -lf /var/lib/dhcp3/dhclient.eth1.leases eth1
There is already a pid file /var/run/dhclient.eth1.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:0e:35:0c:1b:85
Sending on LPF/eth1/00:0e:35:0c:1b:85
Sending on Socket/fallback
DHCPRELEASE on eth1 to 192.168.1.1 port 67
ifconfig eth1 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.eth1.pid
Stopped /sbin/wpa_supplicant (pid 8621).

sudo ifup -v eth1

ifup: interface eth1 already configured
First off I would remove Network Manager (you can reinstall it later on). Second, what network hardware have you got?

[SonWon]

what network hardware have you got?

Intel PRO/Wireless 2200BG Network



I would remove Network Manager

I move around a lot will this make it harder to reconfigure the wireless stuff? I can edit each time if needed but I guess I am lazy. :)


Thank you for your help.

[wieman01]

Intel PRO/Wireless 2200BG Network




I move around a lot will this make it harder to reconfigure the wireless stuff? I can edit each time if needed but I guess I am lazy. :)


Thank you for your help.
IPW2200BG? Man, you don't need this tutorial. :-) Why don't you use Network Manager instead? It only support DHCP (no static IP addresses) but it does a fairly good job, in particular if you need roaming. Why bother (politely asked)?

[SonWon]

Why don't you use Network Manager instead?

Even after just over a year of running Ubuntu I am still a nub. :)

When I goto the Network Manager applet eth0 and eth1 do not show in the list?

I also never see the signal strength on the gnome menu bar?

And the wireless network does work with a wep or open network which I can configure from the System | Administration | Networking menu pick (Network Administration Tool?).

Maybe edgy eft problem?

Thank you again,

[wieman01]

Maybe edgy eft problem?

Thank you again,
Not sure, really. But update "/etc/network/interfaces" so that it looks like:

auto lo
iface lo inet loopback

Only 2 lines left, don't be afraid, you can restore the contents anytime you like. :-) Then reboot the PC and see if NM detects your interfaces.

[graysn05]

Reverting to a static IP address instead of DHCP will definitely speed things up. That's the only option I can offer.

I work for a university and we are trying to get the dual boot laptops to connect to wireless for active directory authentication. I don't have the option to static IP since someone else manages the wireless. Did anyone get the script from post #32 to work? That seemed just restart the wireless connection at startup rather than all networking. When the machines starts one can see when this networking restart happens and it restarts the wired connection first which is where it hangs for a little while.

Thanks.

[wieman01]

I work for a university and we are trying to get the dual boot laptops to connect to wireless for active directory authentication. I don't have the option to static IP since someone else manages the wireless. Did anyone get the script from post #32 to work? That seemed just restart the wireless connection at startup rather than all networking. When the machines starts one can see when this networking restart happens and it restarts the wired connection first which is where it hangs for a little while.

Thanks.
Question... Does Network Manager not support PEAP? I thought it does. That would solve all your problems. The latest version (Gutsy) should do the job.

[elamericano]

Question... Does Network Manager not support PEAP?
NetworkManager supports PEAP.

[SonWon]

Only 2 lines left, don't be afraid, you can restore the contents anytime you like. Then reboot the PC and see if NM detects your interfaces.

I was confused, I do have the icon on the Gnome menubar, sorry. I did delete all of the lines but the two and after reboot no difference. When I go to configure the network setting via the icon there are no settings for WEP, PSA, etc.? Only thing available is SSID, password type, network passwork.

Thank you,

[ilektron]

Thank you to whomever set up these wireless tutorials. After days of searching finally a tutorial on using /etc/network/interfaces for wireless w/o a gui. Is all this documented somewhere?

[wieman01]

Thank you to whomever set up these wireless tutorials. After days of searching finally a tutorial on using /etc/network/interfaces for wireless w/o a gui. Is all this documented somewhere?
It is documented here. :-) I could not find any other documentation back then (2006) but it might have changed in the meantime, who knows.

[kboykowboy]

YEs - i have all info about the network, but i just can't change it (since it is not my network to administrate). as i wrote earlyer the network is called "lykkes Net" and i think you asked if i could change the name so there was no blank spaces in it... and that's a "no"

Marry chrismas !!

bounce .... Think this threat shows Ubuntu still have some way to go before it is really human... hope the next dist. will have good wpa support - untill then maybe i just have to give up...

[graysn05]

Question... Does Network Manager not support PEAP? I thought it does. That would solve all your problems. The latest version (Gutsy) should do the job.

It does support PEAP, but we need the computer to connect at startup so that it connects before attempting to connect to the ldap server. i'm thinking about writing my own script to restart just the wireless connection rather than calling /etc/init.d/networking restart, we'll see how it goes.

[wieman01]

It does support PEAP, but we need the computer to connect at startup so that it connects before attempting to connect to the ldap server. i'm thinking about writing my own script to restart just the wireless connection rather than calling /etc/init.d/networking restart, we'll see how it goes.
Then simply do a "ifdown" and "ifup". And revert to using a static IP address which will speed up the boot process. Keep us posted.

[rootware]

Just one question please, where should I write my WPA-2 password to make it permanent?

Currently I write @ every boot-time the password. And how can I make to make the wlan card to connect at the boot time? Because I have to wait after the sistem has been loaded about 10 seconds for it to communicate with the wireless router.

[rootware]

Just one question please, where should I write my WPA-2 password to make it permanent?

Currently I write @ every boot-time the password. And how can I make to make the wlan card to connect at the boot time? Because I have to wait after the sistem has been loaded about 30 seconds for it to communicate with the wireless router.

[wieman01]

Just one question please, where should I write my WPA-2 password to make it permanent?

Currently I write @ every boot-time the password. And how can I make to make the wlan card to connect at the boot time? Because I have to wait after the sistem has been loaded about 30 seconds for it to communicate with the wireless router.
Permanent? Did you follow this tutorial or are you using Network Manager for wireless networking? What version of Ubuntu are you on?

[rootware]

Permanent? Did you follow this tutorial or are you using Network Manager for wireless networking? What version of Ubuntu are you on?

Greetings!

I am using my network manager GUI from KDE and I am using Feisty!

Thanks!

[wieman01]

Greetings!

I am using my network manager GUI from KDE and I am using Feisty!

Thanks!
Gutsy will let you connect at startup. So upgrading will certainly help as Gutsy has a new version of NM,

[rootware]

Gutsy will let you connect at startup. So upgrading will certainly help as Gutsy has a new version of NM,

I can't upgrade to Gutsy because it's a failure on my HP Pavilion laptop :(

[wieman01]

I can't upgrade to Gutsy because it's a failure on my HP Pavilion laptop :(
Alternatively, install NM from scratch by compiling it yourself. Sorry, I cannot give you any further advice.

[Axtilmor]

Hello,

On Gutsy, I'm trying to connect a Netgear MA311 PCI card to a Linksys WRT54G wireless router using WPA(1), TKIP, and DHCP.

At first, I tried using Network Manager. My network's name showed up on the list of wireless networks, but when I tried to connect to it, the only security types that I was allowed to select were WEP and LEAP. I tried selecting "Connect to Other Network" and was able to enter the proper information, but the network manager showed the connection as having no bars, and I wasn't able to access the network.

After some Googling I found this excellent tutorial, but I'm still having some difficulties. Here's the information requested by the tutorial:

route:

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
link-local * 255.255.0.0 U 0 0 0 wlan1
default * 0.0.0.0 U 1000 0 0 wlan1

iwconfig:

wifi0 IEEE 802.11b ESSID:"test" Nickname:""
Mode:Managed Frequency:2.437 GHz Access Point: None
Bit Rate:2 Mb/s Sensitivity=1/3
Retry short limit:8 RTS thr:off Fragment thr:off
Power Management:off

wlan1 IEEE 802.11b ESSID:"test" Nickname:""
Mode:Managed Frequency:2.437 GHz Access Point: None
Bit Rate:2 Mb/s Sensitivity=1/3
Retry short limit:8 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=0/70 Signal level=-73 dBm Noise level=-73 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:16 Missed beacon:0

sudo iwlist scan:

wifi0 Scan completed :
Cell 01 - Address: 00:13:10:F0:34:F1
ESSID:"OMFGSTFU"
Mode:Master
Frequency:2.417 GHz (Channel 2)
Signal level=-79 dBm Noise level=-90 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:resp_rate=10

wlan1 No scan results

sudo lshw -C network:

*-network:0
description: Wireless interface
product: Prism 2.5 Wavelan chipset
vendor: Intersil Corporation
physical id: b
bus info: pci@0000:00:0b.0
logical name: wifi0
version: 01
serial: 00:09:5b:11:9d:af
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list logical wireless ethernet physical
configuration: broadcast=yes driver=hostap driverversion=0.4.4-kernel firmware=1.3.6 latency=32 module=hostap_pci multicast=yes wireless=IEEE 802.11b
*-network:1 DISABLED
description: Ethernet interface
product: RTL-8139/8139C/8139C+
vendor: Realtek Semiconductor Co., Ltd.
physical id: d
bus info: pci@0000:00:0d.0
logical name: eth0
version: 10
serial: 00:e0:4c:d8:58:4e
size: 10MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=8139too driverversion=0.9.28 duplex=half latency=32 link=no maxlatency=64 mingnt=32 module=8139too multicast=yes port=MII speed=10MB/s


Here's my interfaces file (which still bears a few scars from me trying to figure this out):

auto lo
iface lo inet loopback

#auto eth1
#iface eth1 inet dhcp

#auto eth2
#iface eth2 inet dhcp

#auto ath0
#iface ath0 inet dhcp

#auto wlan0
#iface wlan0 inet dhcp

auto wlan1
iface wlan1 inet dhcp
wpa-driver hostap
wpa-ssid OMFGSTFU
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <MY HEX SHARED KEY>

And here's what I get when I try to do a /etc/init.d/networking restart:

econfiguring network interfaces...
There is already a pid file /var/run/dhclient.wlan1.pid with pid 5833
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/wlan1/00:09:5b:11:9d:af
Sending on LPF/wlan1/00:09:5b:11:9d:af
Sending on Socket/fallback
ioctl[PRISM2_IOCTL_PRISM2_PARAM]: Operation not supported
There is already a pid file /var/run/dhclient.wlan1.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/wlan1/00:09:5b:11:9d:af
Sending on LPF/wlan1/00:09:5b:11:9d:af
Sending on Socket/fallback
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 13
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
[ OK ]
axtilmor@axtilmor-desktop:~$ sudo /etc/init.d/networking restart >> network_rest
art.txt
There is already a pid file /var/run/dhclient.wlan1.pid with pid 6103
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/wlan1/00:09:5b:11:9d:af
Sending on LPF/wlan1/00:09:5b:11:9d:af
Sending on Socket/fallback
ioctl[PRISM2_IOCTL_PRISM2_PARAM]: Operation not supported
There is already a pid file /var/run/dhclient.wlan1.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/wlan1/00:09:5b:11:9d:af
Sending on LPF/wlan1/00:09:5b:11:9d:af
Sending on Socket/fallback
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 3
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

I'm running out of ideas on what I should be searching the net for to solve my problem, so any help would be appreciated.

[wieman01]

@Axtilmor:

This is a tough one... But let's start with a few observations that I have made.

A. Your network interface seems to be "wifi0" rather than "wlan1".
B. The scan results list your network ("OMFGSTFU"), however, there is no mention of WPA. This could be either because you are using WEP or because the current driver (Prism) does not support WPA (that's what I suspect).
C. This error message kind of confirms that there is no WPA support:

ioctl[PRISM2_IOCTL_PRISM2_PARAM]: Operation not supported
D. The script looks ok apart from the fact that the network interface is incorrect. Also I do not know if you have generated the passphrase correctly (wpa-psk). Please check the relevant section in my tutorial once again. The right scipt would be:

auto wifi0
iface wifi0 inet dhcp
wpa-driver hostap
wpa-ssid OMFGSTFU
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <MY HEX SHARED KEY>
If all this fails, you can replace the current Prism driver with "ndiswrapper" and the native Windows driver. But let's try this first.

[Axtilmor]

I tried changing the interfaces file to list wifi0 as you mentioned, but got the same sort of output upon running /etc/init.d/networking restart. Given that this card is very old, I feel like you're right about it being the driver. I'll try changing the driver tomorrow when its not so late.

[wieman01]

I tried changing the interfaces file to list wifi0 as you mentioned, but got the same sort of output upon running /etc/init.d/networking restart. Given that this card is very old, I feel like you're right about it being the driver. I'll try changing the driver tomorrow when its not so late.
It is a wireless B card, isn't it? So it must be fairly old and I doubt that the Windows driver supports WPA... But you should know as you have used it before I guess.

It is definitely on the list of supported devices ("ndiswrapper"):

http://ndiswrapper.sourceforge.net/joomla/index.php?/component/option,com_openwiki/Itemid,33/id,list_m-n/

Try to get hold of an up-to-date Windows driver that specifically supports WPA/WPA2. I can guide you through the installation process if you like to.

[lunatico]

Hello,
This is my first post to this forum, I have read it all and tried several things but I'm still having problems.
I have a IBM Thinkpad T61 with an Atheros wifi card, Ubuntu loaded the madwifi drivers and I installed the wpa-supplicant. The wireless work very well on my home wireless which I have open, with no encryption just MAC address filtering.
I am on my college network. I have attached the instructions they provide for Windows XP and Vista and Mac OS to configure the laptop to work with this network, and I have also attached a screenshot of the settings I have used on my nm-applet which have worked but is very hard to get the connection and once you get connected it will be very unstable.
Please help. :)

[wieman01]

Hello,
This is my first post to this forum, I have read it all and tried several things but I'm still having problems.
I have a IBM Thinkpad T61 with an Atheros wifi card, Ubuntu loaded the madwifi drivers and I installed the wpa-supplicant. The wireless work very well on my home wireless which I have open, with no encryption just MAC address filtering.
I am on my college network. I have attached the instructions they provide for Windows XP and Vista and Mac OS to configure the laptop to work with this network, and I have also attached a screenshot of the settings I have used on my nm-applet which have worked but is very hard to get the connection and once you get connected it will be very unstable.
Please help. :)
This could be due to a number of reasons, but it is impossible for me to find out what the real issue is. Plus it's not really related to the topic of this thread. Please open up a new thread and feel free to send me the link by PM.

[lunatico]

Sorry for my past irrelevant message. Now this one I think does have a lot to do with this thread. Basically I'm trying to setup the interfaces file to work with DHCP, WPA-Enterprise, TKIP, PEAP, EAP-MSCHAPv2, with fast reconnect. If I run iwconfig it looks like it is getting associated with the AP but not authenticated. I have attached on the file all the output you request at the beginning of this howto.
I think I have something wrong on the way I write the interfaces file, the order of things or something like that. If it has relevance I would appreciate all help provided.

[wieman01]

Sorry for my past irrelevant message. Now this one I think does have a lot to do with this thread. Basically I'm trying to setup the interfaces file to work with DHCP, WPA-Enterprise, TKIP, PEAP, EAP-MSCHAPv2, with fast reconnect. If I run iwconfig it looks like it is getting associated with the AP but not authenticated. I have attached on the file all the output you request at the beginning of this howto.
I think I have something wrong on the way I write the interfaces file, the order of things or something like that. If it has relevance I would appreciate all help provided.
No problem. The scripts looks fine. Could you post this as well please:

sudo ifdown -v ath0

sudo ifup -v ath0
I am not entirely sure your card really supports PEAP, but let's see.

EDIT:
Please change the script so that is looks like this (SSID broadcast):

auto ath0
iface ath0 inet dhcp
wpa-driver madwifi
wpa-ssid COMPSCIwireless
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-EAP
wpa-eap PEAP
wpa-phase2 auth=MSCHAPV2
wpa-identity castromd
wpa-password xoo6Quud

[lunatico]

Thank you very much for your help! Find attached the output after I changed what you said plus the two other commands you ask.
Let me mention that I have been able to connect using the nm-applet, on my first post on this thread you can find a screenshot of the configuration used. As I said, I have been able (2 or 3 times) to connect, but is very rare and the connection will not stay up for long.
I do think my card works fine with PEAP because I use it on Windows XP and Vista with no problem (I have dual boot).

[maycitybomber]

My Wifi ESSID is labelled as MY_WIFI
I have input the HEX Passphrase; encryption being WPA1+WPA2 Mixed Mode
followed instructions.. is still not working any help??

route
Brings up:

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface

iwconfig
Brings up:
lo no wireless extensions.

eth0 no wireless extensions.

ath0 IEEE 802.11 ESSID:""
Mode:Managed Frequency:2.427 GHz Access Point: Not-Associated
Bit Rate:1 Mb/s Tx-Power:18 dBm Sensitivity=0/3
Retry:off RTS thr:off Fragment thr:off
Power Management:off
Link Quality=0/94 Signal level=-95 dBm Noise level=-95 dBm
Rx invalid nwid:8 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

sit0 no wireless extensions.

sudo iwlist scan
Brings up:

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

ath0 Scan completed :
Cell 01 - Address: 00:01:38:99:2B:F2
ESSID:"wireless"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=2/94 Signal level=-93 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 22 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:bcn_int=200
Cell 02 - Address: 00:18:39:A2:D0:AC
ESSID:"MY_WIFI"
Mode:Master
Frequency:2.462 GHz (Channel 11)
Quality=47/94 Signal level=-48 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 22 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:rsn_ie=30140100000fac020100000fac040100000fa c020000
Cell 03 - Address: 00:04:ED:0A:43:02
ESSID:"benbenLAN"
Mode:Master
Frequency:2.417 GHz (Channel 2)
Quality=11/94 Signal level=-84 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:wpa_ie=dd160050f20101000050f20201000050f2020 1000050f202
Cell 04 - Address: 00:0F:B5:15:FD:A8
ESSID:"smudgemouth"
Mode:Master
Frequency:2.462 GHz (Channel 11)
Quality=4/94 Signal level=-91 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 22 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:wpa_ie=dd160050f20101000050f20201000050f2020 1000050f202
Cell 05 - Address: 00:0C:E3:61:0B:A1
ESSID:"Virgin Broadband"
Mode:Master
Frequency:2.462 GHz (Channel 11)
Quality=6/94 Signal level=-89 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:wpa_ie=dd180050f20101000050f20201000050f2020 1000050f2020000

sit0 Interface doesn't support scanning.

sudo lshw -C network
Brings up:

*-network:0
description: Ethernet interface
product: SiS900 PCI Fast Ethernet
vendor: Silicon Integrated Systems [SiS]
physical id: 4
bus info: pci@00:04.0
logical name: eth0
version: 91
serial: 00:c0:9f:9a:2c:38
size: 10MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegociation
configuration: autonegociation=on broadcast=yes driver=sis900 driverversion=v1.08.09 Sep. 19 2005 duplex=half link=no multicast=yes port=MII speed=10MB/s resources: ioport:2000-20ff iomemory:e2003000-e2003fff irq:177
*-network:1
description: Wireless interface
product: Atheros Communications, Inc.
vendor: Atheros Communications, Inc.
physical id: b
bus info: pci@00:0b.0
logical name: ath0
version: 01
serial: 00:0e:9b:b2:38:c0
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ath_pci driverversion=0.9.6.0 (EXPERIMENTAL) multicast=yes wireless=IEEE 802.11
resources: iomemory:e2010000-e201ffff irq:225


cat /etc/network/interfaces
Brings up:
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto ath0
iface ath0 inet dhcp

auto ath0
iface ath0 inet dhcp
wpa-driver madwifi
wpa-ssid "MY_WIFI"
wpa-ap-scan 1
wpa-proto WPA RSN
wpa-pairwise TKIP CCMP
wpa-group TKIP CCMP
wpa-key-mgmt WPA-PSK
wpa-psk MY_HEX_PASSKEY [IMPORTANT: See "WPA-PSK key generation"]

This is from a fresh install so the drivers would be supported(?)

using madwifi on an Atheros Card - Ubuntu grabbed it up straight from the install, which im glad cause installing these has been a bit hairy in the past on gentoo and other distros (possible user error?)

it can see the SSID from my card i have it on broadcast however the card doesnt like to associate with the router..

i had some trouble getting essid to stick as well but i finally got it in there... i have the correct hex passphrase in there but i can't see whether or not its accepted by the router when i try to connect

dhcp times out everytime and static IP within the subnet assigned just doesnt want to work either.. it binds but somehow doesn't see the network..

even tried to 'hard' route with bind and route to the gw but again doesnt see the network, pings always fail, and my router doesnt pick up the mac address of my wifi NIC when i check it.

Im guessing its possibly a driver to card interface issue or possibly im missing something in the way of wpa_supplicant setup

but then thats a bit of speculatation...

please help or my gf is going to kill me for sitting in the damn PC room so i can nets my *nix :(

[wieman01]

Thank you very much for your help! Find attached the output after I changed what you said plus the two other commands you ask.
Let me mention that I have been able to connect using the nm-applet, on my first post on this thread you can find a screenshot of the configuration used. As I said, I have been able (2 or 3 times) to connect, but is very rare and the connection will not stay up for long.
I do think my card works fine with PEAP because I use it on Windows XP and Vista with no problem (I have dual boot).
This is really strange. Just for the fun of it, could you try this please:

auto ath0
iface ath0 inet dhcp
wpa-driver wext
wpa-ssid COMPSCIwireless
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-EAP
wpa-eap PEAP
wpa-phase2 auth=MSCHAPV2
wpa-identity castromd
wpa-password xoo6Quud
The post:

sudo ifdown -v ath0

sudo ifup -v ath0
Have you tried Network Manager as well?

[wieman01]

My Wifi ESSID is labelled as MY_WIFI
I have input the HEX Passphrase; encryption being WPA1+WPA2 Mixed Mode
followed instructions.. is still not working any help??
Ok, let's look at the scan results first:

Cell 02 - Address: 00:18:39:A2:D0:AC
ESSID:"MY_WIFI"
Mode:Master
Frequency:2.462 GHz (Channel 11)
Quality=47/94 Signal level=-48 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 22 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:rsn_ie=30140100000fac020100000fac040100000fa c020000
It says that encryption is turned on but does not list the network as a WPA secured one. That is bad news and generally indicates that WPA is not supported by the driver.

In addition see this:

configuration: broadcast=yes driver=ath_pci driverversion=0.9.6.0 (EXPERIMENTAL) multicast=yes wireless=IEEE 802.11
The system seems to be using an experimental version of the driver. Whether it ought to support WPA or not, I don't know, but there is a pretty good chance that it doesn't.

You might have to replace the driver and make use of "ndiswrapper" instead...

[maycitybomber]

Yeah it seems that would be the case, this is the one that came with ubuntu??

ndiswrapper i'll give it a go

[wieman01]

Yeah it seems that would be the case, this is the one that came with ubuntu??

ndiswrapper i'll give it a go
Pretty much. It's the one that has been loaded by the default install.

If you need a hand setting up your card, let me know. Use my Ralink ("ndiswrapper") tutorial as reference if you like to. It should work for you as well.

[maycitybomber]

Well I have a question, will this work considering my card is atheros chipset??

[wieman01]

Well I have a question, will this work considering my card is atheros chipset??
Do you find your card listed anywhere here?

http://ndiswrapper.sourceforge.net/joomla/index.php?/component/option,com_openwiki/Itemid,33/id,list/

[lunatico]

I tried with wext instead of madwifi but it was no fun, didn't work... When you say "Network Manager" you are referring to the nm-applet right? I have tried that, as posted before and as shown on the image posted on my first input here.
The COMPSCIwireless network has to ways to authenticate, with WPA which we are trying to figure out and also with LEAP which have worked for me a couple of times using the nm-applet. So with the nm-applet I have tried in both ways but no luck.

[maycitybomber]

hmm have been trying to install the latest mad wifi driver... and ndiswrapper... issue being now on this fresh install make wont find my kernel :(

Makefile.inc:81: *** Cannot detect kernel version - please check compiler and KERNELPATH. Stop.


arrrgh

this is getting crazy im going backwardser and backwardser!

[wieman01]

hmm have been trying to install the latest mad wifi driver... and ndiswrapper... issue being now on this fresh install make wont find my kernel :(

Makefile.inc:81: *** Cannot detect kernel version - please check compiler and KERNELPATH. Stop.


arrrgh

this is getting crazy im going backwardser and backwardser!
"ndiswrapper" is in the repositories. You don't have to compile it yourself. See my Ralink tutorial (signature) for more.

[wieman01]

I tried with wext instead of madwifi but it was no fun, didn't work... When you say "Network Manager" you are referring to the nm-applet right? I have tried that, as posted before and as shown on the image posted on my first input here.
The COMPSCIwireless network has to ways to authenticate, with WPA which we are trying to figure out and also with LEAP which have worked for me a couple of times using the nm-applet. So with the nm-applet I have tried in both ways but no luck.
Last thing we can try is to remove NM (Network Manager) entirely using Synaptic. Then execute the script once again.

[lunatico]

Removed NetworkManager... nothing.... this is sad....

[lunatico]

- Should the password be plain text or should it be converted with wpa_passphrase?
- Does the order of commands matter?
- Will "extra" commands affect?

Thanks!

[wieman01]

Removed NetworkManager... nothing.... this is sad....
Could it be that your card does not support PEAP after all? This error message is suspicious:

wifi0: unknown hardware address type 801

[wieman01]

- Should the password be plain text or should it be converted with wpa_passphrase?
- Does the order of commands matter?
- Will "extra" commands affect?

Thanks!
You will need to generate a passphrase in this case.

The order has no impact.

What "extra" commands are you referring to?

[maycitybomber]

hmm i have a feeling i missed installing a compiler.. looking pretty stupid atm lol

[wieman01]

hmm i have a feeling i missed installing a compiler.. looking pretty stupid atm lol
'ndiswrapper' is in the respositories, so in fact you don't need a compiler at all. You can compile the package yourself in case you need a more recent version, however, the one in respository works for the majority of people.

[maycitybomber]

was attempting to get the madwifi driver up..

i have ndiswrapper just wanted to get madwifi installed to a more stable version in regards to wpa

[wieman01]

was attempting to get the madwifi driver up..

i have ndiswrapper just wanted to get madwifi installed to a more stable version in regards to wpa
Ok, got it. Let me know how you go later on.

[maycitybomber]

hmm ive loaded ndiswrapper and the correct driver (XP one which i find curious :D)

going to test the wpa settings now

[wieman01]

hmm ive loaded ndiswrapper and the correct driver (XP one which i find curious :D)

going to test the wpa settings now
Also check against my Ralink tutorial so as to make sure that you don't miss anything.

[Sementis]

See http://ubuntuforums.org/showthread.php?t=664586 for my problem

~sorry for double posting~

[Cammy]

Ok. I've been through everything and I'm still stumped. I could get the laptop connected using WPA if I used NetworkManager and typed my ssid/pass/etc in manually, every time, but I couldn't get it to do it after a reboot.

So I followed this thread, uninstalled NetworkManager, and edited /etc/network/interfaces so it looks like this:

auto lo
iface lo inet loopback

auto ath0
iface ath0 inet dhcp
wpa-driver madwifi
wpa-ssid myssid
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk myloooonghexpasskey

and when I do /etc/init.d/networking restart, I get (at the very end, after a few DHCPDISCOVERs:

No DHCPOFFERS received
No working leases in persistent database - sleeping

What could I possibly be doing wrong?

P.S. It's a Dell Inspiron 1100 and the wifi card is an Airlink 101 with an Atheros chip.

[wieman01]

Ok. I've been through everything and I'm still stumped. I could get the laptop connected using WPA if I used NetworkManager and typed my ssid/pass/etc in manually, every time, but I couldn't get it to do it after a reboot.

So I followed this thread, uninstalled NetworkManager, and edited /etc/network/interfaces so it looks like this:

auto lo
iface lo inet loopback

auto ath0
iface ath0 inet dhcp
wpa-driver madwifi
wpa-ssid myssid
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk myloooonghexpasskey

and when I do /etc/init.d/networking restart, I get (at the very end, after a few DHCPDISCOVERs:

No DHCPOFFERS received
No working leases in persistent database - sleeping

What could I possibly be doing wrong?

P.S. It's a Dell Inspiron 1100 and the wifi card is an Airlink 101 with an Atheros chip.
Did you generate the pass phrase as indicated in the tutorial?

Please post:

sudo iwlist scan

sudo ifdown -v ath0

sudo ifup -v ath0

[Axtilmor]

It is a wireless B card, isn't it? So it must be fairly old and I doubt that the Windows driver supports WPA... But you should know as you have used it before I guess.

It is definitely on the list of supported devices ("ndiswrapper"):

http://ndiswrapper.sourceforge.net/joomla/index.php?/component/option,com_openwiki/Itemid,33/id,list_m-n/

Try to get hold of an up-to-date Windows driver that specifically supports WPA/WPA2. I can guide you through the installation process if you like to.


Sorry to get back to this so late.

I tried the card out on my Windows installation, and I didn't have any luck connecting there, either. However, I need to run cable into that room, anyway, so I'll just move the router.

Thanks for all of your help!

[Cammy]

Did you generate the pass phrase as indicated in the tutorial?:
Yep!

sudo iwlist scan:


ath0 Scan completed :
Cell 01 - Address: 00:15:E9:5F:02:CA
ESSID:""
Mode:Master
Frequency:2.412 GHz (Channel 1)
Quality=43/70 Signal level=-52 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : PSK



sudo ifdown -v ath0


Configuring interface ath0=ath0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.ath0.pid -lf /var/lib/dhcp3/dhclient.ath0.leases ath0
There is already a pid file /var/run/dhclient.ath0.pid with pid 5381
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:18:02:5b:19:bb
Sending on LPF/ath0/00:18:02:5b:19:bb
Sending on Socket/fallback
DHCPRELEASE on ath0 to 192.168.0.1 port 67
ifconfig ath0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/madwifi
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.ath0.pid
Stopped /sbin/wpa_supplicant (pid 3966).

sudo ifup -v ath0


Configuring interface ath0=ath0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/madwifi
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver madwifi
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.ath0.pid -i ath0 -D madwifi -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/ath0
wpa_supplicant: wpa-ap-scan 1 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "FoxBunny" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise TKIP -- OK
wpa_supplicant: wpa-group TKIP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto WPA -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.ath0.pid -lf /var/lib/dhcp3/dhclient.ath0.leases ath0
There is already a pid file /var/run/dhclient.ath0.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:18:02:5b:19:bb
Sending on LPF/ath0/00:18:02:5b:19:bb
Sending on Socket/fallback
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 1
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant

[wieman01]

Yep!
Mmm... Same trouble as this user used to have: maycitybomber.

Perhaps it's good to contact him by PM and ask him for advice. Apparently he was able to solve his problems with his Atheros based card. Worth a shot.

I think he had to replace his driver somehow...

EDIT:
If there is no response, please let me know. I can ask him for you.

[Cammy]

FIXED! I somehow got wpa_supplicant to work after poaching some info from this thread (http://ubuntuforums.org/showthread.php?t=263136).

I'm all working 100% now :D

[wieman01]

FIXED! I somehow got wpa_supplicant to work after poaching some info from this thread (http://ubuntuforums.org/showthread.php?t=263136).

I'm all working 100% now :D
What information did you change? Would be nice if you shared your stuff with us, so that other have a reference. :-)

[Cammy]

Ok, I'll give it a shot.

The below is for my Atheros card on ath0, and using a madwifi driver. It can probably be changed to suit needs.

First off, I think you need to have wpa_supplicant installed. I think I installed this and it did not come with gutsy.


sudo apt-get install wpasupplicant

Then, I did this:


wpa_passphrase myssid my_passphrase

which resulted in this appearing in the terminal:


network={
ssid="myssid"
#psk="my_passphrase"
psk=my_looong_hex_passhrase_thing
}

Copy this somewhere, as you'll need it in the next step.

Then:


sudo gedit /etc/wpa_supplicant/wpa_supplicant.conf

And pasted in the code above. Then I added the following lines in blue::



ctrl_interface=/var/run/wpa_supplicant

network={
ssid="myssid"
scan_ssid=1
proto=WPA RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP
#psk="my_passphrase"
psk=my_looong_hex_passhrase_thing
}

Save and close it.

Then I did:


sudo gedit /etc/network/interfaces

And added this:


auto ath0
iface ath0 inet dhcp

pre-up wpa_supplicant -Bw -Dmadwifi -iath0 -c/etc/wpa_supplicant/wpa_supplicant.conf
post-down killall -q wpa_supplicant

Save and close.

Then rebooted and was online.

[lime4x4]

can't get a linksys wmp300n wireless card to connect to my router using wpa
if i disable the secrutiy of the router i can connect just fine. i removed network managers and configured my interface like this

auto lo
iface lo inet loopback



auto wlan0
iface wlan0 inet static
address 192.168.1.105
gateway 192.168.1.1
dns-nameservers 192.168.1.1
netmask 255.255.255.0
wpa-driver wext
wpa-ssid transformers
wpa-ap-scan 1
wpa-proto WPA RSN
wpa-pairwise TKIP CCMP
wpa-group TKIP CCMP
wpa-key-mgmt WPA-PSK
wpa-psk my passkey

if i run iwlist scan i get this

pammy@pammy-desktop:~$ iwlist scan
lo Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:1C:10:C7:52:26
ESSID:"transformers"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.422 GHz (Channel 3)
Quality:90/100 Signal level:-38 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK

So it sees my router but won't connect when i try to run encryption.
If it matters the router is a linksys wrt300N

[wieman01]

can't get a linksys wmp300n wireless card to connect to my router using wpa
if i disable the secrutiy of the router i can connect just fine. i removed network managers and configured my interface like this

auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet static
address 192.168.1.105
gateway 192.168.1.1
dns-nameservers 192.168.1.1
netmask 255.255.255.0
wpa-driver wext
wpa-ssid transformers
wpa-ap-scan 1
wpa-proto WPA RSN
wpa-pairwise TKIP CCMP
wpa-group TKIP CCMP
wpa-key-mgmt WPA-PSK
wpa-psk my passkey

What chipset is your adapter?

Please also post:

sudo lshw -C network
sudo ifdown -v <your_interface>
sudo ifup -v <your_interface>

[dynamethod]

Can someone please confirm this will work with a fresh install of Kubuntu 7.10? because ive found Kubuntu absolutely shocking with wireless (using ralink rt73 usb adapter)

EDIT: Does work, i forgot to install the ralink drivers.

[wieman01]

Can someone please confirm this will work with a fresh install of Kubuntu 7.10? because ive found Kubuntu absolutely shocking with wireless (using ralink rt73 usb adapter)

EDIT: Does work, i forgot to install the ralink drivers.
What drivers did you install eventually?

[lime4x4]

*-network
description: Wireless interface
product: BCM43XG
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:01:00.0
logical name: wlan0
version: 01
serial: 00:1d:7e:9d:1e:3a
width: 32 bits
clock: 33MHz
capabilities: bus_master ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+bcmwl5 driverversion=1.45+Linksys, A Division of Cisc ip=192.168.1.105 latency=64 link=yes module=ndiswrapper multicast=yes wireless=IEEE 802.11g

[mariner8905]

Ive followed everything that was said in this thread to get my WPA wireless running but to no avail. im running a Ibook G3 PPC with an Airport that i know could use WPA before i loaded up Ubuntu 6.06. my current setup is as follows in interfaces
auto eth1
iface eht10 inet dhcp
wpa-driver wext
wpa-ssid <your_essid>
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <your_hex_key>

I have everything that should be filled in filled in as per the instructions. I just noticed a few errors when i run a network restart so im posting that as well, hoping it might help.
Internet Systems Consortium DHCP Client V3.0.3
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

Listening on LPF/eth1/00:30:65:0a:cf:e8
Sending on LPF/eth1/00:30:65:0a:cf:e8
Sending on Socket/fallback
DHCPRELEASE on eth1 to 192.168.1.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODE]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODE]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODE]: Invalid argument
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - Internet Systems Consortium DHCP Client V3.0.3
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

Listening on LPF/eth1/00:30:65:0a:cf:e8
Sending on LPF/eth1/00:30:65:0a:cf:e8
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 17
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
No DHCPOFFERS received.
Trying recorded lease 192.168.1.7
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.

--- 192.168.1.1 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms

No working leases in persistent database - sleeping.
[ ok ]

if anyone can help id greatly appreciate it. and as much detail on what to do would be good, im very new to linux and its workings.

[wieman01]

@mariner8905:

Does not look too promising at the moment:

ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODE]: Invalid argument
You driver does not appear to support the 'wext' interface.

Please issue these commands and post the results:

sudo iwlist scan

sudo lshw -C network
What chipset does your wireless adapter have?

[mariner8905]

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:17:0F:8C:AC:E0
ESSID:"UWLAN"
Mode:Master
Frequency=2.462 GHz (Channel 11)
Signal level:-67 dBm Noise level:-99 dBm
Encryption key:on
Cell 02 - Address: 00:0F:34:C0:44:70
ESSID:"UWLAN"
Mode:Master
Frequency=2.437 GHz (Channel 6)
Signal level:-70 dBm Noise level:-96 dBm
Encryption key:on
Cell 03 - Address: 00:11:20:4B:F0:90
ESSID:"UWLAN"
Mode:Master
Frequency=2.462 GHz (Channel 11)
Signal level:-79 dBm Noise level:-99 dBm
Encryption key:on
Cell 04 - Address: 00:16:46:71:7C:10
ESSID:"UWLAN"
Mode:Master
Frequency=2.462 GHz (Channel 11)
Signal level:-80 dBm Noise level:-99 dBm
Encryption key:on

sit0 Interface doesn't support scanning.

*-network
description: Ethernet interface
product: UniNorth/Pangea GMAC (Sun GEM)
vendor: Apple Computer Inc.
physical id: f
bus info: pci@20:0f.0
logical name: eth0
version: 00
serial: 00:0a:95:77:67:2e
size: 100MB/s
capacity: 100MB/s
width: 32 bits
clock: 66MHz
capabilities: bus_master ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegociation
configuration: autonegociation=on broadcast=yes driver=sungem driverversion=0.98 duplex=full ip=138.49.32.116 link=yes multicast=yes port=MII speed=100MB/s
resources: iomemory:f5200000-f53fffff irq:41
*-network
description: Wireless interface
physical id: 1
logical name: eth1
serial: 00:30:65:0a:cf:e8
capabilities: ethernet physical wireless
configuration: broadcast=yes driver=orinoco driverversion=0.15rc3 firmware=Lucent/Agere 8.70 link=no multicast=yes wireless=IEEE 802.11b

i think that is all you requested, if you need more, let me know.

[wieman01]

@mariner8905:

Tough luck... This driver (Orinoco) does not support WPA as far as I can tell. Now we have 2 options... You either revert to WEP or you install 'ndiswrapper' to get it working. 'ndiswrapper' might not be an option since this is a MacBook and no Windows machine.

There is another user who might give some useful advice: Kevdog. Perhaps you can contact him as well. He maintains a very useful thread which you find here:

http://ubuntuforums.org/showthread.php?t=571188

Let me know if there is anything else I can do...

[mariner8905]

well id like to exhaust any options you might have first before moving onto someone else and having to reexplain everything again. how would i install the ndiswrapper driver? and were do i find it?

[wieman01]

well id like to exhaust any options you might have first before moving onto someone else and having to reexplain everything again. how would i install the ndiswrapper driver? and were do i find it?
Alright then. You find instructions in my own Ralink tutorial. It is basically for Ralink based chip-sets, however, it should also work for other drivers. It explains how to install "ndiswrapper" and how to deploy the Windows drivers.

Are there Windows drivers out there for your wireless adapter?

[lime4x4]

Quote:
Originally Posted by lime4x4 View Post
can't get a linksys wmp300n wireless card to connect to my router using wpa
if i disable the secrutiy of the router i can connect just fine. i removed network managers and configured my interface like this

auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet static
address 192.168.1.105
gateway 192.168.1.1
dns-nameservers 192.168.1.1
netmask 255.255.255.0
wpa-driver wext
wpa-ssid transformers
wpa-ap-scan 1
wpa-proto WPA RSN
wpa-pairwise TKIP CCMP
wpa-group TKIP CCMP
wpa-key-mgmt WPA-PSK
wpa-psk my passkey
What chipset is your adapter?

Please also post:
Quote:
sudo lshw -C network
sudo ifdown -v <your_interface>
sudo ifup -v <your_interface>

here is the info you requested. This was done with my router unsecured

pammy@pammy-desktop:~$ sudo lshw -C network
*-network
description: Wireless interface
product: BCM43XG
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:01:00.0
logical name: wlan0
version: 01
serial: 00:1d:7e:9d:1e:3a
width: 32 bits
clock: 33MHz
capabilities: bus_master ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+bcmwl5 driverversion=1.45+Linksys, A Division of Cisc ip=192.168.1.105 latency=64 link=yes module=ndiswrapper multicast=yes wireless=IEEE 802.11g
pammy@pammy-desktop:~$ sudo ifdown -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/wpasupplicant
route del default gw 192.168.1.1 metric 100 wlan0
ifconfig wlan0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan0.pid
Stopped /sbin/wpa_supplicant (pid 9344).
pammy@pammy-desktop:~$ sudo ifup -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: using default driver type: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan0
wpa_supplicant: wpa-ap-scan 1 -- OK

ifconfig wlan0 192.168.1.105 netmask 255.255.255.0 up
route add default gw 192.168.1.1 metric 100 wlan0
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/openssh-server
run-parts: executing /etc/network/if-up.d/wpasupplicant
pammy@pammy-desktop:~$

[wieman01]

@lim4x4:

Please post the full output of...

sudo ifup -v wlan0
... once again. Some bits are missing. And also provide:

sudo iwlist scan
Thanks, mate.

[lime4x4]

my router is called transformers

pammy@pammy-desktop:~$ sudo ifup -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: using default driver type: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan0
wpa_supplicant: wpa-ap-scan 1 -- OK

ifconfig wlan0 192.168.1.105 netmask 255.255.255.0 up
route add default gw 192.168.1.1 metric 100 wlan0
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/openssh-server
run-parts: executing /etc/network/if-up.d/wpasupplicant
pammy@pammy-desktop:~$ sudo iwlist scan
lo Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:1C:10:C7:52:26
ESSID:"transformers"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.422 GHz (Channel 3)
Quality:76/100 Signal level:-47 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 02 - Address: 00:13:10:99:EA:F2
ESSID:"linksys"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:17/100 Signal level:-85 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 03 - Address: 00:14:D1:3D:71:9F
ESSID:"TRENDnet"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:9/100 Signal level:-90 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 04 - Address: 00:13:10:79:34:CA
ESSID:"coyote"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:15/100 Signal level:-86 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0

pammy@pammy-desktop:~$

[wieman01]

my router is called transformers

pammy@pammy-desktop:~$ sudo ifup -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: using default driver type: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan0
wpa_supplicant: wpa-ap-scan 1 -- OK

This is really strange, there is some stuff missing (number of extra rows saying OK).

What does a scan yield once you have turned on(!) WPA?

sudo iwlist scan

[chriswil]

Weiman01,

This is still very relevant.
The standard Network tool from the GUI does not seem to add the psk line to the networks file. (7.10)

I have just got my Netgear WPN111 adapter working. After fiddling around for hours looking at other posts I manually edited the networks as per your original posting and it all sprang to life!!


auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid xxxxxxxxxxxxx
wpa-ap-scan 1
wpa-proto WPA RSN
wpa-pairwise TKIP CCMP
wpa-group TKIP CCMP
wpa-key-mgmt WPA-PSK
wpa-psk xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx x

Many Thanks

[antisho]

I'm having some trouble with this. The network is WPA, AES, PEAP, MSCHAPV2. I have a Broadcom card and use ndiswrapper. Currently I have this in /etc/network/interfaces:


auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp
wpa-driver ndiswrapper
wpa-ssid (ssid)
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-eap PEAP
wpa-key-mgmt WPA-EAP
wpa-identity (username)
wpa-password (password)

I've rebooted twice and restarted /etc/init.d/networking several times, but it hasn't worked.

---------------------------

ifdown:

Configuring interface eth0=eth0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/clamav-freshclam-ifupdown
run-parts: executing /etc/network/if-down.d/openvpn
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.eth0.pid -lf /var/lib/dhcp3/dhclient.eth0.leases eth0
There is already a pid file /var/run/dhclient.eth0.pid with pid 6412
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:12:3f:d0:a9:7b
Sending on LPF/eth0/00:12:3f:d0:a9:7b
Sending on Socket/fallback
DHCPRELEASE on eth0 to 192.168.1.1 port 67
ifconfig eth0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant

ifup:

Configuring interface eth0=eth0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
ioctl[SIOCSIWMODE]: Operation not supported
ioctl[SIOCGIWRANGE]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODE]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODE]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODE]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODE]: Operation not supported

dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.eth0.pid -lf /var/lib/dhcp3/dhclient.eth0.leases eth0
There is already a pid file /var/run/dhclient.eth0.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:12:3f:d0:a9:7b
Sending on LPF/eth0/00:12:3f:d0:a9:7b
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/clamav-freshclam-ifupdown
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntp
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/openssh-server
run-parts: executing /etc/network/if-up.d/openvpn
run-parts: executing /etc/network/if-up.d/wpasupplicant

iwconfig:

eth1 IEEE 802.11g ESSID:off/any
Mode:Managed Frequency:2.462 GHz Access Point: Not-Associated
Bit Rate:54 Mb/s Tx-Power:32 dBm
RTS thr:2347 B Fragment thr:2346 B
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

iwlist:

eth1 Scan completed :
Cell 01 - Address: 00:1A:A2:FC:71:80
ESSID:""
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:64/100 Signal level:-55 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : 802.1x
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : 802.1x
Cell 02 - Address: 02:13:02:17:E2:0B
ESSID:"DCDS Wireless"
Protocol:IEEE 802.11g
Mode:Ad-Hoc
Frequency:2.462 GHz (Channel 11)
Quality:59/100 Signal level:-58 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 03 - Address: 00:1A:A2:FC:45:A0
ESSID:""
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:23/100 Signal level:-81 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : 802.1x
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : 802.1x
Cell 04 - Address: FA:EA:DE:16:F9:DC
ESSID:"EPSON"
Protocol:IEEE 802.11g
Mode:Ad-Hoc
Frequency:2.412 GHz (Channel 1)
Quality:87/100 Signal level:-40 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0

lshw:

*-network
description: Ethernet interface
product: NetXtreme BCM5751 Gigabit Ethernet PCI Express
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:02:00.0
logical name: eth0
version: 01
serial: 00:12:3f:d0:a9:7b
capacity: 1GB/s
width: 64 bits
clock: 33MHz
capabilities: pm vpd msi pciexpress bus_master cap_list ethernet physical mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=tg3 driverversion=3.77 firmware=5751-v3.29a latency=0 link=no module=tg3 multicast=yes port=twisted pair
*-network
description: Wireless interface
product: BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller
vendor: Broadcom Corporation
physical id: 3
bus info: pci@0000:03:03.0
logical name: eth1
version: 02
serial: 00:90:4b:fb:e4:d7
width: 32 bits
clock: 33MHz
capabilities: bus_master ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+bcmwl5 driverversion=1.49+Broadcom,10/12/2006, 4.100. latency=64 link=no module=ndiswrapper multicast=yes wireless=IEEE 802.11g

route:


Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
link-local * 255.255.0.0 U 0 0 0 eth0
default * 0.0.0.0 U 1000 0 0 eth0

[wieman01]

@Antisho:

This would be the right configuration. Please try again and post your results:

auto lo
iface lo inet loopback

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-ssid (ssid)
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-eap PEAP
wpa-key-mgmt WPA-EAP
wpa-identity (username)
wpa-password (password)
SSID broadcast turned off, right?

[antisho]

Right, I just noticed it should be eth1. It didn't work. Will try again with wext.

SSID broadcast: how do I check that?

[wieman01]

Right, I just noticed it should be eth1. It didn't work. Will try again with wext.

SSID broadcast: how do I check that?
When scanning for the wireless network, do you recognize its name or is it hidden/blank?

[antisho]

When scanning for the wireless network, do you recognize its name or is it hidden/blank?It does not appear in, say, nm-applet when in roaming mode. So I assume so.

[antisho]

@Antisho:

This would be the right configuration. Please try again and post your results:

SSID broadcast turned off, right?This works. Thanks!

[rootware]

Greetings, I have figured out how to configure my wlan card, but the problem is sometimes when I boot into the sistem the internet it's not working, even if I put that network-restart script on my startup.

What can I do?:(

[wieman01]

Greetings, I have figured out how to configure my wlan card, but the problem is sometimes when I boot into the sistem the internet it's not working, even if I put that network-restart script on my startup.

What can I do?:(
Hello,

I don't think this has much to do with this thread. But how about that: You open up a new thread, outline your problem there and also mention the hardware you have got, etc. and you can send me the link to your post by PM?

EDIT:

Oops, I am really sorry... I mistakenly edited your post and pressed "save". I did it unintentionally, I am not yet really familiar with my new role as admin, so I hit the wrong button. My apologies.

[mssever]

Just a quick note to point out that NetworkManager can handle WPA2 without manually messing with wpa-supplicant or any other such nonsense. My network uses WPA2 with AES encryption. I use the bcm43xx driver. I simply ask NetworkManager to connect to the network, enter my key, and I'm in. No manual configuration necessary.

[wieman01]

Just a quick note to point out that NetworkManager can handle WPA2 without manually messing with wpa-supplicant or any other such nonsense. My network uses WPA2 with AES encryption. I use the bcm43xx driver. I simply ask NetworkManager to connect to the network, enter my key, and I'm in. No manual configuration necessary.
I know that it can. But it cannot handle static IP addresses. That's the point of this nonsense.

[lime4x4]

well i ended up installing wicd and now my wireless connection is working fine using wep. i also tried wpa/wpa2 and they work as well. Don't know why this method wouldn't work for me

[mssever]

I know that it can. But it cannot handle static IP addresses. That's the point of this nonsense.

My apologies. I missed the static IP part.

[Paris Heng]

Dear sir,

I saw your post about WPA configuration. I have few question on this, can you help me? I using Atheros + Madwifi for the wifi NIC.

Questions:
(1) hostapd
I recently configure a WPA in a own build Linux access point (AP. But the configuration i not configured in /etc/network/interfaces. I using another program name hostapd to perform the WPA. I configured all the WPA configuration in hostapd config file. My problems not is, I run the hostapd daemon, but the client can connect to the AP without being authenticate by WPA. Did you know about hostapd + Madwifi, please assist me.

Starting the daemon:

/etc/init.d/hostapd start

hostapd.conf:

######################### hostapd configuration file ##########################

#Experiemnt for WPA-PSK



############################# Initial #########################################

interface=ath0

driver=madwifi

logger_syslog=-1

logger_syslog_level=2

logger_stdout=-1

logger_stdout_level=2

debug=4

dump_file=/tmp/hostapd.dump

ctrl_interface=/var/run/hostapd

ctrl_interface_group=0



###################### IEEE 802.11 related config #############################

ssid=heng_AP2

macaddr_acl=0



###### You need create 2 file, /etc/hostapd.accept and /etc/hostapd.deny #####

# Station MAC address -based authentication #

# 0 = accept unless in deny list #

# 1 = deny unless in accept list #

# 2 = use external RADIUS server (accept/deny lists are searched first) #

################################################## ############################

accept_mac_file=/etc/hostapd.allow

#deny_mac_file=/etc/hostapd.deny



################################################## ############################

# IEEE 802.11 specifies two authentication algorithms. hostapd can be #

# configured to allow both of these or only one. Open system authentication #

# should be used with IEEE 802.1X. #

# Bit fields of allowed authentication algorithms: #

# bit 0 = Open System Authentication #

# bit 1 = Shared Key Authentication (requires WEP) #

################################################## ############################

auth_algs=3



######################### IEEE 802.1X related config #########################

# Require IEEE 802.1X authorization

#ieee8021x=0



# EAPOL-Key index workaround (set bit7) for WinXP Supplicant (needed only if

# only broadcast keys are used)

#eapol_key_index_workaround=0



######### IEEE 802.11f - Inter-Access Point Protocol (IAPP) ##################

# Interface to be used for IAPP broadcast packets

#iapp_interface=eth0



####################### WPA/IEEE 802.11i config ##############################

wpa=1

#wpa_psk=701459761a3d17c5ddead0deafbeeffeedbadf00d c659db31e2e3d36f00a12b1

wpa_passphrase=hengfookyauhengfookyauhengfo

wpa_key_mgmt=WPA-PSK

wpa_pairwise=TKIP CCMP


(2) WPA_Supplicant + Madiwif + Network Manager
When I was client, the information about the existing AP even the ESSID name did not shown in network manager. Why?

Thank, please help.

[wieman01]

My apologies. I missed the static IP part.
No problem. This Sticky Thread will be removed as soon as Hardy is released.

[wieman01]

Dear sir,

I saw your post about WPA configuration. I have few question on this, can you help me? I using Atheros + Madwifi for the wifi NIC.

Questions:
(1) hostapd
I recently configure a WPA in a own build Linux access point (AP. But the configuration i not configured in /etc/network/interfaces. I using another program name hostapd to perform the WPA. I configured all the WPA configuration in hostapd config file. My problems not is, I run the hostapd daemon, but the client can connect to the AP without being authenticate by WPA. Did you know about hostapd + Madwifi, please assist me.

Starting the daemon:


hostapd.conf:
[/COLOR]

(2) WPA_Supplicant + Madiwif + Network Manager
When I was client, the information about the existing AP even the ESSID name did not shown in network manager. Why?

Thank, please help.
Frankly I have no experience with the Madwifi driver and it's no real topic for this thread... However, what happens when you do:

sudo iwlist scan

sudo lshw -C network
What device have you got there?

[quodlibetor]

great post, it seems like it almost works for me ;)

I've got a bit of a problem: when i followed your instructions everything seemed to work fine, including up to the "/etc/init.d/networking restart" showing me the new preferences that i wanted and apparently connecting to the correct network, but then my computer freezes.

Based on my system monitor it looks like the CPU over-revs and gets locked down, but i don't know how to check because my computer becomes completely frozen (mouse stuck, ctrl+alt+f1 does nothing, alt+sysrq+r doesn't help...)

I can wirelessly connect to unsecured networks, it's just i've been unable to set up WPA1, which is what i'm trying to do.

some basic stats:
U 7.10
Linksys WMP300n with NDISwrapper

thanks in advance

[wieman01]

great post, it seems like it almost works for me ;)

I've got a bit of a problem: when i followed your instructions everything seemed to work fine, including up to the "/etc/init.d/networking restart" showing me the new preferences that i wanted and apparently connecting to the correct network, but then my computer freezes.

Based on my system monitor it looks like the CPU over-revs and gets locked down, but i don't know how to check because my computer becomes completely frozen (mouse stuck, ctrl+alt+f1 does nothing, alt+sysrq+r doesn't help...)

I can wirelessly connect to unsecured networks, it's just i've been unable to set up WPA1, which is what i'm trying to do.

some basic stats:
U 7.10
Linksys WMP300n with NDISwrapper

thanks in advance
This could be a problem relating to 'ndiswrapper'. I have heard of similar problems before, 'ndiswrapper' making the system freeze and all that stuff. So upgrading to the latest SVN version might help. This thread is a great source:

http://ubuntuforums.org/showthread.php?t=574501

[quodlibetor]

This could be a problem relating to 'ndiswrapper'. I have heard of similar problems before, 'ndiswrapper' making the system freeze and all that stuff. So upgrading to the latest SVN version might help. This thread is a great source:

http://ubuntuforums.org/showthread.php?t=574501

Thanks i'll check that out.

[tad1073]

If I am the one connecting to an AP with WPA2(auto) TPIK I need to configure etc/wpa_supplicant.conf as lited below? Also, I need to use the network key that was genrated when I created the wirless network on the machine that is connected to the router? Will i be able to do this in roaming mode also, because when I use manual configuration I am not able to connect. I an using madwifi w/ Network Manager and ath0 is my wireless device.


auto ath0
iface ath0 inet dhcp
wpa-driver wext
wpa-ssid <your_essid>
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk <your_hex_key> [IMPORTANT: See "WPA-PSK key generation"]

[wieman01]

If I am the one connecting to an AP with WPA2(auto) TPIK I need to configure etc/wpa_supplicant.conf as lited below? Also, I need to use the network key that was genrated when I created the wirless network on the machine that is connected to the router? Will i be able to do this in roaming mode also, because when I use manual configuration I am not able to connect. I an using madwifi w/ Network Manager and ath0 is my wireless device.


auto ath0
iface ath0 inet dhcp
wpa-driver wext
wpa-ssid <your_essid>
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk <your_hex_key> [IMPORTANT: See "WPA-PSK key generation"]
If you want to continue using Network Manager, then this thread is of no use to you. You don't have to do anything manually if NM does the job for you (unless you are in need of static IP addresses).

[jwmcgee1]

Help. I am trying to get my system running on WiFi.

I am using an Apple router, and a Linksys WMP54G adapter on Ubuntu 7.1.

I am trying to use WPA2, DHCP, no SSID broadcast. As long as my SSID IS broadcast, and I enter the info using the network control panel it works ok, but it will not work if the SSID is not broadcast.

Here is the info I have:

Interfaces:

auto lo
iface lo inet loopback

auto wlan1
iface wlan1 inet static
address 10.0.1.112
gateway 10.0.1.1
dns-nameservers 10.0.1.1
netmask 255.255.255.0
wpa-ap-scan 2
wpa-pairwise CCMP
wpa-group CCMP
wpa-psk bd01c01aa270beff1cbc71a7d0df7ce9d398c1d494e7aed1ac cb3ccf09dc1985
wpa-driver wext
wpa-key-mgmt WPA-PSK
wpa-proto RSN
wpa-ssid OKCBears


wlan1 IEEE 802.11g ESSID:"OKCBears"
Mode:Managed Frequency:2.462 GHz Access Point: 00:19:E3:FA:BB:61
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Link Signal level=-50 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

eth0 Link encap:Ethernet HWaddr 00:07:E9:63:3F:AD
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:193 errors:0 dropped:0 overruns:0 frame:0
TX packets:193 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:18302 (17.8 KB) TX bytes:18302 (17.8 KB)

wlan1 Link encap:Ethernet HWaddr 00:1D:7E:9D:A9:4E
inet addr:10.0.1.112 Bcast:10.0.1.255 Mask:255.255.255.0
inet6 addr: fe80::21d:7eff:fe9d:a94e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:123751 errors:0 dropped:0 overruns:0 frame:0
TX packets:87035 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:9091096 (8.6 MB) TX bytes:65516603 (62.4 MB)

wmaster0 Link encap:UNSPEC HWaddr 00-1D-7E-9D-A9-4E-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

Any help would be appreciated!!!

[wieman01]

Help. I am trying to get my system running on WiFi.

I am using an Apple router, and a Linksys WMP54G adapter on Ubuntu 7.1.

I am trying to use WPA2, DHCP, no SSID broadcast. As long as my SSID IS broadcast, and I enter the info using the network control panel it works ok, but it will not work if the SSID is not broadcast.

Here is the info I have:

Any help would be appreciated!!!
Frankly I don't know how to help. Some adapters cannot cope with hidden SSIDs, occasionally it has to do with the drivers, then again Network Manager is the culprit. Tell you what... turning off SSID broadcast does not add any extra security, why do you not leave it enabled? I think it makes sense, I do the same thing simply because client computers work better with SSID broadcast turned on.

[jwmcgee1]

I was afraid you were going to say that.

I figured it was the Linksys card giving me grief!

[Happibun]

Hello, and thank you for what looks like a phenomenal thread.

I am an utter Noob to Linux, having not even used a Linux machine until 48 hours ago, but always wanted to get started with it. I was given a laptop yesterday with no operating system, so I went for it and installed Gutsy 7.1. All worked beautifully except for wireless networking.

It seems that I have innocently stumbled upon the most problematic area by shear folly and ignorance. Such is life :(

Anyhow, this is the set up so far:

Dell Latitude 120L Laptop.
Ubuntu 7.10, Gnome.
Broadcom internal network card chipset, running with ndiswrapper.
Netgear DG834GT router with up to date firmware, was set to hidden SSID with MAC filtering on.
Now broadcasting SSID, using WPA-PSK encryption, and MAC filtering.

I have been able to connect wirelessly when the SSID was broadcast, and I had keyed the MAC addresses in to the router. However, I feel I need an extra level of security if I have to broadcast my SSID.
I would prefer to hide my SSID and I really want to keep the MAC filtering on. I'm not too bothered about WPA, the way I see it - MAC filtering is the most secure way to protect my network. I would like the laptop to be able to connect to my network when it boots, without me having to jigger about with he router or terminal each time I want to connect.

Any help would be greatly appreciated.

I'll warn you now that I am not a wireless network expert, and I'm swamped by commands and acronyms. Please be gentle with me 8-[

Jo

[wieman01]

@Happibun:

Welcome first of all.

Before we go ahead a couple of comments... MAC filtering isn't really a security feature. It takes experienced users like me 5 seconds to get around it. Hiding SSID is no security feature either, and in fact makes your system less secure. See this for more:

http://blogs.technet.com/steriley/archive/2007/10/16/myth-vs-reality-wireless-ssids.aspx

Also you are right in that WPA is the way to go. Again it would take me about 15 minutes to crack your WEP key and take control of your network.

Having said that, do you really want to turn off SSID broadcast? I think WPA is fine. And if network manager (the networking applet that you are most likely using) does a good job with SSID broadcast enabled, I'd go for it. Why bother?

That's my most informed opinion. :-)

If you still have troubles with WPA, please do me a favor, open a terminal (command line), type in the following commands and post the results:

sudo iwlist scan

sudo lshw -C network
"-C" is a capital C. Please post the output.

No worries, this is the right thread to ask all these questions. Bear with me (and Ubuntu) and I promise you it will be a very pleasant experience.

[MountainX]

My wireless networking fails to get a valid IP address after I suspend/resume.

I have already tried (without success) the suggestions here:
http://lilserenity.wordpress.com/2007/10/31/fix-ubuntu-dropping-wireless-on-suspendhibernate-resume/
The core change recommended, which I did, was:
/etc/default/acpi-support:
Change STOP_SERVICES to read:
STOP_SERVICES="networking"

Here is some info on my system:


~$ sudo iwlist scan
Password or swipe finger:
lo Interface doesn't support scanning.

vmnet1 Interface doesn't support scanning.

vmnet8 Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:1B:11:68:7C:69
ESSID:"my-essid"
Protocol:IEEE 802.11bg
Mode:Master
Channel:1
Frequency:2.412 GHz (Channel 1)
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 9 Mb/s; 11 Mb/s
6 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=92/100 Signal level=-39 dBm Noise level=-39 dBm
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : WEP-40
Pairwise Ciphers (2) : WEP-40 TKIP
Authentication Suites (1) : PSK
Preauthentication Supported
Extra: Last beacon: 240ms ago

username@computername:~$ sudo lshw -C network
*-network
description: Ethernet interface
product: 82566MM Gigabit Network Connection
vendor: Intel Corporation
physical id: 19
bus info: pci@0000:00:19.0
logical name: eth0
version: 03
serial: 00:1e:37:86:99:22
capacity: 1GB/s
width: 32 bits
clock: 33MHz
capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e1000 driverversion=7.3.20-k2-NAPI firmware=0.3-0 latency=0 link=no module=e1000 multicast=yes port=twisted pair
*-network
description: Wireless interface
product: PRO/Wireless 3945ABG Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:03:00.0
logical name: eth1
version: 02
serial: 00:1c:bf:75:fc:15
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ipw3945 driverversion=1.2.2mp.ubuntu1 firmware=14.2 1:0 () latency=0 link=no module=ipw3945 multicast=yes wireless=unassociated
username@computername:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:1E:37:86:99:22
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Base address:0x1840 Memory:fe200000-fe220000

eth1 Link encap:Ethernet HWaddr 00:1C:BF:75:FC:15
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:3 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:21 Memory:d7dff000-d7dfffff

eth1:avah Link encap:Ethernet HWaddr 00:1C:BF:75:FC:15
inet addr:169.254.7.83 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Interrupt:21 Memory:d7dff000-d7dfffff

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:68 errors:0 dropped:0 overruns:0 frame:0
TX packets:68 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6154 (6.0 KB) TX bytes:6154 (6.0 KB)


If I restart networking, my wireless device will get an IP address and then everything works. Seems like the change I made here doesn't go the trick.
/etc/default/acpi-support:
STOP_SERVICES="networking"

Should I remove this change or alter it? Or should I add the "sudo /etc/init.d/networking restart" command to a startup script as well?

BTW, I do not have the wireless networking icon in the upper right of my screen. How do I fix this? Thanks.

[wieman01]

@MountainX:

I know very little about ACPI. Therefore I cannot advise here. You could certainly create another startup script but I am not certain which run level that would be. I found some stuff here that could be interesting:

http://gentoo-wiki.com/TIP_ACPI_basic_configuration

For general wireless help & support please see this thread:

http://ubuntuforums.org/showthread.php?t=684495

[wieman01]

@MountainX:

I think you would have to put it here:

sudo gedit /etc/acpi/resume.sh
Then add (no 'sudo'):

/etc/init.d/networking restart
Please try and let me know if it works.

[Average Joe]

wieman01, thanks for this nice how-to! I followed your instructions and it works like a charm.

In a previous post (http://ubuntuforums.org/showpost.php?p=4388526&postcount=1232) you linked to an article (http://blogs.technet.com/steriley/archive/2007/10/16/myth-vs-reality-wireless-ssids.aspx) that explains that hiding your SSID is not secure at all, and you stated that it makes your system even less secure. Maybe that is true, but why do you, as an expert, then configure your system (in the how-to) such that it does hide your SSID?

I use my wireless network for my laptop at home, and apart from using WPA2, I have configured it such that it hides my SSID, and that it uses MAC address filtering. I understand that those last two measures don't add (much) security to my system when I use it.

However, most of the day my laptop is switched off, and I would think that, since there is no wireless traffic then, it is more secure to hide your SSID and use MAC filtering. Or would it still be possible for an attacker to figure out both my SSID and my MAC address while my computer is switched off? My modem/router is on 24/7.

[wieman01]

wieman01, thanks for this nice how-to! I followed your instructions and it works like a charm.

In a previous post (http://ubuntuforums.org/showpost.php?p=4388526&postcount=1232) you linked to an article (http://blogs.technet.com/steriley/archive/2007/10/16/myth-vs-reality-wireless-ssids.aspx) that explains that hiding your SSID is not secure at all, and you stated that it makes your system even less secure. Maybe that is true, but why do you, as an expert, then configure your system (in the how-to) such that it does hide your SSID?

I use my wireless network for my laptop at home, and apart from using WPA2, I have configured it such that it hides my SSID, and that it uses MAC address filtering. I understand that those last two measures don't add (much) security to my system when I use it.

However, most of the day my laptop is switched off, and I would think that, since there is no wireless traffic then, it is more secure to hide your SSID and use MAC filtering. Or would it still be possible for an attacker to figure out both my SSID and my MAC address while my computer is switched off? My modem/router is on 24/7.
Hello,

You are quite right in that my previous advice on turning on SSID broadcast must sound quite ambiguous given the objective of my tutorial, however, I must admit that I have learned in the course of the months and that I was not aware of it by the time I compiled the tutorial.

What comes on top is the fact that a lot of people ask for it, therefore my attempt at explaining how you can achieve it, although I should know better.

The security risk imposed by disabling SSID broadcast are somewhat limited, in particular if you don't do much roaming (see article). To answer your question, yes, MAC filtering and disabling broadcast might make it appear more secure and it makes people feel better, then so be it.

But looking at it from another angle, a system is as secure as the weakest link that holds it together. In terms of wireless security, that would be your security protocol (e.g. WPA2) and your key (PSK). If an attacker can get around these, MAC filtering and a hidden SSID won't help you, either. But if she/he can't, she/he won't even notice you have enabled MAC filtering, and most certainly won't be able to take advantage of the fact that you are broadcast your SSID.

Do you understand what I am trying to get at? Good discussion.

[Average Joe]

Thank you for that explanation. I am using the WPA2 protocol and a strong PSK key, so I feel pretty safe.

Apart from the fact that it just feels more safe to do, I also hide my SSID and use MAC filtering for two reasons:

1) If someone would break in my wireless network, he would have to use my MAC address. I know this is very easy for him to get by just sniffing my network traffic. But it would mean that I would probably lose my connection, since I expect that the MAC address can only work for one computer at a time. Therefore, I would most likely notice that my system would be compromised, and take immediate action.

2) If my SSID is hidden, I would think that in case my computer is off, there are no probe requests from my computer to my non-broadcasting network, and a potential hacker would not be able to retrieve my SSID. Therefore, during the time that I don't use my computer (i.e. it is switched off) I am more safe to attacks on the wireless network.

I understand that the attacker would still need to get around the security protocol, but assuming (for the sake of argument) that he can, I think using MAC address filtering and a hidden SSID has some additional value, that is not only existing in the head of the user.

[wieman01]

Thank you for that explanation. I am using the WPA2 protocol and a strong PSK key, so I feel pretty safe.

Apart from the fact that it just feels more safe to do, I also hide my SSID and use MAC filtering for two reasons:

1) If someone would break in my wireless network, he would have to use my MAC address. I know this is very easy for him to get by just sniffing my network traffic. But it would mean that I would probably lose my connection, since I expect that the MAC address can only work for one computer at a time. Therefore, I would most likely notice that my system would be compromised, and take immediate action.

2) If my SSID is hidden, I would think that in case my computer is off, there are no probe requests from my computer to my non-broadcasting network, and a potential hacker would not be able to retrieve my SSID. Therefore, during the time that I don't use my computer (i.e. it is switched off) I am more safe to attacks on the wireless network.

I understand that the attacker would still need to get around the security protocol, but assuming (for the sake of argument) that he can, I think using MAC address filtering and a hidden SSID has some additional value, that is not only existing in the head of the user.
Hello,

Both valid reasons. This is in fact my own line of thinking as well. Again, it is little extra security and with a strong PSK I doubt an attacker would even have the slightest chance of breaking it and thus compromising your network, but one never knows. :-)

[Average Joe]

I am actually wondering why I cannot use the Network manager (nm-applet) to configure my wireless network.

This applet is now showing up as an icon in my notification area, basically doing nothing. However, since I am using a laptop, I would be convenient for me to use it for easy switching between wireless networks. However, whenever I make some changes with the Network Manager (i.e. switch to roaming) I lose my connection, and what is worse, I lose my settings as well, making me have to recreate the /etc/network/interfaces file from scratch again. This happens even after having saved (and reloaded) the working configuration in nm-applet.

This leaves me with two questions:

1) Is it not possible to use the Network-manager after having followed the how-to in the first post?

2) Is there another way to switch easily between wireless networks?

[wieman01]

@Average Joe:

If you configure your network/device using this approach, you cannot use NM any more. But there are options:

1. WICD (http://wicd.sourceforge.net/)
2. Wifi-Radar (repositories)

[Average Joe]

Thanks for pointing that out wieman01!

I tried them both. Wifi-radar didn't work too well for me. It shows all the wireless networks in range, but it does not show the signal strengths nor the encryption type. What is worse, I cannot edit any configuration with it, so I removed it.

However, Wicd works great! It shows all the information I want, and I can change all the settings for my wireless connection. I usually don't install applications outside the Ubuntu repositories, but for Wicd I made an exception.

I actually hate to tell you this, but I have now cleared all the wireless settings my /etc/network/interfaces file that you described so well in your nice how-to, and I also removed the additional network restart script that I required earlier. With Wicd I simply don't need it any longer.

I could very easy configure my wireless network settings with Wicd (I am using WPA2 with AES and a fixed IP address). I also don't need to convert my WPA ascii key to a hexadecimal pass phrase. All in all it seems less of a hassle to get my wireless network to work, plus I think with Wicd it seems easier to switch from one network to the other.

I think Wicd is actually what I have been looking for, I haven't experienced any drawbacks yet.

[wieman01]

Thanks for pointing that out wieman01!

I tried them both. Wifi-radar didn't work too well for me. It shows all the wireless networks in range, but it does not show the signal strengths nor the encryption type. What is worse, I cannot edit any configuration with it, so I removed it.

However, Wicd works great! It shows all the information I want, and I can change all the settings for my wireless connection. I usually don't install applications outside the Ubuntu repositories, but for Wicd I made an exception.

I actually hate to tell you this, but I have now cleared all the wireless settings my /etc/network/interfaces file that you described so well in your nice how-to, and I also removed the additional network restart script that I required earlier. With Wicd I simply don't need it any longer.

I could very easy configure my wireless network settings with Wicd (I am using WPA2 with AES and a fixed IP address). I also don't need to convert my WPA ascii key to a hexadecimal pass phrase. All in all it seems less of a hassle to get my wireless network to work, plus I think with Wicd it seems easier to switch from one network to the other.

I think Wicd is actually what I have been looking for, I haven't experienced any drawbacks yet.
Excellent! So this exercise did have a purpose. :-)

No problem, if WICD works best for you, so be it. Good news.

[wangrui]

Help please!

I have search for a very long time but still can't find any article talking about how to make LEAP wireless working.
This is my /etc/network/interfaces:



auto lo
iface lo inet loopback

iface ath0 inet dhcp
wpa-ap-scan 1
wpa-eap LEAP
wpa-identity <username>
wpa-password <password>
wireless-essid IBM

iface eth0 inet dhcp
address 10.1.0.5
netmask 255.255.255.0
gateway 10.1.0.1

auto eth0


But I can't get any IP, and ESSID is using another one:

iwconfig ath0


ath0 IEEE 802.11g ESSID:"IBMVISITOR" Nickname:""
Mode:Managed Frequency:2.422 GHz Access Point: Not-Associated
Bit Rate:1 Mb/s Tx-Power:8 dBm Sensitivity=1/1
Retry:off RTS thr:off Fragment thr:off
Power Management:off
Link Quality=3/70 Signal level=-92 dBm Noise level=-95 dBm
Rx invalid nwid:1700 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


ifconfig


ath0 Link encap:Ethernet HWaddr 00:19:7E:0D:B4:29
inet6 addr: fe80::219:7eff:fe0d:b429/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
wifi0 Link encap:UNSPEC HWaddr 00-19-7E-0D-B4-29-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:30318 errors:0 dropped:0 overruns:0 frame:49856
TX packets:6272 errors:5 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:199
RX bytes:4462881 (4.2 MB) TX bytes:288404 (281.6 KB)
Interrupt:21


sudo dhclient ath0
and same result with "sudo dhclient wifi0"


There is already a pid file /var/run/dhclient.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:19:7e:0d:b4:29
Sending on LPF/ath0/00:19:7e:0d:b4:29
Sending on Socket/fallback
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 6
No DHCPOFFERS received.
No working leases in persistent database - sleeping.


Can anybody help me? I still don't know whether ubuntu can support LEAP or not. If there is any library missing, I can copy them from another working OS (Our company offers all kind of software in a single package with Red Hat 5.1, but it's really unbelievable unbelievable unbelievable hard to use, besides a huge amount of spyware installed by the company). I don't know anything about linux networking. Some expert please help me. Even some instructions will be greatly appreciated. If somebody tell me how to do it, I can install a RH5.1 first, copy necessary files out, then throw it away.

[wieman01]

Hello wangrui:

First off I see that you are using a wireless adapter with an Atheros chipset. LEAP is a proprietary protocol developed by Cisco, so I cannot guarantee that the current Linux driver supports it. Actually I doubt it.

LEAP should not be used anyway, as it is highly insecure.

When you try to connect, please post the follwing:

sudo ifdown -v ath0

sudo ifup -v ath0
And also:

sudo iwlist scan

sudo lshw -C network

[wangrui]

Hi wieman01,

Thank you very much! This forum is really amazing. Every question is being answered without any delay. How can you guys do this. It's amazing service. Sometime, it may take me two days to reply all of the mails in my mailbox, even that's my work.

I have almost learned everything about LEAP recently. I know LEAP is insecure. There is also a EAP-TLS available, but whatever, I'm in a big building with may layered security. That won't be a problem.

Please see the detail. Thanks for your help.

sudo ifdown -v ath0


Configuring interface ath0=ath0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.ath0.pid -lf /var/lib/dhcp3/dhclient.ath0.leases ath0
There is already a pid file /var/run/dhclient.ath0.pid with pid 7366
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:19:7e:0d:b4:29
Sending on LPF/ath0/00:19:7e:0d:b4:29
Sending on Socket/fallback
ifconfig ath0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.ath0.pid
Stopped /sbin/wpa_supplicant (pid 7341).


sudo ifup -v ath0


Configuring interface ath0=ath0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: using default driver type: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.ath0.pid -i ath0 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/ath0
wpa_supplicant: wpa-ap-scan 1 -- OK

dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.ath0.pid -lf /var/lib/dhcp3/dhclient.ath0.leases ath0
There is already a pid file /var/run/dhclient.ath0.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:19:7e:0d:b4:29
Sending on LPF/ath0/00:19:7e:0d:b4:29
Sending on Socket/fallback
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 10
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/openssh-server
run-parts: executing /etc/network/if-up.d/wpasupplicant
run-parts: executing /etc/network/if-up.d/wrfirewall


for "sudo iwlist scan", there are 21 Cell from "Cell 01" to "Cell 21", with similar output:


ath0 Scan completed :
Cell 01 - Address: 00:17:59:DB:41:F0
ESSID:"IBM"
Mode:Master
Frequency:2.412 GHz (Channel 1)
Quality=52/70 Signal level=-43 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
...



sudo lshw -C network:


*-network
description: Wireless interface
product: AR5212 802.11abg NIC
vendor: Atheros Communications, Inc.
physical id: 0
bus info: pci@0000:03:00.0
logical name: wifi0
version: 01
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=ath_pci driverversion=0.9.4.5 (0.9.3.2) latency=0 module=ath_pci multicast=yes wireless=IEEE 802.11g


Thank you for looking into the problem. If it can't work, maybe I can copy some files from RedHat, but I don't know how to do it.

[wieman01]

Wangrui:

Guess we really enjoy what we are doing. So response time just reflects that. :-)

This does not look promising:

wpa_supplicant: wpa-ap-scan 1 -- OK
There should be a line for each line in "/etc/network/interfaces". I don't think the current driver supports LEAP.

Second you have cut off the interesting part of the scan... Could you scan once again and list the entire block pertaining to the network in question?

If all this does not yield any results, you probably have to replace the driver... You can do so using a tool called "ndiswrapper" which basically lets you install & use the Windows driver. Pretty cool, I used it as well for one of my Linksys adapters.

Get back to me and we'll see. :-)

[wangrui]

Wangrui:

Guess we really enjoy what we are doing. So response time just reflects that. :-)

This does not look promising:

There should be a line for each line in "/etc/network/interfaces". I don't think the current driver supports LEAP.

Second you have cut off the interesting part of the scan... Could you scan once again and list the entire block pertaining to the network in question?

If all this does not yield any results, you probably have to replace the driver... You can do so using a tool called "ndiswrapper" which basically lets you install & use the Windows driver. Pretty cool, I used it as well for one of my Linksys adapters.

Get back to me and we'll see. :-)

Hi wieman01,

So glad you guys are having passion. I have passion years ago, but can't find any exciting topic recently.

Thank you for the tip. If the current driver don't support LEAP. Do you know what is the driver looks like? Is it a so or kernel module? Because I has a runnable system, maybe it's very easy for me if I can find it out. I just copy it and do some modprobe or linking.

Sorry about the missing lines. I cut two parts of the output. One is lshw, I remove the line which contains the serial no. The other one is the iwlist scan, because I don't understand it and not sure whether it's confidential or not. But after some googling, I found a similar line which only some position of the zeros is different. So I guess it's not confidential. The missing line looks something like:


Extra:wme_ie=dd180050f2020101810003a4000027a400004 2435e0062322f00

All cell is exactly the same.

[wieman01]

You are welcome of course.

A scan will not reveal anything confidential... Kind of would defeat the purpose of a security feature, don't you think? :-)

See, when you scan for networks, cards that support LEAP would state the encryption and authentication type. If no such information is given (only "Encryption key:on" for instance) then it does not recognize the encryption/authentication type. That's bad news.

Are you on Ubuntu 64-bit?

I use "ndiswrapper" with another chipset, so I won't be of much help. But first thing you should do is check if your card is listed here:

http://ndiswrapper.sourceforge.net/joomla/index.php?/component/option,com_openwiki/Itemid,33/id,list/

If it is, get the latest Windows driver for your adapter from the vendor's website, the 64-bit version if you are on 64-bit Ubuntu. Then deploy it using 'ndiswrapper'.

Check out my Ralink tutorial (signature) to get a feel for what you will have to do. And simply post here if you have further questions, I'll try to help you.

[wangrui]

You are welcome of course.

A scan will not reveal anything confidential... Kind of would defeat the purpose of a security feature, don't you think? :-)

See, when you scan for networks, cards that support LEAP would state the encryption and authentication type. If no such information is given (only "Encryption key:on" for instance) then it does not recognize the encryption/authentication type. That's bad news.

Are you on Ubuntu 64-bit?

I use "ndiswrapper" with another chipset, so I won't be of much help. But first thing you should do is check if your card is listed here:

http://ndiswrapper.sourceforge.net/joomla/index.php?/component/option,com_openwiki/Itemid,33/id,list/

If it is, get the latest Windows driver for your adapter from the vendor's website, the 64-bit version if you are on 64-bit Ubuntu. Then deploy it using 'ndiswrapper'.

Check out my Ralink tutorial (signature) to get a feel for what you will have to do. And simply post here if you have further questions, I'll try to help you.

Thanks a lot. Do you mean it's my network card driver don't support LEAP. If I can find a workable network card driver, everything will work?

I will have a try some later time. Thank you!

[wieman01]

Thanks a lot. Do you mean it's my network card driver don't support LEAP. If I can find a workable network card driver, everything will work?

I will have a try some later time. Thank you!
I am pretty sure the current does not work.

So you need to replace it with 'ndiswrapper' and the respective Windows driver. Please try to get the right Windows driver for your card, check the link that I have provided, and install away. :-)

Please make sure you get the right version of the Windows driver. 64-bit one if you are on Ubuntu 64-bit, 32-bit one on a 32-bit Ubuntu machine.

[wangrui]

I am pretty sure the current does not work.

So you need to replace it with 'ndiswrapper' and the respective Windows driver. Please try to get the right Windows driver for your card, check the link that I have provided, and install away. :-)

Please make sure you get the right version of the Windows driver. 64-bit one if you are on Ubuntu 64-bit, 32-bit one on a 32-bit Ubuntu machine.

LEAP is working on my machine!

But I didn't use Windows driver, because I don't have it. The windows driver is installed through a company website. And it has dependency with a lot of other softwares. It's not separatable.

I got some helps from the following forum:

http://ubuntuforums.org/showthread.php?t=235655
http://ubuntuforums.org/showthread.php?t=235655&page=3

The things I tried are the following, not sure which one actually makes it work.

1. Install vpnc and madwifi
2. Modify /etc/network/interfaces to


iface ath0 inet dhcp
wpa-ssid IBM
wpa-scan-ssid 1
wpa-auth-alg OPEN
wpa-key-mgmt IEEE8021X
wpa-eap LEAP
wpa-ap-scan 2
wpa-identity <name>
wpa-password <password>

3. run the following


export IF_WPA_DRIVER=madwifi
sudo ifdown -v eth0
sudo ifdown -v ath0
sudo ifup -v ath0


I have the following files at /etc/network/if-pre-up.d


ls -lA /etc/network/if-pre-up.d/
total 8
-rwxr-xr-x 1 root root 1777 2007-05-01 12:48 madwifi
-rwxr-xr-x 1 root root 2358 2007-04-28 05:37 wireless-tools
lrwxrwxrwx 1 root root 32 2008-01-28 19:36 wpasupplicant -> ../../wpa_supplicant/ifupdown.sh


The following are some weird keywords for google crawler. So next time I can find this page easily if I need to setup the machine again (Leap really has other meanings, it's not a good keyword for searching, but I guess LEAPwirelessT60P was a unique keyword):
How to make LEAPwireless work on Lenovo T60P AR5212 802.11abg NIC - LEAPwirelessT60P

[wieman01]

Hello Wangrui:

Congrats & thanks for sharing this with us.

I think you might be able to use Network Manager or WICD as well, so there is little need for a manual configuration. You could try, since it will make roaming a lot easier for you.

[excogitation]

Just wanted to say thanks (post #2).

Although I don't really understand what

sudo ln -s /etc/init.d/wireless-network.sh /etc/rcS.d/S40wireless-network
does (total linux noob).

Is the "/etc/rcS.d/" sth. like an "autostart" folder?
Do the Sxx have to be uniques?

Mine is now S41wireless-network because there already was
a "symbolic link"? S40networking.

You see - I have no idea what I'm talking about - nonetheless my Ubuntu now goes online during? startup without extra fiddling.

[wieman01]

"/etc/rcS.d/" is indeed an autostart folder. You could do some more reading concerning run-levels, etc. That'll shed some light on the issue. Interesting stuff.

The number does not have to be unique though. The whole file name, yes, but the first 3 characters (S..) are up to you pretty much. So you might as well call it "S41wireless-network", it won't do any damage nor overwrite any other files/links starting with "S40".

[excogitation]

Ok, thanks.
I certainly have to do a lot of reading - if only the day hadn't just 24 hours.

[aarumugham]

Hello all.

I have a Dell Vostro 1500 with a broadcom 1390 card, I am dual booting with XP and Linux Mint (Daryna).

I have been slaving over this for days with no success.

Here is the output for various commands:

akilan@akilan-linux:~$ sudo iwlist eth1 scan
[sudo] password for akilan:
eth1 Scan completed :
Cell 01 - Address: 00:1B:5B:66:B1:99
ESSID:"2WIRE619"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:7/100 Signal level:-91 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 02 - Address: 00:0C:41:CA:6F:E7
ESSID:"RNSNDS"
Protocol:IEEE 802.11b
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:3/100 Signal level:-94 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 03 - Address: 00:90:4C:91:00:01
ESSID:"aarumugham"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:46/100 Signal level:-66 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : PSK



So my card appears to be working and recognized. It recognizes my network (cell 03).

I cannot for the life of me connect to it! WPA-PSK security. ssid broadcast enabled.


other useful info:


akilan@akilan-linux:~$ sudo /usr/lib/linuxmint/mintWifi/mintWifi.py
[sudo] password for akilan:
-------------------------
* I. scanning WIFI PCI devices...
-- Broadcom Corporation BCM94311MCG wlan mini-PCI (rev 01)
==> PCI ID = 14e4:4311 (rev 01)
-------------------------
* II. querying ndiswrapper...
bcmwl5 : driver installed
device (14E4:4311) present (alternate driver: bcm43xx)
-------------------------
* III. querying iwconfig...
lo no wireless extensions.

eth0 no wireless extensions.

eth1 IEEE 802.11g ESSID:off/any
Mode:Managed Frequency:2.462 GHz Access Point: Not-Associated
Bit Rate:54 Mb/s Tx-Power:32 dBm
RTS thr:2347 B Fragment thr:2346 B
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

-------------------------
* IV. querying ifconfig...
eth0 Link encap:Ethernet HWaddr 00:1C:23:89:86:F5
inet addr:192.168.1.12 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:741 errors:0 dropped:0 overruns:0 frame:0
TX packets:543 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:844112 (824.3 KB) TX bytes:82891 (80.9 KB)
Interrupt:17

eth1 Link encap:Ethernet HWaddr 00:1C:26:0F:44:4F
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:17 Memory:f9ffc000-fa000000

eth1:avah Link encap:Ethernet HWaddr 00:1C:26:0F:44:4F
inet addr:169.254.3.49 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Interrupt:17 Memory:f9ffc000-fa000000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:551 errors:0 dropped:0 overruns:0 frame:0
TX packets:551 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:49899 (48.7 KB) TX bytes:49899 (48.7 KB)

-------------------------
* V. querying DHCP...
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:1c:26:0f:44:4f
Sending on LPF/eth1/00:1c:26:0f:44:4f
Listening on LPF/eth0/00:1c:23:89:86:f5
Sending on LPF/eth0/00:1c:23:89:86:f5
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
DHCPOFFER from 192.168.1.10
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 192.168.1.10
bound to 192.168.1.12 -- renewal in 1415 seconds.
-------------------------
* VI. querying nslookup google.com...
Server: 24.93.41.127
Address: 24.93.41.127#53

Non-authoritative answer:
Name: google.com
Address: 72.14.207.99
Name: google.com
Address: 64.233.187.99
Name: google.com
Address: 64.233.167.99



akilan@akilan-linux:~$ sudo gedit /etc/network/interfaces yields the following:



auto lo
iface lo inet loopback

auto eth1
iface eth1 inet dhcp
wpa-driver ndiswrapper
wpa-ssid aarumugham
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 54ac59b66eb01a8e93f07xx9543xx86a085b53ea1x63c4xxxx x339a9a0a2b9e75361
pre-up wpa_supplicant -Bw -Dndiswrapper -ieth1 -c/etc/wpa_supplicant.conf
post-down killall -q wpa_supplicant


the wpa_supplicant file contains the following:


ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
network={
ssid="aarumugham"
scan_ssid=1
proto=WPA
# key_mgmt=WPA-PSK
# psk = 0...7
psk="e...1"
# key_mgmt=WPA-PSK
# pairwise=TKIP
# group=TKIP
}





thanks in advance for your help.

[wieman01]

aarumugham:

Please also post:

sudo lshw -C network

sudo ifdown -v eth1

sudo ifup -v eth1
What hardware have you got? And what chipset is your wireless adapter?

[aarumugham]

wieman, i really appreciate your help! here is the info:

akilan@akilan-linux:~$ sudo lshw -C network


[sudo] password for akilan:
*-network
description: Wireless interface
product: BCM94311MCG wlan mini-PCI
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:0c:00.0
logical name: eth1
version: 01
serial: 00:1c:26:0f:44:4f
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+bcmwl5 driverversion=1.52+Broadcom,10/12/2006, 4.100. latency=0 link=no module=ndiswrapper multicast=yes wireless=IEEE 802.11g
*-network
description: Ethernet interface
product: BCM4401-B0 100Base-TX
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:03:00.0
logical name: eth0
version: 02
serial: 00:1c:23:89:86:f5
size: 100MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=b44 driverversion=1.01 duplex=full ip=192.168.1.12 latency=64 link=yes module=b44 multicast=yes port=twisted pair speed=100MB/s


akilan@akilan-linux:~$ sudo ifdown -v eth1


Configuring interface eth1=eth1 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.eth1.pid -lf /var/lib/dhcp3/dhclient.eth1.leases eth1
There is already a pid file /var/run/dhclient.eth1.pid with pid 6064
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:1c:26:0f:44:4f
Sending on LPF/eth1/00:1c:26:0f:44:4f
Sending on Socket/fallback
ifconfig eth1 down
killall -q wpa_supplicant
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant





akilan@akilan-linux:~$ sudo ifdown -v eth1


Configuring interface eth1=eth1 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.eth1.pid -lf /var/lib/dhcp3/dhclient.eth1.leases eth1
There is already a pid file /var/run/dhclient.eth1.pid with pid 6064
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:1c:26:0f:44:4f
Sending on LPF/eth1/00:1c:26:0f:44:4f
Sending on Socket/fallback
ifconfig eth1 down
killall -q wpa_supplicant
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant





HARDWARE:

I cut/pasted from the following : akilan@akilan-linux:~$ $sudo lshw
hopefully this gives you the information you need.



description: Computer
width: 32 bits
*-core
description: Motherboard
physical id: 0
*-memory
description: System memory
physical id: 0
size: 2025MB
*-cpu
product: Intel(R) Core(TM)2 Duo CPU T5470 @ 1.60GHz

*-pci
description: Host bridge
product: Mobile PM965/GM965/GL960 Memory Controller Hub

*-pci:0
description: PCI bridge
product: Mobile PM965/GM965/GL960 PCI Express Root Port

*-display
description: VGA compatible controller
product: GeForce 8400M GS

*-usb:0-6
description: USB Controller

*-multimedia
description: Audio device
product: 82801H (ICH8 Family) HD Audio Controller

*-pci:1-4
description: PCI bridge
product: 82801H (ICH8 Family) PCI Express Port 1

*-network
description: Wireless interface
product: BCM94311MCG wlan mini-PCI
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:0c:00.0
logical name: eth1
version: 01
serial: 00:1c:26:0f:44:4f
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+bcmwl5 driverversion=1.52+Broadcom,10/12/2006, 4.100. latency=0 module=ndiswrapper multicast=yes wireless=IEEE 802.11g

*-network
description: Ethernet interface
product: BCM4401-B0 100Base-TX
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:03:00.0
logical name: eth0
version: 02
serial: 00:1c:23:89:86:f5
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=b44 driverversion=1.01 ip=192.168.1.12 latency=64 module=b44 multicast=yes

RICOH card reader, firewire.

*-cdrom
description: DVD writer
product: DVD+-RW GSA-T11N
vendor: HL-DT-ST

capabilities: removable audio cd-r cd-rw dvd dvd-r
configuration: ansiversion=5 status=open
*-ide:1
description: IDE interface
product: 82801HBM/HEM (ICH8M/ICH8M-E) SATA IDE Controller

*-serial UNCLAIMED
description: SMBus
product: 82801H (ICH8 Family) SMBus Controller
vendor: Intel Corporation

[wieman01]

OK, you use 'ndiswrapper' with a Broadcom driver. Please make "/etc/network/interfaces" read:

auto lo
iface lo inet loopback

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-ssid aarumugham
wpa-ap-scan 1
wpa-proto WPA RSN
wpa-pairwise TKIP CCMP
wpa-group TKIP CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 54ac59b66eb01a8e93f07xx9543xx86a085b53ea1x63c4xxxx x339a9a0a2b9e75361
Then restart the network:

sudo ifdown -v eth1

sudo ifup -v eth1
Does that work?

[aarumugham]

wieman - you rule! a thousand thanks!

i added the startup script at the begining of this thread and everything is working great!

if you have a moment, just a few questions so that i can learn,

what is the idea behind the changes?
why wext? why ap scan 1?

do i still need the wpa_supplicant file at all?

is there a way i could have multiple profiles saved and just pick one from a list when i am in a different spot?

thanks,

akilan

[wieman01]

aarumugham,

Unfortunately there is no way to have multiple profile with this approach.

As for the changes, you use WPA1 (TKIP) rather than WPA2. That's why I added WPA and TKIP. You SSID isn't hidden, hence "ap scan 1". And 'wext' is the right driver for 'ndiswrapper'.

You won't need "wpa_supplicant" if you have followed this tutorial.

Does this help?

[DieselSnorter]

I'm not able to get mine to connect to my WPA2 network. It was for a while when I was broadcasting the SSID (but it was VERY sketchy), then I tried to configure it based on the 1st post here, and now it won't connect to anything. Sadly, the PC I'm working doesn't have a connection now (hence the reason I'm here) so I have to type everything over.
I'm trying to use a Belkin Wireless G USB adapter.
my /etc/network/interfaces looks like this:

auto wlan1
iface wlan1 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid MYSSSID
wpa-ap scan 1
wpa -proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk MYKEYSTRINGOFTESTJUNK

if I run:
sudo iwlist scan:
it finds my network and two others.

sudo lshw -C network:
*-network
description: wireless interface
physical id 1
logical name: wlan1
serial: 00:1c:df:1c:49:1c
capabilities: ethernet phyical wirelesss
configuration: broadcast-yes multicast=yes wireless=IEEE 802.11g

My network is WPA2 with DHCP. I'd rather have it hidden, but at this point, I'll take what I can get.

[wieman01]

To undo the changes, simply remove the lines you have added in the first place and restart the PC. It's as simple as that.

Please post this after you have working internet connection. This information is very important:

sudo iwlist scan

sudo ifdown -v wlan1

sudo ifup -v wlan1
What chipset is your wireless adapter?

[DieselSnorter]

okay, I'm on the Linux machine now.


$ sudo iwlist scan
lo Interface doesn't support scanning.

eth1 Interface doesn't support scanning.

wmaster0 Interface doesn't support scanning.

wlan1 Scan completed :
Cell 01 - Address: 00:18:01:FB:D1:41
ESSID:"3U437"
Mode:Master
Channel:1
Frequency:2.412 GHz
Signal level=-68 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=00000035ec262e2c
Cell 02 - Address: 00:0F:66:E4:73:5E
ESSID:"XXXX"
Mode:Master
Channel:6
Frequency:2.437 GHz
Signal level=-72 dBm
Encryption key:on
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:tsf=0000001ee2405713
Cell 03 - Address: 00:18:01:F6:C4:2E
ESSID:"58864"
Mode:Master
Channel:11
Frequency:2.462 GHz
Signal level=-68 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=000000235bb7cd97


$ sudo ifdown -v wlan1
Configuring interface wlan1=wlan1 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/50firestarter
* Stopping the Firestarter firewall...
...done.
* Starting the Firestarter firewall...
...done.
run-parts: executing /etc/network/if-down.d/avahi-autoipd
RTNETLINK answers: No such process
run-parts: executing /etc/network/if-down.d/clamav-freshclam-ifupdown
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.wlan1.pid -lf /var/lib/dhcp3/dhclient.wlan1.leases wlan1
There is already a pid file /var/run/dhclient.wlan1.pid with pid 18580
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan1/00:1c:df:1c:49:1c
Sending on LPF/wlan1/00:1c:df:1c:49:1c
Sending on Socket/fallback
DHCPRELEASE on wlan1 to 192.168.1.100 port 67
ifconfig wlan1 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/hostapd
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan1.pid
Stopped /sbin/wpa_supplicant (pid 17412).


$ sudo ifdown -v wlan1
Configuring interface wlan1=wlan1 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/50firestarter
* Stopping the Firestarter firewall...
...done.
* Starting the Firestarter firewall...
...done.
run-parts: executing /etc/network/if-down.d/avahi-autoipd
RTNETLINK answers: No such process
run-parts: executing /etc/network/if-down.d/clamav-freshclam-ifupdown
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.wlan1.pid -lf /var/lib/dhcp3/dhclient.wlan1.leases wlan1
There is already a pid file /var/run/dhclient.wlan1.pid with pid 18580
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan1/00:1c:df:1c:49:1c
Sending on LPF/wlan1/00:1c:df:1c:49:1c
Sending on Socket/fallback
DHCPRELEASE on wlan1 to 192.168.1.100 port 67
ifconfig wlan1 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/hostapd
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan1.pid
Stopped /sbin/wpa_supplicant (pid 17412).
god@Deus-ex-machina:/etc/network$ sudo ifup -v wlan1
Configuring interface wlan1=wlan1 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/hostapd
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan1.pid -i wlan1 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan1
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "XXXX" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto WPA -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.wlan1.pid -lf /var/lib/dhcp3/dhclient.wlan1.leases wlan1
There is already a pid file /var/run/dhclient.wlan1.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan1/00:1c:df:1c:49:1c
Sending on LPF/wlan1/00:1c:df:1c:49:1c
Sending on Socket/fallback
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 7
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/50firestarter
* Stopping the Firestarter firewall...
...done.
* Starting the Firestarter firewall...
...fail!
run-parts: /etc/network/if-up.d/50firestarter exited with return code 2
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/clamav-freshclam-ifupdown
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/openssh-server
run-parts: executing /etc/network/if-up.d/wpasupplicant

I believe my adapter is using an RT2570 chipset.

[wieman01]

Your network is a WPA one as far as I can tell. Please try this script:

auto wlan1
iface wlan1 inet dhcp
wpa-driver wext
wpa-ssid MYSSSID
wpa-ap scan 1
wpa -proto RSN WPA
wpa-pairwise CCMP TKIP
wpa-group CCMP TKIP
wpa-key-mgmt WPA-PSK
wpa-psk MYKEYSTRINGOFTESTJUNK
I have thrown out "wpa-conf managed".

Please then post:

sudo ifdown -v wlan1

sudo ifup -v wlan1
If this is a Ralink chipset I cannot promise this will work. Ralink Linux drivers are problematic.

[DieselSnorter]

wow, that works like a champ. I had to make one modification, i'm not using TKIP, I'm using AES. So for the places you put TKIP, I put AES.


/ sudo ifdown -v wlan1
Configuring interface wlan1=wlan1 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/50firestarter
* Stopping the Firestarter firewall...
...done.
* Starting the Firestarter firewall...
...done.
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/clamav-freshclam-ifupdown
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.wlan1.pid -lf /var/lib/dhcp3/dhclient.wlan1.leases wlan1
There is already a pid file /var/run/dhclient.wlan1.pid with pid 6352
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan1/00:1c:df:1c:49:1c
Sending on LPF/wlan1/00:1c:df:1c:49:1c
Sending on Socket/fallback
DHCPRELEASE on wlan1 to 192.168.1.100 port 67
ifconfig wlan1 down
killall -q wpa_supplicant
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/hostapd
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant


sudo ifup -v wlan1
Configuring interface wlan1=wlan1 (inet)
wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant/wpa_supplicant.conf -Bw
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/hostapd
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan1.pid -i wlan1 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan1
wpa_supplicant: wpa-ap-scan 1 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "XXX" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise CCMP AES -- FAIL
wpa_supplicant: wpa-group CCMP AES -- FAIL
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto RSN WPA -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.wlan1.pid -lf /var/lib/dhcp3/dhclient.wlan1.leases wlan1
There is already a pid file /var/run/dhclient.wlan1.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan1/00:1c:df:1c:49:1c
Sending on LPF/wlan1/00:1c:df:1c:49:1c
Sending on Socket/fallback
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 13
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/50firestarter
* Stopping the Firestarter firewall...
...done.
* Starting the Firestarter firewall...
...fail!
run-parts: /etc/network/if-up.d/50firestarter exited with return code 2
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/clamav-freshclam-ifupdown
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/openssh-server
run-parts: executing /etc/network/if-up.d/wpasupplicant

Anything else i can do? Should I try turning off the SSID broadcast?

[DieselSnorter]

actually, I seem to have spoken too soon. It seems I get connected for about 5-10 minutes...then it just gives up.
Seems like we're getting closer though.
too be fair, it seems as though the USB device just stops responding altogether. if I try to restart networking, I get a message that the network is down. If I unplug it and plug it back in, then restart, it comes back up for a little while.

[DieselSnorter]

of course, it had to go and make a liar out of me, now it's been connected for over an hour...go figure.

[wieman01]

of course, it had to go and make a liar out of me, now it's been connected for over an hour...go figure.
Excellent. :-)

[ginge6000]

I don't get it:confused:!!!!!

I followed the instructions to the letter but as soon as I stop my wireless connection from using roaming and use a manual configuration it stops connecting! My network card is a Linksys WMP54g v7.1.

Please help as I want to be able to mount the home directories on this laptop but this will only work if it's connected to the wireless network before i logon.....

Ben

[wieman01]

I don't get it:confused:!!!!!

I followed the instructions to the letter but as soon as I stop my wireless connection from using roaming and use a manual configuration it stops connecting! My network card is a Linksys WMP54g v7.1.

Please help as I want to be able to mount the home directories on this laptop but this will only work if it's connected to the wireless network before i logon.....

Ben
Please post:

sudo iwlist scan

sudo lshw -C network

sudo cat /etc/network/interfaces

[ginge6000]

Sorry for sounding a bit thick but do you want these after I've done the manual config or when the wireless connection is working?

[wieman01]

Sorry for sounding a bit thick but do you want these after I've done the manual config or when the wireless connection is working?
Anytime you like. But only if you have problems. :-)

[ginge6000]

sudo iwlist scan:


lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wifi0 Interface doesn't support scanning.

ath0 Scan completed :
Cell 01 - Address: 00:13:49:7C:06:7C
ESSID:"porcupine"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=19/70 Signal level=-76 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:bcn_int=100
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : PSK
Extra:wme_ie=dd070050f202000100
Cell 02 - Address: 00:18:39:6A:3A:20
ESSID:"Peakes Court"
Mode:Master
Frequency:2.462 GHz (Channel 11)
Quality=40/70 Signal level=-55 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:bcn_int=100
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : PSK
Cell 03 - Address: 00:1D:68:05:54:A9
ESSID:"BTHomeHub-D171"
Mode:Master
Frequency:2.412 GHz (Channel 1)
Quality=8/70 Signal level=-87 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:wme_ie=dd180050f2020101880003a4000027a400004 2435e0062322f00
Cell 04 - Address: 00:0F:B5:7C:C1:30
ESSID:"Dovecote"
Mode:Master
Frequency:2.462 GHz (Channel 11)
Quality=9/70 Signal level=-86 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100

sudo lshw -C network:


*-network
description: Realtek
physical id: 0
version: Rtl8139
slot: Socket 0
resources: irq:10
*-network
description: AR5001-0000-0000
product: Wireless LAN Reference Card
vendor: Atheros Communications, Inc.
physical id: 0
version: 00
slot: Socket 1
resources: irq:10
*-network:0
description: Ethernet interface
product: RTL-8139/8139C/8139C+
vendor: Realtek Semiconductor Co., Ltd.
physical id: 2
bus info: pci@0000:02:00.0
logical name: eth0
version: 10
serial: 00:e0:4c:00:15:70
size: 10MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=8139too driverversion=0.9.28 duplex=half latency=64 link=no maxlatency=64 mingnt=32 module=8139too multicast=yes port=MII speed=10MB/s
*-network:1
description: Wireless interface
product: AR2413 802.11bg NIC
vendor: Atheros Communications, Inc.
physical id: 0
bus info: pci@0000:06:00.0
logical name: wifi0
version: 01
serial: 00:18:39:6a:4c:d0
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=ath_pci driverversion=0.9.4.5 (0.9.3.2) latency=168 maxlatency=28 mingnt=10 module=ath_pci multicast=yes wireless=IEEE 802.11g

sudo cat /etc/network/interfaces:


auto lo
iface lo inet loopback

auto ath0
iface ath0 inet dhcp
wpa-driver madwifi
wpa-ssid Peakes Court
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk 3521cf0e8cd00d908b43b8ca1b827cd454866ad5d0f6c99f14 13ca012455faf8

Thank you for your help with this!

[wieman01]

ginge6000:

Looks pretty neat in fact. Only one thing that might trip you up... Try another SSID without spaces e.g. "PeakesCourt". Done so please post:

sudo ifdown -v ath0

sudo ifup -v ath0
You are close.

[ginge6000]

sudo ifdown -v ath0:


Configuring interface ath0=ath0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.ath0.pid -lf /var/lib/dhcp3/dhclient.ath0.leases ath0
There is already a pid file /var/run/dhclient.ath0.pid with pid 5077
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:18:39:6a:4c:d0
Sending on LPF/ath0/00:18:39:6a:4c:d0
Sending on Socket/fallback
DHCPRELEASE on ath0 to 192.168.1.1 port 67
ifconfig ath0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.ath0.pid
Stopped /sbin/wpa_supplicant (pid 3628).

sudo ifup -v ath0:


Configuring interface ath0=ath0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver madwifi
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.ath0.pid -i ath0 -D madwifi -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/ath0
wpa_supplicant: wpa-ap-scan 1 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "PeakesCourt" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise TKIP -- OK
wpa_supplicant: wpa-group TKIP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto WPA -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.ath0.pid -lf /var/lib/dhcp3/dhclient.ath0.leases ath0
There is already a pid file /var/run/dhclient.ath0.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:18:39:6a:4c:d0
Sending on LPF/ath0/00:18:39:6a:4c:d0
Sending on Socket/fallback
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 7
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant

[wieman01]

Have you changed the SSID on both the client and the router?

Could you connect to your network while security was turned off?

[ginge6000]

Yep, SSID changed on both. Still can't connect with security turned off......

[wieman01]

Yep, SSID changed on both. Still can't connect with security turned off......
Wow... Even after removing the security modifications in "/etc/network/interfaces"? That's bad news.

Is MAC filtering enabled by chance? Your adapter appears to work, so I don't see an issue here.

While you connect via wireless, your wired connection is down i.e. cable pulled, right?

[ginge6000]

Nope, even with the security config lines removed from /etc/network/interfaces. MAC filtering is not being used. Wired connection not attached.....

What's going on! I do remember reading somewhere to make sure that "Enable Roaming" was checked to make the wireless card work. Why should this be the case?

[wieman01]

Nope, even with the security config lines removed from /etc/network/interfaces. MAC filtering is not being used. Wired connection not attached.....

What's going on! I do remember reading somewhere to make sure that "Enable Roaming" was checked to make the wireless card work. Why should this be the case?
I have no clue what's going on... :confused:

Maybe Kevdog knows the answer:

http://ubuntuforums.org/showthread.php?t=684495

[ginge6000]

Thanks for that thread, not sure how I didn't find it before. I'll have a go at that one (it seems rather involved!) and let you know how it goes!

[recon69]

Having problems setting up a wireless connection, I 'v got a Edimax EW-7128g / Ralink RT61 wireless card, it's installed and works when encryption is off. but get errors when i try with encryption on.

the problem seem to be here
/var/run/wpa_supplicant.ra0.pid -i ra0 -C /var/run/wpa_supplicant -D wext
Starting /sbin/wpa_supplicant...
ioctl[SIOCSIWPMKSA]: Network is down
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]:

look like i need a better driver. I would just upgrade to 6.10 but that not working for me eather. stuck.

any help welcome




here is some details




mec@ubuntu-mec:~$ route
Kernel IP routeing table
Destination Gateway Genmask Flags Metric Ref Use Iface
mec@ubuntu-mec:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

ra0 RT61 Wireless ESSID:""
Mode:Auto Frequency:1 MHz Bit Rate=54 Mb/s
RTS thr:off Fragment thr:off
Link Quality=0/70 Signal level:-121 dBm Noise level:-111 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

sit0 no wireless extensions.

mec@ubuntu-mec:~$ sudo iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

ra0 Scan completed :
Cell 01 - Address: 00:17:3F:15:E3:06
Mode:Managed
ESSID:"topcat"
Encryption key:on
Channel:1

sit0 Interface doesn't support scanning.

mec@ubuntu-mec:~$ sudo lshw -C network
*-network:0 DISABLED
description: Ethernet interface
product: SiS900 PCI Fast Ethernet
vendor: Silicon Integrated Systems [SiS]
physical id: 4
bus info: pci@00:04.0
logical name: eth0
version: 90
serial: 00:0b:6a:62:35:0b
size: 100MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegociation
configuration: autonegociation=on broadcast=yes driver=sis900 driverversion=v1.08.09 Sep. 19 2005 duplex=full link=yes multicast=yes port=MII speed=100MB/s
resources: ioport:d400-d4ff iomemory:cfffc000-cfffcfff irq:201
*-network:1
description: Network controller
product: RaLink
vendor: RaLink
physical id: b
bus info: pci@00:0b.0
version: 00
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list
configuration: driver=rt61
resources: iomemory:cfff0000-cfff7fff irq:201
*-network
description: Wireless interface
physical id: 1
logical name: ra0
serial: 00:0e:2e:f5:d1:be
capabilities: ethernet physical wireless
configuration: broadcast=yes multicast=yes wireless=RT61 Wireless
mec@ubuntu-mec:~$ sudo cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
#auto eth0
#iface eth0 inet dhcp

auto ra0
iface ra0 inet dhcp
wpa-driver wext
wpa-ssid topcat
wpa-ap-scan 1
wpa-proto WPA RSN
wpa-pairwise TKIP CCMP
wpa-group TKIP CCMP
wpa-key-mgmt WPA-PSK
wpa-psk d65c0c06184279e872c98ba82c24ac83a36839df5d9d257df2 f6e8c5f39cca7b
mec@ubuntu-mec:~$ sudo ifdown -v ra0
Configuring interface ra0=ra0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/wpasupplicant
wpa_supplicant: ctrl_interface=/var/run/wpa_supplicant
dhclient3 -r -pf /var/run/dhclient.ra0.pid -lf /var/lib/dhcp3/dhclient.ra0.leases ra0
Internet Systems Consortium DHCP Client V3.0.3
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

Listening on LPF/ra0/00:0e:2e:f5:d1:be
Sending on LPF/ra0/00:0e:2e:f5:d1:be
Sending on Socket/fallback
DHCPRELEASE on ra0 to 192.168.2.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
ifconfig ra0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: ctrl_interface=/var/run/wpa_supplicant
wpa_supplicant: terminating wpa_supplicant daemon
Stopped wpa_supplicant (pid 3245).
mec@ubuntu-mec:~$ sudo ifup -v ra0
Configuring interface ra0=ra0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: ctrl_interface=/var/run/wpa_supplicant
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.ra0.pid -i ra0 -C /var/run/wpa_supplicant -D wext
Starting /sbin/wpa_supplicant...
ioctl[SIOCSIWPMKSA]: Network is down
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/ra0
wpa_supplicant: wpa-ap-scan : OK
wpa_supplicant: configuring new network block "0"wpa_supplicant: wpa-ssid : OK
wpa_supplicant: wpa-psk : OK
wpa_supplicant: wpa-pairwise : OK
wpa_supplicant: wpa-group : OK
wpa_supplicant: wpa-key-mgmt : OK
wpa_supplicant: wpa-proto : OK
wpa_supplicant: enabling network 0 : OK

dhclient3 -pf /var/run/dhclient.ra0.pid -lf /var/lib/dhcp3/dhclient.ra0.leases ra0
Internet Systems Consortium DHCP Client V3.0.3
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

Listening on LPF/ra0/00:0e:2e:f5:d1:be
Sending on LPF/ra0/00:0e:2e:f5:d1:be
Sending on Socket/fallback
DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 21
DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 2
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
Synchronizing clock to ntp.ubuntu.com...
Error : Temporary failure in name resolution
mec@ubuntu-mec:~$

[wieman01]

@recon69:

As highlighted in the tutorial, this won't work for Ralink based wireless adapters. You can either check out my Ralink tutorial (see signature) and then come back, or try WICD instead:

http://wicd.sourceforge.net/

It may work for you as well.

[Rogerwa]

I have a question on whether I can bridge my on-board wired Gb ETH0 controller and my Trendnet 443 wireless controller.

I used the tutorial oringially to get this running and it has been flawless for almost a year. Now I wan to hang an HDHomerun ATSC tuner off of the GB controller and have it obtain the DHCP address through the wireless connection.

I tried all of the Bridge-utils tutorials I can find and I just can't seem to get it to work.

Anyone have any expereince with this??

[cisforcojo]

I'm trying to follow the howto but my wireless card isn't listed in /etc/network/interfaces

All I've got is:

auto lo
iface lo inet loopback
iface eth0 inet dhcp

auto eth0



I have wireless working perfectly however with WEP encryption but want to bump up the security.

Here's my iwconfig:

eth1 IEEE 802.11g ESSID:"Tipping Point" Nickname:"Tipping Point"
Mode:Managed Frequency:2.437 GHz Access Point: 00:15:E9:05:C4:E2
Bit Rate:54 Mb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=97/100 Signal level=-27 dBm Noise level=-77 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0



Will this be a problem for me to just manually add it to /etc/network/interfaces???

EDIT: Nevermind. I got WPA working through Network Manager.

[sourcerer24]

We use WPA connection in my school and there are many different IP addresses I can connect to so a static IP address would not realy work for me. I was wondering how I could do to connect to WPA without using a static IP address.

[wieman01]

We use WPA connection in my school and there are many different IP addresses I can connect to so a static IP address would not realy work for me. I was wondering how I could do to connect to WPA without using a static IP address.
But DHCP is fairly simple. You either use Network Manager straight away or replace the static IP section e.g.:

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid <your_essid>
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk <your_hex_key> [IMPORTANT: See "WPA-PSK key generation"]
That's it.

[DieselSnorter]

okay, I'm back.
I started having a lot of issues with my PC dropping the wireless every few minutes, then it flat out wouldn't connect at all. So I did some searching and made some changes, and now I'm close, but not quite there...I can taste victory.

So, I'm now using the rt73 driver (which is what I found I'm supposedly supposed to be using for my k7s-f507050B Belkin USB stick on a dongle monstrosity). I have my interfaces files set thusly

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid <myr_essid>
wpa-ap-scan 1
wpa-proto RSN WPA
wpa-pairwise CCMP AES
wpa-group CCMP AES
wpa-key-mgmt WPA-PSK
wpa-psk <my_hex_key>
When I restart Networking I get "no DHCP Offers Received:
iwconfig shows that I'm not associated with my AP (though I was earlier...odd)
If I run a scan, it usually finds my AP, but this time I get "resource temporarily unavailable"
I'm in the process of dragging my PC into my other office so I can hardwire and get whatever info you need.

If I do a tail on syslog while trying to connect I see that it finds user avahi-autoipd and gropu avahi-autoipd, then proceeds to assign me an APIPA address...which makes sense since I can't find my DHCP server.



Please help. Thanks in advance,
Eric

[wieman01]

okay, I'm back.
I started having a lot of issues with my PC dropping the wireless every few minutes, then it flat out wouldn't connect at all. So I did some searching and made some changes, and now I'm close, but not quite there...I can taste victory.

So, I'm now using the rt73 driver (which is what I found I'm supposedly supposed to be using for my k7s-f507050B Belkin USB stick on a dongle monstrosity). I have my interfaces files set thusly

When I restart Networking I get "no DHCP Offers Received:
iwconfig shows that I'm not associated with my AP (though I was earlier...odd)
If I run a scan, it usually finds my AP, but this time I get "resource temporarily unavailable"
I'm in the process of dragging my PC into my other office so I can hardwire and get whatever info you need.

If I do a tail on syslog while trying to connect I see that it finds user avahi-autoipd and gropu avahi-autoipd, then proceeds to assign me an APIPA address...which makes sense since I can't find my DHCP server.

Please help. Thanks in advance,
Eric
Hi Eric,

As indicated in the first post, Ralink drivers are an exception somehow. They don't work like others do. You have 3 options:

1. Read this (http://ubuntuforums.org/showthread.php?t=684495) (Ralink section on WPA).
2. Install WICD (http://wicd.sourceforge.net/).
3. Replace the Ralink driver using 'ndiswapper' (see my signature) and then come back.

That's all I can advise at the moment. Ralink drivers don't support the 'wext' interface.

[DieselSnorter]

acutally, I've tried all of the above at one point or another. I have WICD installed, and I just re-set up Ndiswrapper. The issue I'm having now is that my PC won't boot if I have the USB adapter plugged in. It's rebooting now after running the steps in the ndiswrapper post.

I'm currently not getting any access point association. I used the newest driver I could find on the Belkin website for the RT73.
here's what I'm getting
ndiswrapper -l

rt73 : driver installed
device (050D:705A) present (alternate driver: rt73)

iwconfig

lo no wireless extensions.

eth1 no wireless extensions.

wlan0 RT73 WLAN ESSID:""
Mode:Managed Frequency=2.412 GHz Bit Rate=54 Mb/s
RTS thr:off Fragment thr:off
Link Quality=0/100 Signal level:-121 dBm Noise level:-11
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

my /etc/network/interfaces


auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid "****"
wpa-ap-scan 1
wpa-proto RSN WPA
wpa-pairwise CCMP AES
wpa-group CCMP AES
wpa-key-mgmt WPA-PSK
wpa-psk *********

dhclient wlan0

There is already a pid file /var/run/dhclient.pid wit
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:1c:df:1c:49:1c
Sending on LPF/wlan0/00:1c:df:1c:49:1c
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 inte
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 inte
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 inte
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

what else can I show you that would help.

sorry to be such a pain about all this.

[DieselSnorter]

ah, additionally when I try to scan with:
sudo iwlist scan

I get the following



lo Interface doesn't support scanning.

eth1 Interface doesn't support scanning.

wlan0 Failed to read scan data : Resource temporarily unavailable

[DieselSnorter]

ah...I might be on to something. I'll post back shortly.

[DieselSnorter]

nope, back where I started. I had it working once.
at the time my wireless was recognized by the system was wlan0. I managed to configure kwlan to find the right wpa_supplicant.conf file, it connected, life was good.
so I rebooted, now it's called wlan1, kwlan doesn't give me any options to do anything.

I'm finding my AP now, but it won't pull an address.

I'm going to find a good wall with which to restructure my forehead .

[wieman01]

DieselSnorter:

Odd... Are you on a 64-bit system? I mean did you install the 64-bit version of Ubuntu?

Please post this once again:

sudo iwlist scan

sudo lshw -C network

sudo ndiswrapper -l
Unplug the device and plug it in again. What's the output?

[DieselSnorter]

And poof, now it's working. I rebooted and suddenly it started working. no explanation here.

I'm going to see if I have improved performance with this driver using this setup.
I really appreciate your patience.

[DieselSnorter]

wow...this is a trial for sure. I was online for all of about 5 minutes, then it just died. I've spent hours trying to figure out why.
here is the info you've requested.

sudo iwlist scan



lo Interface doesn't support scanning.

eth1 Interface doesn't support scanning.

wlan1 Scan completed :
Cell 01 - Address: 00:0F:66:E4:73:5E
ESSID:"****"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:96/100 Signal level:-34 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK



*-network
description: Wireless interface
physical id: 1
logical name: wlan1
serial: 00:1c:df:1c:49:1c
capabilities: ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+rt73 driverversion=1.45+B
elkin,08/02/2005, 1.00.00. link=yes multicast=yes wireless=IEEE 802.11g




rt73 : driver installed
device (050D:705A) present (alternate driver: rt73)

Wicd sees my network and two others if I run sudo ifdown wlan1
but it won't connect.

right now i'm showing association with my AP


wlan1 IEEE 802.11g ESSID:"***"
Mode:Managed Frequency:2.437 GHz Access Point: 00:0F:66:E4:73:5E
Bit Rate=54 Mb/s Tx-Power:20 dBm Sensitivity=-121 dBm
RTS thr=2347 B Fragment thr=2346 B
Power Management:off
Link Quality:75/100 Signal level:-48 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

I'm thinking of uninstalling NDiswrapper, KWlan, Wicd and starting over...possibly trying wifi radar...
suggestions? This seems like it's way harder than it needs to be...but probably because I'm making it that way. sadly, the OCD I've developed from all these years in IT won't let me leave it alone. :)

[wieman01]

DieselSnorter,

Before you try any other solutions please try to change the wireless channel from 6 to something else (it's a router setting). There might be interference with other wireless networks around you. Your adapter seems to work fine.

[DieselSnorter]

I've changed it to channel 11. According to my newly installed Wifi Radar and WKifiManager, I"m getting good signal strength, I'm connected to the AP, but still not pulling an IP.
I don't think the channel was the problem as I have 3 other PC's in the house that use the same wireless connection with no issue (granted, they are windows boxes).
at this point, it's probably something silly...that one little thing that i'm forgetting, isn't that usually how it works?

[wieman01]

I've changed it to channel 11. According to my newly installed Wifi Radar and WKifiManager, I"m getting good signal strength, I'm connected to the AP, but still not pulling an IP.
I don't think the channel was the problem as I have 3 other PC's in the house that use the same wireless connection with no issue (granted, they are windows boxes).
at this point, it's probably something silly...that one little thing that i'm forgetting, isn't that usually how it works?
Yupp, pretty much. :-)

Please also try this please:

sudo ifdown -v wlan1

sudo ifup -v wlan1
Have you enabled IP tables (firewall)? E.g. via Firestarter?

[DieselSnorter]

I've tried those multiple times.
I'm wondering though, could the problem be my wpa_supplcant.conf?
I'm getting invalid configuration line errors left and write when I try to do a command line scan through wifi radar.
sudo wifi-radar -d


Line 4: Invalid Coniguration line 'network=('.
Line 5: Invalid Configuration line 'ssid="****"'.
Line 6: Invalid Configuration line 'scan_ssid=0"
and so on through line 12.

then it says "failed to read or parse configuration 'etc/wpa_supplicant/wpa_supplicant.conf
SIOCSIFNETMASK: cannot assign requested address
SIOCADDRT: Invalid Arguement

[wieman01]

I've tried those multiple times.
I'm wondering though, could the problem be my wpa_supplcant.conf?
I'm getting invalid configuration line errors left and write when I try to do a command line scan through wifi radar.
sudo wifi-radar -d

and so on through line 12.

then it says "failed to read or parse configuration 'etc/wpa_supplicant/wpa_supplicant.conf
SIOCSIFNETMASK: cannot assign requested address
SIOCADDRT: Invalid Arguement
Actually you should not be using "wpa_supplcant.conf" at all if you follow this tutorial... What does "/etc/network/interfaces" look like at the moment?

[DieselSnorter]

Sounds like I've done a great job of pooching things up :confused:

a search actually shows i have two of those files in two location, should I delete them?

my file currently reads thusly:


iface wlan1 inet dhcp
wpa-ap-scan 2
wpa-key-mgmt WPA-PSK
wpa-proto WPA
wpa-ssid ****
auto wlan1

this was not how i had it set up, it seems to have been reconfigured at some point.
fortunately, I have multiple backups of it in various states.

[wieman01]

OK, now it should read ("/etc/network/interfaces"):

auto wlan1
iface wlan1 inet dhcp
wpa-driver wext
wpa-ssid <ssid>
wpa-ap-scan 1
wpa-proto RSN WPA
wpa-pairwise CCMP AES
wpa-group CCMP AES
wpa-key-mgmt WPA-PSK
wpa-psk <passphrase>
The restart the network and post the results:

sudo ifdown -v wlan1

sudo ifup -v wlan1
That should to. SSID broadcast is enabled.

[DieselSnorter]

Here is the info you requested...as you can see we have 2 failures.


sudo ifdown -v wlan1
Configuring interface wlan1=wlan1 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/50firestarter
* Stopping the Firestarter firewall...
...done.
* Starting the Firestarter firewall...
...fail!
run-parts: /etc/network/if-down.d/50firestarter exited with return code 2
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/clamav-freshclam-ifupdown
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.wlan1.pid -lf /var/lib/dhcp3/dhclient.wlan1.leases wlan1
There is already a pid file /var/run/dhclient.wlan1.pid with pid 16889
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan1/00:1c:df:1c:49:1c
Sending on LPF/wlan1/00:1c:df:1c:49:1c
Sending on Socket/fallback
DHCPRELEASE on wlan1 to 192.168.1.100 port 67
ifconfig wlan1 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/hostapd
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan1.pid
Stopped /sbin/wpa_supplicant (pid 16783).



/etc/network$ sudo ifup -v wlan1
Configuring interface wlan1=wlan1 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/hostapd
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan1.pid -i wlan1 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan1
wpa_supplicant: wpa-ap-scan 1 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "****" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise CCMP AES -- FAIL
wpa_supplicant: wpa-group CCMP AES -- FAIL
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto RSN WPA -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.wlan1.pid -lf /var/lib/dhcp3/dhclient.wlan1.leases wlan1
There is already a pid file /var/run/dhclient.wlan1.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan1/00:1c:df:1c:49:1c
Sending on LPF/wlan1/00:1c:df:1c:49:1c
Sending on Socket/fallback
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 6
No DHCPOFFERS received.
Trying recorded lease 192.168.1.203
PING 192.168.1.100 (192.168.1.100) 56(84) bytes of data.

--- 192.168.1.100 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/50firestarter
* Stopping the Firestarter firewall...
...done.
* Starting the Firestarter firewall...
...fail!
run-parts: /etc/network/if-up.d/50firestarter exited with return code 2
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/clamav-freshclam-ifupdown
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/openssh-server
run-parts: executing /etc/network/if-up.d/wpasupplicant

[wieman01]

Damn it, my fault. I knew something was odd:


auto wlan1
iface wlan1 inet dhcp
wpa-driver wext
wpa-ssid <ssid>
wpa-ap-scan 1
wpa-proto RSN WPA
wpa-pairwise CCMP TKIP
wpa-group CCMP TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <passphrase>
Please try again...

[DieselSnorter]

LOL.


still not pulling an IP though.


sudo ifdown -v wlan1
Configuring interface wlan1=wlan1 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/50firestarter
* Stopping the Firestarter firewall...
...done.
* Starting the Firestarter firewall...
...fail!
run-parts: /etc/network/if-down.d/50firestarter exited with return code 2
run-parts: executing /etc/network/if-down.d/avahi-autoipd
RTNETLINK answers: No such process
run-parts: executing /etc/network/if-down.d/clamav-freshclam-ifupdown
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.wlan1.pid -lf /var/lib/dhcp3/dhclient.wlan1.leases wlan1
There is already a pid file /var/run/dhclient.wlan1.pid with pid 20125
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan1/00:1c:df:1c:49:1c
Sending on LPF/wlan1/00:1c:df:1c:49:1c
Sending on Socket/fallback
DHCPRELEASE on wlan1 to 192.168.1.100 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
ifconfig wlan1 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/hostapd
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan1.pid
Stopped /sbin/wpa_supplicant (pid 20027).



/etc/network$ sudo ifup -v wlan1
Configuring interface wlan1=wlan1 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/hostapd
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan1.pid -i wlan1 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan1
wpa_supplicant: wpa-ap-scan 1 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "****" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise CCMP TKIP -- OK
wpa_supplicant: wpa-group CCMP TKIP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto RSN WPA -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.wlan1.pid -lf /var/lib/dhcp3/dhclient.wlan1.leases wlan1
There is already a pid file /var/run/dhclient.wlan1.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan1/00:1c:df:1c:49:1c
Sending on LPF/wlan1/00:1c:df:1c:49:1c
Sending on Socket/fallback
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 5
No DHCPOFFERS received.
Trying recorded lease 192.168.1.203
PING 192.168.1.100 (192.168.1.100) 56(84) bytes of data.

--- 192.168.1.100 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms

No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/50firestarter
* Stopping the Firestarter firewall...
...done.
* Starting the Firestarter firewall...
...fail!
run-parts: /etc/network/if-up.d/50firestarter exited with return code 2
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/clamav-freshclam-ifupdown
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/openssh-server
run-parts: executing /etc/network/if-up.d/wpasupplicant

[wieman01]

DieselSnorter,

Odd... sure no Firestarter running? You have not configured your firewall, right?

Have you removed Network Manager WICD?

You probably have to restart the PC and manually start the wireless connection once again.

[DieselSnorter]

Firestarter isn't running. Wicd is gone (wifi radar and it can't exist together it seems).
I've rebooted now, I'm seeing where I'm getting offers from my router, but it's still not working.

Signal strength is still really good, just can't get it to take the IP from the router.

[DieselSnorter]

getting warmer...I'm connected, have an IP. Showing good to excellent signal strength at about 24 MBPS (I can live with that), but I can't get any pages to load.
oy, one thing after another.
I've got my DNS server sent in my resolv.conf...it just doesn't seem to want to pull pages.

I really hope all this mess helps someone else out.

[wieman01]

getting warmer...I'm connected, have an IP. Showing good to excellent signal strength at about 24 MBPS (I can live with that), but I can't get any pages to load.
oy, one thing after another.
I've got my DNS server sent in my resolv.conf...it just doesn't seem to want to pull pages.

I really hope all this mess helps someone else out.
Good. Please issue:

route -n
When you ping your router, do you get a response?

ping 192.168.xxx.xxx
What about Google?

ping www.google.com

[DieselSnorter]

GAH, seems today I'm back to not being able to get an IP address. I'm working on that now. I had one briefly, and tried to get some pages to load, but it was horribly slow. I have 20 MBPS service, and my laptop is moving right along, so I have to think it's the Ubuntu box.

[DieselSnorter]

Okay, I managed to get an IP address for a few minutes, here we go.


route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan1
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 wlan1
0.0.0.0 192.168.1.100 0.0.0.0 UG 100 0 0 wlan1


PING 192.168.1.100 (192.168.1.100) 56(84) bytes of data.
64 bytes from 192.168.1.100: icmp_seq=1 ttl=64 time=1350 ms
64 bytes from 192.168.1.100: icmp_seq=2 ttl=64 time=353 ms
64 bytes from 192.168.1.100: icmp_seq=3 ttl=64 time=1.61 ms
64 bytes from 192.168.1.100: icmp_seq=4 ttl=64 time=1.67 ms



ping www.google.com
PING www.l.google.com (74.125.47.147) 56(84) bytes of data.
64 bytes from 74.125.47.147: icmp_seq=1 ttl=241 time=25.4 ms
64 bytes from yw-in-f147.google.com (74.125.47.147): icmp_seq=2 ttl=240 time=25.6 ms
64 bytes from yw-in-f147.google.com (74.125.47.147): icmp_seq=3 ttl=241 time=23.1 ms
64 bytes from yw-in-f147.google.com (74.125.47.147): icmp_seq=4 ttl=240 time=1591 ms
64 bytes from yw-in-f147.google.com (74.125.47.147): icmp_seq=5 ttl=240 time=594 ms
64 bytes from yw-in-f147.google.com (74.125.47.147): icmp_seq=6 ttl=241 time=23.7 ms

my syslog has this entry:


DHCPNAK from 192.168.1.100
avahi-autoipd(wlan1)[14518]: no longer a routable address configured, restarting probe process
avai-autoipd(wlan1)[14518] got SIGTERM, quitting.

[wieman01]

GAH, seems today I'm back to not being able to get an IP address. I'm working on that now. I had one briefly, and tried to get some pages to load, but it was horribly slow. I have 20 MBPS service, and my laptop is moving right along, so I have to think it's the Ubuntu box.
Mmm... This looks like a driver issue to me. Your settings are correct, WPA is working fine, however, there is some issue with 'ndiswrapper' if I am not correct. Is your device listed here?

http://ndiswrapper.sourceforge.net/joomla/index.php?/component/option,com_openwiki/Itemid,33/id,list/

Is it listed as a compatible device? Are you on 64-bit Ubuntu?

[DieselSnorter]

pretty sure this is me

Card: Belkin F5D7050B (USB 2.0 Adaptor 802.11b/g 54Mbps) (”version 3000uk” only tested at this time)
Chipset: RT73
usbid: 050d:705A
Driver: Install the drivers for windows included in the box and fetch the .inf files from the installation directory.
Other: Works fine with WPA(PSK-TKIP) using wpa_supplicant on ubuntu 6.06 with ndiswrapper driver. Will freeze the system if removed without ifdown and/or ifconfig down on the device, and even then sometimes. Even though WPA works, I have not yet managed to succeed in using with WEP!

definitely not on 64 bit.

[DieselSnorter]

okay, getting better. I've managed to get online off and on today. So when i connect, I'll do speed tests at random periods. When I first get on, I can pull a solid 12 mbps, that I can live with. After a time it drops to about 6...then to less than 1...then I get disconnected. Is there some file or buffer that is filling up?
I found great improvement when I added my DNS server directly to my Linux machine and didn't rely on it finding my firewall to look for DNS.
Even though I'm keeping my IP over time, my connectivity just seems to quit after a while.

[wieman01]

Again, changing the wireless channel or reducing the default beacon interval (router setting) can help. But it is tough from here to judge what it could be. in my case these 2 settings made the difference and might network has been running smoothly ever since.

Default beacon interval is 40 at the moment.

[DieselSnorter]

I'll give it a shot and see what happens.
Again, a million thanks for all your help with this issue. if you ever make it to Florida, the beer is on me.

[wieman01]

I'll give it a shot and see what happens.
Again, a million thanks for all your help with this issue. if you ever make it to Florida, the beer is on me.
Haha... Thanks, buddy. Nice working with you.

[izle]

hello,

it seems to be a very nice tutorial... but it doesn't help yet...

My house mate just broke our fine old router and purchased a new one. Everything was fine with the old one using wpa_supplicant, but I can't connect to the new one. I followed many of the tips in this How to but nothing worked...

But I just figured out that my wireless card is a 802.11b and the router is (via iwlist scan) a 802.11g, would that be the problem? Is it possible to change the 802.11g into a 802.11b in the configuration of the router? I seriously doubt about it...thanks to my housemate.... :(

regards

[wieman01]

hello,

it seems to be a very nice tutorial... but it doesn't help yet...

My house mate just broke our fine old router and purchased a new one. Everything was fine with the old one using wpa_supplicant, but I can't connect to the new one. I followed many of the tips in this How to but nothing worked...

But I just figured out that my wireless card is a 802.11b and the router is (via iwlist scan) a 802.11g, would that be the problem? Is it possible to change the 802.11g into a 802.11b in the configuration of the router? I seriously doubt about it...thanks to my housemate.... :(

regards
Well, if it worked before, then apparently a different router setting is keeping from connecting.

I suspect it's exactly because it is a wireless-G device. Your housemate needs to enabled something called "mixed mode" which enables the router to cope with wireless-B and wirelss-G devices/clients. Could you have a chat with your mate?

[izle]

it's amazing, thanks for replying so quickly!

well I just informed him about that we'll see what we can do. But the router is called "Belkin wireless G router", my concern is : is there any mixed mode for this router?.... if so the problem will resolved quickly with the tutorial, if not I guess I'll have to...., say, bury my house mate six feet under....

[wieman01]

it's amazing, thanks for replying so quickly!

well I just informed him about that we'll see what we can do. But the router is called "Belkin wireless G router", my concern is : is there any mixed mode for this router?.... if so the problem will resolved quickly with the tutorial, if not I guess I'll have to...., say, bury my house mate six feet under....
There is no such thing as 100% certainty, but I give you my word that all wireless-G routers I have seen so far had that option. It is fairly standard I would say. That's called downwards compatibility.

[DChamp]

Wieman, there's an INCREDIBLE amount of information here, especially for a COMPLETE NOOB like me.

With so much point/counterpoint here, is there a concise, step by step on how to get a Netgear W111v2 usb to work using WEP with Gutsy 7.1?

Thanks a million, as so much of this is completely foreign to me.

Dave C.
DChamp

[wieman01]

Wieman, there's an INCREDIBLE amount of information here, especially for a COMPLETE NOOB like me.

With so much point/counterpoint here, is there a concise, step by step on how to get a Netgear W111v2 usb to work using WEP with Gutsy 7.1?

Thanks a million, as so much of this is completely foreign to me.

Dave C.
DChamp
This is a WPA tutorial so I cannot offer much help. Please open a new thread and feel free to send me the link to it via PM. Please also state what chipset this particular adapter is using.

[DChamp]

Thanks. I found another forum message related to the NetGear WG111v2, and will look there first.

Believe me, being a noob to Ubuntu/Linux really stinks! *laughing*
I'm trying to get this working for a presentation tonight, but might have to go cabled as I don't think I can process everything in time.

Thanks again,
Dave/DChamp

[izle]

There is no such thing as 100% certainty, but I give you my word that all wireless-G routers I have seen so far had that option. It is fairly standard I would say. That's called downwards compatibility.

houra!!! the new router owns a "mixed mode" enabling me to connect to it. For the record here is what iwlist scan gives me




izle@izle-laptop:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:1C:DF:40:CC:09
ESSID:"Tuna"
Protocol:IEEE 802.11bg
Mode:Master
Channel:9
Frequency:2.452 GHz (Channel 9)
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 9 Mb/s; 11 Mb/s
6 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=90/100 Signal level=-32 dBm Noise level=-47 dBm
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Preauthentication Supported
Extra: Last beacon: 96ms ago


here is my /etc/network/interfaces file



auto lo
iface lo inet loopback

auto eth2
#iface eth2 inet dhcp

auto ath0
#iface ath0 inet dhcp

auto wlan0
#iface wlan0 inet dhcp

iface eth1 inet dhcp
wpa-ssid Tuna
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk my_psk

auto eth1


so far I used wpa_supplicant, but I could not get it to work with WPA2... here it seems even better... at least I save a couple of milliseconds at startup! and it works fine.

Thank you Wieman01 for this great tutorial! :)

[Terratoch]

Sorry in advance 130+ pages of posts is too much for me to read through.
I THINK I have the right settings, but obviously I do not or else I wouldn't be posting asking for help.



auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid ************
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-eap PEAP
wpa-key-mgmt IEEE8021X
wpa-identity ********
wpa-password ********
wpa-phase2 auth=MSCHAPV2

Route:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.18.0.0 * 255.255.0.0 U 0 0 0 eth0
link-local * 255.255.0.0 U 0 0 0 wlan0
default 10.18.1.1 0.0.0.0 UG 0 0 0 eth0
default * 0.0.0.0 U 1000 0 0 wlan0

IWConfig:
wlan0 IEEE 802.11g ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Retry min limit:7 RTS thr: off Fragment thr=2346 B
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

iwlist scan:
wlan0 Scan completed :
Cell 01 - Address: 00:14:A8:36:7A:E0
ESSID:""
Mode:Master
Channel:1
Frequency:2.412 GHz
Quality=14/64 Signal level=39/65
Encryption key: off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=0000257ff117f89a
Cell 02 - Address: 00:14:A8:36:8C:10
ESSID:""
Mode:Master
Channel:6
Frequency:2.437 GHz
Quality=23/64 Signal level=11/65
Encryption key: off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=0000257ffc33fbb7
Cell 03 - Address: 00:14:A8:7D: D7:90
ESSID:""
Mode:Master
Channel:6
Frequency:2.437 GHz
Quality=21/64 Signal level=20/65
Encryption key: off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=00001113bfb67735
Cell 04 - Address: 00:14:A8:43:FF:60
ESSID:""
Mode:Master
Channel:6
Frequency:2.437 GHz
Quality=0/64 Signal level=9/65
Encryption key: off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=00001113bb7a3bcb
Cell 05 - Address: 00:14:A8:36:89:C0
ESSID:""
Mode:Master
Channel:11
Frequency:2.462 GHz
Quality=26/64 Signal level=9/65
Encryption key: off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=0000257ff9f8e109
Cell 06 - Address: 00:14:6A:3D: D3:80
ESSID:""
Mode:Master
Channel:6
Frequency:2.437 GHz
Quality=27/64 Signal level=15/65
Encryption key: off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=00001113bfc06e56
Cell 07 - Address: 00:1C:10:E7:27:04
ESSID:"CRESTRON-N"
Mode:Master
Channel:6
Frequency:2.437 GHz
Quality=50/64 Signal level=9/65
Encryption key: on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=000001bd1a1ccaed

lshw -C network:
*-network
description: Wireless interface
physical id: 1
logical name: wlan0
serial: 00:15:af:0f:0a:ef
capabilities: ethernet physical wireless
configuration: broadcast=yes multicast=yes wireless=IEEE 802.11g

ifdown -v
ifdown: interface /etc/network/interfaces not configured

ifup -v:
Ignoring unknown interface /etc/network/interfaces=/etc/network/interfaces.


Spoiler alert: I am a massive noob with Ubuntu Linux.
I am running 7.10 with an ASUS M2N32-SLI DELUXE Motherboard (if that helps).

Any and all help would truely be appreciated. Thanks.

If it helps at all to know, whenever I do the restart command, I get:


* Reconfiguring network interfaces... There is already a pid file /var/run/dhclient.wlan0.pid with pid 11347
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:15:af:0f:0a:ef
Sending on LPF/wlan0/00:15:af:0f:0a:ef
Sending on Socket/fallback
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - There is already a pid file /var/run/dhclient.wlan0.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:15:af:0f:0a:ef
Sending on LPF/wlan0/00:15:af:0f:0a:ef
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

[wieman01]

Terratoch,

What chipset is your card?

Also post:

sudo lshw -C network

[Terratoch]

nVidia nForce 590 SLI something or other
Motherboard M2N32-SLI Deluxe
I believe I know what the problem is, and perhaps how to fix it.
I was using RTL8187 for the on-board wireless card, which I know does not work, but also had no idea how to replace it. I may now know how to fix this problem.

Okay. I lied. I have no clue what to use instead of RTL8187. Can someone point me in the right direction.

[Terratoch]

Problem partially solved I have a new driver that works. I am going to try again with luck I may be setup.

[Terratoch]

Okay I am now positive I have the correct drivers. It is still not working. I have tried countless configuration settings.
Please help.

[Terratoch]

Details:
I get the very vexing DHCP error where it sits in a loop for about 2 minutes, tells me it didnt receive a dhcp, and then quits.



sudo route:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.10.0.0 * 255.255.0.0 U 0 0 0 eth0
default 10.10.1.1 0.0.0.0 UG 0 0 0 eth0




sudo iwconfig:
lo no wireless extensions.

eth0 no wireless extensions.

eth1 no wireless extensions.

wlan0 IEEE 802.11g ESSID:off/any
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Bit Rate:54 Mb/s Tx-Power:20 dBm Sensitivity=0/3
RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0



sudo iwlist scan:
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Interface doesn't support scanning.

wlan0 No scan results
result not typical.



sudo lshw -C network:
*-network DISABLED
description: Wireless interface
physical id: 1
logical name: wlan0
serial: 00:15:af:0f:0a:ef
capabilities: ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+netrtuw driverversion=1.45+Realtek Semiconductor Corp. link=no multicast=yes wireless=IEEE 802.11g

I see the big DISABLED, and have no clue how to correct that.



sudo cat /etc/network/interfaces:
auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid ************************************************** *****
wpa-proto WPA
wpa-ap-scan 2
wpa-pairwise TKIP
wpa-group TKIP
wpa-eap PEAP
wpa-key-mgmt WPA-EAP
wpa-identity ************************************************** **
wpa-password *************************************************



sudo ifdown -v wlan0 (in my case):
ifdown: interface wlan0 not configured
again. I know what it means (kind of), but have no clue how to fix it.




sudo ifup -v wlan0 (in my case):
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan0
wpa_supplicant: wpa-ap-scan 2 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "*********************************" -- OK
wpa_supplicant: wpa-pairwise TKIP -- OK
wpa_supplicant: wpa-group TKIP -- OK
wpa_supplicant: wpa-key-mgmt WPA-EAP -- OK
wpa_supplicant: wpa-proto WPA -- OK
wpa_supplicant: wpa-identity "******************************" -- OK
wpa_supplicant: wpa-eap PEAP -- OK
wpa_supplicant: wpa-password "***************************" -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:15:af:0f:0a:ef
Sending on LPF/wlan0/00:15:af:0f:0a:ef
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 2
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant

That is all pretty much greek to me. but now im betting if i did ifdown -v wlan0...



yep
post ifup ifdown -v wlan0:
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 6329
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:15:af:0f:0a:ef
Sending on LPF/wlan0/00:15:af:0f:0a:ef
Sending on Socket/fallback
ifconfig wlan0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan0.pid
Stopped /sbin/wpa_supplicant (pid 6296).
still dunno what it means though


I hope this helps you... help me. if not tell me what else I need to provide to help you help me resolve this.
Thanks.

[wieman01]

sudo lshw -C network:
*-network DISABLED
This plus no scan results = bad news. So where did you get the driver from eventually? Are you on a 64-bit Ubuntu installation by chance?

What again is the chipset of your wireless adapter?

And does the Windows driver that you are using support PEAP?

[Terratoch]

Chipset: RTL8187
I have several options available as to what windows driver to use.
They all came on the CD for my Motherboard
Which version would you recommend (98/ME/XP/Vista?)
Or something totally different.

[wieman01]

I recommend the XP version, 32-bit if you are running Ubuntu 32-bit.

Also, is your adapter listed anywhere here?

http://ndiswrapper.sourceforge.net/joomla/index.php?/component/option,com_openwiki/Itemid,33/id,list/

[Terratoch]

Unfortunately the adapter doesn't really have a 'name', as it is built into the motherboard. but I can check the list and see.

But, the board is the M2N32 SLI Deluxe Wifi edition.

[Terratoch]

It looks like I could try the 8187B, L or one of the others from the site. that may do the trick. Ill just have to get it to my computer.

[wieman01]

OK, let me know how you go.

[Terratoch]

Great Success. :D
For those who are using the M2N32 SLI Deluxe WiFi Editition or the RTL8187 native drivers:
follow this link (ftp://61.56.86.122/cn/wlan/WinXP_2K_1304_1119.zip), download the file

use ndiswrapper:
sudo ndiswrapper -i
on the .inf file found inside
and at least for my wireless network settings, it works just fine, without tinkering in the /etc/network/interface file (i completely removed all of the stuff from that file except for the
auto lo
iface lo inet loopback
lines.)
For the record, presently my network is a:
WPA(1)
PEAP
TKIP
MSCHAPV2

Thanks for the assistance.
PS: Don't forget to blacklist the native RTL8187 driver. This could cause no end of headache if you do.

EDIT: A minor inconvenience, I have to modprobe ndiswrapper at startup. But its only minor, I made a script to take care of it for me.
Is there anyway around that? (Besides what I did).

[wieman01]

Well done, Terratoch!

Try this to load "ndiswrapper" at boot:

sudo depmod -a
sudo modprobe ndiswrapper

echo 'ndiswrapper' | sudo tee -a /etc/modules

[derekge]

Very nice - I was looking for a WEP guide too. :confused:

[wieman01]

Very nice - I was looking for a WEP guide too. :confused:
Don't user WEP, it's insecure. But if you really have to, check this out:

http://ubuntuforums.org/showthread.php?t=684495

[anthony.canucks]

I am using a d link DWL-G510 rev. A and I can't figure out what is wrong.


# route

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
link-local * 255.255.0.0 U 0 0 0 wlan0
default * 0.0.0.0 U 1000 0 0 wlan0


# iwconfig

lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11b ESSID:off/any
Mode:Managed Channel:0 Access Point: Not-Associated
Bit Rate:54 Mb/s Sensitivity=-200 dBm
RTS thr=2346 B Fragment thr=2346 B
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


# sudo iwlist scan

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Failed to read scan data : Resource temporarily unavailable


But if I run sudo /etc/init.d/networking stop


lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:03:7F:FE:00:02
ESSID:"anthony"
Protocol:IEEE 802.11b
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:68/100 Signal level:-52 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK


# sudo lshw -C network

*-network
description: Wireless interface
product: Marvell W8300 802.11 Adapter
vendor: Marvell Technology Group Ltd.
physical id: 6
bus info: pci@0000:03:06.0
logical name: wlan0
version: 07
serial: 00:0f:3d:4e:2f:a6
width: 32 bits
clock: 66MHz
capabilities: pm bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+mrv8k51 driverversion=1.52+D-Link,1/09/2004,2.3.0.1 latency=64 link=no module=ndiswrapper multicast=yes wireless=IEEE 802.11b


# sudo cat /etc/network/interfaces

auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid anthony
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk f30669bdd0818043258e4e74da71397c430402d66378394d21 66159801b6cf12


# sudo ifdown -v <your_interface>

Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 16161
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:0f:3d:4e:2f:a6
Sending on LPF/wlan0/00:0f:3d:4e:2f:a6
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 192.168.1.1 port 67
ifconfig wlan0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan0.pid
Stopped /sbin/wpa_supplicant (pid 16130).

# sudo ifup -v <your_interface>

ioctl[SIOCSIWPMKSA]: Invalid argument
There is already a pid file /var/run/dhclient.wlan0.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:0f:3d:4e:2f:a6
Sending on LPF/wlan0/00:0f:3d:4e:2f:a6
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

[wieman01]

Did you do?

sudo ifup -v wlan0
What could this relate to?

ioctl[SIOCSIWPMKSA]: Invalid argument

[anthony.canucks]

edit: it's working now. I didn't change any ubuntu settings (did change my router from aes to tkip though)

thanks anyway


sudo ifup -v wlan0

gives


ioctl[SIOCSIWPMKSA]: Invalid argument
There is already a pid file /var/run/dhclient.wlan0.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:0f:3d:4e:2f:a6
Sending on LPF/wlan0/00:0f:3d:4e:2f:a6
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

[taiwanjohn]

First of all, thanks a million for this great HOWTO, wieman01! :-)

I just wanted to post some notes from my installation, for anyone else who has a Zyxel G-210H (USB) wireless adapter.

When I first got the G-210H, I was still using Kubuntu Gutsy, and had all kinds of trouble... never did get it working reliably. Then, a week or so later, Ubuntu Hardy (8.04) came out, and everything "just worked"... including WPA and ESSID. (Note: Be sure to use ndiswrapper with the Win2k driver. The WinXP driver didn't work for me.)

Then, a couple of days ago, it "just stopped" working... Suddenly I wasn't getting a DHCP lease. I had no IPv4 address for wlan0, but I had a new "wlan0:avahi" showing up in ifconfig.

Googling for answers, I found several threads about how to disable avahi-daemon, none of which worked. (There seems to be no way to disable avahi without removing it, and that requires removing ubuntu-desktop too.)

I also tried wicd, and that ended up wasting a bunch of my time too... because it "seemed" like it ought to work, but didn't.

Anyway, I'm glad I finally found this HOWTO... ;-)

Cheers,

--jrd

PS: Here's my /etc/network/interfaces, for reference:


auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid ########
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk ########

[Terratoch]

Thanks for the tip it worked like a charm. Would you know how to set it up so that it automatically logs me into the wireless network without my having to go through the annoyance of doing it manually every time i reset my computer?

[wieman01]

Thanks for the tip it worked like a charm. Would you know how to set it up so that it automatically logs me into the wireless network without my having to go through the annoyance of doing it manually every time i reset my computer?
You mean you need to start the network manuallly? If that is the case, please take a look at post #2 of this thread. If not, let me know.

[Terratoch]

No, the network program is running as expected when I log in. However, I always have to left-click the icon, go to 'Connect to other wireless networks', put in the SSID, and setup the configuration options (PEAP, TKIP, MSCHAPV2, User ID and password). Its not THAT big of a deal, but it is annoying enough to make me ask if there is a better way. I saw all the config files and wondered if there wasn't a file I could make it read from or something, anything, that I could do so that I don't have to do that anymore.

[wieman01]

No, the network program is running as expected when I log in. However, I always have to left-click the icon, go to 'Connect to other wireless networks', put in the SSID, and setup the configuration options (PEAP, TKIP, MSCHAPV2, User ID and password). Its not THAT big of a deal, but it is annoying enough to make me ask if there is a better way. I saw all the config files and wondered if there wasn't a file I could make it read from or something, anything, that I could do so that I don't have to do that anymore.
If you use NM, then scripts aren't an option. I know what you mean, NM can be quite a pain in the throat. Perhaps an update will fix it in future? Have you tried Hardy?

[Terratoch]

Damn. Alright, thanks anyway.



Have you tried hardy?


No. I tried Suse (10.3) for about... 3 days. Then I switched back to Ubuntu (7.10). I am not really keen on the idea of trying another OS this soon. Plus... I am presently out of CD-Rs.

[wieman01]

Damn. Alright, thanks anyway.

No. I tried Suse (10.3) for about... 3 days. Then I switched back to Ubuntu (7.10). I am not really keen on the idea of trying another OS this soon. Plus... I am presently out of CD-Rs.
A distribution upgrade will do. I did it last week (from Gutsy to Hardy) and it went OK.

[lucia_engel]

This guide is godsend!

I just purchased a Linksys wpc54g v4 card to replace my old laptop integrated network adapter. When I tried to configure it to use WEP, didn't work, so I thought maybe I'll try WPA instead. Following this guide, it JUST WORKED!

Now looking back at my Windows XP partition, for some reason, the new card only works with WEP but not WPA. You know Windows sucks when the official driver doesn't work but the linux driver can.

You're lifesaver!

[ramon13579]

Sorry for the looong post. This is probably my last try before my laptop flies off the window... In short: I can establish a WEP connection but cannot do the same with a WAP EAP-TTLS. I have read the first few posts of this thread and have also browsed through the thread, so I am sorry if the solution to my problem has already been explained.

The instructions I have been given to setup the wifi connection are:

1. Create the file /etc/wpa_supplicant.conf:

ctrl_interface=/var/run/wpa_supplicant
eapol_version=1
ap_scan=1
fast_reauth=0
network={
ssid="uib1x"
key_mgmt=WPA-EAP
proto=WPA
pairwise=TKIP
group=TKIP
eap=TTLS
identity="**********"
password="***********"
phase2="auth=PAP"
ca_cert="/etc/cert/ct_root.pem"
subject_match="sint.uib.es"
}

The ct_root.pem file supplied to me is in /etc/cert of course.

2. iwconfig wlan0 essid uib1x
No output

3. wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant.conf -D wext
This command fails. Output:

ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 -

I am absolutely lost here. Could this be a problem with kernel modules? I have tried to install the mac80211 subsystem and iwlwifi drivers from http://intellinuxwireless.org/?n=Downloads, but could not even recompile the kernel. Nevertheless, I do not even know whether I have the right drivers or not:

# lsmod |grep mac80211
iwlwifi_mac80211 200456 1 iwl4965
cfg80211 8720 1 iwlwifi_mac80211

Some more information (I need to restart the computer because after running wpa_supplicant the route command does not show wlan0):

#route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.138.0 * 255.255.255.0 U 0 0 0 eth0
link-local * 255.255.0.0 U 0 0 0 wlan0
link-local * 255.255.0.0 U 1000 0 0 eth0
default 192.168.138.1 0.0.0.0 UG 0 0 0 eth0
default * 0.0.0.0 U 1000 0 0 wlan0

# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Encryption key:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

# iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wmaster0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:19:07:05:7E:C0
ESSID:"uib1x"
Mode:Master
Channel:1
Frequency:2.412 GHz (Channel 1)
Quality=31/100 Signal level=-90 dBm Noise level=-127 dBm
Encryption key:on
IE: WPA Version 1
Group Cipher : WEP-40
Pairwise Ciphers (1) : WEP-40
Authentication Suites (1) : 802.1x
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=00000058764a0b9e
...
(Cell 02 to Cell 05 omitted -- uib1x is the target network)

# lshw -C network
*-network
description: Wireless interface
product: PRO/Wireless 4965 AG or AGN Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:01:00.0
logical name: wmaster0
version: 61
serial: 00:13:e8:a1:2f:45
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=iwl4965 latency=0 module=iwl4965 multicast=yes wireless=IEEE 802.11g
...
(Ethernet interface omitted)

# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dhcp

# ifdown -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 5957
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:13:e8:a1:2f:45
Sending on LPF/wlan0/00:13:e8:a1:2f:45
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 1.1.1.1 port 67
ifconfig wlan0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant

# ifup -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant

dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 1
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:13:e8:a1:2f:45
Sending on LPF/wlan0/00:13:e8:a1:2f:45
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant

All this looks fine to my unexperienced eyes. Some ideas?

Cheers.

[gedden]

My problem is just like all the others in this thread. I appreciate any help as I have been learning quite a lot about Linux and I haven't had this much fun configuring a computer in a long time! thank you Ubuntu forums!

so for the background
Compaq armadaM300 old laptop. Cisco aironet 350 pc card. 7.10 version.
Card was working fine with linksys wrt54g router in mac filtering mode, until I learned a little bit more about wireless security. Switched to WPA personal pre shared key. Had to switch network manager to manual mode to get an option for wpa personal. Sometimes key disappears from NM. To finally get a connection I had to check, and uncheck the box upwards of 15 times. Eventually I would get a connection and browse away. After a while I wanted to get samba working the way it was before I implemented encryption. During my investigation of why it wasn't working two forum members helped me figure out that I wasn't connecting to my router after all! Thats when I started trying to figure out etc/network/interfaces. Initially I had a lot of garbage in that file, I might have made a back up I can post if needed. I was reading the online docs for NM and it stated to remove anything that you want controlled by NM from interfaces. So I did that, and it didn't do anything to change the problem. So then I started following the Howto from this thread. Below I will post all outputs I can think of.

iwconfig


lo no wireless extensions.

eth0 no wireless extensions.

eth1 IEEE 802.11-DS ESSID:"linksys"
Mode:Managed Frequency:2.437 GHz Access Point: 00:1C:10:14:F0:C3
Bit Rate:11 Mb/s Tx-Power=20 dBm Sensitivity=0/65535
Retry limit:16 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=55/100 Signal level=-68 dBm Noise level=-91 dBm
Rx invalid nwid:462 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:7 Invalid misc:251775 Missed beacon:0

wifi0 IEEE 802.11-DS ESSID:"linksys"
Mode:Managed Frequency:2.437 GHz Access Point: 00:1C:10:14:F0:C3
Bit Rate:11 Mb/s Tx-Power=20 dBm Sensitivity=0/65535
Retry limit:16 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=55/100 Signal level=-68 dBm Noise level=-91 dBm
Rx invalid nwid:462 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:7 Invalid misc:251775 Missed beacon:0

gedden@gedden-laptop:~$ iwlist scan


lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:1B:5B:DB:1F:E9
ESSID:"2WIRE491"
Mode:Master
Frequency:2.412 GHz (Channel 1)
Quality=54/100 Signal level=-69 dBm Noise level:-92 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Extra:bcn_int=100
Cell 02 - Address: 00:18:39:7E:4B:17
ESSID:"apartment"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=90/100 Signal level=-50 dBm Noise level:-92 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s
Extra:bcn_int=100
Cell 03 - Address: 00:1C:10:14:F0:C3
ESSID:"linksys"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=50/100 Signal level=-70 dBm Noise level:-92 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s
Extra:bcn_int=100

wifi0 Scan completed :
Cell 01 - Address: 00:1B:5B:DB:1F:E9
ESSID:"2WIRE491"
Mode:Master
Frequency:2.412 GHz (Channel 1)
Quality=54/100 Signal level=-69 dBm Noise level:-92 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Extra:bcn_int=100
Cell 02 - Address: 00:18:39:7E:4B:17
ESSID:"apartment"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=90/100 Signal level=-50 dBm Noise level:-92 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s
Extra:bcn_int=100
Cell 03 - Address: 00:1C:10:14:F0:C3
ESSID:"linksys"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=50/100 Signal level=-70 dBm Noise level:-92 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s
Extra:bcn_int=100


This is the first time that wifi0 has responded to a scan request. Although I have had a duplicate in my NM for a while.

route

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth1
link-local * 255.255.0.0 U 1000 0 0 eth1
default 192.168.1.1 0.0.0.0 UG 100 0 0 eth1


So following the How to I produced this interfaces file:


auto lo
iface lo inet loopback

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-ssid apartment
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk 3732d419f65fcxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxx

And this produced the error


gedden@gedden-laptop:~$ sudo /etc/init.d/networking restart
[sudo] password for gedden:
* Reconfiguring network interfaces... /etc/network/interfaces:76: duplicate interface
ifdown: couldn't read interfaces file "/etc/network/interfaces"
/etc/network/interfaces:76: duplicate interface
ifup: couldn't read interfaces file "/etc/network/interfaces"
[fail]


So Ill post the output of if up/down

gedden@gedden-laptop:~$ ifdown -v eth1
ifdown: failed to open statefile /var/run/network/ifstate: Permission denied
gedden@gedden-laptop:~$ sudo ifdown -v eth1
Configuring interface eth1=eth1 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.eth1.pid -lf /var/lib/dhcp3/dhclient.eth1.leases eth1
There is already a pid file /var/run/dhclient.eth1.pid with pid 14393
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/eth1/00:40:96:46:1d:9f
Sending on LPF/eth1/00:40:96:46:1d:9f
Sending on Socket/fallback
DHCPRELEASE on eth1 to 192.168.1.1 port 67
ifconfig eth1 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.eth1.pid
Stopped /sbin/wpa_supplicant (pid 14364).
gedden@gedden-laptop:~$ sudo ifup -v eth1
Configuring interface eth1=eth1 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.eth1.pid -i eth1 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 7 value 0x1 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/eth1
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "apartment" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto WPA -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.eth1.pid -lf /var/lib/dhcp3/dhclient.eth1.leases eth1
There is already a pid file /var/run/dhclient.eth1.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/eth1/00:40:96:46:1d:9f
Sending on LPF/eth1/00:40:96:46:1d:9f
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 4
DHCPOFFER from 192.168.1.1
DHCPREQUEST on eth1 to 255.255.255.255 port 67
DHCPACK from 192.168.1.1
bound to 192.168.1.111 -- renewal in 39668 seconds.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntp
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant


I know this is a long post but just a little more.
So I edited out all the stuff I added from interfaces and restarted the network.

gedden@gedden-laptop:~$ sudo /etc/init.d/networking restart
* Reconfiguring network interfaces... RTNETLINK answers: No such process
There is already a pid file /var/run/dhclient.eth1.pid with pid 10613
removed stale PID file
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/eth1/00:40:96:46:1d:9f
Sending on LPF/eth1/00:40:96:46:1d:9f
Sending on Socket/fallback
DHCPRELEASE on eth1 to 192.168.1.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 7 value 0x1 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - There is already a pid file /var/run/dhclient.eth1.pid with pid 134519120
Internet Systems Consortium DHCP Client V3.0.5
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/eth1/00:40:96:46:1d:9f
Sending on LPF/eth1/00:40:96:46:1d:9f
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 20
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
[ OK ]



So, Thats everything I can think of right now. Thanks in advance for any help!.

Andy

[ramon13579]

The problem I posted two days ago (Apr 23 2008) is SOLVED after an upgrade from Gutsy to Hardy.

Cheers,

Ramon

[wieman01]

gedden,

It appears you are using the wrong wpa-driver. What wireless adapter have you got?

Please post the output of:

sudo lshw -C network
Have you removed NM entirely?

[lucky760]

[accidental double post - please disregard and see the next comment]

[lucky760]

You're pretty incredible to offer so much assistance to everyone and for so long, so let me start by saying thanks very much.

Installed 8.04 Desktop on a Vaio laptop with Intel 2200BG interface on eth1. Interface works on some neighbor's insecure network. My router is setup with WPA2, WPA-PSK, AES, SSID broadcast.

The most strange thing to me is that in `iwlist scan` and `iwconfig` my router's reported MAC address is incorrect. The last byte is reported as A9 but is in fact AA.

route


Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
link-local * 255.255.0.0 U 0 0 0 eth1
default * 0.0.0.0 U 1000 0 0 eth1


iwconfig


lo no wireless extensions.

eth0 no wireless extensions.

eth1 unassociated ESSID:"Kikkoman"
Mode:Managed Frequency=2.412 GHz Access Point: 00:19:5B:60:34:A9
Bit Rate:0 kb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:21 Missed beacon:0


sudo iwlist scan


eth1 Scan completed :
...snip...
Cell 02 - Address: 00:19:5B:60:34:A9
ESSID:"Kikkoman"
Protocol:IEEE 802.11g
Mode:Master
Frequency:2.412 GHz (Channel 1)
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=44/100 Signal level=-38 dBm
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
Extra: Last beacon: 212ms ago
...snip...


sudo lshw -C network


SCSI
*-network:0
description: Wireless interface
product: PRO/Wireless 2200BG Network Connection
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:02:02.0
logical name: eth1
version: 05
serial: 00:0e:35:36:b8:a7
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ipw2200 driverversion=1.2.2kmprq firmware=ABG:9.0.2.6 (Mar 22 2005) latency=64 link=no maxlatency=24 mingnt=3 module=ipw2200 multicast=yes wireless=unassociated
*-network:1
description: Ethernet interface
product: 82801DB PRO/100 VE (MOB) Ethernet Controller
vendor: Intel Corporation
physical id: 8
bus info: pci@0000:02:08.0
logical name: eth0
version: 83
serial: 08:00:46:da:a7:12
size: 10MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e100 driverversion=3.5.23-k4-NAPI duplex=half firmware=N/A latency=64 link=no maxlatency=56 mingnt=8 module=e100 multicast=yes port=MII speed=10MB/s


sudo cat /etc/network/interfaces


auto lo
iface lo inet loopback

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-ssid Kikkoman
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk <secret_hash>


sudo ifdown -v eth1


Configuring interface eth1=eth1 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.eth1.pid -lf /var/lib/dhcp3/dhclient.eth1.leases eth1
There is already a pid file /var/run/dhclient.eth1.pid with pid 7115
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:0e:35:36:b8:a7
Sending on LPF/eth1/00:0e:35:36:b8:a7
Sending on Socket/fallback
DHCPRELEASE on eth1 to 192.168.2.1 port 67
ifconfig eth1 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.eth1.pid
Stopped /sbin/wpa_supplicant (pid 7042).


sudo ifup -v eth1


Configuring interface eth1=eth1 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.eth1.pid -i eth1 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/eth1
wpa_supplicant: wpa-ap-scan 1 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "Kikkoman" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise CCMP -- OK
wpa_supplicant: wpa-group CCMP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto RSN -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.eth1.pid -lf /var/lib/dhcp3/dhclient.eth1.leases eth1
There is already a pid file /var/run/dhclient.eth1.pid with pid 134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:0e:35:36:b8:a7
Sending on LPF/eth1/00:0e:35:36:b8:a7
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 12
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant


Any tips you can provide would be greatly appreciated. Thanks very much.

[wieman01]

lucky760:

You're most welcome of course.

First of all, your ipw2200bg should be working out of the box, I own a Sony Vaio laptop as well and never had an issue with this wireless device. Strange.

Do you prefer to use command line or do you want plan to use Network Manager or WICD? Graphical tools are much more convenient, in particular for laptop users. If you don't need a static IP address, I recommend that you use either of these tools.

To do so, make your "/etc/network/interfaces" look like this (this is an exact copy of mine):

auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0

auto eth0

auto eth1
Then restart the PC and see if you can connect via Network Manager. If NM fails on you, give WICD a go:

http://wicd.sourceforge.net/

If all this fails, please let me know, I'll think of something else. The ipw2200bg should be a breeze.

[lucky760]

Funny how that is as equally encouraging as it is discouraging because it is supposed to be so *straightforward*, and it is *supposed* to be so straightforward.

I prefer the command line, but gui's fine if it'll work. Unfortunately, so far it won't.

I am using DHCP, so static addresses are not needed.

I reset my /etc/network/interfaces to the contents you pasted, tried the Network Manager (again) and it failed, then installed Wicd and got it running, but it failed to connect, all the while iwevent continues reporting the same 4 messages repeatedly:


Set Mode:Managed
Set Frequency:2.432 GHz (Channel 5)
Set ESSID:"Kikkoman"
New Access Point/Cell address:Not-Associated

When that didn't work, I booted into LiveCD for a pseudo fresh install then repeated the above and got the same results. : \

I have no idea what the problem could be, but then again I guess I wouldn't. Is there something else I can try? Thanks very much.

[wieman01]

Have you perhaps enabled MAC filtering by mistake?

[lucky760]

Have you perhaps enabled MAC filtering by mistake?

No, sure haven't. MAC filtering is definitely off, and the MAC is definitely in the DHCP reservations list. Furthermore, this is a dual boot and connecting in XP with the same device works fine.

Hope for me is looking more and more dim, isn't it? :( Sounds like I have a strange problem no one else has ever experienced or fixed before.

[wieman01]

But you could connect to your network while it was unsecured?

[lucky760]

But you could connect to your network while it was unsecured?

Actually, it is a neighbor's insecure network, but yes, it did quickly and easily connect to the neighbor's open network when it couldn't connect to my secure one.

[gedden]

gedden,

It appears you are using the wrong wpa-driver. What wireless adapter have you got?

Please post the output of:

Have you removed NM entirely?

As far as I know when I installed wicd it uninstalled NM, however I still have a network applet that can set my dns and such.


under system,administration,network.
the applett is named network settings.

here is the output

gedden@gedden-laptop:~$ sudo lshw -C network
[sudo] password for gedden:
*-network
description: Cisco Systems
physical id: 0
version: 350 Series Wireless LAN Adapter
slot: Socket 0
resources: irq:3
*-network
description: Ethernet interface
product: 82557/8/9 Ethernet Pro 100
vendor: Intel Corporation
physical id: 9
bus info: pci@0000:00:09.0
logical name: eth0
version: 09
serial: 00:d0:59:91:c3:ff
size: 100MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e100 driverversion=3.5.17-k4-NAPI duplex=half firmware=N/A ip=192.168.1.102 latency=66 link=yes maxlatency=56 mingnt=8 module=e100 multicast=yes port=MII speed=100MB/s
*-network
description: Wireless interface
physical id: 1
logical name: eth1
serial: 00:40:96:46:1d:9f
capabilities: ethernet physical wireless
configuration: broadcast=yes multicast=yes wireless=IEEE 802.11-DS


after a bit of looking I might be out of luck with wpa on my cisco.

[wieman01]

Actually, it is a neighbor's insecure network, but yes, it did quickly and easily connect to the neighbor's open network when it couldn't connect to my secure one.
Beats me... I don't know what's going on. Can you find a bug report on Launchpad by chance?

[LauraSakura]

your problem is with IPW2200? Mine seemed to stop working once i upgraded to hardy :(

[wieman01]

your problem is with IPW2200? Mine seemed to stop working once i upgraded to hardy :(
Really? Please post:

sudo iwlist scan

sudo lshw -C network

sudo cat /etc/network/interfaces

[Average Joe]

I thought I found my nirvana by installing Wicd (http://ubuntuforums.org/showpost.php?p=4416845&postcount=1242), but I was wrong. I got some issues with Wicd too, so (after upgrading to Hardy Heron) I went back to the network-manager and this nice how-to.

Everything works fine. I have a static IP address, and use WPA2. The network-restart bug is still there, but instead of starting another script in /etc/rcS.d/ as explained in the second post of this topic, I simply put the line:

/etc/init.d/networking restart
in my /etc/rc.local. I find that easier and it seems to do the trick as well. Or is there a good reason not to do it like this?

P.S. Wieman01, your last edit in the first post says: "15/04/2008: Tested with Gutsy Gibbon (Wieman01)." Shouldn't that be Hardy Heron instead?

[wieman01]

@Average Joe:

Thanks for your note. In fact your solution in regard to restarting the network is much neater. My post is kind of old, you know. Although it makes little difference.

Also changed the change log... it was indeed a mistake. :-)

[geezerone]

Hi

Took a quick look and looks helpful but does anyone know how to get a BT voyager 1055 USB adapter working in ubuntu (8.04 or 7.10) as the wireless adapter doesn't show up when performing lspci or iwlist?

Thanks :)

[K-Man_22]

Dear wieman01, dear readers,

please let me show you my report for a friend's laptop that had so far cost me hours and has still no wlan with linux. Since I am trying to convince this friend to switch over from windows, WLAN is a *must*. Although I have read and searched *a lot* (but not 136 pages in this thread ;-) and I feel that I am vey close, I don't know what to do next without screwing it up more. Maybe one of you finds what I am missing. I am using your report structure, wieman01.

My Requirements:
IBM Thinkpad T23, clean offline Ubuntu 8.04 WUBI installation into a single Win2000 FAT32 partition, D-Link DWL-G650+ (rev. B1)
As to the wlan-card: I don't even know which chipset it has (ACX100, ACX111, TI1130?) or what transfer speed standard (22/44, 54 Mbps?). I have tried several drivers via ndiswrapper, one from Texas Instruments seems to work. EDIT: After probing the system with the suggested commands, I do know: ACX111 from TI, 54Mbps.

# ndiswrapper -l
tnet1130 : driver installed
device (104C:9066) present (alternate driver: acx)

Settings from "MYAP" my accesspoint:
1. WPA
2. ESSID broadcast
3. DHCP
4. Pre-shared key

# route
Kernel-IP-Routentabelle
Ziel Router Genmask Flags Metric Ref Use Iface
link-local * 255.255.0.0 U 0 0 0 wlan0
default * 0.0.0.0 U 1000 0 0 wlan0


In about 3 out of 4 times I get this:
# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

irda0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:"MYAP"
Mode:Managed Frequency:2.437 GHz Access Point: XX:XX:XX:XX:XX
Bit Rate=54 Mb/s Tx-Power:10 dBm Sensitivity=0/3
RTS thr:off Fragment thr:off
Power Management:off
Link Quality:57/100 Signal level:-59 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

Else it gives me this:
# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

irda0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:off/any
Mode:Managed Frequency:2.437 GHz Access Point: Not-Associated
Bit Rate:54 Mb/s Tx-Power:10 dBm Sensitivity=0/3
RTS thr:off Fragment thr:off
Power Management:off
Link Quality:64/100 Signal level:-55 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


On the system monitor there appears a cyclic pattern of network activity corresponding to LED blinking of the card: One high spike followed by three half-sized, and a short pause of no activity.


# sudo iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

irda0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: XX:XX:XX:XX:XX:XX
ESSID:"MYAP"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:50/100 Signal level:-64 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 02 - Address: XX:XX:XX:XX:XX:XX
ESSID:"WLAN-XXXXXXXXXXXX"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:28/100 Signal level:-78 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 03 - Address: XX:XX:XX:XX:XX:XX
ESSID:"Targa-WLAN"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:51/100 Signal level:-63 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 04 - Address: XX:XX:XX:XX:XX:XX
ESSID:"benlan"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:7/100 Signal level:-91 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 05 - Address: XX:XX:XX:XX:XX:XX
ESSID:"WLAN9ED704"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:10/100 Signal level:-89 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 06 - Address: XX:XX:XX:XX:XX:XX
ESSID:"FRITZ!Box WLAN"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:45/100 Signal level:-67 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 07 - Address: XX:XX:XX:XX:XX:XX
ESSID:"Arcor-89B340"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.452 GHz (Channel 9)
Quality:32/100 Signal level:-75 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : TKIP CCMP
Authentication Suites (1) : PSK
Preauthentication Supported
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : TKIP CCMP
Authentication Suites (1) : PSK


# sudo lshw -C network
*-network
description: Ethernet interface
product: 82801CAM (ICH3) PRO/100 VE (LOM) Ethernet Controller
vendor: Intel Corporation
physical id: 8
bus info: pci@0000:02:08.0
logical name: eth0
version: 42
serial: xx:xx:xx:xx:xx:xx
size: 10MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e100 driverversion=3.5.23-k4-NAPI duplex=half firmware=N/A latency=66 link=no maxlatency=56 mingnt=8 module=e100 multicast=yes port=MII speed=10MB/s
*-network
description: Wireless interface
product: ACX 111 54Mbps Wireless Interface
vendor: Texas Instruments
physical id: 1
bus info: pci@0000:07:00.0
logical name: wlan0
version: 00
serial: xx:xx:xx:xx:xx:xx
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+tnet1130 driverversion=1.52+Texas Instruments,12/01/200 latency=64 link=yes module=ndiswrapper multicast=yes wireless=IEEE 802.11g


# sudo cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid MYAP
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk 134f6sj6y4vlse4o8zlse4lmcvoiew4u09qw8euosidjvlsmmy wj129iusap63fo7a3d


# sudo ifdown -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 12758
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/xx:xx:xx:xx:xx:xx
Sending on LPF/wlan0/xx:xx:xx:xx:xx:xx
Sending on Socket/fallback
ifconfig wlan0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan0.pid
Stopped /sbin/wpa_supplicant (pid 12721).


# sudo ifup -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan0
wpa_supplicant: wpa-ap-scan 1 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "MYAP" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise TKIP -- OK
wpa_supplicant: wpa-group TKIP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto WPA -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/xx:xx:xx:xx:xx:xx
Sending on LPF/wlan0/xx:xx:xx:xx:xx:xx
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant

- End of report -

What I find suspicious is "No working leases in persistent database - sleeping." But hey, I'm no expert here *at all*

Glad for any hints. I'll check back tomorrow. Thanks in advance.

K-Man

[AZzKikR]

Hi Wieman01,

Thanks for all the effort you put into all this.

I've installed Hardy Heron a week ago or so, and back with Gutsy everything worked smoothly with your tutorial, except with Hardy. I followed your all your instructions, but I still can't ping my gateway (router).

Any information you might want is posted here (formatted for your convenience):

$ route

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 wlan0
link-local * 255.255.0.0 U 1000 0 0 wlan0

$ iwconfig

lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:off/any
Mode:Auto Frequency:2.462 GHz Access Point: Not-Associated
Bit Rate:36 Mb/s Tx-Power:20 dBm Sensitivity=-114 dBm
RTS thr=2347 B Fragment thr=2346 B
Power Management:off
Link Quality:40/100 Signal level:-70 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


$ sudo iwlist scan

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:14:BF:93:D1:B3
ESSID:"porrus"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:35/100 Signal level:-73 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK

$ sudo lshw -C network

*-network
description: Wireless interface
product: RT2500 802.11g Cardbus/mini-PCI
vendor: RaLink
physical id: 7
bus info: pci@0000:05:07.0
logical name: wlan0
version: 01
serial: 00:12:17:8c:f1:54
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+rt2500 driverversion=1.52+Linksys,04/21/2005, 3.00.03 ip=192.168.1.7 latency=32 link=yes module=ndiswrapper multicast=yes wireless=IEEE 802.11g


$ sudo cat /etc/network/interfaces


auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet static
address 192.168.1.7
gateway 192.168.1.1
netmask 255.255.255.0
wpa-driver wext
wpa-ssid "porrus"
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk "a hex psk thingy"


Note: I've also tried to remove the quotes, to no avail.

$ sudo ifdown -v wlan0

Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/wpasupplicant
route del default gw 192.168.1.1 metric 100 wlan0
ifconfig wlan0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan0.pid
Stopped /sbin/wpa_supplicant (pid 8889).

$ sudo ifup -v wlan0

Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan0
wpa_supplicant: wpa-ap-scan 1 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "porrus" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise TKIP -- OK
wpa_supplicant: wpa-group TKIP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto WPA -- OK
wpa_supplicant: enabling network block 0 -- OK

ifconfig wlan0 192.168.1.7 netmask 255.255.255.0 up
route add default gw 192.168.1.1 metric 100 wlan0
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant


Any pointers? Thanks.

[iwanttobelieve]

Hi Wieman01,

I appreciate all the effort you've put into this thread. I tried following your instructions but I'm still unable to get my wireless card, Dlink DWA-542 to connect to my router. I'm using Ubuntu 8.04. If you could help me to figure out how to make this work I would very much appreciate it. Here's the information that you requested if I was stumped:

route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
link-local * 255.255.0.0 U 0 0 0 wlan0
default * 0.0.0.0 U 1000 0 0 wlan0



jacob@jacob-desktop:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:off/any
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Bit Rate:54 Mb/s
Power Management max timeout:0us mode:All packets received
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0



jacob@jacob-desktop:~$ sudo iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:1B:11:4A:3F:BF
ESSID:"Dominguez Wireless Network"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:46/100 Signal level:-66 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
Cell 02 - Address: 00:1A:70:DD:B9:2C
ESSID:"linksys"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:14/100 Signal level:-87 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0




jacob@jacob-desktop:~$ sudo lshw -C network
*-network:0
description: Wireless interface
product: AR5416 802.11abgn Wireless PCI Adapter
vendor: Atheros Communications Inc.
physical id: 0
bus info: pci@0000:03:00.0
logical name: wlan0
version: 01
serial: 00:17:9a:44:97:8e
width: 32 bits
clock: 66MHz
capabilities: bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+net5416 driverversion=1.52+,07/23/2007,6.0.3.107 latency=128 link=no module=ndiswrapper multicast=yes wireless=IEEE 802.11g
*-network:1 DISABLED
description: Ethernet interface
product: 82562ET/EZ/GT/GZ - PRO/100 VE (LOM) Ethernet Controller
vendor: Intel Corporation
physical id: 8
bus info: pci@0000:03:08.0
logical name: eth0
version: 03
serial: 00:13:20:45:65:57
size: 10MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e100 driverversion=3.5.23-k4-NAPI duplex=half firmware=N/A latency=64 link=no maxlatency=56 mingnt=8 module=e100 multicast=yes port=MII speed=10MB/s



jacob@jacob-desktop:~$ sudo cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid Dominguez Wireless Network
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 8c155590c50e223322cd39e8a9b7b9fdcea10cf3b2f84997ee efa59a79f0a441




jacob@jacob-desktop:~$ sudo ifdown -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 6602
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:17:9a:44:97:8e
Sending on LPF/wlan0/00:17:9a:44:97:8e
Sending on Socket/fallback
ifconfig wlan0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan0.pid
Stopped /sbin/wpa_supplicant (pid 6569).





jacob@jacob-desktop:~$ sudo ifup -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan0
wpa_supplicant: wpa-ap-scan 1 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "Dominguez Wireless Network" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise CCMP -- OK
wpa_supplicant: wpa-group CCMP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto RSN -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:17:9a:44:97:8e
Sending on LPF/wlan0/00:17:9a:44:97:8e
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant
jacob@jacob-desktop:~$

[wieman01]

K-Man_22,

All I can offer is that you have probably installed the wrong driver version. Is your wireless adapter listed anywhere here?

http://ndiswrapper.sourceforge.net/joomla/index.php?/component/option,com_openwiki/Itemid,33/id,list/

This list should provide you with some valuable hints.

EDIT:
If all this fails, look for Kevdog's tutorial on how to compile the latest version of "ndiswrapper". This might be your last hope.

[wieman01]

AZzKikR,

Did the orginal file look exactly the same? Could you remove the "" from the SSID section and try again?

Have you changed anything else in the meantime (e.g. driver, etc.)?

[wieman01]

iwanttobelieve,

Man, beats me... Could you try an SSID without spaces? Plus are you sure this version of the driver for Windows does support WPA2?

Something seems to be seriously wrong... a lot of people posting similar stuff lately. Although it works on my own computer... (scratching my head)

[iwanttobelieve]

wieman01,

I did try changing the ssid to a name without spaces, basically the same one I just deleted the spaces, but it still didn't work. I'm positive that this version of the driver supports WPA2. My original configuration was hidden broadcast, mac filtering on, wpa2 - which worked perfectly fine in WinXP. I've since changed it to broadcast enabled, mac filtering off, wpa2 - which still works just fine in WinXP.

I think I'm going to try to change it to an unsecured network to see if anything changes. The other thing I'll probably try this weekend is to use an older version of Ubuntu to see if that works. From what I've been reading other people also seem to be having problems with wireless cards after upgrading to 8.04. Not sure what's going on, I might need to be patient to see if any kinks need to be worked out.

Thanks for the suggestions. I'll post if I have any success.

[AZzKikR]

AZzKikR,

Did the orginal file look exactly the same? Could you remove the "" from the SSID section and try again?

Have you changed anything else in the meantime (e.g. driver, etc.)?

Thanks for your response, I really appreciate it.

How the original file looked... I don't know. I didn't save my previous /etc/networking/interfaces file, because I thought I would get it to work using this tutorial (it worked before, after all :D)

I've tried removing the "" several times (did a restart of the network everytime). The only thing I've changed in the meantime is removing the NetworkManager applet, and blacklisting the rt2500 and rt2500pci drivers from the modprobe configs.

I'm really baffled. No internet means a no-go for me. Thanks for the response though. Don't you agree though that everything else looks fine (from what I posted)?

[K-Man_22]

K-Man_22,

All I can offer is that you have probably installed the wrong driver version. Is your wireless adapter listed anywhere here?

http://ndiswrapper.sourceforge.net/joomla/index.php?/component/option,com_openwiki/Itemid,33/id,list/

This list should provide you with some valuable hints.

EDIT:
If all this fails, look for Kevdog's tutorial on how to compile the latest version of "ndiswrapper". This might be your last hope.

Hi Wieman01,

thanks for your help. I knew that list and that people got the DWL-G650+ rev. B1 to work. I had even tried all the drivers I could get my hands on (incl. unshielded ones) before I gave up and cried for help in your thread ;-) Your judgement based on the posted system info gave me motivation to keep working on the driver issue.

Long story short: It's working now - Hallelujah!

For all co-sufferers to come, this is what to do:
0. Read and follow wieman01's guide (http://ubuntuforums.org/showthread.php?t=202834)
1. There are many drivers around, some of which can be installed, others may produce errors (neither is relevant!). Ergo: Use a driver that has proven to work for your hardware revision (best: try in windows and stick with it). In my case (D-Link DWL-G650+ rev. B1) use a package called D-Link G650+_v3.10b19_940824_Multi.zip (it's from 2005 and unlikely to be updated anymore, get it from D-Link).
2. Unpack and unshield the windows driver. I used a second PC with Ubuntu and internet connection in the process. Very advisable in conjunction with a USB memory stick. Unshield either one of data1.cab or data2.cab in English_Language ("Others_Language" might also work).
3. You need ndiswrapper, of course. If this is still new to you, read a tutorial or wiki like this one (http://wiki.ubuntuusers.de/WLAN/NdisWrapper) on the german ubuntuusers.de (http://www.ubuntuusers.de/). Ndiswrapper needs to go to your /etc/modules for autostart also.
4. Install via ndiswrapper the previously unpacked driver by chosing the GPLUS.INF in the subfolder /InfXP. BUT: The driver will not work yet, ndiswrapper says 'driver broken'
5. As root copy (sudo cp) the file /DrvXP/GPlus_XP.sys to /etc/ndiswrapper/gplus and I believe it's necessary to make sure it has only small letters: sudo cp /<path to data1 or data2>/DrvXP/GPlus_XP.sys /etc/ndiswrapper/gplus/gplus_xp.sys
6. Restart networking/system.

Thanks again to wieman01 for his tutorial and his ongoing support as well as to the person who provided the crucial hint for my wlan card at NDISwrapper (http://ndiswrapper.sourceforge.net/joomla/index.php?/component/option,com_openwiki/Itemid,33/id,list/) (about the manual driver installation where ndiswrapper failed). Will try to add a reference there, too.

BTW: I think that ndiswrapper can't install the driver by itself because of info given in the INF probably regarding the location of the files. Does anyone know how to fix that?

PS: The system in my sig is not the one I was talking about (see my previous post).

[wieman01]

wieman01,

I did try changing the ssid to a name without spaces, basically the same one I just deleted the spaces, but it still didn't work. I'm positive that this version of the driver supports WPA2. My original configuration was hidden broadcast, mac filtering on, wpa2 - which worked perfectly fine in WinXP. I've since changed it to broadcast enabled, mac filtering off, wpa2 - which still works just fine in WinXP.

I think I'm going to try to change it to an unsecured network to see if anything changes. The other thing I'll probably try this weekend is to use an older version of Ubuntu to see if that works. From what I've been reading other people also seem to be having problems with wireless cards after upgrading to 8.04. Not sure what's going on, I might need to be patient to see if any kinks need to be worked out.

Thanks for the suggestions. I'll post if I have any success.
Trying to connect to an unsecured network is certainly a good idea. Keep me posted, interested to hear if you are making progress.

[wieman01]

Thanks for your response, I really appreciate it.

How the original file looked... I don't know. I didn't save my previous /etc/networking/interfaces file, because I thought I would get it to work using this tutorial (it worked before, after all :D)

I've tried removing the "" several times (did a restart of the network everytime). The only thing I've changed in the meantime is removing the NetworkManager applet, and blacklisting the rt2500 and rt2500pci drivers from the modprobe configs.

I'm really baffled. No internet means a no-go for me. Thanks for the response though. Don't you agree though that everything else looks fine (from what I posted)?
Everything looks super-fine, really.

Question: Can you connect to an unsecured network? What about a WEP secured one? And where have you got the driver from?

[AZzKikR]

I got the driver from the Linksys website. I can connect to my router using SerialMonkey's drivers (although the connection seems to drop every 2 minutes), so the card is working fine.

I've also been looking for any logging about what is actually happening when a connection attempt is made with the router, but can't seem to find anything. I'm really curious what is actually happening. Any ideas where I can find such information? In /var/log perhaps?

[jarviser]

Just to say thanks for the setup instructions. I dropped Dapper when I went wifi and WPA-PSK and went back to XP.
Just installed Hardy Heron and my Belkin USB dongle connected out of the box with WEP, but needed all wieman01's tweaks to get WPA-PSK working. Not sure why this has not been fixed in an update to Hardy but ....

my interface file for BT home hub and belkin USB on WPA-PSK was

auto lo
iface lo inet loopback

iface wlan0 inet static
address 192.168.1.100
netmask 255.255.255.0
gateway 192.168.1.254
wpa-driver wext
wpa-key-mgmt WPA-PSK
wpa-proto WPA
wpa-ssid myhubs-ssid
wpa-group TKIP
wpa-psk <the hex key generated by the wpa_passphrase command>
auto wlan0

then created and associated the restart script totally as per wieman01's instructions.

Wifi card as per my sig below

[wieman01]

I got the driver from the Linksys website. I can connect to my router using SerialMonkey's drivers (although the connection seems to drop every 2 minutes), so the card is working fine.

I've also been looking for any logging about what is actually happening when a connection attempt is made with the router, but can't seem to find anything. I'm really curious what is actually happening. Any ideas where I can find such information? In /var/log perhaps?
You should be able to find stuff in /var/log in fact. Which file exactly, I have no clue.

[wieman01]

Just to say thanks for the setup instructions. I dropped Dapper when I went wifi and WPA-PSK and went back to XP.
Just installed Hardy Heron and my Belkin USB dongle connected out of the box with WEP, but needed all wieman01's tweaks to get WPA-PSK working. Not sure why this has not been fixed in an update to Hardy but ....

my interface file for BT home hub and belkin USB on WPA-PSK was

auto lo
iface lo inet loopback

iface wlan0 inet static
address 192.168.1.100
netmask 255.255.255.0
gateway 192.168.1.254
wpa-driver wext
wpa-key-mgmt WPA-PSK
wpa-proto WPA
wpa-ssid myhubs-ssid
wpa-group TKIP
wpa-psk <the hex key generated by the wpa_passphrase command>
auto wlan0

then created and associated the restart script totally as per wieman01's instructions.

Wifi card as per my sig below
Hardy still cannot handle static IP addresses. Very sad tale.

[jarviser]

Hardy still cannot handle static IP addresses. Very sad tale.

Well the above setup seemed to work. I know my way round XP to find what IP was being used, but I don't know how to check if the 192.168.1.100 was actually assigned to the PC.
Main problem now is I am getting very poor wifi speed, not enough to stream even radio. XP can stream iPlayer video on same wifi dongle. Again how do I look to see what wifi speed I am getting? XP you just hover mousey over the task bar. Don't think Hardy likes WPA.
I only invested a few pennies on this distro, and nice as it is I will probably still use XP. Either that or I'll try Cat5 into a slave wifi router and do the wifi linking in the network itself.

[ninja nicco]

Thanks for a great tutorial! Changed my home wireless to WPA today and it worked without a hitch for the windowses but I couldn't get it working through the GUIs in ubuntu. So I tried this howto and after several hours of tying I finally got it working. I will only say: remember to get the passphrase right when running "wpa_supplicant <essid> <passphrase>" :redface:

Wireless Card: PRO/Wireless 3945ABG
driver: iwl3945
wpa-pairwise: TKIP
wpa-group: TKIP
wpa-key-mgmt: PSK
(width DHCP)

Had to run
sudo /etc/init.d/networking restart twise to get it running.

[AZzKikR]

Trying to connect to an unsecured network is certainly a good idea. Keep me posted, interested to hear if you are making progress.

Hey Wieman01,

I re-read your comment on another post about 'Hardy not supporting static IP addresses'.

I was screwing around a bit, mainly with System -> Administration -> Network. I edited my config from there (just to see what was going to be written to /etc/network/interfaces), and chose DHCP. It seems that my connection is now working with ndiswrapper (it still uses wext as driver).

Looks as if static IP addresses do not work under Hardy. Did work under Gutsy though :S

My connection is now terribly slow though. Running an 'apt-get upgrade' at the moment, and it is downloading at 37.5 Kb/s. When I'm not downloading, pinging the gateway usually gives an average of about 2 or 3 seconds.

Weird stuff. Thanks though for looking into my problem.

EDIT:

My ping average was because I was accidentally running a download in the background. So I've come to the conclusion that:

- Running another download gives me ping results of 3000+ ms average;
- Download capacity is around 35 kb/s. On previous Ubuntus I could get speeds of 500 kb/s;
- Visiting webpages goes slow as hell like this;
- "Concurrent" browsing/downloading/playing games over the internet is a pain in the ****.

Well, at least I can successfully do updates/installation via apt. I'll do some more investigative work tonight at home.

[wieman01]

Hey Wieman01,

I re-read your comment on another post about 'Hardy not supporting static IP addresses'.

I was screwing around a bit, mainly with System -> Administration -> Network. I edited my config from there (just to see what was going to be written to /etc/network/interfaces), and chose DHCP. It seems that my connection is now working with ndiswrapper (it still uses wext as driver).

Looks as if static IP addresses do not work under Hardy. Did work under Gutsy though :S

My connection is now terribly slow though. Running an 'apt-get upgrade' at the moment, and it is downloading at 37.5 Kb/s. When I'm not downloading, pinging the gateway usually gives an average of about 2 or 3 seconds.

Weird stuff. Thanks though for looking into my problem.

EDIT:

My ping average was because I was accidentally running a download in the background. So I've come to the conclusion that:

- Running another download gives me ping results of 3000+ ms average;
- Download capacity is around 35 kb/s. On previous Ubuntus I could get speeds of 500 kb/s;
- Visiting webpages goes slow as hell like this;
- "Concurrent" browsing/downloading/playing games over the internet is a pain in the ****.

Well, at least I can successfully do updates/installation via apt. I'll do some more investigative work tonight at home.
Mmm... Odd indeed!

I know it's an old issue, however, a common workaround for a slow connections used to be disabling IPV6 globally and in the browser. IPV6 used to be the main culprit (or at least one of them) for performance problems.

Not sure if it makes a difference, but I thought I'd mention it.

[geezerone]

What I don't understand is that I cannot get a usb Bt voyager wireless adapter to connect to my wireless network (not even recognised) on either GG or HH BUT when I ran the live cd of Fedora 9 it was recognised and I was up and working in a couple of minutes. Is it too much to get hardware recognised on Ubuntu because at least one other distro doesn't have the same problem. Given also the increasing number of users having problems with HH maybe the time to change to FC9 has come?:confused:

[VayHow]

Thank you very much! Now I understand much more about it.

But what I experienced is another problem. My NIC is Intel 3945ABG and AP is Linksys WRH54G. I shut down DHCP on router, and set wireless security to WPA2 personal (AES+TKIP). I set the static IP correctly on laptop, as well as DNS & gateway, everything. Then open FireFox, all OK. BUT, every time I reboot the system, or power on my laptop, I have to manually configure the security and the password again, or I can't get access to my AP. And I noticed that, static IPs, DNS & gateway are all right, except for the security (shown as WPA instead of WPA2 and the password is incorrect, either). This bothers me a lot. Every time I have to choose WPA2 and type in the password.

PS: How can I modify the config file "interfaces"? I just can't save my change. I'm using the account created when install, not root.

[lunatico]

Hello,

Using this tutorial I created my own wpa_supplicant script which I use to connect to my college network. Before (on gutsy 7.10) I had to kill network manager as stated at the beginning of this tutorial. I was actually using WICD instead of NM which didn't interfere with the script. But now (on hardy 8.04) NM was installed again and I am able to run the same wpa_script with no problem, AND network manager is not messing with it anymore, the connection stays up and very stable.
The only thing is that network manager will not update its connected state. Does anyone know how to make nm-applet to refresh the connection state...? in other words if one configures the wifi connection manually how can nm-applet be updated and show it is connected, signal strength and all that?

Thanks!

[wieman01]

Thank you very much! Now I understand much more about it.

But what I experienced is another problem. My NIC is Intel 3945ABG and AP is Linksys WRH54G. I shut down DHCP on router, and set wireless security to WPA2 personal (AES+TKIP). I set the static IP correctly on laptop, as well as DNS & gateway, everything. Then open FireFox, all OK. BUT, every time I reboot the system, or power on my laptop, I have to manually configure the security and the password again, or I can't get access to my AP. And I noticed that, static IPs, DNS & gateway are all right, except for the security (shown as WPA instead of WPA2 and the password is incorrect, either). This bothers me a lot. Every time I have to choose WPA2 and type in the password.

PS: How can I modify the config file "interfaces"? I just can't save my change. I'm using the account created when install, not root.
You edit it as indicated in the tutorial. You need to add "sudo". Just follow the tutorial or try WICD:

http://wicd.sourceforge.net/

[wieman01]

Hello,

Using this tutorial I created my own wpa_supplicant script which I use to connect to my college network. Before (on gutsy 7.10) I had to kill network manager as stated at the beginning of this tutorial. I was actually using WICD instead of NM which didn't interfere with the script. But now (on hardy 8.04) NM was installed again and I am able to run the same wpa_script with no problem, AND network manager is not messing with it anymore, the connection stays up and very stable.
The only thing is that network manager will not update its connected state. Does anyone know how to make nm-applet to refresh the connection state...? in other words if one configures the wifi connection manually how can nm-applet be updated and show it is connected, signal strength and all that?

Thanks!
I cannot help you there but thanks for sharing this with us. Very interesting discovery. :-)

[VayHow]

You edit it as indicated in the tutorial. You need to add "sudo". Just follow the tutorial or try WICD:

http://wicd.sourceforge.net/

Thanks. I've edited the "interfaces" file following your tutorial. Then $ sudo /etc/init.d/networking restart, everything's OK. BUT, after every reboot, or power on, I just can't connect to my router unless I restart network manually using the above command. It's can't be done automatically. I've added "auto wlan0" in the config file, and other lines are all right. All this need is a manually restart after boot, really weird.:confused:

[spaceboy909]

Compaq r4010us w/ Broadcom 4306 using ndiswrapper / wext on Gutsy

Between this tutorial and this one: http://ubuntuforums.org/showthread.php?t=571188 , I've been able to get my wireless running in WPA2 AES with static IP.

I've spent about a week fiddling with various things, so even though I'm new, I may be able to help out a bit.

First off, to those saying that Hardy won't do static IP's..... well, you may need to do what I had to do in Gutsy, and that is uninstall 'network-manager' and/or 'gnome-network-manager'.

I could not get my static IP and other settings to stick while network manager was still an active service.

For reference, here are my /etc/network/interfaces and /etc/wpa_supplicant.conf files.

Note that I have left out my wired inteface as I don't plan to use it. Also note that I only have the driver (wext) and the location of the supplicant config file in this interfaces file.

All of the remaining wireless info I have placed in the wpa_supplicant.conf file. I have discovered with some experimentation that these two files overlap a certain amount, so you can place some wireless info in one or the other, or even duplicate it in both.

However, unless there is a critical reason why it needs to be duplicated, I would suggest not doing it because if you ever need to change something, you may forget that you have the information duped and won't understand why the new settings won't take.

auto lo
iface lo inet loopback


auto wlan0
iface wlan0 inet static
address 192.168.1.102
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.1

wpa-driver wext
wpa-conf /etc/wpa_supplicant.conf

ap_scan=2

ctrl_interface=/var/run/wpa_supplicant


network={

ssid="stoog"
scan_ssid=0
proto=RSN
key_mgmt=WPA-PSK
psk=your-key-here
pairwise=CCMP
group=CCMP
}
Hope this helps some people.

Edit: Forgot to add, that I used /etc/init.d/networking restart to apply the new settings. I did not need to do a dbus restart in my case.

[wieman01]

Thanks. I've edited the "interfaces" file following your tutorial. Then $ sudo /etc/init.d/networking restart, everything's OK. BUT, after every reboot, or power on, I just can't connect to my router unless I restart network manually using the above command. It's can't be done automatically. I've added "auto wlan0" in the config file, and other lines are all right. All this need is a manually restart after boot, really weird.:confused:
Then please see post #2 of this thread.

[aolias]

Hi lads,

I upgraded my ubuntu installation from Feisty to Hardy and my wireless card just stopped to work.

I have a WPN111 Netgear USB. The ndiswrapper is working fine, because if I turn off the security in my router I can connect to the internet with no problem. But Enabling the WPA I cannot connect to the router.

I have installed wicd and I couldn't get it to work. Also I have running the gnome network manager. I installed the wpa_supplicant and I generated the key structure. So here it is my actual configuration

/etc/wpa_supplicant.conf


ctrl_interface=/var/run/wpa_supplicant
eapol_version=1
ap_scan=2
fast_reauth=1

network={
ssid="xxxxxxxxxxx"
proto=WPA RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP
psk=xxxxxxxxxxxxxxxxxxxxxxxxxx
}

/etc/network/interfaces



#iface wlan0 inet static
#address 192.168.0.9
#netmask 255.255.255.0
#gateway 192.168.0.1
#pre-up wpa_supplicant -Bw -Dwext -i wlan0 -c/etc/wpa_supplicant.conf
#post-down killall -q wpa_supplicant

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid xxxxxxxxxxxxxxxxxx
#wpa-ap-scan 1 # only needed if your access point uses a hidden ssid
wpa-proto WPA RSN
wpa-pairwise CCMP TKIP
wpa-group CCMP TKIP
wpa-key-mgmt WPA-PSK
wpa-psk xxxxxxxxxxxxx



If I run the command sudo ifup -v wlan0



Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan0
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "NETGEAR" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise CCMP TKIP -- OK
wpa_supplicant: wpa-group CCMP TKIP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto WPA RSN -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:18:4d:2b:ee:a0
Sending on LPF/wlan0/00:18:4d:2b:ee:a0
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/000resolvconf
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant



But never connects
I have also tried removing CCMP and RSN from the file, but the result is the same.



iwlist wlan0 scanning



wlan0 Scan completed :

Cell 02 - Address: 00:18:4D:01:BC:5E
ESSID:"NETGEAR"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:17/100 Signal level:-85 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK


iwconfig



wlan0 IEEE 802.11g ESSID:off/any
Mode:Managed Frequency:2.437 GHz Access Point: 00:18:4D:01:BC:5E
Bit Rate=108 Mb/s
Power Management:off
Link Quality:23/100 Signal level:-81 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

sudo lshw -C network



*-network
description: Wireless interface
physical id: 1
logical name: wlan0
serial: 00:18:4d:2b:ee:a0
capabilities: ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+netwpn11 driverversion=1.52+NETGEAR,09/26/2005,1.5.0.21 link=no multicast=yes wireless=IEEE 802.11g


Any idea? please help

[dpsf]

Hi Everyone,

Thank you wieman01 for your excellent tutorial! Using your guide I
got my wireless (Intel 3945) with WPA-PSK & hidden essid working with
only a minimal amount of pain in a Feisty Fawn install CD. A couple
of weeks ago I was at a friend's house; he has a old wireless router
without any security enabled. I tested the Hardy Heron last beta CD
while there and it worked fine; I naively thought I was OK with WPA
as well then. Unfortunately, testing the same setup with the WPA
enabled router has not gone so well...

Here is what Feisty (which I'm using again to post this now) reports
about the configuration:

lo no wireless extensions.

eth0 no wireless extensions.

eth1 IEEE 802.11g ESSID:"<blah>"
Mode:Managed Frequency:2.442 GHz Access Point: xx:...:xx
Bit Rate:54 Mb/s Tx-Power:13 dBm
Retry limit:15 RTS thr:off Fragment thr:off
Encryption key: <blah> Security mode:open
Power Management:off
Link Quality=77/100 Signal level=-58 dBm Noise level=-59 dBm
Rx invalid nwid:0 Rx invalid crypt:22 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:2278 Missed beacon:0

and the /etc/network/interfaces file which got it working:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-ssid <blah>
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk <very-secret-hex-code>


In Hardy Heron, I've noticed that the eth1 interface has been
replaced by wlan0 (what is wmaster0?), so I changed the setup to:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid <blah>
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk <very-secret-hex-code>

I can see the access point with an iwlist scan command, and after
restarting the network it even sees the router's hidden essid,
but everything halts there and DHCP times out.

I would love to get Hardy Heron working with WPA, especially since
once I saw it was working I dove in and installed HH to a partition
on the hard drive and then installed & configured a slew of packages.

It's been many hours now of trying to get this working & I'm losing
sleep & hair over this. I'm just about ready to ditch Hardy as a
lost cause and revert to Feisty (probably for good at that point &
once I get Gentoo WPA working...), but before then I'm making this plea.
Can anyone help me get the HH wireless working properly?

Thanx,
dpsf

------------------------------------------------------------------------
For any Ubuntu devs who stumble upon this:

<growl>

I know I'm not alone here... searching the forums has produced many
other examples of people who previously had their wireless cards
working & now are lost at sea... for ex:

"having it work ok in 7.10 and then break in 8.04 is a real shame.
i was this close to recommending Linux to friends (I have been for
about 5 years now...)"

I feel precisely the same way. It is so painful to watch Linux backtrack-
*again*. I'm sure the resolution to this will turn out to be some
painfully simple 1 or 2 line fix.

what gives? Don't you have anyone testing this critically important
facet of the distribution? This is madness!! Your 'network connection'
application is completely, utterly useless for wireless WPA. Yet with
some fairly simple changes to cfg files and a simple script, magically
that changes... couldn't the network connection application do this so
that new (and less determined) users aren't put off?

Further, a catch-22 exists here. Why isn't this entire, incredibly
useful thread zipped up and placed in your *examples folder* on the
CD/DVD? For that matter, why not add other forum topics addressing
commonly asked questions? If a new user cannot get online then almost
certainly the distribution's CD ends up as a table coaster, if it's
that lucky.

While I've been running Linux I've seen this time & again, for ex:

> Helping a friend get basic Linux installed on a dual-boot computer--
everything working but Linux & Windows fight over the clock! A simple
additional configuration line fixed this & thankfully I knew where to
look, because he as a Linux newbie was getting extremely frustrated.
WHY ISN'T THERE A SIMPLE FREAKING 'DUAL-BOOT' CHECK BOX IN THE KDE
CLOCK APPLET????!!? Why? The last time I checked-- it still wasn't
there! Maddening.

I'm fairly sure he later simply ditched Linux; can you blame him?

I could go on at length with Linux nightmares that were resolved by
ridiculous little fixes *if you knew*, but I'm belabouring the point,
so:

</growl>

[VayHow]

Then please see post #2 of this thread.

Thank you again for your patience. I just missed that part of creating a startup script. I thought it was my problem, not a bug:lolflag:

And one more question: You mentioned "sudo ln -s /etc/init.d/wireless-network.sh /etc/rcS.d/S40wireless-network", and "You may have to choose a boot sequence other than S40". So what does this "S40" stand for? How can I decide this sequence?

[gladstone]

Thank you again for your patience. I just missed that part of creating a startup script. I thought it was my problem, not a bug:lolflag:

And one more question: You mentioned "sudo ln -s /etc/init.d/wireless-network.sh /etc/rcS.d/S40wireless-network", and "You may have to choose a boot sequence other than S40". So what does this "S40" stand for? How can I decide this sequence?

I just wonder, after soooo long, why we still need to make the restart script in Hardy! Why hasn't this bug been fix yet!?

[wieman01]

Thank you again for your patience. I just missed that part of creating a startup script. I thought it was my problem, not a bug:lolflag:

And one more question: You mentioned "sudo ln -s /etc/init.d/wireless-network.sh /etc/rcS.d/S40wireless-network", and "You may have to choose a boot sequence other than S40". So what does this "S40" stand for? How can I decide this sequence?
Any sequence will do in fact. But S40 is OK for wireless networking. :-)

[wieman01]

I just wonder, after soooo long, why we still need to make the restart script in Hardy! Why hasn't this bug been fix yet!?
Too few people who have reported it. I don't know, maybe it isn't a bug after all. Annoying nonetheless.

[wieman01]

Hi Everyone,

Thank you wieman01 for your excellent tutorial! Using your guide I
got my wireless (Intel 3945) with WPA-PSK & hidden essid working with
only a minimal amount of pain in a Feisty Fawn install CD. A couple
of weeks ago I was at a friend's house; he has a old wireless router
without any security enabled. I tested the Hardy Heron last beta CD
while there and it worked fine; I naively thought I was OK with WPA
as well then. Unfortunately, testing the same setup with the WPA
enabled router has not gone so well...

Here is what Feisty (which I'm using again to post this now) reports
about the configuration:

lo no wireless extensions.

eth0 no wireless extensions.

eth1 IEEE 802.11g ESSID:"<blah>"
Mode:Managed Frequency:2.442 GHz Access Point: xx:...:xx
Bit Rate:54 Mb/s Tx-Power:13 dBm
Retry limit:15 RTS thr:off Fragment thr:off
Encryption key: <blah> Security mode:open
Power Management:off
Link Quality=77/100 Signal level=-58 dBm Noise level=-59 dBm
Rx invalid nwid:0 Rx invalid crypt:22 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:2278 Missed beacon:0

and the /etc/network/interfaces file which got it working:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-ssid <blah>
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk <very-secret-hex-code>


In Hardy Heron, I've noticed that the eth1 interface has been
replaced by wlan0 (what is wmaster0?), so I changed the setup to:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid <blah>
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk <very-secret-hex-code>

I can see the access point with an iwlist scan command, and after
restarting the network it even sees the router's hidden essid,
but everything halts there and DHCP times out.

I would love to get Hardy Heron working with WPA, especially since
once I saw it was working I dove in and installed HH to a partition
on the hard drive and then installed & configured a slew of packages.

It's been many hours now of trying to get this working & I'm losing
sleep & hair over this. I'm just about ready to ditch Hardy as a
lost cause and revert to Feisty (probably for good at that point &
once I get Gentoo WPA working...), but before then I'm making this plea.
Can anyone help me get the HH wireless working properly?

Thanx,
dpsf

My setup works with Hardy. Strange thing. I cannot promise there is much I can do but let's give it a try:

sudo iwlist scan

sudo lshw -C network
What adapter have you got and what chipset are we talking about?

[richman241]

I couldn't connect to my secured network, so I ended up closing my network so you have to know the SSID to get on.

[aolias]

But anybody can scan the channels and listen for traffic .. and read what are you sending!

[geezerone]

I can connect to my WPA2 network but only if the SSID is broadcast by the access point.

I configured a manual connection from the network manager applet and have the following interfaces config:


iface wlan0 inet static
address 192.168.0.250
netmask 255.255.255.0
gateway 192.168.0.249
wpa-ap-scan 2
wpa-psk my hex key
wpa-driver wext
wpa-key-mgmt WPA-PSK
wpa-proto WPA2
wpa-ssid networkssid

auto wlan0Have tried this on Gutsy and Hardy to no avail so have to reluctantly broadcast this.

I am using a BT Voyager 1055 usb wireless adaptor (bcm4320b driver)

Any help appreciated of course. :KS

[VayHow]

So much thanks! I'm feeling thankful to you, and this forum. I'm loving it :)

BTW, you love Chinese culture? Coz I saw the big Chinese character below your ID. I'm Chinese and I think it's cool, very cool~ :)

[pallavis11]

See the info below:

http://a2zhowto .blogspot.com/

http://learnphpwithme .blogspot.com/

[wieman01]

So much thanks! I'm feeling thankful to you, and this forum. I'm loving it :)

BTW, you love Chinese culture? Coz I saw the big Chinese character below your ID. I'm Chinese and I think it's cool, very cool~ :)
Wo shi shu long de... :-)

[roninrun]

Ok I followed this guide and still have been unsuccessful. Here is the outputs to help me troubleshoot my wireless card.
The card is a Netgear WG311v2 wireless card trying to connect to a WPA network. I've blacklisted the ACX module and used ndiswrapper on the XP driver to get WPA support. I removed network manager as well.
I can see the network but I cannot get DHCP to pull down an ip.

Please help. This is on a test box. I have yet to install this on my main PC with the exact same card.

route:

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
link-local * 255.255.0.0 U 0 0 0 wlan0
default * 0.0.0.0 U 1000 0 0 wlan0

iwconfig:

wlan0 IEEE 802.11g ESSID:"ARBOUR"
Mode:Managed Frequency:2.462 GHz Access Point: 00:40:10:10:00:03
Bit Rate=54 Mb/s Tx-Power:10 dBm Sensitivity=0/3
RTS thr:off Fragment thr:off
Power Management:off
Link Quality:81/100 Signal level:-44 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

iwlist scan:

wlan0 Scan completed :
Cell 01 - Address: 00:19:5B:58:27:BF
ESSID:""
Protocol:IEEE 802.11b
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:25/100 Signal level:-80 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 02 - Address: 00:40:10:10:00:03
ESSID:"ARBOUR"
Protocol:IEEE 802.11b
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:84/100 Signal level:-42 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK

lshw -C network:

*-network:0
description: Wireless interface
product: ACX 111 54Mbps Wireless Interface
vendor: Texas Instruments
physical id: 6
bus info: pci@0000:01:06.0
logical name: wlan0
version: 00
serial: 00:0f:b5:05:33:ea
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+wg311v2 driverversion=1.52+NETGEAR, Inc.,06/17/2004,6. latency=32 link=yes module=ndiswrapper multicast=yes wireless=IEEE 802.11g
*-network:1 DISABLED
description: Ethernet interface
product: BCM4401 100Base-T
vendor: Broadcom Corporation
physical id: 9
bus info: pci@0000:01:09.0
logical name: eth0
version: 01
serial: 00:0b:db:2e:5a:ca
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=b44 driverversion=2.0 latency=32 link=no module=ssb multicast=yes port=twisted pair

/etc/network/interfaces:

auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid ARBOUR
wpa-ap-scan 2
wpa-proto WPA RSN
wpa-pairwise CCMP TKIP
wpa-group CCMP TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <THIS IS WHERE MY GENERATED KEY IS>

ifdown -v:

Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/wpasupplicant
wpa_supplicant: cannot read contents of managed
run-parts: /etc/network/if-down.d/wpasupplicant exited with return code 1
dhclient3 -r -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 6075
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:0f:b5:05:33:ea
Sending on LPF/wlan0/00:0f:b5:05:33:ea
Sending on Socket/fallback
ifconfig wlan0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
grep: /etc/resolv.conf: No such file or directory
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: cannot read contents of managed
run-parts: /etc/network/if-post-down.d/wpasupplicant exited with return code 1

ifup -v:

Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: cannot read contents of managed
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1

dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:0f:b5:05:33:ea
Sending on LPF/wlan0/00:0f:b5:05:33:ea
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
grep: /etc/resolv.conf: No such file or directory
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant
wpa_supplicant: cannot read contents of managed
run-parts: /etc/network/if-up.d/wpasupplicant exited with return code 1

[geezerone]

Does fixed IP work by any chance? I use fixed IP as DHCP didn't work.

Also used wicd to manage network for Hardy even though nm worked with Gutsy.

[wieman01]

Roninrun:

Try another scanning mode instead and try again:

wpa-ap-scan 1
Otherwise check out geezerone's approach.

[aarnink]

Hi there,
I have been struggling with my Ubuntu 8.04 x64 and the new Wireless USB adapter (Eminent EM4555) which is based on the Ralink rt2870 chipset.
I downloaded the 1.30 version of the native RAlink drivers and installed them on a clean Unbuntu setup.

I followed the instructions in the driver carefully and set the
'HAS_WPA_SUPPLICANT=y' and 'HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y'

After setting up the interfaces file and starting ra0 this is what iwconfig shows:

ra0 RT2870 Wireless ESSID:"aarnink_N" Nickname:"RT2870STA"
Mode:Managed Frequency=2.412 GHz Access Point: 00:60:B3:A6:F9:5A
Bit Rate=270 Mb/s
RTS thr:off Fragment thr:off
Encryption key:xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx
Link Quality=70/100 Signal level:-58 dBm Noise level:-71 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

So this looks promising but, as I read on this forum, like others I cannot get an IP address.

my interfaces file


auto lo
iface lo inet loopback

iface ra0 inet dhcp
wpa-conf /etc/wpa_supplicant/sup.conf
gateway 192.168.0.1
wpa-ap-scan 1
wpa-pairwise CCMP
wpa-group CCMP
wpa-psk <my psk hex string>
wpa-driver wext
wpa-key-mgmt WPA-PSK
wpa-proto RSN WPA
wpa-ssid aarnink_N

auto ra0


sup.conf

network={
ssid="aarnink_N"
#psk="richardenmarloes"
psk=<my psk hex thingy>
}


lshw -C network

*-network
description: Wireless interface
physical id: 1
logical name: ra0
serial: 00:60:b3:a6:f2:30
capabilities: ethernet physical wireless
configuration: broadcast=yes multicast=yes wireless=RT2870 Wireless


ifconfig ra0

ra0 Link encap:Ethernet HWaddr 00:60:b3:a6:f2:30
inet6 addr: fe80::260:b3ff:fea6:f230/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:112614 errors:0 dropped:0 overruns:1513 frame:1513
TX packets:1269 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:20163638 (19.2 MB) TX bytes:114840 (112.1 KB)

ra0:avahi Link encap:Ethernet HWaddr 00:60:b3:a6:f2:30
inet addr:169.254.8.113 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1


As shown in the ifconfig output I receive a local IP address. Already tried a static IP, but this doesnt work, IP address will be shown, but cannot ping.

resolv.conf shows:
nameserver 192.168.0.1


ifup -v ra0

root@mainframe:/usr/lib/rt2870/os/linux# ifup -v ra0
Configuring interface ra0=ra0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.ra0.pid -i ra0 -D wext -c /etc/wpa_supplicant/sup.conf -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/ra0
wpa_supplicant: wpa-ap-scan 1 -- OK
wpa_supplicant: configuring network block -- 1
wpa_supplicant: wpa-ssid "aarnink_N" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise CCMP -- OK
wpa_supplicant: wpa-group CCMP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto RSN WPA -- OK
wpa_supplicant: enabling network block 1 -- OK

dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.ra0.pid -lf /var/lib/dhcp3/dhclient.ra0.leases ra0
There is already a pid file /var/run/dhclient.ra0.pid with pid 0
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/ra0/00:60:b3:a6:f2:30
Sending on LPF/ra0/00:60:b3:a6:f2:30
Sending on Socket/fallback
DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 14
No DHCPOFFERS received.
No working leases in persistent database - sleeping.




Can someone please help me, I am completely lost. help

thanx in adv, Richard

[aarnink]

Hi,

The battle with my rt2870 ralink wireless adapter continuous. Yesterday went back to basics in my struggle for a succesfull connection to the internet.

I succeeded in connecting to my router by disabling the routers security. [Set to OPEN and NO encryption]

- clearing the interfaces file from all 'ra0' enteries in the '/etc/network' directory except 'iface ra0 inet dhcp' and 'auto ra0'
- edit the RT2870STA.dat file in de '/etc/Wireless' directory to match the security settings for the router
- entered the commands


iwconfig ra0 mode managed
iwconfig ra0 channel 6
iwconfig ra0 ap <my ap hex address>
iwconfig ra0 essid aarnink_N
iwpriv ra0 set AuthMode=OPEN
iwpriv ra0 set EncrypType=NONE
ifconfig ra0 up
dhclient ra0

And :) I had a connection to Internet. A step forward, but ofcourse the story continuous by adding security. And this is where it stops. :(

I am not able to set security in the same manner by adding commands on the prompt e.g.

iwpriv ra0 set AuthMode=WPAPSK
iwpriv ra0 set EncrypType=TKIP

iwpriv ra0 set essid "MY_SSID"
>> command fails

iwpriv ra0 set WPAPSK="MY_PASSKEY_HERE"
>> after entering this command my AP and and ssid disappears [I run iwconfig ra0 in seperate window to watch what happens after each command]

ifconfig ra0 up
dhclient ra0

I dont get an IP address... :(


I think I have managed to set a step forward, but I am starting to think that I cannot make this work...

Any Ideas?

[aarnink]

Hi All,

The RAlink RT2870 chipset saga continuous.
A new attempt to create a working Wireless connection today failed. Again, a open system (no encryption) will work fine. I could repeat my succes I had yesterday.

However now I ran into this message in SystemLog on inserting the compiled rt2870sta.ko driver


NetworkManager <WARN> real_get_generic_capabilities(): ra0: driver's Wireless Extensions version (9) is too old. Can't use device.



I installed Kubuntu 8.04 x64 and installed the package wlassistant which was recommended, but to no reveil.

Now I stand empty handed again. Any suggestions?

[AZzKikR]

I installed Gutsy again. Ndiswrapper + rt2500 works now, although it drops a connection here and there. I believe I fixed this previously by compiling a new version of ndiswrapper.

Overall, I get nice 500 kb/s download speeds again. Seems it will be no Hardy Heron for me.

This whole situation made me think: what did they change to ndiswrapper (or the kernel, I don't know) that it does not work in Hardy, but does work in Gutsy?

[creasar]

Nice thread! I really like your provided information. It's really helpful for me.
Thanks a lot!

[wieman01]

aarnink:

What's the latest status?

[aarnink]

Hi all,

Today I received an email from Ralink containing new drivers for the Ralink rt2870. Guess what, they are working!

I run Ubuntu 8.04 x64, my router is set to WPA2 with AES encryption.

I dont know if these modified drivers are on the website already, so I will enclose them in this post

I learned a lot the last couple of days... keep up the positive spirit...:)

gr,
Richard

[dpsf]

Hi Wieman01!

Sorry for the delay but I could not test last week. The adapter is an Intel 3945 "Pro
Wireless"- here is the relevant lspci section:

05:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)

The strange thing is that in Hardy Heron, iwlist scan *does see* the wireless router
and also identifies the essid (once the interfaces file has been changed & the network
restarted- before that it does not list an essid, but it is the same router since I
recognize the MAC address):

#iwlist scan:
lo Interface doesn't support scanning.

wmaster0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: <MAC address of the WPA router>
ESSID:<blah>
Mode:Master
& etc.

Here are the lshw -C network outputs:

lshw -C network in Hardy Heron:
*-network UNCLAIMED
description: Ethernet controller
product: 88E8055 PCI-E Gigabit Ethernet Controller
vendor: Marvell Technology Group Ltd.
physical id: 0
bus info: pci@0000:02:00.0
version: 12
width: 64 bits
clock: 33MHz
capabilities: pm vpd msi pciexpress cap_list
configuration: latency=0
*-network
description: Wireless interface
product: PRO/Wireless 3945ABG Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:05:00.0
logical name: wmaster0
version: 02
serial: <blah>
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=iwl3945 latency=0 module=iwl3945 multicast=yes wireless=IEEE 802.11g
-----------------------------------------------------------------
lshw -C network in Feisty Fawn:
*-network UNCLAIMED
description: Ethernet controller
product: 88E8055 PCI-E Gigabit Ethernet Controller
vendor: Marvell Technology Group Ltd.
physical id: 0
bus info: pci@02:00.0
version: 12
width: 64 bits
clock: 33MHz
capabilities: cap_list
configuration: latency=0
resources: iomemory:f0000000-f0003fff ioport:2000-20ff irq:19
*-network
description: Wireless interface
product: PRO/Wireless 3945ABG Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@05:00.0
logical name: eth1
version: 02
serial: <blah>
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ipw3945 driverversion=1.2.0mp
firmware=14.2 1:0 () ip=<blah> latency=0 link=yes multicast=yes wireless=IEEE 802.11g
resources: iomemory:74100000-74100fff irq:21

The "unclaimed" is because I remove the sky2 module which runs the Marvell hardware.

A possible clue (I hope) comes from the difference in drivers-- The binary blob
module in Feisty may simply work better. While rebooting into Feisty I noted its
whine about "restricted drivers" and then I did a few comparison tests using
iwlist scan-typically using ipw3945 all or nearly all the networks in the area
will show up, whereas with iwl3945 only 1 or 2 do...

So I am going to see if I can get ipw3945 going in HH; I'll give an update once I
can get working (or not... The Linux Kernel needs a stable module API, imho).

Thanx,

dpsf.

[pmurberg]

Gentlemen:
I have tried the HOWTOs of several websites, and
cannot get a HP Pavilion DV2000 to do wireless.
Failing that: I have created this post composed of
Root Terminal responses to most commands that I could locate.
This wireless card worked fine with a TRENDnet TEW-452BRP 108 MPS 11g wireless router before.
Now after installing the bcmwl5.inf driver for the Broadcom 4311 wireless router, I can't get an IP address, from 1 meter distance with Wifi Radar.
This is Linux Mint Celena over Ubuntu Feisty Fawn, and the response to lspci is listed below.

Is there something I have overlooked?



****************************Post this if you are Stumped******************************************
================================================== ===================================
root@peter-laptop:/etc/network# lshw -C network

*-network UNCLAIMED
description: Network controller
product: Dell Wireless 1390 WLAN Mini-PCI Card
vendor: Broadcom Corporation
physical id: 0
bus info: pci@01:00.0
version: 02
width: 64 bits
clock: 33MHz
capabilities: bus_master cap_list
configuration: latency=0
resources: iomemory:b3000000-b3003fff irq:11
Nickname:"Broadcom 4311"

****************************Post this if you are Stumped******************************************
route | iwconfig |sudo iwlist scan | sudo lshw -C network | sudo cat /etc/network/interfaces | sudo ifdown -v eth0 | sudo ifup -v eth0

route | iwconfig |sudo iwlist scan | sudo lshw -C network | sudo cat /etc/network/interfaces | sudo ifdown -v eth0 | sudo ifup -v eth0

peter@peter-laptop:~$ sudo su -
Big book, big bore.
-- Callimachus
root@peter-laptop:~# route | iwconfig |sudo iwlist scan | sudo lshw -C network | sudo cat /etc/network/interfaces | sudo ifdown -v eth0 | sudo ifup -v eth0
lo no wireless extensions.

eth0 no wireless extensions.

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

Configuring interface eth0=eth0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
Configuring interface eth0=eth0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.eth0.pid -lf /var/lib/dhcp3/dhclient.eth0.leases eth0
There is already a pid file /var/run/dhclient.eth0.pid with pid 4868
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
Listening on LPF/eth0/00:16:d3:a7:1b:0d
Sending on LPF/eth0/00:16:d3:a7:1b:0d
Sending on Socket/fallback

dhclient3 -pf /var/run/dhclient.eth0.pid -lf /var/lib/dhcp3/dhclient.eth0.leases eth0
There is already a pid file /var/run/dhclient.eth0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

DHCPRELEASE on eth0 to 192.168.1.1 port 67
ifconfig eth0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
Listening on LPF/eth0/00:16:d3:a7:1b:0d
Sending on LPF/eth0/00:16:d3:a7:1b:0d
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPOFFER from 192.168.1.1
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 192.168.1.1
bound to 192.168.1.101 -- renewal in 297724 seconds.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant
root@peter-laptop:~#
root@peter-laptop:~# lshw -C network
*-network
description: Wireless interface
product: Dell Wireless 1390 WLAN Mini-PCI Card
vendor: Broadcom Corporation
physical id: 0
bus info: pci@01:00.0
logical name: wlan0
version: 02
serial: 00:1a:73:79:f9:ad
width: 64 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper driverversion=1.38 firmware=Broadcom,10/12/2006, 4.100.15.5 latency=0 link=no multicast=yes wireless=IEEE 802.11g
resources: iomemory:b3000000-b3003fff irq:22

root@peter-laptop:~# sudo /usr/lib/linuxmint/mintWifi/mintWifi.py
-------------------------
* I. scanning WIFI PCI devices...
-- Broadcom Corporation Dell Wireless 1390 WLAN Mini-PCI Card (rev 02)
==> PCI ID = 14e4:4311 (rev 02)
-------------------------
* II. querying ndiswrapper...
bcmwl5 : driver installed
device (14E4:4311) present (alternate driver: bcm43xx)
-------------------------
* III. querying iwconfig...
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:off/any
Mode:Managed Frequency:2.462 GHz Access Point: Not-Associated
Bit Rate=54 Mb/s Tx-Power:32 dBm
RTS thr=2347 B Fragment thr=2346 B
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

-------------------------
* IV. querying ifconfig...
eth0 Link encap:Ethernet HWaddr 00:16:D3:A7:1B:0D
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3873 errors:0 dropped:0 overruns:0 frame:0
TX packets:3787 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2754453 (2.6 MiB) TX bytes:533892 (521.3 KiB)
Interrupt:16 Base address:0x8000

eth0:avah Link encap:Ethernet HWaddr 00:16:D3:A7:1B:0D
inet addr:169.254.4.95 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:16 Base address:0x8000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:10 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1080 (1.0 KiB) TX bytes:1080 (1.0 KiB)

wlan0 Link encap:Ethernet HWaddr 00:1A:73:79:F9:AD
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:22 Memory:b3000000-b3004000

-------------------------
* V. querying DHCP...
There is already a pid file /var/run/dhclient.pid with pid 11171
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:1a:73:79:f9:ad
Sending on LPF/wlan0/00:1a:73:79:f9:ad
Listening on LPF/eth0/00:16:d3:a7:1b:0d
Sending on LPF/eth0/00:16:d3:a7:1b:0d
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 192.168.1.1
bound to 192.168.1.101 -- renewal in 293684 seconds.
-------------------------
* VI. querying nslookup google.com...
Server: 192.168.1.1
Address: 192.168.1.1#53

Non-authoritative answer:
Name: google.com
Address: 64.233.167.99
Name: google.com
Address: 64.233.187.99
Name: google.com
Address: 72.14.207.99
root@peter-laptop:~#

root@peter-laptop:~# lspci
00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2)
00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2)
00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2)
00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2)
00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
00:00.6 RAM memory: nVidia Corporation C51 Memory Controller 3 (rev a2)
00:00.7 RAM memory: nVidia Corporation C51 Memory Controller 2 (rev a2)
00:02.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
00:03.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
00:05.0 VGA compatible controller: nVidia Corporation C51 PCI Express Bridge (rev a2)
00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2)
00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a3)
00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a3)
00:0a.3 Co-processor: nVidia Corporation MCP51 PMU (rev a3)
00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3)
00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3)
00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev f1)
00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev f1)
00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2)
00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio (rev a2)
00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a3)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:00.0 Network controller: Broadcom Corporation Dell Wireless 1390 WLAN Mini-PCI Card (rev 02)
05:09.0 FireWire (IEEE 1394): Ricoh Co Ltd Unknown device 0832
05:09.1 Generic system peripheral [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 19)
05:09.2 System peripheral: Ricoh Co Ltd Unknown device 0843 (rev 01)
05:09.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 0a)
05:09.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 05)
root@peter-laptop:~#

================================================== ==================================

[wieman01]

bound to 192.168.1.101 -- renewal in 293684 seconds.
You should have obtained an IP address in fact. What happens if you issue:

sudo iwlist scan

route -n

ping 192.168.1.101
I think you are very close.

[richardh9936]

Could you please make a small cosmetic edit to note #1, to give the "key generation" instructions the heading "key generation"? They currently have the heading "Very Important", which they are, but two lines above, it says "go to key generation below", suggesting that there will be a heading saying "key generation".

[WhiteHorse]

Well you've got an IP and DNS. I'd say you're connected. Perhaps your system is sending the packets from the application layer to the wrong interface? Otherwise... I must cogitate.... could it be....... SATAN??????

Maybe the wlan0 should be eth1 or something like that. I can't remember how to symlink them.

[dpsf]

Hi all,

I have an Intel Pro/Wireless 3945 wireless networking card inside my
notebook, which worked using Feisty Fawn, but lost its ability to
connect to a WPA PSK network under Hardy Heron (but it would still
connect to access points without encryption). The issue turned out
to be the new iwl3945 driver (I think), which may not be really ready.
I'll wait a few months/updates on the iwl driver and give it a new
try.

==> Has anyone had success with the iwl3945 driver and encrypted/psk
access points?

Using these links you can compile and install the Feisty Fawn driver,
ipw3945, on Hardy Heron:

http://www.ubuntugeek.com/using-ipw3945-instead-iwl3945-in-hardy.html
http://james.colannino.org/downloads.html
(Awesome! Many thanks Thomer & James Colannino for the posts! And
wieman01, thanks again for your wonderful tutorial! -- now if only the
Ubuntu devs could be convinced to place this in the CD/DVD Desktop
'Examples' folder to prevent the catch-22) ;)

Not really all that complicated to DIY; just beware of message #16 on
the 1st link cited above. The author of the 2nd link says he will post
a Hardy Heron module on his web site for those who would rather just
pick up a reconfigured ipw3945.ko -- I will email mine to anyone
interested meanwhile; just send me a message.

Note too- Feisty Fawn placed the wireless under eth1, while in Hardy
Heron it's been moved to wlan0. Unless the udev rules are changed the
/etc/network/interfaces file will need adjusting accordingly. (after
compiling the module, see etc/udev/rules.d/70-persistent-net.rules),

Once I figure out how to make it work from the start on boot, get the
access permissions etc. set up correctly, and work seamlessly with
module loading, I'll post an update- right now it's all manual (had
trouble with the module loading part of the 1st link above).

Ciao,

dpsf.

[wieman01]

Could you please make a small cosmetic edit to note #1, to give the "key generation" instructions the heading "key generation"? They currently have the heading "Very Important", which they are, but two lines above, it says "go to key generation below", suggesting that there will be a heading saying "key generation".
Done. Thank you.

[RandomUsr]

OK, So I'm attempting to connect to a network via LEAP to no avail.

auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid xxxxxxxx
wpa-ap-scan 2
wpa-eap LEAP
wpa-key-mgmt IEEE8021X
wpa-identity xxx.xxxxxxx
wpa-password xxxxxxxx


I have set the key encryption to "open"
gksudo iwconfig wlan0 key open

and I'm unable to connect. Any Ideas? Using 8.04

[Quantumstate]

I am unable to associate with a Belkin F5D8230 that is cloaked. I've tried the following in interfaces (wpa_supplicant.conf seems to be depreciated):


iface wlan0 inet static
address 192.168.1.2
netmask 255.255.255.0
gateway 192.168.1.5
#wireless-essid hex
#wireless-key s:<key>
wpa-ssid hex
# 1=broadcast ESSID, 2=no broadcast
wpa-ap-scan 2
# WPA=WPA1, RSN=WPA2
wpa-proto WPA
# CCMP=AES cipher part of WPA2 standard, TKIP=TKIP cipher part of WPA1 standard.
wpa-pairwise TKIP
wpa-group TKIP
# WPA-PSK=Authentication via pre-shared key, WPA-EAP=Enterprise authentication server.
wpa-key-mgmt WPA-PSK
# Generate key: wpa_passphrase <your_essid> <your_ascii_key>
wpa-psk 85739200db1c87e1e4cb9a40bdbf427ca39955303b1af48da4 96237cc27c3eda

It associates all day if Broadcast is on, but not with it off.

The only comment dmesg or messages would have on the whole affair is:

ndiswrapper (link_pe_images:576): fixing KI_USER_SHARED_DATA address in the driver
ndiswrapper: driver netw4x64 (Intel,03/13/2008,11.5.1.15) loaded
ACPI: PCI Interrupt 0000:10:00.0[A] -> GSI 17 (level, low) -> IRQ 17
ndiswrapper: using IRQ 17
wlan0: ethernet device 00:1d:e0:74:3f:7d using NDIS driver: netw4x64, version: 0x1000f, NDIS version: 0x501, vendor: 'Intel(R) Wireless WiFi Link 4965AG Driver', 8086:4229.5.conf
wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK
...
NET: Registered protocol family 17
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
ADDRCONF(NETDEV_UP): wlan0: link is not ready

[geezerone]

Trying to get Edimax 7318UG to work but when I type 'dmesg' the following is shown on Hardy:


[ 1211.998284] wlan0: Initial auth_alg=0
[ 1211.998292] wlan0: authenticate with AP 00:1f:6c:53:50:54
[ 1212.195989] wlan0: authenticate with AP 00:1f:6c:53:50:54
[ 1212.395741] wlan0: authenticate with AP 00:1f:6c:53:50:54
[ 1212.595493] wlan0: authentication with AP 00:1f:6c:50:50:54 timed out
[ 1217.879219] wlan0: Initial auth_alg=0
[ 1217.879229] wlan0: authenticate with AP 00:1f:6c:53:50:54
[ 1218.076707] wlan0: authenticate with AP 00:1f:6c:53:50:54
[ 1218.276468] wlan0: authenticate with AP 00:1f:6c:53:50:54
[ 1218.480212] wlan0: authentication with AP 00:1f:6c:53:56:54 timed out
[ 1223.751777] wlan0: Initial auth_alg=0
[ 1223.751787] wlan0: authenticate with AP 00:1f:6c:53:50:54
[ 1223.949434] wlan0: authenticate with AP 00:1f:6c:53:50:54
[ 1224.149186] wlan0: authenticate with AP 00:1f:6c:53:50:54
[ 1224.348942] wlan0: authentication with AP 00:1f:6c:53:50:54 timed out
[ 1661.831056] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
[ 1661.831170] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 1676.968918] eth0: no IPv6 routers present
[ 1908.705009] eth0: no IPv6 routers present
I see that a bug exists though here (https://bugs.launchpad.net/ubuntu/+source/linux-backports-modules-2.6.24/+bug/190968)

Edit:

After changing Access point channel from 12 to a lower one and selecting wpa in the nm-applet window for entering a wpa2 encryption key it is now working! :)

[wieman01]

OK, I will be around for the weekend. Shoot if these problems have not been resolved yet.

[quixote]

Wieman01: Thanks a million! Your instructions just work. For me, it's a first to have manual wireless setup work!

I have a Sharp MP30, kind of old and slow by now, but I still love it. Atheros wireless chip. I run Hardy Heron. I used the "recipe" for WPA1, using dynamic IPs (dhcp), with a broadcast ssid.

There were only two things I came across that might be confusing to someone who's even more of a newbie than I am:

1) the wpa_passphrase command to get the hex equivalent is run in a terminal, at the usual command prompt. ie not as sudo. Also, if, like me you have spaces in your passphrase, put the whole thing in quotes.

2) when making a link to the startup script, as described in the first comment, it says:

sudo ln -s /etc/init.d/wireless-network.sh /etc/rcS.d/S40wireless-network
[Note: You may have to choose a boot sequence other than S40.]

To find the number that'll work for you, look at the /etc/rcS.d directory. I gave "wireless-network" a higher number than "networking" since I was guessing that the new script would be using the basic connectivity handled by "networking". "Networking" was S40 in my case, so I called it S41wireless-network. No other entry already had that number.

[lisati]

Success! After a bit of mucking around trying different combinations of settings, both in my Ubuntu boc and in my router, and trying to make sense of the output after restarting the network, it works! Goodbye to WEP.


Thanks!

[lisati]

Some users reported (including myself) that the network has to be restarted every time after startup... Apparently this is a bug.

<snip>
Thanks.....

[ar_hnazari]

:KS
You are SUPERB wieman01,,,,, I wanna hug you 'cause you solved my problem in a very pro way :)
Wish you luck
THANK YOU

[gohanssjn]

Can I just download wpa-supplicant somewhere?

My Ubuntu install has NO connection due to this issue, and I really need to get it up and working (and it cannot use a hardwire connection right now).

[ar_hnazari]

Dear wieman01
I have a little problem with the solution you expresses here.
Every time I start my Ubuntu, I have to restart networking after logon to stablish the wifi connection, I mean it doesn't connect automatically after starting linux itself.
Will you please help me?
Thanx

[zzandeamos]

I hope you can give me some direction, I seem to be going in circles. I think I have everything I need I just can't get the linkage to connect them properly. Here is the data you asked for in the front end......
What happens is I get the step icon in the upper right, when I put the cursor on it it says "wireless network connection to 2wire759 72%". Any web site/url I put in gives msg "address not found". The wired works fine and the wireless works with Puppy Linux, but I am using Ubuntu 8.04


fdc@ubfdc:~$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
localnet * 255.255.255.0 U 0 0 0 eth0
link-local * 255.255.0.0 U 1000 0 0 eth0
default home 0.0.0.0 UG 0 0 0 eth0
---------------------------------------------------------
fdc@ubfdc:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:"" Nickname:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

--------------------------------------------------------------
fdc@ubfdc:~$ sudo iwlist scan
[sudo] password for fdc:
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wmaster0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:14:95:C4:15:C1
ESSID:"2WIRE759"
Mode:Master
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=71/100 Signal level=-63 dBm Noise level=-127 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=0000000bd1e544a5
------------------------------------------------------------
fdc@ubfdc:~$ sudo lshw -C network
*-network
description: Wireless interface
product: PRO/Wireless 3945ABG Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:03:00.0
logical name: wmaster0
version: 02
serial: 00:1b:77:85:1c:48
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=iwl3945 latency=0 module=iwl3945 multicast=yes wireless=IEEE 802.11g
*-network
description: Ethernet interface
product: RTL-8110SC/8169SC Gigabit Ethernet
vendor: Realtek Semiconductor Co., Ltd.
physical id: 7
bus info: pci@0000:05:07.0
logical name: eth0
version: 10
serial: 00:1b:fc:d1:e2:f0
size: 100MB/s
capacity: 1GB/s
width: 32 bits
clock: 66MHz
capabilities: pm bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.2LK duplex=full ip=192.168.0.77 latency=64 link=yes maxlatency=64 mingnt=32 module=r8169 multicast=yes port=twisted pair speed=100MB/s
--------------------------------------------------------------------------------
fdc@ubfdc:~$ sudo cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
-------------------------------------------------------------------------------
fdc@ubfdc:~$ sudo ifdown -v 2wire759
ifdown: interface 2wire759 not configured
------------------------------------------------------------------------------
fdc@ubfdc:~$ sudo ifup -v 2wire759
Ignoring unknown interface 2wire759=2wire759.
fdc@ubfdc:~$


I would appreciate any help you can send my way. Sorry about the little faces that got in there, I don't know what caused them.

Thanks
FDC

Edit-----
Here is /etc/network/interfaces

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface




iface wlan0 inet dhcp
wpa-psk <passphrase>
wpa-driver wext
wpa-key-mgmt WPA-PSK
wpa-proto WPA
wpa-ssid 2wire759

auto wlan0

Thank you

[dpsf]

Hi zzandeamos/FDC,

Looks like your wireless is similar to mine. If you search the
forum you can find the posts in which I describe how I got my
Intel 3945 working on Ubuntu Hardy Heron. First, if you have a
CD handy, I would switch to a Feisty Fawn LiveCD and do a sanity
check-- my setup was working within 5-10 minutes in Feisty after
following wieman01's howto.

My own issues stemmed from the substitution of the new driver,
iwl3945, in HH, replacing ipw3945 in FF. Once I switched back to
the old driver, a little script juggling and I had networking
working in HH too.

Ciao,

dpsf.

[zzandeamos]

Thanks dpsf, I'll look into that today.

zzandeamos

[wieman01]

Can I just download wpa-supplicant somewhere?

My Ubuntu install has NO connection due to this issue, and I really need to get it up and working (and it cannot use a hardwire connection right now).
It is in the repositories... Just add it using Synaptic, the package manager.

[wieman01]

Dear wieman01
I have a little problem with the solution you expresses here.
Every time I start my Ubuntu, I have to restart networking after logon to stablish the wifi connection, I mean it doesn't connect automatically after starting linux itself.
Will you please help me?
Thanx
Please look at post #2 of this thread. It's a know problem and a workaround is described there.

[wieman01]

Thanks dpsf, I'll look into that today.

zzandeamos
Keep me posted. I heard that a number of people had an issue with the Intel wireless driver... so you are not alone. Let me know if you are making progess.

[lisati]

Please look at post #2 of this thread. It's a know problem and a workaround is described there.

+1: Quick link: http://ubuntuforums.org/showpost.php?p=1351902&postcount=2

[wieman01]

+1: Quick link: http://ubuntuforums.org/showpost.php?p=1351902&postcount=2
:-)

[GenesisV2.0]

woot someone who is as enthusiastic about wireless security as me

[pokipoki08]

I tried to edit /etc/network/interfaces but made a mess out of it. So, I commented everything about wlan0 and did it manually. Finally, I could get my DLink DWL-G132 working with WPA & TKIP in Hardy. Thanks.

My notes here :

Follow the link below to install ndiswrapper by source, and the wireless driver
http://ubuntuforums.org/showthread.php?t=584014&highlight=ndiswrapper+dlink

How I did it :

- using synaptic : uninstall ndisgtk, ndiswrapper (all of them), network manager (all)
- install latest ndiswrapper by source
- install dwl-g132 driver ver. 1.3 (latest driver makes a difference)

attach dwl-g132 to usb port

$ sudo ndiswrapper -i neta5agu.inf
$ sudo depmod -a
$ sudo modprobe ndiswrapper
$ sudo ndiswrapper -m
$ sudo ndiswrapper -l # observe if hardware is present

# add line "ndiswrapper" (without quotes) at end of file

$ gksudo gedit /etc/modules

# to generate 256-bit PSK for every WPA ssid, to include in /etc/wpa_supplicant.conf

$ wpa_passphrase myssid mypassword

output will be like below


network={
ssid="myssid"
#psk="mypassword"
psk=2f0568b3492812bd56b946dbaf3fd7dd669b9a4602a09a a6462ff057949b025c
}

# edit /etc/wpa_supplicant.conf


ap_scan=1
ctrl_interface=/var/run/wpa_supplicant
fast_reauth=1

network={
ssid="SSID #1"
scan_ssid=1
proto=WPA
key_mgmt=WPA-PSK
#psk="PASSWORD #1"
psk=9545080ed9e1625300943451ca809f32d5b3b8ea7e8049 6c37959da1527cfed5
pairwise=TKIP
group=TKIP
}

network={
ssid="SSID #2"
scan_ssid=1
proto=WPA
key_mgmt=WPA-PSK
#psk="PASSWORD #2"
psk=f1698a938271a4411c8fc028a7474b1a7d32ab14b42daf c8d8b1d7be7c51a26b
pairwise=TKIP
group=TKIP
}

network={
ssid="SSID #3"
scan_ssid=1
proto=WPA
key_mgmt=WPA-PSK
#psk="PASSWORD #3"
psk=8e648d6f83e9a970714a588ebc7baba9eeeddd10072974 26ce2e748239f6aab3
pairwise=TKIP
group=TKIP
}

comment/remove all scripts related to wlan0 in /etc/network/interfaces
unplug dwl-g132
unplug eth0
reboot

(not required if you remove wlan0 in /etc/network/interfaces)

$ sudo rm /var/run/wpa_supplicant/wlan0
$ sudo rm /var/run/wpa_supplicant.wlan0.pid
$ sudo ifconfig wlan0 down
$ sudo dhclient -r wlan0
$ sudo rm /var/run/dhclient.pid
$ sudo iwpriv wlan0 network_type g # if your connection keeps dropping, use a, b or g for your type of card
$ sudo ifconfig wlan0 hw ether 00:16:E5:BA:FE:82 # to change your MAC address


$ sudo ifconfig wlan0 down (the next time you reboot, continue here)


$ iwlist wlan0 scan
$ iwconfig wlan0 mode Managed
$ iwconfig wlan0 key s:PASSWORD#1 restricted # POINT A
$ iwconfig wlan0 essid 'SSID #1' # POINT B

# at this point

$ iwconfig wlan0
# check for your AP name & MAC address, repeat Point A & B until you can see them


$ sudo ifconfig wlan0 up
$ sudo wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf
$ sudo dhclient wlan0

[pokipoki08]

Does anyone know how to use iwpriv? I am getting disconnected from AP after an hour or so. dmesg shows issues with ndis_reset.


wlan0 Available private ioctls :
ndis_reset (8BF0) : set 0 & get 0
power_profile (8BF1) : set 1 int & get 0
deauthenticate (8BF3) : set 0 & get 0
network_type (8BF2) : set 1 char & get 0
media_stream (8BF4) : set 1 int & get 0
reload_defaults (8BF7) : set 0 & get 0

[SlingerXL]

route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.0.1.0 * 255.255.255.0 U 0 0 0 eth0
default girlfess.local 0.0.0.0 UG 0 0 0 eth0

iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:off/any
Mode:Managed Frequency:2.462 GHz Access Point: Not-Associated
Bit Rate:54 Mb/s Tx-Power:32 dBm
RTS thr:2347 B Fragment thr:2346 B
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

sudo iwlist scan[b/]
lo Interface doesn't sudo iwlist scan
support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:17:3F:6A:DD:99
ESSID:"houseoflove"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:35/100 Signal level:-73 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
Preauthentication Supported
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : TKIP CCMP
Authentication Suites (1) : PSK
Cell 02 - Address: 00:1B:63:2D:20:A9
ESSID:"girlfess"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:100/100 Signal level:-32 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 03 - Address: 00:1C:10:14:AB:84
ESSID:"Citgo-3"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:17/100 Signal level:-85 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 04 - Address: 00:1E:2A:53:F6:52
ESSID:"511nfess"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:7/100 Signal level:-91 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0

[b]sudo lshw -C network
*-network DISABLED
description: Wireless interface
product: BCM94311MCG wlan mini-PCI
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:03:00.0
logical name: wlan0
version: 02
serial: 00:1a:73:a6:9d:b4
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+bcmwl5 driverversion=1.52+Broadcom,10/12/2006, 4.100. latency=0 link=no module=ndiswrapper multicast=yes wireless=IEEE 802.11g

sudo cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet static
address 192.168.168.40
gateway 192.168.168.230
dns-nameservers 192.168.168.230
netmask 255.255.255.0
wpa-driver wext
wpa-ssid girlfess
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk b9dbbd5c85da38be466fbaaeba58183a6d5b3f17e5cab567ec 695f7530062cb2

sudo ifdown -v wlan0
ifdown: interface wlan0 not configured

sudo ifup -v
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan0
wpa_supplicant: wpa-ap-scan 2 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "girlfess" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise CCMP -- OK
wpa_supplicant: wpa-group CCMP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto RSN -- OK
wpa_supplicant: enabling network block 0 -- OK

ifconfig wlan0 192.168.168.40 netmask 255.255.255.0 up
route add default gw 192.168.168.230 metric 100 wlan0
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant




I have no idea what I'm doing. All I know is that I can't see the wireless networks despite seeing them with some terminal commands. What do I need to do to connect??

[wieman01]

SlingerXL:

Your adapter is disabled:

sudo lshw -C network
*-network DISABLED
Any idea why that is so?

[s1337m]

Hi, Im new to Ubuntu and am using 8.04 hardy. The instructions say to uninstall network manager, but will we ever reinstall it or are we going to be connecting from the command line from now on?

[geezerone]

I use Network Manager without any problems. What wireless device are you using?

[s1337m]

Im using the dreaded bcm43xx chipset. I can use NM to connect to unsecured/WEP, but I cant get it to connect to WPA (although it detects it). To be more specific, after we do that wpa_supplicant.conf configuration stuff, do we reinstall NM and then NM will work properly?

[geezerone]

You could try WICD which I don't use but has been found to work well with WPA networks.

Do you have the network monitor icon (2.12.1 is the latest; right-click and select about to view) added to a panel in addition to the nm-applet by any chance? I found that connecting to WPA network wouldn't work until I removed it as it clashed with the nm-applet.

[s1337m]

You could try WICD which I don't use but has been found to work well with WPA networks.

Do you have the network monitor icon (2.12.1 is the latest; right-click and select about to view) added to a panel in addition to the nm-applet by any chance? I found that connecting to WPA network wouldn't work until I removed it as it clashed with the nm-applet.


I right clicked the monitor icon on the top right and it said nm-applet 0.6.6. I was under the impression that that was the network manager program... since it is installed. I am new at ubuntu, are nm-applet and network-manager disjoint programs or do they work together?

To make my initial question clear: If we follow the instructions in this tutorial, which means disabling NM, will we ever reenable NM so that it works with our new configuration?

[geezerone]

Didn't mean to confuse but you probably haven't added any icons to the ones already installed in the pane. They nm and net manager should work together but for me with a different chipset didn't. Anyway, try WICD and see if that helps as many use it where nm fails.

[s1337m]

Didn't mean to confuse but you probably haven't added any icons to the ones already installed in the pane. They nm and net manager should work together but for me with a different chipset didn't. Anyway, try WICD and see if that helps as many use it where nm fails.

Thanks for the help so far, I tried wicd and it hangs on "Getting IP" which NM probably also hangs on... when I edit /etc/network/interfaces my NM no longer lists all the networks, so does this tutorial mean that we are no longer working with a GUI but just the command line? I hope this question makes sense, I've been trying to phrase it clearly :)

My original interface file:

sean@sean-laptop:~$ sudo cat /etc/network/interfaces
auto lo
iface lo inet loopback

If i change it to:
auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dhcp


My NetworkManager no longer lists wireless networks!


EDIT: I was surfing around and found this on the release page

Network Manager

*

In Ubuntu 8.04, network-manager only manages interfaces that are marked for roaming. Thus, all interfaces that were previously managed by network-manager will be set to roaming mode during upgrade. Technically, this takes any interface stanzas using the dhcp method with no options and that are marked auto, and removes them from /etc/network/interfaces. If you rely on your interfaces being started by ifupdown when the system starts up, you need to re-enable them in /etc/network/interfaces manually, or disable roaming in System -> Administration -> Network.


That explains why before hand my interfaces file didn't mention wlan0. But, it doesn't really tell me how to have my NM work correctly when I do mention wlan0 in that file, any tips? Thanks for having patience with me, Im new to Ubuntu

[geezerone]

I understand your frustration as I tried a problematic BT Voyager 1055 USB device which worked for a short time and then no more.

Type in a terminal and post results here.

iwconfig

lspci ( lsusb if usb wireless adapter)

ifconfig

route -n

sudo lshw -C network

When I was trying to get internet connectivity back with a wired connection after losing any network managers I manually configured the /etc/network/interfaces file with static IP, mask to allow network connectivity.

Which tutorial(s) do you refer to in your original post btw?

The following posts may be of help too:

Manually configure networking (http://ubuntuforums.org/showthread.php?t=571188)
Broadcom 4318 chipset Tutorial (http://ubuntuforums.org/showthread.php?t=197102&highlight=broadcom)

HTH :)

[quixote]

s1337m: I followed wieman01's instructions to the letter, and WPA1 works perfectly with my atheros chip. (easier than bcm43xx!) I couldn't get wicd working either.

With wieman01's system you don't have a little icon showing when you're connected -- which is the only thing I miss -- but unlike the utilities that do have the icon, you are actually connected. A good trade-off :D

Read through the first post of this thread and find the recipe that suits your purposes, and then just edit the /etc/whatever-it-was (sorry, don't remember) as he gives it in the example. Also be sure to read the first comment, where he gives more info.

On a few occasions, I've lost my connection and had to use the command line:

$sudo dhclient
That kicks the system into talking to the router again.

Hope you get things working again soon!

[wieman01]

geezerone & quixote,

Thanks for helping out. I really appreciate it. I have limited access to the internet at the moment, so it's great that you guys can share your experience. Thank you!

[EarthMind]

Is there any support for the Asus Wlan-167g USB adapter with ndiswrapper driver?

[s1337m]

Thanks for the help everyone... this method sorta works for me. Sometimes it works, sometimes it doesn't. When I booted the machine, I tried to connect and it didn't work but when I was doing the ifup command for output to show you guys it actually worked. I'd say so far about 50% of the time the restart command actually gets me connected. Anyway, here is some output... I tried connecting my wlan0 but that didnt work so I went to my eth0 ethernet


sean@sean-laptop:~$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 wlan0
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
0.0.0.0 0.0.0.0 0.0.0.0 U 1000 0 0 wlan0



sean@sean-laptop:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:"domo"
Mode:Managed Frequency:2.412 GHz Access Point: 00:13:10:04:E0:A0
Bit Rate=54 Mb/s Tx-Power:32 dBm
RTS thr:2347 B Fragment thr:2346 B
Power Management:off
Link Quality:73/100 Signal level:-49 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0



sean@sean-laptop:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:15:c5:4a:16:69
inet addr:192.168.1.103 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::215:c5ff:fe4a:1669/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9732 errors:0 dropped:0 overruns:0 frame:0
TX packets:9013 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:8971409 (8.5 MB) TX bytes:1398631 (1.3 MB)
Interrupt:17

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1486 errors:0 dropped:0 overruns:0 frame:0
TX packets:1486 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:75300 (73.5 KB) TX bytes:75300 (73.5 KB)

wlan0 Link encap:Ethernet HWaddr 00:16:cf:3d:0d:69
inet6 addr: fe80::216:cfff:fe3d:d69/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:193 errors:0 dropped:0 overruns:0 frame:0
TX packets:347 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:24033 (23.4 KB) TX bytes:43552 (42.5 KB)
Interrupt:17 Memory:dfcfc000-dfd00000

wlan0:avahi Link encap:Ethernet HWaddr 00:16:cf:3d:0d:69
inet addr:169.254.4.173 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:17 Memory:dfcfc000-dfd00000




sean@sean-laptop:~$ sudo iwlist scan
[sudo] password for sean:
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:13:10:04:E0:A0
ESSID:"domo"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:76/100 Signal level:-47 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 02 - Address: 00:18:39:76:30:BB
ESSID:"Golf Linksys"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:23/100 Signal level:-81 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 03 - Address: 00:18:39:FD:84:13
ESSID:"linksys"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:26/100 Signal level:-79 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 04 - Address: 00:18:F8:B5:BF:9D
ESSID:"linksys"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:14/100 Signal level:-87 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 05 - Address: 00:12:88:36:52:E1
ESSID:"2WIRE006"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.447 GHz (Channel 8)
Quality:25/100 Signal level:-80 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0



sean@sean-laptop:~$ lspci
00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03)
00:01.0 PCI bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express PCI Express Root Port (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 01)
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 01)
00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 01)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 01)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 01)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 01)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 01)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e1)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 01)
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller (rev 01)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01)
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility X1400
03:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)
03:01.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller
03:01.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 19)
03:01.2 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev 0a)
03:01.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 05)
03:01.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev ff)
0c:00.0 Network controller: Broadcom Corporation BCM4328 802.11a/b/g/n (rev 01)



sean@sean-laptop:~$ lshw -C network
WARNING: you should run this program as super-user.
PCI (sysfs)
*-network
description: Wireless interface
product: BCM4328 802.11a/b/g/n
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:0c:00.0
logical name: wlan0
version: 01
serial: 00:16:cf:3d:0d:69
width: 64 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+bcmwl5 driverversion=1.52+Broadcom,10/12/2006, 4.100. latency=0 module=ndiswrapper multicast=yes wireless=IEEE 802.11g
*-network
description: Ethernet interface
product: BCM4401-B0 100Base-TX
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:03:00.0
logical name: eth0
version: 02
serial: 00:15:c5:4a:16:69
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=b44 driverversion=2.0 ip=192.168.1.103 latency=64 module=ssb multicast=yes
sean@sean-laptop:~$



sean@sean-laptop:~$ sudo cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid domo
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk cd5f01722fe4d1c65779cdbcc7edd78f8b3dd9b18253fda827 cc7dd8623aa81d




sean@sean-laptop:~$ sudo ifdown -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:16:cf:3d:0d:69
Sending on LPF/wlan0/00:16:cf:3d:0d:69
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 192.168.1.1 port 67
ifconfig wlan0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan0.pid
Stopped /sbin/wpa_supplicant (pid 6658).



sean@sean-laptop:~$ sudo ifup -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan0
wpa_supplicant: wpa-ap-scan 1 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "domo" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise TKIP -- OK
wpa_supplicant: wpa-group TKIP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto WPA -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:16:cf:3d:0d:69
Sending on LPF/wlan0/00:16:cf:3d:0d:69
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
DHCPOFFER of 192.168.1.106 from 192.168.1.1
DHCPREQUEST of 192.168.1.106 on wlan0 to 255.255.255.255 port 67
DHCPACK of 192.168.1.106 from 192.168.1.1
bound to 192.168.1.106 -- renewal in 36981 seconds.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant

[wieman01]

s1337m,

Two things I could think of:

1. USB power supply isn't sufficient. Please post the output of "dmesg" after connection issues have occurred.
2. Issue as described in post #2 of this thread.

[wieman01]

Is there any support for the Asus Wlan-167g USB adapter with ndiswrapper driver?
You could check here:

http://ndiswrapper.sourceforge.net/joomla/index.php?/component/option,com_openwiki/Itemid,33/id,list/

[s1337m]

s1337m,

Two things I could think of:

1. USB power supply isn't sufficient. Please post the output of "dmesg" after connection issues have occurred.
2. Issue as described in post #2 of this thread.


I have linked the script to start at boot, (the issue in post #2) and the same thing occurs -- I get a no DCHPOffers received, going to sleep. I kept doing ifup/ifdown til it got a DCHPoffer, so im on the wireless right now. anyway, heres output from dmesg:


sean@sean-laptop:~$ dmesg | grep bcm
[ 23.592693] ndiswrapper: driver bcmwl5 (Broadcom,10/12/2006, 4.100.15.5) loaded
[ 23.649135] wlan0: ethernet device 00:16:cf:3d:0d:69 using NDIS driver: bcmwl5, version: 0x4640f05, NDIS version: 0x501, vendor: 'NDIS Network Adapter', 14E4:4328.5.conf

[geezerone]

I know how much of a pain this can be as happened with a bcm device I tried to get working.

Have you tried static IP to avoid DHCP failing? Is this PCI device and is antenna in good location as my USB needs to be on extension lead to work even though a 'good' signal is obtained?

This page (http://bcm43xx.berlios.de/) and links from it may be of some use re: BCM


geezerone & quixote,

Thanks for helping out. I really appreciate it. I have limited access to the internet at the moment, so it's great that you guys can share your experience. Thank you!

Glad to help - that is what is great about this community!!!! :)

[s1337m]

I know how much of a pain this can be as happened with a bcm device I tried to get working.

Have you tried static IP to avoid DHCP failing? Is this PCI device and is antenna in good location as my USB needs to be on extension lead to work even though a 'good' signal is obtained?

This page (http://bcm43xx.berlios.de/) and links from it may be of some use re: BCM



Glad to help - that is what is great about this community!!!! :)


Thanks for the help, I havent tried static IP since Im renting a room in someone else's place and they dont want me to mess with the settings... I guess Ill write a script that loops ifdown/ifup until I get a DHCP offer accepted

[geezerone]

Thanks for the help, I havent tried static IP since Im renting a room in someone else's place and they dont want me to mess with the settings... I guess Ill write a script that loops ifdown/ifup until I get a DHCP offer accepted

They could limit the range of DHCP and leave you at least one address or just select a high IP address (ping this address when everyone is connected to see if in use).

[Monarch2007]

I have followed your tutorial and a few other tutorials on this subject. Thank you for your time and patience coming up with such informative material.
However, I am having a problem here for which I seem to be getting nowhere. I have Ubuntu 8.04 on a Dell 620 laptop. I have Intel 3945 Wireless card. When I use the laptop at home, I have no problem getting the wireless connection up. However, in office we have the wireless LAN network configured with LEAP with user ID and password authentication. I tried using the native iwl3945 as well as the ndiswrapper drivers (used wpa_supplicant as well as xsupplicant) but couldnt get the wireless LAN up. All the time the authentication seems to be failing with messages such as "...privacy mismatch...". Can some one please help? Or is it a known problem that I can't use LEAP authentication at all? Or should I be using a special driver? (in fact, for the ndiswrapper, I used the same driver in the XP partition that is working fine under Windows). I really appreciate any guidance in this regard.

Thanks.

[wieman01]

I have followed your tutorial and a few other tutorials on this subject. Thank you for your time and patience coming up with such informative material.
However, I am having a problem here for which I seem to be getting nowhere. I have Ubuntu 8.04 on a Dell 620 laptop. I have Intel 3945 Wireless card. When I use the laptop at home, I have no problem getting the wireless connection up. However, in office we have the wireless LAN network configured with LEAP with user ID and password authentication. I tried using the native iwl3945 as well as the ndiswrapper drivers (used wpa_supplicant as well as xsupplicant) but couldnt get the wireless LAN up. All the time the authentication seems to be failing with messages such as "...privacy mismatch...". Can some one please help? Or is it a known problem that I can't use LEAP authentication at all? Or should I be using a special driver? (in fact, for the ndiswrapper, I used the same driver in the XP partition that is working fine under Windows). I really appreciate any guidance in this regard.

Thanks.
OK, please post what is under section "Post this if you are stumped"... Then we'll see.

[galbers]

I'm currently stumped. I have had this working previously (although somewhat intermittently) but I have just upgraded to 8.04 and cannot get wireless to work with WPA. Below is my output, any help is greatly appreciated:



dave@rosa:/etc/network$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan1
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 wlan1
0.0.0.0 192.168.0.1 0.0.0.0 UG 100 0 0 wlan1





dave@rosa:/etc/network$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan1 IEEE 802.11g ESSID:"vince-galbraith"
Mode:Managed Frequency:2.417 GHz Access Point: 00:18:4D:F1:35:2C
Bit Rate=54 Mb/s Tx-Power:20 dBm Sensitivity=0/3
RTS thr:off Fragment thr:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0






dave@rosa:/etc/network$ sudo iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan1 Scan completed :
Cell 01 - Address: 00:11:50:9D:20:04
ESSID:"Belkin54g"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:37/100 Signal level:-72 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 02 - Address: 00:11:50:B9:A9:3A
ESSID:""
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:37/100 Signal level:-72 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 03 - Address: 00:18:4D:F1:35:2C
ESSID:"vince-galbraith"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.417 GHz (Channel 2)
Quality:39/100 Signal level:-71 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 04 - Address: 00:19:E0:A1:2D:72
ESSID:"XeonAV"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:37/100 Signal level:-72 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK






dave@rosa:/etc/network$ sudo lshw -C network
*-network
description: Ethernet interface
product: VT6102 [Rhine-II]
vendor: VIA Technologies, Inc.
physical id: 12
bus info: pci@0000:00:12.0
logical name: eth0
version: 74
serial: 00:30:18:01:31:3c
size: 10MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=via-rhine driverversion=1.4.3 duplex=half latency=32 link=no maxlatency=8 mingnt=3 module=via_rhine multicast=yes port=MII speed=10MB/s
*-network
description: Wireless interface
physical id: 1
logical name: wlan1
serial: 00:18:4d:aa:f6:05
capabilities: ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+net111v2 driverversion=1.53+NETGEAR Inc.,3/16/2006,5.12 ip=192.168.0.3 link=no multicast=yes wireless=IEEE 802.11g




dave@rosa:/etc/network$ sudo cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto wlan1
iface wlan1 inet static
address 192.168.0.3
gateway 192.168.0.1
dns-nameservers 62.24.199.13
netmask 255.255.255.0
broadcast 255.255.255.255
wpa-driver wext
wpa-ssid vince-galbraith
wpa-ap-scan 1
wpa-proto WPA RSN
wpa-pairwise TKIP CCMP
wpa-group TKIP CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 47029f5e65c33124b592d010e4b309fb54cae858f822a99a91 a2f6edd8c3d35d





dave@rosa:/etc/network$ sudo ifdown -v wlan1
Configuring interface wlan1=wlan1 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/wpasupplicant
route del default gw 192.168.0.1 metric 100 wlan1
ifconfig wlan1 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan1.pid
Stopped /sbin/wpa_supplicant (pid 6719).




dave@rosa:/etc/network$ sudo ifup -v wlan1
Configuring interface wlan1=wlan1 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan1.pid -i wlan1 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan1
wpa_supplicant: wpa-ap-scan 1 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "vince-galbraith" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise TKIP CCMP -- OK
wpa_supplicant: wpa-group TKIP CCMP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto WPA RSN -- OK
wpa_supplicant: enabling network block 0 -- OK

ifconfig wlan1 192.168.0.3 netmask 255.255.255.0 broadcast 255.255.255.255 up
route add default gw 192.168.0.1 metric 100 wlan1
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant

description: Wireless interface
physical id: 1
logical name: wlan1
serial: 00:18:4d:aa:f6:05
capabilities: ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+net111v2 driverversion=1.53+NETGEAR Inc.,3/16/2006,5.12 ip=192.168.0.3 link=no multicast=yes wireless=IEEE 802.11g

[cantseejack]

New to Ubuntu, just installed it on a Thinkpad T61 with Intel Pro Wireless 3945. Worked like a charm; all other attempts/avenues were stressing me out. Thanks for the writeup!

[Monarch2007]

Apologies since I couldnt get access to my wlan at office during the weekend. Here are the logs.
I will first start with the native driver, iwl3945 since that seems to be working at my home. Also, I will attach wpa_supplicant results. I can surely run the ndiswrapper and xsupplicant tests if you want me to. Please let me know.

root@MY_LAPTOP-01:~# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.232.176.0 0.0.0.0 255.255.248.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth0
0.0.0.0 10.232.176.1 0.0.0.0 UG 100 0 0 eth0
root@MY_LAPTOP-01:~#



root@MY_LAPTOP-01:~# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:"" Nickname:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0



root@MY_LAPTOP-01:~# iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wmaster0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:15:FA:B3:2D:50
ESSID:""
Mode:Master
Channel:3
Frequency:2.422 GHz (Channel 3)
Quality=76/100 Signal level=-58 dBm Noise level=-127 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=0000009b2db0c58f


root@MY_LAPTOP-01:~# lshw -C network
*-network
description: Wireless interface
product: PRO/Wireless 3945ABG Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:0c:00.0
logical name: wmaster0
version: 02
serial: 00:1b:77:2d:c4:ae
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=iwl3945 latency=0 module=iwl3945 multicast=yes wireless=IEEE 802.11g
*-network
description: Ethernet interface
product: NetXtreme BCM5752 Gigabit Ethernet PCI Express
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:09:00.0
logical name: eth0
version: 02
serial: 00:18:8b:d0:97:bd
size: 100MB/s
capacity: 1GB/s
width: 64 bits
clock: 33MHz
capabilities: pm vpd msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=tg3 driverversion=3.86 duplex=full firmware=5752-v3.19 ip=10.232.176.83 latency=0 link=yes module=tg3 multicast=yes port=twisted pair speed=100MB/s
root@MY_LAPTOP-01:~#

root@MY_LAPTOP-01:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0



iface eth0 inet dhcp

auto eth0

iface wlan0 inet dhcp

auto wlan0

root@MY_LAPTOP-01:~# ifconfig wlan0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant


root@MY_LAPTOP-01:/etc# cat wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
update_config=1
ap_scan=1
network={
ssid="wlan_ap"
scan_ssid=1
key_mgmt=IEEE8021X
eap=LEAP
identity="my_domain\xxx"
password="yyyy"
}



root@MY_LAPTOP-01:/etc# wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -dd
Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
update_config=1
ap_scan=1
Line: 4 - start of a new network block
ssid - hexdump_ascii:
wlan_ap
scan_ssid=1 (0x1)
key_mgmt: 0x8
eap methods - hexdump(len=16): 00 00 00 00 11 00 00 00 00 00 00 00 00 00 00 00
identity - hexdump_ascii:
my_doamin\my_login
password - hexdump_ascii(len=8): [REMOVED]
Priority group 0
id=0 ssid='wlan_ap'
Initializing interface (2) 'wlan0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0xf
capabilities: key_mgmt 0xf enc 0xf
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:1b:77:2d:c4:ae
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
Setting scan request: 0 sec 100000 usec
Added interface wlan0
RTM_NEWLINK: operstate=0 ifi_flags=0x1002 ()
Wireless event: cmd=0x8b06 len=8
Ignore event for foreign ifindex 3
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
State: DISCONNECTED -> SCANNING
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii
wlan_ap
Trying to get current scan results first without requesting a new scan to speed up initial association
Received 0 bytes of scan results (0 BSSes)
Scan results: 0
Selecting BSS from priority group 0
Try to find WPA-enabled AP
Try to find non-WPA AP
No suitable AP found.
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b19 len=8
Received 205 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:15:fa:b3:2d:50 ssid='' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - no WPA/RSN IE
Try to find non-WPA AP
0: 00:15:fa:b3:2d:50 ssid='' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - SSID mismatch
No suitable AP found.
Setting scan request: 5 sec 0 usec
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii
wlan_ap
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b19 len=8
Received 213 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:15:fa:b3:2d:50 ssid='wlan_ap' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - no WPA/RSN IE
Try to find non-WPA AP
0: 00:15:fa:b3:2d:50 ssid='wlan_ap' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
selected non-WPA AP 00:15:fa:b3:2d:50 ssid='wlan_ap'
Trying to associate with 00:15:fa:b3:2d:50 (SSID='wlan_ap' freq=2422 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x4
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: clearing own WPA/RSN IE
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - portControl=Auto
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b04 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b1a len=17
Authentication with 00:00:00:00:00:00 timed out.
Added BSSID 00:15:fa:b3:2d:50 into blacklist
No keys have been configured - skip key clearing
State: ASSOCIATING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b19 len=8
Received 213 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:15:fa:b3:2d:50 ssid='wlan_ap' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - no WPA/RSN IE
Try to find non-WPA AP
0: 00:15:fa:b3:2d:50 ssid='wlan_ap' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
selected non-WPA AP 00:15:fa:b3:2d:50 ssid='wlan_ap'
Trying to associate with 00:15:fa:b3:2d:50 (SSID='wlan_ap' freq=2422 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x4
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: clearing own WPA/RSN IE
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - portControl=Auto
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b04 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b1a len=17
CTRL_IFACE monitor attached - hexdump(len=22): 2f 74 6d 70 2f 77 70 61 5f 63 74 72 6c 5f 31 31 35 36 32 2d 31 00
RX ctrl_iface - hexdump_ascii(len=10):
49 4e 54 45 52 46 41 43 45 53 INTERFACES
RX ctrl_iface - hexdump_ascii(len=6):
53 54 41 54 55 53 STATUS
ioctl[SIOCGIFADDR]: Cannot assign requested address
RX ctrl_iface - hexdump_ascii(len=13):
4c 49 53 54 5f 4e 45 54 57 4f 52 4b 53 LIST_NETWORKS
RX ctrl_iface - hexdump_ascii(len=4):
50 49 4e 47 PING
Authentication with 00:00:00:00:00:00 timed out.
CTRL_IFACE monitor send - hexdump(len=22): 2f 74 6d 70 2f 77 70 61 5f 63 74 72 6c 5f 31 31 35 36 32 2d 31 00
BSSID 00:15:fa:b3:2d:50 blacklist count incremented to 2
No keys have been configured - skip key clearing
State: ASSOCIATING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii
wlan_ap
RX ctrl_iface - hexdump_ascii(len=4):
50 49 4e 47 PING
RX ctrl_iface - hexdump_ascii(len=6):
53 54 41 54 55 53 STATUS
ioctl[SIOCGIFADDR]: Cannot assign requested address
RX ctrl_iface - hexdump_ascii(len=13):
4c 49 53 54 5f 4e 45 54 57 4f 52 4b 53 LIST_NETWORKS
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b19 len=8
Received 213 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:15:fa:b3:2d:50 ssid='wlan_ap' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - blacklisted
Try to find non-WPA AP
0: 00:15:fa:b3:2d:50 ssid='wlan_ap' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - blacklisted
No APs found - clear blacklist and try again
Removed BSSID 00:15:fa:b3:2d:50 from blacklist (clear)
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:15:fa:b3:2d:50 ssid='wlan_ap' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - no WPA/RSN IE
Try to find non-WPA AP
0: 00:15:fa:b3:2d:50 ssid='wlan_ap' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
selected non-WPA AP 00:15:fa:b3:2d:50 ssid='wlan_ap'
Trying to associate with 00:15:fa:b3:2d:50 (SSID='wlan_ap' freq=2422 MHz)
CTRL_IFACE monitor send - hexdump(len=22): 2f 74 6d 70 2f 77 70 61 5f 63 74 72 6c 5f 31 31 35 36 32 2d 31 00
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x4
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: clearing own WPA/RSN IE
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - portControl=Auto
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b04 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b1a len=17
RX ctrl_iface - hexdump_ascii(len=4):
50 49 4e 47 PING
RX ctrl_iface - hexdump_ascii(len=6):
53 54 41 54 55 53 STATUS
ioctl[SIOCGIFADDR]: Cannot assign requested address
RX ctrl_iface - hexdump_ascii(len=13):
4c 49 53 54 5f 4e 45 54 57 4f 52 4b 53 LIST_NETWORKS
RX ctrl_iface - hexdump_ascii(len=4):
50 49 4e 47 PING
RX ctrl_iface - hexdump_ascii(len=4):
50 49 4e 47 PING
RX ctrl_iface - hexdump_ascii(len=4):
50 49 4e 47 PING
RX ctrl_iface - hexdump_ascii(len=4):
50 49 4e 47 PING
RX ctrl_iface - hexdump_ascii(len=4):
50 49 4e 47 PING
RX ctrl_iface - hexdump_ascii(len=4):
50 49 4e 47 PING
RX ctrl_iface - hexdump_ascii(len=4):
50 49 4e 47 PING
RX ctrl_iface - hexdump_ascii(len=4):
50 49 4e 47 PING
RX ctrl_iface - hexdump_ascii(len=4):
50 49 4e 47 PING
CTRL_IFACE monitor detached - hexdump(len=22): 2f 74 6d 70 2f 77 70 61 5f 63 74 72 6c 5f 31 31 35 36 32 2d 31 00
Authentication with 00:00:00:00:00:00 timed out.
Added BSSID 00:15:fa:b3:2d:50 into blacklist
No keys have been configured - skip key clearing
State: ASSOCIATING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b19 len=8
Received 213 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:15:fa:b3:2d:50 ssid='wlan_ap' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - no WPA/RSN IE
Try to find non-WPA AP
0: 00:15:fa:b3:2d:50 ssid='wlan_ap' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
selected non-WPA AP 00:15:fa:b3:2d:50 ssid='wlan_ap'
Trying to associate with 00:15:fa:b3:2d:50 (SSID='wlan_ap' freq=2422 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x4
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: clearing own WPA/RSN IE
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - portControl=Auto
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b04 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b1a len=17
CTRL-EVENT-TERMINATING - signal 2 received
Removing interface wlan0
State: ASSOCIATING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
wpa_driver_wext_set_wpa
wpa_driver_wext_set_drop_unencrypted
wpa_driver_wext_set_countermeasures
No keys have been configured - skip key clearing
Removed BSSID 00:15:fa:b3:2d:50 from blacklist (clear)
Cancelling scan request
Cancelling authentication timeout
WEXT: Operstate: linkmode=0, operstate=6




root@MY_LAPTOP-01:~$ dmesg
[ 1024.250583] wlan0: Initial auth_alg=128
[ 1024.250591] wlan0: authenticate with AP 00:15:fa:b3:2d:50
[ 1024.250614] wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
[ 1024.251565] wlan0: RX authentication from 00:15:fa:b3:2d:50 (alg=128 transaction=2 status=0)
[ 1024.251569] wlan0: authenticated
[ 1024.251571] wlan0: associate with AP 00:15:fa:b3:2d:50
[ 1024.251574] wlan0: mismatch in privacy configuration and mixed-cell disabled - abort association
[ 1024.252420] wlan0: RX deauthentication from 00:15:fa:b3:2d:50 (reason=2)
[ 1024.252422] wlan0: deauthenticated
[ 1026.719104] wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
[ 1024.454061] wlan0: RX deauthentication from 00:15:fa:b3:2d:50 (reason=2)
[ 1037.859670] wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
[ 1037.861816] wlan0: RX deauthentication from 00:15:fa:b3:2d:50 (reason=2)
[ 1037.862490] wlan0: Initial auth_alg=128
[ 1037.862494] wlan0: authenticate with AP 00:15:fa:b3:2d:50
[ 1037.862510] wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
[ 1037.863437] wlan0: authenticated
[ 1037.863439] wlan0: associate with AP 00:15:fa:b3:2d:50
[ 1037.863442] wlan0: mismatch in privacy configuration and mixed-cell disabled - abort association
[ 1037.864809] wlan0: RX deauthentication from 00:15:fa:b3:2d:50 (reason=2)
[ 1037.864812] wlan0: deauthenticated
[ 1035.795540] wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
[ 1035.796444] wlan0: RX deauthentication from 00:15:fa:b3:2d:50 (reason=2)
[ 1049.205114] wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
[ 1049.207906] wlan0: RX deauthentication from 00:15:fa:b3:2d:50 (reason=2)
[ 1049.210887] wlan0: Initial auth_alg=128
[ 1049.210893] wlan0: authenticate with AP 00:15:fa:b3:2d:50
[ 1049.210911] wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
[ 1049.211842] wlan0: RX authentication from 00:15:fa:b3:2d:50 (alg=128 transaction=2 status=0)
[ 1049.211845] wlan0: authenticated
[ 1049.211847] wlan0: associate with AP 00:15:fa:b3:2d:50
[ 1049.211849] wlan0: mismatch in privacy configuration and mixed-cell disabled - abort association
[ 1049.212748] wlan0: RX deauthentication from 00:15:fa:b3:2d:50 (reason=2)
[ 1049.212750] wlan0: deauthenticated
[ 1047.144928] wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
[ 1047.145844] wlan0: RX deauthentication from 00:15:fa:b3:2d:50 (reason=2)

[Monarch2007]

Here are the results with configuration changes applied to /etc/network/interfaces instead of running wpa_supplicant. Please let me know if any other logs are useful. Once again, I appreciate your time and effort on this. Thanks,




auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0



iface eth0 inet dhcp

auto eth0

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid wlan_ap
wpa-ap-scan 1
wpa-eap LEAP
wpa-key-mgmt IEEE8021X
wpa-identity "my_domain\\xxxxx"
wpa-password "xxxx"


Here is the dmesg output with grep on iwl3945:


[ 30.155868] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.0
[ 30.155872] iwl3945: Copyright(c) 2003-2007 Intel Corporation
[ 30.156062] iwl3945: Detected Intel PRO/Wireless 3945ABG Network Connection
[ 29.108716] iwl3945: Tunable channels: 13 802.11bg, 4 802.11a channels
[ 29.132041] wmaster0: Selected rate control algorithm 'iwl-3945-rs'


Here is the output of iwconfig:

lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:"" Nickname:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

[GuruCesc]

Hello All,
I'm having problems with my wireless ever since I migrated to 8.04. My wireless used to work perfectly with 6.10.

It will just not connect. If I use the Network Manager or any other GUI (I have tried WICD, NM, and KnetworkManager) it just asks for the WPA passphrase, tries to connect but it does not accept it.

If I try to configure manually as of this post, it doesn't get any response from the DHCP.

Notice that I used to connect to this very router on 6.10 and I still connect to this router using a different laptop.

See below the results of the commands:


root@marilu-laptop:/home/marilu# route
Tabla de rutas IP del núcleo
Destino Pasarela Genmask Indic Métric Ref Uso Interfaz
link-local * 255.255.0.0 U 0 0 0 wlan0
default * 0.0.0.0 U 1000 0 0 wlan0

root@marilu-laptop:/home/marilu# route -n
Tabla de rutas IP del núcleo
Destino Pasarela Genmask Indic Métric Ref Uso Interfaz
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 wlan0
0.0.0.0 0.0.0.0 0.0.0.0 U 1000 0 0 wlan0




root@marilu-laptop:/home/marilu# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

irda0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:off/any
Mode:Managed Frequency:2.462 GHz Access Point: Not-Associated
Bit Rate:1 Mb/s Sensitivity=-200 dBm
RTS thr=2346 B Fragment thr=2346 B
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0



Notice that "GuruNet" is the network I'm trying to connect!!


root@marilu-laptop:/home/marilu# iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

irda0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:1E:C7:BA:0B:E9
ESSID:"INFINITUM8662"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.457 GHz (Channel 10)
Quality:15/100 Signal level:-86 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 02 - Address: 00:1F:B3:55:FD:21
ESSID:"GuruNet"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:65/100 Signal level:-54 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK





root@marilu-laptop:/home/marilu# lshw -C network
*-network
description: 88W8300 802.11b Cardbus PC Card
product: 83
vendor: Marvell Semiconductor
physical id: 0
version: 01
slot: Socket 1
resources: irq:11
*-network
description: Ethernet interface
product: 3c556B CardBus [Tornado]
vendor: 3Com Corporation
physical id: 3
bus info: pci@0000:00:03.0
logical name: eth0
version: 20
serial: 00:00:86:4c:08:e1
size: 10MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=3c59x duplex=half latency=80 link=no maxlatency=10 mingnt=10 module=3c59x multicast=yes port=MII speed=10MB/s
*-network
description: Wireless interface
product: 88w8335 [Libertas] 802.11b/g Wireless
vendor: Marvell Technology Group Ltd.
physical id: 1
bus info: pci@0000:06:00.0
logical name: wlan0
version: 03
serial: 00:1b:2f:28:a6:82
width: 32 bits
clock: 66MHz
capabilities: pm bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+wg511v2 driverversion=1.52+NETGEAR,02/22/2005,3.1.1.7 latency=64 link=no module=ndiswrapper multicast=yes wireless=IEEE 802.11g



I have tried as wpa-driver "ndiswrapper" and wext.
I have tried as wpa-ssid "GuruNet" and "GURUNET"


root@marilu-laptop:/home/marilu# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid GURUNET
wpa-ap-scan 1
wpa-proto WPA RSN
wpa-pairwise TKIP CCMP
wpa-group TKIP CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 382a60783668193e4c55eedc95d30ce7c04a146e67c3150d3d 73b61c03e69f22





root@marilu-laptop:/home/marilu# ifdown -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 7035
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:1b:2f:28:a6:82
Sending on LPF/wlan0/00:1b:2f:28:a6:82
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 192.168.1.254 port 67
ifconfig wlan0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan0.pid
Stopped /sbin/wpa_supplicant (pid 6961).


Notice that the DHCP doesn't receive any offers! :(


root@marilu-laptop:/home/marilu# ifup -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan0
wpa_supplicant: wpa-ap-scan 1 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "GURUNET" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise TKIP CCMP -- OK
wpa_supplicant: wpa-group TKIP CCMP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto WPA RSN -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:1b:2f:28:a6:82
Sending on LPF/wlan0/00:1b:2f:28:a6:82
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant



I'm so tired now, I would REALLY like to fix this. I do not have any problems with the wired network, but I want it wireless!!!

[wieman01]

Monarch2007,

Does the IPW3945 support LEAP at all?

You could also try WICD:

http://wicd.sourceforge.net/

[NumerataNero]

Hi, now I'm confused. I followed the steps in your other posting 'HOWTO: RT2500, etc wireless cards'. Great to follow.
At the end I'm able to see my own router with iwlist scan. Great.
I aslo see that the ndiswrapper is used with lshw -C network.

However, at bullet nr 6 Ralink drivers do not support this approach:



6. RTxxx (Ralink) drivers do not support this approach. Either install "ndiswrapper" replacing Serialmonkey's driver or visit this site (http://rt2x00.serialmonkey.com/phpBB2/viewtopic.php?p=21546&sid=c5e02ed97dde07681fb564639e9f50c5).


and further down



wpa-driver:
That's the wpa-driver for your card ('wext' is a generic driver that is applicable when using "ndiswrapper"). Leave it as it is.


So can I use this approach to get me connected with the wireless internet (WPA)???:confused:

I've a LinkSys pci card, i've added rt61 and rt61pci to the blacklist.

thanks for the great support. (A newby)
Rob

[Monarch2007]

Sure, I will try WiCD and let you know. Also, do you think it would be useful to debug with ndiswrapper? If so, I will get some logs using ndiswrapper.
Thanks.

[Ziggy8.04]

hi im new to ubuntu.i have been using ubuntu hardy for
about a week, so i have no idea of the commands in terminal
and what to do in general. i have not been able to conect
to a secure wireless network, i can conect to an unsecure
network, but i want my network to be secure at home.
i use wrt160 router, with ssid broadcast disabled, and
wpa2for security.
i hope you can help. this is the info i can give you



ubuntu@ubuntu:~$ route



Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface


ubuntu@ubuntu:~$ iwconfig



lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:off/any
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Bit Rate:130 Mb/s Tx-Power:32 dBm
RTS thr:2347 B Fragment thr:2346 B
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

sudo iwlist scan


[sudo] password for ubuntu:
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:1C:10:28:73:20
ESSID:"Tigress74"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:71/100 Signal level:-50 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK

sudo lshw -C network

*-network
description: Wireless interface
product: BCM4328 802.11a/b/g/n
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:03:00.0
logical name: wlan0
version: 03
serial: 00:1a:73:ff:50:58
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+bcmwl5 driverversion=1.52+Broadcom,10/12/2006, 4.100. latency=0 link=no module=ndiswrapper multicast=yes wireless=IEEE 802.11g


sudo cat /etc/network/interfaces



auto lo
iface lo inet loopback



iface wlan0 inet dhcp
wpa-psk b57bb5ed4ff49cb4ea629840c4ea4522d5344200e30fa22583 defbf8a66c8410
wpa-driver wext
wpa-key-mgmt WPA-PSK
wpa-proto WPA2
wpa-ssid 0987654321

auto wlan0


sudo ifdown -v wlan0



Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 9581
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:1a:73:ff:50:58
Sending on LPF/wlan0/00:1a:73:ff:50:58
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 192.168.2.1 port 67
ifconfig wlan0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan0.pid
Stopped /sbin/wpa_supplicant (pid 9418).


sudo ifup -v wlan0



Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan0
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "0987654321" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto WPA2 -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 0
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:1a:73:ff:50:58
Sending on LPF/wlan0/00:1a:73:ff:50:58
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant

[lisati]

hi im new to ubuntu.i have been using ubuntu hardy for
about a week, so i have no idea of the commands in terminal
and what to do in general. i have not been able to conect
to a secure wireless network, i can conect to an unsecure
network, but i want my network to be secure at home.
i use wrt160 router, with ssid broadcast disabled, and
wpa2for security.
i hope you can help. this is the info i can give you
<snip>

Please read http://ubuntuforums.org/showpost.php?p=1884950&postcount=2 and try again

[Ziggy8.04]

hi im new to ubuntu.i have been using ubuntu hardy for
about a week, so i have no idea of the commands in terminal
and what to do in general. i have not been able to conect
to a secure wireless network, i can conect to an unsecure
network, but i want my network to be secure at home.
i use wrt160 router, with ssid broadcast disabled, and
wpa2for security.
i hope you can help. this is the info i can give you


route


Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface


iwconfig


lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:off/any
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Bit Rate:130 Mb/s Tx-Power:32 dBm
RTS thr:2347 B Fragment thr:2346 B
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


sudo iwlist scan



[sudo] password for ubuntu:
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:1C:10:28:73:20
ESSID:"Tigress74"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:71/100 Signal level:-50 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK


sudo lshw -C network


*-network
description: Wireless interface
product: BCM4328 802.11a/b/g/n
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:03:00.0
logical name: wlan0
version: 03
serial: 00:1a:73:ff:50:58
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+bcmwl5 driverversion=1.52+Broadcom,10/12/2006, 4.100. latency=0 link=no module=ndiswrapper multicast=yes wireless=IEEE 802.11g


sudo cat /etc/network/interfaces


auto lo
iface lo inet loopback



iface wlan0 inet dhcp
wpa-psk b57bb5ed4ff49cb4ea629840c4ea4522d5344200e30fa22583 defbf8a66c8410
wpa-driver wext
wpa-key-mgmt WPA-PSK
wpa-proto WPA2
wpa-ssid 0987654321

auto wlan0


sudo ifdown -v wlan0


Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 9581
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:1a:73:ff:50:58
Sending on LPF/wlan0/00:1a:73:ff:50:58
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 192.168.2.1 port 67
ifconfig wlan0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan0.pid
Stopped /sbin/wpa_supplicant (pid 9418).


sudo ifup -v wlan0



Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan0
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "0987654321" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto WPA2 -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 0
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:1a:73:ff:50:58
Sending on LPF/wlan0/00:1a:73:ff:50:58
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant

[Nesster]

Thanks ! I finally tried it with my router's broadcast on (with WPA / WPA-PSK). It worked !!! (Belkin F5D7010, chipset Broadcom 4306 rev 02, the card is up at 54G). On Xubuntu 8.04.

BUT I'd like to add a little more security though, in disabling the router's ssid broadcast. I tried searching around but the people reporting having issues with this just didn't responses from what I could find.

Is someone knows a trick ... I'd like to hear it !

Regards,

[wieman01]

Hi, now I'm confused. I followed the steps in your other posting 'HOWTO: RT2500, etc wireless cards'. Great to follow.
At the end I'm able to see my own router with iwlist scan. Great.
I aslo see that the ndiswrapper is used with lshw -C network.

However, at bullet nr 6 Ralink drivers do not support this approach:



and further down



So can I use this approach to get me connected with the wireless internet (WPA)???:confused:

I've a LinkSys pci card, i've added rt61 and rt61pci to the blacklist.

thanks for the great support. (A newby)
Rob
You have basically replaced the Ralink driver with "ndiswrapper" so you are OK. :-) Just continue to follow this thread if you like.

[wieman01]

Sure, I will try WiCD and let you know. Also, do you think it would be useful to debug with ndiswrapper? If so, I will get some logs using ndiswrapper.
Thanks.
You could try out "ndiswrapper", but I am sure your problems can be resolved after some more research. I have seen many posts and users that reports issues with the IPW3945.

[wieman01]

Thanks ! I finally tried it with my router's broadcast on (with WPA / WPA-PSK). It worked !!! (Belkin F5D7010, chipset Broadcom 4306 rev 02, the card is up at 54G). On Xubuntu 8.04.

BUT I'd like to add a little more security though, in disabling the router's ssid broadcast. I tried searching around but the people reporting having issues with this just didn't responses from what I could find.

Is someone knows a trick ... I'd like to hear it !

Regards,
Disabling SSID broadcast adds no extra security at all. It's an urban myth. Please read this for more:

http://blogs.technet.com/steriley/archive/2007/10/16/myth-vs-reality-wireless-ssids.aspx

Guess you can live with it. :-) Personally I have turned it on.

[wieman01]

Ziggy8.04,

I suggest you read the tutorial carefully once again, some stuff appears to be incorrect or missing.

Please start with a simpler set-up... Try WPA1 first and enable SSID broadcast. Then use one of my examples from page 1. Don't leave out anything please. Post back if you still have issues. :-)

[Aesrak]

I'm having connection problems with my Netgear WPN111 USB Device.

I have followed your tutorial exactly and so far I am using ndiswrapper and the device is detected fine and detects my network. But it is not connecting.

My router is using WPA1 with SSID broadcast enabled. I have all other network managers disabled. My settings are:


auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid SSID_HERE
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk SSID_HERE

I have replaced the ssid and psk values...

When I restart the network I get:


Listening on LPF/wlan0/00:18:4d:2f:ab:d2
Sending on LPF/wlan0/00:18:4d:2f:ab:d2
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

Any ideas why it is not connecting?

[Nesster]

Disabling SSID broadcast adds no extra security at all. It's an urban myth. Please read this for more:

http://blogs.technet.com/steriley/archive/2007/10/16/myth-vs-reality-wireless-ssids.aspx

Guess you can live with it. :-) Personally I have turned it on.

Hey thanks a lot ! That was really interesting reading !

Cheers !

[Nesster]

I'm having connection problems with my Netgear WPN111 USB Device.

I have followed your tutorial exactly and so far I am using ndiswrapper and the device is detected fine and detects my network. But it is not connecting.

My router is using WPA1 with SSID broadcast enabled. I have all other network managers disabled. My settings are:


auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid SSID_HERE
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk SSID_HERE

I have replaced the ssid and psk values...

When I restart the network I get:


Listening on LPF/wlan0/00:18:4d:2f:ab:d2
Sending on LPF/wlan0/00:18:4d:2f:ab:d2
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

Any ideas why it is not connecting?

Hi, I have the exact same situation at home. I was able to connect to my v8 Linksys router at work but at home with my v2 WRT54G (linksys), with latest Tomato firmware, I have the same as you. Can't connect with WPA1. It says something about rejecting packets (see syslog I think, at the moment I don't have access to my Ubuntu machine). I use the same laptop at home and at work by the way.

Keep us posted if you succeed.

[Monarch2007]

You could try out "ndiswrapper", but I am sure your problems can be resolved after some more research. I have seen many posts and users that reports issues with the IPW3945.

I tried WiCD, no success. The same messages about privacy mismatch show up in dmesg output. I have inserted the same here. Looks like there is a fundamental problem here. Also, WiCD did not show me any dialog to input user name password required for LEAP. Am I missing something here?
Btw, I tried various drivers options in the WiCD, no luck.
Again, thanks for all the help;
Regards.


[ 1932.968953] wlan0: Initial auth_alg=128
[ 1932.968957] wlan0: authenticate with AP 00:15:fa:b3:2d:50
[ 1932.968964] wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
[ 1932.968971] wlan0: RX deauthentication from 00:15:fa:b3:2d:50 (reason=2)
[ 1932.969953] wlan0: RX authentication from 00:15:fa:b3:2d:50 (alg=128 transaction=2 status=0)
[ 1932.969956] wlan0: authenticated
[ 1932.969958] wlan0: associate with AP 00:15:fa:b3:2d:50
[ 1932.969960] wlan0: mismatch in privacy configuration and mixed-cell disabled - abort association
[ 1935.390308] wlan0: RX deauthentication from 00:15:fa:b3:2d:50 (reason=2)
[ 1935.390311] wlan0: deauthenticated
[ 1933.965379] wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
[ 1933.966294] wlan0: RX deauthentication from 00:15:fa:b3:2d:50 (reason=2)
[ 1944.289229] wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
[ 1946.710222] wlan0: Initial auth_alg=128
[ 1946.710229] wlan0: authenticate with AP 00:15:fa:b3:2d:50
[ 1946.710247] wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
[ 1946.710259] wlan0: RX deauthentication from 00:15:fa:b3:2d:50 (reason=2)
[ 1946.712334] wlan0: RX deauthentication from 00:15:fa:b3:2d:50 (reason=2)
[ 1946.712922] wlan0: RX authentication from 00:15:fa:b3:2d:50 (alg=128 transaction=2 status=0)
[ 1946.712925] wlan0: authenticated
[ 1946.712927] wlan0: associate with AP 00:15:fa:b3:2d:50
[ 1946.712929] wlan0: mismatch in privacy configuration and mixed-cell disabled - abort association
[ 1946.713481] wlan0: RX deauthentication from 00:15:fa:b3:2d:50 (reason=2)
[ 1946.713483] wlan0: deauthenticated

[ddcc]

This is using ndiswrapper for a Ralink 2860 chipset on a new Airlink card. I've been wrangling with this card for a while, and this is the closest I've gotten. Both iwevent and the router log shows the computer connecting for a few seconds, then disconnecting, etc. Help would be much appreciated.

route:


192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
192.168.1.0 * 255.255.255.0 U 0 0 0 wlan0
link-local * 255.255.0.0 U 1000 0 0 eth0
default 192.168.1.1 0.0.0.0 UG 100 0 0 wlan0
default 192.168.1.1 0.0.0.0 UG 100 0 0 eth0


iwconfig:


lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:off/any
Mode:Managed Frequency:2.437 GHz Access Point: Not-Associated
Bit Rate:54 Mb/s Tx-Power:20 dBm Sensitivity=0/3
RTS thr:off Fragment thr:off
Power Management:off
Link Quality:53/100 Signal level:-62 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


sudo iwlist scan:


lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:1D:6A:D0:48:FB
ESSID:"linksys123"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:53/100 Signal level:-62 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 9 Mb/s
18 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 12 Mb/s
24 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK


sudo lshw -C network:


*-network
description: Wireless interface
product: RaLink
vendor: RaLink
physical id: 5
bus info: pci@0000:01:05.0
logical name: wlan0
version: 00
serial: 00:1d:6a:2b:e8:9e
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+rt2860 driverversion=1.53+Ralink Technology, Corp.,11 ip=192.168.1.110 latency=64 link=yes maxlatency=4 mingnt=2 module=ndiswrapper multicast=yes wireless=IEEE 802.11g


sudo cat /etc/network/interfaces:


auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
address 192.168.1.111
netmask 255.255.255.0
gateway 192.168.1.1

auto eth1
#iface eth1 inet dhcp

auto eth2
#iface eth2 inet dhcp

auto ath0
#iface ath0 inet dhcp

auto wlan0
iface wlan0 inet static
address 192.168.1.110
netmask 255.255.255.0
gateway 192.168.1.1
dns-nameservers 208.67.222.222
wpa-driver wext
wpa-ssid linksys123
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk <key>


sudo ifdown -v wlan0:


Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/clamav-freshclam-ifupdown
run-parts: executing /etc/network/if-down.d/wpasupplicant
route del default gw 192.168.1.1 metric 100 wlan0
ifconfig wlan0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan0.pid
Stopped /sbin/wpa_supplicant (pid 10021).


sudo ifup -v wlan0:


Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan0
wpa_supplicant: wpa-ap-scan 1 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "linksys123" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise CCMP -- OK
wpa_supplicant: wpa-group CCMP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto RSN -- OK
wpa_supplicant: enabling network block 0 -- OK

ifconfig wlan0 192.168.1.110 netmask 255.255.255.0 up
route add default gw 192.168.1.1 metric 100 wlan0
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/clamav-freshclam-ifupdown
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntp
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/openssh-server
run-parts: executing /etc/network/if-up.d/wpasupplicant
* Stopping NTP server ntpd
...done.
* Starting NTP server ntpd
...done.

[wieman01]

ddcc,

I know the rt2860 well and just installed one over the weekend. I suggest that you remove the corresponding lines from "interfaces" and use Network Manager or WICD instead (unless you need static IP addresses of course). It would then read:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
address 192.168.1.111
netmask 255.255.255.0
gateway 192.168.1.1
Note that I have removed all "wlan0" reference which is the way to go.

Now restart the PC and see if NM can connect. I ought to work.

[bioshake]

OK - If I understand this thread correctly, you CANNOT get wireless networking working in Ubuntu 7.10 (using WPA et al) without using wpasupplicant and configuring it manually (no network manager).

I'm using a DWA-140 USB adapter from d-link and I have it working to the point where I can scan networks and it looks like it is pulling IPs, but I get no net.

One of the steps I was told to do was copy a dat file over to /etc/Wireless/RT2870 folder, how important is this to have this file here and configured for your AP settings?

I have to configure my ESSID in this dat file as well as do it in the interfaces file?

[ddcc]

wieman01,

Thanks for your prompt reply. I would prefer to assign a static IP, although
getting the card working is the first priority. However, I have heard that
network manager has a bug that prevents it from "remembering" the WPA2 key
after a reboot. I would also like to ask which driver would be better in
this case; the GPL driver provided by Ralink, or the Windows XP x64 driver
through ndiswrapper.

I've commented out all the wlan0 lines in the interfaces file, installed wicd, and rebooted, however it still shows the wireless connecting, then dropping after a few seconds, then connecting again, etc.

[hookzilla]

I think I've followed the guide but I can't connect. Any help will be appreciated.

System:
P4 1500 mkz, 512 mb ram,
Ubuntu 8.04 with updates
DSL combo modem/router, SSID Broadcast off, WPA-PSK
Trendnet TWE423PI pci adapter, Marvell 88w8335 chip set
ndiswrapper using Mrv8000c Win98 driver
Network Manager is installed (with O/S). I don't know how to deactivate it.
EDIT: 7/11/08 - I removed Network-Manager using Synaptic. The only changes were that more networks were detected today.


Reference Information requested in the How-To:
(I hope this formats OK)

user@user-Desktop:~$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
link-local * 255.255.0.0 U 0 0 0 wlan0
default * 0.0.0.0 U 1000 0 0 wlan0


user@user-Desktop:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11b ESSID:off/any
Mode:Managed Channel:0 Access Point: Not-Associated
Bit Rate:1 Mb/s Sensitivity=-200 dBm
RTS thr=2346 B Fragment thr=2346 B
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


user@user-Desktop:~$ sudo iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:12:0E:7B:49:57
ESSID:""
Protocol:IEEE 802.11b
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:51/100 Signal level:-63 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK


user@user-Desktop:~$ sudo lshw -C network
*-network:0
description: Wireless interface
product: 88w8335 [Libertas] 802.11b/g Wireless
vendor: Marvell Technology Group Ltd.
physical id: 2
bus info: pci@0000:02:02.0
logical name: wlan0
version: 03
serial: 00:40:f4:f7:31:50
width: 32 bits
clock: 66MHz
capabilities: pm bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+mrv8000c driverversion=1.52+Marvell,09/17/2004,3.1.0.19 latency=64 link=no module=ndiswrapper multicast=yes wireless=IEEE 802.11b
*-network:1
description: Ethernet interface
product: RTL-8139/8139C/8139C+
vendor: Realtek Semiconductor Co., Ltd.
physical id: 3
bus info: pci@0000:02:03.0
logical name: eth0
version: 10
serial: 00:40:ca:b5:62:4c
size: 10MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=8139too driverversion=0.9.28 duplex=half latency=32 link=no maxlatency=64 mingnt=32 module=8139too multicast=yes port=MII speed=10MB/s


user@user-Desktop:~$ sudo cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dhcp

wpa-driver wext
wpa-ssid <my essid>
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <my pw>


user@user-Desktop:~$ sudo ifdown -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 8591
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:40:f4:f7:31:50
Sending on LPF/wlan0/00:40:f4:f7:31:50
Sending on Socket/fallback
ifconfig wlan0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan0.pid
Stopped /sbin/wpa_supplicant (pid 8560).


user@user-Desktop:~$ sudo ifup -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
ioctl[SIOCSIWPMKSA]: Invalid argument
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan0
wpa_supplicant: wpa-ap-scan 2 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "<my essid>" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise TKIP -- OK
wpa_supplicant: wpa-group TKIP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto WPA -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:40:f4:f7:31:50
Sending on LPF/wlan0/00:40:f4:f7:31:50
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant


user@user-Desktop:~$ lspci
00:00.0 Host bridge: Intel Corporation 82845 845 [Brookdale] Chipset Host Bridge (rev 03)
00:01.0 PCI bridge: Intel Corporation 82845 845 [Brookdale] Chipset AGP Bridge (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 12)
00:1f.0 ISA bridge: Intel Corporation 82801BA ISA Bridge (LPC) (rev 12)
00:1f.1 IDE interface: Intel Corporation 82801BA IDE U100 Controller (rev 12)
00:1f.2 USB Controller: Intel Corporation 82801BA/BAM USB Controller #1 (rev 12)
00:1f.3 SMBus: Intel Corporation 82801BA/BAM SMBus Controller (rev 12)
00:1f.4 USB Controller: Intel Corporation 82801BA/BAM USB Controller #1 (rev 12)
00:1f.5 Multimedia audio controller: Intel Corporation 82801BA/BAM AC'97 Audio Controller (rev 12)
01:00.0 VGA compatible controller: nVidia Corporation NV11DDR [GeForce2 MX200] (rev b2)
02:00.0 Modem: ALi Corporation SmartLink SmartPCI561 56K Modem
02:02.0 Ethernet controller: Marvell Technology Group Ltd. 88w8335 [Libertas] 802.11b/g Wireless (rev 03)
02:03.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)


user@user-Desktop:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:40:ca:b5:62:4c
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:17 Base address:0xc400

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1616 errors:0 dropped:0 overruns:0 frame:0
TX packets:1616 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:84328 (82.3 KB) TX bytes:84328 (82.3 KB)

wlan0 Link encap:Ethernet HWaddr 00:40:f4:f7:31:50
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:19 Memory:ef000000-ef010000

wlan0:avahi Link encap:Ethernet HWaddr 00:40:f4:f7:31:50
inet addr:169.254.7.98 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Interrupt:19 Memory:ef000000-ef010000

[victorsf]

well, i've the problem:
victor@victor-desktop:~$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 No scan results
Can you help me? Now i'm connected

[wieman01]

wieman01,

Thanks for your prompt reply. I would prefer to assign a static IP, although
getting the card working is the first priority. However, I have heard that
network manager has a bug that prevents it from "remembering" the WPA2 key
after a reboot. I would also like to ask which driver would be better in
this case; the GPL driver provided by Ralink, or the Windows XP x64 driver
through ndiswrapper.

I've commented out all the wlan0 lines in the interfaces file, installed wicd, and rebooted, however it still shows the wireless connecting, then dropping after a few seconds, then connecting again, etc.
Honest answer? Go for "ndiswraper" and the Windows driver. Save you a lot of trouble...

[ddcc]

After spending a few more hours messing with both the Ralink and ndiswrapper, I've found that the only way I can get the wireless to work is with WEP or with no encryption; WPA or WPA2 just makes the wireless endlessly connect and disconnect. I've tried toggling all the settings on the router, but none make any difference. Especially since this is one of those new 802.11n draft wireless cards, I think that this problem is because it's too new, or the router is doing something strange with WPA, neither of which I can easily solve.

Since we originally bought the wireless because there was no more room on the back of the wired router, I think I'm going to move the wireless card to a Windows-only PC, and leave this Vista/Ubuntu as wired.

Thanks for your help wieman01

[geezerone]

Out of interest what signal strength do you get with your wireless adapter. I have a Ralink USB adapter and if strength drops below 50% I get disconnected (WPA2). I find my sig. strength between 69 to 90% is stable enough with 54Mbps on 802.11g standard (max.)

If you have Cat * cabling you could invest in another Ethernet switch and connect this to your Router's ethernet port to an auto X-over port or via crossover cable (1&3, 2&6 cross-over).

[ddcc]

Oddly enough, Windows shows it as 70-80, but in Linux it shows as somewhere around 50%. We do have CAT5 cabling, but I don't happen to have any of the cable crimpers (though I do have a few spare heads).

The reason we decided to go for wireless though, is that the router and modem are downstairs in the computer room, from which one port is plugged into the CAT5 cable, which is then connected to a CAT5 going to another room at the cable box. We originally considered moving all the equipment up into the cable box but there wasn't enough room, nor was there any documentation on how to get it working.

[wieman01]

I think I've followed the guide but I can't connect. Any help will be appreciated.

System:
P4 1500 mkz, 512 mb ram,
Ubuntu 8.04 with updates
DSL combo modem/router, SSID Broadcast off, WPA-PSK
Trendnet TWE423PI pci adapter, Marvell 88w8335 chip set
ndiswrapper using Mrv8000c Win98 driver
Network Manager is installed (with O/S). I don't know how to deactivate it.
EDIT: 7/11/08 - I removed Network-Manager using Synaptic. The only changes were that more networks were detected today.


Reference Information requested in the How-To:
(I hope this formats OK)

user@user-Desktop:~$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
link-local * 255.255.0.0 U 0 0 0 wlan0
default * 0.0.0.0 U 1000 0 0 wlan0


user@user-Desktop:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11b ESSID:off/any
Mode:Managed Channel:0 Access Point: Not-Associated
Bit Rate:1 Mb/s Sensitivity=-200 dBm
RTS thr=2346 B Fragment thr=2346 B
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


user@user-Desktop:~$ sudo iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:12:0E:7B:49:57
ESSID:""
Protocol:IEEE 802.11b
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:51/100 Signal level:-63 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK

Everything looks set to me. What wireless adapter have you got? You could also use Network Manager or WICD instead if you don't plan on using static IP addresses. I guess it would make things a lot easier for you.

Weird. It ought to work.

[wieman01]

Oddly enough, Windows shows it as 70-80, but in Linux it shows as somewhere around 50%. We do have CAT5 cabling, but I don't happen to have any of the cable crimpers (though I do have a few spare heads).

The reason we decided to go for wireless though, is that the router and modem are downstairs in the computer room, from which one port is plugged into the CAT5 cable, which is then connected to a CAT5 going to another room at the cable box. We originally considered moving all the equipment up into the cable box but there wasn't enough room, nor was there any documentation on how to get it working.
Question though... Is your adapter a USB one? Power supply could be the issue at hand. You could try an extra external USB power supply. That was the issue in my case a while back.

[hookzilla]

Thanks, wiemon01, for the response.

Adaptor:
I have a Trendnet TEW423PI (H/W Build B1) PCI adaptor using the Marvel 88w8335 Libertas chipset . I have installed ndiswrapper using the W98 driver Mrv8000c. I tried the WinXP driver but didn't see any difference. I forgot to add in my first post that mine is a WUBI installation. (Does that matter?)

Questions:
I have looked at several HowTo's, and may have some clutter. Should I have both the /etc/networks/interfaces and /etc/wpa_supplicant.conf files? I think the wpa_supplicant.conf was from an attempt with ssid broadcast on. Should I delete the wpa_supplicant file? I tried resetting /etc/newtowk/interfaces for SSID broadcast, but that didn't work.
Here are the files:

wpa_supplicant.conf
ap_scan=1
ctrl_interface=/var/run/wpa_supplicant

network={
ssid="<ssid>"
scan_ssid=0
proto=WPA
key_mgmt=WPA-PSK
psk="<asciipw>"
pairwise=TKIP
group=TKIP
}


user@user-Desktop:~$ sudo cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dhcp

wpa-driver wext
wpa-ssid <ssid>
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <hex pw>

When I removed network-manager, should I have deleted just network-manager or all the setup files also?

I have tried wicd previously, so I may give that a try. Do I need to do anything with the previously mentioned files?

Once again, thanks very much for your time and support of this HowTo.

[wieman01]

hookzilla,

You don't need "wpa_supplicant.conf" if you follow this tutorial.

In order to try WICD or Network Manager, "/etc/network/interfaces" must read:

auto lo
iface lo inet loopback
Nothing else. After a restart you can try either of these tools.

I guess you don't have to remove NM if you run Hardy... not sure though. If you remove NM, the system does all the clean-up for you, there is no need to remove an other files yourself.

[ddcc]

wieman01: No, it's an integrated PCI one.
geezerone: I didn't consider signal strength before; it might very well be due to a weak signal. I'm going to move it closer to the AP and try again.

[hookzilla]

wieman01

Once again, thanks for the suggestions.

I did a fresh install of Ubuntu and tried Network manager (with ndiswrapper and the W98 driver) No luck. It showed the networks after a scan, bur would not connect. If I tried connecting using the NM applet, it at least showed the signal strength. However, it would not connect. I would enter the password and it would think a moment and ask for the password, etc.

I then installed wicd. Same thing - showed several networks, including mine. But it wouldn't connect. Also, once wicd was installed, everything got really slow.

I'm at a loss. The card connnects in WPA in WXP, so the card will handle WPA. I've tried both the W98 and XP drivers in ndiswrapper. I didn't see any difference.

One thing...My router is using channel 11. Do I have to specify that somewhere? I noticed that RUtilT has a place to set the channel. Unfortunately, is doesn't appear to handle WPA.

I really don't want to drop bask to WEP. I have another adapter (Belkin F5D7000 Rev 2 - Broadcom BCM4306(?)chipset) if you think that might be worth the effort.

Any suggestions? Are there any reports that might help?

Once again, thanks.

[geezerone]

Your symptoms of not connecting and being password-nagged are all too familiar with most here I would guess. I also experienced that signal strength less than 50% results in not being connected or dropping connections.

Change your channel to a lower one, e.g. 7 and see if this helps. I know that I had a high channel and weird as it sounds once lowered on the WAP it worked. I tried changing back and forth between the channels and the wireless would work and not work when I went from low to high channel #.

Good luck.

[wieman01]

wieman01

Once again, thanks for the suggestions.

I did a fresh install of Ubuntu and tried Network manager (with ndiswrapper and the W98 driver) No luck. It showed the networks after a scan, bur would not connect. If I tried connecting using the NM applet, it at least showed the signal strength. However, it would not connect. I would enter the password and it would think a moment and ask for the password, etc.

I then installed wicd. Same thing - showed several networks, including mine. But it wouldn't connect. Also, once wicd was installed, everything got really slow.

I'm at a loss. The card connnects in WPA in WXP, so the card will handle WPA. I've tried both the W98 and XP drivers in ndiswrapper. I didn't see any difference.

One thing...My router is using channel 11. Do I have to specify that somewhere? I noticed that RUtilT has a place to set the channel. Unfortunately, is doesn't appear to handle WPA.

I really don't want to drop bask to WEP. I have another adapter (Belkin F5D7000 Rev 2 - Broadcom BCM4306(?)chipset) if you think that might be worth the effort.

Any suggestions? Are there any reports that might help?

Once again, thanks.
You don't have to set the channel, the driver does that for you.

You could give the Broadcom adapter a shot, there are tutorials out there, some of them well written and easy to follow. Don't throw in the towel just yet, there is light at the end of the tunnel.

Good call... don't give in to WEP. It's a security protocol that does not deserve the name.

[hookzilla]

wieman01

I tried changing the channel but that didn't work either. Last chance is to change adapters.

Have you heard of anyone who got this working in Hardy?

And again, thanks for all the help..

[geezerone]

Open a terminal and copy/paste the output of
dmesg here after authentication fails.

What make/model and chipset of Wireless device are you using?

[hookzilla]

geezerone

I'm using a Trendnet TEW423PI build B.1with Marvell 88w8335 Libertas chipset - W98 Driver Mrv8000c Router is now on channel 11 using WPA TKIP

dmesg output:


user@user-desktop:~$ dmesg
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.24-19-generic (buildd@palmer) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #1 SMP Wed Jun 18 14:43:41 UTC 2008 (Ubuntu 2.6.24-19.34-generic)
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
[ 0.000000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 0000000017ff0000 (usable)
[ 0.000000] BIOS-e820: 0000000017ff0000 - 0000000017ff3000 (ACPI NVS)
[ 0.000000] BIOS-e820: 0000000017ff3000 - 0000000018000000 (ACPI data)
[ 0.000000] BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
[ 0.000000] BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
[ 0.000000] BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved)
[ 0.000000] 0MB HIGHMEM available.
[ 0.000000] 383MB LOWMEM available.
[ 0.000000] found SMP MP-table at 000f49a0
[ 0.000000] Entering add_active_range(0, 0, 98288) 0 entries of 256 used
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0 -> 4096
[ 0.000000] Normal 4096 -> 98288
[ 0.000000] HighMem 98288 -> 98288
[ 0.000000] Movable zone start PFN for each node
[ 0.000000] early_node_map[1] active PFN ranges
[ 0.000000] 0: 0 -> 98288
[ 0.000000] On node 0 totalpages: 98288
[ 0.000000] DMA zone: 32 pages used for memmap
[ 0.000000] DMA zone: 0 pages reserved
[ 0.000000] DMA zone: 4064 pages, LIFO batch:0
[ 0.000000] Normal zone: 735 pages used for memmap
[ 0.000000] Normal zone: 93457 pages, LIFO batch:31
[ 0.000000] HighMem zone: 0 pages used for memmap
[ 0.000000] Movable zone: 0 pages used for memmap
[ 0.000000] DMI 2.3 present.
[ 0.000000] ACPI: RSDP signature @ 0xC00F6740 checksum 0
[ 0.000000] ACPI: RSDP 000F6740, 0014 (r0 FIC )
[ 0.000000] ACPI: RSDT 17FF3000, 0030 (r1 FIC AWRDACPI 42302E31 AWRD 0)
[ 0.000000] ACPI: FACP 17FF3040, 0074 (r1 FIC AWRDACPI 42302E31 AWRD 0)
[ 0.000000] ACPI: DSDT 17FF30C0, 3A32 (r1 FIC AWRDACPI 1000 MSFT 100000C)
[ 0.000000] ACPI: FACS 17FF0000, 0040
[ 0.000000] ACPI: DBGP 17FF6B80, 0034 (r1 FIC AWRDACPI 42302E31 AWRD 0)
[ 0.000000] ACPI: APIC 17FF6B00, 0054 (r1 FIC AWRDACPI 42302E31 AWRD 0)
[ 0.000000] ACPI: PM-Timer IO Port: 0x4008
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[ 0.000000] Processor #0 15:0 APIC version 20
[ 0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[ 0.000000] ACPI: IRQ0 used by override.
[ 0.000000] ACPI: IRQ2 used by override.
[ 0.000000] ACPI: IRQ9 used by override.
[ 0.000000] Enabling APIC mode: Flat. Using 1 I/O APICs
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] Allocating PCI resources starting at 20000000 (gap: 18000000:e6c00000)
[ 0.000000] swsusp: Registered nosave memory region: 000000000009f000 - 00000000000a0000
[ 0.000000] swsusp: Registered nosave memory region: 00000000000a0000 - 00000000000f0000
[ 0.000000] swsusp: Registered nosave memory region: 00000000000f0000 - 0000000000100000
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 97521
[ 0.000000] Kernel command line: root=UUID=0CBC0E96BC0E7B0A loop=/ubuntu/disks/root.disk ro quiet splash
[ 0.000000] mapped APIC to ffffb000 (fee00000)
[ 0.000000] mapped IOAPIC to ffffa000 (fec00000)
[ 0.000000] Enabling fast FPU save and restore... done.
[ 0.000000] Enabling unmasked SIMD FPU exception support... done.
[ 0.000000] Initializing CPU#0
[ 0.000000] PID hash table entries: 2048 (order: 11, 8192 bytes)
[ 0.000000] Detected 1495.704 MHz processor.
[ 30.418536] Console: colour VGA+ 80x25
[ 30.418544] console [tty0] enabled
[ 30.419265] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 30.419998] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 30.438294] Memory: 377348k/393152k available (2177k kernel code, 15188k reserved, 1006k data, 368k init, 0k highmem)
[ 30.438311] virtual kernel memory layout:
[ 30.438313] fixmap : 0xfff4b000 - 0xfffff000 ( 720 kB)
[ 30.438315] pkmap : 0xff800000 - 0xffc00000 (4096 kB)
[ 30.438317] vmalloc : 0xd8800000 - 0xff7fe000 ( 623 MB)
[ 30.438319] lowmem : 0xc0000000 - 0xd7ff0000 ( 383 MB)
[ 30.438321] .init : 0xc0421000 - 0xc047d000 ( 368 kB)
[ 30.438323] .data : 0xc0320434 - 0xc041bdc4 (1006 kB)
[ 30.438325] .text : 0xc0100000 - 0xc0320434 (2177 kB)
[ 30.438331] Checking if this processor honours the WP bit even in supervisor mode... Ok.
[ 30.438404] SLUB: Genslabs=11, HWalign=64, Order=0-1, MinObjects=4, CPUs=1, Nodes=1
[ 30.518364] Calibrating delay using timer specific routine.. 2995.24 BogoMIPS (lpj=5990496)
[ 30.518413] Security Framework initialized
[ 30.518426] SELinux: Disabled at boot.
[ 30.518453] AppArmor: AppArmor initialized
[ 30.518462] Failure registering capabilities with primary security module.
[ 30.518479] Mount-cache hash table entries: 512
[ 30.518746] Initializing cgroup subsys ns
[ 30.518755] Initializing cgroup subsys cpuacct
[ 30.518776] CPU: After generic identify, caps: 3febfbff 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 30.518801] CPU: Trace cache: 12K uops, L1 D cache: 8K
[ 30.518807] CPU: L2 cache: 256K
[ 30.518812] CPU: Hyper-Threading is disabled
[ 30.518816] CPU: After all inits, caps: 3febfbff 00000000 00000000 0000b080 00000000 00000000 00000000 00000000
[ 30.518843] Compat vDSO mapped to ffffe000.
[ 30.518870] Checking 'hlt' instruction... OK.
[ 30.535078] SMP alternatives: switching to UP code
[ 30.538170] Freeing SMP alternatives: 11k freed
[ 30.538478] Early unpacking initramfs... done
[ 31.176558] ACPI: Core revision 20070126
[ 31.176667] ACPI: Looking for DSDT in initramfs... error, file /DSDT.aml not found.
[ 31.182140] CPU0: Intel(R) Pentium(R) 4 CPU 1500MHz stepping 0a
[ 31.182214] Total of 1 processors activated (2995.24 BogoMIPS).
[ 31.182375] ENABLING IO-APIC IRQs
[ 31.182589] ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 31.329718] Brought up 1 CPUs
[ 31.329762] CPU0 attaching sched-domain:
[ 31.329768] domain 0: span 01
[ 31.329772] groups: 01
[ 31.330206] net_namespace: 64 bytes
[ 31.330226] Booting paravirtualized kernel on bare hardware
[ 31.331294] Time: 18:32:46 Date: 07/13/08
[ 31.331354] NET: Registered protocol family 16
[ 31.331845] EISA bus registered
[ 31.331892] ACPI: bus type pci registered
[ 31.357911] PCI: PCI BIOS revision 2.10 entry at 0xfaf70, last bus=2
[ 31.357916] PCI: Using configuration type 1
[ 31.357944] Setting up standard PCI resources
[ 31.366162] ACPI: EC: Look up EC in DSDT
[ 31.372045] ACPI: Interpreter enabled
[ 31.372056] ACPI: (supports S0 S1 S4 S5)
[ 31.372086] ACPI: Using IOAPIC for interrupt routing
[ 31.383131] ACPI: PCI Root Bridge [PCI0] (0000:00)
[ 31.383501] PCI quirk: region 4000-407f claimed by ICH4 ACPI/GPIO/TCO
[ 31.383508] PCI quirk: region 4080-40bf claimed by ICH4 GPIO
[ 31.384439] PCI: Transparent bridge - 0000:00:1e.0
[ 31.384487] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[ 31.384775] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
[ 31.408261] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
[ 31.408463] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
[ 31.408665] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
[ 31.408861] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
[ 31.409057] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
[ 31.409253] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
[ 31.409448] ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
[ 31.409690] ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
[ 31.410035] Linux Plug and Play Support v0.97 (c) Adam Belay
[ 31.410110] pnp: PnP ACPI init
[ 31.410132] ACPI: bus type pnp registered
[ 31.417825] pnp: PnP ACPI: found 17 devices
[ 31.417833] ACPI: ACPI bus type pnp unregistered
[ 31.417844] PnPBIOS: Disabled by ACPI PNP
[ 31.418388] PCI: Using ACPI for IRQ routing
[ 31.418396] PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
[ 31.449526] NET: Registered protocol family 8
[ 31.449531] NET: Registered protocol family 20
[ 31.449718] AppArmor: AppArmor Filesystem Enabled
[ 31.453504] Time: tsc clocksource has been installed.
[ 31.461617] system 00:00: ioport range 0x280-0x287 has been reserved
[ 31.461636] system 00:01: iomem range 0xcc000-0xcffff has been reserved
[ 31.461642] system 00:01: iomem range 0xf0000-0xf7fff could not be reserved
[ 31.461647] system 00:01: iomem range 0xf8000-0xfbfff could not be reserved
[ 31.461652] system 00:01: iomem range 0xfc000-0xfffff could not be reserved
[ 31.461658] system 00:01: iomem range 0x17ff0000-0x17ffffff could not be reserved
[ 31.461662] system 00:01: iomem range 0x0-0x9ffff could not be reserved
[ 31.461668] system 00:01: iomem range 0x100000-0x17feffff could not be reserved
[ 31.461674] system 00:01: iomem range 0xfec00000-0xfec00fff could not be reserved
[ 31.461679] system 00:01: iomem range 0xfee00000-0xfee00fff could not be reserved
[ 31.461684] system 00:01: iomem range 0xffb00000-0xffbfffff could not be reserved
[ 31.461689] system 00:01: iomem range 0xfff00000-0xffffffff could not be reserved
[ 31.461694] system 00:01: iomem range 0xe0000-0xeffff has been reserved
[ 31.461708] system 00:03: ioport range 0x4000-0x40bf could not be reserved
[ 31.461720] system 00:04: ioport range 0x4d0-0x4d1 has been reserved
[ 31.461725] system 00:04: ioport range 0x800-0x87f has been reserved
[ 31.492698] PCI: Bridge: 0000:00:01.0
[ 31.492703] IO window: disabled.
[ 31.492711] MEM window: ec000000-edffffff
[ 31.492717] PREFETCH window: e0000000-e7ffffff
[ 31.492726] PCI: Bridge: 0000:00:1e.0
[ 31.492731] IO window: c000-cfff
[ 31.492739] MEM window: ee000000-efffffff
[ 31.492745] PREFETCH window: disabled.
[ 31.492771] PCI: Setting latency timer of device 0000:00:1e.0 to 64
[ 31.492801] NET: Registered protocol family 2
[ 31.529611] IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
[ 31.530095] TCP established hash table entries: 16384 (order: 5, 131072 bytes)
[ 31.530278] TCP bind hash table entries: 16384 (order: 5, 131072 bytes)
[ 31.530491] TCP: Hash tables configured (established 16384 bind 16384)
[ 31.530497] TCP reno registered
[ 31.541805] checking if image is initramfs...<7>Switched to high resolution mode on CPU 0
[ 32.123769] it is
[ 32.779050] Freeing initrd memory: 7572k freed
[ 32.780366] audit: initializing netlink socket (disabled)
[ 32.780398] audit(1215973967.240:1): initialized
[ 32.784858] VFS: Disk quotas dquot_6.5.1
[ 32.785062] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 32.785411] io scheduler noop registered
[ 32.785417] io scheduler anticipatory registered
[ 32.785420] io scheduler deadline registered
[ 32.785452] io scheduler cfq registered (default)
[ 32.785537] Boot video device is 0000:01:00.0
[ 32.786173] isapnp: Scanning for PnP cards...
[ 33.140389] isapnp: No Plug & Play device found
[ 33.248892] Real Time Clock Driver v1.12ac
[ 33.249101] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
[ 33.249309] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 33.249704] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
[ 33.251397] 00:0a: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 33.252410] 00:0b: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
[ 33.253025] ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 21 (level, low) -> IRQ 16
[ 33.257452] 0000:02:00.0: ttyS2 at I/O 0xc028 (irq = 16) is a 8250
[ 33.259842] 0000:02:00.0: ttyS3 at I/O 0xc040 (irq = 16) is a 8250
[ 33.260242] Couldn't register serial port 0000:02:00.0: -28
[ 33.261645] RAMDISK driver initialized: 16 RAM disks of 65536K size 1024 blocksize
[ 33.261820] input: Macintosh mouse button emulation as /devices/virtual/input/input0
[ 33.262105] PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
[ 33.265245] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 33.265256] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 33.272002] mice: PS/2 mouse device common for all mice
[ 33.272312] EISA: Probing bus 0 at eisa.0
[ 33.272338] Cannot allocate resource for EISA slot 4
[ 33.272342] Cannot allocate resource for EISA slot 5
[ 33.272358] EISA: Detected 0 cards.
[ 33.272366] cpuidle: using governor ladder
[ 33.272370] cpuidle: using governor menu
[ 33.272569] NET: Registered protocol family 1
[ 33.272632] Using IPI No-Shortcut mode
[ 33.272709] registered taskstats version 1
[ 33.272877] Magic number: 0:370:544
[ 33.273073] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[ 33.273077] EDD information not available.
[ 33.274031] Freeing unused kernel memory: 368k freed
[ 33.296002] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1
[ 34.811279] fuse init (API version 7.9)
[ 34.850474] ACPI: Fan [FAN] (on)
[ 34.864460] ACPI: Processor [CPU0] (supports 2 throttling states)
[ 34.873236] ACPI: Thermal Zone [THRM] (40 C)
[ 36.287161] usbcore: registered new interface driver usbfs
[ 36.287216] usbcore: registered new interface driver hub
[ 36.306680] SCSI subsystem initialized
[ 36.351029] usbcore: registered new device driver usb
[ 36.438239] 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
[ 36.438331] 8139cp 0000:02:03.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible chip
[ 36.438340] 8139cp 0000:02:03.0: Try the "8139too" driver instead.
[ 36.462509] libata version 3.00 loaded.
[ 36.488694] 8139too Fast Ethernet driver 0.9.28
[ 36.488832] ACPI: PCI Interrupt 0000:02:03.0[A] -> GSI 17 (level, low) -> IRQ 17
[ 36.489791] eth0: RealTek RTL8139 at 0xc400, 00:40:ca:b5:62:4c, IRQ 17
[ 36.489797] eth0: Identified 8139 chip type 'RTL-8100'
[ 36.514450] USB Universal Host Controller Interface driver v3.0
[ 36.514605] ACPI: PCI Interrupt 0000:00:1f.2[D] -> GSI 19 (level, low) -> IRQ 18
[ 36.514627] PCI: Setting latency timer of device 0000:00:1f.2 to 64
[ 36.514634] uhci_hcd 0000:00:1f.2: UHCI Host Controller
[ 36.515344] uhci_hcd 0000:00:1f.2: new USB bus registered, assigned bus number 1
[ 36.515401] uhci_hcd 0000:00:1f.2: irq 18, io base 0x0000d000
[ 36.515749] usb usb1: configuration #1 chosen from 1 choice
[ 36.515798] hub 1-0:1.0: USB hub found
[ 36.515811] hub 1-0:1.0: 2 ports detected
[ 36.616739] ACPI: PCI Interrupt 0000:00:1f.4[C] -> GSI 23 (level, low) -> IRQ 19
[ 36.616764] PCI: Setting latency timer of device 0000:00:1f.4 to 64
[ 36.616771] uhci_hcd 0000:00:1f.4: UHCI Host Controller
[ 36.616821] uhci_hcd 0000:00:1f.4: new USB bus registered, assigned bus number 2
[ 36.616862] uhci_hcd 0000:00:1f.4: irq 19, io base 0x0000d800
[ 36.617123] usb usb2: configuration #1 chosen from 1 choice
[ 36.617172] hub 2-0:1.0: USB hub found
[ 36.617185] hub 2-0:1.0: 2 ports detected
[ 36.701658] Floppy drive(s): fd0 is 1.44M
[ 36.720085] FDC 0 is a post-1991 82077
[ 36.721282] PCI: Setting latency timer of device 0000:00:1f.1 to 64
[ 36.771469] ata_piix 0000:00:1f.1: version 2.12
[ 36.771605] PCI: Setting latency timer of device 0000:00:1f.1 to 64
[ 36.789293] scsi0 : ata_piix
[ 36.797845] scsi1 : ata_piix
[ 36.799051] ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xf000 irq 14
[ 36.799057] ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xf008 irq 15
[ 37.016699] ata1.00: ATA-6: ST3120026A, 3.06, max UDMA/100
[ 37.016708] ata1.00: 234441648 sectors, multi 16: LBA48
[ 37.032628] ata1.00: configured for UDMA/100
[ 37.517495] ata2.00: ATAPI: HL-DT-STDVD-ROM GDR8163B, 0L23, max UDMA/33
[ 37.517544] ata2.01: ATAPI: LG CD-RW CED-8120B, 2.00, max MWDMA2
[ 37.687785] ata2.00: configured for UDMA/33
[ 37.859717] ata2.01: configured for MWDMA2
[ 37.859992] scsi 0:0:0:0: Direct-Access ATA ST3120026A 3.06 PQ: 0 ANSI: 5
[ 37.869697] scsi 1:0:0:0: CD-ROM HL-DT-ST DVD-ROM GDR8163B 0L23 PQ: 0 ANSI: 5
[ 37.871134] scsi 1:0:1:0: CD-ROM LG CD-RW CED-8120B 2.00 PQ: 0 ANSI: 5
[ 38.299150] Driver 'sd' needs updating - please use bus_type methods
[ 38.299333] sd 0:0:0:0: [sda] 234441648 512-byte hardware sectors (120034 MB)
[ 38.299362] sd 0:0:0:0: [sda] Write Protect is off
[ 38.299367] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 38.299407] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 38.299514] sd 0:0:0:0: [sda] 234441648 512-byte hardware sectors (120034 MB)
[ 38.299537] sd 0:0:0:0: [sda] Write Protect is off
[ 38.299542] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 38.299580] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 38.299589] sda:<4>Driver 'sr' needs updating - please use bus_type methods
[ 38.311193] sda1
[ 38.311327] sd 0:0:0:0: [sda] Attached SCSI disk
[ 38.329618] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 38.329660] sr 1:0:0:0: Attached scsi generic sg1 type 5
[ 38.329695] scsi 1:0:1:0: Attached scsi generic sg2 type 5
[ 38.331236] sr0: scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda tray
[ 38.331247] Uniform CD-ROM driver Revision: 3.20
[ 38.331373] sr 1:0:0:0: Attached scsi CD-ROM sr0
[ 38.346816] sr1: scsi3-mmc drive: 24x/32x writer cd/rw xa/form2 cdda tray
[ 38.346944] sr 1:0:1:0: Attached scsi CD-ROM sr1
[ 39.217236] loop: module loaded
[ 39.268373] kjournald starting. Commit interval 5 seconds
[ 39.268412] EXT3-fs: mounted filesystem with ordered data mode.
[ 52.708881] Linux agpgart interface v0.102
[ 52.854584] iTCO_vendor_support: vendor-support=0
[ 52.924722] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.02 (26-Jul-2007)
[ 52.925839] iTCO_wdt: failed to reset NO_REBOOT flag, reboot disabled by hardware
[ 52.925857] iTCO_wdt: No card detected
[ 53.003537] agpgart: Detected an Intel 845G Chipset.
[ 53.008045] agpgart: AGP aperture is 64M @ 0xe8000000
[ 53.080586] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 53.172657] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 53.280327] intel_rng: FWH not detected
[ 53.420468] input: PC Speaker as /devices/platform/pcspkr/input/input2
[ 54.036721] input: Power Button (FF) as /devices/virtual/input/input3
[ 54.057046] ACPI: Power Button (FF) [PWRF]
[ 54.057611] input: Power Button (CM) as /devices/virtual/input/input4
[ 54.067480] ACPI: Power Button (CM) [PWRB]
[ 54.067753] input: Sleep Button (CM) as /devices/virtual/input/input5
[ 54.079469] ACPI: Sleep Button (CM) [SLPB]
[ 54.650978] ndiswrapper version 1.52 loaded (smp=yes, preempt=no)
[ 55.527040] ndiswrapper: driver mrv8000c (Marvell,09/17/2004,3.1.0.19) loaded
[ 55.527549] ACPI: PCI Interrupt 0000:02:02.0[A] -> GSI 23 (level, low) -> IRQ 19
[ 55.530144] ndiswrapper: using IRQ 19
[ 55.790538] wlan0: ethernet device 00:40:f4:f7:31:50 using NDIS driver: mrv8000c, version: 0x3000027, NDIS version: 0x500, vendor: 'NDIS Network Adapter', 11AB:1FAA.5.conf
[ 55.790567] ndiswrapper (set_iw_encr_mode:717): setting encryption mode to 6 failed (C00000BB)
[ 55.790579] wlan0: encryption modes supported: WEP; TKIP with WPA
[ 55.790737] usbcore: registered new interface driver ndiswrapper
[ 58.956810] input: PS/2 Generic Mouse as /devices/platform/i8042/serio1/input/input6
[ 59.068821] parport_pc 00:0c: reported by Plug and Play ACPI
[ 59.068888] parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,ECP,DMA]
[ 59.272113] ACPI: PCI Interrupt 0000:00:1f.5[B] -> GSI 17 (level, low) -> IRQ 17
[ 59.272145] PCI: Setting latency timer of device 0000:00:1f.5 to 64
[ 59.594128] intel8x0_measure_ac97_clock: measured 54588 usecs
[ 59.594136] intel8x0: clocking to 48000
[ 62.676556] NET: Registered protocol family 17
[ 63.984456] lp0: using parport0 (interrupt-driven).
[ 64.934454] EXT3 FS on loop0, internal journal
[ 90.927334] Adding 976552k swap on /host/ubuntu/disks/swap.disk. Priority:-1 extents:1 across:976552k
[ 91.782055] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 92.668167] No dock devices found.
[ 94.631749] apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac)
[ 94.631761] apm: overridden by ACPI.
[ 94.791438] ppdev: user-space parallel port driver
[ 95.020532] audit(1215988430.280:2): type=1503 operation="inode_permission" requested_mask="a::" denied_mask="a::" name="/dev/tty" pid=4936 profile="/usr/sbin/cupsd" namespace="default"
[ 97.984770] Bluetooth: Core ver 2.11
[ 97.986313] NET: Registered protocol family 31
[ 97.986323] Bluetooth: HCI device and connection manager initialized
[ 97.986331] Bluetooth: HCI socket layer initialized
[ 98.072682] Bluetooth: L2CAP ver 2.9
[ 98.072694] Bluetooth: L2CAP socket layer initialized
[ 98.211486] Bluetooth: RFCOMM socket layer initialized
[ 98.212012] Bluetooth: RFCOMM TTY layer initialized
[ 98.212022] Bluetooth: RFCOMM ver 1.8
[ 98.689567] eth0: link down
[ 110.530266] NET: Registered protocol family 10
[ 110.531396] lo: Disabled Privacy Extensions
[ 110.532997] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 110.534012] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 179.502667] UDF-fs: Partition marked readonly; forcing readonly mount
[ 179.628083] UDF-fs INFO UDF 0.9.8.1 (2004/29/09) Mounting volume ' DVD_RECORDER', timestamp 2006/08/06 17:42 (1f10)
user@user-desktop:~$


Thanks for any help you can give.

[ugraham]

I am running Hardy with a linksys WPC54G V2.

I have used these 2 threads:
http://ubuntuforums.org/showthread.php?t=324148
http://ubuntuforums.org/showthread.php?t=318539

Using WPA-PSK (TKIP)

it still doesn't work. When I do sudo /etc/init.d/networking restart

I get ioctl[SIOCSIWPMKSA]: Invalid argument

Can anyone offer any suggestions.

Thanks.

[wesswei]

For WPA1 my example would look like this:

I have never bothered to setup wpa_supplicant outside of "interfaces" because I don't think it is nice. So I cannot give you any advice there. However, I am having a similar issue as you whereby I need to initialize my wireless network at startup, then immediately bring it down & restart it. For some reason the network would remain disconnected if I did not restart it.

So my advice is to follow post #2 and restart the network during the boot process. Not sure if this is a bug but I have not found a solution ever since.

Thanks wieman! I used your post before to get my WPA working for linksys wusb54gv4 but had to manually restart the network EVERY time. I totally missed the second post which explains this bug.

I did this to update the links for all the rc folders.

sudo update-rc.d wireless-networking defaults 40

Thanks again. Very informative how-to...

PS. I'm not sure if you or anyone else had this problem, but when I updated to Hardy and used WPA, my system would sometimes instantly shut down. This did not happen using WEP on hardy. I updated my bios and the kernel as it wouldn't even boot after the shutdown had occurred unless I switched voltage on my computer and cycle power a few times. Hasn't happened since. whew!

[panda2004]

Thanks for your post is very detailed. I'm not sure if you or anyone else had this problem, but when I install Hardy and used WPA, my system would not connect. The wireless without WPA or WEP works fine. But as long as I enabled security on route, wireless doesn't work. (the same machine booted to vista can access the same route with WPA/WEP without any issue.)

I started a post :Wireless with WPA/WEP doesn't work
http://ubuntuforums.org/showthread.php?p=5425857#post5425857

Any suggestion to my issue?

[ugraham]

I am running Hardy with a linksys WPC54G V2.

I have used these 2 threads:
http://ubuntuforums.org/showthread.php?t=324148
http://ubuntuforums.org/showthread.php?t=318539

Using WPA-PSK (TKIP)

it still doesn't work. When I do sudo /etc/init.d/networking restart

I get ioctl[SIOCSIWPMKSA]: Invalid argument

Can anyone offer any suggestions.




Thanks.

Interestingly enough, I ran up my machine with Opensus 10.3 and followed the ubuntu forums and the Linksys WPC54G V2 works straight away. It is using ndiswrapper 1.9 and wpa_supplicant 0.5.8. Linux kernel 2.6.22.5-31

Being a newbie, how can I get this to work under Ubuntu Hardy. What makes the 2 versions of Linux so different (I assume the kernel)

[sputnikkk]

Is the info in the change log highlited in RED, still true 1 year later, or has it just not been tried since then?



CHANGE LOG:
08/11/2006: Added section "Post this if you are stumped" (SquibT).
08/11/2006: Added sample configuration for WPA2 with DHCP & ESSID broadcast (Wieman01).
08/11/2006: Added sample configuration for WPA1 with DHCP & ESSID broadcast (Wieman01).
08/11/2006: Added section "Tested adapters" (Wieman01).
08/11/2006: Added section "Useful commands" (SquibT).
08/11/2006: Added section "Common stumbling blocks" (Wieman01).
08/11/2006: Changed section "wpa-driver" and added new drivers (Wieman01).
08/11/2006: Added section "Revoking read-permission from group 'others'" (Wieman01).
09/11/2006: Minor changes in layout (Wieman01).
09/11/2006: Added sample configuration for mixed mode (WPA1, WPA2) with DHCP & ESSID broadcast (Wieman01).
09/11/2006: Added experimental sample configuration for LEAP with WEP, DHCP & ESSID broadcast (Wieman01).
09/11/2006: Added section "Install wpa-supplicant" (Wieman01).
10/11/2006: Added experimental sample configuration for TTLS with WEP, DHCP & ESSID broadcast (Wieman01).
15/11/2006: Added experimental sample configuration for EAP-FAST with WPA1/WPA2, DHCP & ESSID broadcast (Wieman01).
04/12/2006: Changed "wpa_passphrase" section & added quotes ("") for encryption keys containing special characters (Wieman01).
04/01/2007: Added various security options (Wieman01).
15/01/2007: Added valid script for EAP-LEAP (Wieman01).
31/01/2007: Added valid script for EAP-PEAP (Wieman01).
21/04/2007: Removed "wpa-conf" for Edgy Eft (Wieman01).
22/04/2007: Simplified section concerning static network settings (Wieman01).
02/05/2007: Added note concerning WPA2 support for Atheros cards & drivers (Wieman01).
13/05/2007: Added note on Ralink drivers (Wieman01).
15/04/2008: Tested with Hardy Heron (Wieman01).

[Innova]

I just bought a trendnet TEW-424UB:


wesley@kids-desktop:~$ lsusb
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 002: ID 0bda:8189 Realtek Semiconductor Corp.
Bus 001 Device 001: ID 0000:0000

I used the modified driver from here: http://www.datanorth.net/~cuervo/rtl8187b/.

This seemed to work to get the hardware portion working:


wesley@kids-desktop:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 802.11b/g Mode:Managed Channel=8
Access Point: Not-Associated Bit Rate:11 Mb/s
Retry:on Fragment thr:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


wesley@kids-desktop:~$ sudo iwlist wlan0 scan
wlan0 Scan completed :
Cell 01 - Address: 00:18:F8:6D:97:E6
ESSID:"linksys"
Protocol:IEEE 802.11bg
Mode:Master
Channel:11
Encryption key:on
Bit Rates:54 Mb/s
Extra: Rates (Mb/s): 1 2 5.5 6 9 11 12 18 24 36 48 54
Quality:17 Signal level:0 Noise level:77
Extra: Last beacon: 1850ms ago


wesley@kids-desktop:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:17:9a:39:e1:5a
inet addr:192.168.1.103 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::217:9aff:fe39:e15a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:12234 errors:0 dropped:0 overruns:0 frame:0
TX packets:9497 errors:0 dropped:0 overruns:0 carrier:0
collisions:31 txqueuelen:1000
RX bytes:13714273 (13.0 MB) TX bytes:1316310 (1.2 MB)
Interrupt:11 Base address:0x2000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2324 errors:0 dropped:0 overruns:0 frame:0
TX packets:2324 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:116640 (113.9 KB) TX bytes:116640 (113.9 KB)

wlan0 Link encap:Ethernet HWaddr 00:14:d1:48:1e:1c
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:48 dropped:232 overruns:0 frame:0
TX packets:4308 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:180936 (176.6 KB)

wlan0:avahi Link encap:Ethernet HWaddr 00:14:d1:48:1e:1c
inet addr:169.254.3.147 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1

After setting up my interfaces file:


auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid linksys
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk KEY_GOES_HERE


And restarting networking, I get the following error:


wesley@kids-desktop:~$ sudo /etc/init.d/networking restart
* Reconfiguring network interfaces... There is already a pid file /var/run/dhclient.wlan0.pid with pid 7344
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:14:d1:48:1e:1c
Sending on LPF/wlan0/00:14:d1:48:1e:1c
Sending on Socket/fallback
There is already a pid file /var/run/dhclient.wlan0.pid with pid 134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:14:d1:48:1e:1c
Sending on LPF/wlan0/00:14:d1:48:1e:1c
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

Did I grab the wrong driver, or did I set up my interfaces file incorrectly?

[geezerone]

Even though the hardware is detected that doesn't mean the driver is 100% working. Output your dmesg too from terminal.

You aren't being issued an IP address hence the 169.254.x.x address for wlan0.

Take a look here (http://ubuntuforums.org/showthread.php?t=536373) where someone else used ndiswrapper to fix their problem.

HTH

[Innova]

Here is what I see in dmesg:


[ 452.413726] ieee80211_crypt: registered algorithm 'NULL'
[ 452.435893] ieee80211_crypt: registered algorithm 'WEP'
[ 452.473905] ieee80211_crypt: registered algorithm 'TKIP'
[ 452.523760] ieee80211_crypt: registered algorithm 'CCMP'
[ 452.740907] r8187: no version for "ieee80211_reset_queue" found: kernel tainted.
[ 452.746219]
[ 452.746225] Linux kernel driver for RTL8187/RTL8187B based WLAN cards
[ 452.746233] Copyright (c) 2004-2005, Andrea Merello
[ 452.746237] rtl8187: Initializing module
[ 452.746240] rtl8187: Wireless extensions version 22
[ 452.746243] rtl8187: Initializing proc filesystem
[ 452.752008] rtl8187: Reported EEPROM chip is a 93c46 (1Kbit)
[ 453.834905] rtl8187: Card MAC address is 00:14:d1:48:1e:1c
[ 455.204566] rtl8187: PAPE from CONFIG2: 0
[ 455.205657] rtl8187: Driver probe completed
[ 455.205660]
[ 455.205697] usbcore: registered new interface driver rtl8187
[ 455.506361] rtl8187: Card successfully reset
[ 455.506386] This is RTL8187B Reset procedure
[ 467.055203] WIRELESS_MODE_G
[ 467.088127] Set chan.call ieee80211_start_bss.in start bss call check.<6>ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 467.384829] Set chan.call ieee80211_start_bss.in start bss call check.<6>rtl8187: Setting SW wep key
[ 467.682930] rtl8187: Setting SW wep key
[ 467.682970] rtl8187: Setting SW wep key
[ 467.683005] rtl8187: Setting SW wep key
[ 477.715144] Linking with linksys
[ 477.831991] Associated successfully
[ 477.832007] Using G rates
[ 477.931211] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 481.805266] rtl8187: Setting SW wep key
[ 481.805326] rtl8187: Setting SW wep key
[ 481.805362] rtl8187: Setting SW wep key
[ 481.805397] rtl8187: Setting SW wep key
[ 481.805430] rtl8187: Setting SW wep key
[ 481.913804] Associated successfully
[ 481.913823] Using G rates


The setting SW wep key is repeated constantly (about every 4 seconds)..... Then when I tried to restart /etc/init.d/networking


[ 597.060695] rtl8187: Setting SW wep key
[ 597.060754] rtl8187: Setting SW wep key
[ 597.060789] rtl8187: Setting SW wep key
[ 597.060823] rtl8187: Setting SW wep key
[ 597.060859] rtl8187: Setting SW wep key
[ 597.429841] Associated successfully
[ 597.429862] Using G rates
[ 597.835807] rtl8180_close process
[ 597.835824] rtl8180_down process
[ 597.850688] RX Status Error!
[ 597.850710] RX process aborted due to explicit shutdown (ffffff8d) RX Status Error!
[ 597.851542] RX process aborted due to explicit shutdown (ffffff8d) RX Status Error!
[ 597.853558] RX process aborted due to explicit shutdown (ffffff8d) RX Status Error!
[ 597.854539] RX process aborted due to explicit shutdown (ffffff8d) RX Status Error!
[ 597.855537] RX process aborted due to explicit shutdown (ffffff8d) RX Status Error!
[ 597.856535] RX process aborted due to explicit shutdown (ffffff8d) RX Status Error!
[ 597.857535] RX process aborted due to explicit shutdown (ffffff8d) RX Status Error!
[ 597.858533] RX process aborted due to explicit shutdown (ffffff8d) RX Status Error!
[ 597.859535] RX process aborted due to explicit shutdown (fffffffe) RX Status Error!
[ 597.861560] RX process aborted due to explicit shutdown (fffffffe) RX Status Error!
[ 597.862532] RX process aborted due to explicit shutdown (fffffffe) RX Status Error!
[ 597.863529] RX process aborted due to explicit shutdown (fffffffe) RX Status Error!
[ 597.864530] RX process aborted due to explicit shutdown (fffffffe) RX Status Error!
[ 597.865529] RX process aborted due to explicit shutdown (fffffffe) RX Status Error!
[ 597.866526] RX process aborted due to explicit shutdown (fffffffe) RX Status Error!
[ 597.867528] RX process aborted due to explicit shutdown (fffffffe) <6>rtl8187: Setting SW wep key
[ 597.973462] rtl8187: Setting SW wep key
[ 597.973501] rtl8187: Setting SW wep key
[ 597.973535] rtl8187: Setting SW wep key
[ 597.973570] rtl8187: Setting SW wep key
[ 598.281306] rtl8187: Card successfully reset
[ 598.281328] This is RTL8187B Reset procedure
[ 610.447488] WIRELESS_MODE_G
[ 610.477423] Set chan.call ieee80211_start_bss.in start bss call check.<6>ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 610.771168] Set chan.call ieee80211_start_bss.in start bss call check.<6>Linking with linksys
[ 610.993886] Associated successfully
[ 610.993905] Using G rates
[ 611.068846] rtl8187: Setting SW wep key
[ 611.068918] rtl8187: Setting SW wep key
[ 611.068962] rtl8187: Setting SW wep key
[ 611.069004] rtl8187: Setting SW wep key
[ 611.123193] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 614.945138] rtl8187: Setting SW wep key
[ 614.945227] rtl8187: Setting SW wep key
[ 614.945265] rtl8187: Setting SW wep key
[ 614.945300] rtl8187: Setting SW wep key
[ 614.945337] rtl8187: Setting SW wep key
[ 615.052727] Associated successfully
[ 615.052743] Using G rates


Unfortunately the link you gave me for the ndiswrapper is for a different chipset:


wesley@kids-desktop:~/tmp/rtl8187b-modified$ lsusb
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 002: ID 0bda:8189 Realtek Semiconductor Corp.
Bus 001 Device 001: ID 0000:0000


Does the dmesg tell you anything?

[wieman01]

Is the info in the change log highlited in RED, still true 1 year later, or has it just not been tried since then?
Yes, it sadly is.

[geezerone]

If you can get the windows .inf driver for your USB adapter then it should work. I personally would try ndiswrapper (ndisgtk for frontend in Synaptic) to get an exact driver match for your device.

You could also try fixed IP address too as DHCP isn't assigning an IP for you.

[wieman01]

If you can get the windows .inf driver for your USB adapter then it should work. I personally would try ndiswrapper (ndisgtk for frontend in Synaptic) to get an exact driver match for your device.

You could also try fixed IP address too as DHCP isn't assigning an IP for you.
+1

Way to go.

[tjwilli]

Hi. I've been struggling with this for the past few days, and I still can't get connected with WPA. I have a Linksys WMP300N PCI adapter and can connect with > WPA on XP, but not with ubuntu. I can connect fine on an unsecured router. I've tried wicd, but that isn't helping either.

Here's my interfaces file:

auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dhcp
#wireless-essid dlink

wpa-driver wext
wpa-ssid tasha
wpa-ap-scan 1
wpa-proto RSN WPA
wpa-pairwise CCMP TKIP
wpa-group CCMP TKIP
wpa-key-mgmt WPA-PSK
wpa-psk xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

My wpa_supplicant.conf file:

ap_scan=1
ctrl_interface=/var/run/wpa_supplicant

network={
ssid="tasha"
scan_ssid=0
key_mgmt=WPA-PSK
proto=WPA
#psk="zzzzzzzzzzzzzzzzzzzzz"
psk=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx x
pairwise=TKIP
group=TKIP
}

tim@linux-loft:/etc/network$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:"dlink"
Mode:Managed Frequency:2.412 GHz Access Point: 00:1E:58:E9:2E:23
Bit Rate=130 Mb/s Tx-Power:32 dBm
RTS thr:2347 B Fragment thr:2346 B
Power Management:off
Link Quality:60/100 Signal level:-57 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


tim@linux-loft:/etc/network$ ndiswrapper -l
bcmwl5 : driver installed
device (14E4:4329) present

(I want essid tasha)

tim@linux-loft:/etc/network$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:1E:58:E9:2E:23
ESSID:"dlink"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:60/100 Signal level:-57 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 02 - Address: 00:15:E9:1E:BC:4A
ESSID:"default"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:42/100 Signal level:-69 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 03 - Address: 00:1C:10:CB:E8:92
ESSID:"tasha"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:35/100 Signal level:-73 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 04 - Address: 00:18:01:F8:5C:AF
ESSID:"RCZE4"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:42/100 Signal level:-69 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 05 - Address: 00:18:01:E5:78:A0
ESSID:""
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.427 GHz (Channel 4)
Quality:26/100 Signal level:-79 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 06 - Address: 00:18:F8:FB:27:A5
ESSID:"M&L"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:32/100 Signal level:-75 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0

tim@linux-loft:/etc/network$



When I try to restart my network after disconnecting from the unsecured access and quiting wicd I get this in daemon.log:

Aug 5 19:40:08 linux-loft dhclient: There is already a pid file /var/run/dhclient.wlan0.pid with pid 12838
Aug 5 19:40:08 linux-loft dhclient: removed stale PID file
Aug 5 19:40:08 linux-loft dhclient: Internet Systems Consortium DHCP Client V3.0.6
Aug 5 19:40:08 linux-loft dhclient: Copyright 2004-2007 Internet Systems Consortium.
Aug 5 19:40:08 linux-loft dhclient: All rights reserved.
Aug 5 19:40:08 linux-loft dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Aug 5 19:40:08 linux-loft dhclient:
Aug 5 19:40:08 linux-loft dhclient: Listening on LPF/wlan0/00:1e:e5:fa:3a:09
Aug 5 19:40:08 linux-loft dhclient: Sending on LPF/wlan0/00:1e:e5:fa:3a:09
Aug 5 19:40:08 linux-loft dhclient: Sending on Socket/fallback
Aug 5 19:40:08 linux-loft dhclient: DHCPRELEASE on wlan0 to 192.168.0.1 port 67
Aug 5 19:40:08 linux-loft dhclient: send_packet: Network is unreachable
Aug 5 19:40:08 linux-loft dhclient: send_packet: please consult README file regarding broadcast address.
Aug 5 19:40:08 linux-loft avahi-daemon[5015]: Withdrawing address record for fe80::21e:e5ff:fefa:3a09 on wlan0.
Aug 5 19:40:09 linux-loft dhclient: There is already a pid file /var/run/dhclient.wlan0.pid with pid 134519072
Aug 5 19:40:09 linux-loft dhclient: Internet Systems Consortium DHCP Client V3.0.6
Aug 5 19:40:09 linux-loft dhclient: Copyright 2004-2007 Internet Systems Consortium.
Aug 5 19:40:09 linux-loft dhclient: All rights reserved.
Aug 5 19:40:09 linux-loft dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Aug 5 19:40:09 linux-loft dhclient:
Aug 5 19:40:10 linux-loft avahi-daemon[5015]: Registering new address record for fe80::21e:e5ff:fefa:3a09 on wlan0.*.
Aug 5 19:40:10 linux-loft dhclient: Listening on LPF/wlan0/00:1e:e5:fa:3a:09
Aug 5 19:40:10 linux-loft dhclient: Sending on LPF/wlan0/00:1e:e5:fa:3a:09
Aug 5 19:40:10 linux-loft dhclient: Sending on Socket/fallback
Aug 5 19:40:11 linux-loft dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
Aug 5 19:40:17 linux-loft dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
Aug 5 19:40:32 linux-loft dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
Aug 5 19:40:42 linux-loft dhclient: No DHCPOFFERS received.
Aug 5 19:40:42 linux-loft dhclient: No working leases in persistent database - sleeping.
Aug 5 19:40:42 linux-loft avahi-autoipd(wlan0)[15173]: Found user 'avahi-autoipd' (UID 105) and group 'avahi-autoipd' (GID 113).
Aug 5 19:40:42 linux-loft avahi-autoipd(wlan0)[15173]: Successfully called chroot().
Aug 5 19:40:42 linux-loft avahi-autoipd(wlan0)[15173]: Successfully dropped root privileges.
Aug 5 19:40:42 linux-loft avahi-autoipd(wlan0)[15173]: Starting with address 169.254.5.236
Aug 5 19:40:47 linux-loft avahi-autoipd(wlan0)[15173]: Callout BIND, address 169.254.5.236 on interface wlan0
Aug 5 19:40:47 linux-loft avahi-daemon[5015]: Joining mDNS multicast group on interface wlan0.IPv4 with address 169.254.5.236.
Aug 5 19:40:47 linux-loft avahi-daemon[5015]: New relevant interface wlan0.IPv4 for mDNS.
Aug 5 19:40:47 linux-loft avahi-daemon[5015]: Registering new address record for 169.254.5.236 on wlan0.IPv4.
Aug 5 19:40:51 linux-loft avahi-autoipd(wlan0)[15173]: Successfully claimed IP address 169.254.5.236
Aug 5 19:41:11 linux-loft ntpdate[15236]: can't find host ntp.ubuntu.com
Aug 5 19:41:11 linux-loft ntpdate[15236]: no servers can be used, exiting

####################

Thanks for any help.

[Ziggy8.04]

so... i've tryed again and im still unable to conect
to my wpa network, any idea of what might be wrong???
i have a wrt160n. i must say also that i am new to linux
and i have no idea really. im trying to use ubunto on
an hp tx2000. 1 more thing ,i know tha my wifi works
in ubuntu because if i dont use any type of security
i will conect but thats not what i want to do i want
to use either wpa or wap2

ubuntu@ubuntu:~$ route

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
link-local * 255.255.0.0 U 0 0 0 wlan0
link-local * 255.255.0.0 U 0 0 0 eth0
link-local * 255.255.0.0 U 1000 0 0 wlan0
default * 0.0.0.0 U 1000 0 0 wlan0


ubuntu@ubuntu:~$ iwconfig

lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:"0987654321"
Mode:Managed Frequency:2.412 GHz Access Point: 00:1E:E5:4F:CD:FD
Bit Rate=130 Mb/s Tx-Power:32 dBm
RTS thr:2347 B Fragment thr:2346 B
Power Management:off
Link Quality:79/100 Signal level:-45 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:71 Invalid misc:13748 Missed beacon:0


ubuntu@ubuntu:~$ sudo iwlist scan

[sudo] password for ubuntu:
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:1E:E5:4F:CD:FD
ESSID:"0987654321"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:71/100 Signal level:-50 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 02 - Address: 00:1C:10:28:73:20
ESSID:"Tigress74"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:71/100 Signal level:-50 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 03 - Address: 00:0F:66:CC:28:80
ESSID:"linksys"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:28/100 Signal level:-78 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 04 - Address: 00:1E:2A:51:1E:B8
ESSID:"MEGAAHHHN"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:17/100 Signal level:-85 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 05 - Address: 00:1C:DF:8C:C7:37
ESSID:"Belkin_G_Plus_MIMO_8CC737"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:10/100 Signal level:-89 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 9 Mb/s
18 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 12 Mb/s
24 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0


ubuntu@ubuntu:~$ sudo lshw -C network

*-network
description: Wireless interface
product: BCM4328 802.11a/b/g/n
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:03:00.0
logical name: wlan0
version: 03
serial: 00:1a:73:ff:50:58
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+bcmwl5 driverversion=1.52+Broadcom,10/12/2006, 4.100. latency=0 link=no module=ndiswrapper multicast=yes wireless=IEEE 802.11g


ubuntu@ubuntu:~$ sudo cat /etc/network/interfaces

auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid 0987654321
wpa-ap-scan 1
wpa-proto WPA RSN
wpa-pairwise TKIP CCMP
wpa-group TKIP CCMP
wpa-key-mgmt WPA-PSK
wpa-psk b57bb5ed4ff49cb4ea629840c4ea4522d5344200e30fa22583 defbf8a66c8410


ubuntu@ubuntu:~$ sudo ifdown -v wlan0

Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 5784
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:1a:73:ff:50:58
Sending on LPF/wlan0/00:1a:73:ff:50:58
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 192.168.2.1 port 67
ifconfig wlan0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan0.pid
Stopped /sbin/wpa_supplicant (pid 4823).


ubuntu@ubuntu:~$ sudo ifup -v wlan0


Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan0
wpa_supplicant: wpa-ap-scan 1 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "0987654321" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise TKIP CCMP -- OK
wpa_supplicant: wpa-group TKIP CCMP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto WPA RSN -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 0
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:1a:73:ff:50:58
Sending on LPF/wlan0/00:1a:73:ff:50:58
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant

[n99]

Hello

I've been struggling with this for few days and have searched many posts and forums and hope posting here will help.

I've a dell inspiron 1525 with ubuntu 8.04/ vista dual boot and a WIRELESS DELL 1395 (802.B/G) MINI CARD F trying to connect to a netgear dg834g router using WPA-PSk. I've got WEP working on both OSs and WPA on vista but not on ubuntu.

I installed wireless drivers using these instructions...
http://ubuntuforums.org/showthread.php?t=405990&highlight=ndiswrapper

here is my outputs before restarting networking - hope the formatting works.

nome@nome-laptop:~$ sudo iwconfig

lo no wireless extensions.

eth0 no wireless extensions.

eth1 IEEE 802.11bg ESSID:"" Nickname:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Bit Rate:54 Mb/s Tx-Power:32 dBm
Retry min limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=5/5 Signal level=0 dBm Noise level=0 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

nome@nome-laptop:~$ sudo iwlist scan

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Scan completed :

Cell 04 - Address: 00:0F:B5:79:7F:74
ESSID:"n99"
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:5/5 Signal level:-41 dBm Noise level:-27 dBm
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s

nome@nome-laptop:~$ sudo cat /etc/network/interfaces

auto lo
iface lo inet loopback

auto eth1
iface eth1 inet dhcp
wpa-ssid n99
wpa-driver wext
wpa-proto WPA
wpa-ap-scan 1
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <my key>


then I restart

nome@nome-laptop:~$ sudo /etc/init.d/networking restart

* Reconfiguring network interfaces... There is already a pid file /var/run/dhclient.eth1.pid with pid 5970
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:1f:e1:c6:07:7a
Sending on LPF/eth1/00:1f:e1:c6:07:7a
Sending on Socket/fallback
DHCPRELEASE on eth1 to 192.168.0.1 port 67
There is already a pid file /var/run/dhclient.eth1.pid with pid 134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:1f:e1:c6:07:7a
Sending on LPF/eth1/00:1f:e1:c6:07:7a
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 4
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

I run iwconfig during the restart I can see something being picked up and then dropped for some reason and am not sure why....


nome@nome-laptop:~$ sudo iwconfig

lo no wireless extensions.

eth0 no wireless extensions.

eth1 IEEE 802.11bg ESSID:"n99" Nickname:""
Mode:Managed Frequency:2.462 GHz Access Point: 00:0F:B5:79:7F:74
Bit Rate=54 Mb/s Tx-Power:32 dBm
Retry min limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=5/5 Signal level=-40 dBm Noise level=-89 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

nome@nome-laptop:~$ sudo iwconfig

lo no wireless extensions.

eth0 no wireless extensions.

eth1 IEEE 802.11bg ESSID:"" Nickname:""
Mode:Managed Frequency:2.462 GHz Access Point: Not-Associated
Bit Rate:54 Mb/s Tx-Power:32 dBm
Retry min limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=5/5 Signal level=-40 dBm Noise level=-89 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


The above behavior is exhibited if I do this manually using the interfaces file or through the network manager applet.

Hope a ubuntu superhero can help!

cheeeeeeeeeeeeeers

n

[blizzardman1219]

michael@michael-desktop:~$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
link-local * 255.255.0.0 U 0 0 0 wlan1
default * 0.0.0.0 U 1000 0 0 wlan1

michael@michael-desktop:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan1 IEEE 802.11g ESSID:off/any
Mode:Managed Frequency:2.437 GHz Access Point: Not-Associated
Bit Rate:108 Mb/s
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

michael@michael-desktop:~$ sudo iwlist scan
[sudo] password for michael:
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan1 Failed to read scan data : Resource temporarily unavailable



michael@michael-desktop:~$ sudo lshw -C network
*-network
description: Ethernet interface
product: 88E8056 PCI-E Gigabit Ethernet Controller
vendor: Marvell Technology Group Ltd.
physical id: 0
bus info: pci@0000:02:00.0
logical name: eth0
version: 20
serial: 00:1c:25:4e:a5:ea
capacity: 1GB/s
width: 64 bits
clock: 33MHz
capabilities: pm vpd msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.20 firmware=N/A latency=0 link=no module=sky2 multicast=yes port=twisted pair
*-network
description: Wireless interface
physical id: 1
logical name: wlan1
serial: 00:1c:f0:a7:f6:8f
capabilities: ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+neta5agu driverversion=1.52+D-Link,05/08/2006,1.5.202.2 link=no multicast=yes wireless=IEEE 802.11g



michael@michael-desktop:~$ sudo cat /etc/network/interfaces
auto wlan1
iface wlan1 inet dhcp
wpa-driver wext
wpa-ssid blizzardman1219
wpa-ap-scan 1
wpa-proto WPA RSN
wpa-pairwise TKIP CCMP
wpa-group TKIP CCMP
wpa-key-mgmt WPA-PSK
wpa-psk (I put my psk here in hex, but I would rather not post it on a forum)



michael@michael-desktop:~$ sudo ifdown -v wlan1
Configuring interface wlan1=wlan1 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.wlan1.pid -lf /var/lib/dhcp3/dhclient.wlan1.leases wlan1
There is already a pid file /var/run/dhclient.wlan1.pid with pid 25297
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan1/00:1c:f0:a7:f6:8f
Sending on LPF/wlan1/00:1c:f0:a7:f6:8f
Sending on Socket/fallback
ifconfig wlan1 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
grep: /etc/resolv.conf: No such file or directory
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan1.pid
Stopped /sbin/wpa_supplicant (pid 25256).

michael@michael-desktop:~$ sudo ifup -v wlan1
Configuring interface wlan1=wlan1 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan1.pid -i wlan1 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan1
wpa_supplicant: wpa-ap-scan 1 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "blizzardman1219" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise TKIP CCMP -- OK
wpa_supplicant: wpa-group TKIP CCMP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto WPA RSN -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.wlan1.pid -lf /var/lib/dhcp3/dhclient.wlan1.leases wlan1
There is already a pid file /var/run/dhclient.wlan1.pid with pid 134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan1/00:1c:f0:a7:f6:8f
Sending on LPF/wlan1/00:1c:f0:a7:f6:8f
Sending on Socket/fallback
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 11
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
grep: /etc/resolv.conf: No such file or directory
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant michael@michael-desktop:~$ sudo ifup -v wlan1
Configuring interface wlan1=wlan1 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan1.pid -i wlan1 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan1
wpa_supplicant: wpa-ap-scan 1 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "blizzardman1219" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise TKIP CCMP -- OK
wpa_supplicant: wpa-group TKIP CCMP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto WPA RSN -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.wlan1.pid -lf /var/lib/dhcp3/dhclient.wlan1.leases wlan1
There is already a pid file /var/run/dhclient.wlan1.pid with pid 134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan1/00:1c:f0:a7:f6:8f
Sending on LPF/wlan1/00:1c:f0:a7:f6:8f
Sending on Socket/fallback
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 11
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
grep: /etc/resolv.conf: No such file or directory
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant


I've been trying to get this to work for like 3 months now, but it just isn't happening!!!

[crowolf]

I just bought a trendnet TEW-424UB:


wesley@kids-desktop:~$ lsusb
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 002: ID 0bda:8189 Realtek Semiconductor Corp.
Bus 001 Device 001: ID 0000:0000

I used the modified driver from here: http://www.datanorth.net/~cuervo/rtl8187b/.

After setting up my interfaces file:
And restarting networking, I get the following error:

Listening on LPF/wlan0/00:14:d1:48:1e:1c
Sending on LPF/wlan0/00:14:d1:48:1e:1c
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
No DHCPOFFERS received.
No working leases in persistent database - sleeping.[/CODE]

Did I grab the wrong driver, or did I set up my interfaces file incorrectly?

The modified rtl8187b driver you used requires ipw driver for encryption, so try to modify your intefaces file:



auto wlan0
iface wlan0 inet dhcp
wpa-driver ipw
wpa-ssid linksys
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk KEY_GOES_HERE

[SjRaptor]

Anyone else having problems like this?



Aug 16 19:23:32 thinker kernel: [ 5247.159835] ipw2200: Firmware error detected. Restarting.
Aug 16 19:23:32 thinker NetworkManager: <info> Supplicant state changed: 0
Aug 16 19:23:33 thinker NetworkManager: <info> Supplicant state changed: 1
Aug 16 19:23:33 thinker kernel: [11167.408622] ipw2200: Firmware error detected. Restarting.
Aug 16 19:23:34 thinker NetworkManager: <info> Supplicant state changed: 0
Aug 16 19:23:36 thinker NetworkManager: <info> Supplicant state changed: 1
Aug 16 19:23:37 thinker kernel: [ 5250.472882] ipw2200: Firmware error detected. Restarting.
Aug 16 19:23:37 thinker NetworkManager: <info> Supplicant state changed: 0
Aug 16 19:23:39 thinker NetworkManager: <info> Supplicant state changed: 1

My hardware was working perfect the week before, but now my laptop is bugging out.


02:02.0 Network controller: Intel Corporation PRO/Wireless 2200BG Network Connection (rev 05)
Subsystem: Intel Corporation Unknown device 2711
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64 (750ns min, 6000ns max), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 11
Region 0: Memory at c0214000 (32-bit, non-prefetchable) [size=4K]
Capabilities: <access denied>

[knedlyk]

Here is my experience with Wireless USB dongle (Wireless Pentagram WU61RL). It appeared has rt73 chip, so it was naturally to use precompiled kernel rt73usb module. I also compiled opensource driver from serialmonkey project (rt73). I have WPA2 wireless network and I thought, that for both drivers my /etc/network/interface setting was the same. But not everything is that easy. After some experiments I found usable configuration for both of them. Note, that I have static ip.

For rt73usb:


# WPA2 rt73usb
auto wlan0
iface wlan0 inet static
wpa-driver wext
wpa-ssid MYNETWORKNAME
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk GENERATED_BY_wpa-password_KEY
address 192.168.0.2
netmask 255.255.255.128
gateway 192.168.0.1


For rt73:


# WPA2 rt73
auto wlan0
iface wlan0 inet static
address 192.168.0.2
netmask 255.255.255.128
gateway 192.168.0.1
pre-up ifconfig wlan0 up
pre-up iwconfig wlan0 mode managed
pre-up iwconfig wlan0 essid MYNETWORKNAME
pre-up iwpriv wlan0 set AuthMode=WPA2PSK
pre-up iwpriv wlan0 set EncrypType=AES
pre-up iwpriv wlan0 set SSID=MYNETWORKNAME
pre-up iwpriv wlan0 set WPAPSK=MY_WIRELESS_WPA2_PASSWORD
pre-up iwpriv wlan0 set SSID=MYNETWORKNAME


Hope it will help someone.

[ktechman]

Does anyone have wireless working on a Toshiba A305-S6864? Wireless specs are Atheros AR9821 chipset with the ath9k driver.

[funnyveryfunny]

Hello,

Please help, I've tried hard but things are not going too well ... still no connection

Much appreciated if someone could point why I had failed. I hope the following info is enough to restart from the begining again otherwise please let me know:

///////////
ndiswrapper -l

lsmvnds : driver installed
device (11AB:1FAA) present

///////////
lshw -C network

*-network
description: 88W8300 802.11b Cardbus PC Card
product: 83
vendor: Marvell Semiconductor
physical id: 0
version: 01
slot: Socket 0
resources: irq:10
*-network DISABLED
description: Wireless interface
product: 88w8335 [Libertas] 802.11b/g Wireless
vendor: Marvell Technology Group Ltd.
physical id: 1
bus info: pci@0000:01:00.0
logical name: wlan0
version: 03
serial: 00:14:bf:d9:07:0f
width: 32 bits
clock: 66MHz
capabilities: pm bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+lsmvnds driverversion=1.52+Linksys,10/13/2004,3.1.0.36 latency=64 link=no module=ndiswrapper multicast=yes wireless=IEEE 802.11g

///////////////
ifconfig

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:192 (192.0 B) TX bytes:192 (192.0 B)

//////////////////
iwlist wlan0 scan

wlan0 Scan completed :
Cell 01 - Address: 00:1F:9F:15:1F:85
ESSID:"O2wirelessE2DB51"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:20/100 Signal level:-83 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 02 - Address: 00:1F:E2:C2:C5:AD
ESSID:"BTHomeHub2-N8JK"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:6/100 Signal level:-92 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
Cell 03 - Address: 00:1B:2F:A8:81:96
ESSID:"SKY66155"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:7/100 Signal level:-91 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 04 - Address: 00:1B:2F:A7:1C:9E
ESSID:"SKY78708"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:7/100 Signal level:-91 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 05 - Address: 00:1D:68:09:6B:FF
ESSID:"CUMMINGS5"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.442 GHz (Channel 7)
Quality:12/100 Signal level:-88 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 06 - Address: 00:1D:68:05:72:D3
ESSID:"BTHomeHub-323B"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.442 GHz (Channel 7)
Quality:7/100 Signal level:-91 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 07 - Address: 00:08:5C:AC:C6:B6
ESSID:"monkeyweb"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:76/100 Signal level:-47 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=200
Extra:atim=0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
Preauthentication Supported
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK

////////////////

'Cell 07' is my network.

I wonder whether '*-network DISABLED' is the main cause if so how do i fix it?

Many thanks

[knedlyk]

Looks like you don't have right wireless configuration. Try ifconfig wlan0 down and then ifconfig wlan0 up, and then try again lshw -C network just to check if "* network DISABLED" issue appeared.

[funnyveryfunny]

Thanks knedlyk, your advice had sorted it out the network DISABLED problem. I gave the howto another try but no lucl still, could you see why? Here is another dump:

*-network
description: 88W8300 802.11b Cardbus PC Card
product: 83
vendor: Marvell Semiconductor
physical id: 0
version: 01
slot: Socket 0
resources: irq:10
*-network
description: Wireless interface
product: 88w8335 [Libertas] 802.11b/g Wireless
vendor: Marvell Technology Group Ltd.
physical id: 1
bus info: pci@0000:01:00.0
logical name: wlan0
version: 03
serial: 00:14:bf:d9:07:0f
width: 32 bits
clock: 66MHz
capabilities: pm bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+lsmvnds driverversion=1.52+Linksys,10/13/2004,3.1.0.36 ip=192.168.1.18 latency=64 link=no module=ndiswrapper multicast=yes wireless=IEEE 802.11g


auto wlan0
iface wlan0 inet static
wpa-driver wext
wpa-ssid monkeyweb
wpa-conf managed
wpa-ap-scan 1
wpa-proto RSA
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk <generated psk key from ssid & my current router PSK key>
address 192.168.1.18
gateway 192.168.1.253
dns-nameservers 192.168.1.253
netmask 255.255.255.0

* Reconfiguring network interfaces... 
[ OK ]
wlan0 Link encap:Ethernet HWaddr 00:14:bf:d9:07:0f
inet addr:192.168.1.18 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:36 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:10 Memory:24010000-24020000

wlan0 IEEE 802.11g ESSID:off/any
Mode:Managed Frequency:2.462 GHz Access Point: Not-Associated
Bit Rate:1 Mb/s Sensitivity=-200 dBm
RTS thr=2346 B Fragment thr=2346 B
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

wlan0 No scan results


Do you know why?

[knedlyk]

I don't know. But I see you used wext driver for wpa_supplicant instead of ndiswrapper driver. You have to set wpa-driver ndiswrapper in your /etc/network/interfaces file.
BTW, I have never could make ndiswrapper drivers to work well. Only one exception was my laptop with Broadcom Wireless card, but in the latter ubuntu issue they work well with b43 kernel module.

Did you look on ndiswrapper site http://ndiswrapper.sourceforge.net/joomla/index.php?/component/option,com_openwiki/Itemid,33/id,list_m-n/ ?

[funnyveryfunny]

I did. Alos, I've managed to get network connection for a few seconds and all was lost again. Need to find out here...

[leopoldocosta]

Hi everyone, has many first timers i'm here trying to solve a problem.
I've recently installed ubuntu in my computer and i have a wireless card that should work alrite. its a DWL G510 something like that, i only care about the chipset anyway. below i'm posting more information about it.

I dont know why, i've tryied every single manual out there to get this thing going but i cant.

i have a wireless router with wpa/wpa2 tkip connection (wich is shown down here also) with a pre-shared key. its very near to the computer and also this installation is a fresh one.

can anyone help me getting this on? every time i configure all the steps the thing doesnt seem to connect... maybe its something about AES and TKIP.

################################################## ######################
## route
################################################## ######################
root@casa:~# route
Tabela de Roteamento IP do Kernel
Destino Roteador MáscaraGen. Opções Métrica Ref Uso Iface
192.168.2.0 * 255.255.255.0 U 0 0 0 ath0
192.168.2.0 * 255.255.255.0 U 0 0 0 eth0
link-local * 255.255.0.0 U 1000 0 0 eth0
################################################## ######################
## iwconfig
################################################## ######################
root@casa:~# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wifi0 no wireless extensions.

ath0 IEEE 802.11g ESSID:"GSL" Nickname:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Bit Rate:1 Mb/s Tx-Power:18 dBm Sensitivity=1/1
Retry:off RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=37/70 Signal level=-59 dBm Noise level=-96 dBm
Rx invalid nwid:11161 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
################################################## ######################
## iwlist scan
################################################## ######################
root@casa:~# iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wifi0 Interface doesn't support scanning.

ath0 Scan completed : // this is my router.. //
Cell 01 - Address: 00:01:E3:C3:4B:46
ESSID:"GSL"
Mode:Master
Frequency:2.412 GHz (Channel 1)
Quality=42/70 Signal level=-53 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Extra:bcn_int=100
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
Preauthentication Supported
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : TKIP CCMP
Authentication Suites (1) : PSK
Extra:wme_ie=dd180050f2020101000003a4000027a400004 2435e00623
22f00
Extra:ath_ie=dd0900037f0101000cff7f
################################################## ######################
## lshw -C network
################################################## ######################
root@casa:~# lshw -C network
*-network:0
description: Wireless interface
product: AR2413 802.11bg NIC
vendor: Atheros Communications Inc.
physical id: a
bus info: pci@0000:00:0a.0
logical name: wifi0
version: 01
serial: 00:17:9a:c7:69:6c
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=ath_pci ip=192.168.2.199 latency=168 maxlatency=28 mingnt=10 module=ath_pci multicast=yes wireless=IEEE 802.11g
*-network:1
description: Ethernet interface
product: VT6102 [Rhine-II]
vendor: VIA Technologies, Inc.
physical id: 12
bus info: pci@0000:00:12.0
logical name: eth0
version: 74
serial: 00:11:5b:74:6d:d6
size: 100MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=via-rhine driverversion=1.4.3 duplex=full ip=192.168.2.108 latency=32 link=yes maxlatency=8 mingnt=3 module=via_rhine multicast=yes port=MII speed=100MB/s
################################################## ######################
## cat /etc/network/interfaces
################################################## ######################
root@casa:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback


auto ath0
iface ath0 inet static
address 192.168.2.199
gateway 192.168.2.11
dns-nameservers 192.168.2.11
netmask 255.255.255.0
wpa-driver madwifi
wpa-ssid GSL
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 11d2c50c76d6381acd5e48264bd81bd1a965cdd54bfeb60744 5af16e1a31f437
################################################## ######################
## ifdown -v ath0
################################################## ######################
root@casa:~# ifdown -v ath0
Configuring interface ath0=ath0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/50firestarter
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/wpasupplicant
route del default gw 192.168.2.11 metric 100 ath0
ifconfig ath0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.ath0.pid
Stopped /sbin/wpa_supplicant (pid 14236).
run-parts: executing /etc/network/if-post-down.d/z50madwifi
################################################## ######################
## ifup -v ath0
################################################## ######################
root@casa:~# ifup -v ath0
Configuring interface ath0=ath0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/050madwifi
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver madwifi
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.ath0.pid -i ath0 -D madwifi -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/ath0
wpa_supplicant: wpa-ap-scan 2 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "GSL" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise CCMP -- OK
wpa_supplicant: wpa-group CCMP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto RSN -- OK
wpa_supplicant: enabling network block 0 -- OK

ifconfig ath0 192.168.2.199 netmask 255.255.255.0 up
route add default gw 192.168.2.11 metric 100 ath0
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/50firestarter
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant
################################################## ######################
##
################################################## ######################
root@casa:~# uname -a
Linux casa 2.6.24-19-generic #1 SMP Fri Jul 11 23:41:49 UTC 2008 i686 GNU/Linux
################################################## ######################
##
################################################## ######################
root@casa:~# cat /etc/resolv.conf
### BEGIN INFO
#
# Modified_by: NetworkManager
# Process: /usr/bin/NetworkManager
# Process_id: 4674
#
### END INFO



nameserver 192.168.2.11
################################################## ######################
## /etc/init.d/networking restart
################################################## ######################
root@casa:~# /etc/init.d/networking restart
* Reconfiguring network interfaces... RTNETLINK answers: No such process
There is already a pid file /var/run/dhclient.eth0.pid with pid 15150
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/eth0/00:11:5b:74:6d:d6
Sending on LPF/eth0/00:11:5b:74:6d:d6
Sending on Socket/fallback
DHCPRELEASE on eth0 to 192.168.2.11 port 67
There is already a pid file /var/run/dhclient.eth0.pid with pid 134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/eth0/00:11:5b:74:6d:d6
Sending on LPF/eth0/00:11:5b:74:6d:d6
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPOFFER of 192.168.2.108 from 192.168.2.11
DHCPREQUEST of 192.168.2.108 on eth0 to 255.255.255.255 port 67
DHCPACK of 192.168.2.108 from 192.168.2.11
bound to 192.168.2.108 -- renewal in 81066 seconds.

################################################## ######################
## bootmessages - dmesg
################################################## ######################
root@casa:~# dmesg
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.24-19-generic (buildd@terranova) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #1 SMP Fri Jul 11 23:41:49 UTC 2008 (Ubuntu 2.6.24-19.36-generic)
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
[ 0.000000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 000000000dff0000 (usable)
[ 0.000000] BIOS-e820: 000000000dff0000 - 000000000dff3000 (ACPI NVS)
[ 0.000000] BIOS-e820: 000000000dff3000 - 000000000e000000 (ACPI data)
[ 0.000000] BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
[ 0.000000] BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
[ 0.000000] BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
[ 0.000000] 0MB HIGHMEM available.
[ 0.000000] 223MB LOWMEM available.
[ 0.000000] found SMP MP-table at 000f5310
[ 0.000000] Entering add_active_range(0, 0, 57328) 0 entries of 256 used
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0 -> 4096
[ 0.000000] Normal 4096 -> 57328
[ 0.000000] HighMem 57328 -> 57328
[ 0.000000] Movable zone start PFN for each node
[ 0.000000] early_node_map[1] active PFN ranges
[ 0.000000] 0: 0 -> 57328
[ 0.000000] On node 0 totalpages: 57328
[ 0.000000] DMA zone: 32 pages used for memmap
[ 0.000000] DMA zone: 0 pages reserved
[ 0.000000] DMA zone: 4064 pages, LIFO batch:0
[ 0.000000] Normal zone: 415 pages used for memmap
[ 0.000000] Normal zone: 52817 pages, LIFO batch:15
[ 0.000000] HighMem zone: 0 pages used for memmap
[ 0.000000] Movable zone: 0 pages used for memmap
[ 0.000000] DMI 2.2 present.
[ 0.000000] ACPI: RSDP signature @ 0xC00F6CD0 checksum 0
[ 0.000000] ACPI: RSDP 000F6CD0, 0014 (r0 KM400 )
[ 0.000000] ACPI: RSDT 0DFF3000, 002C (r1 KM400 AWRDACPI 42302E31 AWRD 0)
[ 0.000000] ACPI: FACP 0DFF3040, 0074 (r1 KM400 AWRDACPI 42302E31 AWRD 0)
[ 0.000000] ACPI: DSDT 0DFF30C0, 4974 (r1 KM400 AWRDACPI 1000 MSFT 100000E)
[ 0.000000] ACPI: FACS 0DFF0000, 0040
[ 0.000000] ACPI: APIC 0DFF7A40, 005A (r1 KM400 AWRDACPI 42302E31 AWRD 0)
[ 0.000000] ACPI: PM-Timer IO Port: 0x4008
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[ 0.000000] Processor #0 6:8 APIC version 16
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
[ 0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 2, version 3, address 0xfec00000, GSI 0-23
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 dfl dfl)
[ 0.000000] ACPI: IRQ0 used by override.
[ 0.000000] ACPI: IRQ2 used by override.
[ 0.000000] ACPI: IRQ9 used by override.
[ 0.000000] Enabling APIC mode: Flat. Using 1 I/O APICs
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] Allocating PCI resources starting at 10000000 (gap: 0e000000:f0c00000)
[ 0.000000] swsusp: Registered nosave memory region: 000000000009f000 - 00000000000a0000
[ 0.000000] swsusp: Registered nosave memory region: 00000000000a0000 - 00000000000f0000
[ 0.000000] swsusp: Registered nosave memory region: 00000000000f0000 - 0000000000100000
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 56881
[ 0.000000] Kernel command line: root=UUID=6368746f-2074-616b-6f65-207575696400 ro quiet splash locale=pt_BR
[ 0.000000] mapped APIC to ffffb000 (fee00000)
[ 0.000000] mapped IOAPIC to ffffa000 (fec00000)
[ 0.000000] Enabling fast FPU save and restore... done.
[ 0.000000] Enabling unmasked SIMD FPU exception support... done.
[ 0.000000] Initializing CPU#0
[ 0.000000] PID hash table entries: 1024 (order: 10, 4096 bytes)
[ 0.000000] Detected 1494.110 MHz processor.
[ 11.043811] Console: colour VGA+ 80x25
[ 11.043816] console [tty0] enabled
[ 11.044075] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 11.044253] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 11.052267] Memory: 215428k/229312k available (2177k kernel code, 13408k reserved, 1006k data, 368k init, 0k highmem)
[ 11.052279] virtual kernel memory layout:
[ 11.052281] fixmap : 0xfff4b000 - 0xfffff000 ( 720 kB)
[ 11.052282] pkmap : 0xff800000 - 0xffc00000 (4096 kB)
[ 11.052284] vmalloc : 0xce800000 - 0xff7fe000 ( 783 MB)
[ 11.052286] lowmem : 0xc0000000 - 0xcdff0000 ( 223 MB)
[ 11.052288] .init : 0xc0421000 - 0xc047d000 ( 368 kB)
[ 11.052289] .data : 0xc0320474 - 0xc041bdc4 (1006 kB)
[ 11.052291] .text : 0xc0100000 - 0xc0320474 (2177 kB)
[ 11.052295] Checking if this processor honours the WP bit even in supervisor mode... Ok.
[ 11.052349] SLUB: Genslabs=11, HWalign=32, Order=0-1, MinObjects=4, CPUs=1, Nodes=1
[ 11.132339] Calibrating delay using timer specific routine.. 2991.85 BogoMIPS (lpj=5983708)
[ 11.132380] Security Framework initialized
[ 11.132389] SELinux: Disabled at boot.
[ 11.132414] AppArmor: AppArmor initialized
[ 11.132420] Failure registering capabilities with primary security module.
[ 11.132433] Mount-cache hash table entries: 512
[ 11.132603] Initializing cgroup subsys ns
[ 11.132609] Initializing cgroup subsys cpuacct
[ 11.132622] CPU: After generic identify, caps: 0383fbff c1cbfbff 00000000 00000000 00000000 00000000 00000000 00000000
[ 11.132634] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
[ 11.132638] CPU: L2 Cache: 256K (64 bytes/line)
[ 11.132642] CPU: After all inits, caps: 0383fbff c1cbfbff 00000000 00000420 00000000 00000000 00000000 00000000
[ 11.132656] Compat vDSO mapped to ffffe000.
[ 11.132672] Checking 'hlt' instruction... OK.
[ 11.148624] SMP alternatives: switching to UP code
[ 11.150070] Freeing SMP alternatives: 11k freed
[ 11.150257] Early unpacking initramfs... done
[ 11.587991] ACPI: Core revision 20070126
[ 11.588146] ACPI: Looking for DSDT in initramfs... error, file /DSDT.aml not found.
[ 11.592217] CPU0: AMD Sempron(tm) 2200+ stepping 01
[ 11.592254] Total of 1 processors activated (2991.85 BogoMIPS).
[ 11.593007] ENABLING IO-APIC IRQs
[ 11.593327] ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 11.740104] Brought up 1 CPUs
[ 11.740173] CPU0 attaching sched-domain:
[ 11.740177] domain 0: span 01
[ 11.740180] groups: 01
[ 11.740478] net_namespace: 64 bytes
[ 11.740488] Booting paravirtualized kernel on bare hardware
[ 11.741119] Time: 13:00:22 Date: 08/22/08
[ 11.741164] NET: Registered protocol family 16
[ 11.741478] EISA bus registered
[ 11.741515] ACPI: bus type pci registered
[ 11.746917] PCI: PCI BIOS revision 2.10 entry at 0xfb5e0, last bus=1
[ 11.746921] PCI: Using configuration type 1
[ 11.746927] Setting up standard PCI resources
[ 11.757340] ACPI: EC: Look up EC in DSDT
[ 11.762884] ACPI: Interpreter enabled
[ 11.762894] ACPI: (supports S0 S1 S4 S5)
[ 11.762918] ACPI: Using IOAPIC for interrupt routing
[ 11.769593] ACPI: PCI Root Bridge [PCI0] (0000:00)
[ 11.770024] PCI quirk: region 4000-407f claimed by vt8235 PM
[ 11.770029] PCI quirk: region 5000-500f claimed by vt8235 SMB
[ 11.770328] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[ 11.793270] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 6 7 10 *11 12)
[ 11.793460] ACPI: PCI Interrupt Link [LNKB] (IRQs *3 4 6 7 10 11 12)
[ 11.793653] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 6 7 *10 11 12)
[ 11.793840] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 6 7 10 11 12) *5
[ 11.793998] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 6 7 10 11 12) *0, disabled.
[ 11.794151] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 6 7 10 11 12) *0, disabled.
[ 11.794303] ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 6 7 10 11 12) *0, disabled.
[ 11.794455] ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 6 7 10 11 12) *0, disabled.
[ 11.794655] ACPI: PCI Interrupt Link [ALKA] (IRQs 20) *0
[ 11.794856] ACPI: PCI Interrupt Link [ALKB] (IRQs 21) *0
[ 11.795080] ACPI: PCI Interrupt Link [ALKC] (IRQs 22) *0
[ 11.795280] ACPI: PCI Interrupt Link [ALKD] (IRQs 23) *0
[ 11.795450] Linux Plug and Play Support v0.97 (c) Adam Belay
[ 11.795500] pnp: PnP ACPI init
[ 11.795512] ACPI: bus type pnp registered
[ 11.799405] pnp: PnP ACPI: found 13 devices
[ 11.799411] ACPI: ACPI bus type pnp unregistered
[ 11.799416] PnPBIOS: Disabled by ACPI PNP
[ 11.799790] PCI: Using ACPI for IRQ routing
[ 11.799795] PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
[ 11.828061] NET: Registered protocol family 8
[ 11.828064] NET: Registered protocol family 20
[ 11.828178] AppArmor: AppArmor Filesystem Enabled
[ 11.831986] Time: tsc clocksource has been installed.
[ 11.840042] system 00:00: iomem range 0xd0000-0xd3fff has been reserved
[ 11.840046] system 00:00: iomem range 0xf0000-0xf7fff could not be reserved
[ 11.840050] system 00:00: iomem range 0xf8000-0xfbfff could not be reserved
[ 11.840054] system 00:00: iomem range 0xfc000-0xfffff could not be reserved
[ 11.840058] system 00:00: iomem range 0xdff0000-0xdffffff could not be reserved
[ 11.840062] system 00:00: iomem range 0xffff0000-0xffffffff could not be reserved
[ 11.840066] system 00:00: iomem range 0x0-0x9ffff could not be reserved
[ 11.840070] system 00:00: iomem range 0x100000-0xdfeffff could not be reserved
[ 11.840073] system 00:00: iomem range 0xfec00000-0xfec00fff could not be reserved
[ 11.840077] system 00:00: iomem range 0xfee00000-0xfee00fff could not be reserved
[ 11.840081] system 00:00: iomem range 0xfff80000-0xfffeffff has been reserved
[ 11.840091] system 00:02: ioport range 0x4000-0x407f has been reserved
[ 11.840095] system 00:02: ioport range 0x5000-0x500f has been reserved
[ 11.840106] system 00:03: ioport range 0x4d0-0x4d1 has been reserved
[ 11.840109] system 00:03: ioport range 0x800-0x805 has been reserved
[ 11.840113] system 00:03: ioport range 0x290-0x297 has been reserved
[ 11.870743] PCI: Bridge: 0000:00:01.0
[ 11.870746] IO window: disabled.
[ 11.870752] MEM window: dc000000-ddffffff
[ 11.870756] PREFETCH window: d8000000-dbffffff
[ 11.870775] PCI: Setting latency timer of device 0000:00:01.0 to 64
[ 11.870792] NET: Registered protocol family 2
[ 11.908070] IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 11.908383] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
[ 11.908513] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[ 11.908637] TCP: Hash tables configured (established 8192 bind 8192)
[ 11.908641] TCP reno registered
[ 11.920125] checking if image is initramfs... it is
[ 12.371730] Switched to high resolution mode on CPU 0
[ 12.748841] Freeing initrd memory: 7275k freed
[ 12.749874] audit: initializing netlink socket (disabled)
[ 12.749897] audit(1219410022.592:1): initialized
[ 12.752837] VFS: Disk quotas dquot_6.5.1
[ 12.752949] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 12.753154] io scheduler noop registered
[ 12.753157] io scheduler anticipatory registered
[ 12.753160] io scheduler deadline registered
[ 12.753176] io scheduler cfq registered (default)
[ 12.753194] PCI: VIA PCI bridge detected. Disabling DAC.
[ 12.753258] Boot video device is 0000:01:00.0
[ 12.753669] isapnp: Scanning for PnP cards...
[ 13.107222] isapnp: No Plug & Play device found
[ 13.149636] Real Time Clock Driver v1.12ac
[ 13.149788] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
[ 13.149931] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 13.150827] 00:09: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 13.152306] RAMDISK driver initialized: 16 RAM disks of 65536K size 1024 blocksize
[ 13.152408] input: Macintosh mouse button emulation as /devices/virtual/input/input0
[ 13.152562] PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
[ 13.152984] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 13.152991] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 13.163337] mice: PS/2 mouse device common for all mice
[ 13.163517] EISA: Probing bus 0 at eisa.0
[ 13.163538] Cannot allocate resource for EISA slot 4
[ 13.163541] Cannot allocate resource for EISA slot 5
[ 13.163555] EISA: Detected 0 cards.
[ 13.163561] cpuidle: using governor ladder
[ 13.163563] cpuidle: using governor menu
[ 13.163769] NET: Registered protocol family 1
[ 13.163809] Using IPI No-Shortcut mode
[ 13.163856] registered taskstats version 1
[ 13.163965] Magic number: 4:6:29
[ 13.163981] hash matches device ttydc
[ 13.164238] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[ 13.164241] EDD information not available.
[ 13.164825] Freeing unused kernel memory: 368k freed
[ 13.191250] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1
[ 14.491744] fuse init (API version 7.9)
[ 14.518073] ACPI: Fan [FAN] (on)
[ 14.527355] ACPI: CPU0 (power states: C1[C1] C2[C2])
[ 14.726444] ACPI: Thermal Zone [THRM] (40 C)
[ 15.587881] usbcore: registered new interface driver usbfs
[ 15.587918] usbcore: registered new interface driver hub
[ 15.605882] usbcore: registered new device driver usb
[ 15.621867] USB Universal Host Controller Interface driver v3.0
[ 15.622375] ACPI: PCI Interrupt Link [ALKB] BIOS reported IRQ 0, using IRQ 21
[ 15.622380] ACPI: PCI Interrupt Link [ALKB] enabled at IRQ 21
[ 15.622391] ACPI: PCI Interrupt 0000:00:10.0[A] -> Link [ALKB] -> GSI 21 (level, low) -> IRQ 16
[ 15.622408] uhci_hcd 0000:00:10.0: UHCI Host Controller
[ 15.622804] uhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 1
[ 15.622848] uhci_hcd 0000:00:10.0: irq 16, io base 0x0000d000
[ 15.623065] usb usb1: configuration #1 chosen from 1 choice
[ 15.623102] hub 1-0:1.0: USB hub found
[ 15.623111] hub 1-0:1.0: 2 ports detected
[ 15.698120] SCSI subsystem initialized
[ 15.725955] ACPI: PCI Interrupt 0000:00:10.1[B] -> Link [ALKB] -> GSI 21 (level, low) -> IRQ 16
[ 15.725976] uhci_hcd 0000:00:10.1: UHCI Host Controller
[ 15.726022] uhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 2
[ 15.726052] uhci_hcd 0000:00:10.1: irq 16, io base 0x0000d400
[ 15.726216] usb usb2: configuration #1 chosen from 1 choice
[ 15.726250] hub 2-0:1.0: USB hub found
[ 15.726259] hub 2-0:1.0: 2 ports detected
[ 15.764712] via-rhine.c:v1.10-LK1.4.3 2007-03-06 Written by Donald Becker
[ 15.764722] via-rhine: Broken BIOS detected, avoid_D3 enabled.
[ 15.765605] libata version 3.00 loaded.
[ 15.829915] ACPI: PCI Interrupt 0000:00:10.2[C] -> Link [ALKB] -> GSI 21 (level, low) -> IRQ 16
[ 15.829936] uhci_hcd 0000:00:10.2: UHCI Host Controller
[ 15.829972] uhci_hcd 0000:00:10.2: new USB bus registered, assigned bus number 3
[ 15.830000] uhci_hcd 0000:00:10.2: irq 16, io base 0x0000d800
[ 15.830175] usb usb3: configuration #1 chosen from 1 choice
[ 15.830215] hub 3-0:1.0: USB hub found
[ 15.830224] hub 3-0:1.0: 2 ports detected
[ 15.898953] Floppy drive(s): fd0 is 1.44M
[ 15.917577] FDC 0 is a post-1991 82077
[ 15.933988] ACPI: PCI Interrupt 0000:00:10.3[D] -> Link [ALKB] -> GSI 21 (level, low) -> IRQ 16
[ 15.934012] ehci_hcd 0000:00:10.3: EHCI Host Controller
[ 15.934058] ehci_hcd 0000:00:10.3: new USB bus registered, assigned bus number 4
[ 15.934115] ehci_hcd 0000:00:10.3: irq 16, io mem 0xde010000
[ 15.945650] ehci_hcd 0000:00:10.3: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
[ 15.945844] usb usb4: configuration #1 chosen from 1 choice
[ 15.945881] hub 4-0:1.0: USB hub found
[ 15.945892] hub 4-0:1.0: 6 ports detected
[ 16.050297] ACPI: PCI Interrupt Link [ALKD] BIOS reported IRQ 0, using IRQ 23
[ 16.050304] ACPI: PCI Interrupt Link [ALKD] enabled at IRQ 23
[ 16.050315] ACPI: PCI Interrupt 0000:00:12.0[A] -> Link [ALKD] -> GSI 23 (level, low) -> IRQ 17
[ 16.054875] eth0: VIA Rhine II at 0xde011000, 00:11:5b:74:6d:d6, IRQ 17.
[ 16.055589] eth0: MII PHY found at address 1, status 0x786d advertising 05e1 Link 41e1.
[ 16.061932] ACPI: PCI Interrupt Link [ALKA] BIOS reported IRQ 0, using IRQ 20
[ 16.061939] ACPI: PCI Interrupt Link [ALKA] enabled at IRQ 20
[ 16.061949] ACPI: PCI Interrupt 0000:00:11.1[A] -> Link [ALKA] -> GSI 20 (level, low) -> IRQ 18
[ 16.062042] ACPI: PCI interrupt for device 0000:00:11.1 disabled
[ 16.068104] pata_via 0000:00:11.1: version 0.3.3
[ 16.068142] ACPI: PCI Interrupt 0000:00:11.1[A] -> Link [ALKA] -> GSI 20 (level, low) -> IRQ 18
[ 16.069734] scsi0 : pata_via
[ 16.071081] scsi1 : pata_via
[ 16.073505] ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xdc00 irq 14
[ 16.073510] ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xdc08 irq 15
[ 16.561834] ata1.00: ATA-6: ST340014A, 8.01, max UDMA/100
[ 16.561841] ata1.00: 78165360 sectors, multi 16: LBA48
[ 16.561867] ata1.01: ATAPI: HL-DT-ST GCE-8525B, 1.03, max UDMA/33
[ 16.577714] ata1.00: configured for UDMA/100
[ 16.741511] ata1.01: configured for UDMA/33
[ 16.908296] scsi 0:0:0:0: Direct-Access ATA ST340014A 8.01 PQ: 0 ANSI: 5
[ 16.909028] scsi 0:0:1:0: CD-ROM HL-DT-ST CD-RW GCE-8525B 1.03 PQ: 0 ANSI: 5
[ 16.922925] Driver 'sd' needs updating - please use bus_type methods
[ 16.923067] sd 0:0:0:0: [sda] 78165360 512-byte hardware sectors (40021 MB)
[ 16.923089] sd 0:0:0:0: [sda] Write Protect is off
[ 16.923093] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 16.923121] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 16.923192] sd 0:0:0:0: [sda] 78165360 512-byte hardware sectors (40021 MB)
[ 16.923209] sd 0:0:0:0: [sda] Write Protect is off
[ 16.923212] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 16.923236] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 16.923243] sda:<4>Driver 'sr' needs updating - please use bus_type methods
[ 16.937492] sda1 sda2
[ 16.957355] sd 0:0:0:0: [sda] Attached SCSI disk
[ 16.965854] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 16.965887] sr 0:0:1:0: Attached scsi generic sg1 type 5
[ 16.968978] sr0: scsi3-mmc drive: 40x/52x writer cd/rw xa/form2 cdda tray
[ 16.968989] Uniform CD-ROM driver Revision: 3.20
[ 16.969131] sr 0:0:1:0: Attached scsi CD-ROM sr0
[ 17.351243] Attempting manual resume
[ 17.351250] swsusp: Resume From Partition 8:2
[ 17.351253] PM: Checking swsusp image.
[ 17.351518] PM: Resume from disk failed.
[ 17.415384] kjournald starting. Commit interval 5 seconds
[ 17.415405] EXT3-fs: mounted filesystem with ordered data mode.
[ 25.991560] ndiswrapper version 1.52 loaded (smp=yes, preempt=no)
[ 26.819439] usbcore: registered new interface driver ndiswrapper
[ 27.075036] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 27.300142] Linux agpgart interface v0.102
[ 27.407159] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 27.490970] irda_init()
[ 27.491008] NET: Registered protocol family 23
[ 27.714914] agpgart: Detected VIA KM400/KM400A chipset
[ 27.723799] agpgart: AGP aperture is 128M @ 0xd0000000
[ 27.854875] input: PC Speaker as /devices/platform/pcspkr/input/input2
[ 28.084693] input: Power Button (FF) as /devices/virtual/input/input3
[ 28.095061] ACPI: Power Button (FF) [PWRF]
[ 28.095196] input: Power Button (CM) as /devices/virtual/input/input4
[ 28.106569] ACPI: Power Button (CM) [PWRB]
[ 29.106042] input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input5
[ 29.142034] parport_pc 00:0a: reported by Plug and Play ACPI
[ 29.142102] parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,ECP,DMA]
[ 30.499068] ACPI: PCI Interrupt Link [ALKC] BIOS reported IRQ 0, using IRQ 22
[ 30.499076] ACPI: PCI Interrupt Link [ALKC] enabled at IRQ 22
[ 30.499086] ACPI: PCI Interrupt 0000:00:11.5[C] -> Link [ALKC] -> GSI 22 (level, low) -> IRQ 19
[ 30.499234] PCI: Setting latency timer of device 0000:00:11.5 to 64
[ 34.451902] lp0: using parport0 (interrupt-driven).
[ 34.517780] Adding 1389612k swap on /dev/sda2. Priority:-1 extents:1 across:1389612k
[ 35.107603] EXT3 FS on sda1, internal journal
[ 36.720746] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 38.381346] No dock devices found.
[ 40.492926] apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac)
[ 40.492936] apm: overridden by ACPI.
[ 40.707003] ppdev: user-space parallel port driver
[ 41.054215] audit(1219410051.801:2): type=1503 operation="inode_permission" requested_mask="a::" denied_mask="a::" name="/dev/tty" pid=4760 profile="/usr/sbin/cupsd" namespace="default"
[ 42.323817] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
[ 42.504297] Bluetooth: Core ver 2.11
[ 42.505332] NET: Registered protocol family 31
[ 42.505341] Bluetooth: HCI device and connection manager initialized
[ 42.505347] Bluetooth: HCI socket layer initialized
[ 42.538260] Bluetooth: L2CAP ver 2.9
[ 42.538268] Bluetooth: L2CAP socket layer initialized
[ 42.652406] Bluetooth: RFCOMM socket layer initialized
[ 42.652439] Bluetooth: RFCOMM TTY layer initialized
[ 42.652442] Bluetooth: RFCOMM ver 1.8
[ 45.755583] [drm] Initialized drm 1.1.0 20060810
[ 45.849854] ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 20
[ 45.850131] [drm] Initialized via 2.11.1 20070202 on minor 0
[ 46.004638] NET: Registered protocol family 17
[ 46.060348] agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0.
[ 46.060372] agpgart: Device is in legacy mode, falling back to 2.x
[ 46.060379] agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode
[ 46.060424] agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode
[ 51.255209] NET: Registered protocol family 10
[ 51.255882] lo: Disabled Privacy Extensions
[ 61.491225] eth0: no IPv6 routers present
[ 230.053665] ath_hal: 0.9.18.0 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
[ 232.213415] wlan: 0.9.4
[ 232.237570] ath_pci: 0.9.4
[ 232.237962] ACPI: PCI Interrupt 0000:00:0a.0[A] -> GSI 18 (level, low) -> IRQ 21
[ 232.859053] ath_rate_sample: 1.2 (0.9.4)
[ 232.860819] wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
[ 232.860834] wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
[ 232.860845] wifi0: H/W encryption support: WEP AES AES_CCM TKIP
[ 232.860850] wifi0: mac 7.8 phy 4.5 radio 5.6
[ 232.860858] wifi0: Use hw queue 1 for WME_AC_BE traffic
[ 232.860861] wifi0: Use hw queue 0 for WME_AC_BK traffic
[ 232.860864] wifi0: Use hw queue 2 for WME_AC_VI traffic
[ 232.860867] wifi0: Use hw queue 3 for WME_AC_VO traffic
[ 232.860869] wifi0: Use hw queue 8 for CAB traffic
[ 232.860871] wifi0: Use hw queue 9 for beacons
[ 233.063717] wifi0: Atheros 5212: mem=0xde000000, irq=21
[ 233.115824] ACPI: PCI interrupt for device 0000:00:0a.0 disabled
[ 233.116126] ACPI: PCI Interrupt 0000:00:0a.0[A] -> GSI 18 (level, low) -> IRQ 21
[ 233.702769] wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
[ 233.702786] wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
[ 233.702797] wifi0: H/W encryption support: WEP AES AES_CCM TKIP
[ 233.702802] wifi0: mac 7.8 phy 4.5 radio 5.6
[ 233.702814] wifi0: Use hw queue 1 for WME_AC_BE traffic
[ 233.702816] wifi0: Use hw queue 0 for WME_AC_BK traffic
[ 233.702819] wifi0: Use hw queue 2 for WME_AC_VI traffic
[ 233.702822] wifi0: Use hw queue 3 for WME_AC_VO traffic
[ 233.702825] wifi0: Use hw queue 8 for CAB traffic
[ 233.702827] wifi0: Use hw queue 9 for beacons
[ 233.705652] wifi0: Atheros 5212: mem=0xde000000, irq=21
[ 244.405200] ath0: no IPv6 routers present
[ 357.191853] ath0: no IPv6 routers present
[ 358.646286] ADDRCONF(NETDEV_UP): ath0: link is not ready
[ 360.669452] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
[ 360.771250] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
[ 361.262379] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
[ 377.108113] eth0: no IPv6 routers present
[ 1181.596079] ADDRCONF(NETDEV_UP): ath0: link is not ready
[ 1372.748849] ADDRCONF(NETDEV_UP): ath0: link is not ready
[ 1393.165665] ADDRCONF(NETDEV_UP): ath0: link is not ready
[ 1403.254896] ADDRCONF(NETDEV_UP): ath0: link is not ready
[ 1443.698035] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
[ 1460.876044] eth0: no IPv6 routers present
[ 1486.159698] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
[ 1502.907688] eth0: no IPv6 routers present
[ 1676.975929] ADDRCONF(NETDEV_UP): ath0: link is not ready

[leopoldocosta]

I have another problem also with the card. After i tryied using ndiswrapper (and it didn't work, so i unninstalled it), the drivers won't load automaticly. I have to disable them and re-enable to make it work. every time.

[d.avid]

Hi!
My WLAN works fine when I start wpa_supplicant manually. I'd rather like to use the HowTo's variant with the /etc/network/interfaces, but it doesn't work.

/etc/network/interfaces


auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet static
address 192.168.178.22
gateway 192.168.178.1
dns-nameservers 192.168.178.1
netmask 255.255.255.0
wpa-driver wext
wpa-ssid Sub-Etha-Net
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 6dd5eccc9f814ec5567d13a4730d8312eccf6a0e4fec9aebff a7bd823f0cf


etc/wpa_supplicant/wpa_supplicant.conf


ctrl_interface=/var/run/wpa_supplicant

network={
ssid="Sub-Etha-Net"
proto=RSN
pairwise=CCMP
group=CCMP
key_mgmt=WPA-PSK
psk=6dd5eccc9f814ec5567d13a4730d8312eccf6a0e4fec9a ebffa7bd823f0cf
}


I think the problem is: The wpa-part of the interfaces file is not executed. I assume that's because the /etc/network/if-pre-up.d/wpasupplicant file is missing. (I compiled wpa_supplicant 5.10 from source)
Could anyone share his/her /etc/network/if-pre-up.d/wpasupplicant if that would work? Installing wpa_supplicant from the repos is not an option, it just won't work :/
Any help would be appreciated!

[jharkn]

Not having any joy trying to get my USR5422 usb adapter going (U.S. Robotics)..

I'm using ndiswrapper, the obligatory console output is below :)


jharkn@holly:~$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
link-local * 255.255.0.0 U 0 0 0 wlan0
default * 0.0.0.0 U 1000 0 0 wlan0


jharkn@holly:~$ iwconfig
lo no wireless extensions.

wlan0 IEEE 802.11g ESSID:"USR9110"
Mode:Managed Frequency:2.437 GHz Access Point: 00:C0:49:F2:CC:45
Bit Rate=24 Mb/s Tx-Power:18 dBm
RTS thr:2347 B Fragment thr:2346 B
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


jharkn@holly:~$ iwlist scan
lo Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:C0:49:F2:CC:45
ESSID:"USR9110"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:35/100 Signal level:-73 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=1
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK


jharkn@holly:~$ sudo lshw -C network
*-network
description: Wireless interface
physical id: 1
logical name: wlan0
serial: 00:c0:49:f3:46:f6
capabilities: ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+rsc4usb driverversion=1.53+U.S. Robotics,06/02/2005, 3 link=yes multicast=yes wireless=IEEE 802.11g


jharkn@holly:~$ sudo cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid USR9110
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk 326a53d91b1c963bd6096c722c695e1ab99f6c17b5a1754bd1 233dbd4143b9b1


jharkn@holly:~$ sudo ifdown -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 7844
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:c0:49:f3:46:f6
Sending on LPF/wlan0/00:c0:49:f3:46:f6
Sending on Socket/fallback
ifconfig wlan0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan0.pid
Stopped /sbin/wpa_supplicant (pid 7813).


jharkn@holly:~$ sudo ifup -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan0
wpa_supplicant: wpa-ap-scan 1 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "USR9110" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise TKIP -- OK
wpa_supplicant: wpa-group TKIP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto WPA -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:c0:49:f3:46:f6
Sending on LPF/wlan0/00:c0:49:f3:46:f6
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 1
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant

Any help would be greatly appreciated, thanks :)

[mssever]

Could anyone share his/her /etc/network/if-pre-up.d/wpasupplicant if that would work?I dunno if it will work for you (my wireless works with WPA with zero manual configuration. However, here's my wpasupplicant file:
#!/bin/sh

# Copyright (C) 2006 Debian/Ubuntu wpasupplicant Maintainers
# <pkg-wpa-devel@lists.alioth.debian.org>
#
# This program is free software; you can redistribute it and/or
# modify it under the terms of the GNU General Public License
# as published by the Free Software Foundation; either version 2
# of the License, or (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# On Debian GNU/Linux systems, the text of the GPL license can be
# found in /usr/share/common-licenses/GPL.

if [ -n "$IF_WPA_MAINT_DEBUG" ]; then
set -x
fi

# quit if we're called for the loopback
if [ "$IFACE" = lo ]; then
exit 0
fi

# allow wpa_supplicant interface to be specified via wpa-iface
# useful for starting wpa_supplicant on one interface of a bridge
if [ -n "$IF_WPA_IFACE" ]; then
WPA_IFACE="$IF_WPA_IFACE"
else
WPA_IFACE="$IFACE"
fi

# source functions
if [ -f /etc/wpa_supplicant/functions.sh ]; then
. /etc/wpa_supplicant/functions.sh
else
exit 0
fi

# quit if executables are not installed
if [ ! -x "$WPA_SUP_BIN" ] || [ ! -x "$WPA_CLI_BIN" ]; then
exit 0
fi

# quit if wpa_action is active
if test_wpa_cli; then
exit 0
fi

# preliminary sanity checks for roaming daemon
if [ -n "$IF_WPA_ROAM" ]; then
if [ "$METHOD" != "manual" ]; then
wpa_msg stderr "wpa-roam can only be used with the \"manual\" inet METHOD"
exit 1
fi
if [ -n "$IF_WPA_MAPPING_SCRIPT" ]; then
if ! type "$IF_WPA_MAPPING_SCRIPT" >/dev/null; then
wpa_msg stderr "wpa-mapping-script \"$IF_WPA_MAPPING_SCRIPT\" is not valid"
exit 1
fi
fi
if [ -n "$IF_WPA_MAPPING_SCRIPT_PRIORITY" ] && [ -z "$IF_WPA_MAPPING_SCRIPT" ]; then
wpa_msg stderr "\"wpa-mapping-script-priority 1\" is invalid without a wpa-mapping-script"
exit 1
fi
IF_WPA_CONF="$IF_WPA_ROAM"
WPA_ACTION_SCRIPT="/sbin/wpa_action"
fi

# master function; determines if ifupdown.sh should do something or not
if [ -n "$IF_WPA_CONF" ]; then
if [ ! -s "$IF_WPA_CONF" ]; then
wpa_msg stderr "cannot read contents of $IF_WPA_CONF"
exit 1
fi
WPA_SUP_CONF_CTRL_DIR=$(sed --quiet \
's/[[:space:]]*#.*//g;s/[[:space:]]\+.*$//g;s/^\(ctrl_interface\|DIR\)=\(.*\)/\2/p' "$IF_WPA_CONF")
if [ -n "$WPA_SUP_CONF_CTRL_DIR" ]; then
WPA_CTRL_DIR="$WPA_SUP_CONF_CTRL_DIR"
fi
WPA_SUP_CONF="-c $IF_WPA_CONF -C $WPA_CTRL_DIR"
elif set | grep --quiet "^IF_WPA"; then
WPA_SUP_CONF="-C $WPA_CTRL_DIR"
else
exit 0
fi

case "$MODE" in
start)
case "$PHASE" in
pre-up)
kill_wpa_supplicant
init_wpa_supplicant || exit 1
conf_wpa_supplicant || { kill_wpa_supplicant; exit 1; }
;;
post-up)
init_wpa_cli || { kill_wpa_supplicant; exit 1; }
;;
esac
;;

stop)
case "$PHASE" in
pre-down)
kill_wpa_cli
;;
post-down)
kill_wpa_supplicant
;;
*)
wpa_msg stderr "unknown phase: \"$PHASE\""
exit 1
;;
esac
;;

*)
wpa_msg stderr "unknown mode: \"$MODE\""
exit 1
;;
esac

exit 0It's actually a symlink to /etc/wpa_supplicant/ifupdown.sh, which is owned by root:root and has permissions 0755.

[d.avid]

It's actually a symlink to /etc/wpa_supplicant/ifupdown.sh, which is owned by root:root and has permissions 0755.

Great! That's the information I needed, thanks a lot!

[Faz1]

Some users reported (including myself) that the network has to be restarted every time after startup... Apparently this is a bug.

Here is a workaround that helps restart the network during boot so that one does not have to do it manually after logging on to the system.

Create startup script:

Add this line & save file:

Change permission (executable):

Create symbolic link:

[Note: You may have to choose a boot sequence other than S40.]

Restart...

Worked a treat! Thank you wieman01! =D>
I can finally reboot remotely! :)

[showcaser]

Hello,

i've got a pci wireless card in my desktop and have been trying for quite some time to get it working with WPA. Works fine with WEP and unsecured. I'm using NDISWRAPPER and am on a fresh install of Hardy 32. Using DHCP I get "no offers received" and so i'm now configured with a static IP. No problems/errors after running sudo /etc/init.d/networking restart but opening up a browser i'm still not connected.

Any help that can be offered would be greatly appreciated as i'd really like to get this working.

Thanks

Here's some info, let me know if you need more:


lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:"Jones"
Mode:Managed Frequency:2.452 GHz Access Point: 00:18:F8:EB:9B:B6
Bit Rate=270 Mb/s Tx-Power:32 dBm
RTS thr:2347 B Fragment thr:2346 B
Power Management:off
Link Quality:60/100 Signal level:-57 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0



Cell 10 - Address: 00:18:F8:EB:9B:B6
ESSID:"Jones"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.452 GHz (Channel 9)
Quality:54/100 Signal level:-61 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK




*-network DISABLED
description: Ethernet interface
product: 82547EI Gigabit Ethernet Controller
vendor: Intel Corporation
physical id: 1
bus info: pci@0000:02:01.0
logical name: eth0
version: 00
serial: 00:0e:a6:55:01:08
capacity: 1GB/s
width: 32 bits
clock: 66MHz
capabilities: pm bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e1000 driverversion=7.3.20-k2-NAPI firmware=N/A latency=0 link=no mingnt=255 module=e1000 multicast=yes port=twisted pair
*-network
description: Wireless interface
product: BCM43XG
vendor: Broadcom Corporation
physical id: d
bus info: pci@0000:03:0d.0
logical name: wlan0
version: 01
serial: 00:1a:70:3c:25:36
width: 32 bits
clock: 33MHz
capabilities: bus_master ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+bcmwl5 driverversion=1.52+Linksys, A Division of Cisc ip=192.168.1.130 latency=64 link=yes module=ndiswrapper multicast=yes wireless=IEEE 802.11g




showcaser@showcaser-desktop:~$ sudo cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet static
wpa-driver wext
address 192.168.1.130
gateway 192.168.1.1
dns-nameservers 192.168.1.1
netmask 255.255.255.0
broadcast 192.168.1.255
wpa-ssid Jones
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk 0fec690f80676366e185cd6f5d13144faa8d8e923ed419a2cc 29d6136836907f



showcaser@showcaser-desktop:~$ sudo ifdown -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/wpasupplicant
route del default gw 192.168.1.1 metric 100 wlan0
ifconfig wlan0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan0.pid
Stopped /sbin/wpa_supplicant (pid 6630).
showcaser@showcaser-desktop:~$ sudo ifup -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan0
wpa_supplicant: wpa-ap-scan 1 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "Jones" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise TKIP -- OK
wpa_supplicant: wpa-group TKIP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto WPA -- OK
wpa_supplicant: enabling network block 0 -- OK

ifconfig wlan0 192.168.1.130 netmask 255.255.255.0 broadcast 192.168.1.255 up
route add default gw 192.168.1.1 metric 100 wlan0
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant

[wieman01]

@showcaser:

What happens when you do:

route
After restarting the network.

[Ziggy8.04]

ive tryed to set up my bcm4328 im using hardy heron
i followed this how to and havent been successful so far.
im able to connect to unsecured wireless networks
but i need to be able to connect to a secure network
with at least wpa. i would really appreciate it if someone
could help me im new to linux so i dont realy know what to do.
ive posted my results before but here they are again

ubuntu@ubuntu:~$ route

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
link-local * 255.255.0.0 U 0 0 0 wlan0
link-local * 255.255.0.0 U 0 0 0 eth0
link-local * 255.255.0.0 U 1000 0 0 wlan0
default * 0.0.0.0 U 1000 0 0 wlan0


ubuntu@ubuntu:~$ iwconfig

lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:"0987654321"
Mode:Managed Frequency:2.412 GHz Access Point: 00:1E:E5:4F:CD:FD
Bit Rate=130 Mb/s Tx-Power:32 dBm
RTS thr:2347 B Fragment thr:2346 B
Power Management:off
Link Quality:79/100 Signal level:-45 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:71 Invalid misc:13748 Missed beacon:0


ubuntu@ubuntu:~$ sudo iwlist scan

[sudo] password for ubuntu:
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:1E:E5:4F:CD:FD
ESSID:"0987654321"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:71/100 Signal level:-50 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 02 - Address: 00:1C:10:28:73:20
ESSID:"Tigress74"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:71/100 Signal level:-50 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 03 - Address: 00:0F:66:CC:28:80
ESSID:"linksys"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:28/100 Signal level:-78 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 04 - Address: 00:1E:2A:51:1E:B8
ESSID:"MEGAAHHHN"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:17/100 Signal level:-85 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 05 - Address: 00:1C:DF:8C:C7:37
ESSID:"Belkin_G_Plus_MIMO_8CC737"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:10/100 Signal level:-89 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 9 Mb/s
18 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 12 Mb/s
24 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0


ubuntu@ubuntu:~$ sudo lshw -C network

*-network
description: Wireless interface
product: BCM4328 802.11a/b/g/n
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:03:00.0
logical name: wlan0
version: 03
serial: 00:1a:73:ff:50:58
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+bcmwl5 driverversion=1.52+Broadcom,10/12/2006, 4.100. latency=0 link=no module=ndiswrapper multicast=yes wireless=IEEE 802.11g


ubuntu@ubuntu:~$ sudo cat /etc/network/interfaces

auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid 0987654321
wpa-ap-scan 1
wpa-proto WPA RSN
wpa-pairwise TKIP CCMP
wpa-group TKIP CCMP
wpa-key-mgmt WPA-PSK
wpa-psk <password>


ubuntu@ubuntu:~$ sudo ifdown -v wlan0

Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 5784
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:1a:73:ff:50:58
Sending on LPF/wlan0/00:1a:73:ff:50:58
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 192.168.2.1 port 67
ifconfig wlan0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan0.pid
Stopped /sbin/wpa_supplicant (pid 4823).


ubuntu@ubuntu:~$ sudo ifup -v wlan0

Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan0
wpa_supplicant: wpa-ap-scan 1 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "0987654321" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise TKIP CCMP -- OK
wpa_supplicant: wpa-group TKIP CCMP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto WPA RSN -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 0
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:1a:73:ff:50:58
Sending on LPF/wlan0/00:1a:73:ff:50:58
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant

any help would be much appreciated

[showcaser]

@showcaser:

What happens when you do: route

After restarting the network.

Here is the route info:


showcaser@showcaser-desktop:~$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 wlan0
link-local * 255.255.0.0 U 1000 0 0 wlan0
default 192.168.1.1 0.0.0.0 UG 100 0 0 wlan0

Just for fun I also tried using Wicd on a fresh install. Wicd with DHCP did the same thing as the manual way (never gets an DHCP offer). Entering static values it then connected, well at least it thought it was connected (with the connection quality meter bar and all) but still no internet and was unable to ping across the network.

I imagine it has something to do with the combination of my particular broadcom chip (BCM43XG aka 4329), the windows driver, and ndiswrapper compatibility. I'm using the latest driver for XP from the linksys website, and have tried others to no avail.

Thanks for your help Wieman01.

[showcaser]

Holy s$%t, got it to work finally after way to many hours. Ends up it was because the router was set to Mixed-mode (it's a draft-n router). I changed the router to BG-only and presto it worked right away, no problems at all. In all the forums and all the similar posts where people complained of wpa issues with their 4328/4329 routers no where was it mentioned that this could be the issue. I noticed that one person mentioned (in a post in another thread) that ndiswrapper doesn't support draft-n so I disabled it on a whim and presto. Kind of weird as it connects fine when unsecured :confused:

Zhiggy 8.04 can this be your problem. I was getting the same "No DHCPOFFERS received" issue.

Wieman01 it may be worth mentioning "Set router to BG-Only if using ndiswrapper (and perhaps Broadcom 43xx as I don't know about others)" in the "stumbling blocks" portion at the top of the how-to.

Thanks

[Ziggy8.04]

WOW!!!!!
\\:D/
thanks showcaser
that was it was my router was set to mixed mode
works fine so far when its set to b and g only
:popcorn:

[wieman01]

Holy s$%t, got it to work finally after way to many hours. Ends up it was because the router was set to Mixed-mode (it's a draft-n router). I changed the router to BG-only and presto it worked right away, no problems at all. In all the forums and all the similar posts where people complained of wpa issues with their 4328/4329 routers no where was it mentioned that this could be the issue. I noticed that one person mentioned (in a post in another thread) that ndiswrapper doesn't support draft-n so I disabled it on a whim and presto. Kind of weird as it connects fine when unsecured :confused:

Zhiggy 8.04 can this be your problem. I was getting the same "No DHCPOFFERS received" issue.

Wieman01 it may be worth mentioning "Set router to BG-Only if using ndiswrapper (and perhaps Broadcom 43xx as I don't know about others)" in the "stumbling blocks" portion at the top of the how-to.

Thanks
Thanks, buddy. Done so. :-)

[showcaser]

WOW!!!!!
\\:D/
thanks showcaser
that was it was my router was set to mixed mode
works fine so far when its set to b and g only
:popcorn:

I'm happy it worked for you Ziggy!

Thanks for adding the info Wieman01!

[raoulteeuwen]

Thanks, this thread (first post) helped me getting WPA2 working on my Acer Travelmate 4001WLMi with Ubuntu 7.10 Gutsy Gibbon! I left it to DHCP, might cost a few extra seconds, but it is working! I wish the Ubuntu-people would include a "restart network"-button in the network-interface (maybe as well as an ifconfig-button). Thanks again!

[ialexei]

wicd is the way to go.
I could never set WPA2 to stick , it would always revert back to WPA after I click close on the networking dialog.

I wish Xubuntu guys either fix it or add wicd into the distro. wicd is also much cleaner looking UI.

[_iridium_]

Thanks wieman01 for this post!!!

However, I'm not able to run 100% the wireless following your instructions....:confused:

I'm using:
- Ubuntu 8.04
- Broadcom Corporation BCM4311 802.11b/g WLAN (rev 01) ----> Using new B43 driver
- WPA-TKIP encryption, SMC Router.....

Works perfect with the following configuration if the ESSID is broadcasted


auto eth1
iface eth1 inet static
address 192.168.0.4
netmask 255.255.255.0
gateway 192.168.0.1
wpa-driver wext
#wpa-conf managed
wpa-ssid Iridium
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk e5c88e453bf74af034679355c34afad11e53f2524f388d3857 f4dc6a420b1f5f

Doesn't works with the following configuration if the ESSID is hidden....


auto eth1
iface eth1 inet static
address 192.168.0.4
netmask 255.255.255.0
gateway 192.168.0.1
wpa-driver wext
#wpa-conf managed
wpa-ssid Iridium
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk e5c88e453bf74af034679355c34afad11e53f2524f388d3857 f4dc6a420b1f5f


Anybody, What the f%$k could be happening? :(
It's all the same........just changed '1' for '2'


Thanks in advance,
Iridium.

[wieman01]

Thanks wieman01 for this post!!!

However, I'm not able to run 100% the wireless following your instructions....:confused:

I'm using:
- Ubuntu 8.04
- Broadcom Corporation BCM4311 802.11b/g WLAN (rev 01) ----> Using new B43 driver
- WPA-TKIP encryption, SMC Router.....

Works perfect with the following configuration if the ESSID is broadcasted


auto eth1
iface eth1 inet static
address 192.168.0.4
netmask 255.255.255.0
gateway 192.168.0.1
wpa-driver wext
#wpa-conf managed
wpa-ssid Iridium
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk e5c88e453bf74af034679355c34afad11e53f2524f388d3857 f4dc6a420b1f5f

Doesn't works with the following configuration if the ESSID is hidden....


auto eth1
iface eth1 inet static
address 192.168.0.4
netmask 255.255.255.0
gateway 192.168.0.1
wpa-driver wext
#wpa-conf managed
wpa-ssid Iridium
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk e5c88e453bf74af034679355c34afad11e53f2524f388d3857 f4dc6a420b1f5f


Anybody, What the f%$k could be happening? :(
It's all the same........just changed '1' for '2'


Thanks in advance,
Iridium.
Just broadcast your SSID as it adds no extra security if you hide it. Some wireless drivers might not be capable of coping with it...

[raoulteeuwen]

@Wieman: why is it that broadcasting your SSID doesn't weaken your security? I would think it is easier for a hacker when they see what wlan's are around. Or is the SSID to be sniffed, whether or not you broadcast it?

I ask this as i reported 5 days earlier i got wpa2 working thanks to this thread, but i found out Ubuntu somehow forgot ... my wlan isn't working anymore, so i have to find out why (and maybe it is because ssid-broadcasting is turned off)

[wieman01]

@Wieman: why is it that broadcasting your SSID doesn't weaken your security? I would think it is easier for a hacker when they see what wlan's are around. Or is the SSID to be sniffed, whether or not you broadcast it?

I ask this as i reported 5 days earlier i got wpa2 working thanks to this thread, but i found out Ubuntu somehow forgot ... my wlan isn't working anymore, so i have to find out why (and maybe it is because ssid-broadcasting is turned off)
The clients broadcast it anyway and any wireless security tool (e.g. Aircrack) lets you sniff it.

Read this article on SSID broadcast for more:

http://blogs.technet.com/steriley/archive/2007/10/16/myth-vs-reality-wireless-ssids.aspx

That explains what I have been just saying.

[Trash_Gordon]

Hi,
I'm using a Ralink rt61-Chipset card which is working fine, but when I got a new wireless network I wanted to connect to, it doesn't work. Here's relevant output:
http://nopaste.debianforum.de/11520

PS: I'm using Debian lenny, but there shouldn't be much of a difference to Ubuntu, right?

/edit: Problem solved, wrong IP allocation.

[anindya_m]

Hi. I am (still!) running Feisty Fawn on my laptop because everything works fine, touch wood. I have set up my wireless interface to be configured manually at boot time (while at home or at work; I use networkmanager if I am at a public place). It is important sometimes to have the wireless interface come up automatically at boot without a network services restart, because some programs like ntpd require it. This is why networkmanager is not useful in such a situation, as it sets up the network after login. It is also not nice (inelegant) to have to tinker with system startup scripts.

So, all was fine while I had an old router with WEP encryption, as network-admin could be used to update the /etc/network/interfaces file. This changed when I got a new router (the old one died) and set it up with WPA2. It turns out that the Feisty version of network-admin does not have a WPA option - it's a bug which has been fixed in the later releases.

I therefore was trying to use wpa_supplicant to manually set up my interfaces file. The logic is: whenever I need to use the manual method I would simply disable networking in nm, overwrite the interfaces file with the manual version (which is what network-admin used to do in the WEP case), and then re enable networking in nm. This would cause networkmanager to stop managing the wifi - the trigger is the appearance of the "auto eth1" line. To switch back to automatic mode, I would follow the same steps, but now replace the interfaces file with one which does not have a "eth1" stanza.

I initially tried to put everything in the interfaces file as mentioned in this (excellent) howto, but was very annoyed at having to restart networking and then ntpd every time. So I moved the configuration to wpa_supplicant.conf. Here are my files:

/etc/network/interfaces.atboot (this will be copied as /etc/network/interface for manual configuration):

auto lo eth1

iface lo inet loopback

iface eth1 inet dhcp
pre-up /sbin/wpa_supplicant -Bw -Dwext -ieth1 -dd -c/etc/wpa_supplicant/wpa_supplicant.conf
post-down killall -q wpa_supplicant



/etc/network/interfaces.nm (this will be copied as /etc/network/interface for automatic configuration by nm):

auto lo

iface lo inet loopback



/etc/wpa_supplicant/wpa_supplicant.conf:

ctrl_interface=/var/run/wpa_supplicant

network={
ssid="secret"
scan_ssid=1
proto=WPA2
key_mgmt=WPA-PSK
pairwise=CCMP
group=TKIP
psk=some_hex_code
}



With these changes everything works perfectly - no need to restart networking. I think moving the configuration to wpa_supplicant.conf is not so bad because if you have many networks (home, office, friend's place, etc.) where you want wireless to be enabled at boot time you can put all these in the conf file and have a clean and uncluttered interfaces file which just selects manual or automatic (nm) mode. wpa_supplicant then selects a network (while in manual mode) from the conf file depending on signal strengths. Note that wpa_supplicant also supports plain old WEP networks as well, and it is very easy to set up, but for some strange reason the man page has very little to say about this (they might be trying to discourage people from using WEP).

Hope this is useful. Thanks again to wieman01 for a very useful howto.

[ethx]

Thank you so much dude.. got it to work flawlessly.

[master2010]

http://ubuntuforums.org/showthread.php?p=5893031#post5893031

[LinuxGuy80]

Hi.
Thank you for this guide it works great.
One problem though, after about 30 minutes or so of use i lose my network connection and i can't get it back without restarting my computer.
Any idea why this happens?
Thanks in advance.

[wieman01]

Hi.
Thank you for this guide it works great.
One problem though, after about 30 minutes or so of use i lose my network connection and i can't get it back without restarting my computer.
Any idea why this happens?
Thanks in advance.
Try to use another wireless channel.

[LinuxGuy80]

Didn't work.
I had to use ndiswrapper for my wifi card if that helps.
It's a realtek8185.
Do you think it has anything to do with my encryption?
It's Wpa.
Here is what is my /etc/network/interfaces.
Don't know if it will help.


auto lo
iface lo inet loopback


auto wlan0
iface wlan0 inet dhcp


wpa-ap-scan 1
wpa-pairwise TKIP
wpa-group TKIP
wpa-psk xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
wpa-driver wext
wpa-key-mgmt WPA-PSK
wpa-proto WPA
wpa-ssid xxxx

[wieman01]

I don't think it's an issue with encryption. What router have you got? Is there a setting called "beacon interval" and what's the current value?

[LinuxGuy80]

It's a cheap Belkin Wireless Router. I think it cost me $40.;)
It had no option for Beacon Interval.
Another thing that's weird, when i have my Cat5 cable plugged in sometimes i have to restart my network because it will hang.
You think my cheap router my be the problem?
By the way thank you for all the help.:D

[wieman01]

It's a cheap Belkin Wireless Router. I think it cost me $40.;)
It had no option for Beacon Interval.
Another thing that's weird, when i have my Cat5 cable plugged in sometimes i have to restart my network because it will hang.
You think my cheap router my be the problem?
By the way thank you for all the help.:D
Hard to tell what the issue is, but you could try another router and do some testing.

[LinuxGuy80]

Cool thanks for the help.

[MattTeddy]

This may sound like one of the stupidest questions you will ever hear, but why do I get these results when typing "iwconfig":

$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:off/any
Mode:Managed Frequency:2.462 GHz Access Point: Not-Associated
Bit Rate:54 Mb/s Tx-Power:32 dBm
RTS thr:2347 B Fragment thr:2346 B
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


This is really starting to get to me now because I've been picking through articles for 2 days now and yours looks like it will work..

I am using a hidden SSID and also WPA2 protection.
Any help appreciated.

Matt

[geezerone]

Have you tried NOT hiding your ESSID as this is often doesn't work in Ubuntu and has little effect against hackers?

[Moncho12]

wieman01,

Thanks you very much for a great comprehensive "howto" on wifi connectivity!

Cheers.....

[samwisgg]

Some users reported (including myself) that the network has to be restarted every time after startup... Apparently this is a bug.

Here is a workaround that helps restart the network during boot so that one does not have to do it manually after logging on to the system.

Create startup script:

Add this line & save file:

Change permission (executable):

Create symbolic link:

[Note: You may have to choose a boot sequence other than S40.]

Restart...

Wieman01,

what you described works but you should add the line '/etc/init.d/networking restart' to the already existing script /etc/rc.local. This script is meant to hold customizations at boot up and it's called after all other scripts.

[MistressSheena]

I followed this guide and it worked for my laptop. But after I shut down and started back up, the internet didn't work anymore. Also when I try to restart the network, my lappy freezes. Weird.

[cb474]

What would be the protocol just for a simple wep connection with a passphrase, not using any special other elements (leap, ttls, etc.)?

Also, can I put more than one entry in the interfaces file, for different access points?

[wieman01]

What would be the protocol just for a simple wep connection with a passphrase, not using any special other elements (leap, ttls, etc.)?

Also, can I put more than one entry in the interfaces file, for different access points?
See this for more:

http://ubuntuforums.org/showthread.php?t=571188

[wieman01]

Interesting read for all security nerds:

http://www.itworld.com/security/57285/once-thought-safe-wpa-wi-fi-encryption-cracked

[Cammy]

Well, I've done the auto update from 6.10 to 8.04 on my laptop, and now my wireless is hosed again, and the trick I used last time isn't working.

It's very annoying that there can't just be a GUI that I can use to connect to my wireless network. It seems like whenever I switch from my home wireless to a different wireless, I have to go through all this all over again.

EDIT: Ok, I got it working. I hard-wired it to my router and let Hardy update itself. After doing so, I got the reboot icon, so I rebooted, and found that restricted drivers had been installed for my wireless card. After that, I was able to get it working with a bit of fiddling, and it holds after a reboot.

It's still very annoying that it's this much of a pain! heh. Oh well.

[wieman01]

Well, I've done the auto update from 6.10 to 8.04 on my laptop, and now my wireless is hosed again, and the trick I used last time isn't working.

It's very annoying that there can't just be a GUI that I can use to connect to my wireless network. It seems like whenever I switch from my home wireless to a different wireless, I have to go through all this all over again.

EDIT: Ok, I got it working. I hard-wired it to my router and let Hardy update itself. After doing so, I got the reboot icon, so I rebooted, and found that restricted drivers had been installed for my wireless card. After that, I was able to get it working with a bit of fiddling, and it holds after a reboot.

It's still very annoying that it's this much of a pain! heh. Oh well.
:-)

[Cammy]

:-)

That's easy for you to say!

[wieman01]

That's easy for you to say!
Nah... it just reminds me of what I had to go through in the past... I am more than with you. Every upgrade comes with its own set of suprises. Every time. :-)

[kannedheat]

I tried, but I still can't connect my wireless:


route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 wlan0
link-local * 255.255.0.0 U 0 0 0 eth0
iwconfig
default 192.168.1.1 0.0.0.0 UG 100 0 0 wlan0

iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11bg ESSID:"Zapper"
Mode:Managed Frequency:2.437 GHz Access Point: Not-Associated
Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

pan0 no wireless extensions.


sudo iwlist
[sudo] password for kannedheat:

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wmaster0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:E0:98:DB:D6:65
ESSID:"Zapper"
Mode:Master
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=46/100 Signal level:-66 dBm Noise level=-73 dBm
Encryption key:on
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:tsf=000000f5ea61e122
Extra: Last beacon: 120ms ago
Cell 02 - Address: 00:1D:7E:E8:26:A1
ESSID:"PC Serv"
Mode:Master
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=30/100 Signal level:-83 dBm Noise level=-73 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:tsf=000003dc88144a78
Extra: Last beacon: 404ms ago
Cell 03 - Address: 00:1C:F0:57:3E:C3
ESSID:"xbox360"
Mode:Master
Channel:8
Frequency:2.447 GHz (Channel 8)
Quality=35/100 Signal level:-78 dBm Noise level=-73 dBm
Encryption key:off
IE: Unknown: 2D1A6E101EFFFF000000000000000000000000000004000000 000000
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=000002a73b246345
Extra: Last beacon: 300ms ago
Cell 04 - Address: 00:1B:2F:65:31:34
ESSID:"NETGEAR"
Mode:Master
Channel:11
Frequency:2.462 GHz (Channel 11)
Quality=31/100 Signal level:-81 dBm Noise level=-73 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=000009fdd60f9181
Extra: Last beacon: 60ms ago

pan0 Interface doesn't support scanning.


sudo lshw -C network
*-network:0
description: Network controller
product: BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller
vendor: Broadcom Corporation
physical id: 2
bus info: pci@0000:06:02.0
version: 02
width: 32 bits
clock: 33MHz
capabilities: bus_master
configuration: driver=b43-pci-bridge latency=64 module=ssb
*-network:1
description: Ethernet interface
product: RTL-8139/8139C/8139C+
vendor: Realtek Semiconductor Co., Ltd.
physical id: 6
bus info: pci@0000:06:06.0
logical name: eth0
version: 10
serial: 00:0f:b0:be:ea:6a
size: 10MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=8139too driverversion=0.9.28 duplex=half latency=128 link=no maxlatency=64 mingnt=32 module=8139too multicast=yes port=MII speed=10MB/s
*-network:0
description: Wireless interface
physical id: 2
logical name: wlan0
serial: 00:14:a5:63:75:a6
capabilities: ethernet physical wireless
configuration: broadcast=yes ip=192.168.1.47 multicast=yes wireless=IEEE 802.11bg
*-network:1 DISABLED
description: Ethernet interface
physical id: 3
logical name: pan0
serial: 82:3d:c7:80:65:43
capabilities: ethernet physical
configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A link=yes multicast=yes

sudo cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0

# The primary network interface
auto eth0
iface eth0 inet dhcp

auto wlan0
iface wlan0 inet static
address 192.168.1.47
gateway 192.168.1.1
dns-westell 192.168.1.1
netmask 255.255.255.0
wpa-driver wext
wpa-ssid Zapper
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <my psk>


sudo ifdown -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/50firestarter
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/wpasupplicant
route del default gw 192.168.1.1 metric 100 wlan0
ifconfig wlan0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant

sudo ifup -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -D wext -q -f /var/log/wpa_supplicant.wlan0.log -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1

ifconfig wlan0 192.168.1.47 netmask 255.255.255.0 up
route add default gw 192.168.1.1 metric 100 wlan0
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/50firestarter
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant

uname -a
Linux dv8000 2.6.27-7-generic #1 SMP Tue Nov 4 19:33:06 UTC 2008 x86_64 GNU/Linux

[geezerone]

What does your dmesg output say and what does /etc/init.d/networking restart do?

There is useful info HERE (http://www.cs.bham.ac.uk/%7Eaxs/laptop/ubuntu.html) which may get past your wpasupplicant issue.

The 4318 driver is also availablestored here: BCM Drivers (http://linuxwireless.org/en/users/Drivers/b43#b43andb43legacy) if that helps.

[kannedheat]

What does your dmesg output say and what does /etc/init.d/networking restart do?

There is useful info HERE (http://www.cs.bham.ac.uk/%7Eaxs/laptop/ubuntu.html) which may get past your wpasupplicant issue.

The 4318 driver is also availablestored here: BCM Drivers (http://linuxwireless.org/en/users/Drivers/b43#b43andb43legacy) if that helps.


dmesg
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.27-7-generic (buildd@crested) (gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu11) ) #1 SMP Tue Nov 4 19:33:06 UTC 2008 (Ubuntu 2.6.27-7.16-generic)
[ 0.000000] Command line: root=UUID=ce35b58d-ee2c-4311-a0a8-8646007548e1 ro quiet splash
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] Centaur CentaurHauls
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
[ 0.000000] BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000d0000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 000000007fea0000 (usable)
[ 0.000000] BIOS-e820: 000000007fea0000 - 000000007feac000 (ACPI data)
[ 0.000000] BIOS-e820: 000000007feac000 - 000000007ff00000 (ACPI NVS)
[ 0.000000] BIOS-e820: 000000007ff00000 - 0000000080000000 (reserved)
[ 0.000000] BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
[ 0.000000] BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
[ 0.000000] BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
[ 0.000000] BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
[ 0.000000] last_pfn = 0x7fea0 max_arch_pfn = 0x3ffffffff
[ 0.000000] init_memory_mapping
[ 0.000000] 0000000000 - 007fe00000 page 2M
[ 0.000000] 007fe00000 - 007fea0000 page 4k
[ 0.000000] kernel direct mapping tables up to 7fea0000 @ 8000-c000
[ 0.000000] last_map_addr: 7fea0000 end: 7fea0000
[ 0.000000] RAMDISK: 3775f000 - 37fef505
[ 0.000000] DMI present.
[ 0.000000] ACPI: RSDP 000F7C50, 0014 (r0 PTLTD )
[ 0.000000] ACPI: RSDT 7FEA4843, 0034 (r1 PTLTD RSDT 6040000 LTP 0)
[ 0.000000] ACPI: FACP 7FEABE31, 0074 (r1 HP Piranha 6040000 ATI F4240)
[ 0.000000] ACPI: DSDT 7FEA4877, 75BA (r1 HP 309B 6040000 MSFT 100000E)
[ 0.000000] ACPI: FACS 7FEACFC0, 0040
[ 0.000000] ACPI: SSDT 7FEABEA5, 00CF (r1 PTLTD POWERNOW 6040000 LTP 1)
[ 0.000000] ACPI: APIC 7FEABF74, 0050 (r1 PTLTD APIC 6040000 LTP 0)
[ 0.000000] ACPI: MCFG 7FEABFC4, 003C (r1 PTLTD MCFG 6040000 LTP 0)
[ 0.000000] ACPI: DMI detected: Hewlett-Packard
[ 0.000000] Scanning NUMA topology in Northbridge 24
[ 0.000000] No NUMA configuration found
[ 0.000000] Faking a node at 0000000000000000-000000007fea0000
[ 0.000000] Bootmem setup node 0 0000000000000000-000000007fea0000
[ 0.000000] NODE_DATA [0000000000001000 - 0000000000005fff]
[ 0.000000] bootmap [000000000000a000 - 0000000000019fd7] pages 10
[ 0.000000] (6 early reservations) ==> bootmem [0000000000 - 007fea0000]
[ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
[ 0.000000] #1 [0000006000 - 0000008000] TRAMPOLINE ==> [0000006000 - 0000008000]
[ 0.000000] #2 [0000200000 - 00008b8f9c] TEXT DATA BSS ==> [0000200000 - 00008b8f9c]
[ 0.000000] #3 [003775f000 - 0037fef505] RAMDISK ==> [003775f000 - 0037fef505]
[ 0.000000] #4 [000009f800 - 0000100000] BIOS reserved ==> [000009f800 - 0000100000]
[ 0.000000] #5 [0000008000 - 000000a000] PGTABLE ==> [0000008000 - 000000a000]
[ 0.000000] found SMP MP-table at [ffff8800000f7c80] 000f7c80
[ 0.000000] [ffffe20000000000-ffffe20001ffffff] PMD -> [ffff880001200000-ffff8800031fffff] on node 0
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0x00000000 -> 0x00001000
[ 0.000000] DMA32 0x00001000 -> 0x00100000
[ 0.000000] Normal 0x00100000 -> 0x00100000
[ 0.000000] Movable zone start PFN for each node
[ 0.000000] early_node_map[2] active PFN ranges
[ 0.000000] 0: 0x00000000 -> 0x0000009f
[ 0.000000] 0: 0x00000100 -> 0x0007fea0
[ 0.000000] On node 0 totalpages: 523839
[ 0.000000] DMA zone: 2112 pages, LIFO batch:0
[ 0.000000] DMA32 zone: 511717 pages, LIFO batch:31
[ 0.000000] SB4X0 revision 0x11
[ 0.000000] Ignoring ACPI timer override.
[ 0.000000] If you got timer trouble try acpi_use_timer_override
[ 0.000000] ACPI: PM-Timer IO Port: 0x8008
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
[ 0.000000] ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 1, version 0, address 0xfec00000, GSI 0-23
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 21 low level)
[ 0.000000] Setting APIC routing to flat
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] SMP: Allowing 1 CPUs, 0 hotplug CPUs
[ 0.000000] PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
[ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000d0000
[ 0.000000] PM: Registered nosave memory: 00000000000d0000 - 0000000000100000
[ 0.000000] Allocating PCI resources starting at 88000000 (gap: 80000000:60000000)
[ 0.000000] PERCPU: Allocating 64928 bytes of per cpu data
[ 0.000000] NR_CPUS: 64, nr_cpu_ids: 1, nr_node_ids 1
[ 0.000000] Built 1 zonelists in Node order, mobility grouping on. Total pages: 513829
[ 0.000000] Policy zone: DMA32
[ 0.000000] Kernel command line: root=UUID=ce35b58d-ee2c-4311-a0a8-8646007548e1 ro quiet splash
[ 0.000000] Initializing CPU#0
[ 0.000000] PID hash table entries: 4096 (order: 12, 32768 bytes)
[ 0.000000] TSC: PIT calibration confirmed by PMTIMER.
[ 0.000000] TSC: using PIT calibration value
[ 0.000000] Detected 1790.812 MHz processor.
[ 0.004000] Console: colour VGA+ 80x25
[ 0.004000] console [tty0] enabled
[ 0.004000] Checking aperture...
[ 0.004000] No AGP bridge found
[ 0.004000] Node 0: aperture @ fb92000000 size 32 MB
[ 0.004000] Aperture beyond 4GB. Ignoring.
[ 0.004000] Memory: 2046696k/2095744k available (3112k kernel code, 48660k reserved, 1575k data, 536k init)
[ 0.004000] CPA: page pool initialized 1 of 1 pages preallocated
[ 0.004000] SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.004012] Calibrating delay loop (skipped), value calculated using timer frequency.. 3581.62 BogoMIPS (lpj=7163248)
[ 0.004050] Security Framework initialized
[ 0.004060] SELinux: Disabled at boot.
[ 0.004083] AppArmor: AppArmor initialized
[ 0.004324] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
[ 0.006610] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
[ 0.007700] Mount-cache hash table entries: 256
[ 0.007941] Initializing cgroup subsys ns
[ 0.007946] Initializing cgroup subsys cpuacct
[ 0.007949] Initializing cgroup subsys memory
[ 0.007972] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
[ 0.008008] CPU: L2 Cache: 512K (64 bytes/line)
[ 0.008011] CPU 0/0 -> Node 0
[ 0.008013] tseg: 007ff00000
[ 0.008037] SMP alternatives: switching to UP code
[ 0.014727] Freeing SMP alternatives: 24k freed
[ 0.014773] ACPI: Core revision 20080609
[ 0.017647] ACPI: Checking initramfs for custom DSDT
[ 0.424556] ..TIMER: vector=0x30 apic1=0 pin1=0 apic2=-1 pin2=-1
[ 0.464258] CPU0: AMD Turion(tm) 64 Mobile Technology ML-32 stepping 02
[ 0.464264] Using local APIC timer interrupts.
[ 0.468030] APIC timer calibration result 12436212
[ 0.468032] Detected 12.436 MHz APIC timer.
[ 0.468125] Brought up 1 CPUs
[ 0.468128] Total of 1 processors activated (3581.62 BogoMIPS).
[ 0.468177] CPU0 attaching sched-domain:
[ 0.468181] domain 0: span 0 level NODE
[ 0.468183] groups: 0
[ 0.468533] net_namespace: 1552 bytes
[ 0.468538] Booting paravirtualized kernel on bare hardware
[ 0.468727] Time: 22:10:20 Date: 11/15/08
[ 0.468769] NET: Registered protocol family 16
[ 0.469129] node 0 link 0: io port [1000, fffff]
[ 0.469133] TOM: 0000000080000000 aka 2048M
[ 0.469137] node 0 link 0: mmio [a0000, bffff]
[ 0.469139] node 0 link 0: mmio [f0000000, ffffffff]
[ 0.469142] node 0 link 0: mmio [e0000000, efffffff]
[ 0.469145] node 0 link 0: mmio [80000000, dfffffff]
[ 0.469148] bus: [00,ff] on node 0 link 0
[ 0.469150] bus: 00 index 0 io port: [0, ffff]
[ 0.469152] bus: 00 index 1 mmio: [a0000, bffff]
[ 0.469154] bus: 00 index 2 mmio: [80000000, fcffffffff]
[ 0.469164] ACPI: bus type pci registered
[ 0.469284] PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 0
[ 0.469287] PCI: MCFG area at e0000000 reserved in E820
[ 0.469351] PCI: Using MMCONFIG at e0000000 - e00fffff
[ 0.469353] PCI: Using configuration type 1 for base access
[ 0.470917] ACPI: EC: Look up EC in DSDT
[ 0.474267] ACPI: Interpreter enabled
[ 0.474270] ACPI: (supports S0 S3 S4 S5)
[ 0.474287] ACPI: Using IOAPIC for interrupt routing
[ 0.477827] ACPI: EC: non-query interrupt received, switching to interrupt mode
[ 0.556768] ACPI: EC: GPE = 0x1a, I/O: command/status = 0x66, data = 0x62
[ 0.556771] ACPI: EC: driver started in interrupt mode
[ 0.556822] ACPI: PCI Root Bridge [PCI0] (0000:00)
[ 0.556958] pci 0000:00:04.0: PME# supported from D0 D3hot D3cold
[ 0.556962] pci 0000:00:04.0: PME# disabled
[ 0.557023] PCI: 0000:00:13.0 reg 10 32bit mmio: [c0000000, c0000fff]
[ 0.557118] PCI: 0000:00:13.1 reg 10 32bit mmio: [c0001000, c0001fff]
[ 0.557226] PCI: 0000:00:13.2 reg 10 32bit mmio: [c0002000, c0002fff]
[ 0.557287] pci 0000:00:13.2: supports D1
[ 0.557289] pci 0000:00:13.2: supports D2
[ 0.557291] pci 0000:00:13.2: PME# supported from D0 D1 D2 D3hot
[ 0.557296] pci 0000:00:13.2: PME# disabled
[ 0.557341] PCI: 0000:00:14.0 reg 10 io port: [8400, 840f]
[ 0.557349] PCI: 0000:00:14.0 reg 14 32bit mmio: [c0003000, c00033ff]
[ 0.557394] HPET not enabled in BIOS. You might try hpet=force boot option
[ 0.557439] PCI: 0000:00:14.1 reg 10 io port: [8430, 8437]
[ 0.557448] PCI: 0000:00:14.1 reg 14 io port: [8424, 8427]
[ 0.557457] PCI: 0000:00:14.1 reg 18 io port: [8428, 842f]
[ 0.557465] PCI: 0000:00:14.1 reg 1c io port: [8420, 8423]
[ 0.557474] PCI: 0000:00:14.1 reg 20 io port: [8410, 841f]
[ 0.557647] PCI: 0000:00:14.5 reg 10 32bit mmio: [c0003400, c00034ff]
[ 0.557740] PCI: 0000:00:14.6 reg 10 32bit mmio: [c0003800, c00038ff]
[ 0.557892] PCI: 0000:01:05.0 reg 10 32bit mmio: [c8000000, cfffffff]
[ 0.557897] PCI: 0000:01:05.0 reg 14 io port: [9000, 90ff]
[ 0.557901] PCI: 0000:01:05.0 reg 18 32bit mmio: [c0100000, c010ffff]
[ 0.557910] PCI: 0000:01:05.0 reg 30 32bit mmio: [0, 1ffff]
[ 0.557917] pci 0000:01:05.0: supports D1
[ 0.557919] pci 0000:01:05.0: supports D2
[ 0.557933] PCI: bridge 0000:00:01.0 io port: [9000, 9fff]
[ 0.557936] PCI: bridge 0000:00:01.0 32bit mmio: [c0100000, c01fffff]
[ 0.557941] PCI: bridge 0000:00:01.0 64bit mmio pref: [c8000000, cfffffff]
[ 0.557998] PCI: bridge 0000:00:04.0 io port: [0, fff]
[ 0.558001] PCI: bridge 0000:00:04.0 32bit mmio: [0, fffff]
[ 0.558042] PCI: 0000:06:02.0 reg 10 32bit mmio: [c0204000, c0205fff]
[ 0.558148] PCI: 0000:06:04.0 reg 10 32bit mmio: [c0208000, c0208fff]
[ 0.558172] pci 0000:06:04.0: supports D1
[ 0.558173] pci 0000:06:04.0: supports D2
[ 0.558175] pci 0000:06:04.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.558182] pci 0000:06:04.0: PME# disabled
[ 0.558232] PCI: 0000:06:04.2 reg 10 32bit mmio: [c0209000, c02097ff]
[ 0.558243] PCI: 0000:06:04.2 reg 14 32bit mmio: [c0200000, c0203fff]
[ 0.558309] pci 0000:06:04.2: supports D1
[ 0.558311] pci 0000:06:04.2: supports D2
[ 0.558313] pci 0000:06:04.2: PME# supported from D0 D1 D2 D3hot
[ 0.558319] pci 0000:06:04.2: PME# disabled
[ 0.558366] PCI: 0000:06:04.3 reg 10 32bit mmio: [c0206000, c0207fff]
[ 0.558436] pci 0000:06:04.3: supports D1
[ 0.558438] pci 0000:06:04.3: supports D2
[ 0.558439] pci 0000:06:04.3: PME# supported from D0 D1 D2 D3hot
[ 0.558446] pci 0000:06:04.3: PME# disabled
[ 0.558494] PCI: 0000:06:04.4 reg 10 32bit mmio: [c020a000, c020a0ff]
[ 0.558504] PCI: 0000:06:04.4 reg 14 32bit mmio: [c0209c00, c0209cff]
[ 0.558515] PCI: 0000:06:04.4 reg 18 32bit mmio: [c0209800, c02098ff]
[ 0.558569] pci 0000:06:04.4: supports D1
[ 0.558571] pci 0000:06:04.4: supports D2
[ 0.558573] pci 0000:06:04.4: PME# supported from D0 D1 D2 D3hot
[ 0.558579] pci 0000:06:04.4: PME# disabled
[ 0.558633] PCI: 0000:06:06.0 reg 10 io port: [a000, a0ff]
[ 0.558643] PCI: 0000:06:06.0 reg 14 32bit mmio: [c020a400, c020a4ff]
[ 0.558706] pci 0000:06:06.0: supports D1
[ 0.558708] pci 0000:06:06.0: supports D2
[ 0.558710] pci 0000:06:06.0: PME# supported from D1 D2 D3hot D3cold
[ 0.558716] pci 0000:06:06.0: PME# disabled
[ 0.558768] pci 0000:00:14.4: transparent bridge
[ 0.558776] PCI: bridge 0000:00:14.4 io port: [a000, afff]
[ 0.558782] PCI: bridge 0000:00:14.4 32bit mmio: [c0200000, c02fffff]
[ 0.558829] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[ 0.559014] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PB4_._PRT]
[ 0.559177] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P2P_._PRT]
[ 0.559350] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP_._PRT]
[ 0.562218] ACPI: PCI Interrupt Link [LNKA] (IRQs 10 11) *0, disabled.
[ 0.562357] ACPI: PCI Interrupt Link [LNKB] (IRQs 10 11) *0, disabled.
[ 0.562493] ACPI: PCI Interrupt Link [LNKC] (IRQs 10 11) *0, disabled.
[ 0.562630] ACPI: PCI Interrupt Link [LNKD] (IRQs 10 11) *0, disabled.
[ 0.562766] ACPI: PCI Interrupt Link [LNKE] (IRQs 10 11) *0, disabled.
[ 0.562903] ACPI: PCI Interrupt Link [LNKF] (IRQs 10 11) *0, disabled.
[ 0.563040] ACPI: PCI Interrupt Link [LNKG] (IRQs 10 11) *0, disabled.
[ 0.563183] ACPI: PCI Interrupt Link [LNKH] (IRQs 10 11) *0, disabled.
[ 0.563364] Linux Plug and Play Support v0.97 (c) Adam Belay
[ 0.563405] pnp: PnP ACPI init
[ 0.563415] ACPI: bus type pnp registered
[ 0.565887] pnp 00:08: io resource (0x72-0x73) overlaps 0000:00:04.0 BAR 7 (0x0-0xfff), disabling
[ 0.565891] pnp 00:08: io resource (0xb0-0xb1) overlaps 0000:00:04.0 BAR 7 (0x0-0xfff), disabling
[ 0.565895] pnp 00:08: io resource (0x92-0x92) overlaps 0000:00:04.0 BAR 7 (0x0-0xfff), disabling
[ 0.565898] pnp 00:08: io resource (0x40b-0x40b) overlaps 0000:00:04.0 BAR 7 (0x0-0xfff), disabling
[ 0.565901] pnp 00:08: io resource (0x4d0-0x4d1) overlaps 0000:00:04.0 BAR 7 (0x0-0xfff), disabling
[ 0.565904] pnp 00:08: io resource (0x4d6-0x4d6) overlaps 0000:00:04.0 BAR 7 (0x0-0xfff), disabling
[ 0.565908] pnp 00:08: io resource (0x870-0x87f) overlaps 0000:00:04.0 BAR 7 (0x0-0xfff), disabling
[ 0.565911] pnp 00:08: io resource (0xc00-0xc01) overlaps 0000:00:04.0 BAR 7 (0x0-0xfff), disabling
[ 0.565914] pnp 00:08: io resource (0xc14-0xc14) overlaps 0000:00:04.0 BAR 7 (0x0-0xfff), disabling
[ 0.565918] pnp 00:08: io resource (0xc50-0xc52) overlaps 0000:00:04.0 BAR 7 (0x0-0xfff), disabling
[ 0.565921] pnp 00:08: io resource (0xc6c-0xc6c) overlaps 0000:00:04.0 BAR 7 (0x0-0xfff), disabling
[ 0.565924] pnp 00:08: io resource (0xc6f-0xc6f) overlaps 0000:00:04.0 BAR 7 (0x0-0xfff), disabling
[ 0.565927] pnp 00:08: io resource (0xcd4-0xcd5) overlaps 0000:00:04.0 BAR 7 (0x0-0xfff), disabling
[ 0.565931] pnp 00:08: io resource (0xcd6-0xcd7) overlaps 0000:00:04.0 BAR 7 (0x0-0xfff), disabling
[ 0.565934] pnp 00:08: io resource (0xcd8-0xcdf) overlaps 0000:00:04.0 BAR 7 (0x0-0xfff), disabling
[ 0.565937] pnp 00:08: io resource (0xf40-0xf47) overlaps 0000:00:04.0 BAR 7 (0x0-0xfff), disabling
[ 0.565941] pnp 00:08: io resource (0x280-0x293) overlaps 0000:00:04.0 BAR 7 (0x0-0xfff), disabling
[ 0.566157] pnp 00:09: mem resource (0xe0000-0xfffff) overlaps 0000:00:04.0 BAR 8 (0x0-0xfffff), disabling
[ 0.566161] pnp 00:09: mem resource (0x0-0xfff) overlaps 0000:00:04.0 BAR 8 (0x0-0xfffff), disabling
[ 0.566174] pnp 00:09: mem resource (0x0-0xfff) overlaps 0000:01:05.0 BAR 6 (0x0-0x1ffff), disabling
[ 0.588113] pnp: PnP ACPI: found 10 devices
[ 0.588116] ACPI: ACPI bus type pnp unregistered
[ 0.588516] PCI: Using ACPI for IRQ routing
[ 0.588524] pci 0000:00:04.0: BAR 7: can't allocate resource
[ 0.588527] pci 0000:00:04.0: BAR 8: can't allocate resource
[ 0.600054] NET: Registered protocol family 8
[ 0.600057] NET: Registered protocol family 20
[ 0.600101] NetLabel: Initializing
[ 0.600103] NetLabel: domain hash size = 128
[ 0.600104] NetLabel: protocols = UNLABELED CIPSOv4
[ 0.600121] NetLabel: unlabeled traffic allowed by default
[ 0.601055] tracer: 1286 pages allocated for 65536 entries of 80 bytes
[ 0.601057] actual entries 65586
[ 0.601251] AppArmor: AppArmor Filesystem Enabled
[ 0.601282] ACPI: RTC can wake from S4
[ 0.612056] system 00:01: iomem range 0xe0000000-0xefffffff could not be reserved
[ 0.612059] system 00:01: iomem range 0xfec00000-0xfec00fff could not be reserved
[ 0.612063] system 00:01: iomem range 0xfee00000-0xfee00fff could not be reserved
[ 0.612076] system 00:08: ioport range 0x1080-0x1080 has been reserved
[ 0.612080] system 00:08: ioport range 0x8000-0x805f has been reserved
[ 0.612087] system 00:09: iomem range 0xfff80000-0xffffffff could not be reserved
[ 0.617243] pci 0000:00:01.0: PCI bridge, secondary bus 0000:01
[ 0.617247] pci 0000:00:01.0: IO window: 0x9000-0x9fff
[ 0.617252] pci 0000:00:01.0: MEM window: 0xc0100000-0xc01fffff
[ 0.617255] pci 0000:00:01.0: PREFETCH window: 0x000000c8000000-0x000000cfffffff
[ 0.617260] pci 0000:00:04.0: PCI bridge, secondary bus 0000:02
[ 0.617262] pci 0000:00:04.0: IO window: disabled
[ 0.617265] pci 0000:00:04.0: MEM window: disabled
[ 0.617268] pci 0000:00:04.0: PREFETCH window: disabled
[ 0.617276] pci 0000:06:04.0: CardBus bridge, secondary bus 0000:07
[ 0.617278] pci 0000:06:04.0: IO window: 0x00a400-0x00a4ff
[ 0.617284] pci 0000:06:04.0: IO window: 0x00a800-0x00a8ff
[ 0.617291] pci 0000:06:04.0: PREFETCH window: 0x88000000-0x8bffffff
[ 0.617297] pci 0000:06:04.0: MEM window: 0x8c000000-0x8fffffff
[ 0.617304] pci 0000:00:14.4: PCI bridge, secondary bus 0000:06
[ 0.617308] pci 0000:00:14.4: IO window: 0xa000-0xafff
[ 0.617315] pci 0000:00:14.4: MEM window: 0xc0200000-0xc02fffff
[ 0.617321] pci 0000:00:14.4: PREFETCH window: 0x00000088000000-0x0000008bffffff
[ 0.617342] pci 0000:00:04.0: setting latency timer to 64
[ 0.617367] pci 0000:06:04.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
[ 0.617374] bus: 00 index 0 io port: [0, ffff]
[ 0.617377] bus: 00 index 1 mmio: [0, ffffffffffffffff]
[ 0.617379] bus: 01 index 0 io port: [9000, 9fff]
[ 0.617381] bus: 01 index 1 mmio: [c0100000, c01fffff]
[ 0.617384] bus: 01 index 2 mmio: [c8000000, cfffffff]
[ 0.617386] bus: 01 index 3 mmio: [0, 0]
[ 0.617388] bus: 02 index 0 mmio: [0, fff]
[ 0.617390] bus: 02 index 1 mmio: [0, fffff]
[ 0.617392] bus: 02 index 2 mmio: [0, 0]
[ 0.617394] bus: 02 index 3 mmio: [0, 0]
[ 0.617396] bus: 06 index 0 io port: [a000, afff]
[ 0.617398] bus: 06 index 1 mmio: [c0200000, c02fffff]
[ 0.617400] bus: 06 index 2 mmio: [88000000, 8bffffff]
[ 0.617402] bus: 06 index 3 io port: [0, ffff]
[ 0.617405] bus: 06 index 4 mmio: [0, ffffffffffffffff]
[ 0.617407] bus: 07 index 0 io port: [a400, a4ff]
[ 0.617409] bus: 07 index 1 io port: [a800, a8ff]
[ 0.617411] bus: 07 index 2 mmio: [88000000, 8bffffff]
[ 0.617413] bus: 07 index 3 mmio: [8c000000, 8fffffff]
[ 0.617430] NET: Registered protocol family 2
[ 0.656155] IP route cache hash table entries: 65536 (order: 7, 524288 bytes)
[ 0.657331] TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
[ 0.661752] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
[ 0.662838] TCP: Hash tables configured (established 262144 bind 65536)
[ 0.662842] TCP reno registered
[ 0.672151] NET: Registered protocol family 1
[ 0.672297] checking if image is initramfs... it is
[ 1.120039] Switched to high resolution mode on CPU 0
[ 1.540920] Freeing initrd memory: 8769k freed
[ 1.551635] audit: initializing netlink socket (disabled)
[ 1.551653] type=2000 audit(1226787020.548:1): initialized
[ 1.558229] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[ 1.561357] VFS: Disk quotas dquot_6.5.1
[ 1.561472] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 1.561608] msgmni has been set to 4014
[ 1.561765] io scheduler noop registered
[ 1.561767] io scheduler anticipatory registered
[ 1.561769] io scheduler deadline registered
[ 1.561912] io scheduler cfq registered (default)
[ 1.561924] pci 0000:00:00.0: MSI quirk detected; MSI disabled
[ 1.561985] pci 0000:01:05.0: Boot video device
[ 1.562124] pcieport-driver 0000:00:04.0: setting latency timer to 64
[ 1.562146] pcieport-driver 0000:00:04.0: found MSI capability
[ 1.562150] pci_express 0000:00:04.0:pcie00: allocate port service
[ 1.562206] pci_express 0000:00:04.0:pcie01: allocate port service
[ 1.588097] aer 0000:00:04.0:pcie01: AER service couldn't init device: no _OSC support
[ 1.631364] Linux agpgart interface v0.103
[ 1.631372] Serial: 8250/16550 driver4 ports, IRQ sharing enabled
[ 1.632165] serial 0000:00:14.6: PCI INT B -> GSI 17 (level, low) -> IRQ 17
[ 1.632174] serial 0000:00:14.6: PCI INT B disabled
[ 1.634157] brd: module loaded
[ 1.634249] input: Macintosh mouse button emulation as /devices/virtual/input/input0
[ 1.634396] PNP: PS/2 Controller [PNP0303:KBC0,PNP0f13:MSE0] at 0x60,0x64 irq 1,12
[ 1.654988] i8042.c: Detected active multiplexing controller, rev 1.1.
[ 1.671076] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 1.671082] serio: i8042 AUX0 port at 0x60,0x64 irq 12
[ 1.671084] serio: i8042 AUX1 port at 0x60,0x64 irq 12
[ 1.671087] serio: i8042 AUX2 port at 0x60,0x64 irq 12
[ 1.671089] serio: i8042 AUX3 port at 0x60,0x64 irq 12
[ 1.680136] mice: PS/2 mouse device common for all mice
[ 1.680296] rtc_cmos 00:04: rtc core: registered rtc_cmos as rtc0
[ 1.680326] rtc0: alarms up to one month
[ 1.680373] cpuidle: using governor ladder
[ 1.680375] cpuidle: using governor menu
[ 1.680837] TCP cubic registered
[ 1.681115] registered taskstats version 1
[ 1.681276] Magic number: 0:110:199
[ 1.681323] tty ttype: hash matches
[ 1.681423] rtc_cmos 00:04: setting system clock to 2008-11-15 22:10:21 UTC (1226787021)
[ 1.681426] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[ 1.681428] EDD information not available.
[ 1.681488] Freeing unused kernel memory: 536k freed
[ 1.681876] Write protecting the kernel read-only data: 4348k
[ 1.698880] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1
[ 1.888027] fuse init (API version 7.9)
[ 2.001734] ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3])
[ 2.001804] processor ACPI0007:00: registered as cooling_device0
[ 2.001808] ACPI: Processor [CPU0] (supports 8 throttling states)
[ 2.005515] Marking TSC unstable due to TSC halts in idle
[ 2.016629] thermal LNXTHERM:01: registered as thermal_zone0
[ 2.030998] ACPI: Thermal Zone [THRM] (0 C)
[ 2.536647] usbcore: registered new interface driver usbfs
[ 2.536686] usbcore: registered new interface driver hub
[ 2.536773] usbcore: registered new device driver usb
[ 2.542937] ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
[ 2.542977] ohci_hcd 0000:00:13.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
[ 2.542995] ohci_hcd 0000:00:13.0: OHCI Host Controller
[ 2.543056] ohci_hcd 0000:00:13.0: new USB bus registered, assigned bus number 1
[ 2.543090] ohci_hcd 0000:00:13.0: irq 19, io mem 0xc0000000
[ 2.600288] usb usb1: configuration #1 chosen from 1 choice
[ 2.600321] hub 1-0:1.0: USB hub found
[ 2.600336] hub 1-0:1.0: 4 ports detected
[ 2.607281] No dock devices found.
[ 2.651462] SCSI subsystem initialized
[ 2.704432] ohci_hcd 0000:00:13.1: PCI INT A -> GSI 19 (level, low) -> IRQ 19
[ 2.704456] ohci_hcd 0000:00:13.1: OHCI Host Controller
[ 2.704490] ohci_hcd 0000:00:13.1: new USB bus registered, assigned bus number 2
[ 2.704511] ohci_hcd 0000:00:13.1: irq 19, io mem 0xc0001000
[ 2.734462] libata version 3.00 loaded.
[ 2.758401] 8139too Fast Ethernet driver 0.9.28
[ 2.764238] usb usb2: configuration #1 chosen from 1 choice
[ 2.764272] hub 2-0:1.0: USB hub found
[ 2.764286] hub 2-0:1.0: 4 ports detected
[ 2.868574] ehci_hcd 0000:00:13.2: PCI INT A -> GSI 19 (level, low) -> IRQ 19
[ 2.868593] ehci_hcd 0000:00:13.2: EHCI Host Controller
[ 2.868623] ehci_hcd 0000:00:13.2: new USB bus registered, assigned bus number 3
[ 2.868686] ehci_hcd 0000:00:13.2: irq 19, io mem 0xc0002000
[ 2.880082] ehci_hcd 0000:00:13.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
[ 2.880287] usb usb3: configuration #1 chosen from 1 choice
[ 2.880316] hub 3-0:1.0: USB hub found
[ 2.880326] hub 3-0:1.0: 8 ports detected
[ 2.984788] pata_atiixp 0000:00:14.1: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 2.984840] pata_atiixp 0000:00:14.1: setting latency timer to 64
[ 2.984985] scsi0 : pata_atiixp
[ 2.985130] scsi1 : pata_atiixp
[ 2.986750] ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0x8410 irq 14
[ 2.986753] ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x8418 irq 15
[ 3.199800] ata1.00: ATA-7: WDC WD1600BEVE-00UYT0, 01.04A01, max UDMA/100
[ 3.199805] ata1.00: 312581808 sectors, multi 16: LBA48
[ 3.213578] ata1.00: configured for UDMA/100
[ 3.377219] ata2.00: ATAPI: HL-DT-ST DVD-RW GWA-4082N, CC15, max MWDMA2
[ 3.392607] ata2.00: configured for MWDMA2
[ 3.392674] isa bounce pool size: 16 pages
[ 3.392787] scsi 0:0:0:0: Direct-Access ATA WDC WD1600BEVE-0 01.0 PQ: 0 ANSI: 5
[ 3.396658] scsi 1:0:0:0: CD-ROM HL-DT-ST DVD-RW GWA-4082N CC15 PQ: 0 ANSI: 5
[ 3.398107] b43-pci-bridge 0000:06:02.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
[ 3.456698] ssb: Sonics Silicon Backplane found on PCI device 0000:06:02.0
[ 3.456832] ohci1394 0000:06:04.2: PCI INT C -> GSI 23 (level, low) -> IRQ 23
[ 3.506638] ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[23] MMIO=[c0209000-c02097ff] Max Packet=[2048] IR/IT contexts=[4/8]
[ 3.511100] 8139too 0000:06:06.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[ 3.512414] eth0: RealTek RTL8139 at 0xa000, 00:0f:b0:be:ea:6a, IRQ 22
[ 3.512417] eth0: Identified 8139 chip type 'RTL-8100B/8139D'
[ 3.515545] 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
[ 3.900963] scsi 0:0:0:0: Attached scsi generic sg0 type 0
[ 3.901006] scsi 1:0:0:0: Attached scsi generic sg1 type 5
[ 3.927067] Driver 'sd' needs updating - please use bus_type methods
[ 3.927230] sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB)
[ 3.927259] sd 0:0:0:0: [sda] Write Protect is off
[ 3.927261] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 3.927307] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 3.927403] sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB)
[ 3.927427] sd 0:0:0:0: [sda] Write Protect is off
[ 3.927429] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 3.927472] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 3.927477] sda:<4>Driver 'sr' needs updating - please use bus_type methods
[ 3.971572] sda1 sda2 sda3
[ 4.003473] sd 0:0:0:0: [sda] Attached SCSI disk
[ 4.016944] sr0: scsi3-mmc drive: 24x/24x writer cd/rw xa/form2 cdda tray
[ 4.016950] Uniform CD-ROM driver Revision: 3.20
[ 4.017080] sr 1:0:0:0: Attached scsi CD-ROM sr0
[ 4.338832] PM: Starting manual resume from disk
[ 4.338836] PM: Resume from partition 8:2
[ 4.338838] PM: Checking hibernation image.
[ 4.339113] PM: Resume from disk failed.
[ 4.387629] kjournald starting. Commit interval 5 seconds
[ 4.387649] EXT3-fs: mounted filesystem with ordered data mode.
[ 4.780194] ieee1394: Host added: ID:BUS[0-00:1023] GUID[5c3f0200c17e407a]
[ 13.134256] udevd version 124 started
[ 13.610706] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 13.660773] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 13.924797] piix4_smbus 0000:00:14.0: SMBus Host Controller at 0x8400, revision 0
[ 13.957041] input: Power Button (FF) as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
[ 13.972053] ACPI: Power Button (FF) [PWRF]
[ 13.972218] input: Sleep Button (FF) as /devices/LNXSYSTM:00/LNXSLPBN:00/input/input3
[ 13.988070] ACPI: Sleep Button (FF) [SLPF]
[ 13.988244] input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input4
[ 13.988335] ACPI: Lid Switch [LID]
[ 13.988430] input: Power Button (CM) as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input5
[ 14.004045] ACPI: Power Button (CM) [PWRB]
[ 14.019350] ACPI: WMI: Mapper loaded
[ 14.147116] fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel.
[ 14.320732] [fglrx] Maximum main memory to use for locked dma buffers: 1880 MBytes.
[ 14.320769] [fglrx] vendor: 1002 device: 5955 count: 1
[ 14.321298] [fglrx] ioport: bar 1, base 0x9000, size: 0x100
[ 14.321320] pci 0000:01:05.0: power state changed by ACPI to D0
[ 14.321329] pci 0000:01:05.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 14.321982] [fglrx] PAT is enabled successfully!
[ 14.322027] [fglrx] module loaded - fglrx 8.54.3 [Oct 10 2008] with 1 minors
[ 14.352243] ACPI: AC Adapter [ACAD] (on-line)
[ 14.794263] ACPI: Battery Slot [BAT1] (battery present)
[ 14.994631] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A03:00/device:0f/device:10/input/input6
[ 15.004078] ACPI: Video Device [VGA] (multi-head: yes rom: no post: no)
[ 15.836550] Yenta: CardBus bridge found at 0000:06:04.0 [103c:309b]
[ 15.836577] Yenta: Enabling burst memory read transactions
[ 15.836583] Yenta: Using INTVAL to route CSC interrupts to PCI
[ 15.836585] Yenta: Routing CardBus interrupts to ISA
[ 15.836592] Yenta TI: socket 0000:06:04.0, mfunc 0x00a61b22, devctl 0x64
[ 16.069225] Yenta: ISA IRQ mask 0x0ef8, PCI irq 20
[ 16.069231] Socket status: 30000006
[ 16.069235] pcmcia: parent PCI bridge I/O window: 0xa000 - 0xafff
[ 16.069239] pcmcia: parent PCI bridge Memory window: 0xc0200000 - 0xc02fffff
[ 16.069241] pcmcia: parent PCI bridge Memory window: 0x88000000 - 0x8bffffff
[ 16.097077] tifm_7xx1 0000:06:04.3: PCI INT B -> GSI 23 (level, low) -> IRQ 23
[ 16.234653] input: PC Speaker as /devices/platform/pcspkr/input/input7
[ 16.287396] sdhci: Secure Digital Host Controller Interface driver
[ 16.287399] sdhci: Copyright(c) Pierre Ossman
[ 16.322381] sdhci-pci 0000:06:04.4: SDHCI controller found [104c:8034] (rev 0)
[ 16.322402] sdhci-pci 0000:06:04.4: PCI INT A -> GSI 20 (level, low) -> IRQ 20
[ 16.322487] mmc0: SDHCI controller on PCI [0000:06:04.4] using PIO
[ 16.324541] mmc1: SDHCI controller on PCI [0000:06:04.4] using PIO
[ 16.324584] mmc2: SDHCI controller on PCI [0000:06:04.4] using PIO
[ 16.512057] b43-phy0: Broadcom 4318 WLAN found
[ 16.616599] phy0: Selected rate control algorithm 'pid'
[ 16.680760] ATI IXP MC97 controller 0000:00:14.6: PCI INT B -> GSI 17 (level, low) -> IRQ 17
[ 16.781128] Broadcom 43xx driver loaded [ Features: PLR, Firmware-ID: FW13 ]
[ 16.792105] MC'97 0 converters and GPIO not ready (0x1)
[ 16.793690] ATI IXP AC97 controller 0000:00:14.5: PCI INT B -> GSI 17 (level, low) -> IRQ 17
[ 17.107076] Synaptics Touchpad, model: 1, fw: 6.2, id: 0x1a0b1, caps: 0xa04713/0x200000
[ 17.172211] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio4/input/input8
[ 19.947303] loop: module loaded
[ 20.001283] lp: driver loaded but no devices found
[ 20.314544] Adding 248996k swap on /dev/sda2. Priority:-1 extents:1 across:248996k
[ 20.871095] EXT3 FS on sda3, internal journal
[ 21.117316] device-mapper: uevent: version 1.0.3
[ 21.119367] device-mapper: ioctl: 4.14.0-ioctl (2008-04-23) initialised: dm-devel@redhat.com
[ 22.367142] type=1505 audit(1226805042.547:2): operation="profile_load" name="/usr/lib/cups/backend/cups-pdf" name2="default" pid=3982
[ 22.367432] type=1505 audit(1226805042.547:3): operation="profile_load" name="/usr/sbin/cupsd" name2="default" pid=3982
[ 22.513297] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 22.575323] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
[ 23.879379] NET: Registered protocol family 17
[ 28.132841] powernow-k8: Found 1 AMD Turion(tm) 64 Mobile Technology ML-32 processors (1 cpu cores) (version 2.20.00)
[ 28.132895] powernow-k8: 0 : fid 0xa (1800 MHz), vid 0x4
[ 28.132897] powernow-k8: 1 : fid 0x8 (1600 MHz), vid 0x6
[ 28.132900] powernow-k8: 2 : fid 0x0 (800 MHz), vid 0x16
[ 28.132941] powernow-k8: ph2 null fid transition 0xa
[ 29.155603] warning: `avahi-daemon' uses 32-bit capabilities (legacy support in use)
[ 29.510865] ppdev: user-space parallel port driver
[ 32.116049] Clocksource tsc unstable (delta = -113874087 ns)
[ 34.234995] input: b43-phy0 as /devices/virtual/input/input9
[ 34.324082] firmware: requesting b43/ucode5.fw
[ 34.575805] firmware: requesting b43/pcm5.fw
[ 34.593044] firmware: requesting b43/b0g0initvals5.fw
[ 34.612896] firmware: requesting b43/b0g0bsinitvals5.fw
[ 34.883050] b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
[ 35.000609] Registered led device: b43-phy0::radio
[ 36.117652] Bluetooth: Core ver 2.13
[ 36.122522] NET: Registered protocol family 31
[ 36.122534] Bluetooth: HCI device and connection manager initialized
[ 36.122542] Bluetooth: HCI socket layer initialized
[ 36.180194] Bluetooth: L2CAP ver 2.11
[ 36.180208] Bluetooth: L2CAP socket layer initialized
[ 36.273301] Bluetooth: SCO (Voice Link) ver 0.6
[ 36.273314] Bluetooth: SCO socket layer initialized
[ 36.322806] Bluetooth: RFCOMM socket layer initialized
[ 36.323378] Bluetooth: RFCOMM TTY layer initialized
[ 36.323390] Bluetooth: RFCOMM ver 1.10
[ 36.327641] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 36.327654] Bluetooth: BNEP filters: protocol multicast
[ 36.513275] Bridge firewalling registered
[ 36.517896] pan0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
[ 36.660769] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
[ 39.842712] [fglrx] GART Table is not in FRAME_BUFFER range
[ 39.853746] [fglrx] Reserved FB block: Shared offset:0, size:40000
[ 39.853762] [fglrx] Reserved FB block: Unshared offset:7ff5000, size:b000
[ 146.061928] psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 4
[ 146.064056] psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
[ 146.074427] psmouse.c: TouchPad at isa0060/serio4/input0 - driver resynched.
[ 477.279521] NET: Registered protocol family 10
[ 477.284588] lo: Disabled Privacy Extensions
[ 477.288891] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 488.140061] eth0: no IPv6 routers present


/etc/init.d/networking restart
* Reconfiguring network interfaces...ifdown: failed to open statefile /var/run/network/ifstate: Permission denied
rm: cannot remove `/var/run/network/initialized': Permission denied


My wireless does work. Unfortunately it won't connect to me WPA connection.

[wieman01]

Starting /sbin/wpa_supplicant...
wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1

kannedheat,

This isn't good news at all. What wireless adapter have you got there and what driver did you install?

When restarting your network, you need to add 'sudo' in front and enter your password when prompted:

sudo /etc/init.d/networking restart

[kannedheat]

kannedheat,

This isn't good news at all. What wireless adapter have you got there and what driver did you install?

When restarting your network, you need to add 'sudo' in front and enter your password when prompted:


sudo /etc/init.d/networking restart

* Reconfiguring network interfaces... [ OK ]


sudo lshw -C network

*-network:0
description: Network controller
product: BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller
vendor: Broadcom Corporation
physical id: 2
bus info: pci@0000:06:02.0
version: 02
width: 32 bits
clock: 33MHz
capabilities: bus_master
configuration: driver=b43-pci-bridge latency=64 module=ssb
*-network:1
description: Ethernet interface
product: RTL-8139/8139C/8139C+
vendor: Realtek Semiconductor Co., Ltd.
physical id: 6
bus info: pci@0000:06:06.0
logical name: eth0
version: 10
serial: 00:0f:b0:be:ea:6a
size: 100MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=8139too driverversion=0.9.28 duplex=full ip=192.168.1.42 latency=128 link=yes maxlatency=64 mingnt=32 module=8139too multicast=yes port=MII speed=100MB/s
*-network:0 DISABLED
description: Wireless interface
physical id: 2
logical name: wlan0
serial: 00:14:a5:63:75:a6
capabilities: ethernet physical wireless
configuration: broadcast=yes multicast=yes wireless=IEEE 802.11bg
*-network:1 DISABLED
description: Ethernet interface
physical id: 3
logical name: pan0
serial: 46:76:66:c7:f2:64
capabilities: ethernet physical
configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A link=yes multicast=yes

[kannedheat]

Well I dropped trying to get WPA to work on Intrepid 8.10. I went and setup WEP encryption, which worked with no problems at all except now I have to change eight other system that were connected to my network. Thanks for trying =)

[blommie]

Hi I'm desperately looking for assistance.
Up to two days ago my WPA Security Wireless connection was working fine then I had a update and things changed. I now can't get my WPA wireless connection to work BUT when I disable the WPA security it connects no problem. I have a ACER ASPIRE 4315 Notebook with Linux and a DLINK G604T Wireless router. I'm not to sure how to set up the wireless WPA connection though. When I go to network settings and click on the wireless connections properties it brings up wlan0 for Security then I do the WPA PERSONAL settings but do I click the Automatic Configuration(DHCP) option? Also when I click the enable roaming button all that detail I just completed disappears. .Linux is very new to me so don't know where to look.
Terminal mode is like Greek to me I don't know much about the commands. I have to google a lot to try and figure out what to do.
I have looked through this thread but most of it is above my head. WHat I do see is for your assistance you need a few things from me like
sudo iwlist scan
sudo lshw -C network

Well here they are:

sudo iwlist scan
[sudo] password for blommie:
lo Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:17:9A:1E:DC:38
ESSID:"DLINK"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:100/100 Signal level:-26 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:bcn_int=200
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK

eth0 Interface doesn't support scanning.




sudo lshw -C network
*-network
description: Ethernet interface
product: 88E8039 PCI-E Fast Ethernet Controller
vendor: Marvell Technology Group Ltd.
physical id: 0
bus info: pci@0000:02:00.0
logical name: eth0
version: 15
serial: 00:1d:72:0e:1d:4e
size: 100MB/s
capacity: 100MB/s
width: 64 bits
clock: 33MHz
capabilities: pm vpd msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.20 duplex=full firmware=N/A ip=10.1.1.3 latency=0 link=yes module=sky2 multicast=yes port=twisted pair speed=100MB/s
*-network
description: Wireless interface
product: AR242x 802.11abg Wireless PCI Express Adapter
vendor: Atheros Communications Inc.
physical id: 0
bus info: pci@0000:04:00.0
logical name: wlan0
version: 01
serial: 00:17:c4:09:b1:47
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+net5211 driverversion=1.52+,05/02/2007,5.3.0.45 latency=0 link=no module=ndiswrapper multicast=yes wireless=IEEE 802.11g


Please help thanks

[wieman01]

blommie,

DHCP is fine, so leave it like it is. The scan ("iwlist scan") recognizes your WPA secured network, therefore I don't thing that's an issue.

Can you connect to your network while all security is turned off? That's an important first step we got to take.

[jodef]

Is this method applicable to more recent versions of ubuntu? I ask because I am new to networking / wireless networking in ubuntu. Recently bought a linksys router right now I am posting using the wireless network w/out security enabled.

I had the wireless network configured to use WEP it was detected and I was prompted for security passphrase but when it connected it didn't auto receive an IP address. When I disabled the security setting everything works ok.

Will the instructions work using 8.04? had to downgrade from 8.10 problem with my intel 3945abg wireless card.

Thanks.

[blommie]

Hi Wieman01

Thanks for your reply and assistance. To answer your question: Yes if I turn off all security on the wireless router I can connect no problem at all. With WPA back on I cannot connect.

Thanks

[wieman01]

blommie,

DHCP is fine, so leave it like it is. The scan ("iwlist scan") recognizes your WPA secured network, therefore I don't thing that's an issue.

Can you connect to your network while all security is turned off? That's an important first step we got to take.
What about WEP secured ones? Success as well?

[wieman01]

Is this method applicable to more recent versions of ubuntu? I ask because I am new to networking / wireless networking in ubuntu. Recently bought a linksys router right now I am posting using the wireless network w/out security enabled.

I had the wireless network configured to use WEP it was detected and I was prompted for security passphrase but when it connected it didn't auto receive an IP address. When I disabled the security setting everything works ok.

Will the instructions work using 8.04? had to downgrade from 8.10 problem with my intel 3945abg wireless card.

Thanks.
They should also apply to 8.10, but that's the theory. I have not upgraded yet, so frankly I can only use common sense to judge. :-) To answer your question, yes, it should.

Neither WEP nor WPA does the job for you? That is odd, because WEP should by all means be OK.

[blommie]

Your question: What about WEP secured ones? Success as well?

Sorry is WPA and WEP the same? I have another laptop with Windows XP and it's configured for WPA and it works fine.


On the linux box only when I configure WPA security then I cannot connect when I disable all security in the router I can connect fine.

[wieman01]

Your question: What about WEP secured ones? Success as well?

Sorry is WPA and WEP the same? I have another laptop with Windows XP and it's configured for WPA and it works fine.


On the linux box only when I configure WPA security then I cannot connect when I disable all security in the router I can connect fine.
WPA and WEP aren't the same. Two different protocols. Please try out both. Not sure what's wrong at this stage.

[blommie]

Hi Wieman01

Yes I just changed the security to WEP and no problem I can connect no worries.

WPA is more secure than WEP correct? If so I would prefer WPA to work rather that WEP. You tell me I'm not a expert on these things.

Thanks for your help so far.

[wieman01]

Hi Wieman01

Yes I just changed the security to WEP and no problem I can connect no worries.

WPA is more secure than WEP correct? If so I would prefer WPA to work rather that WEP. You tell me I'm not a expert on these things.

Thanks for your help so far.
Then there is indeed a problem with WPA... dang. Well, WEP is very insecure (see signature) and it would take even unexperienced users very little time to crack the key. Personally I would never use WEP under any circumstances.

Not sure what's wrong at the moment. You use "ndiswrapper" for your wireless adapter and the corresponding Windows driver. Could you check on the manufacturer's website if there is a more up-to-date driver available that you could install? Thing is, you driver might not fully support WPA, therefore these issues.

[blommie]

Hi wieman01

How secure will a combination of WEP and MAC Filtering be?

[blommie]

. I have noticed something else when I start up my notebook I get for Kernels I can pick from I can't remember that before and it seemed the kernels were upgrade must have been when I did a auto update. The 4 I can choose from is:

Linux Mint Kernel 2.6.24-21
Linux Mint Kernel 2.6.24-21 Recovery Mode
Linux Mint Kernel 2.6.24-16
Linux Mint Kernel 2.6.24-16 Recovery Mode
Linux Mint Kernel memtest86+

There wont be a conflict will there?

[wieman01]

Hi wieman01

How secure will a combination of WEP and MAC Filtering be?
Completely useless. :-) You can actually clone/fake Mac addresses:

ifconfig eth1 down hw ether 00:00:00:00:00:01
ifconfig eth1 up
As simple as that.

[wieman01]

There won't be any conflict, don't worry. But what system are you on? Ubuntu 8.10?

[blommie]

No sorry I'm on Linux Mint Elyssa.

[kevdog]

Weiman

Dont know if you are actively maintaining this thread, however with Ibex (yes I read the disclaimer and it didn't say specifically tested with ibex), however the driver named to be used with wpa_supplicant is now almost always wext. Due to the changes with the wireless tools package, wpa_supplicant is now no longer compiled against the madwifi or ndiswrapper or intel sources. They now all default to wext. I think atmel may be an exception, however if using Ibex, wpa_supplicant -h will show specifically the sources wpa_aupplicant was compiled against.

[blommie]

Guys Wieman01 and kevdog

I did another command on my linux box namely:

lshw -class network

Please have a look and see if anything sticks out please I'm getting desperate all I want is for the wireless WPA connection to work as before:

lshw -class network
WARNING: you should run this program as super-user.
*-network
description: Ethernet interface
product: 88E8039 PCI-E Fast Ethernet Controller
vendor: Marvell Technology Group Ltd.
physical id: 0
bus info: pci@0000:02:00.0
logical name: eth0
version: 15
serial: 00:1d:72:0e:1d:4e
width: 64 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=sky2 driverversion=1.20 firmware=N/A ip=10.1.1.4 latency=0 module=sky2 multicast=yes
*-network
description: Wireless interface
product: AR242x 802.11abg Wireless PCI Express Adapter
vendor: Atheros Communications Inc.
physical id: 0
bus info: pci@0000:04:00.0
logical name: wlan0
version: 01
serial: 00:17:c4:09:b1:47
width: 64 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+net5211 driverversion=1.52+,05/02/2007,5.3.0.45 latency=0 module=ndiswrapper multicast=yes wireless=IEEE 802.11g

[wieman01]

Hi Kevdog,

Nice to hear from you.

I am still maintaining this thread, or say, I mean to. Good point. From your perspective, is this thread still relevant for Ibex users?

I tried out Kubuntu 8.10 last night and was impressed to see that Network Manager (yes, that very tool) hooked up to my network immediately and even let me configure a static IP address. Amazing.

No need for "ndiswrapper" (Ralink) either... Quite impressed.

So what do you think? Your tutorial seem more appropriate for all related questions than this one.

[blommie]

Hi I'm thinking about starting all over again by re-installing Elyssa or even upgrading to Felicia or another distro.

Can you please give me suggestions on that road please. All I want is a reliable wireless connection in the OS also I have a problem with my CD /DVD COMBO player so I will have to do the re-install/upgrade via USB .... What are you thoughts on that please as a layman I am open for suggestions.

Thanks

[kevdog]

weiman

Not sure if you are hanging out in the networking section a lot these days -- I get kind of burnt out over there also -- however this thread is totally relevant. I found network manager to work out of the box with both my broadcom and atheros card, however a lot of people are still resorting to wicd to make things work. Still others are modifying the interfaces file as you have suggested.

Wireless support in my opinion is really screwed up. Just when I think I have a handle on the chipsets, a new kernel is released along with new chipsets, and the old solutions don't work any longer. As an example, the old way I used to use with my Broadcom card using ndiswrapper, no longer works with any wpa2 based encryption. The b43 and madwifi modules however do connect without any problems.

Please keep support of this thread as long as you can.

See you around.

[kevdog]

Guys Wieman01 and kevdog

I did another command on my linux box namely:

lshw -class network

Please have a look and see if anything sticks out please I'm getting desperate all I want is for the wireless WPA connection to work as before:

lshw -class network
WARNING: you should run this program as super-user.
*-network
description: Ethernet interface
product: 88E8039 PCI-E Fast Ethernet Controller
vendor: Marvell Technology Group Ltd.
physical id: 0
bus info: pci@0000:02:00.0
logical name: eth0
version: 15
serial: 00:1d:72:0e:1d:4e
width: 64 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=sky2 driverversion=1.20 firmware=N/A ip=10.1.1.4 latency=0 module=sky2 multicast=yes
*-network
description: Wireless interface
product: AR242x 802.11abg Wireless PCI Express Adapter
vendor: Atheros Communications Inc.
physical id: 0
bus info: pci@0000:04:00.0
logical name: wlan0
version: 01
serial: 00:17:c4:09:b1:47
width: 64 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+net5211 driverversion=1.52+,05/02/2007,5.3.0.45 latency=0 module=ndiswrapper multicast=yes wireless=IEEE 802.11g

Just a thought -- I know the atheros 242x chipset is a royal pai in the butt, but why do you want to use ndiswrapper??? There are plenty of threads posted within the last 2 days on the networking subforum that show how to use the native madwifi drivers (which I think you have to compile -- SCARY -- no not really at all). I really would take a look at these threads and save yourself a lot of later headache. If you get started in one of the threads I can help you since I've compiled madwifi drivers like 1000 times (but not for the 242x chipset).

[blommie]

kevdog all I want is for my wpa wireless to work no matter how beggars can't be choosers so if it is ndiswrapper or ath_pci or a big 18 wheel driver and it get my WPA to work like it worked before I would be over the moon. So you tell me how to go about getting it sorted and I will be hanging on your lips so to speak.

I'm close to go back to the start and reload ELyssa from a DVD and do the hole thing over again but if I can avoid it would be great.

Thanks

[kevdog]

Do a search for Atheros 242x in the fourms, and then point me to the post. I'm not going to do all the work for you -- although you may not think so, but this is an excellent, and rather easy way to become independent and learn how to do things within Ubuntu. I will tell you its not hard to do, but I'm not going to specifically lead you by the hand at everystep.

PS Here is a tip: http://www.ubuntugeek.com/how-to-get-atheros-ar5007eg-or-ar242x-wireless-cards-may-be-other-models-working-in-ubuntu-810-intrepid-ibex.html

[wieman01]

Kevdog,

It's Wieman in fact, not Weiman. ;-) Always wanted to tell you that. :-)

I don't hang out in the wireless section a lot these day to be honest. I meant to but other stuff (I wouldn't more important but...) kept me from being more active. I should definitely get back into it, but I know it's in good hands at the moment.

Yes, I also got a little burned out... happens I guess. Keep up the good work, I know a lot of people appreciate it!

P.S.: I'll update this thread soonest. If you have further suggestions, let me know.

[blommie]

kevdog thanks for the tip so is it just a matter of implementing methode 1 in my notebook and see how I get on?

[kevdog]

Sorry wieman -- hope you were not offended. I see I've stuck my foot in my mouth many, many times.:(

[wieman01]

Sorry wieman -- hope you were not offended. I see I've stuck my foot in my mouth many, many times.:(
:-) Just kiddin'. No problem of course.

[misha680]

Hi, I believe this is correct for an ipw2100 card (I think), hidden network, WPA2 Enterprise, PEAP, Dynamic WEP, None for Phase2? Please let
me know if obvious errors. I will try tomorrow. My wired network is acting weird.


auto eth0
iface eth0 inet dhcp
wpa-driver wext
wpa-ssid ssid
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt IEEE8021X
wpa-eap PEAP
wpa-identity identity
wpa-password password


Thanks
Misha

[mssever]

My Requirements:
1. WPA2 / RSN
2. AES / CCMP
3. Hidden ESSID (no broadcast)
4. Static IP (because I use port forwarding & firewall, etc.)
5. Pre-shared key (no EAP)
@wieman01:

I noticed you haven't yet updated this guide for Intrepid. Since the version of NetworkManager in Intrepid now allows static IPs (finally!), and since NM has supported the other items on your requirements list for at least several Ubuntu releases, am I correct in understanding that your HOWTO is unnecessary for Intrepid? Or am I missing something (I don't have exotic hardware, and I only know the hardware I own...)?

[wieman01]

@mssever:

With Intrepid, yes, there is a good chance you won't need this tutorial. Static IP support for wireless is new (at least when using WPA), I hope you don't need this tutorial any longer.

[mssever]

@mssever:

With Intrepid, yes, there is a good chance you won't need this tutorial. Static IP support for wireless is new (at least when using WPA), I hope you don't need this tutorial any longer.
Perhaps the original post should be updated to that effect so Intrepid users realize that there's an easier way.

Personally, I've been using NetworkManager with WPA2 since Dapper (except for Gutsy when a bug forced me to go wired). Prior to Intrepid, I used my own hacked-together dynamic DNS setup to get around the lack of a static IP since I wanted to use NM instead of digging around at a lower level as your HOWTO does. With Intrepid, my hacks are obsolete.

[omer.qadir]

Hello

I have been trying to get my wireless to work and had some luck... but not done yet.

I have intrepid on a Gateway M280, with intel wireless pro 2200.

Network Manager would not connect so I scoured the internet and found manual wpa_supplicant solutions. Now I am able to connect intermittenly but not every time. So everytime I want to connect, I have to go through this routine of killing wpa_supplicant (using wpa_cli terminate) and then restart wpa_supplicant. On average, it takes about 5-10 attempts to connect.

My network is WPA-EAP with TKIP and MSCHAPV2 (some in the UK may know it as eduroam)

So I did the next logical thing... compared the logs from wpa_supplicant for successfull and failed connections. I am attaching relevant portions of the logs as well, but this is what i noticed. When the connection fails, the machine seems to repeatedly receive the same packet during the 4-way handshake (Pairwise Install ACK MIC). At other times, it just magically receives the next packet as well. Something wrong with key exchange maybe?

My connection is not very stable and has periodical disconnections and every time I need to go through this cycle... its very frustrating. Help would be greatly appreciated.

[Favux]

Hi omer.qadir,

While probably not relevant to your situation, several of us have discovered network manager is writing the wrong information in the keys and we have corrected it with gconf editor. We also have noticed that NM will rewrite those keys if it is invoked ie edit connections. On the off chance it's somehow related to your problem:

http://ubuntuforums.org/showthread.php?t=1010650

[Psycho Sonic]

I've followed every step in this and the only problem I have is that when I try to restart my network, I get this:


sudo /etc/init.d/networking restart
* Reconfiguring network interfaces... RTNETLINK answers: No such process
SIOCDELRT: No such process
RTNETLINK answers: No such process
SIOCDELRT: No such process
ioctl[SIOCSIWPMKSA]: Invalid argument
[ OK ]

I'm on Hardy and my card is a WPC54G v2.
A strange thing is that I can't connect to WEP either. When I click on either one (in wicd) I get "This network requires encryption to be enabled."

[wieman01]

I've followed every step in this and the only problem I have is that when I try to restart my network, I get this:

I'm on Hardy and my card is a WPC54G v2.
A strange thing is that I can't connect to WEP either. When I click on either one (in wicd) I get "This network requires encryption to be enabled."
What chipset is your wireless adapter? Please also run & post these for me:

sudo iwlist scan

sudo lshw -C network

[mikhmv]

How can I connect to wifi in ubuntu? Our network has following configuration:
* Network SSID
WIRELESS-PITTNET
* Security Type
WPA-Enterprise
* Encryption Type
TKIP
* Authentication Method
PEAP
EAP-MSCHAPv2
In ubuntu I didn't find how to change encryption type. Before this I used kubuntu and internet worked without any problems.
Thanks advance.

[mikhmv]

sorry, I found solution.
our network used PEAP version 0. in ubuntu by default version 1. when i changed it wifi start work

[Psycho Sonic]

What chipset is your wireless adapter? Please also run & post these for me:
My chipset is Texas Instruments ACX111. I already followed this (http://ubuntuforums.org/showthread.php?t=324148) thread on installing ndiswrapper for it.

That was weird. My card was disabled/turned off, i had to eject it then insert it again.


sudo iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:0D:67:00:4F:F2
ESSID:"Softcom_WiFi_Call_888-4-SOFTCOM"
Protocol:IEEE 802.11b
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:37/100 Signal level:-72 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 02 - Address: 00:1E:58:F3:D1:21
ESSID:"The Garner Fam"
Protocol:IEEE 802.11b
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:100/100 Signal level:-29 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK



sudo lshw -C network
*-network:0 UNCLAIMED
description: Ethernet controller
product: RTL8180L 802.11b MAC
vendor: Realtek Semiconductor Co., Ltd.
physical id: 4
bus info: pci@0000:02:04.0
version: 20
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list
configuration: latency=64 maxlatency=64 mingnt=32
*-network:1
description: Ethernet interface
product: 82801DB PRO/100 VE (MOB) Ethernet Controller
vendor: Intel Corporation
physical id: 8
bus info: pci@0000:02:08.0
logical name: eth0
version: 83
serial: 00:e0:b8:72:ac:01
size: 100MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e100 driverversion=3.5.23-k4-NAPI duplex=full firmware=N/A ip=192.168.0.102 latency=64 link=yes maxlatency=56 mingnt=8 module=e100 multicast=yes port=MII speed=100MB/s
*-network
description: Wireless interface
product: ACX 111 54Mbps Wireless Interface
vendor: Texas Instruments
physical id: 1
bus info: pci@0000:03:00.0
logical name: wlan0
version: 00
serial: 00:0f:66:b3:75:58
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+lstinds driverversion=1.52+Linksys,03/10/2004,6.0.0.18 latency=64 link=no module=ndiswrapper multicast=yes wireless=IEEE 802.11g

[wieman01]

Psycho Sonic,

That is weird. Your adapter seems to be alright.

Have you tried the option "Connect to other wireless network" using Network Manager? Then enter the network's name & key. There shouldn't be an issue.

[Psycho Sonic]

Psycho Sonic,

That is weird. Your adapter seems to be alright.

Have you tried the option "Connect to other wireless network" using Network Manager? Then enter the network's name & key. There shouldn't be an issue.

Do mean Knetwork Manager? Because that won't even detect my wireless card, and Manual Configure just sends me to Network Settings which won't let me do... anything. Wicd just tells me "This network requires encryption to be enabled."

I should probably mention that I'm on KDE.

...am I gonna have to switch back to windows?

[wieman01]

KNetworkManager will do. I am also on KDE.

When you click on "Connect to other wireless network" and check the device name in the following dialog, what does it say?

[omer.qadir]

Hi omer.qadir,

While probably not relevant to your situation, several of us have discovered network manager is writing the wrong information in the keys and we have corrected it with gconf editor. We also have noticed that NM will rewrite those keys if it is invoked ie edit connections. On the off chance it's somehow related to your problem:

http://ubuntuforums.org/showthread.php?t=1010650

Hey Favux,

Thanks for that. Thats not a bad idea. My problem may well be related. I'll look into it and post back here if it helps.
Sincerely
Omer

[PCDoc]

Hi there, I have a problem that I've tried resolving for myself and with helpful posts from dmizer in another thread.
I've been on this now for about a week (which makes me wonder if it's worth it lol).

Basically, after a lot of struggling, I managed to get wpa_supplicant to connect to the internet after a fashion.

What's happening is this:

My wifi access point is WPA2-TKIP and usually has the SSID hidden.
I couldn't connect with a hidden ssid so I set it to show SSID.

Now, I've followed the guide at the start of this thread as dmizer suggested and have rebooted and what happens when you reboot is about halfway through boot up, it slows down and looks for DHCPREQUEST and finds nothing.

So when ubuntu is booted I tried running this in terminal:

sudo wpa_supplicant -c/etc/wpa_supplicant.conf -iwlan0 dhclinet wlan0

but it tells me there is another instance of wpa_supplicant running in var/run and it may not have terminated correctly.

So I go to var/run and in there is a wpa_supplicant folder and a file called wpa_supplicant.wlan0.pid

So in terminal I kill the process id and then run

sudo wpa_supplicant -c/etc/wpa_supplicant.conf -iwlan0 dhclinet wlan0
which then runs and I get internet.

I cant understand what's going on.

here is my wpa_supplicant.conf

ctrl_interface=/var/run/wpa_supplicant
#ap_scan=1

network={
ssid="myssidhere"
scan_ssid=1
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP
psk="mypasskey"
}

and here is my interfaces file


auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid myssidhere
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 8b79c14a1311970##############################
pre-up wpa_supplicant -Dwext -wlan0 -BW -c/etc/wpa_supplicant wpa_supplicant.conf post-down killall -q wpa_supplicant


If anyone can shed some light on why the wireless conenction is not starting and connecting properly when ubuntu starts up, please share =)

Many thanks,

(A slightly bauld from hair pulling) Mike.

EDIT: The reason I'm doing things this way is:
A) I need WPA2-TKIP security and
B) NetworkManager does not let me run lan and wifi connections together which I need to do to share the internet that comes in via the wireless to other computers via the lan connection.

So far I haven't even gotten to the lan side of things yet, I'm still trying to get a stable WPA2-TKIP connection that starts up and connects automatically when Ubuntu does.

Incidentally, I have followed the start up script that was posted in post #2 at the start of this thread.

Thanks again.

I'm totally new to linux other than accessing a web server through shell so I only know a little.
This ubuntu box has been built to act as a secured gateway ICS box.

Basically I have a wireless router downstairs which the ubuntu box (located upstairs) is supposed to connect to via a PCI wireless card.
This internet conenction should then go to the ubuntu box's on board ethernet and then from there to a wired router to disperse the internet to any computer connected to that router.

I wanted to use ubuntu as a secured gateway and file server and chose linux rather than windows due to linux being more secure.
I repair and maintain PC's and any I need to connect to the internet, I wanted to do it as securely as possible to protect any sensitive data that may or may not be on those machines.

[PCDoc]

Anyone???
I don't mean to stress but I could do with some help on this rather urgently.

Been at it a week and getting no where fast.

I'm open to any suggestions anyone might have that may help.

Thanks, Mike.

[wieman01]

PCDoc,

Please try this (leave out the last line of your settings):

auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid myssidhere
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 8b79c14a1311970##############################
Then reboot and do a:

sudo ifdown -v wlan0
sudo ifup -v wlan0
Please post the output message.

Have you also tried to use a static IP address? I have seen such DHCP issues before.

[PCDoc]

Many thanks for replying wieman01.

Ok, did as you suggested with the last line of the interfaces file.
I also assigned a static address, gateway, subnet etc as you suggested.

I rebooted.

At start up ubuntu slowed down about halfway in again and I could see DHCP Client by Internet Consortium then it issued DHCPRELEASE and dropped the static IP I gave it in interfaces file.

It then began to DHCPDISCOVER again looking at 255.255.255.255 on port 67,
Found nothing and went sleep.

Ubuntu booted up and I Checked and there was no internet connection so I issued the commands you told me to.

Here are the results:

sudo ifdown -v wlan0


Configuring interface wlan0=wlan0 (inet)

run-parts --verbose /etc/network/if-down.d

run-parts: executing /etc/network/if-down.d/avahi-autoipd

run-parts: executing /etc/network/if-down.d/wpasupplicant

dhclient3 -r -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0

There is already a pid file /var/run/dhclient.wlan0.pid with pid 4568

killed old client process, removed PID file

Internet Systems Consortium DHCP Client V3.1.1

Copyright 2004-2008 Internet Systems Consortium.

All rights reserved.

For info, please visit http://www.isc.org/sw/dhcp/



wmaster0: unknown hardware address type 801

wmaster0: unknown hardware address type 801

Listening on LPF/wlan0/00:a1:b0:90:0b:b9

Sending on LPF/wlan0/00:a1:b0:90:0b:b9

Sending on Socket/fallback

DHCPRELEASE on wlan0 to 192.168.123.1 port 67

ifconfig wlan0 down

run-parts --verbose /etc/network/if-post-down.d

run-parts: executing /etc/network/if-post-down.d/avahi-daemon

run-parts: executing /etc/network/if-post-down.d/wireless-tools

run-parts: executing /etc/network/if-post-down.d/wpasupplicant

wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan0.pid

Stopped /sbin/wpa_supplicant (pid 4533).

wpa_supplicant: removing /lib/init/rw/sendsigs.omit.d/wpasupplicant.wpa_supplicant.wlan0.pid




sudo ifup -v wlan0


Configuring interface wlan0=wlan0 (inet)

run-parts --verbose /etc/network/if-pre-up.d

run-parts: executing /etc/network/if-pre-up.d/wireless-tools

run-parts: executing /etc/network/if-pre-up.d/wpasupplicant

wpa_supplicant: wpa-driver wext

wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -D wext -q -f /var/log/wpa_supplicant.wlan0.log -C /var/run/wpa_supplicant

Starting /sbin/wpa_supplicant...

wpa_supplicant: creating sendsigs omission pidfile: /lib/init/rw/sendsigs.omit.d/wpasupplicant.wpa_supplicant.wlan0.pid

wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan0

wpa_supplicant: wpa-ap-scan 1 -- OK

wpa_supplicant: configuring network block -- 0

wpa_supplicant: wpa-ssid "IcArUsNeT" -- OK

wpa_supplicant: wpa-psk ***** -- OK

wpa_supplicant: wpa-pairwise CCMP -- OK

wpa_supplicant: wpa-group CCMP -- OK

wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK

wpa_supplicant: wpa-proto RSN -- OK

wpa_supplicant: enabling network block 0 -- OK



dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0

Internet Systems Consortium DHCP Client V3.1.1

Copyright 2004-2008 Internet Systems Consortium.

All rights reserved.

For info, please visit http://www.isc.org/sw/dhcp/



wmaster0: unknown hardware address type 801

wmaster0: unknown hardware address type 801

Listening on LPF/wlan0/00:a1:b0:90:0b:b9

Sending on LPF/wlan0/00:a1:b0:90:0b:b9

Sending on Socket/fallback

DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8

DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10

DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 21

DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18

DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4

No DHCPOFFERS received.

No working leases in persistent database - sleeping.

run-parts --verbose /etc/network/if-up.d

run-parts: executing /etc/network/if-up.d/avahi-autoipd

run-parts: executing /etc/network/if-up.d/avahi-daemon

run-parts: executing /etc/network/if-up.d/mountnfs

run-parts: executing /etc/network/if-up.d/ntpdate

run-parts: executing /etc/network/if-up.d/wpasupplicant




So still no internet, so I again I ran


sudo wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -B


which told me another instance of wpa_supplicant was running.


ctrl_iface exists and seems to be in use - cannot override it
Delete '/var/run/wpa_supplicant/wlan0' manually if it is not used anymore
Failed to initialize control interface '/var/run/wpa_supplicant'.
You may have another wpa_supplicant process already running or the file was
left by an unclean termination of wpa_supplicant in which case you will need
to manually remove this file before starting wpa_supplicant again.


I terminated the process ID and ran that command again which game me this:


CTRL-EVENT-SCAN-RESULTS
CTRL-EVENT-SCAN-RESULTS
CTRL-EVENT-SCAN-RESULTS
CTRL-EVENT-SCAN-RESULTS
CTRL-EVENT-SCAN-RESULTS
CTRL-EVENT-SCAN-RESULTS
Trying to associate with 00:06:4f:61:2b:22 (SSID='IcArUsNeT' freq=2412 MHz)
Associated with 00:06:4f:61:2b:22
WPA: Key negotiation completed with 00:06:4f:61:2b:22 [PTK=TKIP GTK=TKIP]
CTRL-EVENT-CONNECTED - Connection to 00:06:4f:61:2b:22 completed (auth) [id=0 id_str=]
WPA: Group rekeying completed with 00:06:4f:61:2b:22 [GTK=TKIP]


And the internet connected.
But it's not after rebooting.

Also fter rebooting I removed the SH start up script that was mentioned in post #2 of this thread and now it no longer does the DHCPRELEASE and DHCDISCOVER thing at boot up which I thought was interfering (I may be wrong and can easily put it back).

However, I can't get internet anymore.
I tried terminating the PID of the already running wpa_supplicant and running the wpa_suplicant command above and I get nothing.

It just repeats CTRL-EVENT-SCAN-RESULTS in the terminal window.

Now I'm really confoooosed.
I hope I have provided all the info and more that you requested.
I have tried to be detailed and methodical to help you to help me.

Many many thanks Mike.

[wieman01]

You should not have to run:

sudo wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -B

...if you configure WPA using the "interface" configuration file. Either one is enough.

Could you post the contents of "interfaces" after enabling it to use a static IP address? It's still trying to get an address via DHCP and that is odd.

[PCDoc]

Hi again weimoan01,

Sorry I haven't replied sooner, but I've not been around and so haven't been working on the server.

Please find a copy and paste of my interfaces file:



auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dhcp
address 192.168.123.40
gateway 192.168.123.1
dns-nameservers 192.168.123.1
netmask 255.255.255.0
wpa-driver wext
wpa-ssid IcArUsNeT
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 8b79c14a1311970a6fec1578326753b80f62c885dd8b5c5c22 7148d81c73f8c8


This is exactly as it sits.
As previously mentioned, my SSID was hidden, but I set it to broadcast while getting this working.

Ideally, if we get this resolved, I'd like it to go back to being hidden if possible.

Thanks again, your continued support is extremely valued!

Mike.

[holotropik]

Thank you! thread number 50 solved my problem...now i get wireless connection after boot-up.
Cheers ;)

[wieman01]

PCDoc,

Try this instead and post back please:

auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet static
address 192.168.123.40
gateway 192.168.123.1
dns-nameservers 192.168.123.1
netmask 255.255.255.0
wpa-driver wext
wpa-ssid IcArUsNeT
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 8b79c14a1311970a6fec1578326753b80f62c885dd8b5c5c22 7148d81c73f8c8

[PCDoc]

Wow, I can't beleive I missed that..
Still set to DHCP instead of static.. My brain must be fried lol.

I changed it to static, but still the same.
No internet. :(

[wieman01]

Happens...

Then what's the output of this now:

sudo ifdown -v wlan0

sudo ifup -v wlan0

[ieshadover]

I just want to cry now

[kevdog]

Why?

[geezerone]

Wow, I can't beleive I missed that..
Still set to DHCP instead of static.. My brain must be fried lol.

I changed it to static, but still the same.
No internet. :(

Saw you are having difficulites - my sympathies - been there, T-shirt etc and many hours staring at the wireless icon waiting for connections!

Hidden ESSID isn't well supported so you may have to run with advertised ESSID. There are some chipsets which work I understand but I have tried a couple and didn't work. I used static IP too as this was often less hassle and quicker to work.

You could try the command after reboot of 'sudo /etc/init.d/networking restart' and see if that brings up your internet. If it does then add the command to the /etc/rc.local file (removing the top lhs # so the script will run of course) as this runs after all run level processes on boot-up and was the way I got a wireless network to connect. I had to manually configure my interfaces and forget Network Manager or WICD completely.

Regarding you ICS query, have you considered firestarter (http://www.fs-security.com/docs/introduction.php#features)?

Hope you make progress. :)

[misha680]

Thank you for your guide, I have the following on two computers (both 8.04):



auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid ssid
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP TKIP
wpa-group CCMP TKIP
wpa-key-mgmt WPA-PSK
wpa-psk psk


works fine on one computer for the hidden ssid (ipw2100), on the other (iwl3945) works sometimes, but often dhcp does not catch a lease. Sometimes it works on the other. NM works fine on both. Any ideas?

Thanks
Misha

[wieman01]

Some adapters have issues with hidden SSIDs. Try not to hide it and see if it gets any better. Hiding the SSID does not really add extra security anyway.

[emerging]

The house I moved to has wifi set up with WPA-PSK (ver. 1), and I have no access to the router/AP to view or change any of the settings. All I have are the ESSID and passphrase. The ipw2100 wifi adapter refuses to associate with the AP. My wife's Windows XP laptop connects with the exact same passphrase. Can someone please try to help?

[afeasfaerw23231233]

I have your tutorial but doesn't work
I am using realtek 8187L with ndiswrapper windows 98 driver.
Here's my /etc/network/interfaces


auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid dlink
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 899dd8474982835b4dc01d7f65415ed4f8c469b8cf22227823 933baa502cc673

Here's what I get from sudo /etc/init.d/networking restart

* Reconfiguring network interfaces... There is already a pid file /var/run/dhclient.wlan0.pid with pid 4041
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:22:43:74:7b:05
Sending on LPF/wlan0/00:22:43:74:7b:05
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 192.168.123.1 port 67
Ignoring unknown interface eth0=eth0.
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:22:43:74:7b:05
Sending on LPF/wlan0/00:22:43:74:7b:05
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 21
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
[ OK ]
coppen@coppen-laptop:~$

it says
There is already a pid file /var/run/dhclient.wlan0.pid with pid 4041
killed old client process, removed PID file what's that mean?

I've also tried the setting of WPA2, didn't work either. Is that the problem of this line

wpa-driver wext?
Many thanks!

[wieman01]

Mmmm... the Win98 driver? That does not sound right. Have you checked which driver version you ought to use?

[afeasfaerw23231233]

The preconfig of my wireless by ubuntu seemed not working right. It disconnected ramdomly. So I searched the forum and found these I followed their instructions:
http://ubuntuforums.org/showthread.php?t=493958
http://ubuntuforums.org/showthread.php?t=678094

The OP of the second thread mentioned that Windows 98 driver works. And it works for me too. So far no abnormal disconnection though the signal strength was 30% weaker than in M$ XP.

But I can't even use WEP on it.

[afeasfaerw23231233]

edit: actually I don't know whether my wifi card was realtek 8187B or 8187L. In xp the device manager shows it as "8187". But the xp driver cd comes with my notebook says it is B but it failed to work. So I frustrately searched around and finally discover there were 8187 B / L / SE three versions from realtek's website. I tried them one by one and only L worked in XP. So I assume it is 8187 L.

[afeasfaerw23231233]

Hi, I found out this guide http://ubuntuforums.org/showthread.php?t=571188 . The op of that tutorial said I should try it first.

[wieman01]

Try to get your card working before you enabled security. Otherwise it will be a moving target.

[excbuntu]

my laptop (asus eee 1000HA) doesn't acquire a wireless connection unless someone logs in after boot. in addition, after login, it takes an additional 30 seconds before i get connected automatically.

i'm using network manager and intrepid. my /etc/network/interfaces file contains the following:


auto lo
iface lo inet loopback

please help. thanks.

[wieman01]

Hello,

I think this has little to do with this tutorial. It would make more sense if you opened your own thread in the wireless section, there are many competent people who will be able to help you. :-)

[wieman01]

I am closing this thread as it seems less relevant than it used to be. If you still think it is relevant, please send me a PM.

I thank everybody for their contributions.

[wieman01]

Upon request from users, I am re-opening this thread and will update it in the weeks to come.

[kevdog]

Thanks for reopening the thread. I always thought it was a classic

[wieman01]

Thanks for reopening the thread. I always thought it was a classic
Thanks, Kevdog. I thought it was sort of outdated, but never say never I guess. Time to roll up my sleeves... it's been a while.

I sort of prefer your method now though. Came to like it a lot.

[kevdog]

One thing is true about linux -- you can never learn too many ways to solve a problem -- this particularly given the fact the methods change between kernel versions. If anyone really wants to become a ubuntu/linux connoisseur, then they really have to spend time reading different ways of accomplishing things. Unfortunately or fortunately this requires time and practice. Although this tutorial may not be as applicable as it once was with prior kernel versions and releases, its essential for anyone learning how to troubleshoot/configure there wireless card -- a problem for thousands of users. I'd vote this thread as required reading along with several others, however that's just me.

One idea that never got of the ground is a recommended reading / or recommended thread reading list for users. This isn't just for beginners. Unfortunately this project would actually require an editor or authoritarian that could discrimate between what is good information, and what is not. It seems I'm always trolling the forums in search of high quality information on various topics. This process is highly inefficient since I end up spending >90% of my time reading noninformative posts. As a method of giving back to community and way to speed up the learning curve -- I always thought a recommended reading list was a good idea. This idea isn't novel or unique, however it just seems like some of the other methods such as the ubuntu wiki are poorly maintained. I guess its the never ending battle or search for the holy grail of how best to distill useful information to others. I'm not sure this problem will ever be solved.

Either way -- thanks for reopening the thread!

[wieman01]

Thank you for your words. And I agree with you, there should be a list of stuff that new Ubuntu users should read first to gain a thorough understanding. I also know most people won't do it because it takes time and it's easier to post a question in the forums and get a tailored reply immediately. Guess that's the world we live in.

That should not keep you from maintaining such a list. With a bit support from me, I am sure we could make it a sticky thread also. It's an offer, please let me know if you think it's a worthwhile undertaking. You'd have my support.

[epha]

hi,

I have a broadcom 4306 rev2 wireless card, and I can connect to the internet using ndiswrapper driver. I am trying to get wpa2 to work. Can you help ?

I have followed the instructions and looked through a lot of posts -but no sucess yet.

I changed the last two lines in "/etc/network/interfaces"
to:

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid <my_essid>
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk <my_hexkey>

thankyou for the tutorial, and all the follow up support.

epha

[epha]

here is a link to all the requested info:

http://zeroplusequals.net/downloads/wireless_info.txt

[wieman01]

Hello,

WPA authentication seems to work, that's not the problem. Have you disabled Network Manager?

Second, I would also check out WPA1, maybe the Windows driver does not support WPA2.

Then please also post:

sudo iwlist scan
Let's see...

[epha]

oh - wpa1 does work. this is the output of iwlist scan:
saul@saul-desktop:~$ sudo iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

pan0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:1F:33:86:4B:4C
ESSID:"vbroadband"
Protocol:IEEE 802.11b
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:32/100 Signal level:-75 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK



Thanks! (Perhaps I should have done a bit more tinkering before asking.) I am guilty of this: 'it's easier to post a question in the forums and get a tailored reply immediately. Guess that's the world we live in.' Next time I'll do more tinkering before asking. Thankyou.

epha

[wieman01]

I think you got it solved no, right? :-) It's a WPA1 secured network.

No worries, these things happen.

[epha]

Hi,

In the interests of clarity and incase anyone else is having trouble with this driver and wpa2 - the network was wpa2 before, and I couldn't connect, so it may be that the driver (ndiswrapper) doesn't handle wpa2. I changed the router security to WPA1 and then changed the details in my "/etc/network/interfaces" file, and it worked with that.
cheers,
epha

[espinosa]

hi, i've been trying to use wpa1 for my AP.

auto ath0
iface ath0 inet static
address 192.168.23.1
netmask 255.255.255.0
broadcast 192.168.23.255
network 192.168.23.0
wpa-driver madwifi
wpa-ssid security-mesh
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk 36ee01b32d5f137e915d340c4d8b4c0e...

whenever i tried to restart the network, /etc/init.d/networking restart, there's an error :

Reconfiguring network interfaces...ioctl[SIOCSIWMODE]: Invalid argument
Could not configure driver to use managed mode
done.

i use adhoc mode for this... Can you tell me what's the problem ?
tx

[wieman01]

Please try...

wpa-driver wext
...rather than...

wpa-driver madwifi
Does it make a difference?

[espinosa]

Please try...

...rather than...

Does it make a difference?

it doesn't make any difference.
there's still an error :


Debian-Security:/# /etc/init.d/networking restart
Reconfiguring network interfaces...ioctl[SIOCSIWMODE]: Invalid argument
Could not configure driver to use managed mode
done.

i tried to check using iwconfig and iwlist scan, but i can't find my adhoc network there.

Debian-Security:/# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

eth1 no wireless extensions.

wifi0 no wireless extensions.

sit0 no wireless extensions.

ath0 IEEE 802.11g ESSID:"security-mesh"
Mode:Ad-Hoc Frequency:2.422 GHz Cell: 02:02:6F:54:04:22
Bit Rate:0 kb/s Tx-Power:16 dBm Sensitivity=0/3
Retry:off RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=13/94 Signal level=-81 dBm Noise level=-94 dBm
Rx invalid nwid:26 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


Debian-Security:/# iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Interface doesn't support scanning.

wifi0 Interface doesn't support scanning.

sit0 Interface doesn't support scanning.

ath0 Scan completed :
Cell 01 - Address: 00:90:4C:91:00:01
ESSID:"telematika"
Mode:Master
Frequency:2.462 GHz (Channel 11)
Quality=9/94 Signal level=-86 dBm Noise level=-95 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100

i installed wpasupplicant from repository because whenever i installed from sourcecode, it always fail.

[wieman01]

But hey, the scan says all security is off. Have you enabled WPA on the router?

[espinosa]

But hey, the scan says all security is off. Have you enabled WPA on the router?

as far as i know, i've enabled it.
i'm confused here. i installed the wpa_supplicant but there's no folder/file in /var/run/wpa_supplicant. Is it ok or it indicates my installation was fail ?
it keeps getting an error and i don't why.
i read some forums and they said that adhoc mode doesn't support 4 this wpa. is it right ? i switch to master mode but it keeps send me that error.

[papibe]

Hi all,
I’m not able to set up my wireless connection using Xubuntu 9.04 RC.I have a 2Wire wireless router set to:
Authentication: WPA2-PSK
Encryption: AES
SSID broadcast disable.

My wife’s HP (with XP) worked immediately. My Ubuntu 8.10 Toshiba also is working fine. But my Dell with Jaunty is getting me lots of trouble. It used to have Xubuntu 8.04 on it, and it worked fine with regular WEP. Now that I upgraded both OS and wireless security is not connecting at all.

After the install, I encountered a nasty bug where there was no way to set the security protocol and key. I connected a Ethernet cable and updated xubuntu. Finally, every field was there to set. I’m using the same Netgear PCMCIA card in both my Toshiba and my Dell (the same actual card which I unplugged from one to use in the other). I’ve tried to use both the default driver and the madwifi (using the Hardware Drivers) with no luck.

I took a look around the forums before posting here. I found lots of ways to use wpa, but all of them involve editing files with particular formats. Although I can follow those instructions, it doesn’t make sense to me to solve this kind of problem like that. Isn’t a simple way to do it using the graphical interface? or, Is Xubuntu not able to work with wpa2 as a design?

Maybe it’s a bug, since it works in 8.10 and not in 9.04 RC.

Any help would be much appreciated,
Thanks in advance

Notes: (1) Wpasupplicant is installed and is the newest version (from apt-get). (2) Unfortunately my Dell is old, and can’t take the much larger Ubuntu.

[kevdog]

papibe

can you try wpa2 with tkip?

[papibe]

kevdog: yes, I tried it out.

It did not work with Xubuntu 9.04 RC. This time it asked me for the key several times before failing.

Thanks for the suggestion, any other idea?

[arobinson]

Broken in Jaunty...

I have been running great on Intrepid, just upgraded to Jaunty tonight and my wireless is dead.

WPA2 with AES, no SSID broadcast, and MAC filtering enabled.

My card is the EDIMAX EW-7128G IEEE 802.11b/g PCI Wireless Card

lspci output:

01:08.0 Network controller: RaLink RT2561/RT61 802.11g PCI
Subsystem: RaLink Device 2561
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 32, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 18
Region 0: Memory at fdef0000 (32-bit, non-prefetchable) [size=32K]
Capabilities: <access denied>
Kernel driver in use: rt61pci
Kernel modules: rt61pci


My /etc/network/interfaces (no I do not use NetworkManager):

auto lo
iface lo inet loopback

auto eth0 wlan0

iface eth0 inet static
address 192.168.1.1
netmask 255.255.255.0

iface wlan0 inet dhcp
wireless-essid myhiddenssid
pre-up wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -B -f/var/log/wpa_supplicant.log
post-down killall -q wpa_supplicant


My /etc/wpa_supplicant.conf:

ctrl_interface=/var/run/wpa_supplicant
#ap_scan=2

network={
scan_ssid=1
key_mgmt=WPA-PSK
ssid="myhiddenssid"
psk=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
proto=WPA2
eap=TLS
}


My iwconfig output:

lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11bg ESSID:"myhiddenssid"
Mode:Managed Frequency:2.437 GHz Access Point: Not-Associated
Tx-Power=16 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


ifconfig output:

wlan0 Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx
inet6 addr: fe80::21f:1fff:fe32:5e6e/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:624 (624.0 B)

wlan0:avahi Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx
inet addr:169.254.4.146 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1

wmaster0 Link encap:UNSPEC HWaddr xxxxxxxxxxxxx
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)


What could be going on? Any suggestions on anything to back-port or try?

This is especially hard to work on as this is a Mythbuntu box with no keyboard or mouse and it is in a different room than my TV. Luckily I have a wired ethernet port with a switch attached so I can use my laptop to get on the box.


-------

UPDATE: I got this to work with the manufacturer's drivers. The bug I filed and how to fix it can be found here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/366170

Hope that helps anyone that experiences my problem.

[papibe]

It is looking more like a bug every day now. I also tried the “manual” way as described by wieman01 in the thread’s beginning… not working.

As much as disappointed I am, I wonder if there is a way let the right people know about this.

[wieman01]

Papibe,

You should probably file a bug report on Launchpad. This is weird.

I heard Network Manager's handling of non-broadcasting SSIDs is broken, at least in Kubuntu by the way. Just in case anybody would like to know.

[codedmin]

I have the same problem i buy an broadcom wifi card to put in my 901go so i can connect with osx. With jaunty betas i can connect with the b43 drivr but with the jaunty final release no juice :S

Only wpa wpa2 personal option is show but i need wpa2 entreprise..


Any info??

Thanks

[kevdog]

Can wicd do wpa enterprise? If so I suggest you use this tool!

[martinbures]

I think that this is a regression. Worked fine for me in 8.10. In 9.04, it will connect every now and then - when it does, it takes _MINUTES_. Otherwise, it keeps failing and asking for passwords. This is on an atheros-based macbook pro.

[wieman01]

I think that this is a regression. Worked fine for me in 8.10. In 9.04, it will connect every now and then - when it does, it takes _MINUTES_. Otherwise, it keeps failing and asking for passwords. This is on an atheros-based macbook pro.
You can try Kevdog's approach then. Works fine for me on 9.04.

[martinbures]

I am reading this thread from the bottom up, so forgive me if I say something dumb...

Is this what you were referring to?

can you try wpa2 with tkip?

[wieman01]

I am reading this thread from the bottom up, so forgive me if I say something dumb...

Is this what you were referring to?
Sorry, dude. This is the one I am referring to:

http://ubuntuforums.org/showthread.php?t=571188

Another great source.

[thaltek]

this is quite an annoying quirk....

the wpa i have at home requiers a network key and works flawlessly....

however my laptop is unable to link with the wpa wifi at purdue uni.... :(

[wieman01]

this is quite an annoying quirk....

the wpa i have at home requiers a network key and works flawlessly....

however my laptop is unable to link with the wpa wifi at purdue uni.... :(
Well, that's probably because they use WPA security with authentication by username and password. I advise you have a chat with the network's admin and see what the requirements are.

WICD can do all sorts of protocols, it might be the tool for you.

[amainejr]

This method has been working for me for about 3 weeks, flawlessly. I moved my DLink router into another room, along with the modem, set it up, and it worked perfectly. Last night, I downloaded Oracle 11g db software, and this morning I woke up and I can no longer connect to the router. I've been using WPA2 with no broadcast on the 802.11b+g setting. I'm lost as to why it quit working. `iwlist scan` recognizes the router, along with all of it's security settings. When I type `iwconfig`, I get "Access-Point: not associated." Any idea why the sudden change? I do recall running the update manager last night before bed, updating about 6 packages, and I continued working. The download was still going when I went to bed, and was complete this morning. No one else touched it, and the logs don't report any unauthorized logins. Any ideas?

[wieman01]

Could you post everything that you find in the section "Post this if you are stumped"? We'll find out what's happening. :-)

[amainejr]

Sorry. Will repost under "Post this if you are stumped".

[amainejr]

Okay


# route
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 * 255.255.255.0 U 0 0 0 eth1
link-local * 255.255.0.0 U 1000 0 0 eth1
default 192.168.2.1 0.0.0.0 UG 100 0 0 eth1




# iwconfig
eth1 IEEE 802.11bg ESSID:"" Nickname:""
Mode:Managed Frequency:2.442 GHz Access Point:Not-Associated
Bit Rate:54 Mb/s Tx-Power:32 dBm
Retry min limit:7 RTS thr:off Fragment thr:off
Power Managementmode:All packets received
Link Quality=5/5 Signal level=0 dBm Noise level=0 dbm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


# sudo iwlist scan
Cell 01 - Address: 00:17:3F:A8:90:79
Essid:""
Mode:Managed
Frequency:2.442 GHz (Channel 7)
Quality:4/5 Signal level:-64 dBm Noise level:-92 dBm
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
Preauthentication Supported
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s;
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s;
48 Mb/s; 54 Mb/s;




# sudo lshw -C network
*-network
description: Wireless interface
product: BCM4311 802.11b/g WLAN
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:06:00.0
logical name: eth1
version: 01
serial: 00:14:a5:fc:c5:f2
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=wl0 driverversion=5.10.79.10 ip=192.168.2.4 latency=0 module=wl multicast=yes wireless=IEEE 802.11bg



# sudo cat /etc/network/interfaces
auto lo
iface lo inet loopback

mapping hotplug
script grep
map eth0

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet static
address 192.168.2.4
gateway 192.168.2.1
dns-nameservers 192.168.2.1
netmask 255.255.255.0
wpa-driver wext
wpa-ssid maine
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 38ce8f42dd9a635353e4e0d66a2bba10021c36f005bff9734e 77a7b96daa0265



# sudo ifdown -v <your_interface>
Configuring interface eth1=eth1 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/wpasupplicant
route del default gw 192.168.2.1 metric 100 eth1
ifconfig eth1 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant




# sudo ifup -v <your_interface>
Configuring interface eth1=eth1 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/dhclient3-apparmor
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.eth1.pid -i eth1 -D wext -q -s -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1

ifconfig eth1 192.168.2.4 netmask 255.255.255.0 up
route add default gw 192.168.2.1 metric 100 eth1
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant


The only thing I've noticed, is that the wpa_supplicant failed to start. Any tips on that? Sorry about the format. I had to type it all out by hand.

[rvgsd]

Hi All,
I have recently installed Ubuntu 9.04, and a new user.
I have BCM 4306 with the drivers auto-installed by ubuntu using b43-fwcutter.

I am able to connect to the Unsecured Networks but not my secured Network which is Wpa2.

I Opened "/etc/network/interfaces":

auto lo
iface lo inet loopback


It does not contain the line:
auto wlan0
iface wlan0 inet dhcp
as given on the first page of this thread.

I tried adding them with the settings as instructed on the first page, but that makes my wiress unusable.

What can I do?

Thanks,
RVGSD

[rvgsd]

Hi all,

I have WPA2 with DHCP, and my '/etc/network/interfaces' file looks like this:



auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid MYESSID
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk MY_HEX_KEY


so when I run 'sudo /etc/init.d/networking restart'
here's what I get:



* Reconfiguring network interfaces... There is already a pid file /var/run/dhclient.wlan0.pid with pid 4764
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:90:4b:2d:e7:e2
Sending on LPF/wlan0/00:90:4b:2d:e7:e2
Sending on Socket/fallback
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:90:4b:2d:e7:e2
Sending on LPF/wlan0/00:90:4b:2d:e7:e2
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 21
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
No DHCPOFFERS received.
No working leases in persistent database - sleeping.


What could be wrong? Any suggestions?
Thanks for helping out!

Regards,
RVGSD.

[amainejr]

Try doing the


sudo ifup -v <your interface>

Not saying that this is a fix, but if you notice in mine, my wpasupplicant failed to start. It's been working using WPA2 and no broadcast up until I upgraded to 9.04 and did the updates after the install. Nothing else changed, so I think it may be a wpa_supplicant problem. I just don't know how to find out further or fix it. If it's the same on yours, then there may be a bug.

[rvgsd]

Nopes..that does not work. I wonder if this issue can be fixed or not!

[wieman01]

The only thing I've noticed, is that the wpa_supplicant failed to start. Any tips on that? Sorry about the format. I had to type it all out by hand.
You don't have to type it out by hand, you could copy and paste the stuff by highlighting the output with your mouse and then pressing the scroll-wheel to paste the stuff.

The only thing I can offer right now is to enable SSID broadcast and reinstall wpa-supplicant. Could you try? Don't forget to adjust the script.

[wieman01]

Hi all,

I have WPA2 with DHCP, and my '/etc/network/interfaces' file looks like this:

...

What could be wrong? Any suggestions?
Thanks for helping out!

Regards,
RVGSD.
It looks to me that this is a hardware issue. Your adapter has not been recognized. Please also post:

sudo iwlist scan

[rvgsd]

Here's the output of 'sudo iwlist scan':



lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wmaster0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:1F:33:46:C8:80
ESSID:"NETGEAR"
Mode:Master
Channel:1
Frequency:2.412 GHz (Channel 1)
Quality=58/100 Signal level:-73 dBm Noise level=-55 dBm
Encryption key:on
IE: Unknown: 00074E455447454152
IE: Unknown: 010882848B962430486C
IE: Unknown: 030101
IE: Unknown: 2A0100
IE: Unknown: 2F0100
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
IE: Unknown: 32040C121860
IE: Unknown: DD090010180200F0000000
IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F 00
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:tsf=0000000d62a2db09
Extra: Last beacon: 1484ms ago
Cell 02 - Address: 00:18:3A:AF:2D:B2
ESSID:"NITTIANS@TAMU"
Mode:Master
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=58/100 Signal level:-73 dBm Noise level=-55 dBm
Encryption key:on
IE: Unknown: 000D4E49545449414E534054414D55
IE: Unknown: 010882848B962430486C
IE: Unknown: 030106
IE: Unknown: 2A0104
IE: Unknown: 2F0104
IE: Unknown: 32040C121860
IE: Unknown: DD090010180203F0000000
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:tsf=0000014e9a0b5170
Extra: Last beacon: 1140ms ago
Cell 03 - Address: 00:18:3A:D6:EF:54
ESSID:""
Mode:Master
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=68/100 Signal level:-63 dBm Noise level=-55 dBm
Encryption key:off
IE: Unknown: 000C000000000000000000000000
IE: Unknown: 010882848B962430486C
IE: Unknown: 030106
IE: Unknown: 050401030000
IE: Unknown: 2A0100
IE: Unknown: 2F0100
IE: Unknown: 32040C121860
IE: Unknown: DD090010180200F0000000
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:tsf=0000002496f4a184
Extra: Last beacon: 920ms ago
Cell 04 - Address: 00:1C:10:46:00:30
ESSID:"Horizon"
Mode:Master
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=58/100 Signal level:-73 dBm Noise level=-55 dBm
Encryption key:on
IE: Unknown: 0007486F72697A6F6E
IE: Unknown: 010882848B962430486C
IE: Unknown: 030106
IE: Unknown: 2A0104
IE: Unknown: 2F0104
IE: Unknown: 32040C121860
IE: Unknown: DD09001018020014000000
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:tsf=000000af472b43d7
Extra: Last beacon: 1144ms ago
Cell 05 - Address: 00:14:D1:30:BF:14
ESSID:"carmen"
Mode:Master
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=51/100 Signal level:-79 dBm Noise level=-55 dBm
Encryption key:on
IE: Unknown: 00066361726D656E
IE: Unknown: 010882848B960C183048
IE: Unknown: 030106
IE: Unknown: DD0600032F010001
IE: Unknown: 2A0104
IE: Unknown: 32041224606C
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=00000229011f5181
Extra: Last beacon: 1164ms ago
Cell 06 - Address: 00:12:0E:8A:B1:CE
ESSID:"07FX09079070"
Mode:Master
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=53/100 Signal level:-77 dBm Noise level=-55 dBm
Encryption key:on
IE: Unknown: 000C303746583039303739303730
IE: Unknown: 010482848B96
IE: Unknown: 030106
IE: Unknown: 2A0104
IE: Unknown: 32080C1218243048606C
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=00000000fc17f238
Extra: Last beacon: 1292ms ago
Cell 07 - Address: 00:1C:DF:3F:24:09
ESSID:"MYNETWORK"
Mode:Master
Channel:11
Frequency:2.462 GHz (Channel 11)
Quality=83/100 Signal level:-49 dBm Noise level=-55 dBm
Encryption key:on
IE: Unknown: 00124C6F7374496E476F6C664279506C75733131
IE: Unknown: 010882848B960C183048
IE: Unknown: 03010B
IE: Unknown: 0706555320010B1B
IE: Unknown: 2A0102
IE: Unknown: 32041224606C
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
Preauthentication Supported
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=0000000ea24d2181
Extra: Last beacon: 32ms ago


One more thing, I was able to connect when I had the 8.04 and 8.10 version. (the 8.10 version like the 9.04 had autmoatically detected and installed frpm b43=fwcutter.)
It would be great if I could connect!!
Thanks for help.

[juje]

ok, my wifi connection on jaunty it's pretty buggie too...i can only connect thru nm, only wpa, no mac address filter allowed and the transfer rate become slower and slower every second, until i have to restart my pc (half an hour or so, maybe an hour).
My wpa2 connection had been working pretty straight (thanks weiman01!) since feisty.
Now, i can't barely open my "/etc/network/interfaces" config file...anything i do there it shut down the wifi connection...

This is my "iwlist scan":



lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wmaster0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: ***************
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=54/70 Signal level=-56 dBm
Encryption key:on
ESSID:"***************"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s
Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
Mode:Master
Extra:tsf=0000000094a2538e
Extra: Last beacon: 368ms ago
IE: Unknown: 0012582540324232355F356E75774B3331257154
IE: Unknown: 010882848B962430486C
IE: Unknown: 030106
IE: Unknown: 2A0104
IE: Unknown: 2F0104
IE: Unknown: 32040C121860
IE: Unknown: DD090010180200F4000000
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK


and here is my "lshw -C network"



*-network
description: Ethernet interface
product: RTL8111/8168B PCI Express Gigabit Ethernet controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:02:00.0
logical name: eth0
version: 01
serial: 00:18:f3:f3:ea:78
width: 64 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=r8169 driverversion=2.3LK-NAPI latency=0 module=r8169 multicast=yes
*-network
description: Wireless interface
product: RT2561/RT61 rev B 802.11g
vendor: RaLink
physical id: 0
bus info: pci@0000:01:00.0
logical name: wmaster0
version: 00
serial: **************
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=rt61pci ip=192.168.1.100 latency=64 module=rt61pci multicast=yes wireless=IEEE 802.11bg


any clue how to make this workout?
thanks in advance!

Pd. sorry for my lousy english!

[wieman01]

rvgsd & juje,

There is a problem with your hardware. The scan results look odd. No idea what this is about, but you'd better open new threads in the wireless section and ask others to jump in. Never seen this before.

[amainejr]

Weiman, I didn't fully explain I guess. I'm on a windows pc, and as I execute the commands on my ubuntu box (laptop), i'm hand typing them into the windows pc to post. The ubuntu box is failing to get on the internet for wpa1 and wpa2. I tried it with commenting out everything wpa related in the interfaces file and changing my router to use dhcp. I can connect with WEP or no security, but anything that uses the wpa_supplicant utility won't authorize to get on the net. My router's wireless light goes crazy whenever I `sudo /etc/init.d/networking restart` or reboot the box, but it just won't connect.

[juje]

Thanks wieman01, i'll start a new threat...

[VladCE]

I am completely new to Ubuntu and love it, so please be nice to my first posting here...

OK, I don't know what I did but about a week ago my Network Manager (applet) stopped discovering wireless networks. I still can connect to previously discovered networks, but can't see any others. I use Ubuntu 9.04 with all the latest updates.

Now, if I run

iwlist scan

...it says "Interface doesn't support scanning" on all interfaces.

If I do

sudo iwlist scan

... then it does discover all wireless networks.

The question is how do I make it discover thru the nm-applet, at boottime?

P. S. Another question, maybe - is it possible somehow to roll back to older versions (of nm-applet, namely) without reinstalling the whole OS?

Please help and thanks in advance,

[wieman01]

Kevdog, could you take over for a minute? I don't have time to respond today... Sorry, guys.

[VladCE]

Kevdog, could you take over for a minute?

Looks like not

[Gert-Jan]

Just a small addition to this great HowTo: In Jaunty the wpasupplicant is installed by default. :)

[wieman01]

I am completely new to Ubuntu and love it, so please be nice to my first posting here...

OK, I don't know what I did but about a week ago my Network Manager (applet) stopped discovering wireless networks. I still can connect to previously discovered networks, but can't see any others. I use Ubuntu 9.04 with all the latest updates.

Now, if I run

iwlist scan

...it says "Interface doesn't support scanning" on all interfaces.

If I do

sudo iwlist scan

... then it does discover all wireless networks.

The question is how do I make it discover thru the nm-applet, at boottime?

P. S. Another question, maybe - is it possible somehow to roll back to older versions (of nm-applet, namely) without reinstalling the whole OS?

Please help and thanks in advance,
Sorry for my late replying.

Yes, sometimes you have to add "sudo" and I have corrected the tutorial accordingly. Thanks.

I am pretty sure that NM cannot connect to networks at boot time. That is why I never used it. You could install a previous version but what's value of it?

[wieman01]

Just a small addition to this great HowTo: In Jaunty the wpasupplicant is installed by default. :)
Thanks for highlighting that. I have added a note in my tutorial. Good point.

[VladCE]

I am pretty sure that NM cannot connect to networks at boot time. That is why I never used it. You could install a previous version but what's value of it?

But it did (and does). I mean it used to discover all networks and now connects to the previously discovered networks at boot time. I don't know what's changed and whether it's a bug or a new feature of a new version. How do I roll it back?
Did you really never used NM, the default Ubuntu wireless app?!

[Gert-Jan]

[quote=VladCE;7242012]But it did (and does). I mean it used to discover all networks and now connects to the previously discovered networks at boot time.

I can confirm that (at least for Jaunty).

[VladCE]

[quote]

I can confirm that (at least for Jaunty).

Do you have the same problem as I do (see above)?

[wieman01]

But it did (and does). I mean it used to discover all networks and now connects to the previously discovered networks at boot time. I don't know what's changed and whether it's a bug or a new feature of a new version. How do I roll it back?
Did you really never used NM, the default Ubuntu wireless app?!
Alright, I stand corrected. :-)

No, I never really used it. I tried on a few occasions, but I don't like NM much.

[Gert-Jan]

[quote=Gert-Jan;7243889]

Do you have the same problem as I do (see above)?

No, I don't.

[silverhorse]

I tried your --Sample configuration WPA1 & DHCP, ESSID broadcast enabled -- without success.

It may be that I'm using that pesky 4318 Broadcom card.

It took me forever to install the driver for that card, now I can wireless connect, but can't WPA.

See the attachment to read my configuration

Thank you for the time

[VladCE]

[QUOTE]

No, I don't.

Looks like I won't get help here then. Probably complete Ubuntu reinstall is coming...

[VladCE]

[QUOTE=Gert-Jan;7246385]
Looks like I won't get help here then.

Now I can see how exactly "Ubuntu is 'humanity towards others'. It is 'the belief in a universal bond of sharing that connects all humanity'."

Probably I have to get back to the XP concept of "universal bond of sharing that connects".

[Gert-Jan]

Now I can see how exactly "Ubuntu is 'humanity towards others'. It is 'the belief in a universal bond of sharing that connects all humanity'."

Probably I have to get back to the XP concept of "universal bond of sharing that connects".

I'm sorry you can't find any help. Unfortunately I'm an Ubuntu-n00b as well and not that big a computer expert :(
However, it seems to me that it's not always possible to get Ubuntu working with a wireless connection...

[wieman01]

[QUOTE=VladCE;7247503]

Now I can see how exactly "Ubuntu is 'humanity towards others'. It is 'the belief in a universal bond of sharing that connects all humanity'."

Probably I have to get back to the XP concept of "universal bond of sharing that connects".
Somtimes that's reality.

[VladCE]

[QUOTE=VladCE;7266468]
Somtimes that's reality.

Gee, what a buggy soft... I thought after all these years Linux could have been more mature.

Anyway, as far as I understand, NM and wicd are just GUI interfaces to some real command-line, flat file settings. Is there any way I can get rid of them and do it (discover and connect) manually?

[wieman01]

Gee, what a buggy soft... I thought after all these years Linux could have been more mature.

Anyway, as far as I understand, NM and wicd are just GUI interfaces to some real command-line, flat file settings. Is there any way I can get rid of them and do it (discover and connect) manually?
You won't believe it, but yes, just follow this tutorial...

Alternatively, try Kevdog's tutorial. It's definitely worth a try and my preferred solution at the moment:

http://ubuntuforums.org/showthread.php?t=571188

[VladCE]

You won't believe it, but yes, just follow this tutorial...

Alternatively, try Kevdog's tutorial. It's definitely worth a try and my preferred solution at the moment:

http://ubuntuforums.org/showthread.php?t=571188

Thank you, you are very helpful.
BTW, sorry for the noob question, but it's hard to browse through 170+ pages: what's wrong with WEP? All my neighbourgs seem to use it.

[wieman01]

Thank you, you are very helpful.
BTW, sorry for the noob question, but it's hard to browse through 170+ pages: what's wrong with WEP? All my neighbourgs seem to use it.
Good point. My recommendation is that you don't use WEP at all as it is highly insecure. An experienced user can crack WEP in a matter of minutes (I have written a tutorial on it for educational purposes).

WPA or WPA2 is the way to go. WEP is highly flawed and should not be use any longer.

[VladCE]

Good point. My recommendation is that you don't use WEP at all as it is highly insecure. An experienced user can crack WEP in a matter of minutes (I have written a tutorial on it for educational purposes).

WPA or WPA2 is the way to go. WEP is highly flawed and should not be use any longer.

Hmm, sounds like fun to try, can I see the tutorial? How bad is the possible exposure? Can someone get to my Windows shares, for example, or is it just traffic snooping?

[wieman01]

Hmm, sounds like fun to try, can I see the tutorial? How bad is the possible exposure? Can someone get to my Windows shares, for example, or is it just traffic snooping?
It's a lot of fun. To test your own network's security, give it a go:

http://ubuntuforums.org/showthread.php?t=528276

Yes, somebody could also get access to your shares... or anything else that isn't password protected. It's not very likely but it's a risk one can easily avoid.

[Fischer]

weiman01,

I posted on kevdog's thread as well but i really need to get this fixed ASAP so I will ask you as well. (kevdog also hinted that he isnt very familiar with Ra and intel chipsets...which I am so luckily blessed with):

I have been trying to get your tutorial to work for the past few hours and I can make it work if I take the encryption off my network. Since that is not the most desirable way to communicate with my router, I've been trying to get my wireless card to connect via WPA-Personal encryption.

Im using a Ra-based chipset (I think)

when I type:

sudo iwpriv wlan0 set AuthMode=WPA-PSK

which returns: "Invalid command: set"
this happens with all the iwpriv commands.

please assist. this is for my little brothers computer and I am leaving on sunday ( i dont think they will be able to get it running without me)

also my network manager doesnt appear to work. when I connected to the unencrypted network, it didn't reflect it on the top right corner of the screen. it still had the red x.

Thanks

[wieman01]

Fischer,

You need to provide some more information please. Please post every output that you get when following section "Post this if you are stumped" in the original post.

We'll get you hooked up til Sunday.

[geezerone]

I had problems with ralink wireless adaptor too and Network Manager didn't work correctly so manually configured the network interfaces file.

Like Wieman01 says, plenty of info if you please.

[Fischer]

Thanks for the response, I fixed it last night. I just had to change the specified driver in the network-config application. it worked with the generic linux driver "wext".

[wieman01]

Thanks for the response, I fixed it last night. I just had to change the specified driver in the network-config application. it worked with the generic linux driver "wext".
Yes, Ralink work with "wext" nowadays. Glad you got it fixed.

[leetone]

Hello guys,

how to configure it for this:

Authentication: WPA
Data encryption : TKIP
EAP type: PEAP
auth method: EAP-MSCHAPV2

[snowcraig]

Sony PCG-V505BX (WPA not listed)
Does anyone else here have this laptop? I have Ubuntu installed, but cannot connect to my home wireless network when I have it set to WPA security. It successfully detects the network, but when I try to connect it doesn't list WPA as an option. I can plug in my USB WIFI stick and then connect to WPA, but not with the internal hardware in my laptop. I can also switch the network to WEP and connect with the interal wireless card alone, but I don't really want to do that. Does anyone here have a suggestion for me?


I believe this is the actual wireless hardware that comes with the computer:

LAN Express AS-IEEE 802.11 miniPCI Adapter



Here is what I came up with from Ubuntu:


*-network:0
description: Wireless interface
product: Prism 2.5 Wavelan chipset
vendor: Intersil Corporation
physical id: 2
bus info: pci@0000:02:02.0
logical name: eth1
version: 01
serial: 00:02:8a:94:be:87
width: 32 bits
clock: 33MHz
capabilities: cap_list ethernet physical wireless
configuration: broadcast=yes driver=orinoco driverversion=0.15 firmware=Intersil 1.5.6 latency=64 module=orinoco_pci multicast=yes wireless=IEEE 802.11b
*-network:1
description: Ethernet interface
product: 82801CAM (ICH3) PRO/100 VE (LOM) Ethernet Controller
vendor: Intel Corporation
physical id: 8
bus info: pci@0000:02:08.0
logical name: eth0
version: 42
serial: 08:00:46:ad:1d:0b
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=e100 driverversion=3.5.23-k6-NAPI firmware=N/A latency=66 maxlatency=56 mingnt=8 module=e100 multicast=yes
*-network:0
description: Wireless interface
physical id: 2
logical name: wlan0
serial: 00:1c:df:78:1f:87
capabilities: ethernet physical wireless
configuration: broadcast=yes ip=192.168.2.3 multicast=yes wireless=IEEE 802.11bg
*-network:1 DISABLED
description: Ethernet interface
physical id: 3
logical name: pan0
serial: 9a:a0:51:05:54:4e
capabilities: ethernet physical
configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A multicast=yes


Thanks

[wieman01]

Please post every output that results from running the stuff that's posted under section "Post this if you are stumped". We'll go from there.

[snowcraig]

Please post every output that results from running the stuff that's posted under section "Post this if you are stumped". We'll go from there.


Here is what I came up with up to the last two items:


craig@craig-laptop:~$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 * 255.255.255.0 U 2 0 0 wlan0
link-local * 255.255.0.0 U 1000 0 0 wlan0
default 192.168.2.1 0.0.0.0 UG 0 0 0 wlan0
craig@craig-laptop:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

eth1 IEEE 802.11b ESSID:"2WIRE684" Nickname:"Prism I"
Mode:Managed Frequency:2.422 GHz Access Point: 00:1B:5B:65:43:51
Bit Rate:11 Mb/s Sensitivity:1/3
Retry short limit:8 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=24/92 Signal level=-87 dBm Noise level=-141 dBm
Rx invalid nwid:0 Rx invalid crypt:212 Rx invalid frag:0
Tx excessive retries:1 Invalid misc:0 Missed beacon:0

wmaster0 no wireless extensions.

wlan0 IEEE 802.11bg ESSID:"Frank"
Mode:Managed Frequency:2.437 GHz Access Point: 00:1C:DF:DA:F2:D1
Bit Rate=1 Mb/s Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Power Management:off
Link Quality=94/100 Signal level:27/100
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

pan0 no wireless extensions.

craig@craig-laptop:~$ sudo iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:21:29:9F:30:EA
ESSID:"lohe56-j"
Mode:Master
Channel:6
Frequency:2.437 GHz (Channel 6)
Signal level:45 dBm Noise level:16 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:capab=0x0411
Extra: Last beacon: 12ms ago
Cell 02 - Address: 00:1C:DF:DA:F2:D1
ESSID:"Frank"
Mode:Master
Channel:6
Frequency:2.437 GHz (Channel 6)
Signal level:48 dBm Noise level:16 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 9 Mb/s
18 Mb/s; 36 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:capab=0x0411
Extra: Last beacon: 12ms ago
Cell 03 - Address: 00:22:75:27:63:ED
ESSID:"Tardiff"
Mode:Master
Channel:6
Frequency:2.437 GHz (Channel 6)
Signal level:20 dBm Noise level:16 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 9 Mb/s
18 Mb/s; 36 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:capab=0x0411
Extra: Last beacon: 12ms ago
Cell 04 - Address: 00:1B:5B:65:43:51
ESSID:"2WIRE684"
Mode:Master
Channel:3
Frequency:2.422 GHz (Channel 3)
Signal level:28 dBm Noise level:16 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Extra:bcn_int=100
Extra:capab=0x0011
Extra: Last beacon: 12ms ago
Cell 05 - Address: 00:16:B6:02:6E:52
ESSID:"chipsnet"
Mode:Master
Channel:7
Frequency:2.442 GHz (Channel 7)
Signal level:22 dBm Noise level:16 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:capab=0x0411
Extra: Last beacon: 12ms ago

wmaster0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:21:1E:54:C9:90
ESSID:"Skynet"
Mode:Master
Channel:1
Frequency:2.412 GHz (Channel 1)
Quality=94/100 Signal level:28/100
Encryption key:on
IE: Unknown: 0006536B796E6574
IE: Unknown: 010582848B962C
IE: Unknown: 030101
IE: Unknown: 2A0104
IE: Unknown: 32080C1218243048606C
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:tsf=000000b807ffe1bf
Extra: Last beacon: 676ms ago
Cell 02 - Address: 00:1B:5B:65:43:51
ESSID:"2WIRE684"
Mode:Master
Channel:3
Frequency:2.422 GHz (Channel 3)
Quality=17/100 Signal level:9/100
Encryption key:on
IE: Unknown: 00083257495245363834
IE: Unknown: 010882848B0C12961824
IE: Unknown: 030103
IE: Unknown: 0706555320010B1B
IE: Unknown: 2A0107
IE: Unknown: 32043048606C
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=0000000e74ed4675
Extra: Last beacon: 564ms ago
Cell 03 - Address: 00:21:29:9F:30:EA
ESSID:"lohe56-j"
Mode:Master
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=5/100 Signal level:32/100
Encryption key:on
IE: Unknown: 00086C6F686535362D6A
IE: Unknown: 010882848B962430486C
IE: Unknown: 030106
IE: Unknown: 2A0104
IE: Unknown: 2F0104
IE: Unknown: 32040C121860
IE: Unknown: DD09001018020015000000
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:tsf=0000007496162e6f
Extra: Last beacon: 312ms ago
Cell 04 - Address: 00:1C:DF:DA:F2:D1
ESSID:"Frank"
Mode:Master
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=100/100 Signal level:28/100
Encryption key:on
IE: Unknown: 00054672616E6B
IE: Unknown: 010882840B161224486C
IE: Unknown: 030106
IE: Unknown: 2A0104
IE: Unknown: 32040C183060
IE: Unknown: 2D1AEE110FFFFF0000010000000000000000000000000C0000 000000
IE: Unknown: 3D1606070700000000000000000000000000000000000000
IE: Unknown: 3E0100
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
IE: Unknown: DD180050F2020101000003A4000027A4000042435E0062322F 00
IE: Unknown: 7F0101
IE: Unknown: DD07000C4304000000
IE: Unknown: DD1E00904C33EE110FFFFF0000010000000000000000000000 000C0000000000
IE: Unknown: DD1A00904C3406070700000000000000000000000000000000 000000
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 9 Mb/s
18 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 12 Mb/s
24 Mb/s; 48 Mb/s
Extra:tsf=0000000caaf0abab
Extra: Last beacon: 388ms ago

pan0 Interface doesn't support scanning.

craig@craig-laptop:~$ sudo lshw -C network
*-network:0
description: Wireless interface
product: Prism 2.5 Wavelan chipset
vendor: Intersil Corporation
physical id: 2
bus info: pci@0000:02:02.0
logical name: eth1
version: 01
serial: 00:02:8a:94:be:87
width: 32 bits
clock: 33MHz
capabilities: pm cap_list ethernet physical wireless
configuration: broadcast=yes driver=orinoco driverversion=0.15 firmware=Intersil 1.5.6 latency=64 link=yes module=orinoco_pci multicast=yes wireless=IEEE 802.11b
*-network:1
description: Ethernet interface
product: 82801CAM (ICH3) PRO/100 VE (LOM) Ethernet Controller
vendor: Intel Corporation
physical id: 8
bus info: pci@0000:02:08.0
logical name: eth0
version: 42
serial: 08:00:46:ad:1d:0b
size: 10MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e100 driverversion=3.5.23-k6-NAPI duplex=half firmware=N/A latency=66 link=no maxlatency=56 mingnt=8 module=e100 multicast=yes port=MII speed=10MB/s
*-network:0
description: Wireless interface
physical id: 1
logical name: wlan0
serial: 00:1c:df:78:1f:87
capabilities: ethernet physical wireless


Thanks for your help

[kevdog]

Where do I get my network interface from?



Its wlan0 -- thats your wireless interface

*-network:0
description: Wireless interface
physical id: 1
logical name: wlan0
serial: 00:1c:df:78:1f:87
capabilities: ethernet physical wireless
configuration: broadcast=yes ip=192.168.2.3 multicast=yes wireless=IEEE 802.11bg

[snowcraig]

Ok, I will edit my original post then with the updated info. Just in case there is some confusion, I am currently using a USB stick to connect to the internet, but I have the internal wireless card turned on as well.

[wieman01]

snowcraig,

There is a problem with your wireless device, it does not seem to support WPA. Could you do some googling on the topic and check it out? You might not be the only one having this issue.

[snowcraig]

It did support WPA when I had XP installed on the computer. It doesn't appear that the driver Ubuntu comes with for the device supports WPA however. Is there a way around that?

[wieman01]

It did support WPA when I had XP installed on the computer. It doesn't appear that the driver Ubuntu comes with for the device supports WPA however. Is there a way around that?
Yes, using "ndiswrapper" could solve the problem.

I wrote a tutorial on Ralink drivers and the use of ndiswrapper once, it might still do the job:

http://ubuntuforums.org/showthread.php?t=563547

If not, search for ndiswrapper. I believe it's the way to go in your case.

[snowcraig]

I have tried WPA supplicant, no luck there. I want to try ndiswrapper, but all I can find for the driver are windows installers, and I can't seem to find a way to get the actual driver files out of them. Anyone have any suggestions?

[geezerone]

I had problems with a Edimx 7318UG (I think) until it went faulty. In the end I configured the network interfaces file manually. Obtained driver from this (http://linuxwireless.org/en/users/Drivers) site.

In case you haven't looked already you could look at the list here (http://lmgtfy.com/?q=linux+wireless+drivers) too?

Good luck!

[wieman01]

I have tried WPA supplicant, no luck there. I want to try ndiswrapper, but all I can find for the driver are windows installers, and I can't seem to find a way to get the actual driver files out of them. Anyone have any suggestions?
Occasionally these exe. files are ZIP archives which you can then open with your favorite zip tool and extract the files.

Can you try?

[upa]

It worked for me. I used the configuratioon WPA1 -TKIP-DHCP-Broadcast.

Linksys WRT54G
Kubuntu 9.04.

regards

[alleycatuk]

Hi! Great tutorial. I'm completely new to ubuntu and thanks to your post I've managed to connect to my router and access the internet using ndiswrapper and WPA2 AES. I can't get it to work on boot though and even manually, dhcp doesn't always find an ip address straight away - it takes a lot of tries.

ndiswrapper starts up fine and there's a wpa_supplicant process running after boot but I'm not sure if it starts ok - I don't know how to find out.

The odd thing is that if I run wpa_supplicant from terminal (without the -B), it seems to connect to the router and negotiate the keys fine because it says "WPA: Key negotiation completed with <router's MAC>". Though this runs ok, it takes a few attempts to get an ip address assigned by dhcp every time I start the computer. I seem to have to keep on doing:

sudo pkill wpa_supplicant
sudo ifconfig wlan0 down
sudo wpa_supplicant -iwlan0 -Dwext -c/etc/wpa_supplciant.confthen in another terminal window:


sudo ifconfig wlan0 up
sudo dhclient wlan0
and if it still doesn't get an address, do it all over again until it does. Sometimes closing one terminal window and opening another, then running wpa_supplican't in the new window seems to do the trick (coincidence?). If I stop the process (Ctrl-C), it will again take a few goes to get an ip address again.

wpa_supplicant can see the router because it says "WPA: Key negotiation completed with <router's MAC>". It then keeps renegotiating every once in a while, always saying completed. What's odd is that I can't ping the router's ip address (it either shows "Network is unreachable" or keeps pinging without finding it). I can only ping once dhclient has found an address.

The set-up must be ok in some respect as eventually it will get an ip address and I can access the internet so this suggests that ndiswrapper, wpa_supplicant etc are configured ok (doesn't it?)... the problem is that it can take between 1 and a lot of tries to get an ip address... I just have to keep trying. My goal is to get it to work all the time on boot.

If I do a
sudo /etc/init.d/networking restart I get "etc/network/if-pre-up.d/wpasupplicant exited with return code 1" but though lots of posts mention this error, I couldn't see an answer of what caused it. One post said ndiswrapper but ndiswrapper -l shows it's ok and the connection does occasionally work.

I'd be really grateful if you could point me in the right direction - I've spent 10 days trying different things from different forums but as yet none have worked and, being new to linux, I don't know what to do next or even where to look! It feels like I've overcome the biggest hurdles so far in getting a connection that works with WPA2 some times and there's just something missing that's the final piece of the puzzle.

I found something that said I need a route to the gateway so I tried a
sudo route add default gw 192.168.1.1 wlan0 to add the gateway but it came up with "SIOCADDRT: No such process". I did try change /etc/network/interfaces to a static ip address but have never got that to connect.

I posted a question on the forum but no one replied. Can anyone here offer any advice? Thanks in advance.

For info, I'm using Ubuntu 9.04 (dual boot setup with XP) with a linksys WMP54GS pci card (shows as Broadcom Airforce One 54g in lspci), ndiswrapper and have blacklisted b43 drivers. I've also killed the network manager process as that seemed to interfere (one post said to kill it) and just said "no wireless" even though iwlist wlan0 scan sees the router/AP.

[urban_ryoga]

I have a question about this. I currently automatically reconnect to my WPA2 access point, but now from the UI it says for Wireless Networks "device not managed". How will I be able to access other wi-fi points in the future?

[wieman01]

I have a question about this. I currently automatically reconnect to my WPA2 access point, but now from the UI it says for Wireless Networks "device not managed". How will I be able to access other wi-fi points in the future?
If you own a mobile device, I don't encourage you to use this method. Network Manager or other networking tools will be an advantage.

[mdhoerr]

I can scan and see my network from my Dell Dimension running Ubuntu 8.10, but I can't connect to it using WPA. Until recently, I connected this to my router directly via Ethernet cable, but now I have to use wireless because I had to move the modem and router to another room.

My setup includes a DSL modem, a US Robotics Wireless MAXg Router (USR5461)hoerr, an Acer Windows Vista, a Dell laptop Windows XP, and a eeePC 701 Xandros/KDE, all of which connect using wireless WPA with no problem (but not using the D-Link).

I followed your instructions, and the results were that I could no longer see my network when I ran sudo iwlist scan.

Thanks for your help!

Here's all my info before I went through your instructions.


Machine Brand and Model
Dell Dimension 8200 tower PC
Wireless Brand, Model and Wireless Chipset
D-Link DWL-122 802.11b, prism2 chipset
lspci
02:0a.0 Ethernet controller: D-Link System Inc RTL8139 Ethernet (rev 10)
lsusb
Bus 002 Device 002: ID 2001:3700 D-Link Corp. [hex] DWL-122 802.11b
ifconfig
wlan0 Link encap:Ethernet HWaddr 00:0d:88:66:e3:6f
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wlan0:avahi Link encap:Ethernet HWaddr 00:0d:88:66:e3:6f
inet addr:169.254.8.7 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
iwconfig
wlan0 IEEE 802.11-DS ESSID:off/any
Mode:Auto Frequency:2.422 GHz Access Point: Not-Associated
Bit Rate:2 Mb/s Tx-Power:18 dBm
Retry short limit:8 RTS thr:off Fragment thr:off
Encryption key:off
Link Quality=0/100 Signal level=0 dBm Noise level=0 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
lsmod
Module Size Used by
====== ==== =======
prism2_usb 80260 0
p80211 38536 1 prism2_usb
8139too 31616 0
mii 13440 1 8139too
uhci_hcd 30736 0
libata 177312 3 ata_piix,ata_generic,pata_acpi
usbcore 148848 3 prism2_usb,uhci_hcd
scsi_mod 155212 4 sr_mod,sd_mod,sg,libata
dmesg
[ 2.428476] Magic number: 5:594:350
[ 4.111349] hub 1-0:1.0: USB hub found
[ 4.111371] hub 1-0:1.0: 2 ports detected
[ 4.121177] 8139too Fast Ethernet driver 0.9.28
[ 4.213095] hub 2-0:1.0: USB hub found
[ 4.213115] hub 2-0:1.0: 2 ports detected
[ 4.420653] pata_acpi 0000:00:1f.1: setting latency timer to 64
[ 4.420816] 8139too 0000:02:0a.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
[ 4.421756] eth0: RealTek RTL8139 at 0xe400, 00:0d:88:3d:86:22, IRQ 19
[ 4.421761] eth0: Identified 8139 chip type 'RTL-8100B/8139D'
[ 4.536111] usb 2-2: new full speed USB device using uhci_hcd and address 2
[ 4.600608] ata1.00: ATA-5: ST340016A, 3.10, max UDMA/100
[ 4.600615] ata1.00: 78165360 sectors, multi 8: LBA
[ 4.608517] ata1.00: configured for UDMA/100
[ 4.700041] usb 2-2: configuration #1 chosen from 1 choice
[ 18.519870] prism2usb_init: prism2_usb.o: 0.2.9 Loaded
[ 18.519876] prism2usb_init: dev_info is: prism2_usb
[ 20.829232] Prism2 card SN: 000000000000
[ 20.833307] usbcore: registered new interface driver prism2_usb
[ 102.419074] warning: `avahi-daemon' uses 32-bit capabilities (legacy support in use)
[ 205.454646] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 205.455182] ADDRCONF(NETDEV_UP): wlan0: link is not ready

sudo lshw -C network
*-network
description: Ethernet interface
produmary@mary-dell:~$ sudo /etc/init.d/networking restart
* Reconfiguring network interfaces... There is already a pid file /var/run/dhclient.wlan0.pid with pid 3915
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:0d:88:66:e3:6f
Sending on LPF/wlan0/00:0d:88:66:e3:6f
Sending on Socket/fallback
grep: /etc/resolv.conf: No such file or directory
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:0d:88:66:e3:6f
Sending on LPF/wlan0/00:0d:88:66:e3:6f
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
grep: /etc/resolv.conf: No such file or directory
ct: RTL8139 Ethernet
vendor: D-Link System Inc
physical id: a
bus info: pci@0000:02:0a.0
logical name: eth0
version: 10
serial: 00:0d:88:3d:86:22
size: 10MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=8139too driverversion=0.9.28 duplex=half latency=64 link=no maxlatency=64 mingnt=32 module=8139too multicast=yes port=MII speed=10MB/s
*-network:0 DISABLED
description: Ethernet interface
physical id: 1
logical name: pan0
serial: 6e:d0:31:62:51:d8
capabilities: ethernet physical
configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A link=yes multicast=yes
*-network:1
description: Wireless interface
physical id: 2
logical name: wlan0
serial: 00:0d:88:66:e3:6f
capabilities: ethernet physical wireless
configuration: broadcast=yes multicast=yes wireless=IEEE 802.11-DS
sudo iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:14:C1:33:90:C0
ESSID:"hoerrs"
Mode:Master
Encryption key:on
Channel:11
Quality:45/100 Signal level:-72 dBm Noise level:-90 dBm

pan0 Interface doesn't support scanning.

lsb_release -d
Description: Ubuntu 8.10
uname -mr
2.6.27-7-generic i686

sudo /etc/init.d/networking restart
* Reconfiguring network interfaces...
There is already a pid file /var/run/dhclient.wlan0.pid with pid 3915
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:0d:88:66:e3:6f
Sending on LPF/wlan0/00:0d:88:66:e3:6f
Sending on Socket/fallback
grep: /etc/resolv.conf: No such file or directory
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:0d:88:66:e3:6f
Sending on LPF/wlan0/00:0d:88:66:e3:6f
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
grep: /etc/resolv.conf: No such file or directory

[wieman01]

Hello mdhoerr,

I suppose "hoerrs" is your network. So the network is recognized, however, your wireless adapter does not seem to recognize it as a WPA secured one. I believe the driver can't really cope with WPA and might have to be replaced through "ndiswrapper".

Do you know what driver your card is supposed to work with? I would do a little research there.

[mantes]

hi guys ! new to this forum. you are are doing really great job helping out newbies like me. I am also tryin to do WPA setup on my small network of 3 PC's. All the 3 PC's have Ubuntu 9.04 . I use Wicd as my network manager. I am using D-link DWL AG530 PCI cards with Atheros chipset. I have wext as my wpa supplicant driver.

First i'll show my /ect/interfaces file,

auto ath0
iface ath0 inet static
address 192.168.X.X
netmask 255.255.255.0
wpa-driver wext
wpa-ssid <my ssid>
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk ,pass phrase in hex>

now this is my /etc/wpa_supplicant/wpa_supplicat.conf file,

ctrl_interface=var/run/wpa_supplicant
network={
ssid= <my ssid>
scan_ssid=1
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
psk=<hex passphrase key>
}


after running, wpa_suplicant -d -c /etc/wpa_supplicant/wpa_supplicant.conf -iath0 -Dwext

i get a lonnggg error msg ,at the end of the error it shows,

Failed to add interface ath0
State DISCONNECTED > DISCONNECTED
wpa_driver_wext_set_operstate : operstate 0>0 (DORMANT)
WEXT: OPerstate: linkmode=-1, operstate=5
No keys have been configured -skip key clearing
Cancelling scan request
Cancelling authentication timeout
WEXT:OPerstate:linkmode=0, operstate=6

I need to eneable WPA and preferably WPA 2 in all the 3 PC's and make one of the PC as master and rest will be clients. How should i go about this ???? do i need to make any change in interfaces or wpa_supplicant.conf file ???


Please guys any help would b greatly appreciated.

Thanks .

[mantes]

wi(s)eman 01 plzzz help me out here. really important for me to get it working in a short time.

looking forward to any kind of help.


cheers.

[wieman01]

Hello Mantes,

Sorry, but I don't use any chat clients at all.

This could be the right thread for you:

http://ubuntuforums.org/showthread.php?t=571188

Since you use the method outlined in the thread mentioned above, it might find an answer there. If you want to follow my method, let me know and post everything that's mentioned in section "Post this if you are stumped...".

[Xkutzy]

I am having trouble getting WPA to work with an Edimax EW-7318Ug USB wireless device in Ubuntu Hardy. I'm using an old Toshiba laptop with a Toshiba Mini PCI lan card installed. The card is functioning but slow and does not support WPA, hence my trying the EW-7318Ug.

The EW-7318Ug works fine with WEP64. I tried setting up WPA with network manager and by using this how to. In my preferred configuration using DHCP, it does not get an IP address from the router. If I use a fixed IP it won't connect.

I have the internal card switched off on the hardware switch. I have other laptops that connect to the router fine using WPA so I think the router is OK. The EW-7318Ug is reported as working out of the box in Hardy, so I would be grateful if someone could point out what I am doing wrong.

ians@ubuntuToshiba:~$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
link-local * 255.255.0.0 U 0 0 0 wlan0
link-local * 255.255.0.0 U 0 0 0 eth0
default * 0.0.0.0 U 1000 0 0 wlan0

ians@ubuntuToshiba:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

eth1 IEEE 802.11b ESSID:"" Nickname:"HERMES I"
Mode:Managed Frequency:2.457 GHz Access Point: None
Bit Rate:2 Mb/s Sensitivity:1/3
Retry limit:4 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=0/92 Signal level=134/153 Noise level=134/153
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

wmaster0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

ians@ubuntuToshiba:~$ sudo iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 No scan results

wmaster0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:1F:9F:49:D7:71
ESSID:"ThomsonE9A7D8"
Mode:Master
Channel:1
Frequency:2.412 GHz (Channel 1)
Quality=46/100 Signal level=-80 dBm
Encryption key:on
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:tsf=00000003ab73407d
Cell 02 - Address: 00:12:17:38:A8:86
ESSID:""
Mode:Master
Channel:11
Frequency:2.462 GHz (Channel 11)
Quality=49/100 Signal level=-62 dBm
Encryption key:on
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:tsf=00000058629af18b

ians@ubuntuToshiba:~$ sudo lshw -C network
*-network
description: Ethernet interface
product: 82801BA/BAM/CA/CAM Ethernet Controller
vendor: Intel Corporation
physical id: 8
bus info: pci@0000:02:08.0
logical name: eth0
version: 03
serial: 00:00:39:ff:88:81
size: 10MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e100 driverversion=3.5.23-k4-NAPI duplex=half firmware=N/A latency=64 link=no maxlatency=56 mingnt=8 module=e100 multicast=yes port=MII speed=10MB/s
*-network
description: Wireless LAN Card
product: Version 01.01
vendor: TOSHIBA
physical id: 0
slot: Socket 0
resources: irq:11
*-network:0
description: Wireless interface
physical id: 2
logical name: eth1
serial: 00:02:2d:13:3c:86
capabilities: ethernet physical wireless
configuration: broadcast=yes driver=orinoco driverversion=0.15 firmware=Lucent/Agere 6.14 link=no multicast=yes wireless=IEEE 802.11b
*-network:1
description: Wireless interface
physical id: 3
logical name: wlan0
serial: 00:1f:1f:3b:0f:ba
capabilities: ethernet physical wireless
configuration: broadcast=yes multicast=yes wireless=IEEE 802.11g

ians@ubuntuToshiba:~$ sudo cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface

iface eth1 inet dhcp
# wireless-* options are implemented by the wireless-tools package
wireless-mode managed
wireless-key 3XXXXXXXXc
wireless-essid gXXXXXX9

iface eth0 inet dhcp

auto eth0


iface wlan0 inet dhcp
wpa-psk 5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXe
wpa-driver wext
wpa-key-mgmt WPA-PSK
wpa-proto WPA
wpa-ssid gXXXXXX9
wpa-ap-scan 2
wpa-pairwise TKIP
wpa-group TKIP

auto wlan0

ians@ubuntuToshiba:~$ sudo ifdown -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 5771
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:1f:1f:3b:0f:ba
Sending on LPF/wlan0/00:1f:1f:3b:0f:ba
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 192.168.1.1 port 67
ifconfig wlan0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan0.pid
Stopped /sbin/wpa_supplicant (pid 3973).

ians@ubuntuToshiba:~$ sudo ifup -v wlan
Ignoring unknown interface wlan=wlan.
ians@ubuntuToshiba:~$ sudo ifup -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan0
wpa_supplicant: wpa-ap-scan 2 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "gXXXXXX9" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise TKIP -- OK
wpa_supplicant: wpa-group TKIP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto WPA -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:1f:1f:3b:0f:ba
Sending on LPF/wlan0/00:1f:1f:3b:0f:ba
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 20
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/wpasupplicant

P.S. The router I am trying to attach to is identified as cell 2 on the scan.

P.P.S. How do I put the above pasted stuff is a scrollable box?

[daniel.pool]

Hi,

I've recently had to rebuild my machine and I'm unable to get the wireless card working. I've previously had it working using the RT2870 drivers and WPA using the instructions on this and another thread (http://ubuntuforums.org/showthread.php?p=7600077#post7600077) which provides info on how to get the drivers working.

For some reason this time around I just can't get the wireless working properly. As requested by the OP, here are my files for inspection:

Output of route:



Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 ra0
default 192.168.1.254 0.0.0.0 UG 100 0 0 ra0Output of iwconfig:


ra0 Ralink STA ESSID:"[detail removed]" Nickname:"RT2870STA"
Mode:Managed Frequency=2.437 GHz Access Point: 00:22:69:2A:C8:1B
Bit Rate=130 Mb/s
RTS thr:off Fragment thr:off
Encryption key:[Detail removed]
Link Quality=100/100 Signal level:-52 dBm Noise level:-71 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0Output of iwlist:


ra0 Scan completed :
Cell 01 - Address: 00:22:69:2A:C8:1B
Protocol:802.11b/g/n
ESSID:"[detail removed]"
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:96/100 Signal level:-52 dBm Noise level:-92 dBm
Encryption key:on
Bit Rates:130 Mb/s
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSKOutput of lshw -C network


*-network DISABLED
description: Ethernet interface
product: MCP78S [GeForce 8200] Ethernet
vendor: nVidia Corporation
physical id: a
bus info: pci@0000:00:0a.0
logical name: eth0
version: a2
serial: 00:23:54:19:a8:bf
size: 100MB/s
capacity: 1GB/s
width: 32 bits
clock: 66MHz
capabilities: pm msi ht bus_master cap_list ethernet physical mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=forcedeth driverversion=0.61 duplex=full latency=0 link=yes maxlatency=20 mingnt=1 module=forcedeth multicast=yes port=MII speed=100MB/s
*-network
description: Wireless interface
physical id: 1
logical name: ra0
serial: 00:1c:df:d1:a0:c9
capabilities: ethernet physical wireless
configuration: broadcast=yes ip=192.168.1.25 multicast=yes wireless=Ralink STAOutput of /etc/network/interfaces


# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
#auto eth0
#iface eth0 inet dhcp
#iface eth0 inet static
#address 192.168.1.25
#netmask 255.255.255.0
#gateway 192.168.1.254


#wireless configuration
auto ra0
#iface ra0 inet dhcp
iface ra0 inet static
address 192.168.1.25
gateway 192.168.1.254
dns-nameservers 192.168.1.254
netmask 255.255.255.0
wpa-driver wext
wpa-ssid [detail removed]
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk [detail removed]Output of ifdown -v ra0


Configuring interface ra0=ra0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/postfix
run-parts: executing /etc/network/if-down.d/wpasupplicant
route del default gw 192.168.1.254 metric 100 ra0
ifconfig ra0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicantOutput of ifup -v ra0


Configuring interface ra0=ra0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/dhclient3-apparmor
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.ra0.pid -i ra0 -D wext -q -s -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1

ifconfig ra0 192.168.1.25 netmask 255.255.255.0 up
route add default gw 192.168.1.254 metric 100 ra0
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/openssh-server
run-parts: executing /etc/network/if-up.d/postfix
run-parts: executing /etc/network/if-up.d/wpasupplicant
root@HTPC:/home/htpc# ifdown -v ra0
Configuring interface ra0=ra0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/postfix
run-parts: executing /etc/network/if-down.d/wpasupplicant
route del default gw 192.168.1.254 metric 100 ra0 The interface seems to get the static IP given to it and it sees the AP, I thought that it might be a dns problem as it can't resolve anything, but it also doesn't connect via IP addresses. I tried connecting using DHCP and it fails to get a lease, so my guess is that the interface isn't connecting and something in the wpa_supplicant is breaking (confirmed I guess by the wpa_supplicant daemon failing on startup). What is breaking though I don't know, and I'm pretty sure that I have done nothing different since my last working build (which was a few days ago).

Oh, just thought I should add that I've tried various combinations of WPA/RSN and CCMP/TKIP with the interfaces config. The AP seems to support WPA 1 & 2 and CCMP and TKIP on the pairwise. The current config is what was previously working.

Thanks in advance for any help
~Dan

[wieman01]

Hi daniel.pool,

Two things... What happens when you ping your router after trying to connect?

Second, can you connect when all security is turned off? And what about WEP security, does that work?

wieman01

[daniel.pool]

Wieman,

Thanks for your response.


What happens when you ping your router after trying to connect?

I get Destination unreachable


Second, can you connect when all security is turned off? And what about WEP security, does that work?

I tried setting up an open network and interestingly this didn't work either. The information came up exactly as before but I wasn't able to connect through. I hadn't tried this earlier because I'd gotten it working on WPA before and was sure it was something in config I hadn't done right ... looks like it might be a driver issue instead if I can't connect full stop :-(

[wieman01]

Wieman,

Thanks for your response.

I tried setting up an open network and interestingly this didn't work either. The information came up exactly as before but I wasn't able to connect through. I hadn't tried this earlier because I'd gotten it working on WPA before and was sure it was something in config I hadn't done right ... looks like it might be a driver issue instead if I can't connect full stop :-(
Hello,

Alright, that's what you have to work on then. You are close, but you need to fix your adapter first before we go ahead. Please open a new thread and feel free to post the link here.

wieman01

[daniel.pool]

Hello,

Alright, that's what you have to work on then. You are close, but you need to fix your adapter first before we go ahead. Please open a new thread and feel free to post the link here.

wieman01

Hey,

I downgraded the driver version from the 2.2 version to the 2.1.2 that I would have used a few months back. It appears that the latest version is broken. I've posted on the ubuntu support thread (http://ubuntuforums.org/showpost.php?p=7870385&postcount=57) for the ralink 2870sta adaptor that I use and will see if I can raise a bug report with ralink themselves.

The wpa_supplicant stuff connected straight off once the driver was replaced, though I still get the occasional message that wpa_supplicant daemon couldn't start even though the connection is working fine :confused:


root@HTPC:/home/htpc# /etc/init.d/networking restart
* Reconfiguring network interfaces...
wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1

[Xkutzy]

This is a bump for my last post in this thread (#1750). Has anyone got any thoughts?

Thanks,

Xkutzy

[ugm6hr]

This is a bump for my last post in this thread (#1750). Has anyone got any thoughts?

I would suggest you search for posts relating to your device.

Essentially, some people found it works out of the box, some didn't. It worked better with the serialmonkey drivers in general than the default legacy ones. The serialmonkey drivers are now in the Jaunty kernel.

[Xkutzy]

Thanks for the tip Ugm6hr. I did a bit of further research as suggested. From what I gather the ealier versions of the serial monkey driver that were incorporated into the Hardy kernel were by their own admission a bit buggy.
I didn't fancy installing a later version of that driver. Too much hassle every time there is a new kernel. So I did a fresh install of Jaunty instead. Wireless with WPA worked straight out of the box. I've almost finished getting things the way I want them. Just one or two issues with some web sites in Firefox. But that's a job for another day.

[kevdog]

serialmonkey drivers finally contained in the jaunty kernel -- wow -- its about time. Thank you to whom ever made this happen!!! Can't wait until the release date!!!

[bud_man]

I tried following the steps for WPA1, static IP address, but I can't seem to get it up and running. I'm fairly new to this stuff and I'm running out of ideas. I think it might have to do with the Ethernet interface because it says "*-network DISABLED", but I'm not sure.
The system that I'm trying to get the internet to work on is Ubuntu Studio 9.04, and the weird thing about it is that I can get my other partition, Ubuntu 9.04, to get wireless access except for that one.


buddy@roz:~$ sudo /etc/init.d/networking restart
* Reconfiguring network interfaces...
wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1
* if-up.d/mountnfs[wlan0]: waiting for interface eth0 before doing NFS mounts
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/eth0/00:16:d4:8b:35:30
Sending on LPF/eth0/00:16:d4:8b:35:30
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 19
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 19
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 1
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
[ OK ]
buddy@roz:~$ sudo lshw -C network
*-network
description: Wireless interface
product: PRO/Wireless 3945ABG [Golan] Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:04:00.0
logical name: wmaster0
version: 02
serial: 00:19:d2:1e:42:99
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=iwl3945 ip=192.168.1.100 latency=0 module=iwl3945 multicast=yes wireless=IEEE 802.11abg
*-network DISABLED
description: Ethernet interface
product: RTL8101E/RTL8102E PCI Express Fast Ethernet controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:05:00.0
logical name: eth0
version: 01
serial: 00:16:d4:8b:35:30
size: 10MB/s
capacity: 100MB/s
width: 64 bits
clock: 33MHz
capabilities: pm vpd msi pciexpress bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half latency=0 link=yes module=r8169 multicast=yes port=MII speed=10MB/s
*-network DISABLED
description: Ethernet interface
physical id: 2
logical name: pan0
serial: a6:6c:2f:48:09:e0
capabilities: ethernet physical
configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A link=yes multicast=yes

buddy@roz:~$ sudo iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wmaster0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:22:6B:53:69:FD
ESSID:"Margarita1"
Mode:Master
Channel:1
Frequency:2.412 GHz (Channel 1)
Quality=31/100 Signal level:-90 dBm Noise level=-127 dBm
Encryption key:on
IE: Unknown: 000A4D617267617269746131
IE: Unknown: 010882848B9624B0486C
IE: Unknown: 030101
IE: Unknown: 050400010000
IE: Unknown: 2A0104
IE: Unknown: 2F0104
IE: Unknown: 32048C129860
IE: Unknown: DD0E0050F204104A0001101044000102
IE: Unknown: DD090010180200F4000000
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:tsf=00000066b4bca183
Extra: Last beacon: 1418ms ago
Cell 02 - Address: 00:18:39:3F:D8:1F
ESSID:<some_name>
Mode:Master
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=88/100 Signal level:-44 dBm Noise level=-127 dBm
Encryption key:on
IE: Unknown: 0003726F7A
IE: Unknown: 010882848B962430486C
IE: Unknown: 030106
IE: Unknown: 050400010000
IE: Unknown: 2A0104
IE: Unknown: 2F0104
IE: Unknown: 32040C121860
IE: Unknown: DD060010180202F4
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:tsf=000000fe690103b6
Extra: Last beacon: 384ms ago
Cell 03 - Address: 00:11:E3:3E:A2:8F
ESSID:"M_Network"
Mode:Master
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=31/100 Signal level:-90 dBm Noise level=-127 dBm
Encryption key:on
IE: Unknown: 00094D5F4E6574776F726B
IE: Unknown: 010882848B962430486C
IE: Unknown: 030106
IE: Unknown: 050400010000
IE: Unknown: 2A0100
IE: Unknown: 2F0100
IE: Unknown: 32040C121860
IE: Unknown: DD06001018020100
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:tsf=0000005327e59187
Extra: Last beacon: 730ms ago

pan0 Interface doesn't support scanning.

buddy@roz:~$ sudo lshw -C network
*-network
description: Wireless interface
product: PRO/Wireless 3945ABG [Golan] Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:04:00.0
logical name: wmaster0
version: 02
serial: 00:19:d2:1e:42:99
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=iwl3945 latency=0 module=iwl3945 multicast=yes wireless=IEEE 802.11abg
*-network DISABLED
description: Ethernet interface
product: RTL8101E/RTL8102E PCI Express Fast Ethernet controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:05:00.0
logical name: eth0
version: 01
serial: 00:16:d4:8b:35:30
size: 10MB/s
capacity: 100MB/s
width: 64 bits
clock: 33MHz
capabilities: pm vpd msi pciexpress bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half latency=0 link=yes module=r8169 multicast=yes port=MII speed=10MB/s
*-network DISABLED
description: Ethernet interface
physical id: 2
logical name: pan0
serial: a6:6c:2f:48:09:e0
capabilities: ethernet physical
configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A link=yes multicast=yes

buddy@roz:~$ lsmod
Module Size Used by
nls_iso8859_1 13440 1
nls_cp437 15104 1
vfat 21120 1
fat 65840 1 vfat
usb_storage 94912 1
cbc 12288 62
aes_x86_64 16384 63
aes_generic 36264 1 aes_x86_64
i915 75272 2
drm 124432 3 i915
ppdev 16904 0
bridge 64160 0
stp 11268 1 bridge
bnep 23168 2
joydev 20864 0
lp 20676 0
parport 50188 2 ppdev,lp
arc4 10240 2
snd_hda_intel 557236 2
ecb 11392 3
pcmcia 48080 0
snd_pcm_oss 52352 0
snd_mixer_oss 25088 1 snd_pcm_oss
snd_pcm 98056 2 snd_hda_intel,snd_pcm_oss
snd_seq_dummy 11524 0
snd_seq_oss 42496 0
snd_seq_midi 15872 0
snd_rawmidi 33664 1 snd_seq_midi
iwl3945 111736 0
snd_seq_midi_event 16640 2 snd_seq_oss,snd_seq_midi
mac80211 253832 1 iwl3945
snd_seq 66848 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_mid i_event
iTCO_wdt 21632 0
yenta_socket 35724 1
iTCO_vendor_support 12420 1 iTCO_wdt
led_class 13064 1 iwl3945
rsrc_nonstatic 19584 1 yenta_socket
sdhci_pci 16896 0
snd_timer 33544 2 snd_pcm,snd_seq
tifm_7xx1 14976 0
sdhci 27396 1 sdhci_pci
snd_seq_device 16276 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi ,snd_seq
pcmcia_core 50004 3 pcmcia,yenta_socket,rsrc_nonstatic
tifm_core 18056 1 tifm_7xx1
cfg80211 43552 2 iwl3945,mac80211
pcspkr 11136 0
intel_agp 39280 1
psmouse 64028 0
serio_raw 14468 0
input_polldev 12816 0
snd 79432 13 snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,sn d_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_de vice
soundcore 17312 1 snd
snd_page_alloc 18832 2 snd_hda_intel,snd_pcm
video 29204 0
output 11648 1 video
ohci1394 42548 0
ieee1394 110176 1 ohci1394
r8169 46724 0
mii 14464 1 r8169
fbcon 50048 0
tileblit 11264 1 fbcon
font 17024 1 fbcon
bitblit 14464 1 fbcon
softcursor 10368 1 bitblit

buddy@roz:~$ sudo wpa_supplicant -Dwext -iwlan0 -c wpa_supplicant.conf
Failed to read or parse configuration '/home/buddy/wpa_supplicant.conf'.
buddy@roz:~$ sudo gedit /etc/resolv.conf
buddy@roz:~$ sudo ln -s /etc/init.d/wireless-network /etc/rcS.d/S40wireless-network
ln: creating symbolic link `/etc/rcS.d/S40wireless-network': File exists
buddy@roz:~$ sudo gedit /etc/init.d/wireless-network
buddy@roz:~$ lspci -v | less

04:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
Subsystem: Intel Corporation Device 1040
Flags: bus master, fast devsel, latency 0, IRQ 2299
Memory at d8000000 (32-bit, non-prefetchable) [size=4K]
Capabilities: <access denied>
Kernel driver in use: iwl3945
Kernel modules: iwl3945

05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 01)
Subsystem: Toshiba America Info Systems Device ff00
Flags: bus master, fast devsel, latency 0, IRQ 2300
I/O ports at 4000 [size=256]
Memory at da000000 (64-bit, non-prefetchable) [size=4K]
[virtual] Expansion ROM at d4000000 [disabled] [size=64K]
Capabilities: <access denied>
Kernel driver in use: r8169
Kernel modules: r8169

buddy@roz:~$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:16:d4:8b:35:30
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:252 Base address:0x8000

eth0:avahi Link encap:Ethernet HWaddr 00:16:d4:8b:35:30
inet addr:169.254.5.36 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Interrupt:252 Base address:0x8000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:106 errors:0 dropped:0 overruns:0 frame:0
TX packets:106 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:7916 (7.9 KB) TX bytes:7916 (7.9 KB)

pan0 Link encap:Ethernet HWaddr a6:6c:2f:48:09:e0
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wlan0 Link encap:Ethernet HWaddr 00:19:d2:1e:42:99
inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.255
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wmaster0 Link encap:UNSPEC HWaddr 00-19-D2-1E-42-99-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

buddy@roz:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11abg ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=15 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

pan0 no wireless extensions.

buddy@roz:~$ sudo gedit /etc/network/interfaces

auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet static
address 192.168.1.100
netmask 255.255.255.255
wpa-driver wext
wpa-conf managed
wpa-essid <some_name>
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <some_key>

auto eth0
iface eth0 inet dhcp

Any help is greatly appreciated! Thanks!

[doixanh]

Sorry to bump this old thread, but I'm really confused about my wireless problem.

It's my Dell Vostro 1500 laptop. I installed the wireless card successfully (using ndiswrapper) in Hardy. After a clean format/install of Karmic, the problem started. I cannot connect to the AP. Encryption is WPA2 RSN, CCMP, PSK. I followed the first post but I still cannot connect to it. I also tried to reset the WPA2 password but no luck yet.

The wireless LED is on.

These are output from the commands

dx@dx-ubuntu:~$ lspci | grep Broadcom\ Corporation
03:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)
0c:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g (rev 01)

dx@dx-ubuntu:~$ lshw -C network
WARNING: you should run this program as super-user.
*-network
description: Wireless interface
product: BCM4312 802.11b/g
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:0c:00.0
logical name: wlan0
version: 01
serial: 00:1e:4c:48:65:ea
width: 64 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ndiswrapper+bcmwl5 driverversion=1.55+Broadcom,09/20/2007, 4.170. latency=0 multicast=yes wireless=IEEE 802.11g
resources: irq:17 memory:f9ffc000-f9ffffff
*-network
description: Ethernet interface
product: BCM4401-B0 100Base-TX
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:03:00.0
logical name: eth0
version: 02
serial: 00:1d:09:bf:f5:a4
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical
configuration: broadcast=yes driver=b44 driverversion=2.0 ip=192.168.254.102 latency=64 multicast=yes
resources: irq:17 memory:f9bfe000-f9bfffff

dx@dx-ubuntu:~$ cat /etc/modprobe.d/blacklist
blacklist b43
blacklist b43legacy
blacklist wl

dx@dx-ubuntu:~$ cat /etc/modprobe.d/ndiswrapper
alias wlan0 ndiswrapper
install ndiswrapper modprobe -r b43 b44 b43legacy ssb; modprobe --ignore-install ndiswrapper $CMDLINE_OPTS; modprobe ssb; modprobe b44;

dx@dx-ubuntu:~$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto wlan0
iface wlan0 inet dhcp
# address 192.168.254.199
# gateway 192.168.254.1
# dns-nameservers 192.168.254.1
# netmask 255.255.255.0
wpa-driver wext
wpa-ssid dnxp
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
(I replaced my psk)

And this is my problem : I cannot connect to my AP to get IP

dx@dx-ubuntu:~$ sudo ifup -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -s -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: sendsigs omission pidfile not created
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan0
wpa_supplicant: wpa-ap-scan 1 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "dnxp" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise CCMP -- OK
wpa_supplicant: wpa-group CCMP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto RSN -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
Internet Systems Consortium DHCP Client V3.1.2
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:1e:4c:48:65:ea
Sending on LPF/wlan0/00:1e:4c:48:65:ea
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 21
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/upstart
run-parts: executing /etc/network/if-up.d/wpasupplicant
Can someone help me to solve this problem? Thanks!

[kevdog]

Couple of suggestions I would make and a few comments:

#1 - Do you know your bcmwl5 driver actually support wpa2.

#2 - Confirm you can actually do wpa1 with your current setup if possible.

#3 - Try to do a manual connection at the command line and a wpa_supplicant.conf file (as explained by the link in my signature) rather than going for network manager. This isn't meant as a permanent solution rather than a means of discovery to what this current problem represents.

[doixanh]

Thanks for your quick reply, kevdog.


#1 - Do you know your bcmwl5 driver actually support wpa2.

yes, I successfully used it in Hardy.


#2 - Confirm you can actually do wpa1 with your current setup if possible.

I reconfigured my access point to WPA1, and I still have same problem under Karmic. Windows connects to my AP using old (WPA2) and this new configuration (WPA1) with no problem.


#3 - Try to do a manual connection at the command line and a wpa_supplicant.conf file (as explained by the link in my signature) rather than going for network manager. This isn't meant as a permanent solution rather than a means of discovery to what this current problem represents.

I didn't use any network manager at all. I only installed ndiswrapper-utils-1.9, wpasupplicant and I manually edited the "interfaces" file. I also tried to use wifi-radar and wicd, no luck. After trying these packages with no success, I removed them immediately.

Anyway I will try your solution.

/edit : I tried manually connecting, no luck yet.
Current setup is WPA1, and these are the output:

dx@dx-ubuntu:~$ sudo ifconfig wlan0 down
dx@dx-ubuntu:~$ sudo dhclient -r wlan0
There is already a pid file /var/run/dhclient.pid with pid 1512
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.1.2
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:1e:4c:48:65:ea
Sending on LPF/wlan0/00:1e:4c:48:65:ea
Sending on Socket/fallback

dx@dx-ubuntu:~$ sudo wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -dd Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ap_scan=1
ctrl_interface='/var/run/wpa_supplicant'
Line: 4 - start of a new network block
ssid - hexdump_ascii(len=4):
64 6e 78 70 dnxp
scan_ssid=0 (0x0)
proto: 0x1
key_mgmt: 0x2
PSK (ASCII passphrase) - hexdump_ascii(len=9): [REMOVED]
pairwise: 0x8
group: 0x8
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
id=0 ssid='dnxp'
Interface wlan0 set UP - waiting a second for the driver to complete initialization
SIOCGIWRANGE: WE(compiled)=22 WE(source)=18 enc_capa=0xf
capabilities: key_mgmt 0xf enc 0xf flags 0x0
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:1e:4c:48:65:ea
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
WPS: UUID based on MAC address - hexdump(len=16): f3 65 df c1 39 c0 55 13 8c 52 ed 21 2a bd 81 cc
WPS: Build Beacon and Probe Response IEs
WPS: * Version
WPS: * Wi-Fi Protected Setup State (0)
WPS: * Version
WPS: * Wi-Fi Protected Setup State (0)
WPS: * Response Type (2)
WPS: * UUID-E
WPS: * Manufacturer
WPS: * Model Name
WPS: * Model Number
WPS: * Serial Number
WPS: * Primary Device Type
WPS: * Device Name
WPS: * Config Methods (0)
WPS: * RF Bands (3)
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
Using existing control interface directory.
ctrl_iface bind(PF_UNIX) failed: Address already in use
ctrl_iface exists and seems to be in use - cannot override it
Delete '/var/run/wpa_supplicant/wlan0' manually if it is not used anymore
Failed to initialize control interface '/var/run/wpa_supplicant'.
You may have another wpa_supplicant process already running or the file was
left by an unclean termination of wpa_supplicant in which case you will need
to manually remove this file before starting wpa_supplicant again.

Failed to add interface wlan0
State: DISCONNECTED -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
wpa_driver_wext_set_wpa
wpa_driver_wext_set_drop_unencrypted
wpa_driver_wext_set_countermeasures
No keys have been configured - skip key clearing
Cancelling scan request
Cancelling authentication timeout
WEXT: Operstate: linkmode=0, operstate=6
and try iwconfig


dx@dx-ubuntu:~$ iwconfig
lo no wireless extensions.

wlan0 IEEE 802.11g ESSID:"dnxp"
Mode:Managed Frequency:2.437 GHz Access Point: 00:1A:70:94:FC:A8
Bit Rate=54 Mb/s Tx-Power:32 dBm
RTS thr:2347 B Fragment thr:2346 B
Power Management:off
Link Quality:54/100 Signal level:-61 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

eth0 no wireless extensions.
and then try getting IP


dx@dx-ubuntu:~$ sudo dhclient wlan0
Internet Systems Consortium DHCP Client V3.1.2
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:1e:4c:48:65:ea
Sending on LPF/wlan0/00:1e:4c:48:65:ea
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
My current wpa_supplicant.conf for current WPA1 setup:


ap_scan=1
ctrl_interface=/var/run/wpa_supplicant

network={
ssid="dnxp"
scan_ssid=0
proto=WPA
key_mgmt=WPA-PSK
psk="pure-key-here"
pairwise=TKIP
group=TKIP
}
and my current "interfaces" file


# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto wlan0
iface wlan0 inet dhcp
# address 192.168.254.199
# gateway 192.168.254.1
# dns-nameservers 192.168.254.1
# netmask 255.255.255.0
# wpa-driver wext
# wpa-ssid dnxp
# wpa-ap-scan 2
# wpa-proto WPA
# wpa-pairwise TKIP
# wpa-group TKIP
# wpa-key-mgmt WPA-PSK
# wpa-psk xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Any help please?

[kevdog]

I saw this examining your output:

Failed to initialize control interface '/var/run/wpa_supplicant'.
You may have another wpa_supplicant process already running or the file was
left by an unclean termination of wpa_supplicant in which case you will need
to manually remove this file before starting wpa_supplicant again.

[doixanh]

Ok I got it solved. My problem is the same as the one described here (http://ubuntuforums.org/showpost.php?p=8082022&postcount=4).

The drawback is that I have to manually use wpa_supplicant and run renice every boot. Kinda annoying but no fix to this time.

Thank you kevdog. :popcorn:

[kevdog]

I have no idea why the renice command works for you since a nice value of +19 is actually almost the lowest priority available (+20). I actually looked at the link you provided but the link within the link actually didn't provide any information. That's pretty good detective work on your part since I've never seen this command used in conjunction with wpa_supplicant.

[darkod]

Sorry if this is covered in any post, but there are 177 pages already. :) I also tried googling for 2 days.

Can someone please give instructions how to use wlan0 as soft AP? Not directly as ad-hoc but as soft AP. I heard that improves signal strength and/or security. I would definitely want to use WPA2 with that if possible.
I have been searching for any software about this, but no luck. I don't mind setting it up in /etc/network/interfaces in fact it might be better that way.
From reading around setting Master mode of the adapter is the main thing.
Do I just add that line and use the rest of the settings as per this how-to?
My usb N wi-fi adapter is still in the post but from what I could find out it seems to use Ralink RT2870 chip, if that helps. I am searching for tutorials to be ready when it arrives. :)

I basically want to share my desktop eth0 connected to the internet with my netbook. The netbook has integrated G (in ubuntu reported as ath5k I think), and I'm waiting for the usb N for the desktop. Any help greatly appreciated.

PS. It might be good idea to add soft AP section or modification instructions to the original how-to, during these 2 days I saw many threads asking for soft AP solution but no answer.

[urrfaust]

Hi everyone,

I'm having a problem with my wireless connection.
I use WPA2-AES with an Intel 2915abg adapter. I get the Ip address from the dhcp server but then after a few seconds the connection drops. Sometimes the connection stays on but I have no access to DNS server. Could it be a ipw2200 driver error? Or a configuration error? I tried all sorts of tips given here on this forum but to no avail. Funny thing is that I tried the same card on Windows XP SP3 and it has the same problem: I get IP address but then no DNS connection. With a friend who knows about networking, we looked at the DNS server logs and apparently the server gets corrupted requests (ICMP for example) from the wireless adapter.
It works fine with WPA(1) and WEP.
Any clue?

Using Karmic 9.10 kernel 2.6.31-16-generic and latest ipw2200 drivers

Thanks a lot.

Here are some info:


lspci
02:02.0 Network controller: Intel Corporation PRO/Wireless 2915ABG [Calexico2] Network Connection (rev 05)


lsmod:



lsmod | grep ipw2200
ipw2200 140292 0
libipw 43148 1 ipw2200
lib80211 6432 2 ipw2200,libipw


Route:


Destination Gateway Genmask Flags Metric Ref Use Iface
10.0.0.0 * 255.255.255.192 U 0 0 0 eth0
link-local * 255.255.0.0 U 0 0 0 eth1
default 10.0.0.1 0.0.0.0 UG 0 0 0 eth0




/etc/network$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

irda0 no wireless extensions.

eth1 unassociated Mode:Managed Frequency=2.467 GHz
Access Point: Not-Associated Bit Rate:0 kb/s Tx-Power=20 dBm
Sensitivity=8/0
Retry limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0




/etc/network$ sudo iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

irda0 Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:1F:C6:53:0E:17
ESSID:"karli"
Protocol:IEEE 802.11bg
Mode:Master
Frequency:2.412 GHz (Channel 1)
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=41/100 Signal level=-76 dBm
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Extra: Last beacon: 4028ms ago
Cell 02 - Address: 00:02:CF:9B:F7:DA
ESSID:"WPK"
Protocol:IEEE 802.11bg
Mode:Master
Frequency:2.417 GHz (Channel 2)
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=68/100 Signal level=-59 dBm
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
Extra: Last beacon: 1604ms ago
Cell 03 - Address: 00:02:CF:9B:F7:DB
ESSID:"VOIP"
Protocol:IEEE 802.11bg
Mode:Master
Frequency:2.417 GHz (Channel 2)
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=70/100 Signal level=-58 dBm
Extra: Last beacon: 1604ms ago
Cell 04 - Address: 00:24:36:AE:0E:BF
ESSID:"UNYP"
Protocol:IEEE 802.11bg
Mode:Master
Frequency:2.427 GHz (Channel 4)
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=39/100 Signal level=-77 dBm
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
Extra: Last beacon: 13632ms ago
Cell 05 - Address: 06:24:36:AE:0E:BF
ESSID:"Peter Cizek's Guest Network"
Protocol:IEEE 802.11bg
Mode:Master
Frequency:2.427 GHz (Channel 4)
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=35/100 Signal level=-79 dBm
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
Extra: Last beacon: 3952ms ago
Cell 06 - Address: 00:1C:F0:48:A8:62
ESSID:"chameleoun"
Protocol:IEEE 802.11bg
Mode:Master
Frequency:2.437 GHz (Channel 6)
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=39/100 Signal level=-77 dBm
Extra: Last beacon: 3928ms ago
Cell 07 - Address: 00:B0:0C:42:2A:A0
ESSID:"Studna"
Protocol:IEEE 802.11bg
Mode:Master
Frequency:2.437 GHz (Channel 6)
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 11 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=33/100 Signal level=-80 dBm
IE: WPA Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
Extra: Last beacon: 3912ms ago
Cell 08 - Address: 00:E0:98:B7:38:A5
ESSID:"tauri"
Protocol:IEEE 802.11b
Mode:Master
Frequency:2.447 GHz (Channel 8)
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Quality=41/100 Signal level=-76 dBm
Extra: Last beacon: 3824ms ago
Cell 09 - Address: 00:1B:2F:4D:5F:B0
ESSID:"SWAMP"
Protocol:IEEE 802.11bg
Mode:Master
Frequency:2.462 GHz (Channel 11)
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 9 Mb/s; 11 Mb/s
6 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=51/100 Signal level=-70 dBm
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Extra: Last beacon: 1276ms ago
Cell 10 - Address: 00:24:01:90:E7:04
ESSID:"Marquez"
Protocol:IEEE 802.11bg
Mode:Master
Frequency:2.462 GHz (Channel 11)
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 48 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 54 Mb/s
Quality=35/100 Signal level=-79 dBm
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Extra: Last beacon: 13456ms ago
Cell 11 - Address: XXX
ESSID:"APEIRON"
Protocol:IEEE 802.11bg
Mode:Master
Frequency:2.467 GHz (Channel 12)
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=85/100 Signal level=-33 dBm
IE: IEEE 802.11i/WPA2 Version 1
ESSID:"CARONTE"
Protocol:IEEE 802.11b
Mode:Master
Frequency:2.467 GHz (Channel 12)
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Quality=64/100 Signal level=-62 dBm
Extra: Last beacon: 1256ms ago
Cell 13 - Address: 00:23:F8:8B:4D:C0
ESSID:"lotos111"
Protocol:IEEE 802.11bg
Mode:Master
Frequency:2.447 GHz (Channel 8)
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=31/100 Signal level=-81 dBm
Extra: Last beacon: 3824ms ago
Cell 14 - Address: 00:23:F8:8B:4D:C1
ESSID:"VOIP"
Protocol:IEEE 802.11bg
Mode:Master
Frequency:2.447 GHz (Channel 8)
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=33/100 Signal level=-80 dBm
Extra: Last beacon: 3864ms ago


/etc/network$ sudo lshw -C network
*-network:0
description: Wireless interface
product: PRO/Wireless 2915ABG [Calexico2] Network Connection
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:02:02.0
logical name: eth1
version: 05
serial: XXX
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ipw2200 driverversion=1.2.2kmprq firmware=ABG:9.0.5.27 (Dec 12 2007) latency=64 link=no maxlatency=24 mingnt=3 multicast=yes wireless=unassociated
resources: irq:11 memory:d0200000-d0200fff




sudo cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto eth1
iface eth1 inet dhcp
wpa-driver wext
wpa-conf managed
wpa-ssid APEIRON
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk XXX




sudo ifdown -v eth1
Configuring interface eth1=eth1 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/upstart
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.eth1.pid -lf /var/lib/dhcp3/dhclient.eth1.leases eth1
There is already a pid file /var/run/dhclient.eth1.pid with pid 5338
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.1.2
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/XXX
Sending on LPF/eth1/XXX
Sending on Socket/fallback
DHCPRELEASE on eth1 to 172.16.0.1 port 67
ifconfig eth1 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant





sudo ifup -v eth1
Configuring interface eth1=eth1 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/ethtool
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -s -B -P /var/run/wpa_supplicant.eth1.pid -i eth1 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: sendsigs omission pidfile not created
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/eth1
wpa_supplicant: wpa-ap-scan 2 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "APEIRON" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise CCMP -- OK
wpa_supplicant: wpa-group CCMP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto RSN -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.eth1.pid -lf /var/lib/dhcp3/dhclient.eth1.leases eth1
Internet Systems Consortium DHCP Client V3.1.2
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/XXX
Sending on LPF/eth1/XXX
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
DHCPOFFER of 172.16.0.7 from 172.16.0.1
DHCPREQUEST of 172.16.0.7 on eth1 to 255.255.255.255 port 67
DHCPACK of 172.16.0.7 from 172.16.0.1
bound to 172.16.0.7 -- renewal in 16748 seconds.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/ethtool
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/upstart
run-parts: executing /etc/network/if-up.d/wpasupplicant

[staffann]

I had some problems when following the guide in the first post in this thread.

Although my Philips router uses WPA2, it uses wpa-groun TKIP and not CCMP. I realised that by the command iwlist wlan1 scan which gave the following result my network:




wlan1 Scan completed :
Cell 01 - Address: 00:1A:2A:2E:4D:BC
ESSID:"staffan"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:28/100 Signal level:-78 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
Preauthentication Supported
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : TKIP CCMP
Authentication Suites (1) : PSK



After that I could connect to the router but the dns servers didn't work. I still haven't been able to get dns running the way that is described in the post. Instead I manually edited resolv.conf and added my dns server there:


nameserver 192.168.1.2


That in combination with this interface file works:


auto lo
iface lo inet loopback

auto wlan1
iface wlan1 inet static
address 192.168.1.102
gateway 192.168.1.2
dns-nameservers 192.168.1.2
netmask 255.255.255.0
wpa-driver wext
wpa-ssid *MyNetwork*
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk *MyCode*


Does anyone know why the dns-nameservers part of the interfaces file doesn't do its job? I use Ubuntu 9.10.

[wieman01]

Please post the content of "/etc/resolv.conf".

Also could you ping your router please and see what happens?

[staffann]

Is the question to me?
My /etc/resolv.conf was empty to start with. Now I've manually added my router as a dns server in that file. The content is shown in my previous post - there isn't anything else. The thing is that the howto in the first post doesn't say I have to add anything in resolv-conf. I thought the line "dns-nameservers 192.168.1.2" in the /etc/network/interface file should do the job but it didn't seem to work. Is it supposed to? Is the howto in the first post of this thread incorrect?

I could ping my router without problems. The problem was just with the dns.

Oh, and the reason I started manually editing these files was that the System->Preferences->Network Connections didn't work. It did sporadically but very unfrequently succeed to connect. I removed my network from there before adding things into the interface file.

[wieman01]

Hi Staffann,

Yes, it was directed at you.

I think the problem has indeed something to do with resolv.conf. It a problem that I had before, therefore I was asking. Could you post the contents please?

I am pretty sure you are very close!

[staffann]

Hi!
Before I edited it, it was empty. Now I've added the following line:

nameserver 192.168.1.2

This line makes the dns work.

[wieman01]

Hi!
Before I edited it, it was empty. Now I've added the following line:

nameserver 192.168.1.2

This line makes the dns work.
That's exactly what I was going to get at. :-) The DNS needs an entry in this file and occasionally, it does not get updated.

Well done!

[Alligator]

Stumped - I can't get the wireless to work. I'm using 9.10 and 9.04 wireless worked on a different network. i.e. the one at work, but I'm now retired. Wired works fine. I have a router/firewall from my IP with wireless capability.
The following is the suggested info from this post.

ronh@ronh-laptop:~$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
link-local * 255.255.0.0 U 0 0 0 wlan0

ronh@ronh-laptop:~$ iwconfig

wlan0 IEEE 802.11abgn ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=15 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


ronh@ronh-laptop:~$ sudo iwlist scan

wlan0 Scan completed :
Cell 01 - Address: 00:1A:C4:63:F6:09
Channel:7
Frequency:2.442 GHz (Channel 7)
Quality=37/70 Signal level=-73 dBm
Encryption key:on
ESSID:"2WIRE762"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s
Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
Mode:Master
Extra:tsf=00000000b51a8181
Extra: Last beacon: 2870ms ago
IE: Unknown: 00083257495245373632
IE: Unknown: 010882848B0C12961824
IE: Unknown: 030107
IE: Unknown: 0706555320010B1B
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: Unknown: 2A0100
IE: Unknown: 32043048606C
Cell 02 - Address: 00:23:51:4C:6D:89
Channel:2
Frequency:2.417 GHz (Channel 2)
Quality=31/70 Signal level=-79 dBm
Encryption key:on
ESSID:"2WIRE795"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s
Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
Mode:Master
Extra:tsf=0000006422052306
Extra: Last beacon: 3230ms ago
IE: Unknown: 00083257495245373935
IE: Unknown: 010882848B0C12961824
IE: Unknown: 030102
IE: Unknown: 0706555320010B1B
IE: Unknown: 2A0100
IE: Unknown: 32043048606C


ronh@ronh-laptop:~$ sudo lshw -C network
*-network
description: Ethernet interface
product: NetXtreme BCM5764M Gigabit Ethernet PCIe
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:02:00.0
logical name: eth0
version: 10
serial: 00:1d:72:ed:4a:9e
capacity: 1GB/s
width: 64 bits
clock: 33MHz
capabilities: pm vpd msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=tg3 driverversion=3.99 firmware=5764m-v3.34 latency=0 link=no multicast=yes port=twisted pair
resources: irq:30 memory:f3000000-f300ffff
*-network
description: Wireless interface
product: Wireless WiFi Link 5100
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:03:00.0
logical name: wmaster0
version: 00
serial: 00:21:6b:06:45:0c
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=iwlagn latency=0 multicast=yes wireless=IEEE 802.11abgn
resources: irq:29 memory:f3100000-f3101fff
*-network DISABLED
description: Ethernet interface
physical id: 4
logical name: vboxnet0
serial: 0a:00:27:00:00:00
capabilities: ethernet physical
configuration: broadcast=yes multicast=yes

ronh@ronh-laptop:~$ sudo cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid 00:1a:c4:63:f6:09
wpa-ap-scan 1
wpa-proto WPA RSN
wpa-pairwise TKIP CCMP
wpa-group TKIP CCMP
wpa-key-mgmt WPA-PSK
wpa-psk <my_code>

ronh@ronh-laptop:~$ sudo ifdown -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/50firestarter
* Stopping the Firestarter firewall...
...done.
* Starting the Firestarter firewall...
...fail!
run-parts: /etc/network/if-down.d/50firestarter exited with return code 2
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/upstart
run-parts: executing /etc/network/if-down.d/wpasupplicant
dhclient3 -r -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
There is already a pid file /var/run/dhclient.wlan0.pid with pid 2351
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.1.2
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:21:6b:06:45:0c
Sending on LPF/wlan0/00:21:6b:06:45:0c
Sending on Socket/fallback
ifconfig wlan0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.wlan0.pid
Stopped /sbin/wpa_supplicant (pid 1176).


ronh@ronh-laptop:~$ sudo ifup -v wlan0
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/ethtool
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -s -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: sendsigs omission pidfile not created
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/wlan0
wpa_supplicant: wpa-ap-scan 1 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "00:1a:c4:63:f6:09" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise TKIP CCMP -- OK
wpa_supplicant: wpa-group TKIP CCMP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto WPA RSN -- OK
wpa_supplicant: enabling network block 0 -- OK

dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.wlan0.pid -lf /var/lib/dhcp3/dhclient.wlan0.leases wlan0
Internet Systems Consortium DHCP Client V3.1.2
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:21:6b:06:45:0c
Sending on LPF/wlan0/00:21:6b:06:45:0c
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/50firestarter
* Stopping the Firestarter firewall...
...done.
* Starting the Firestarter firewall...
...fail!
run-parts: /etc/network/if-up.d/50firestarter exited with return code 2
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/ethtool
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/upstart
run-parts: executing /etc/network/if-up.d/wpasupplicant

ronh@ronh-laptop:~$ uname -a
Linux ronh-laptop 2.6.31-16-generic #53-Ubuntu SMP Tue Dec 8 04:02:15 UTC 2009 x86_64 GNU/Linux

ronh@ronh-laptop:~$ sudo dhclient wlan0
Internet Systems Consortium DHCP Client V3.1.2
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:21:6b:06:45:0c
Sending on LPF/wlan0/00:21:6b:06:45:0c
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
No DHCPOFFERS received.
No working leases in persistent database - sleeping.


Firewall is Firestarter

Network settings
Internet detect devices wlan0
Local network connected devices wlan0

enable DHCP

keep existing DHCP configuration

ronh@ronh-laptop:~$ cat /etc/resolv.conf
# Generated by NetworkManager

[wieman01]

Hello Alligator,

I have been using WICD for a while which you find in the repositories. Would this be an option for you? Or do you need a command line configuration?

[Alligator]

I will give this a try. Thank you.

[wieman01]

I will give this a try. Thank you.
It's the most obvious solution if everything fails at the moment. Give it a go and let me know if it works out for you.

[Alligator]

It doesn't work. I get an error message - unable to find ip address.

[lightsabersetc]

Hey everyone, I have been working on this for a while now and am absolutely stumped. Basically, what i am attempting to do is make my ubuntu box into a gateway for my network. I have everything working thru hard wire, but I simply cant get the wireless to work. No matter what I do, I cannot get my wireless card to transmit an essid and allow nodes to connect. I have tried assigning it in the interfaces file (shown below), and I have also tried manually modifying it using the iwconfig command. Here is the topology:
eth1: internet WAN
eth2: ethernet out to LAN
ra0: wireless out to LAN

Here is a copy of my /etc/network/interfaces file:


auto lo
iface lo inet loopback
auto eth2
iface eth2 inet static
address 192.168.0.102
netmask 255.255.255.0
broadcast 192.168.0.0
network 192.168.0.0
auto eth1
iface eth1 inet dhcp

auto ra0
iface ra0 inet static
address 192.168.2.102
netmask 255.255.255.0
broadcast 192.168.2.0
network 192.168.2.0
#wireless-mode Ad-Hoc
#wireless-essid laz
wpa-driver wext
wpa-ssid las
wpa-ap-scan 1
wpa-proto WPA RSN
wpa-pairwise TKIP CCMP
wpa-group TKIP CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 56a72e371fd87baef20cda1a198f2972e479890dbe982ed336 de33293c20d891 [CODE]

route command:
[CODE]Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 * 255.255.255.0 U 0 0 0 ra0
192.168.0.0 * 255.255.255.0 U 0 0 0 eth2
98.160.136.0 * 255.255.252.0 U 0 0 0 eth1
link-local * 255.255.0.0 U 1000 0 0 eth2
default ip98-160-136-1. 0.0.0.0 UG 100 0 0 eth1

ifconfig:

eth1 Link encap:Ethernet HWaddr 00:1a:66:4b:51:b0
inet addr:98.160.137.113 Bcast:98.160.139.255 Mask:255.255.252.0
inet6 addr: fe80::21a:66ff:fe4b:51b0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:890686 errors:744 dropped:0 overruns:0 frame:744
TX packets:614991 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1068172509 (1.0 GB) TX bytes:73325990 (73.3 MB)

eth2 Link encap:Ethernet HWaddr 00:25:11:73:89:75
inet addr:192.168.0.102 Bcast:192.168.0.0 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:26 Base address:0xe000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:542 errors:0 dropped:0 overruns:0 frame:0
TX packets:542 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:56456 (56.4 KB) TX bytes:56456 (56.4 KB)

ra0 Link encap:Ethernet HWaddr 00:1a:ef:07:4b:4a
inet addr:192.168.2.102 Bcast:192.168.2.0 Mask:255.255.255.0
inet6 addr: fe80::21a:efff:fe07:4b4a/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:5416 errors:0 dropped:0 overruns:0 frame:0
TX packets:8712 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:599565 (599.5 KB) TX bytes:0 (0.0 B)
Interrupt:22

ifdown -v ra0 && ifup -v ra0:


Configuring interface ra0=ra0 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/clamav-freshclam-ifupdown
run-parts: executing /etc/network/if-down.d/openvpn
run-parts: executing /etc/network/if-down.d/upstart
run-parts: executing /etc/network/if-down.d/wpasupplicant

ifconfig ra0 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/bridge
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.ra0.pid
Stopped /sbin/wpa_supplicant (pid 31784).
wpa_supplicant: removing /lib/init/rw/sendsigs.omit.d/wpasupplicant.wpa_supplicant.ra0.pid
Configuring interface ra0=ra0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/bridge
run-parts: executing /etc/network/if-pre-up.d/ethtool
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -s -B -P /var/run/wpa_supplicant.ra0.pid -i ra0 -D wext -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: creating sendsigs omission pidfile: /lib/init/rw/sendsigs.omit.d/wpasupplicant.wpa_supplicant.ra0.pid
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/ra0
wpa_supplicant: wpa-ap-scan 1 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "las" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise TKIP CCMP -- OK
wpa_supplicant: wpa-group TKIP CCMP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto WPA RSN -- OK
wpa_supplicant: enabling network block 0 -- OK

ifconfig ra0 192.168.2.102 netmask 255.255.255.0 broadcast 192.168.2.0 up

run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/clamav-freshclam-ifupdown
run-parts: executing /etc/network/if-up.d/ethtool
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/openssh-server
run-parts: executing /etc/network/if-up.d/openvpn
run-parts: executing /etc/network/if-up.d/upstart
run-parts: executing /etc/network/if-up.d/wpasupplicant


Last, but not least-iwconfig:

lo no wireless extensions.

eth2 no wireless extensions.

ra0 RT2860 Wireless ESSID:"" Nickname:"RT2860STA"
Mode:Auto Frequency=2.437 GHz Bit Rate=1 Mb/s
RTS thr:off Fragment thr:off
Encryption key:off
Link Quality=10/100 Signal level:0 dBm Noise level:-87 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

eth1 no wireless extensions.


During the ifup command, you can even see where the system "successfully" assigns the essid and psk to the device. Am i missing a step somewhere or is my syntax just incorrect? Any help would be greatly appreciated :)

[gregkane]

I've been struggling to get a laptop working with ubunto 9.10 since last week. The install left me with no ip connectivity. The wired jack is either malfunctioning or my Gig switch and this laptop just can't auto negotiated to 100Mbs.

Anyway I've read a good bit of this thread and applied the recommended wpa config for WPA2. The only change is that "dmesg" tells me that my wlan1 interface is using the "arusb-xp" ndis driver.

when I restarted the network it tells me:
...wpa-supplicant /sbin/wpa_supplicant daemon failed to start run-parts /etc/network/if-pre-up.d/wpasupplicant exited with return code 1

iwconfig shows wlan1 active

ifconfig shows wlan1 OK and that is has the static IP I assigned

sudo iwlist scan shows wlan1 up and active on 2 bands

any ideas?

Thanks

[savyboy24]

Will the first page of this guide work for my linksys wpc45g ver 2 wireless card, on Ubuntu 8.04.4 Hardy, on a old dell latitude?

[boubbin]

Hello,

I managed to get this thing working.
I have one problem tho:
The icon next to my clock (nm-applet but in kubuntu) wont show the signal or any other information anymore. This also means that i cannot connect to any other wifi network besides the one spesified in interfaces file.

The only way to connect to internet is now via this interface i made

EDIT: I also found out that boot will take 10s longer cause of the dhcp request that is made to my router.

How to fix this ?

[wieman01]

EDIT: I also found out that boot will take 10s longer cause of the dhcp request that is made to my router.

How to fix this ?

You could use a static IP address instead.

[boubbin]

You could use a static IP address instead.
ok, thats not really a concern, but how bout when im outside of my home and i cant use the network applet to select another wifi network... that is my problem

[wieman01]

ok, thats not really a concern, but how bout when im outside of my home and i cant use the network applet to select another wifi network... that is my problem
Then I would not follow this approach, but only use the network applet. It is able to handle WPA security, you don't need this tutorial in fact.

[savyboy24]

Wieman any idea what I should do about not getting a WPA signal on my Dell laptop? http://ubuntuforums.org/showthread.php?t=1406854

[NFAD]

I'm new to Ubuntu, and I have been trying for 2 weeks to get an wireless internet connection and a private LAN connection working with iptables and MAC spoofing. I FINALLY got it working and I wanted to post my solution somewhere, so I decided here because this thread helped me the most.


Completely remove Network Manager or Wicd.


sudo aptitude remove network-manager
sudo aptitude purge network-manager

Follow the instructions in this post.
Broadcast and network are not needed.
IMPORTANT: Ensure your netmasks are different!!!
I am also using pre-up to load macchanger and iptables before any of the network settings are applied. Macchanger automatically spoofs my mac address before iptables is brought up. The order of the pre-up's are very important!


# loopback interface
auto lo
iface lo inet loopback

# Marvell
auto eth0
iface eth0 inet static
address 192.168.0.2
netmask 255.255.255.248

# D-link
auto wlan0
iface wlan0 inet static
address 10.0.0.11
netmask 255.255.255.0
gateway 10.0.0.1
wpa-driver wext
wpa-ssid BLAH
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk BLAH
pre-up macchanger -a wlan0
pre-up iptables-restore < /etc/iptables.rulesiptables: https://help.ubuntu.com/community/IptablesHowTo

macchanger: http://linux.die.net/man/1/macchanger

[derelict888]

Hey Wieman thanks for that howto, lots there and I've almost got myself setup. I've got a server (no gui) that I'm trying to move from wired to wireless networking (dont ask). I think I have it setup but wireless only works when wired is on and active. Here is my /etc/network/interfaces;

# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo

iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet static
address 192.168.1.11
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.1
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 192.168.1.1
dns-search [domain]

# WiFi Adapter
auto ath0
iface ath0 inet static
address 192.168.1.10
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.1
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 192.168.1.1
dns-search [domain]
wpa-driver madwifi
wpa-ssid Derelict
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk X.......this is correct.........X

I created a script to restart network when the server starts up, since I was having trouble with WiFi not starting up correctly. So here is iwconfig on my server;

iwconfig ath0
ath0 IEEE 802.11g ESSID:"Derelict" Nickname:""
Mode:Managed Frequency:2.437 GHz Access Point: 00:40:10:10:00:03
Bit Rate:24 Mb/s Tx-Power:18 dBm Sensitivity=1/1
Retry:off RTS thr:off Fragment thr:off
Encryption key:A2AA-4A9E-B452-E812-5F30-6D3E-46C4-32C8 Security mode:restricted
Power Management:off
Link Quality=51/70 Signal level=-45 dBm Noise level=-96 dBm
Rx invalid nwid:221457 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

So it looks like its working and I can see that MAC address on my router. However if I disconnect ethernet from my server, or if I comment out the eth0 section of my /etc/network/interfaces and restart the server, I get nothing. Any ideas? Here are the "stumped" troubleshooting results;

root@media-server:~# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
localnet * 255.255.255.0 U 0 0 0 eth0
localnet * 255.255.255.0 U 0 0 0 ath0
default 192.168.1.1 0.0.0.0 UG 100 0 0 ath0
default 192.168.1.1 0.0.0.0 UG 100 0 0 eth0
root@media-server:~# iwconfig
lo no wireless extensions.

eth1 no wireless extensions.

eth0 no wireless extensions.

wifi0 no wireless extensions.

ath0 IEEE 802.11g ESSID:"Derelict" Nickname:""
Mode:Managed Frequency:2.437 GHz Access Point: 00:40:10:10:00:03
Bit Rate:54 Mb/s Tx-Power:18 dBm Sensitivity=1/1
Retry:off RTS thr:off Fragment thr:off
Encryption key:**F3-**A0-**DA-**86-**15-**1F-**AB-**27 Security mode:restricted
Power Management:off
Link Quality=51/70 Signal level=-45 dBm Noise level=-96 dBm
Rx invalid nwid:222357 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

root@media-server:~# iwlist scan
lo Interface doesn't support scanning.

eth1 Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wifi0 Interface doesn't support scanning.

ath0 Scan completed :
Cell 01 - Address: **:**:**:**:AB:F2
ESSID:"Vesta"
Mode:Master
Frequency:2.462 GHz (Channel 11)
Quality=3/70 Signal level=-92 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK

Cell 03 - Address: 00:40:10:10:00:03
ESSID:"Derelict"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=50/70 Signal level=-45 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK

root@media-server:~# lshw -C network
*-network:0
description: Wireless interface
product: AR5212/AR5213 Multiprotocol MAC/baseband processor
vendor: Atheros Communications Inc.
physical id: 6
bus info: pci@0000:05:06.0
logical name: wifi0
version: 01
serial: **:**:**:**:2c:d4
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=ath_pci ip=192.168.1.10 latency=168 maxlatency=28 mingnt=10 module=ath_pci multicast=yes wireless=IEEE 802.11g
*-network:1 DISABLED
description: Ethernet interface
product: 88E8001 Gigabit Ethernet Controller
vendor: Marvell Technology Group Ltd.
physical id: c
bus info: pci@0000:05:0c.0
logical name: eth1
version: 13
serial: **:**:**:**:c1:67
capacity: 1GB/s
width: 32 bits
clock: 66MHz
capabilities: pm vpd bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=skge driverversion=1.13 firmware=N/A latency=32 link=no maxlatency=31 mingnt=23 module=skge multicast=yes port=twisted pair

I actually have 2 wired NICs, not sure why the other didn't show - 192.168.1.11 isn't showing. Oh well...

EDIT: I see that my driver from lshw shows ath_pci but I'm specifying madwifi, that the cause?

[derelict888]

Anyone? Bueler?

I changed the driver from madwifi to ath_pci but that didn't change anything.
:confused:

[derelict888]

Figured it out, I had to drop my eth0 routes. If anyone needs the syntax I used I can dig it up.

[padapada]

Just wanted to let you know that I finally have succes.

Network-manager is finally working for me:
- Lucid
- WPA2-PSK
- Intel 4965AGN

I could not work network-manager before, so managed=false in nm-system-settings.conf and
this in /etc/network/interfaces:
auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid <my-ssid>
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk <my-psk>

[prupert]

I wrote a little How To on my blog based on this guide, but for Lucid, since that is what many people are running now:

http://www.prupert.co.uk/2010/06/25/how-to-configure-wireless-wifi-networking-in-ubuntu-via-the-command-line-cli/ (http://www.prupert.co.uk/2010/06/25/how-to-configure-wireless-wifi-networking-in-ubuntu-via-the-command-line-cli/)

[BriarHood]

I am having similar issues. After entering


lspci -v | grep -i Network
sudo lshw -C network

This is what I have

*-network
description: Ethernet interface
product: NetXtreme BCM5751 Gigabit Ethernet PCI Express
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:02:00.0
logical name: eth0
version: 01
serial: 00:12:3f:1a:57:8e
size: 100MB/s
capacity: 1GB/s
width: 64 bits
clock: 33MHz
capabilities: pm vpd msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=tg3 driverversion=3.102 duplex=full firmware=5751-v3.29a ip=68.3.54.55 latency=0 link=yes multicast=yes port=twisted pair speed=100MB/s
resources: irq:16 memory:dfdf0000-dfdfffff
*-network
description: Instant Wireless Network PC Card
product: ISL37300P
vendor: The Linksys Group, Inc.
physical id: 0
version: RevA
slot: Socket 0
resources: irq:3
*-network
description: Wireless interface
physical id: 2
logical name: eth1
serial: 00:06:25:0b:80:9a
capabilities: ethernet physical wireless
configuration: broadcast=yes driver=orinoco driverversion=0.15 firmware=Intersil 1.4.2 link=no multicast=yes wireless=IEEE 802.11b

One light is solid, the other is blinking. Network manager recognizes it because wireless networks is accessible, but no networks show up, even when I know I am near them. I have no idea what to do and have tried almost everything I could find. Many reinstalls later, I'm stuck in the same position. Can anyone help?

[jarviser]

If that is a laptop with a PCMCIA Linksys Instant wifi card see here http://manpages.ubuntu.com/manpages/lucid/man4/if_wi.4freebsd.html

[iSpyCreativity]

Some users reported (including myself) that the network has to be restarted every time after startup... Apparently this is a bug.

Here is a workaround that helps restart the network during boot so that one does not have to do it manually after logging on to the system.

Create startup script:

Add this line & save file:

Change permission (executable):

Create symbolic link:

[Note: You may have to choose a boot sequence other than S40.]

Restart...

I'm new to all this Ubuntu malarkey, and followed these steps through curiosity but instead of auto connecting to a wifi connection like I'd hopes it attempts to but never succeeds; so I end up having to manually disconnect the attempt and then manually connect to the desired router. Could someone please walk me through back tracking these changes?

It would be greatly appreciated, thanks in advance.

[jarviser]

If you are referring to this...

Create startup script:
Quote:
sudo gedit /etc/init.d/wireless-network
Add this line & save file:
Quote:
/etc/init.d/networking restart
Change permission (executable):
Quote:
sudo chmod +x /etc/init.d/wireless-network
Create symbolic link:
Quote:
sudo ln -s /etc/init.d/wireless-network /etc/rcS.d/S40wireless-network
[Note: You may have to choose a boot sequence other than S40.]

Then firstly (if you are new to Linux) I would suggest not running scripts opr fixes that were written in 2006 - a lot has happened since then, including this being unnecessary in latest Ubuntu. WPA works out of the box in 9.xx and 10.04

Secondly you should have printed the whole thing as it was 180 pages ago and took some finding

Thirdly you need to remove the symbolic link by

sudo rm /etc/rcS.d/S40wireless-network

finally delete the extra line in the script you edited

sudo gedit /etc/init.d/wireless-network and delete the line . If it was the only line
then delete the whole script.

No guarantees this will work or is safe.

[wieman01]

Maybe we should really have this thread closed by the admins. Not sure if it's still relevant...

[wieman01]

Maybe we should really have this thread closed by the admins. Not sure if it's still relevant...

[iSpyCreativity]

If you are referring to this...

Create startup script:
Quote:
sudo gedit /etc/init.d/wireless-network
Add this line & save file:
Quote:
/etc/init.d/networking restart
Change permission (executable):
Quote:
sudo chmod +x /etc/init.d/wireless-network
Create symbolic link:
Quote:
sudo ln -s /etc/init.d/wireless-network /etc/rcS.d/S40wireless-network
[Note: You may have to choose a boot sequence other than S40.]

Then firstly (if you are new to Linux) I would suggest not running scripts opr fixes that were written in 2006 - a lot has happened since then, including this being unnecessary in latest Ubuntu. WPA works out of the box in 9.xx and 10.04

Secondly you should have printed the whole thing as it was 180 pages ago and took some finding

Thirdly you need to remove the symbolic link by

sudo rm /etc/rcS.d/S40wireless-network

finally delete the extra line in the script you edited

sudo gedit /etc/init.d/wireless-network and delete the line . If it was the only line
then delete the whole script.

No guarantees this will work or is safe.

Thanks for the tips ;)

[mrmylanman]

Hey all;

I am attempting to get my wireless interface to work on my laptop (seeing how far I can go without GUI!) and it isnt associating with the access point. Here is the output of the commands listed in the OP:

Note, the AP I am trying to connect to is "wireless".


Log of route
Sat Dec 4 08:25:50 2010

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth1
link-local * 255.255.0.0 U 1000 0 0 eth1
default 192.168.1.1 0.0.0.0 UG 100 0 0 eth1


Log of iwconfig
Sat Dec 4 08:26:26 2010

lo no wireless extensions.

eth0 no wireless extensions.

eth1 IEEE 802.11 Access Point: Not-Associated
Link Quality:5 Signal level:0 Noise level:166
Rx invalid nwid:0 invalid crypt:0 invalid misc:0


Log of sudo iwlist scan
Sat Dec 4 08:27:55 2010

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:22:75:B2:F1:1C
ESSID:"wireless"
Mode:Managed
Frequency:2.452 GHz (Channel 9)
Quality:5/5 Signal level:-30 dBm Noise level:-91 dBm
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : TKIP CCMP
Authentication Suites (1) : PSK
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : TKIP CCMP
Authentication Suites (1) : PSK
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 9 Mb/s
18 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 12 Mb/s
24 Mb/s; 48 Mb/s
Cell 02 - Address: 0C:D5:02:17:F9:0B
ESSID:"westell8057"
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:1/5 Signal level:-85 dBm Noise level:-83 dBm
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s


Log of sudo lshw -C network
Sat Dec 4 08:30:03 2010

*-network
description: Wireless interface
product: BCM4322 802.11a/b/g/n Wireless LAN Controller
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:02:00.0
logical name: eth1
version: 01
serial: 00:26:5e:81:61:68
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=wl0 driverversion=5.60.48.36 ip=192.168.1.195 latency=0 multicast=yes wireless=IEEE 802.11abgn
resources: irq:18 memory:f0200000-f0203fff
*-network DISABLED
description: Ethernet interface
product: RTL8101E/RTL8102E PCI Express Fast Ethernet controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:08:00.0
logical name: eth0
version: 02
serial: 00:21:cc:3b:f2:29
size: 10MB/s
capacity: 100MB/s
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix vpd bus_master cap_list rom ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half latency=0 link=yes multicast=yes port=MII speed=10MB/s
resources: irq:43 ioport:a000(size=256) memory:f0410000-f0410fff memory:f0400000-f040ffff memory:f0420000-f043ffff


auto lo
iface lo inet loopback

#auto eth0
#iface eth0 inet dhcp

auto eth1
iface eth1 inet static
address 192.168.1.195
gateway 192.168.1.1
dns-nameservers 8.8.8.8
netmask 255.255.255.0
wpa-driver wext
wpa-ssid wireless
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise TKIP CCMP
wpa-group TKIP CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 4d654660a791a199f0aaabb5a961f37e24507903e270ebd736 b50eb63e9e82ef


Log of sudo ifdown -v eth1
Sat Dec 4 08:30:52 2010

Configuring interface eth1=eth1 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/upstart
run-parts: executing /etc/network/if-down.d/wpasupplicant
route del default gw 192.168.1.1 metric 100 eth1
ifconfig eth1 down
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/avahi-daemon
run-parts: executing /etc/network/if-post-down.d/wireless-tools
run-parts: executing /etc/network/if-post-down.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile /var/run/wpa_supplicant.eth1.pid
Stopped /sbin/wpa_supplicant (pid 1991).
wpa_supplicant: removing /lib/init/rw/sendsigs.omit.d/wpasupplicant.wpa_supplicant.eth1.pid


Log of sudo ifup -v eth1
Sat Dec 4 08:31:01 2010

Configuring interface eth1=eth1 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -s -B -P /var/run/wpa_supplicant.eth1.pid -i eth1 -D wext -C /var/run/wpa_supplicant
wpa_supplicant: creating sendsigs omission pidfile: /lib/init/rw/sendsigs.omit.d/wpasupplicant.wpa_supplicant.eth1.pid
wpa_supplicant: ctrl_interface socket located at /var/run/wpa_supplicant/eth1
wpa_supplicant: wpa-ap-scan 1 -- OK
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "wireless" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: wpa-pairwise TKIP CCMP -- OK
wpa_supplicant: wpa-group TKIP CCMP -- OK
wpa_supplicant: wpa-key-mgmt WPA-PSK -- OK
wpa_supplicant: wpa-proto RSN -- OK
wpa_supplicant: enabling network block 0 -- OK

ifconfig eth1 192.168.1.195 netmask 255.255.255.0 up
route add default gw 192.168.1.1 metric 100 eth1
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/upstart
run-parts: executing /etc/network/if-up.d/wpasupplicant

Thanks so much I hope I can get this to work without relying on networkmanager (it works using that, btw. I removed it before doing this tutorial).

[mrmylanman]

Update I got it working! Thanks again for the walkthrough. I screwed up the WPA psk. I put the SSID and passphrase in backwards I think

[Gourmand]

Please help me. On my desktop runs WinXP Pro with D-Link DWA-125 USB WiFi dongle. It tethers Inet as Ad-Hoc with WPA2-PSK and AES. Android device connects well with these settings. But Linux on handheld cannot connect in Network Manager. I tried use your method. This is my /etc/network/interfaces file:



auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
address 192.168.0.3
gateway 10.64.202.150
dns-nameservers XXX.XXX.XXX.XXX XXX.XXX.XXX.XXX
netmask 255.255.255.0
wpa-driver wext
wpa-ssid <AP-name>
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk <longkey>


But when I try restart network I get error message from ifup:



* Reconfigyring network interfaces
ioctl[SI0CSIWPMKSA]:Invalid argument *1
ioctl[SI0CSIWPMKSA]:Invalid argument *1
SI0CADDRT: Network is unreachabe *2
Failed to bring up eth0 *2


I tried use DHCP instead of static IP - looks like Wi-Fi authentication passes well. I can see connected device MAC address in Wi-Fi list. *2 messages with DHCP didn't appear. But *1 messages appeared too. But Wi-Fi connection can't get dynamic IP (probably provider limitation). As I told Android device works well with static IP.

[Gourmand]

Hmmm... iwconfig tells:


eth0 MRVL-SD8686 ESSID:<SSID> [2]
Mode:Managed Frequency:2.412 GHz Access Point: <MAC>
Bit Rate:54 Mb/s
Encryption key:<too big> Security mode:open
^^^^^^^^^^^^^^^^^^^^^^^^
Power Management:on
Link Quality=100/100 Signal level=0 dBm Noise level=-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:105
Tx excessive retries:77 Invalid misc:234 Missed beacon:0

what's wrong with security key? I've got it following topic instructions... or it's just too big to show?

and why "Security mode: open"?

[Gourmand]

Then if I try DHCP:


auto eth0
#iface eth0 inet static
iface eth0 inet dhcp
#addresss 192.168.0.3
#gateway 10.64.202.150
#dns-nameservers <...>
#netmask 255.255.255.0
wpa-driver wext
wpa-ssid <...>
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk <...>


What happiness:



* Reconfiguring network interfaces... ioctl[SIOCSIWPMKSA]: Invalid argument
ioctl[SIOCSIWPMKSA]: Invalid argument
There is already a pid file /var/run/dhclient.eth0.pid with pid 18093
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.1.2
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:27:13:f0:25:2f
Sending on LPF/eth0/00:27:13:f0:25:2f
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 1
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

[314ttus]

@weiman01,

...
auto wlan0
iface wlan0 inet static
wpa-driver wext (tried ndiswrapper also)
wpa-conf managed
wpa-ssid <my_essid>
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk <my_64_hex_key>
address 192.168.168.40
netmask 255.255.255.0
network 192.168.168.0
broadcast 192.168.168.255
gateway 192.168.168.230
dns-nameservers 192.168.168.230

...
/etc/init.d/network restart
...

squibt

Perfect! Thank you so much! Straight forward and simply working!
Peter

[tioneb]

Some users reported (including myself) that the network has to be restarted every time after startup... Apparently this is a bug.

Here is a workaround that helps restart the network during boot so that one does not have to do it manually after logging on to the system.

Create startup script:

Add this line & save file:

Change permission (executable):

Create symbolic link:

[Note: You may have to choose a boot sequence other than S40.]

Restart...



Hey all,

Thanks to this great HOW-TO the wireless network is operational.
Nevertheless I'm struggling with the boot sequence.

It works at boot up if I stop the server with
init 0
It doesn't if I restart with
init 6

I created a link in /etc/rcS.d/S90**** to restart the networking

I'm with the server version 11.4

Thanks for any help

[needDrivers]

Simple WLAN configuration script
http://hencvik.googlecode.com/files/wlan-config.sh


$ wget http://hencvik.googlecode.com/files/wlan-config.sh
$ chmod a+rx wlan-config.sh
$ sudo ./wlan-config.sh

[tech_ninja]

After following your instructions to the letter, I've successfully enabled a wifi connection with wpa2 aes on my box running ubuntu server 11.10. Thanks

[wieman01]

After following your instructions to the letter, I've successfully enabled a wifi connection with wpa2 aes on my box running ubuntu server 11.10. Thanks
Wow, I am amazed the tutorial still does the job after so many years. Oh well, I got more gray hair, but WPA2 is still the same.

[sgtzim]

All right, this is driving me batty.

I have a dual-boot Ubuntu, 11.10 desktop and 11.10 server. The desktop connects to my WAP with no trouble, but I can't get the server to connect.

I'm broadcasting my essid and using wpa2 personal with psk

interfaces looks like this:
auto wlan0
iface wlan0 inet static
address 192.168.1.6
netmask 255.255.255.0
gateway 192.168.1.1
network 192.168.1.0
broadcast 192.168.1.255
wpa-driver wext
wpa-ssid NETWORKNAME
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk *64 bit hex number*


iwconfig returns this:
wlan0 802.11b/g link ESSID: "NETWORKNAME"
Mode: managed frequency 2.463 GHz Access Point: (it's the right MAC address)
Bit Rate=54 Mb/s
Retry: on RTS thr: off Fragment thr: off
Encryption key: off
Power Management: off
Link Quality = 73/100 Signal level= -44 dBm Noise level= -102 dBm
Rx invalid nwid: 0 Rx invalid crypt: 0 Rx invalid frag: 0
Tx excessive retries: 0 Invalid misc: 0 Missed beacon: 0


So....I'm seeing the WAP from the server, I'm just not connecting. I've triple-checked the PSK.

I'm sure the solution is posted somewhere within the 182 pages of this thread, but I can't find it.

I have noticed something odd, though. ifup/ifdown wlan0 don't work, but ifconfig wlan0 up/down do work.

Thanks in advance

[wieman01]

iwconfig returns this:
wlan0 802.11b/g link ESSID: "NETWORKNAME"
Mode: managed frequency 2.463 GHz Access Point: (it's the right MAC address)
Bit Rate=54 Mb/s
Retry: on RTS thr: off Fragment thr: off
Encryption key: off
Power Management: off
Link Quality = 73/100 Signal level= -44 dBm Noise level= -102 dBm
Rx invalid nwid: 0 Rx invalid crypt: 0 Rx invalid frag: 0
Tx excessive retries: 0 Invalid misc: 0 Missed beacon: 0
Silly question... Have you turned on WPA at all? This says security is off. So this script isn't really useful under those circumstances.

What does "sudo iwlist scan" return?

[sgtzim]

Silly question... Have you turned on WPA at all? This says security is off. So this script isn't really useful under those circumstances.

What does "sudo iwlist scan" return?

Not such a silly question. I didn't know you had to. I'm a MS net admin and Linux is brand-spanking new to me. The thing that's really frying my bacon is that wlan0 works on the desktop side, but not on server side. The only thing I'm doing differently on the desktop side is using bootp instead of static.

It returns every WAP in the neighborhood, including mine.

Cell 01 - Address: MAC is correct
essid: NETWORKNAME
Protocol: 802.11bg
Mode: Master
Channel: 11
Encryption Key: on
Bit Rates: 54mbps
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher: CCMP
Pairwise Ciphers (1): CCMP
Authentication Suites (1): PSK


***************
edit:
now it's only finding my WAP on iwlist scan. I was getting returns on about 7 or 8 different WAPs yesterday

something else that's kind of strange to me. iwconfig under my normal account doesn't give any indication as to the Encryption, but when I run iwconfig as root, it shows encryption as off

[wieman01]

Perhaps you can post some more stuff, you find the relevant commands under section "Post this if you are stumped". Not entirely sure what is going on at this point.

[sgtzim]

Perhaps you can post some more stuff, you find the relevant commands under section "Post this if you are stumped". Not entirely sure what is going on at this point.

Is there something I need to do with wpa_supplicant? I've left it and all of its shell scripts just as they were right out of the box.

As I said, I'm a total noob with Linux. Knowing that, what other stuff would be helpful for me to post?

[kevdog]

Thought this thread was dead!!! What a revival!! I'm impressed!

[sgtzim]

I finally figured out the problem. I have an eth0 set in my interfaces file, and whenever I tried to ping my server or ping from my server, the attempted connections were always made through the eth0 NIC which, of course, wasn't connected to anything.

I deleted the eth0 portion of interfaces, and now everything works. :P

[wieman01]

Thought this thread was dead!!! What a revival!! I'm impressed!
Man, I could not believe it either. Lol. :-)

[sgtzim]

Now the question becomes...

How do I force the "first look" to be at wlan0 instead of eth0 when resolving IP/DNS names?

This is a development server on a laptop, and I split time between my house and my fiance's house. When I'm at home, I'm running two subnets, but when I'm here, it's just too much of a PITA to use ethernet. So when I don't have ethernet cable hooked up, I only want responses through wlan0. Am I just going to have to have 2 copies of interfaces, or is there a config file someplace where I can force first look to wlan0, or "if eth0 fails then ask wlan0"?

I'd think that there has to be because winblows does it automatically, and if winblows has it, surely Linux has it better. Not to mention the fact that Ubuntu desktop does it, too.

Something else that is strange to me is that when I'm connected to my network via ethernet cable, I could ping both the eth0 and the wlan0.

[mihirshah]

hello sir i followed ur settng for WPA2 DHCP and have done all the properly to my knowledge..
The output of iwconfig is:
wlan0 IEEE 802.11abgn ESSID:"dlink"
Mode:Managed Frequency:2.437 GHz Access Point: 00:24:01:BA:57:0B
Bit Rate=54 Mb/s Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:on
Link Quality=50/70 Signal level=-60 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
my dmesg o/p is :
ubuntu@omap:/etc/init.d$ dmesg | tail
[ 3119.295043] wlan0: associated
[ 3122.320373] wlan0: deauthenticated from 00:24:01:ba:57:0b (Reason: 2)
[ 3122.448577] cfg80211: All devices are disconnected, going to restore regulatory settings
[ 3122.448608] cfg80211: Restoring regulatory settings
[ 3122.448638] cfg80211: Calling CRDA to update world regulatory domain
[ 3124.344268] wlan0: authenticate with 00:24:01:ba:57:0b (try 1)
[ 3124.347076] wlan0: authenticated
[ 3124.376068] wlan0: associate with 00:24:01:ba:57:0b (try 1)
[ 3124.379913] wlan0: RX AssocResp from 00:24:01:ba:57:0b (capab=0x431 status=0 aid=2)
[ 3124.379943] wlan0: associated

my interace file is
auto lo
iface lo inet loopback
auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid dlink
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxx

i am putting these setting on my pandaboard es having ubuntu 11.10 .
sometimes i get this error message automaticcaly :
wl1271: ERROR invalid hlid. dropping skb
(confused)
please help!!!

[Adrian98]

WIreless Security is always been one of the main issues with us and this issue becomes more complicated for the newbies, Thanks for the guide of the wireless security!! WPA 2 , is always been my main concerned one to think about!!

[moose4204l]

i too am also trying to get the wireless working on my ubuntu server.

i followed you beginning tutorial and i am still not connecting.

iwconfig shows the ESSID

however, when i enter in

/etc/init.d/networking restart

i get the following message



wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1


I know the wireless works because I was using it when I had the machine running the Ubuntu Desktop.

I am also using WPA and TKIP with the static addressing.

any ideas why?

[kevdog]

@moose4204

Please share your configuration file so we can take a look at it

[vinaobraga]

Hello Guys.

I'm trying to configure my wireless connection on my server but something weird is happening.
I have two cards on my server, one wired and another one wireless.
After set up all the setting of wpa_supplicant and execute the commands to connect, the wlan0 network get IP and connected on my AP.
But, when I log into my AP and ask to list all attached devices, I see the wlan0 card connected with the same MAC Address from the wired card. And if I unplug the network cabe from eth0, both connections goes down.

I will sent the steps that I followed with my configuration files to see if you can help me, please.

root@server:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:08:54:21:27:1f
inet addr:192.168.1.9 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::208:54ff:fe21:271f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1116 errors:0 dropped:0 overruns:0 frame:0
TX packets:517 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:106880 (106.8 KB) TX bytes:80933 (80.9 KB)
Interrupt:19 Base address:0x2c00

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:16 errors:0 dropped:0 overruns:0 frame:0
TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1524 (1.5 KB) TX bytes:1524 (1.5 KB)

wlan0 Link encap:Ethernet HWaddr 00:06:4f:70:f8:c8
inet addr:192.168.1.10 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::206:4fff:fe70:f8c8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:130 errors:0 dropped:0 overruns:0 frame:0
TX packets:122 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:19857 (19.8 KB) TX bytes:21919 (21.9 KB)

root@server:~#

Follow the steps:

ifconfig wlan0 up
ifconfig
wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
ifconfig
ps aux | grep [w]pa
iwconfig wlan0
dhclient wlan0

root@server:~# cat /etc/wpa_supplicant/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
network={
ssid="AP-NOVO"
scan_ssid=1
proto=WPA
key_mgmt=WPA-PSK
#psk="H3l0m0t0"
psk=11b00480d2b7b625fe893385ff627f55780afb3348f91a 6685d9b5000c1fa0f9
}
root@server:~#

root@server:~# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet dhcp

#wireless
auto wlan0
iface wlan0 inet dhcp


Follow the output of the attached devices from router:

3 192.168.1.9 SERVER 00:08:54:21:27:1F
4 192.168.1.10 SERVER 00:08:54:21:27:1F

if you can see, the MAC is the same of the eth0.

What is wrong? I want to use only the wireless card..is it possible, right?

I'm running ubutu 12.04.

Thanks in advanced by any help.

[Rolandmaffia]

Hi!

I have only CLI access to a machine, I want to config to connect to a Hidden SSID AP, but it can't. It works with SSID boardcast.

The config (/etc/network/interfaces):


auto wlan0
iface wlan0 inet dhcp
wpa-ssid <name>
wpa-psk <hex>

It works with SSID boardcast. If I hide SSID, and add this line, it don't want to work.

wpa-ap-scan 2

What else must I add to work?

Thank you!

UPDATE: I've found a solution here (http://unix.stackexchange.com/questions/48431/connect-to-hidden-wifi-ap-with-wpa-supplicant).

[wieman01]

I know this might not be a satisfying answer, but hiding the SSID adds no extra security. You might want to broadcast it and take the path of least resistance. :-)

[MrScience101]

:popcorn:Thank you so much. I spent all day trying to get the wireless working on my acer aspire one (the mini kind) with ubuntu 12.04.1 web server. With this guide I was able to do it. Very helpful. Like the Chinese character too.

[wieman01]

You're welcome. I am amazed this still works after so many year. Rock on!

[mbboots]

I followed the steps on the first page of this thread, but ran into problems.

Below are the output from the "Follow if you're stumped" section

# route

Kernel IP routing tableDestination Gateway Genmask Flags Metric Ref Use Iface
default 192.168.1.1 0.0.0.0 UG 100 0 0 eth0
link-local * 255.255.0.0 U 1000 0 0 eth0
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
192.168.1.0 * 255.255.255.0 U 0 0 0 wlan0

# iwconfig

wlan0 IEEE 802.11bg ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off


# sudo iwlist scan

wlan0 Scan completed : Cell 01 - Address: 00:7F:28:23:D9:B3
Channel:11
Frequency:2.462 GHz (Channel 11)
Quality=55/70 Signal level=-55 dBm
Encryption key:on
ESSID:"VPCC5"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s
Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
Mode:Master
Extra:tsf=0000000b93772ab2
Extra: Last beacon: 440ms ago
IE: Unknown: 00055650434335
IE: Unknown: 010882848B960C121824
IE: Unknown: 03010B
IE: Unknown: 200100
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
IE: Unknown: 2A0100
IE: Unknown: 32043048606C
IE: Unknown: DD180050F2020101040003A4000027A4000042435E0062322F 00
IE: Unknown: 2D1A8C131BFFFF000000000000000000000000000000000000 000000
IE: Unknown: 3D160B001B00000000000000000000000000000000000000
IE: Unknown: DD0900037F01010000FF7F
IE: Unknown: DD0A00037F04010000000000
IE: Unknown: 0706555320010B1B
Cell 02 - Address: 2C:B0:5D:DC:1D:AC
Channel:11
Frequency:2.462 GHz (Channel 11)
Quality=30/70 Signal level=-80 dBm
Encryption key:on
ESSID:"Clark"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s
Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
Mode:Master
Extra:tsf=0000000000000000
Extra: Last beacon: 444ms ago
IE: Unknown: 0005436C61726B
IE: Unknown: 010882848B962430486C
IE: Unknown: 03010B
IE: Unknown: 2A0100
IE: Unknown: 2F0100
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: Unknown: 32040C121860
IE: Unknown: 2D1A7C181BFFFF000000000000000000000000000000000000 000000
IE: Unknown: 3D160B081100000000000000000000000000000000000000
IE: Unknown: DD760050F204104A0001101044000102103B00010310470010 340F266D809B77AB54465617608B1C06102100074E65746765 6172102300074E657467656172102400063132333435361042 0007303030303030311054000800060050F204000110110009 4E6574676561724150100800020088103C000101
IE: Unknown: DD090010180200F00C0000
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F 00


# sudo lshw -C network

*-network description: Wireless interface
product: RT2500 Wireless 802.11bg
vendor: Ralink corp.
physical id: 8
bus info: pci@0000:01:08.0
logical name: wlan0
version: 01
serial: 00:16:b6:57:47:81
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=rt2500pci driverversion=3.2.0-34-generic firmware=N/A ip=192.168.1.23 latency=32 link=no multicast=yes wireless=IEEE 802.11bg

resources: irq:16 memory:fdffe000-fdffffff

# sudo cat /etc/network/interfaces

auto loiface lo inet loopback


auto eth0
iface eth0 inet static
address 192.168.1.2
netmask 255.255.255.0
gateway 192.168.1.1


auto wlan0
iface wlan0 inet static
address 192.168.1.23
gateway 192.168.1.1
netmask 255.255.255.0
wpa-driver wext
wpa-ssid VPCC5
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk WPA-PSKHEX

# sudo ifdown -v <your_interface>

ifdown: interface wlan0 not configured

# sudo ifup -v <your_interface>

Failed to bring up wlan0.supplicant -s -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -D wext -C /var/run/wpa_supplicant
Configuring interface wlan0=wlan0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Invalid argument
wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1
ip addr add 192.168.1.23/255.255.255.0 broadcast + dev wlan0 label wlan0

RTNETLINK answers: File exists

[jerrylamos]

Raring Ringtail on every boot (with U+1 I do a lot of boots) does not automatically connect to WPA wireless.

Raring invariably lways "disconnects" on boot. Systems Settings Network says "out of range" obviously tried to connect without the encryption key it already has. Manually select drop down window, shows the correct network, select it, and after a while presents a drop down with all the required info, and waits for me to select it. I do, and after a while it connects. Syslog has some network manager messages about "secrets required" and is oblivious to the "secrets" network manager already has.

Pangolin on the same pc and netowrk connects autmatically, might take a couple seconds. Raring doesn't connect, as a matter of Network Manager policy.

Android tablets on the same network (7" and 10.1") set up encryption once and they connect immediately. Every time. Raring doesn't.

Chromebook boots, zooms up, connects, and bam into the internet. Once encryption is set up always boots right up, using the info, no manual intervention required.

Launchpad bug#1097002. Apparently not considered a bug, just the way Ubuntu Raring network manager has decided to slow down boot.

[AvocadoRed]

Hey,

Not to bring an old thread back to life, but just wanted to say thanks to wieman01 & the many others in this thread. After much hair pulling, I'm up and running in Ubuntu 13.04 using WPA2!

One question though - I've only updated the /etc/network/interfaces file, and when I boot up, wireless is automatically connected (not complaining :) ). Throughout the thread I've seen mentions to a configuration in order to have the wireless connect at boot. Is there something that has changed over the releases to make this automatically happen, or have I done something unknowingly to make this happen?

Should anyone be interested, I've included my configurations below. Note: I uninstalled network manager after struggling for many days. I found that I wasn't finding my network name in the iwlist scan results. Once I removed network manager, my network name popped up. No idea if it is relevant, but just thought I'd throw it out there. I also tried running the 'wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -dd' command with no success. Would be interested if anyone could fill me in on why this command doesn't work, but simply configuring the /etc/network/interfaces file does.


# lspci -nnvv



02:0a.0 Network controller [0280]: Atheros Communications Inc. AR922X Wireless Network Adapter [168c:0029] (rev 01)
Subsystem: D-Link System Inc DWA-552 802.11n Xtreme N Desktop Adapter (rev A2) [1186:3a7a]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 168, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 18
Region 0: Memory at cfee0000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=100mA PME(D0+,D1-,D2-,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: ath9k



# lshw -C network



*-network description: Wireless interface
product: AR922X Wireless Network Adapter
vendor: Atheros Communications Inc.
physical id: a
bus info: pci@0000:02:0a.0
logical name: wlan0
version: 01
serial: 00:18:e7:d5:b5:6e
width: 32 bits
clock: 66MHz
capabilities: bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ath9k driverversion=3.8.0-29-generic firmware=N/A ip=192.168.0.50 latency=168 link=yes multicast=yes wireless=IEEE 802.11bgn
resources: irq:18 memory:cfee0000-cfeeffff



# /etc/network/interfaces



# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).


# The loopback network interface
auto lo
iface lo inet loopback


auto wlan0
iface wlan0 inet static
address 192.168.0.50
gateway 192.168.0.1
dns-nameservers 8.8.8.8 192.168.0.1
netmask 255.255.255.0
wpa-driver wext
wpa-ssid office
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 648376b573d37212568631ca58cedfb5f9d6027e268131e5de 4cb90d166ab76b


Cheers!

[wieman01]

Thank you for the feedback, AvocadoRed! I am thrilled to see this still works after so many years.

Perhaps something has changed over the years in terms of wireless connection at boot, I am not entirely sure. But I noticed this as well, I no longer need the scripts mentioned in post 2.

And thanks for posting the contents of your configuration files for reference!