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: Tue, 30 Nov 2004 02:39:52 +0000	[thread overview]
Message-ID: <41ABDD78.2010007@dsl.pipex.com> (raw)
In-Reply-To: <20041109175203.11372.qmail@web41524.mail.yahoo.com>

Ricardo Soria wrote:

> 
> There may be traffic for a local (linux box) process,
> but the most of the traffic will be redirected or
> passed.
> 
> 
>>Do you want to shape eth0 aswell as the internet
>>link or is it OK for 
>>spare bandwidth?
>>
> 
> 
> I cannot translate/understand perfectly this question,
> but I do need to shape the internet link.

I didn't know if there was other (LAN) traffic that needed shaping 
aswell as internet traffic.

> 
> So, returning to the question that originated this
> discussion, how can I diferentiate/separate incoming
> and outgoing traffic for the same interface (eth0),
> without confusing each other, and without using IMQ
> devices if possible ??

If bulk transfers from internet to shaping box are rare enough for you 
not to care about them, then you can do without IMQ.

As for seperating traffic - in prerouting you should be able to mark 
traffic by source MAC address (1600) and the same in postrouting for 
destination MAC. You could then use the marks to send to different HTB 
classes that don't share.

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-30  2:39 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
2004-11-30  2:07 ` Ricardo Soria
2004-11-30  2:39 ` Andy Furniss [this message]
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=41ABDD78.2010007@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.