From: William Thompson <wt@electro-mechanical.com>
To: Nicolas de Peslo?an <nicolas.2p.debian@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: Network problem with bridge and virtualbox
Date: Fri, 30 Sep 2011 10:36:03 -0400 [thread overview]
Message-ID: <20110930143603.GJ19871@electro-mechanical.com> (raw)
In-Reply-To: <4E84E9A7.4080008@gmail.com>
On Thu, Sep 29, 2011 at 11:56:55PM +0200, Nicolas de Peslo?an wrote:
> Le 29/09/2011 14:49, William Thompson a ?crit :
> >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.
>
> Why do you use bridge with VirtualBox?
>
> VirtualBox provide several network modes, which remove the need for bridge on the host.
>
> One of Bridged Network mode (using eth0), Internal Networking mode
> or Host-only Networking mode may suit your need well, without having
> to use a bridge.
I originally set this up as a hostonly (and routed) network. The bridge has
no other interfaces added to it. I know virtualbox has hostonly builtin, but
I did not want to use it's limited DHCP server and this was the only solution
I came up with at the time. Due to the way the vboxnet interfaces are
dynamically created, I didn't have a way at the time to start programs on
that interface when it came up.
next prev parent reply other threads:[~2011-09-30 14:36 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 [this message]
2011-10-01 0:18 ` Stephen Hemminger
2011-10-03 11:30 ` William Thompson
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=20110930143603.GJ19871@electro-mechanical.com \
--to=wt@electro-mechanical.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.2p.debian@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 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.