From: Edgar <donvodka@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB and bittorrent, won't work
Date: Thu, 07 Jul 2005 04:51:54 +0000 [thread overview]
Message-ID: <200507062351.54553.donvodka@gmail.com> (raw)
In-Reply-To: <200507061623.38806.donvodka@gmail.com>
First of all thank you for answering to my email, I will answer to all the
questions you ask:
> On Wednesday 06 July 2005 23:23, Edgar wrote:
> > I've been trying to shape the bittorrent traffic (on my external
> > interface, upload), but without luck, for this I'm using layer7 filter
> > right now, but I've also tried ipp2p, with the same results
>
> I don't have any problems with BT shaping... if you want to have a look at
> my script, it's this one: http://www.metamorpher.de/fairnat/
> It uses IPP2P, but should work about the same way with layer7.
>
> The main difference between my iptables rules and yours seems to be that
> you are not using CONNMARK to mark BT connections permamently - IIRC you
> can't do without because the filters only match one of the first few
> packets of a connection.
>
In the layer7 filter the examples don't use CONNMARK like with ipp2p, but I
will try to add CONNMARK to my rules, and see what happens.
> Have you checked your class statistics with tc, somehow I doubt that all BT
> packets go into your P2P class in your current setup.
>
I've checked this with tc -s class show dev eth1, and I see almost all the
traffic going to the p2p class, right now I will add a new ACK rule, to match
ack packets, since someone told me that might be the problem.
> > I hope someone can help me out with this, maybe it not ok to use tcng
> > with iptables? thank you in advance
>
> Well, I'm not familiar with tcng syntax at all. I think this kind of setup
> is weird; in the tcng part no class ids seem to be specified, yet you have
> to use them in iptables to classify your packets. How can you be sure that
> you got the right class...
When the tcng code gets compiled, it returns tc commands, and then I can see
them, and I know those are the classes I need for iptables =)
Thanks for your interest, I'll check your rules right now, to see if that
helps.
>
> HTH
> Andreas
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
EDGAR MERINO
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-07-07 4:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-06 21:23 [LARTC] HTB and bittorrent, won't work Edgar
2005-07-07 4:29 ` Andreas Klauer
2005-07-07 4:30 ` Jody Shumaker
2005-07-07 4:51 ` Edgar [this message]
2005-07-07 5:42 ` Edgar
2005-07-07 7:22 ` Klaus
2005-07-07 11:36 ` Forte Systems - Iosif Peterfi
2005-07-07 20:34 ` Edgar
2005-07-08 8:49 ` Forte Systems - Iosif Peterfi
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=200507062351.54553.donvodka@gmail.com \
--to=donvodka@gmail.com \
--cc=lartc@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.