From: Jandre Olivier <jandre@megaserve.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Interfaces basic question
Date: Thu, 29 Sep 2005 10:31:31 +0000 [thread overview]
Message-ID: <433BC283.5000106@megaserve.net> (raw)
In-Reply-To: <2abc3335050929025264182ead@mail.gmail.com>
Hey Marius,
u can only run the qdisc per interface, so if u have "tc qdisc add dev
eth0 root handle 1: htb default 30" it will be applied to eth0:0 ,
eth0:1 aliases as well
U can shape on the one interface, your iptables commands must just be
very specific.
hope it helps
J
Marius Corici wrote:
> I have a router with only one physical ethernet cable. I know it's
> stupid, but it is the network I have to use for a demo.
> I have in mind to construct an HTB class tree for some network
> limitations for the outgoing traffic.
>
> The question is: can i use the HTB class mechanism on 2 subinterfaces
> of the same physical network card without any interference?
>
> Please let me know as soon as possible. I need to know if I start
> working on this or I have to change the hardware.
>
> Thank you,
>
> Marius
>
>------------------------------------------------------------------------
>
>_______________________________________________
>LARTC mailing list
>LARTC@mailman.ds9a.nl
>http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
>
>
--
Regards
Jandre
"One man's irritation is anothers bread and butter."
_____________________________________________________________________
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2005-09-29 10:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-29 9:52 [LARTC] Interfaces basic question Marius Corici
2005-09-29 10:11 ` Andreas Klauer
2005-09-29 10:31 ` Jandre Olivier [this message]
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=433BC283.5000106@megaserve.net \
--to=jandre@megaserve.net \
--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.