From: Mihai Moldovan <ionic@ionic.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Ubiquity SR71-E: direct probe timed out
Date: Sun, 31 Jul 2011 03:04:10 +0200 [thread overview]
Message-ID: <4E34AA0A.4040305@ionic.de> (raw)
In-Reply-To: <CAN0CFw3L3LWOjAxeRTj+oGH+dYsy-O+OQw3BjreF4GdwnJpLrg@mail.gmail.com>
* On 31.07.2011 01:41 AM, Grant wrote:
> It's fixed! The problem was actually interference from an ath5k
> 802.11g card I had in the same system. I've noticed that any wireless
> card installed in the system will pump out enough RF to interfere with
> any other card in the system even if the interfering card's drivers
> are compiled out of the kernel.
I've had similar problems before, sorry. More specifically, I've been
using 2 ath9k operated cards in one system and my STAs were able to
connect for a short time, but were as well disconnected after at most 5
minutes. Another fact aggravating this problem was using the same SSID
for both AP mode cards.
I suspect using two cards on the same base frequency (i.e. 2GHz) in the
same system (or even in the same range) is a bad thing to do, even if
the channels themselves are not overlapping.
On the other hand, my current setup involves 2 ath9k driven cards, each
with separate SSIDs and on different base frequencies (2GHz and 5GHz)
which doesn't show any of these problems and indeed is running fine,
from what I can tell.
Every now and then my laptop will "disconnect" from the network and any
connection time out until I manually tell the system to reconnect to the
network or cycle the WLAN card's power (thus forcing a reconnect), but
I'm not entirely sure what's causing it, as I'm not getting any errors
on either my STA (which, granted, is an OS X system and I don't even
know where Apple would log wireless errors but via syslog or in the
Kernel log ring buffer, no one showing any error traces though) or my
AP. Weirdly it does only seem to happen when streaming a video file over
NFS, so I'm reluctant to blame it on the 2 cards setup. :)
Best regards,
Mihai
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4369 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20110731/f687e723/attachment.bin
next prev parent reply other threads:[~2011-07-31 1:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 18:31 [ath9k-devel] Ubiquity SR71-E: direct probe timed out Grant
2011-07-29 6:34 ` Mohammed Shafi
2011-07-29 6:50 ` Mohammed Shafi
2011-07-29 18:11 ` Grant
2011-07-30 23:41 ` Grant
2011-07-31 1:04 ` Mihai Moldovan [this message]
2011-07-31 3:40 ` Adrian Chadd
2011-07-31 19:27 ` Grant
2011-08-01 2:22 ` Adrian Chadd
2011-08-01 5:19 ` Alex Hacker
2011-08-01 8:31 ` Alex Hacker
2011-08-01 9:07 ` Adrian Chadd
2011-08-01 10:15 ` Alex Hacker
2011-07-29 18:09 ` Grant
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E34AA0A.4040305@ionic.de \
--to=ionic@ionic.de \
--cc=ath9k-devel@lists.ath9k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.