From: "Jorge Dávila" <jorgedavilalopez@gmail.com>
To: Fabio Marcone <fabio.marcone@duet.it>
Cc: netfilter@vger.kernel.org
Subject: Re: tc and virtual interfaces
Date: Fri, 10 Jul 2009 07:56:03 -0600 [thread overview]
Message-ID: <bf0e93a30907100656o7388cbdbw984f3e90786033d5@mail.gmail.com> (raw)
In-Reply-To: <4A5747FC.1040509@duet.it>
The traffic shapping must be applied to the physical interface ( eth0
in this case).
Jorge Dávila.
On Fri, Jul 10, 2009 at 7:54 AM, Fabio Marcone<fabio.marcone@duet.it> wrote:
> thanks for your reply,
>>
>> eth0:0 is not an interface, it is an IPv4 alias on eth0. The real and only
>> interface here is eth0.
>
> ok, so I can't set up a queue on it, isn't it?
>
>>
>> tun0 is an interface on its own. However, if encapsulating traffic happens
>> to go through eth0, it will be affected by traffic shaping just as any other
>> traffic going through eth0.
>
> ok, and I can limit datarate on tun0 and on eth0 ? the first is applied only
> on vpn packets and the last on all eth0 outgoinig traffic I think...
>
>
> thanks,
> Fabio
> --
> To unsubscribe from this list: send the line "unsubscribe netfilter" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Jorge Isaac Dávila López
+505 8430 5462
jorgedavilalopez@gmail.com
---
Esta tierra es Linux. En las noches calladas puede escucharse a las
máquinas Windows re-iniciándose...
next prev parent reply other threads:[~2009-07-10 13:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-10 12:01 tc and virtual interfaces Fabio Marcone
2009-07-10 13:08 ` Pascal Hambourg
2009-07-10 13:54 ` Fabio Marcone
2009-07-10 13:56 ` Jorge Dávila [this message]
2009-07-10 14:00 ` Jorge Bastos
2009-07-10 14:06 ` Karel Rericha
2009-07-10 13:22 ` Jorge Dávila
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=bf0e93a30907100656o7388cbdbw984f3e90786033d5@mail.gmail.com \
--to=jorgedavilalopez@gmail.com \
--cc=fabio.marcone@duet.it \
--cc=netfilter@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