Why does my access point keep dropping all wireless connections?

A couple of weeks ago, I replaced my ageing DI-624 with a WRT54G because the connection was getting flaky. Unfortunately, this only made things worse: pretty much from the start, I was losing my connection all the time. I decided immediately that I’d just replace it, so I picked up a WRT54GL, which has more more memory and is easier to flash with third party firmware.

Here’s the issue: no matter which firmware I go with (I’ve tried stock, DD-WRT and Tomato so far), I have the SAME problem in all cases: the access point periodically drops ALL wireless connections. The router isn’t crashing or rebooting, and LAN connections are unaffected - the router is simply periodically dropping all connected wireless clients. I have tried upping transmit power and dropping the ACK timeout, to no avail. I don’t think it’s a signal strength issue, and as I say the router itself isn’t actually crashing.

Any ideas? Are there any other settings I can tweak? I looked for a ‘kill my wireless connection every five minutes’ option in the firmware and it’s not there.

Vista, by any chance?

My desktop is running XP, and my laptop is running Vista. It drops both of them at the exact same time.

Blame the hardware. Perhaps it’s a loose antenna connector wires, or a bad solder joint. Perhaps there is cordless phone nearby operating on the 2.4GHz frequency.

My WRT54G started doing something like this post Vista. ‘Reset to factory defaults’ sorted it out for me, for a week or two.

Hey, that actually seems to be working so far. I haven’t even dared put encryption back on yet - hopefully it will hold up when I do so.

I had regular drops on my WRT54GL with both stock and HyperWRT firmware,
but DD-WRT has been good. But I also changed the channel at the same time.

Mine is still holding up. I think there was some weird setting left over from the stock firmware that was causing the drops. It’s rock solid now.

Interference from a cordless phone?

Don’t blame just Vista for this. OS X has a notorious dropping connection problem. Still hasn’t been fixed.

I spent over a week and swapped out access points three times troubleshooting
frequent network drops and disabled laptop wireless cards.

Turns out the network was being attacked:

A hospital had rented space in the same building as one of Brian’s clients,
and the hospital has a Cisco device which detects any nearby access points and
targets them as “rogues” and then hits them with a death flood.

We had to call the hospital and give them our MAC address so they would
classify us as a “friendly” access point and stop hammering us. This is
likely
to become an issue with anyone who uses this Cisco system, such as hospitals,
govt. security acencies, or mega-corporations.

I think the hospital uses a Cisco SWAN WLAN IDS, which “quickly detects,
locates, and automatically shuts down rogue access points.”

See below:

"Jamming for Defense

One a side note, jamming is not just for malicious use. One way of
controlling
rogue access points in an enterprise is the flooding of packets to client
devices that are connected to a rogue access point. Some current wireless
network vendors include a method for creating a denial-of-service situation
for unauthorized wireless implementations by sending packets with the same
characteristics as a valid access points with disassociate packets. These
packets fool the client into thinking that the rogue access point doesn’t
want
to communicate with the device anymore, effectively killing network
connectivty before it can be established. This is a very powerful feature
that
must be used carefully, as legal and political repercussions could arise."

We think the hospital may be breaking the law:

The operation of transmitters designed to jam or block wireless
communications is a violation of the Communications Act of 1934, as
amended (“Act”). See 47 U.S.C. Sections 301, 302a, 333. The Act
prohibits any person from willfully or maliciously interfering with the
radio communications of any station licensed or authorized under the Act
or operated by the U.S. government. 47 U.S.C. Section 333. The
manufacture, importation, sale or offer for sale, including advertising,
of devices designed to block or jam wireless transmissions is
prohibited. 47 U.S.C. Section 302a(b). Parties in violation of these
provisions may be subject to the penalties set out in 47 U.S.C. Sections
501-510. Fines for a first offense can range as high as $11,000 for each
violation or imprisonment for up to one year, and the device used may
also be seized and forfeited to the U.S. government.

Spread the word to all your tech buddies to be on the lookout for this
if you have any clients near hospitals, etc.

REPORTED