Why do I keep getting kicked off the unsecure wireless LAN at the library?
Linux - NewbieThis 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.
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.
Why do I keep getting kicked off the unsecure wireless LAN at the library?
I was wondering if anyone can tell me why I keep getting kicked off the wirelss LAN at the public library I use. When this happens, I get the following message from the /var/log/messages file:
Aug 21 19:14:30 linux kernel: [ 1864.853508] wlan0: deauthenticated from 00:17:0f:db:3b:50 (Reason: 1)
Once I reboot the computer, I can connect to the same wireless LAN, but it will kick me off in about 15 to 20 minutes.
Locally, Librarians know nothing about networking (but there is a department, somewhere, that does) so you may or may not have success with that.
In the past, I have seen some success with the following measures:
Ensure that NM (or WicD) are set to reconnect automatically.
Open a terminal and run a ping in the background to ensure that the line never goes quiet for too long
In principle, you probably shouldn't have to do either of the above, in practice they seem to help. I have no idea whether it would help you, as the network to which you connect is probably very unlike the ones local to me.
It also helps to ensure that the computer is not swapping as that seems to occasionally add long delays, and it seems possible that if there is a long delay, something times out.
Sorry to hear that. Generally, it's not the case (e.g.: http://code4lib.org/about). Otherwise, if it's an authentication issue, then the librarians should be able to help. It won't hurt to ask as it may be a common problem that has nothing to do with the OS anyone is running.
Last edited by cseanburns; 08-22-2012 at 12:23 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.