Subject: Re: tap0 device stopped working in 2.6.36 (ok in 2.6.35)

From: Jim <[email-masked]>
Date: Thu, 04 Nov 2010 21:17:59 +0100

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.