From: Claudiu Gafton <lartc@go.ro>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] tc and iptables trouble
Date: Wed, 24 Nov 2004 14:59:37 +0000 [thread overview]
Message-ID: <1101308378.5166.5.camel@ns> (raw)
In-Reply-To: <000a01c4d230$00a14a50$e00010ac@awacat.com>
On Wed, 2004-11-24 at 15:15 +0100, LluÃs Gili wrote:
> Hi all
> I have a trouble configuring the qdiscs, when I indicate the "perturb
> 10" option to tc, i gives me this error:
>
> tc qdisc add dev eth0 parent 5:1323 handle 1323 sfq perturb 10
> RTNETLINK answers: Invalid argument
>
> if I don't put the "perturb 10" option, it works.
perturb 10 it's used by default!!!
nice parent class 5:1323 :o
> another question is about iptables, when I indicate the " --set-mark"
> option:
>
> iptables -t mangle -A egress -s 10.0.0.124 -j MARK --set-mark 1323
> iptables: Invalid argument
When you "--set-mark 1323", iptables try to transform it in HEX... give
it a lower value, like 132! 1323 in HEX = 52B and I think that it
doesn't know how to use 52B as a mark...
> which will be the problem?
> I'm using Debian testing, with kernel 2.6.9 compiled with netfilter
> patches, iptables 1.2.11, iproute2 2.6.9-1, and I have these modules
> loaded:
>
> Module Size Used by
> ebt_mark_m 1096 -
> ebt_mark 1096 -
> ebtables 17768 -
> ipt_mark 1128 -
> sch_wrr 11176 -
> sch_teql 4168 -
> sch_dsmark 5224 -
> cls_route 4936 -
> ipt_tcpmss 1640 -
> cls_tcindex 5256 -
> cls_u32 5772 -
> sch_ingress 2604 -
> ipt_TCPMSS 3208 -
> iptable_filter 1864 -
> ipt_MARK 1512 -
> cls_fw 3208 -
> iptable_mangle 1832 -
> ppp_async 7816 -
> crc_ccitt 1512 -
> ip_gre 8672 -
> sch_esfq 4936 -
> sch_netem 4808 -
> ipt_connlimit 2248 -
> ipt_connmark 1160 -
> sch_gred 5704 -
> sch_red 3368 -
> sch_hfsc 16360 -
> sch_cbq 13864 -
> sch_prio 3528 -
> sch_tbf 4168 -
> iptable_nat 20264 -
> ip_conntrack 37076 -
> ip_tables 13440 -
> ppp_mppe_mppc 13384 -
> ppp_generic 17788 -
> slhc 6312 -
> sch_sfq 4168 -
> sch_htb 20488 -
> rtc 8640 -
> 8139too 16936 -
> mii 3464 -
> crc32 3688 -
>
> Thank you for your time, and sorry my BAD english !!!
--
Claudiu Gafton <lartc@go.ro>
Alvatec Data SRL
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-11-24 14:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-24 14:15 [LARTC] tc and iptables trouble Lluís Gili
2004-11-24 14:59 ` Claudiu Gafton [this message]
2004-11-24 15:21 ` Claudiu Gafton
2004-11-24 15:41 ` Lopsch
2004-11-25 11:27 ` Lluís Gili
2004-11-27 3:33 ` Lluis
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=1101308378.5166.5.camel@ns \
--to=lartc@go.ro \
--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.