From: Felix Fietkau <nbd@openwrt.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [OpenWrt-Devel] ath9k (ad-hoc?) problems in compat-wireless trunk as of sept 6/2
Date: Sun, 15 Sep 2013 11:25:17 +0200 [thread overview]
Message-ID: <52357CFD.60107@openwrt.org> (raw)
In-Reply-To: <522DB12B.5000409@altermundi.net>
On 2013-09-09 1:29 PM, Nicol?s Ech?niz wrote:
> I have kept testing this and was able to reproduce the same problem
> every time.
> The performance perception when the network is at "rush hour" is very
> unstable so I tried to reproduce traffic conditions during late night.
> I sent multiple netperfs through different routes and while the netperfs
> were running turned of one node. Latency climbed to the thousands and it
> took a while for it to stabilize again.
>
> Then I turned off another node, latency went sky high again for some
> seconds until I lost conectivity and could monitor no more.
>
> I waited more than 15 minutes for the net to be reachable again from my
> local node. (Nodes are automatically reset when they cannot reach the
> network gateway for more than 15 minutes)
>
> All ping tests are done on fe80 local IPv6 addresses so no routing
> protocol is involved in case someone's wondering. Also, from what I see
> (iw station dump), routers are associated but can send no data.
I've committed some fixes that might be related to this issue. Please
test current OpenWrt trunk.
Thanks,
- Felix
prev parent reply other threads:[~2013-09-15 9:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-08 1:40 [ath9k-devel] ath9k (ad-hoc?) problems in compat-wireless trunk as of sept 6/2 Nicolás Echániz
2013-09-09 11:29 ` [ath9k-devel] [OpenWrt-Devel] " Nicolás Echániz
2013-09-15 9:25 ` Felix Fietkau [this message]
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=52357CFD.60107@openwrt.org \
--to=nbd@openwrt.org \
--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.