From: William Thompson <wt@electro-mechanical.com>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: netdev@vger.kernel.org
Subject: Re: Network problem with bridge and virtualbox
Date: Mon, 3 Oct 2011 07:30:44 -0400 [thread overview]
Message-ID: <20111003113044.GR19871@electro-mechanical.com> (raw)
In-Reply-To: <20110930171839.2893bfa6@nehalam.linuxnetplumber.net>
On Fri, Sep 30, 2011 at 05:18:39PM -0700, Stephen Hemminger wrote:
> On Thu, 29 Sep 2011 08:49:41 -0400
> William Thompson <wt@electro-mechanical.com> wrote:
>
> > Please keep me in the CC as I am not subscribed.
> >
> > I'm using a 64-bit kernel 3.0.0 and virtualbox 4.1.2.
> >
> > My problem is that I cannot ping the host from a virtual machine.
> >
> > My bridge is configured as follows:
> > # brctl addbr br0
> > # brctl setfd br0 0
> > # brctl stp br0 off
> > # ifconfig br0 10.2.3.1 netmask 255.255.255.0
> >
> > In the virtual machine, it is set to use br0 as it's interface (bridge mode)
> > and it's IP is 10.2.3.10.
> >
> > The host gets packets from the vm, but the vm does not receive packets back.
> >
> > I have this same setup working on a 32-bit kernel 2.6.38.6 on another
> > machine with virtualbox 4.0.4.
> >
> > I had a thought that the bridge on the host wasn't responding due to having
> > no ports configured so I added one of my spare ethernet cards to it as
> > follows:
> > # brctl addif br0 eth1
> > # ifconfig eth1 up
> >
> > The card was plugged into a switch. After doing this, the vm still could not
> > talk to the host. I added a physical machine to the switch that eth1 was
> > connected to and configured it to 10.2.3.2. I was able to ping 10.2.3.2 but
> > not 10.2.3.1
>
> Did you add any interface to the bridge?
Initially, no.
> I think you were bit by the change in carrier behavior. No carrier on the
> bridge interface tracks the union of the devices in the bridge.
> Several people have been using bridge in strange way (as a dummy device)
> with no physical interfaces and some applications are checking for carrier.
That's how I have been using it.
Using it as a dummy, ie no interfaces added to the bridge, on 3.0.0 I was
unable to communicate with the host from the VM. I added eth1 to it. This
has a link to a physical network. I assigned IPs to the host and the VM to
be on the same network that eth1 was attached. From the VM I could
communicate with devices on the physical network but not the host. The host
could also communicate with the other devices.
prev parent reply other threads:[~2011-10-03 11:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 12:49 Network problem with bridge and virtualbox William Thompson
2011-09-29 21:56 ` Nicolas de Pesloüan
2011-09-30 14:36 ` William Thompson
2011-10-01 0:18 ` Stephen Hemminger
2011-10-03 11:30 ` William Thompson [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=20111003113044.GR19871@electro-mechanical.com \
--to=wt@electro-mechanical.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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 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.