All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] SEPARATING VOIP AND SURFING
Date: Thu, 25 Nov 2004 10:48:19 +0000	[thread overview]
Message-ID: <41A5B873.40306@dsl.pipex.com> (raw)
In-Reply-To: <20041109175203.11372.qmail@web41524.mail.yahoo.com>

Ricardo Soria wrote:
> Well, as I promised, here I am again :-)
> 
> I have not got ESFQ yet, but what I think really
> helped was shorting bandwidth capacity to its 88%. 
> But here I have a new problem again:  there are
> certain moments when I am really running out of
> bandwidth.  The scenario now is as follows:
> 
> I am using my linux box as a router;  forwarding
> packages from on subnet to another.  But, since I have
> only one interface (eth0) for this purpose, both
> incoming and outgoing traffic passes for this
> interface.  So, I though it was correct to duplicate
> bandwidth capacity (512kbit * 88% = 450kbit * 2 > 900kbit), considering that I have 512kbit for uplink
> and 512 for downlink.  So, I am now considering a
> rate/ceil of 900kbit for eth0 on my script. 
> Everything appeared to be OK, But, since I did this
> change, there are certain moments that I run out of
> downlink bandwidth, so, I think the script is trying
> to take more thank the total 512 of downlink I have.
> 
> So, my question would be, how to 'divide' or
> 'recognize' incoming and outgoing traffic, and to
> treat it as different channels??  I was thinking about
> using a IMQ device for incoming traffic, but this
> apperas to be a 'little bit' more complicated that
> what I expected.  So, may it be a way to do this
> without installing IMQ ??

Yes you will need IMQ.

I assume you can mark traffic from/to the ciscos.

The detail depends on your exact setup - NAT, link speeds and type of 
link from ciscos etc.

Do you just wan't to shape traffic forwarded from internet to remote subnet?

Andy.


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

  parent reply	other threads:[~2004-11-25 10:48 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-09 17:52 [LARTC] SEPARATING VOIP AND SURFING Ricardo Soria
2004-11-15 12:42 ` Andy Furniss
2004-11-16  1:06 ` Ricardo Soria
2004-11-16  1:33 ` Jason Boxman
2004-11-16 14:53 ` Andy Furniss
2004-11-16 17:08 ` Jason Boxman
2004-11-17  1:15 ` Andy Furniss
2004-11-17 22:36 ` Ricardo Soria
2004-11-18  0:44 ` Andy Furniss
2004-11-18  1:08 ` Rick Marshall
2004-11-23 15:57 ` Ricardo Soria
2004-11-24 19:08 ` Ricardo Soria
2004-11-24 22:19 ` Ricardo Soria
2004-11-24 22:42 ` Rick Marshall
2004-11-25 10:48 ` Andy Furniss [this message]
2004-11-25 15:55 ` Andy Furniss
2004-11-28 23:50 ` Ricardo Soria
2004-11-29 21:53 ` Andy Furniss
2004-11-30  2:07 ` Ricardo Soria
2004-11-30  2:39 ` Andy Furniss
2004-11-30 12:23 ` Andy Furniss
2004-12-01 15:16 ` Ricardo Soria
2004-12-01 21:57 ` Andy Furniss
2004-12-06 22:54 ` Ricardo Soria

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=41A5B873.40306@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 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.