From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: [LARTC] Re: Queries
Date: Wed, 30 Jan 2002 07:55:48 +0000 [thread overview]
Message-ID: <marc-lartc-101237737313988@msgid-missing> (raw)
On Wednesday 30 January 2002 05:01, Arindam Haldar wrote:
> hi all,
> hi stef,
>
> stef i went thru the site www.docum.org & would really like to thank u
> on one part--->monitor.pl.. :-).. havent tried it yestreday but will
> today when i find time but reading it i know that ... :-)
> 1) comming accros 2 one of the pages -->
> www.docum.org/stef.coene/qos/tests/cbq/splitting/weight/splitting-weight.ht
>ml ..i saw these 4 lines & got curious 2know y ur sending pkts with mark of
> 1 & 2 to both classes 10:2 & 20:10 ?..wont there b confusion 2 what rulesse
> 2b applied?
> tc filter add $DEV parent 10: protocol ip prio 3 handle 1 fw classid
> 10:2
> tc filter add $DEV parent 10: protocol ip prio 3 handle 2 fw classid
> 10:2
> tc filter add $DEV parent 20: protocol ip prio 3 handle 1 fw classid
> 20:10
> tc filter add $DEV parent 20: protocol ip prio 3 handle 2 fw classid
> 20:20
The filters are attached to different parents. So when a packets enters 10:,
it's matched. If it has mark 1 it's sended to class 10:2. But qdisc 20: is
attached to 10:2 so the packet is matched to the filter that puts the packet
in 20:10. This test was to see how you have to attach the filters. But it's
not recommended to use more then 1 qdisc in your setup.
> 2) our linux box does managemnt of public lan(office ) & pvt
> lan(cable)--by ip's.. sucess with public ips, marking & using tc filter
> is sucessful but not true with pvt ips (10 series, marking part!).. to
> let u know better here is what we did with public ip..
> iptables -t mangle -A PREROUTING -i eth1 -s <a.b.c.0/26> -d
> <a.b.e.0/25> -j MARK --set-mark 90
> iptables -t mangle -A PREROUTING -i eth0 -d <a.b.c.0/26> -s
> <a.b.e.0/25> -j MARK --set-mark 91
> the tc commands
> tc filter add dev eth0 parent 1:105 pfifo limit 2
> tc filter add dev eth1 parent 2:105 pfifo limit 2
> This works fine--tested with different traffic loads of download&
> upload.
> BUT with lan on eth4 which has pvt ip range(10series) vr not sucesful.
> the problem is how to make sure that the pkts detination for 10.0.0.0/8
> should be marked as they r MASQUERADEd. so i trired to mark with
> FORWARD/OUTPUT/POSTROUTING but unsuccesful. tc -s class.... etc command
> doesnt show any data being passed thru the class while iptables -nvL -t
> mangle shows pkts r being marked & passing thru.
>
> 3) do we need to reset/restart the iptables script when iproute script
> is reapplied or vice versa ?
Nop.
Stef
--
stef.coene@docum.org
More QOS info : http://www.docum.org/
Title : "Using Linux as bandwidth manager"
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
next reply other threads:[~2002-01-30 7:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-30 7:55 Stef Coene [this message]
2002-01-31 6:39 ` [LARTC] Re: Queries Arindam Haldar
2002-01-31 20:17 ` 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-101237737313988@msgid-missing \
--to=stef.coene@docum.org \
--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