All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim <jim876@xs4all.nl>
To: Nolan Leake <nolan@cumulusnetworks.com>
Cc: netdev@vger.kernel.org
Subject: Re: tap0 device stopped working in 2.6.36 (ok in 2.6.35)
Date: Wed, 27 Oct 2010 18:09:17 +0200	[thread overview]
Message-ID: <4CC84EAD.7040506@xs4all.nl> (raw)
In-Reply-To: <1288142302.26640.7.camel@voxel>

On 10/27/2010 03:18 AM, Nolan Leake wrote:
> On Sun, 2010-10-24 at 11:59 +0200, Jim wrote:
>> Thanks for explaining the purpose of the patch.
>> But it appears something is missing and I think it breaks current
>> userspace. I use this tap0 device together with VirtualBox, I have a
>> virtual machine setup as bridged to tap0, not a very odd or strange
>> setup (this used to be the only method).
>> On the host side I run dhcpd to hand out IP address to the virtual
>> machine, but despite the dhcpd running on the tap0 device it never got
>> 'ready' in the sense that no IP packets made it out from the host to the
>> guest.
> 
> To make sure I understand the situation, is this correct (ignoring the
> exact names of the interfaces):
> br0 bridges between eth0 and tap0, and you run dhcpd on tap0?
> 
> Since tap0 is part of the bridge, I think dhcpd should be running on
> br0.  Does that work?
> 

Not exactly, VirtualBox calls it "bridged adapter", it 'bridges' the
guest machine to the tap0 interface on the host for so called host-only
networking.
See eg. http://forums.virtualbox.org/viewtopic.php?f=1&t=165

And this sequence is now simply failing
  tunctl -t tap0 -u tuxuser
  ifconfig tap0 10.0.0.1 up

Jim

  reply	other threads:[~2010-10-27 16:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-23 12:55 tap0 device stopped working in 2.6.36 (ok in 2.6.35) Jim
2010-10-23 19:39 ` Nolan Leake
2010-10-24  9:59   ` Jim
2010-10-27  1:18     ` Nolan Leake
2010-10-27 16:09       ` Jim [this message]
2010-10-27 17:48         ` Nolan Leake
2010-10-27 17:52           ` David Miller
2010-11-03 23:10         ` Nolan Leake
2010-11-04 20:17           ` Jim

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=4CC84EAD.7040506@xs4all.nl \
    --to=jim876@xs4all.nl \
    --cc=netdev@vger.kernel.org \
    --cc=nolan@cumulusnetworks.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.