From: Damion de Soto <damion@snapgear.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Shaping inbound ok, outbound wrong
Date: Tue, 20 Jan 2004 04:59:43 +0000 [thread overview]
Message-ID: <400CB5BF.2040006@snapgear.com> (raw)
In-Reply-To: <000901c3deae$e465abd0$cd302bc8@traza>
> Yes, I think my problem is on the filters. Actually I`m quite confused.
> If I have eth0 facing the link and eth1 facing the LAN. I should shape
> download in eth1 and upload in eth0, right?
Correct.
> So, for example I should use this filter for shapìng upload
> tc filter add dev eth0 parent 1:0 protocol ip prio 100 u32 match ip src
> 200.43.134.17 classid 1:102
>
> And this one for download
> tc filter add dev eth1 parent 1:0 protocol ip prio 100 u32 match ip dst
> 200.43.134.17 classid 1:80
What is 200.43.134.17?
Is that a machine on your LAN?
Is your network fully routed or are you using MASQ/NAT ?
If that is a PC on your LAN, and you have a fully routed subnet, and all your
qdiscs/classes are setup correctly, then yes, those filters should work.
otherwise no.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Damion de Soto - Software Engineer email: damion@snapgear.com
SnapGear - A CyberGuard Company --- ph: +61 7 3435 2809
| Custom Embedded Solutions fax: +61 7 3891 3630
| and Security Appliances web: http://www.snapgear.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--- Free Embedded Linux Distro at http://www.snapgear.org ---
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-01-20 4:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 17:08 [LARTC] Shaping inbound ok, outbound wrong Gastón
2004-01-19 18:22 ` Stef Coene
2004-01-20 4:34 ` gaston
2004-01-20 4:59 ` Damion de Soto [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=400CB5BF.2040006@snapgear.com \
--to=damion@snapgear.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox