All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rio Martin." <rio@martin.mu>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Shape both incoming and outgoing traffic with HTB ?
Date: Tue, 22 Jul 2003 03:11:06 +0000	[thread overview]
Message-ID: <marc-lartc-105884333104913@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105884124903697@msgid-missing>

On Tuesday 22 July 2003 09:41, Martin A. Brown wrote:
> Hello Rio Martin,
>  : I want to shape both incoming and outgoing traffic with HTB.  Since the
>  : first time i applied HTB, i only limit incoming traffic from internet,
>  : while the outgoing traffic is unlimited and now these days my outgoing
>  : traffic really getting higher.
>  : INTERNET ----- eth0 | BW.MANAGER | eth1 --- LAN
> This is not an uncommon problem for masquerading or SNATting hosts.  In
> short, your upload traffic has already been masqueraded/SNATted, so you no
> longer have a source IP of 192.168.0.0/19.

Yes, you re right.
I tried entering my public ip for the match ip src, and it goes smoothly 
shaped.

> The best thing to do is to use fwmark to mark the traffic with
> iptables/ipchains (whichever you are using) and classify the outbound
> traffic according to the fwmark.  See the LARTC documentation on this
> topic [1].

Yes i realized that if i didnt use fwmark, it will be hard to manage outgoing 
traffic from all different network i managed down here.

Thanks ..

Regards,
Rio Martin.

-- 
43rd Law of Computing:
	Anything that can go wr
fortune: Segmentation violation -- Core dumped

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      parent reply	other threads:[~2003-07-22  3:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-22  2:36 [LARTC] Shape both incoming and outgoing traffic with HTB ? Rio Martin.
2003-07-22  2:41 ` Martin A. Brown
2003-07-22  3:11 ` Rio Martin. [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=marc-lartc-105884333104913@msgid-missing \
    --to=rio@martin.mu \
    --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.