Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then 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.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Did you try ps -aux|grep wpa_supplicant or ps -ef|grep wpa_supplicant to see if the wpa_supplicant process is already running and if so killing it via kill pid#? That was exactly the problem I had where it would continuously try to connect, but as soon as I did that it worked for me.. Besides that you may need to specify a different driver.. See man wpa_supplicant for available drivers...
What do you think? As part of following suggestions to fix this I have installed:
Network Manager
Wicd
wpa supplicant
thinking some of these may conflict, but do not know how to tell.
Also I went back to /etc/network/interfaces and entered seperate lines for:
Code:
auto wlan0
iface wlan0 inet dhcp
To autostart the wifi. Had disabled this earlier and the searching for wifi networks causes boot-up to stall for over 10 minutes. Goes immediately without.
Help please!
TBNK
as far as I know it is one or the other.
I had a linux os using Network manager (applet) and wicd
I have a linux os using Network manager and Oh Hell I do not even know, haha. but it works. you cannot mix them though is all.
Wicd
and
wpa supplicant
Since I'm clueless on wifi networking would like to disable wpa_supplicant and Network Manager to see if I can resolve this with wicd.
I use to have a system that used a wifi link via high gain antenna, on wlan0, and then was PDC so served as DHCP server on eth0 and could only resolve all the issues with wicd so think it should be my choice here as well.
Do you guys agree?
If so want to disable the other 2 without removal, till I get this right then and only then remove them.
That wouldnt help cause like I said such programs use wpa_supplicant as the back-end their front-end.. The wicd-daemon depends on wpa_supplicant, you can verify that's the case if you type apt-cache showpkg wicd-daemon.. I would keep trying wpa_supplicant with the -dd option which increase debugging verbosity and provide a little more insight into what the output is refering to as it's trying to connect.. Also I would check dmesg and grep for your wireless card driver and interface... Get your wireless card driver info by issuing lspci | egrep -i --color 'wifi|wlan|wireless' and then lspci -vv -s 06:00.0 (get your '06:00.0' from the previous command)..
Last edited by justmy2cents; 09-02-2017 at 05:52 PM.
That wouldnt help cause like I said such programs use wpa_supplicant as the back-end their front-end.. The wicd-daemon depends on wpa_supplicant, you can verify that's the case if you type apt-cache showpkg wicd-daemon.. I would keep trying wpa_supplicant with the -dd option which increase debugging verbosity and provide a little more insight into what the output is refering to as it's trying to connect.. Also I would check dmesg and grep for your wireless card driver and interface... Get your wireless card driver info by issuing lspci | egrep -i --color 'wifi|wlan|wireless' and then lspci -vv -s 06:00.0 (get your '06:00.0' from the previous command)..
justmy2cents,
None of your ideas, though good, address the problem. Already know wifi is connecting, so no problem with the RF side of the connection. The problem is somehow dhclient is misconfigured or just not working, thus no IP assigned and therefore no communications. Even direct ping to google's known/shown IP doesn't work, because if not IP is set on wlan0 it will not communicate, even with the RF section of wifi connected.
I tried purging dhclient, to re-install but dependencies with WireShark and 2 other apps would not let purge go through. Documenting those as may need to purge them as well to clear this issue.
I don't know which command to execute to show the connection is up and workin but dhclient not working other than what I see. I get the lower right popups that show:
Connection found,
Establishing connection
Connection established.
the the connection button in wicd turns green
but can never ping. Don't get any errors from dhclient
but:
Code:
ping -c 3 www.google.com
and
ping -c 3 172.217.12.60
or
ping -c 3 8.8.8.8
all yield
Code:
3 packets transmitted, 0 received, 100% packet loss, time 2016ms
So you can see I have connection but no IP so cannot actually connect without the IP assigned!
I also ran:
Code:
Ifconfig wlan0
which shows IP as 192.168.43.147, which is a local network IP and it shoul be showing a non local IP. Assume something there is the problem.
What else I know, that may now be pointing to my phone as the problem area:
Code:
I just got inet connect to my house after 6 months no service.
I can run wired.
I can connect and ping through my Netis wireless router, so DNS seems to be working OK.
Conclusion:
I'll mark this closed as I now can connect and ping via the Netis router, and will open a thread on this at the Android forum, as this appears now to just be an issue with the WIFI hotspot on my phone.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.