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: Mon, 29 Nov 2004 21:53:32 +0000	[thread overview]
Message-ID: <41AB9A5C.1000109@dsl.pipex.com> (raw)
In-Reply-To: <20041109175203.11372.qmail@web41524.mail.yahoo.com>

Ricardo Soria wrote:
>  --- Andy Furniss <andy.furniss@dsl.pipex.com>
> escribió: 
> 
>>Andy Furniss wrote:
>>
>>
>>>>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.
>>
>>Second thoughts - you may be able to do without IMQ
>>as long as it's just 
>>forwarded traffic.
>>
>>Andy.
>>
>> 
> 
> 
> Andy:
> 
> What I am exactly doing is this:  I receive all
> traffic from the cisco 1600, then,
> filter/shape/monitor it, then, if this traffic is
> destined to the remote subnet, it is send to the cisco
> 827, but, if the traffic is for the local subnet
> (including both ciscos, and the linux box),

The only thing you would need IMQ for is if you need to shape traffic 
from the 1600 to a local process on the linux box - so you may - it 
depends on what else you are running on the shaping box that causes bulk 
traffic to it.


  it is
> directly delivered to its destination.  All of this is
> done via eth0, as much outgoing as incoming traffic. 
> So, specially cosidering about the local subnet, do
> you think I should definitively use IMQ or not??

If eth0 has as much incoming as outgoing then there is no traffic to 
local process?

Do you want to shape eth0 aswell as the internet link or is it OK for 
spare bandwidth?

Andy.


> 
> However, I have also posted in linuximq list, because
> I cannot find IMQ patch for my linux box (Redhat 7.3,
> 2.4.18-3 Kernel)
> 
> Very thanks in advance.
> 
> Ricardo.
> 
> _________________________________________________________
> Do You Yahoo!?
> Información de Estados Unidos y América Latina, en Yahoo! Noticias.
> Visítanos en http://noticias.espanol.yahoo.com
> 


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

  parent reply	other threads:[~2004-11-29 21:53 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
2004-11-25 15:55 ` Andy Furniss
2004-11-28 23:50 ` Ricardo Soria
2004-11-29 21:53 ` Andy Furniss [this message]
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=41AB9A5C.1000109@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.