From: "Aron Brand" <Aron@sofaware.com>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] virtual interface
Date: Mon, 05 Jan 2004 09:14:38 +0000 [thread overview]
Message-ID: <50F73B338A7FD943B7937BBCF99BFBDE2DADBF@mail.sofaware.com> (raw)
In-Reply-To: <001601c3d348$25749810$b8a14150@dijana>
>Alen,
>
> : can i add HTB rule on virtual interface?
> : example: eth0:0
>
>First, it's not really a virtual interface--it's just a convention from
the old days of IP aliasing to have names like eth0:0.
> The IP exists and is active on an interface, eth0 in your case.
> The short answer is "no". Traffic control occurs just prior to the
release of the packet for transmission by the hardware driver. See the
KPTD [0].
>
> You can however select packets based on many characteristics, so you
may be able to accomplish what you need. You'll use characteristics
other than the
> label "eth0:0".
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/
next prev parent reply other threads:[~2004-01-05 9:14 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 [this message]
2004-01-05 14:29 ` Roy
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=50F73B338A7FD943B7937BBCF99BFBDE2DADBF@mail.sofaware.com \
--to=aron@sofaware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox