PDA

View Full Version : HOWTO: Wireless Security - WPA1, WPA2, LEAP, etc.


Pages : 1 2 [3] 4 5 6 7 8

wieman01
May 25th, 2007, 02:36 PM
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
May 25th, 2007, 06:51 PM
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
May 26th, 2007, 04:50 AM
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
May 26th, 2007, 09:11 AM
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
May 26th, 2007, 10:31 AM
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
May 26th, 2007, 10:37 AM
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
May 26th, 2007, 06:01 PM
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
May 27th, 2007, 03:27 AM
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
May 28th, 2007, 12:18 AM
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
May 28th, 2007, 04:40 AM
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
May 28th, 2007, 06:48 AM
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
May 28th, 2007, 09:43 AM
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
May 28th, 2007, 07:14 PM
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
May 28th, 2007, 11:31 PM
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
May 29th, 2007, 02:13 AM
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
May 29th, 2007, 02:15 AM
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
May 29th, 2007, 02:22 AM
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
May 29th, 2007, 02:30 AM
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
May 29th, 2007, 03:10 AM
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
May 29th, 2007, 03:22 AM
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
May 29th, 2007, 03:47 PM
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
May 29th, 2007, 05:32 PM
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
May 29th, 2007, 05:37 PM
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
May 30th, 2007, 02:19 AM
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
May 30th, 2007, 02:27 AM
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
May 30th, 2007, 10:57 AM
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
May 30th, 2007, 11:04 AM
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
May 30th, 2007, 12:09 PM
>> 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
May 30th, 2007, 01:24 PM
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
May 30th, 2007, 01:37 PM
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
May 30th, 2007, 02:11 PM
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
May 30th, 2007, 02:25 PM
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
May 30th, 2007, 08:04 PM
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
May 30th, 2007, 09:34 PM
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
May 31st, 2007, 02:26 AM
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
May 31st, 2007, 02:28 AM
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
May 31st, 2007, 09:15 AM
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
May 31st, 2007, 09:19 AM
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
May 31st, 2007, 11:37 AM
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
May 31st, 2007, 11:47 AM
@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
May 31st, 2007, 12:06 PM
@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
May 31st, 2007, 04:53 PM
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
May 31st, 2007, 06:46 PM
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
May 31st, 2007, 10:49 PM
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
June 1st, 2007, 02:28 AM
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
June 1st, 2007, 02:32 AM
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
June 1st, 2007, 12:07 PM
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
June 1st, 2007, 12:35 PM
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
June 1st, 2007, 01:29 PM
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
June 1st, 2007, 08:37 PM
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
June 2nd, 2007, 03:31 AM
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
June 2nd, 2007, 04:23 AM
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
June 2nd, 2007, 04:25 AM
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
June 2nd, 2007, 06:45 AM
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
June 2nd, 2007, 09:52 AM
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
June 2nd, 2007, 01:55 PM
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
June 4th, 2007, 08:26 AM
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
June 4th, 2007, 08:41 AM
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
June 4th, 2007, 08:50 AM
Yes, I tried that, no luck. :-(

wieman01
June 4th, 2007, 08:57 AM
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
June 4th, 2007, 09:00 AM
I am at work currently. I will try your suggestions when I get home and post the results.

wieman01
June 4th, 2007, 09:02 AM
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
June 4th, 2007, 01:38 PM
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
June 4th, 2007, 02:42 PM
any idea if the .cer file can be use for PEAP?

frkstein
June 4th, 2007, 08:19 PM
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
June 5th, 2007, 02:26 AM
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
June 5th, 2007, 02:30 AM
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
June 5th, 2007, 02:35 AM
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
June 5th, 2007, 10:13 AM
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
June 5th, 2007, 10:16 AM
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
June 5th, 2007, 01:49 PM
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
June 5th, 2007, 03:23 PM
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
June 5th, 2007, 04:47 PM
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
June 5th, 2007, 08:13 PM
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
June 5th, 2007, 08:47 PM
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
June 6th, 2007, 02:19 AM
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
June 6th, 2007, 02:25 AM
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
June 6th, 2007, 02:27 AM
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
June 6th, 2007, 09:09 AM
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
June 6th, 2007, 09:13 AM
Would you like to see the results of iwlist scan before or after I bring the network up after a reboot?

wieman01
June 6th, 2007, 10:03 AM
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
June 6th, 2007, 10:04 AM
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
June 6th, 2007, 09:05 PM
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
June 7th, 2007, 06:12 AM
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
June 7th, 2007, 10:57 AM
"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
June 8th, 2007, 02:44 AM
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
June 8th, 2007, 03:09 PM
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
June 9th, 2007, 02:19 AM
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
June 9th, 2007, 01:01 PM
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
June 9th, 2007, 01:04 PM
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
June 9th, 2007, 01:12 PM
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
June 9th, 2007, 04:08 PM
@ 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
June 10th, 2007, 03:09 PM
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
June 11th, 2007, 07:08 AM
@ 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
June 11th, 2007, 07:12 AM
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
June 11th, 2007, 02:13 PM
@ 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
June 11th, 2007, 04:03 PM
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
June 12th, 2007, 02:53 AM
@ 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
June 12th, 2007, 02:59 AM
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
June 12th, 2007, 05:52 AM
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
June 12th, 2007, 07:10 AM
@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
June 12th, 2007, 01:06 PM
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
June 13th, 2007, 02:38 AM
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
June 13th, 2007, 05:32 AM
That's fine, I'll swap to ndiswrapper - just point me in the right direction, would you please?

wieman01
June 13th, 2007, 05:43 AM
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
June 13th, 2007, 05:52 AM
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
June 13th, 2007, 06:01 AM
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
June 13th, 2007, 10:30 AM
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
June 13th, 2007, 10:48 AM
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
June 13th, 2007, 03:15 PM
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
June 14th, 2007, 01:14 AM
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
June 14th, 2007, 10:02 AM
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
June 14th, 2007, 10:20 AM
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
June 14th, 2007, 10:24 AM
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
June 14th, 2007, 10:43 AM
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
June 14th, 2007, 10:49 AM
@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
June 14th, 2007, 10:53 AM
well how do i uninstall it ? ive already killed it with 'killall NetworkManager'

clegg13
June 14th, 2007, 10:55 AM
oh and no, im not running firestarter or any other firewall.

wieman01
June 14th, 2007, 11:01 AM
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
June 14th, 2007, 11:03 AM
yes i do the ifup and ifdown while network cable is removed.

wieman01
June 14th, 2007, 11:08 AM
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
June 14th, 2007, 11:13 AM
also i cannot seem to get rid of that PID thing, any ideas ?

clegg13
June 14th, 2007, 11:14 AM
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
June 14th, 2007, 11:22 AM
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
June 14th, 2007, 11:27 AM
i was able to remove network manager completely. so now gonna resatrt and see maybe that PID isnt locked up anymore.

clegg13
June 14th, 2007, 11:35 AM
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
June 14th, 2007, 12:45 PM
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
June 14th, 2007, 01:58 PM
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
June 14th, 2007, 02:01 PM
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
June 14th, 2007, 02:08 PM
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
June 14th, 2007, 03:24 PM
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
June 15th, 2007, 02:22 AM
@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
June 15th, 2007, 05:09 AM
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
June 15th, 2007, 06:34 AM
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
June 15th, 2007, 07:12 AM
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
June 15th, 2007, 09:43 AM
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
June 15th, 2007, 06:44 PM
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
June 16th, 2007, 06:07 PM
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
June 17th, 2007, 06:40 AM
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
June 17th, 2007, 09:57 AM
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
June 17th, 2007, 11:18 AM
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
June 17th, 2007, 11:20 AM
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
June 17th, 2007, 11:25 AM
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
June 17th, 2007, 11:29 AM
route gives this

needless to say, it foesnt ping the router.
Quick question... do you know what "vmnet1" and "vmnet8" is?

clegg13
June 17th, 2007, 11:31 AM
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
June 17th, 2007, 11:33 AM
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
June 17th, 2007, 12:53 PM
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
June 19th, 2007, 10:26 PM
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
June 20th, 2007, 02:23 AM
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
June 20th, 2007, 06:07 PM
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
June 21st, 2007, 02:18 AM
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
June 22nd, 2007, 05:51 PM
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
June 22nd, 2007, 08:06 PM
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
June 23rd, 2007, 10:35 AM
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
June 23rd, 2007, 12:42 PM
@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
June 23rd, 2007, 04:18 PM
Thanks, it worked

mahasmb
June 25th, 2007, 12:53 PM
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
June 25th, 2007, 07:22 PM
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
June 26th, 2007, 09:55 AM
Thanks! I finally got my IPN2220 working thanks to this guide.

wieman01
June 26th, 2007, 10:36 AM
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
June 26th, 2007, 12:40 PM
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
June 26th, 2007, 03:49 PM
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
June 26th, 2007, 04:03 PM
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
June 27th, 2007, 02:38 AM
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
June 27th, 2007, 02:39 AM
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
June 27th, 2007, 05:29 PM
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
June 28th, 2007, 11:05 AM
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
June 28th, 2007, 03:43 PM
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
June 28th, 2007, 03:44 PM
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
June 28th, 2007, 09:40 PM
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
June 28th, 2007, 10:18 PM
Good grief. That's an RTL8187 and my interfaces file.

Sorry.

weinju
June 28th, 2007, 11:49 PM
@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
June 29th, 2007, 01:19 AM
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
June 29th, 2007, 01:21 AM
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
June 29th, 2007, 07:33 AM
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
June 29th, 2007, 02:11 PM
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
June 29th, 2007, 03:58 PM
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
June 29th, 2007, 03:58 PM
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
June 29th, 2007, 07:26 PM
"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
June 29th, 2007, 09:19 PM
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
June 30th, 2007, 02:53 AM
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
June 30th, 2007, 11:19 AM
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
July 1st, 2007, 09:16 AM
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
July 2nd, 2007, 06:32 PM
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
July 3rd, 2007, 11:04 AM
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
July 3rd, 2007, 06:50 PM
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
July 3rd, 2007, 08:38 PM
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
July 5th, 2007, 09:46 PM
Just a short note that this posting is awesome and should be a friggin' sticky in GOOGLE.

Thanks for the HowTo!!!

rq

max_croft
July 6th, 2007, 08:59 AM
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
July 6th, 2007, 05:29 PM
what does your wpa_supplicant file look like?

John Wiersba
July 8th, 2007, 12:46 AM
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
July 9th, 2007, 03:33 AM
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
July 9th, 2007, 10:38 AM
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
July 10th, 2007, 06:12 AM
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
July 17th, 2007, 02:11 AM
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
July 18th, 2007, 04:11 PM
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
July 18th, 2007, 07:02 PM
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
July 20th, 2007, 11:11 PM
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
July 23rd, 2007, 12:14 AM
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
July 24th, 2007, 01:01 PM
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
July 24th, 2007, 04:14 PM
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
July 24th, 2007, 04:30 PM
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
July 24th, 2007, 04:36 PM
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
July 24th, 2007, 04:57 PM
@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
July 24th, 2007, 05:15 PM
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
July 25th, 2007, 02:23 AM
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
July 25th, 2007, 09:19 PM
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
July 26th, 2007, 02:14 AM
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
July 30th, 2007, 10:14 PM
I just came here to say thank you very much.

celloyd
July 31st, 2007, 12:24 AM
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
July 31st, 2007, 02:14 AM
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
August 1st, 2007, 12:22 AM
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
August 1st, 2007, 02:30 AM
@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
August 1st, 2007, 10:25 AM
@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
August 2nd, 2007, 02:21 AM
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
August 2nd, 2007, 01:55 PM
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
August 3rd, 2007, 04:35 AM
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
August 3rd, 2007, 10:19 AM
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
August 3rd, 2007, 11:48 AM
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
August 4th, 2007, 09:41 PM
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
August 5th, 2007, 05:05 AM
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
August 5th, 2007, 01:37 PM
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
August 6th, 2007, 09:01 AM
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
August 6th, 2007, 09:51 AM
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
August 10th, 2007, 03:26 AM
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
August 10th, 2007, 05:38 AM
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
August 11th, 2007, 12:32 AM
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
August 11th, 2007, 05:13 AM
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
August 12th, 2007, 04:30 AM
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
August 12th, 2007, 10:41 AM
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
August 13th, 2007, 03:05 AM
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
August 13th, 2007, 03:24 AM
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
August 13th, 2007, 02:29 PM
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
August 13th, 2007, 03:19 PM
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
August 13th, 2007, 09:38 PM
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
August 14th, 2007, 02:26 AM
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
August 14th, 2007, 02:27 AM
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
August 14th, 2007, 02:36 AM
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
August 14th, 2007, 03:11 AM
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
August 14th, 2007, 03:15 AM
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
August 14th, 2007, 04:23 AM
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
August 14th, 2007, 04:28 AM
:-) 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
August 14th, 2007, 07:57 AM
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
August 14th, 2007, 08:00 AM
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
August 14th, 2007, 05:26 PM
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
August 15th, 2007, 12:03 AM
Can someone point me towards some drivers for RTL8180L that actually supports WPA?

wieman01
August 15th, 2007, 02:21 AM
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
August 15th, 2007, 07:16 PM
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
August 16th, 2007, 02:14 AM
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
August 16th, 2007, 12:56 PM
Any good cardbus cards?