Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place! |
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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
|
06-06-2012, 12:41 PM
|
#1
|
Member
Registered: May 2009
Distribution: slackware, fedora, ubuntu
Posts: 101
Rep:
|
wicd can't connect to wireless
I have ethernet network working on my system, but the wireless wouldn't work. So I installed wicd, but now it seems that even wicd can't connect to the wireless network. It hangs on saying "validating authentication" and after around 30 seconds quits saying "No connection".
The output of lspci -v is
Code:
04:00.0 Network controller: Intel Corporation Wireless WiFi Link 5100
Kernel driver in use: iwlagn
Kernel modules: iwlagn
08:00.0 Ethernet controller: Broadcom Corporation NetLink BCM5784M Gigabit Ethernet PCIe (rev 10)
Kernel driver in use: tg3
Kernel modules: tg3
I'm using a WEP passphrase which is definitely correct.
|
|
|
06-06-2012, 02:55 PM
|
#2
|
Member
Registered: May 2012
Posts: 426
Rep:
|
It could be as simple as (but might not be) the access point not negotiating DHCP correctly with your device - this has happened to me. Try setting your IP address, subnet mask, gateway and DNS servers manually in wicd then try connecting.
Also, what distro are you using and why are you using WEP (is quite insecure)?
|
|
|
06-06-2012, 04:58 PM
|
#3
|
Member
Registered: May 2009
Distribution: slackware, fedora, ubuntu
Posts: 101
Original Poster
Rep:
|
Quote:
Originally Posted by nixblog
It could be as simple as (but might not be) the access point not negotiating DHCP correctly with your device - this has happened to me. Try setting your IP address, subnet mask, gateway and DNS servers manually in wicd then try connecting.
|
Tried, but still fails.
Quote:
Originally Posted by nixblog
so, what distro are you using and why are you using WEP (is quite insecure)?
|
I'm using slackware. Yeah, I know WEP is too insecure but facing the same problem with WPA.
|
|
|
06-06-2012, 09:06 PM
|
#4
|
LQ Guru
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Ubuntu MATE, Mageia, and whatever VMs I happen to be playing with
Posts: 19,580
|
It's farfetched, but I sometimes have this problem and found that rebooting my wireless router fixes it. I think the router needs replaced, but I've been too lazy to get around to it.
When the problem occurs, wireless devices that are already connected remain connected, but new connection attempts throw an authentication error.
|
|
|
06-06-2012, 10:14 PM
|
#5
|
Member
Registered: May 2012
Posts: 426
Rep:
|
Quote:
Originally Posted by frankbell
When the problem occurs, wireless devices that are already connected remain connected, but new connection attempts throw an authentication error.
|
Yeah, just replaced a friends Dlink router as it was doing something similar. Some disconnected, some stayed connected and new connections never completed.
|
|
|
06-06-2012, 10:53 PM
|
#6
|
Member
Registered: May 2003
Location: The Left coast, USA
Distribution: Slack_64 14.2
Posts: 226
Rep:
|
Are you sure the encryption level is set the same between the router and the computer? The symptoms are similar to what you are seeing.
I've had problems with this before(in windows) Usually 40 & 64 bit are compatible with each other, but neither of those are compatible with 128 bit.
I haven't used WEP in a long, long time... Not sure how to change the encryption level in WICD, but it should be easy to change in your routers configuration....
Last edited by ceh383; 06-06-2012 at 10:56 PM.
|
|
|
06-07-2012, 12:04 AM
|
#7
|
Senior Member
Registered: Apr 2005
Location: OZ
Distribution: Debian Sid/RPIOS
Posts: 4,903
|
Try using wpa_passphrase
for the proper usage, man wpa_passphrase
|
|
|
06-07-2012, 05:19 AM
|
#8
|
LQ 5k Club
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware64 15; SlackwareARM-current (aarch64); Debian 12
Posts: 8,307
Rep:
|
Don't know if this is relevant or helpful, but I had problems getting or maintaining a wireless connection with wicd on my laptop and netbook - so I installed Network Manager. No problems since.
|
|
|
06-07-2012, 01:59 PM
|
#9
|
Member
Registered: May 2009
Distribution: slackware, fedora, ubuntu
Posts: 101
Original Poster
Rep:
|
I installed Network manager and it's dependencies. But when I run nm-applet it says
Code:
bash: /usr/bin/nm-applet: cannot execute binary file
the user is already in the netdev group..
|
|
|
06-07-2012, 02:13 PM
|
#10
|
LQ 5k Club
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware64 15; SlackwareARM-current (aarch64); Debian 12
Posts: 8,307
Rep:
|
When I installed it, I ran:
Code:
chmod +x /etc/rc.d/rc.networkmanager
then:
Code:
/etc/rc.d/rc.networkmanager start
And edited the wicd entry in /etc/rc.d/rc.M to read:
Code:
# Start Network Manager:
if [ -x /etc/rc.d/rc.networkmanager ]; then
sh /etc/rc.d/rc.networkmanager start
To start it at boot-up.
|
|
|
06-07-2012, 02:45 PM
|
#11
|
Member
Registered: May 2009
Distribution: slackware, fedora, ubuntu
Posts: 101
Original Poster
Rep:
|
I've already changed the permissions and also edited the /etc/rc.d/rc.M file, but I can't seem to run nm-applet. I was trying to figure out a way to connect using nmcli. But it seems that nmcli only connects to pre-connected connections.
shows me my the connection. But whenever I try
Code:
nmcli con up id 'connection id here'
it throws me the following error
Code:
Error: Unknown connection: connection id here.
I can't seem to figure out what the id is. Is it the SSID or just the name of the connection?
|
|
|
06-07-2012, 03:06 PM
|
#12
|
LQ 5k Club
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware64 15; SlackwareARM-current (aarch64); Debian 12
Posts: 8,307
Rep:
|
I don't know. Try your SSID. I only had to do like craigevil mentioned regarding wpa_passphrase, edit /etc/wpa_supplicant.conf, then what I said in my previous post, and everything worked OK. nm-applet showed up in my system tray on the next boot-up.
Last edited by brianL; 06-07-2012 at 03:08 PM.
|
|
|
06-07-2012, 03:28 PM
|
#13
|
Member
Registered: May 2009
Distribution: slackware, fedora, ubuntu
Posts: 101
Original Poster
Rep:
|
Worked. re-installed network-manager-applet 0.8.2 and it worked.
btw. nmcli can't be used to connect to networks you haven't connected before. I was able to use it to connect to my ethernet network but not my wireless.
|
|
|
06-07-2012, 03:35 PM
|
#14
|
LQ 5k Club
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware64 15; SlackwareARM-current (aarch64); Debian 12
Posts: 8,307
Rep:
|
Glad you've got it sorted out.
|
|
|
All times are GMT -5. The time now is 04:38 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|