All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arun Khan <knura9@gmail.com>
To: Linux Bridge <bridge@lists.linux-foundation.org>
Subject: Re: [Bridge] Packet "leakage" between two bridges
Date: Fri, 28 Jan 2011 10:39:24 +0530	[thread overview]
Message-ID: <AANLkTimwB1pGHPQ6j6joQB0TSxpGW4P8kBSahpQ6amL1@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikQtHi15t9hSck8-p-fhf3QNXfY02PwxQ_4tSNW@mail.gmail.com>

Ben and Jarrod thanks very much for sharing your thoughts.   I will
try Jarrod's suggestion first.

On Fri, Jan 28, 2011 at 2:02 AM, J L <lists@rrod.net> wrote:

> You have assumed (as I did, when I first tried this) that the first
> "-net nic" and "-net tap" are automatically associated with each
> other. They aren't - you have to tell KVM explicitly.

Yes, I had assumed the implicit association.

> I find it easiest to think of it as if there was a (in your example
> here) *four* port switch inside the KVM process - with two ports
> connected to the host, and two to the guests.
>
> Like a real switch, in order to run two networks through it, you need
> to VLAN it.
> Add "vlan=1" to your first pair of "-net"'s, and "vlan=2" to the other.

Although the usage of VLAN is documented in the kvm man page, this did
not strike me because my mind was set with the above assumption :)
I will give it a shot and post my results here.

Thanks again.
-- Arun Khan

  reply	other threads:[~2011-01-28  5:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-27 19:52 [Bridge] Packet "leakage" between two bridges Arun Khan
2011-01-27 20:20 ` Ben Greear
2011-01-27 20:32 ` J L
2011-01-28  5:09   ` Arun Khan [this message]
2011-01-28 11:08     ` Arun Khan

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=AANLkTimwB1pGHPQ6j6joQB0TSxpGW4P8kBSahpQ6amL1@mail.gmail.com \
    --to=knura9@gmail.com \
    --cc=bridge@lists.linux-foundation.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.