All of lore.kernel.org
 help / color / mirror / Atom feed
From: Raghuveer <raghuveer-rc@naturesoft.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] How to limit a dev bandwidth.
Date: Thu, 14 Aug 2003 10:57:38 +0000	[thread overview]
Message-ID: <marc-lartc-106085794930943@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106032592806296@msgid-missing>

Hi Stef,

You have mentioned in "
http://www.docum.org/stef.coene/qos/docs/BB/BB.html" that "It's very
important to understand that you can only shape outgoing traffic". So is
it not possible to shape the incomming traffic at all...? I already got
some useful links and suggestion from Martin for ingress mode. Can you
pls suggest how to do incomming traffic control, if the incomming
traffic hitting the firewall at WAN interface eth0 with LAN interface at
eth1. I would like to do traffic control based on LAN IP's and protocols
like HTTP, FTP, SMTP, POP etc, for incomming traffic only. Meanwhile Iam
going through the links send by Martin.

Regards
-Raghu



Stef Coene wrote:

>On Friday 08 August 2003 08:59, anzp wrote:
>  
>
>>The device is 100M.
>>How to limit it to 1M?
>>    
>>
>lartc.org
>docum.org
>
>Stef
>
>  
>


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

  parent reply	other threads:[~2003-08-14 10:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-08  6:59 [LARTC] How to limit a dev bandwidth anzp
2003-08-08 17:06 ` Stef Coene
2003-08-10  0:16 ` Martin A. Brown
2003-08-14 10:57 ` Raghuveer [this message]
2003-08-15  4:16 ` Martin A. Brown
2003-08-16  4:36 ` Madhuri Patwardhan
2003-08-16 17:18 ` Martin A. Brown
2003-08-16 18:43 ` Madhuri Patwardhan
2003-08-19  9:26 ` Raghuveer

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-106085794930943@msgid-missing \
    --to=raghuveer-rc@naturesoft.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.