Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in Linux.
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.
for some reason my wireless internet is going extremly slow. when sniffing the traffic, i can see tons of "standard DNS requests" going from my machine to 192.168.1.1 (the wireless router). this does not happen in windows, or with a wired connection. i am using madwifi with an atheros wireless card. my /etc/resolv.conf is set to
this is what it says
ath0 IEEE 802.11g ESSID:"Scooter" Nickname:"linux"
Mode:Managed Frequency:2.462 GHz Access Point: 00:x:x:x:x:x
Bit Rate:11 Mb/s Tx-Power:16 dBm Sensitivity=0/3
Retry:off RTS thr:off Fragment thr:off
Link Quality=23/94 Signal level=-72 dBm Noise level=-95 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
does anyone have any ideas?
Last edited by true_atlantis; 06-07-2006 at 10:41 PM.
I don't think your resolv.conf file should be set to your router. You say it doesn't happen with a wired connection. Check the resolv.conf file with the wired connection. Assuming you're using the same router for both, your wireless resolv.conf should be the same as it is when you're wired.
i tried that little fix, and it doesnt seem to help. i changed my distro to fedora core 5 (x86_64)and i get the same problem, but now its a little different... when im downloading things using bittorrent, it does huge activity spikes... at one second, it will be downloading at 100k, then ill look 10 minutes later, and its stalled at 0k... any other ideas?
If you are not having problems with wired connections, and you changed distros and are still having the same problem with wireless, it makes me wonder if there is something wrong with your driver or wireless configuration setup.
It is also possible you are getting a weak signal. Wireless can be flaky if the signal is "borderline." That is, my wife's machine, which is one room away from our wireless access point, has no problems getting a solid, consistent signal. However, the family room computer, which is across the house, tends to exhibit behavior like you describe--great for a few minutes and then slows to a standstill the next. I was able to eliminate about 90 or 95% of the problem by changing the wireless adapter in the family room computer from Netgear to D-Link (some brands or models are a lot better than others), but I think there is only so much I can do without replacing the antenna with some sort of high gain one.
well, i have a sort of work around... i allowed DNS caching on my machine... for some reason the DNS was not being resolved all the time and was timing out a lot... i think that has something to do with my router, but i am not sure.