[SOLVED] Atheros madwifi Debian AP causing 'Beacon Missed'
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.
I have a very strange and annoying problem. I haev been running a wireless AP for several years now (4-5) without a single problem. This was built using Debian Etch and an Atheros card using the Madwifi module and a pretty simple iptables script. Worked beatifully, all devices (pc/laptop/WII/phones/etc) find it, connect and it's all good.
Last weekend I [foolishly?] decided to upgrade to Debian Squeeze. First Madwifi was not available, so I downloaded the src, built and installed. This is where it started to go wrong. It caused my new install to freeze, requiring a forced reboot. Thankfully, I kept my original Etch install and booted back into it but now I'm getting 'Beacon missed' errors and client machines disconnect!!
How on earth could running the card on another OS cause this fault? And how the heck do I fix it?
like I say, it was and has been working lovely for years. It hasn't physically altered, I haven't removed it from the machine, I have simply installed another OS (on the same physical machine) then switched back to the original.