From: Julien Vehent <julien@linuxwall.info>
To: netfilter <netfilter@vger.kernel.org>
Subject: Re: about "tc"
Date: Wed, 07 Apr 2010 15:04:25 +0200 [thread overview]
Message-ID: <0b165b34c69893e6d154392a2d3df036@localhost> (raw)
In-Reply-To: <alpine.LSU.2.01.1004061231370.20809@obet.zrqbmnf.qr>
On Tue, 6 Apr 2010 12:31:43 +0200 (CEST), Jan Engelhardt
<jengelh@medozas.de> wrote:
> On Tuesday 2010-04-06 08:30, Mihamina Rakotomandimby wrote:
>
>>Manao ahoana, Hello, Bonjour,
>>
>>After a few search, I thought netdev@vger.kernel.org was the right ML
>>to discuss about "tc".
>>
>>But when just lurking the traffic, it's more about network devices
>>development...
>>
>>Where would you recommend to subscribe in order to talk about "tc"?
>
> If in doubt, use this one.
There are a few folks discussing QoS and Firewalling on the Debian
Firewall list as well.
debian-firewall@lists.debian.org
prev parent reply other threads:[~2010-04-07 13:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 6:30 about "tc" Mihamina Rakotomandimby
2010-04-06 7:41 ` Marek Kierdelewicz
2010-04-06 10:31 ` Jan Engelhardt
2010-04-07 13:04 ` Julien Vehent [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=0b165b34c69893e6d154392a2d3df036@localhost \
--to=julien@linuxwall.info \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).