Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have a funny issue. I set my wireless information using "NetworkManager", but I cannot set my wireless information using the command console. I'm testing it on a wireless network that has no WEP, just the basics (ESSID: lynksys).
When I type in this command (as root), it gives me this result:
Code:
linux-fergatron:/home/marc # iwconfig wlan0 essid linksys
Error for wireless request "Set ESSID* (8B1A) :
SET failed on device wlan0 ; Operation not supported.
I read somewhere that I can find out the information on my NIC by using the "lspci" command. His example resulted in about 2 to 3 lines, but mine is a bit more and at this point, it's all chinese, to me.:
All and all, a very funny situation because I can, again, connect using the Network wizard (set to use ifup), but I can't do anything manually. Thanks again for any help.
make sure you don't have an instance of network manager running as well. The "notrailers" is something I haven't seen before.. take the card down (ifconfig wlan0 down) make sure NM isn't running (check with ps) and bring it back up again and try.
Distribution: openSUSE 10->11.2, fedora 8->11, CentOS 5+, et al
Posts: 6
Rep:
ad hoc mode...
some funny stuff going on with NetworkManager - I was having the exact same issue [openSUSE 11.0 however]
"service network restart" as root showed
wlan0 device: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
command 'iwconfig wlan0 nick host' returned
Error for wireless request "Set Nickname" (8B1C) :
SET failed on device wlan0 ; Operation not supported.
command 'iwconfig wlan0 essid id' returned
Error for wireless request "Set ESSID" (8B1A) :
SET failed on device wlan0 ; Input/output error.
switching out of "ad hoc" and using managed mode in the yast Network Settings control panel solved the issue...
Also using WEP and not WPA Personal when setting up security got me a connection, I could never get WPA to work with my card on OS.11 [the quality of the card I have is questionable - connection issues are persistent]
edit:
WEP is not a good long term solution nor is WPA personal...
Last edited by weaponsofwar; 02-01-2010 at 01:58 PM.
Also use WEP and not WPA Personal when you do set up security, could never get WPA to work...
--in case anyone runs into this again...
I just registered because of that statement. That is the most stupid sentence I have read for a long time. WEP is highly insecure. You might also just leave the network open and unencrypted. Cracking WEP takes about 5 mins.
Use WPA2, its not that difficult to setup.
man iwconfig will tell you how
Distribution: openSUSE 10->11.2, fedora 8->11, CentOS 5+, et al
Posts: 6
Rep:
Quote:
Originally Posted by Rodnox
I just registered because of that statement. That is the most stupid sentence I have read for a long time. WEP is highly insecure. You might also just leave the network open and unencrypted. Cracking WEP takes about 5 mins.
Use WPA2, its not that difficult to setup.
man iwconfig will tell you how
I was obviously having problems getting it set up or I wouldn't have used WEP at all. Ended up re-installing Leonidas and WPA is working correctly now.
When debugging an issue, taking avenues you wouldn't normally take in the process is acceptable... even if it means using WEP for a couple of hours so you can actually get online to look for more solutions/known issues with hardware, etc...
I should have added that WEP isn't a good long term solution - mea culpa.
Also keep in mind that WPA Personal isn't secure either...
It can be cracked in 60 seconds.
Use AES, turn off DHCP, turn off SSID broadcast[not that that will deter anyone who is seriously looking for your network], and Bind IP address to your card MAC addresses for even more security.
that being said, this is a thread about getting your wireless card to work at all - not getting your wireless network secured.
Also keep in mind that WPA Personal isn't secure either...
It can be cracked in 60 seconds.
Use AES, turn off DHCP, turn off SSID broadcast[not that that will deter anyone who is seriously looking for your network], and Bind IP address to your card MAC addresses for even more security.
Could you reference this claim? Did you mean turn off uPNP? Also, since the essid is used in combination with the passphrase, it functions as salt. It reduces the risk of dictionary attacks against the passphrase.
So far I'm only aware of a caught handshake that than will have to match a word list. A good chosen password should make WPA1 pretty secure.
WPA2 is absolutely secure.
Now, I have no problem of you proofing me wrong. Please do so, if you can.
I know this is old but I cracked a WPA2 against a dictionary I made using a script that generates 10 digit numbers. In my case, I generated a dictionary using my local area code for the first 3 digits and then the subsequent numbers in their order. On a machine running only 100 keys per second, it was eventually concluded that the password was a phone number, like they usually are.
Tell me how do you crack CCMP/AES in 60 seconds? Do you own your private super-computer, which magically isn't appearing as most powerfull? Go on, I can give my handshake - crack it! Have a go! Just to let you know - yes I am using WPA/RSN (version 2) Personal CCMP/AES and even if you would crack my passphrase (ha ha ha), you still would be unable to use my network, as MAC do not match passphrase, neither MAC filter! Do not state such ridiculous statements, as you even don't know what you are talking about man. WPA isn't WEP and have nothing to do with WEP (apart from TKIP and even TKIP isn't easy to crack). 60 seconds to find passphrase, when passphrase could 63 characters long and keys are salted with ESSID? No way man. First of all approach is completely different, second even generating all possible passphrases would take ages and it won't fit into your 60 seconds! It won't be done even after 24 hours, so think and research subject, before you would start to talk about it! OK?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.