From: "Julián Muñoz" <jmunoz@telefonica.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] In & out traffic
Date: Mon, 08 Apr 2002 17:52:16 +0000 [thread overview]
Message-ID: <marc-lartc-101828846806753@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101828667204749@msgid-missing>
Hello, yes this is possible, this is called "ingress policy".
Take a look at the lartc doc, at the end there is somo cookbook examples.
I had it working. You can limit the incoming traffic "killing" some
packets.
Very recently on the list was also published the new IMQ device, which can
do advanced traffic shapping over incoming traffic.
On the other hand, I don't know if in case of semi-duplex mediums, where
the real bandwidth is shared between reception and transmition, it is
possible to limit this real bandwidth (transmit bandwidth dependent of
receive bandwidth). Maybe IMQ is also the solution, I don't know.
On Mon, 8 Apr 2002, Ali badilli wrote:
>
> Hi all,
>
> I have the following test-bed.
>
> A-----B-----C
>
> Router A,B, and C. Router A has eth0, B has eth0 and
> eth1, and C has eth0.
>
> I can apply TC functions in B (eth0) for traffic
> coming from A, for example limit the link BW to 5Mb
> and divide among multiple clasess. Now, I want to the
> same thing for traffic coming from C and going to A. I
> can have similar action for traffic coming from C in
> eth1. However, it seems the link capacity allocated in
> eth0 is only for incoming traffic (from A), how can I
> specify link capacity for incoming and outgoing
> traffic separately.
>
> In Howto document it seems, all the examples for the
> traffic for outgoing from one interface, Is tehre any
> way to divide the link for incoming and outgoing
> traffic, and apply tc function separately.
>
> Thanks in advance
> Haci
>
>
>
>
>
>
>
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Tax Center - online filing with TurboTax
> http://taxes.yahoo.com/
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
--
__o
_ \<_
(_)/(_)
Saludos de Julián
EA4ACL
-.-
Foro Wireless Madrid
http://opennetworks.rg3.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-04-08 17:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-08 17:23 [LARTC] In & out traffic Ali badilli
2002-04-08 17:52 ` Julián Muñoz [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-101828846806753@msgid-missing \
--to=jmunoz@telefonica.net \
--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.