From: Gastón <gaston@steel.com.ar>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Whats wrong with my script?
Date: Fri, 30 Jan 2004 12:33:59 +0000 [thread overview]
Message-ID: <002c01c3e72d$56166a40$cd302bc8@traza> (raw)
In-Reply-To: <001301c3e4db$50143c20$cd302bc8@traza>
What if I use public, routable IPs? i.e eth0: public eth1: public and
client`s ips also public.
----- Original Message -----
From: "Damion de Soto" <damion@snapgear.com>
To: "Gastón" <gaston@steel.com.ar>
Cc: <lartc@mailman.ds9a.nl>
Sent: Friday, January 30, 2004 4:16 AM
Subject: Re: [LARTC] Whats wrong with my script?
> Gastón wrote:
> > What about this? : tc filter add dev eth1 parent 1:0 protocol ip prio
100
> > u32 match ip dst 192.168.0.50 classid 1:56
> > Is this correct for shaping upload?
> On your upload (eth0) interface, you can't use private IPs, because
they've already
> been natted to real ones (see http://www.docum.org/stef.coene/qos/kptd/ )
> If you want to shape outbound traffic based on private-lan IP, you need to
mark the
> packets with iptables, then filter based on mark.
> (There are lots of examples of this in the doco and mail archives).
>
> Your download rules seem correct enough.
>
> regards,
_______________________________________________
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-01-30 12:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 13:41 [LARTC] Whats wrong with my script? Gastón
2004-01-29 13:05 ` andybr
2004-01-29 20:19 ` Gastón
2004-01-30 7:16 ` [LARTC] " Damion de Soto
2004-01-30 12:33 ` Gastón [this message]
2004-01-30 14:23 ` Anderson O Muniz
2004-02-01 23:09 ` [LARTC] " Damion de Soto
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='002c01c3e72d$56166a40$cd302bc8@traza' \
--to=gaston@steel.com.ar \
--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