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: Thu, 04 Nov 2010 21:17:59 +0100 [thread overview]
Message-ID: <4CD314F7.4070305@xs4all.nl> (raw)
In-Reply-To: <1288825835.26640.517.camel@voxel>
On 11/04/2010 12:10 AM, Nolan Leake wrote:
> On Wed, 2010-10-27 at 18:09 +0200, Jim wrote:
>> 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,
>
> Could you do me a favor and try this sequence:
> tunctl -t tap0 -u tuxuser
> <run virtualbox such that it attaches to tap0>
> ifconfig tap0 10.0.0.1 up
>
> Thanks,
> - nolan
>
Doesn't really work, virtualbox complaints loudly the tap0 device is
down, ignoring that after virtual machine is up-n-running, the
ifconfig tap0 192.168.20.1 up
still gives ADDRCONF(NETDEV_UP): tap0: link is not ready
Using wireshark I see guest machine is sending dhcp request but no
message is sent out from the host as before.
prev parent reply other threads:[~2010-11-04 20:18 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
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 [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=4CD314F7.4070305@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.