From: "Nicolas de Pesloüan" <nicolas.2p.debian@gmail.com>
To: Roya Kachooei <rkachooei@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: VLAN Question
Date: Sat, 29 Oct 2011 17:51:12 +0200 [thread overview]
Message-ID: <4EAC20F0.9060508@gmail.com> (raw)
In-Reply-To: <CANgyXsS=cE_ONExEuOvL7NEme1xCTM5s2Eek+oM6SXu_0g_bAQ@mail.gmail.com>
Le 29/10/2011 15:35, Roya Kachooei a écrit :
> Hi there
>
>
> My question is that is it possible to bond or aggregate two virtual
> interfaces created by VLAN?
>
> In other words is it possible to bond two virtual links for improving
> fail over and load balance?
If both virtual links are supported by the same physical link, nothing will improve.
That being said, some people used VLAN to provide end-to-end links, across one or several common
switches.
+-eth0-----vlan-100-----eth0-+
| |
bond0-+ +-bond0
| |
+-eth1-----vlan-200-----eth1-+
Nicolas.
prev parent reply other threads:[~2011-10-29 15:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-29 13:35 VLAN Question Roya Kachooei
2011-10-29 15:51 ` Nicolas de Pesloüan [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=4EAC20F0.9060508@gmail.com \
--to=nicolas.2p.debian@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=rkachooei@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).