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 am running Ubuntu 17.04 on a Microsoft Surfacebook. For the most part, it works well, other than it randomly disconnecting from the WiFi, but only on one particular network (as far as I can tell -- have only tried home/this other connection). It will work for some time, and then still show as being connected, but loading anything will result in a timeout. The network manager becomes unresponsive -- I can't even turn the WiFi off. After waiting about 30 seconds or so after it drops, I get a timeout error popup.
I have disabled power saving mode, and I am plugged in. Dual boot with Windows 10, 64bit.
Wireless network script output here. After a week or so of looking around, I have been unsuccessful.
For the most part, it works well, other than it randomly disconnecting from the WiFi, but only on one particular network (as far as I can tell -- have only tried home/this other connection). It will work for some time, and then still show as being connected, but loading anything will result in a timeout.
Without knowing anything about the wireless network environment you're describing, could it be disassociating when there is no activity perhaps? You could open a terminal window and observe the NetworkManager logging while using the wireless connection. This might throw up something pertinent when the connection becomes problematic...
A quick look at the wireless info you uploaded to pastebin does reveal a very congested wireless environment. You're connected to AP 'PRISM' at 5.745MHz, along with a number of other APs operating at the same frequency. So interference likely impacting here. Some frequency management (on the part of the operator/administrator) may be needed here.
Sorry for taking so long to respond -- I did not have access to the network until today. Thanks for the information about the congestion, I will forward this to the network manager to see what he could do. One thing that I don't quite understand: if this is a congestion issue, why is it that I can connect to the network via Windows 10 without any issues whatsoever, yet problems occur with Linux? Would this not indicate some sort of driver issue, rather than a congestion issue?
For the time being, they set up an apple router that I could connect to, which seems to make things a little better (as opposed to dropping every 5 minutes, it will now drop every 30 minutes to 2 hours) though this seems to have worsened the last few hours I have been trying it out.
I have attached the network manager logs for both of them. Not sure what is going on, they seem to indicate that I disconnect, and have trouble reconnecting.
This is the original connection method, direct access via connecting to AT&T router (which other computers on network utilize): original-disconnected-notice.txt
This is the same internet connection, access via an Apple router (My computer is the only device that is connected): other-wifi-error.txt
I'm not sure of the underlying reason, but it does appear that there are timeouts involved with connecting to the 'PRISM' AP. This may be impacted by congestion or number of concurrent clients perhaps. With the Apple router (DOBY AP), I note that towards the end of your log it appears to try to connect to PRISM again. I don't know if that is something you did deliberately, or whether you have configured this connection profile to activate when available.
Returning to the uploaded scan results submitted in your opening post, there are multiple APs' (PRISM and PRISM-GUEST) present to provide distributed wifi coverage in a large building I assume. NetworkManager can roam by design in such cases, sometimes a little too often for its own good. However, it can be locked down to a particular AP MAC address (connection editor settings) so that it doesn't roam, and this might help with stability here. Some users simply set up connection profiles for a few preferred access points, so that the connection doesn't roam unnecessarily. I think that is your issue here.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.