Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Simple case here!
Date: Sun, 02 Jan 2005 00:34:50 +0000	[thread overview]
Message-ID: <41D741AA.9090209@dsl.pipex.com> (raw)
In-Reply-To: <41D17063.6030406@hotpop.com>

Amit Vyas wrote:
> 
> Hi All,
> 
> I want to setup a machine to connect to internet at a limited rate of 64 
> kbps.
> That machine is connected to a switch. so my LAN and Internet both comes 
> from the same eth0.
> How can I limit only the internet access from this machine to 64kbps and 
> still using 100mbps for LAN
> 
> I am trying to implement this Please guide me If i am wrong.
> I mark all the packets going out to LAN.
> Then I can setup a root qdisc to classify packets based on that mark. If 
> match  then I can setup a class to accept those setup a fifo for those 
> packets. but if the packets are not for the LAN then i can pass them to 
> other class which is tbf shaping at rate 64kbps.
> 
> Am i right on these lines.
> This is the setup
> 
> +------------+   eth0        +-----------+   internet
> | machine   |---------------|   Switch  |-------------
> +------------+                  +-----------+
> 
> trying to get some thing like this
> 
>                         root qdisc  (CBQ or something)
>                            /     \
>                          /         \
>                        /             \
>                      /                 \
>                class              class
> Internal LAN Pcakets        Any other unclassified Packets
>                  |                      |
>                  |                      |
>               FIFO             TBF (rate 64kbps)
> 
> Please Help me out with marking the packets and to classify them.
> Just started off with Traffic Shaping.  gigles...... : )
> 
> It is alos possible to alternatively to mark internet traffic as it 
> would be less in comparison to LAN and thus processor friendly.
> 
> Amit Vyas

I would use netfilter + HTB something like -

$TC qdisc add dev eth0 root handle 1:0 htb default 0
$TC class add dev eth0 parent 1:0 classid 1:1 htb rate 64kbit

$TC filter add dev eth0 parent 1:0 protocol ip handle 1 fw flowid 1:1

$IPTABLES -t mangle -A POSTROUTING -o eth0 --dst ! 192.168.0.0/24 -j 
MARK --set-mark 1

Depending on what the PC does it may be nicer to priorotise empty acks / 
udp headed for the internet over bulk traffic.

Andy.



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

      parent reply	other threads:[~2005-01-02  0:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-28 14:52 [LARTC] Simple case here! Amit Vyas
2004-12-29 11:41 ` Amit Vyas
2005-01-02  0:34 ` Andy Furniss [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=41D741AA.9090209@dsl.pipex.com \
    --to=andy.furniss@dsl.pipex.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