All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roy" <roy@xxx.lt>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] virtual interface
Date: Mon, 05 Jan 2004 14:29:40 +0000	[thread overview]
Message-ID: <002701c3d398$5be4b1f0$030aa8c0@t> (raw)
In-Reply-To: <001601c3d348$25749810$b8a14150@dijana>

There is no need to use imq ant everything is easy to do anyway
interface name is usefull only to attach qdisc to something and that all
you need to clasify packets by source or destination ip antway

if you have idea how to use imq there then just use your interface instead.
also why it is so obvious that they must be shaped separately, ususly it is
much better to shape everything in one einterface


Hi guys,

I have this problem too. I have two Internet routers connected to the
same Ethernet interface (using a hub). And each one obviously needs to
be shaped seperately. It seems like a very common and logical scenario
and this issue seems like a design problem.
Any Ideas on a workaround? Perhaps IMQ can be used somehow (although I
hear it has serious stability problems...)?

Aron


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

  parent reply	other threads:[~2004-01-05 14:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-04 20:17 [LARTC] virtual interface alen sarkinovic
2004-01-04 20:36 ` Stef Coene
2004-01-04 20:40 ` Martin A. Brown
2004-01-05  9:14 ` Aron Brand
2004-01-05 14:29 ` Roy [this message]
2006-02-02 12:33 ` [LARTC] Virtual Interface Roger Singh
2006-02-02 18:08 ` Ryan Castellucci
2006-02-03 15:17 ` Roger Singh
  -- strict thread matches above, loose matches on Subject: below --
2006-02-03 18:48 [lartc] " list user
2006-02-07 13:23 ` Roger Singh

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='002701c3d398$5be4b1f0$030aa8c0@t' \
    --to=roy@xxx.lt \
    --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.