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.
Here it is: http://pastebin.com/m7a7bc2e3
Could be of any more help to have the messages I find as soon as I find the network down? I mean, before a reboot...
Try the following command as root, when you machine can no longer connect to your ISP:
# iwlist wlan0 scan
if you get no joy and your wifi card hasn't gotten too hot and still appears to be functional - I don't if it has any led lights that indicate it is transmitting and or receiving then it appears to me that your ISP ap (access point) has dropped you rather than your machine, your wifi card or your ubuntu os dropping the connection at your end.
Luckily, I have an old acer tablet lapop running XP that I can crank up to check if there is a signal in the air when I get dropped because the signal becomes too weak. When I was trying karmic this resulted in my machine trying to scan for the strongest signal in town and then trying to connect - unsuccessfully - using my static ip settings. Very boring.
nimnull, I already switched to wicd after the first reply in this thread.
Besides, the output of dmesg you see is *after* the reboot.
What you point out is probably the result of my wifi card connecting to the ap after rebooting the machine.
I can't really understand those timestamps (those between brackets are timestamps, right?), so I cannot say for sure, but that seems very likely to me.
minrich, already tried that, the laptop doesn't find any wireless network. I mean, I live in an apartment block and at any time of the day I can scan at least five or six other networks, my neighbor's.
Actually, when my network goes down, my laptop doesn't get disconnected: wicd says I'm still connected but the power of the signal has dropped to -256 dbm, with no other network to be found. I tried to disconnect manually and rescan for available networks but nothing came up. That is, until I reboot.
I can say everything is fine on the part of my ap and isp since I can connect my phone. Sadly I don't have another computer to run any deeper test.
It looks to me that it's a hardware related problem. Of course it shouldn't be a faulty wireless card since under windows everything ran fine.
It must be the kernel or drivers or firmware or whatever messing with my wifi card in some way.
Anyway, thanks for your time so far. Should you ever come up with some other idea, please let me know.
Last edited by Johnnie.it; 11-16-2009 at 11:33 PM.
Ok.
If you use WICD it is good, because it has its own log.
So, please, reboot your comp, connect to wireless, and use it. When wireless disconnects, do not reboot,
save 2 log files: /var/log/daemon.log and one for WICD in /var/log/wicd/wicd.log (copy them to somewhere, but keep the original).
Johnnie.it
I have been pondering your intermittent wireless problem, and wondered if it has something to do with the rfkill module and your wireless card. The first thing I would do is see if rfkill is loaded:
lsmod | grep rfkill
if it is you might want to read the following bug report which emanated on intrepid and your wifi card: (not that I understand it completely!)
Hi guys, there's some news.
it happened again and, so i grabbed a copy of those two files.
daemon.log --- http://pastebin.com/m3f3233a1
wicd.log --- http://pastebin.com/m55028928
disconnection must have happened just a little before 3:00 am. When I found out, I opened wicd, hit "refresh" a couple of times, and nothing.
So I disconnected from that "ghost" wifi network and hit refresh again - nothing yet.
Besides, I found out that wicd logs my password in PLAIN TEXT during handshakes!!! That's insane!!! And I can read the log file without having admin privileges!!!
Why, thank you!
But I didn't do them myself, the merit goes all to linux
Quote:
Originally Posted by nimnull22
First and most strange thing, that there is no any log for /var/log/daemon.log - nothing until Nov 18 12:45:37
What do you mean? On /var/log/daemon I can see like 680 lines before Nov 18 12:45:37
Quote:
Originally Posted by nimnull22
Second, WICD start connects after 1 hour
[cut]
And it successfully connected:
[cut]
But 30 minutes later, there is no networks
[cut]
The question is what happened after 03:47, and why WICD start over?
[cut]
2009/11/08 03:49:35 :: Sending connection attempt result Success
After 3:47 I rebooted. Every time wicd starts over it's because I reboot.
That usually happens because of this very problem, less often for other reasons, like sometimes blueman or pulseaudio going crazy
I almost never shut down...
But shouldn't you be looking at most recent entries?
Like:
Code:
2009/11/19 03:06:09 :: scanning start
and on...?
Anyway, that's the problem. How can I further troubleshoot it?
Last edited by Johnnie.it; 11-19-2009 at 09:28 AM.
Nov 17 02:43:51 localhost blueman-mechanism: Exiting
Nov 18 12:45:37 localhost bluetoothd[1581]: link_key_request (sba=00:1F:3A:E0:B8:51, dba=00:1D:82:02:E1:F0)
Nothing between Nov 17 02:43:51 and Nov 18 12:45:37.
So you just reboot. OK
Lets do next step.
In preferences of the WICD there is option "Debug Log". Please enable it. But log will be very long, and we do not interesting to see all of it.
So when next time your comp. lose connection, cat a part of the log since last successful connection (Sending connection attempt result Success.). And of course delete all passwords.
I can explain why I an asking, because
2009/11/08 03:16:20 :: Sending connection attempt result Success
2009/11/08 03:47:27 :: found window_width in configuration 530
2009/11/08 03:47:27 :: found window_height in configuration 470
2009/11/08 03:47:27 :: scanning start
2009/11/08 03:47:27 :: ifconfig wlan0 up
2009/11/08 03:47:28 :: iwlist wlan0 scan
2009/11/08 03:47:28 :: scanning done
2009/11/08 03:47:28 :: found 0 networks
2009/11/13 20:01:52 :: Sending connection attempt result Success
2009/11/15 14:48:37 :: found window_width in configuration 530
2009/11/15 14:48:37 :: found window_height in configuration 470
2009/11/15 14:48:38 :: scanning start
2009/11/15 14:48:38 :: ifconfig wlan0 up
2009/11/15 14:48:38 :: iwlist wlan0 scan
2009/11/15 14:48:38 :: scanning done
2009/11/15 14:48:38 :: found 0 networks:
2009/11/15 14:55:14 :: Sending connection attempt result Success
2009/11/15 15:00:09 :: found window_width in configuration 530
2009/11/15 15:00:09 :: found window_height in configuration 470
2009/11/15 15:00:10 :: scanning start
2009/11/15 15:00:10 :: ifconfig wlan0 up
2009/11/15 15:00:10 :: iwlist wlan0 scan
2009/11/15 15:00:11 :: Forced disconnect on
2009/11/15 15:00:11 :: /sbin/dhclient -r wlan0
2009/11/15 15:00:11 :: ifconfig wlan0 0.0.0.0
2009/11/15 15:00:11 :: /sbin/ip route flush dev wlan0
2009/11/15 15:00:11 :: ifconfig wlan0 down
2009/11/15 15:00:11 :: ifconfig wlan0 up
2009/11/15 15:00:11 :: scanning done
2009/11/15 15:00:11 :: found 0 networks:
No one knows what was between (for ex.):
2009/11/08 03:16:20 - 2009/11/08 03:47:27
2009/11/13 20:01:52 - 2009/11/15 14:48:37
2009/11/15 14:55:14 - 2009/11/15 15:00:09
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.