From: Jan Kiszka <jan.kiszka@web.de>
To: Jiri Benc <jbenc@suse.cz>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Ivo Van Doorn <ivdoorn@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: d80211: How does TX flow control work?
Date: Tue, 01 May 2007 12:50:25 +0200 [thread overview]
Message-ID: <46371B71.2090508@web.de> (raw)
In-Reply-To: <20070501124733.47c45dd0@logostar.upir.cz>
[-- Attachment #1: Type: text/plain, Size: 772 bytes --]
Jiri Benc wrote:
> On Tue, 01 May 2007 12:41:34 +0200, Jan Kiszka wrote:
>> Now I came across this issue once again. It is still present, I just
>> observed it over the latest rt2x00 tree after updating shorewall and
>> forgetting to fix its config.
>>
>> I redirected tc to some logging filter, and this is what shorewall does
>> when "CLEAR_TC=Yes" is set in shorewall.conf:
>>
>> ...
>> tc qdisc del dev wmaster0 root
>> tc qdisc del dev wmaster0 ingress
>> tc qdisc del dev wlan0 root
>> tc qdisc del dev wlan0 ingress
>
> Could you retest with the latest wireless-dev? It should be fixed there.
Could you point me to the patch(es) in question? I only have 2MBit/s
downlink, so that downloading only the patch would speed things up here.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2007-05-01 10:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-02 13:08 d80211: How does TX flow control work? Jan Kiszka
2007-01-03 17:52 ` Jiri Benc
2007-01-03 18:10 ` Jan Kiszka
2007-01-03 18:18 ` Jiri Benc
2007-01-03 18:50 ` Jan Kiszka
2007-01-07 0:00 ` Jan Kiszka
2007-01-08 20:18 ` Jan Kiszka
2007-01-10 18:20 ` Jiri Benc
2007-01-10 18:29 ` Simon Barber
2007-03-27 20:58 ` Johannes Berg
2007-03-29 8:45 ` Jan Kiszka
2007-05-01 10:41 ` Jan Kiszka
2007-05-01 10:47 ` Jiri Benc
2007-05-01 10:50 ` Jan Kiszka [this message]
2007-05-01 11:04 ` Johannes Berg
2007-05-01 13:07 ` Jan Kiszka
2007-05-01 13:26 ` Johannes Berg
2007-05-01 14:18 ` Jan Kiszka
2007-05-01 15:25 ` Jiri Benc
2007-05-01 17:01 ` Michael Wu
2007-05-01 18:57 ` Jan Kiszka
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=46371B71.2090508@web.de \
--to=jan.kiszka@web.de \
--cc=ivdoorn@gmail.com \
--cc=jbenc@suse.cz \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.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.