From: Walter Haidinger <walter.haidinger@gmx.at>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Packets Redirection
Date: Thu, 24 Oct 2002 08:43:56 +0000 [thread overview]
Message-ID: <marc-lartc-103544919612270@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103544064405271@msgid-missing>
On Thu, 24 Oct 2002, Tom wrote:
> tc filter add dev $DEV parent 1:0 prio 0 protocol ip handle 20 fw flowid 1:20
> tc filter add dev $DEV parent 1:0 prio 0 protocol ip handle 21 fw flowid 1:21
> tc filter add dev $DEV parent 1:0 prio 0 protocol ip handle 22 fw flowid 1:22
This odd. With my setup (2.4.20pre10 and tc from the 3.6 tarball) I need
to specify classid instead of flowid:
# tc filter add fw help
Usage: ... fw [ classid CLASSID ] [ police POLICE_SPEC ]
POLICE_SPEC := ... look at TBF
CLASSID := X:Y
> iptables -t mangle -N MYSHAPER-OUT
> iptables -t mangle -I POSTROUTING -o $DEV -j MYSHAPER-OUT
Tried OUTPUT chain for locally generated packets?
> I transfered a file by ftp. The packets was sent through the class 22 and
> its bandwith limited to 88kbits, which is normal.
Yes if normal = default.
> But i sent pings and thoose packets were sent through the class 22 too
> which is not normal due to the mangle packets marking. I know which
> class was used by looking the tc classes status. Why icmp packets was
> not sent through class 20 ?
To see which chain you're required to use, append your MYSHAPER-OUT chain
to all default chains in the mangle table and see if it works.
Then have a look at the packet counts and remove the unused.
Walter
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-10-24 8:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-24 6:22 [LARTC] Packets Redirection Tom
2002-10-24 8:43 ` Walter Haidinger [this message]
2002-10-24 11:17 ` Stef Coene
2002-10-24 11:27 ` Tom
2002-10-24 11:37 ` Stef Coene
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=marc-lartc-103544919612270@msgid-missing \
--to=walter.haidinger@gmx.at \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox