<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Host Networking with VirtualBox on Ubuntu 7.04 Feisty</title>
	<atom:link href="http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/</link>
	<description>Markus Bertheau, Software developer</description>
	<lastBuildDate>Thu, 01 Sep 2011 15:52:42 +0200</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: doez</title>
		<link>http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/comment-page-1/#comment-59717</link>
		<dc:creator>doez</dc:creator>
		<pubDate>Tue, 24 Feb 2009 09:00:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/#comment-59717</guid>
		<description>thank&#039;s</description>
		<content:encoded><![CDATA[<p>thank&#8217;s</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: saurabh</title>
		<link>http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/comment-page-1/#comment-53201</link>
		<dc:creator>saurabh</dc:creator>
		<pubDate>Mon, 10 Nov 2008 15:26:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/#comment-53201</guid>
		<description>update: actually it is intel pro1000 MT network adapter</description>
		<content:encoded><![CDATA[<p>update: actually it is intel pro1000 MT network adapter</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: saurabh</title>
		<link>http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/comment-page-1/#comment-53181</link>
		<dc:creator>saurabh</dc:creator>
		<pubDate>Mon, 10 Nov 2008 01:58:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/#comment-53181</guid>
		<description>I have followed each step as in the guide and then started my VM running windowsxp. After that i intalled driver for intel pro100 MT network adapter.It then started to configure the ip but failed with limited connectivity .I then tried to configure it manually to 192.168.0.1 but still no connectivity...Please help me with this problem ASAP as i need to run some &quot;cant do without&quot; application in windows to connect to the internet.</description>
		<content:encoded><![CDATA[<p>I have followed each step as in the guide and then started my VM running windowsxp. After that i intalled driver for intel pro100 MT network adapter.It then started to configure the ip but failed with limited connectivity .I then tried to configure it manually to 192.168.0.1 but still no connectivity&#8230;Please help me with this problem ASAP as i need to run some &#8220;cant do without&#8221; application in windows to connect to the internet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Markus Bertheau</title>
		<link>http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/comment-page-1/#comment-53152</link>
		<dc:creator>Markus Bertheau</dc:creator>
		<pubDate>Sun, 09 Nov 2008 12:43:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/#comment-53152</guid>
		<description>No idea.</description>
		<content:encoded><![CDATA[<p>No idea.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthias</title>
		<link>http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/comment-page-1/#comment-53151</link>
		<dc:creator>Matthias</dc:creator>
		<pubDate>Sun, 09 Nov 2008 12:39:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/#comment-53151</guid>
		<description>Great work, many thanks, does it works with Ibex without modifications too?</description>
		<content:encoded><![CDATA[<p>Great work, many thanks, does it works with Ibex without modifications too?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J</title>
		<link>http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/comment-page-1/#comment-52095</link>
		<dc:creator>J</dc:creator>
		<pubDate>Mon, 27 Oct 2008 15:52:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/#comment-52095</guid>
		<description>This description beats all others I have found because it is so logically structured and best of it all: it works.

It made clear, that the bridge has the exact settings as the eth0 interface it bridges to and also how to configure the guest Network settings (as a normal physical machine).

My configuration: Host: Ubuntu 8.04.1, Guest: XP SP2
Host can ping guest and vice versa. Host can see shared files from guest and guest can work with samba share from host! 

Thanks a lot.</description>
		<content:encoded><![CDATA[<p>This description beats all others I have found because it is so logically structured and best of it all: it works.</p>
<p>It made clear, that the bridge has the exact settings as the eth0 interface it bridges to and also how to configure the guest Network settings (as a normal physical machine).</p>
<p>My configuration: Host: Ubuntu 8.04.1, Guest: XP SP2<br />
Host can ping guest and vice versa. Host can see shared files from guest and guest can work with samba share from host! </p>
<p>Thanks a lot.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Pfeifer</title>
		<link>http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/comment-page-1/#comment-40087</link>
		<dc:creator>Aaron Pfeifer</dc:creator>
		<pubDate>Sun, 15 Jun 2008 07:44:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/#comment-40087</guid>
		<description>Thanks so much for this guide.  It was, by far, the best and most clear instructions of any that I had run across and worked perfectly on the first shot.</description>
		<content:encoded><![CDATA[<p>Thanks so much for this guide.  It was, by far, the best and most clear instructions of any that I had run across and worked perfectly on the first shot.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cOnf_ua</title>
		<link>http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/comment-page-1/#comment-39329</link>
		<dc:creator>cOnf_ua</dc:creator>
		<pubDate>Tue, 03 Jun 2008 13:26:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/#comment-39329</guid>
		<description>Oh, i solved this problem!
The solution was to set intel host interface and setup drivers :)
Thx again!</description>
		<content:encoded><![CDATA[<p>Oh, i solved this problem!<br />
The solution was to set intel host interface and setup drivers :)<br />
Thx again!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cOnf_ua</title>
		<link>http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/comment-page-1/#comment-38491</link>
		<dc:creator>cOnf_ua</dc:creator>
		<pubDate>Fri, 23 May 2008 15:26:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/#comment-38491</guid>
		<description>when i look at status of Network Connection - there are none of packets received and some amount of packets sent.</description>
		<content:encoded><![CDATA[<p>when i look at status of Network Connection &#8211; there are none of packets received and some amount of packets sent.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cOnf_ua</title>
		<link>http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/comment-page-1/#comment-38488</link>
		<dc:creator>cOnf_ua</dc:creator>
		<pubDate>Fri, 23 May 2008 15:02:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/#comment-38488</guid>
		<description>I have done all this staff on host Ubuntu.
My ubuntu guests work perfectly in network, so thx a lot.
But!!!
In the same time, my windows XP guests dont see anything in network except themselves((( Even internal network dont work. What should be done?</description>
		<content:encoded><![CDATA[<p>I have done all this staff on host Ubuntu.<br />
My ubuntu guests work perfectly in network, so thx a lot.<br />
But!!!<br />
In the same time, my windows XP guests dont see anything in network except themselves((( Even internal network dont work. What should be done?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Smylie</title>
		<link>http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/comment-page-1/#comment-38280</link>
		<dc:creator>Dave Smylie</dc:creator>
		<pubDate>Wed, 21 May 2008 19:40:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/#comment-38280</guid>
		<description>Just fyi for any others having issues with host networking. . . 
I was unable to get any connectivity between the host and my windows xp guest using the default network card. Changing to one of the other virtual network cards in vbox guest settings fixed this.

Cheers
Dave Smylie</description>
		<content:encoded><![CDATA[<p>Just fyi for any others having issues with host networking. . .<br />
I was unable to get any connectivity between the host and my windows xp guest using the default network card. Changing to one of the other virtual network cards in vbox guest settings fixed this.</p>
<p>Cheers<br />
Dave Smylie</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pmorton</title>
		<link>http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/comment-page-1/#comment-36054</link>
		<dc:creator>pmorton</dc:creator>
		<pubDate>Tue, 29 Apr 2008 16:18:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/#comment-36054</guid>
		<description>Many thanks for setting that out so clearly and concisely.  By the time you&#039;ve read through a 50-thread discussion of blind-leading-blind, with a tricky issue  like this, your head is spinning. So its a great relief to get a well-defined method that just works. Well done.</description>
		<content:encoded><![CDATA[<p>Many thanks for setting that out so clearly and concisely.  By the time you&#8217;ve read through a 50-thread discussion of blind-leading-blind, with a tricky issue  like this, your head is spinning. So its a great relief to get a well-defined method that just works. Well done.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Seabass</title>
		<link>http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/comment-page-1/#comment-34782</link>
		<dc:creator>Seabass</dc:creator>
		<pubDate>Sun, 13 Apr 2008 07:35:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/#comment-34782</guid>
		<description>I have followed the instructions. Upon restarting my network I get an error message stating the br0 bridge was not found. Any suggestions?


Thanks</description>
		<content:encoded><![CDATA[<p>I have followed the instructions. Upon restarting my network I get an error message stating the br0 bridge was not found. Any suggestions?</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shivagit</title>
		<link>http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/comment-page-1/#comment-34566</link>
		<dc:creator>Shivagit</dc:creator>
		<pubDate>Thu, 10 Apr 2008 05:46:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/#comment-34566</guid>
		<description>Thank you.  I like the way you&#039;ve broken the instructions up into sections.  It helped me more clearly see the logic of how it&#039;s configured.</description>
		<content:encoded><![CDATA[<p>Thank you.  I like the way you&#8217;ve broken the instructions up into sections.  It helped me more clearly see the logic of how it&#8217;s configured.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mr. Shiney</title>
		<link>http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/comment-page-1/#comment-33624</link>
		<dc:creator>Mr. Shiney</dc:creator>
		<pubDate>Sat, 29 Mar 2008 05:25:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/#comment-33624</guid>
		<description>You rock for posting this. I have viewed at least twenty posts on this subject and fuxored my network settings at least four times -- yours is the first solution that worked. Kudos, sir!</description>
		<content:encoded><![CDATA[<p>You rock for posting this. I have viewed at least twenty posts on this subject and fuxored my network settings at least four times &#8212; yours is the first solution that worked. Kudos, sir!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon</title>
		<link>http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/comment-page-1/#comment-32828</link>
		<dc:creator>Simon</dc:creator>
		<pubDate>Tue, 18 Mar 2008 13:20:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/#comment-32828</guid>
		<description>Hi, 

Worked first time even though I am using the AMD64 bit version. Great stuff.

Thanks for posting it.

-- 
Simon.</description>
		<content:encoded><![CDATA[<p>Hi, </p>
<p>Worked first time even though I am using the AMD64 bit version. Great stuff.</p>
<p>Thanks for posting it.</p>
<p>--<br />
Simon.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frikkie Thirion</title>
		<link>http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/comment-page-1/#comment-30955</link>
		<dc:creator>Frikkie Thirion</dc:creator>
		<pubDate>Tue, 26 Feb 2008 09:39:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/#comment-30955</guid>
		<description>Good day,
I would like to provide a detailed post of settings on my machine and would appreciate it if anybody can give me some insight into why my tap0 interface isn&#039;t transmitting any data.
I&#039;ve managed to get NAT networking going and my Guest OS is happily communicating. The trouble seems to be with the &#039;Host networking&#039; setup.

VirtualBox configuration (1.5.6-28241_Ubuntu_gutsy) on Kubuntu (ubuntu 7.10)

Guest OS
  Windows XP, sp2
  Network settings: Set to DHCP, firewalled 
  (NAT from guest to host works fine)


# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

#auto eth1
#iface eth1 inet dhcp

#auto eth2
#iface eth2 inet dhcp

#auto ath0
#iface ath0 inet dhcp

#auto wlan0
#iface wlan0 inet dhcp

auto tap0
iface tap0 inet manual
tunctl_user frix
#Ed:15 is the adress issued to eth0 via dhcp
uml_proxy_arp 192.168.10.15  
uml_proxy_ether eth0

auto br0
iface br0 inet dhcp
bridge_ports eth0 tap0
bridge_maxwait 0


# ifconfig
br0       
Link encap:Ethernet  
HWaddr 00:16:E6:16:03:9C
inet addr:192.168.10.15  
Bcast:192.168.10.255  
Mask:255.255.255.0
inet6 addr: fe80::216:e6ff:fe16:39c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:163 errors:0 dropped:0 overruns:0 
frame:0 TX packets:27 errors:0 dropped:0 
overruns:0 carrier:0 collisions:0 txqueuelen:0
RX bytes:13829 (13.5 KB)  TX bytes:3118 (3.0 KB)

eth0      
Link encap:Ethernet
HWaddr 00:16:E6:16:03:9C
inet6 addr: fe80::216:e6ff:fe16:39c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:743408 errors:0 dropped:0 overruns:0 
frame:0 TX packets:364349 errors:0 dropped:0 
overruns:0 carrier:0 collisions:0 txqueuelen:1000
RX bytes:942876440 (899.1 MB)  TX bytes:93147181 
(88.8 MB) Interrupt:21 Base address:0xc800

lo
Link encap:Local Loopback
inet addr:127.0.0.1  Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING  MTU:16436  Metric:1
RX packets:16724 errors:0 dropped:0 overruns:0 
frame:0 TX packets:16724 errors:0 dropped:0 
overruns:0 carrier:0 collisions:0 txqueuelen:0
RX bytes:79485844 (75.8 MB)  TX bytes:79485844 
(75.8 MB) 

tap0      
Link encap:Ethernet  HWaddr 00:FF:5E:00:68:74
inet6 addr: fe80::2ff:5eff:fe00:6874/64 Scope:Link
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:294 errors:0 dropped:0 overruns:0 
frame:0 TX packets:4 errors:0 dropped:1127 
overruns:0 carrier:0 collisions:0 txqueuelen:500
RX bytes:42941 (41.9 KB)  TX bytes:240 (240.0 b)

# netstat -rn
Kernel IP routing table Destination     Gateway         Genmask         Flags   MSS Window      irtt
Iface
192.168.10.15 0.0.0.0 255.255.255.255 
UH        0 0          0               tap0

192.168.10.0  0.0.0.0 255.255.255.0   
U         0 0          0               br0

0.0.0.0       192.168.10.1    0.0.0.0
UG        0 0          0               br0

# iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination


# ls -sal /dev/net/tun
0 crw-rw---- 1 root vboxusers 10, 200 
  2008-01-10 19:18 /dev/net/tun

# cat /etc/group
...
vboxusers:x:113:frix
...

VirtualBox setup:
Network:
  Adapter 0
  Enable Network Adapter: Checked
  Adapter Type: PCnet-FAST III (Am79C973)
  Attached to: Host Interface
  Network Name: 
  MAC Address: 00FF5E006874 
  (Ed: Tried to set it to the same value as tap0
       and have it auto generated, neither making 
       any difference)
  Cable Connected: Checked

  Host Interface Settings:
   Interface Name: tap0
   Setup Application: 
   Terminate Application: 




Testing with an IP adres on tap0:
# ifconfig tap0 192.168.10.100 up
# ifconfig tap0
tap0      
Link encap:Ethernet  
HWaddr 00:FF:40:52:E4:03
inet addr:192.168.10.100  
Bcast:192.168.10.255  
Mask:255.255.255.0
inet6 addr: fe80::2ff:40ff:fe52:e403/64 
Scope:Link UP BROADCAST RUNNING MULTICAST  MTU:1500 
Metric:1 RX packets:0 errors:0 dropped:0 overruns:0
frame:0 TX packets:0 errors:0 dropped:192 
overruns:0 carrier:0 collisions:0 txqueuelen:500
RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

# netstat -rn
Kernel IP routing table Destination     Gateway        
Genmask         Flags   MSS Window  irtt Iface
192.168.10.0  0.0.0.0 255.255.255.0
U         0 0          0             tap0
192.168.10.0  0.0.0.0 255.255.255.0   
U         0 0          0             br0
0.0.0.0       192.168.10.1 0.0.0.0         
UG        0 0          0             br0

# iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

# ping -I br0 192.168.10.1
PING 192.168.10.1 (192.168.10.1) from 192.168.10.15 br0: 56(84) bytes of data.
64 bytes from 192.168.10.1: icmp_seq=1 ttl=255 time=2.49 ms
64 bytes from 192.168.10.1: icmp_seq=2 ttl=255 time=0.595 ms

# ping -I tap0 192.168.10.1
PING 192.168.10.1 (192.168.10.1) from 192.168.10.100 tap0: 56(84) bytes of data.
From 192.168.10.100 icmp_seq=1 Destination Host Unreachable

The tap0 interface itself at the moment can&#039;t see the rest of my local LAN - I guess getting this to work will solve a lot of the problems already.

Note: I&#039;ve also tested the tap0 interface with
/proc/sys/net/ipv4/ip_forward == 1 and ...==0, 
making no difference to the connectivity.

Any help would be appreciated.
Regards,
-frix</description>
		<content:encoded><![CDATA[<p>Good day,<br />
I would like to provide a detailed post of settings on my machine and would appreciate it if anybody can give me some insight into why my tap0 interface isn&#8217;t transmitting any data.<br />
I&#8217;ve managed to get NAT networking going and my Guest OS is happily communicating. The trouble seems to be with the &#8216;Host networking&#8217; setup.</p>
<p>VirtualBox configuration (1.5.6-28241_Ubuntu_gutsy) on Kubuntu (ubuntu 7.10)</p>
<p>Guest OS<br />
  Windows XP, sp2<br />
  Network settings: Set to DHCP, firewalled<br />
  (NAT from guest to host works fine)</p>
<p># cat /etc/network/interfaces<br />
auto lo<br />
iface lo inet loopback</p>
<p>auto eth0<br />
iface eth0 inet dhcp</p>
<p>#auto eth1<br />
#iface eth1 inet dhcp</p>
<p>#auto eth2<br />
#iface eth2 inet dhcp</p>
<p>#auto ath0<br />
#iface ath0 inet dhcp</p>
<p>#auto wlan0<br />
#iface wlan0 inet dhcp</p>
<p>auto tap0<br />
iface tap0 inet manual<br />
tunctl_user frix<br />
#Ed:15 is the adress issued to eth0 via dhcp<br />
uml_proxy_arp 192.168.10.15<br />
uml_proxy_ether eth0</p>
<p>auto br0<br />
iface br0 inet dhcp<br />
bridge_ports eth0 tap0<br />
bridge_maxwait 0</p>
<p># ifconfig<br />
br0<br />
Link encap:Ethernet<br />
HWaddr 00:16:E6:16:03:9C<br />
inet addr:192.168.10.15<br />
Bcast:192.168.10.255<br />
Mask:255.255.255.0<br />
inet6 addr: fe80::216:e6ff:fe16:39c/64 Scope:Link<br />
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1<br />
RX packets:163 errors:0 dropped:0 overruns:0<br />
frame:0 TX packets:27 errors:0 dropped:0<br />
overruns:0 carrier:0 collisions:0 txqueuelen:0<br />
RX bytes:13829 (13.5 KB)  TX bytes:3118 (3.0 KB)</p>
<p>eth0<br />
Link encap:Ethernet<br />
HWaddr 00:16:E6:16:03:9C<br />
inet6 addr: fe80::216:e6ff:fe16:39c/64 Scope:Link<br />
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1<br />
RX packets:743408 errors:0 dropped:0 overruns:0<br />
frame:0 TX packets:364349 errors:0 dropped:0<br />
overruns:0 carrier:0 collisions:0 txqueuelen:1000<br />
RX bytes:942876440 (899.1 MB)  TX bytes:93147181<br />
(88.8 MB) Interrupt:21 Base address:0xc800</p>
<p>lo<br />
Link encap:Local Loopback<br />
inet addr:127.0.0.1  Mask:255.0.0.0<br />
inet6 addr: ::1/128 Scope:Host<br />
UP LOOPBACK RUNNING  MTU:16436  Metric:1<br />
RX packets:16724 errors:0 dropped:0 overruns:0<br />
frame:0 TX packets:16724 errors:0 dropped:0<br />
overruns:0 carrier:0 collisions:0 txqueuelen:0<br />
RX bytes:79485844 (75.8 MB)  TX bytes:79485844<br />
(75.8 MB) </p>
<p>tap0<br />
Link encap:Ethernet  HWaddr 00:FF:5E:00:68:74<br />
inet6 addr: fe80::2ff:5eff:fe00:6874/64 Scope:Link<br />
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1<br />
RX packets:294 errors:0 dropped:0 overruns:0<br />
frame:0 TX packets:4 errors:0 dropped:1127<br />
overruns:0 carrier:0 collisions:0 txqueuelen:500<br />
RX bytes:42941 (41.9 KB)  TX bytes:240 (240.0 b)</p>
<p># netstat -rn<br />
Kernel IP routing table Destination     Gateway         Genmask         Flags   MSS Window      irtt<br />
Iface<br />
192.168.10.15 0.0.0.0 255.255.255.255<br />
UH        0 0          0               tap0</p>
<p>192.168.10.0  0.0.0.0 255.255.255.0<br />
U         0 0          0               br0</p>
<p>0.0.0.0       192.168.10.1    0.0.0.0<br />
UG        0 0          0               br0</p>
<p># iptables -L<br />
Chain INPUT (policy ACCEPT)<br />
target     prot opt source               destination</p>
<p>Chain FORWARD (policy ACCEPT)<br />
target     prot opt source               destination</p>
<p>Chain OUTPUT (policy ACCEPT)<br />
target     prot opt source               destination</p>
<p># ls -sal /dev/net/tun<br />
0 crw-rw&#8212;- 1 root vboxusers 10, 200<br />
  2008-01-10 19:18 /dev/net/tun</p>
<p># cat /etc/group<br />
&#8230;<br />
vboxusers:x:113:frix<br />
&#8230;</p>
<p>VirtualBox setup:<br />
Network:<br />
  Adapter 0<br />
  Enable Network Adapter: Checked<br />
  Adapter Type: PCnet-FAST III (Am79C973)<br />
  Attached to: Host Interface<br />
  Network Name:<br />
  MAC Address: 00FF5E006874<br />
  (Ed: Tried to set it to the same value as tap0<br />
       and have it auto generated, neither making<br />
       any difference)<br />
  Cable Connected: Checked</p>
<p>  Host Interface Settings:<br />
   Interface Name: tap0<br />
   Setup Application:<br />
   Terminate Application: </p>
<p>Testing with an IP adres on tap0:<br />
# ifconfig tap0 192.168.10.100 up<br />
# ifconfig tap0<br />
tap0<br />
Link encap:Ethernet<br />
HWaddr 00:FF:40:52:E4:03<br />
inet addr:192.168.10.100<br />
Bcast:192.168.10.255<br />
Mask:255.255.255.0<br />
inet6 addr: fe80::2ff:40ff:fe52:e403/64<br />
Scope:Link UP BROADCAST RUNNING MULTICAST  MTU:1500<br />
Metric:1 RX packets:0 errors:0 dropped:0 overruns:0<br />
frame:0 TX packets:0 errors:0 dropped:192<br />
overruns:0 carrier:0 collisions:0 txqueuelen:500<br />
RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)</p>
<p># netstat -rn<br />
Kernel IP routing table Destination     Gateway<br />
Genmask         Flags   MSS Window  irtt Iface<br />
192.168.10.0  0.0.0.0 255.255.255.0<br />
U         0 0          0             tap0<br />
192.168.10.0  0.0.0.0 255.255.255.0<br />
U         0 0          0             br0<br />
0.0.0.0       192.168.10.1 0.0.0.0<br />
UG        0 0          0             br0</p>
<p># iptables -L<br />
Chain INPUT (policy ACCEPT)<br />
target     prot opt source               destination</p>
<p>Chain FORWARD (policy ACCEPT)<br />
target     prot opt source               destination</p>
<p>Chain OUTPUT (policy ACCEPT)<br />
target     prot opt source               destination</p>
<p># ping -I br0 192.168.10.1<br />
PING 192.168.10.1 (192.168.10.1) from 192.168.10.15 br0: 56(84) bytes of data.<br />
64 bytes from 192.168.10.1: icmp_seq=1 ttl=255 time=2.49 ms<br />
64 bytes from 192.168.10.1: icmp_seq=2 ttl=255 time=0.595 ms</p>
<p># ping -I tap0 192.168.10.1<br />
PING 192.168.10.1 (192.168.10.1) from 192.168.10.100 tap0: 56(84) bytes of data.<br />
From 192.168.10.100 icmp_seq=1 Destination Host Unreachable</p>
<p>The tap0 interface itself at the moment can&#8217;t see the rest of my local LAN &#8211; I guess getting this to work will solve a lot of the problems already.</p>
<p>Note: I&#8217;ve also tested the tap0 interface with<br />
/proc/sys/net/ipv4/ip_forward == 1 and &#8230;==0,<br />
making no difference to the connectivity.</p>
<p>Any help would be appreciated.<br />
Regards,<br />
-frix</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Airwick Oil</title>
		<link>http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/comment-page-1/#comment-30574</link>
		<dc:creator>Airwick Oil</dc:creator>
		<pubDate>Fri, 22 Feb 2008 19:28:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/#comment-30574</guid>
		<description>Aaack! Should have check guest firewall before post #28.

I _could_ connect by IP w/rdesktop from the host and network to the guest. But I could not ping.

After I turned off the firewall on the WinXP guest, I could ping and rdp by WINS name.

If reconfigured the firewall on guest to allow all ICMP traffic and allowed Exceptions for &quot;File and Print Sharing&quot; and &quot;UPnP Framework&quot;. 

Now with firewall up, have full access to guest by WINS name.</description>
		<content:encoded><![CDATA[<p>Aaack! Should have check guest firewall before post #28.</p>
<p>I _could_ connect by IP w/rdesktop from the host and network to the guest. But I could not ping.</p>
<p>After I turned off the firewall on the WinXP guest, I could ping and rdp by WINS name.</p>
<p>If reconfigured the firewall on guest to allow all ICMP traffic and allowed Exceptions for &#8220;File and Print Sharing&#8221; and &#8220;UPnP Framework&#8221;. </p>
<p>Now with firewall up, have full access to guest by WINS name.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Airwick Oil</title>
		<link>http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/comment-page-1/#comment-30571</link>
		<dc:creator>Airwick Oil</dc:creator>
		<pubDate>Fri, 22 Feb 2008 18:37:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/#comment-30571</guid>
		<description>I&#039;ve tried the VBox user manual and several different methods for HIF I&#039;ve found online (including yours) and I still get the same effect as NAT. I cannot connect or ping from network to guest.

VBox: PUEL 1.5.6 w/ guest additions
Host: ubuntu 7.10 gutsy
Guest: WinXP Pro SP2

Could this be a firewall issue?</description>
		<content:encoded><![CDATA[<p>I&#8217;ve tried the VBox user manual and several different methods for HIF I&#8217;ve found online (including yours) and I still get the same effect as NAT. I cannot connect or ping from network to guest.</p>
<p>VBox: PUEL 1.5.6 w/ guest additions<br />
Host: ubuntu 7.10 gutsy<br />
Guest: WinXP Pro SP2</p>
<p>Could this be a firewall issue?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Markus Bertheau</title>
		<link>http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/comment-page-1/#comment-29757</link>
		<dc:creator>Markus Bertheau</dc:creator>
		<pubDate>Sat, 16 Feb 2008 18:50:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.bluetwanger.de/blog/2007/04/30/host-networking-with-virtualbox-on-ubuntu-704-feisty/#comment-29757</guid>
		<description>JeSTeR: Yes, that&#039;s one way of saying it. With host networking the guest is a regular member of the same ethernetwork that the host is.</description>
		<content:encoded><![CDATA[<p>JeSTeR: Yes, that&#8217;s one way of saying it. With host networking the guest is a regular member of the same ethernetwork that the host is.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

