<?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: VirtualBox Host Interface Networking with NAT</title>
	<atom:link href="http://savvyadmin.com/virtualbox-host-interface-networking-with-nat/feed/" rel="self" type="application/rss+xml" />
	<link>http://savvyadmin.com/virtualbox-host-interface-networking-with-nat/</link>
	<description>For savvy admins everywhere...</description>
	<lastBuildDate>Thu, 17 May 2012 16:06:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Frans</title>
		<link>http://savvyadmin.com/virtualbox-host-interface-networking-with-nat/comment-page-1/#comment-1009</link>
		<dc:creator>Frans</dc:creator>
		<pubDate>Sun, 17 Jul 2011 18:07:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.savvyadmin.com/?p=231#comment-1009</guid>
		<description>Very good article !! Thank you for this, it really solves my problem.. ;)</description>
		<content:encoded><![CDATA[<p>Very good article !! Thank you for this, it really solves my problem.. ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frank</title>
		<link>http://savvyadmin.com/virtualbox-host-interface-networking-with-nat/comment-page-1/#comment-1005</link>
		<dc:creator>Frank</dc:creator>
		<pubDate>Thu, 09 Jun 2011 18:56:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.savvyadmin.com/?p=231#comment-1005</guid>
		<description>This is outdated and should be removed. Configuring the host to use tap0 in VirtualBox settings doesn&#039;t work - the tap0 interface doesn&#039;t exist in the Linux guest.</description>
		<content:encoded><![CDATA[<p>This is outdated and should be removed. Configuring the host to use tap0 in VirtualBox settings doesn&#8217;t work &#8211; the tap0 interface doesn&#8217;t exist in the Linux guest.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: boulboul</title>
		<link>http://savvyadmin.com/virtualbox-host-interface-networking-with-nat/comment-page-1/#comment-794</link>
		<dc:creator>boulboul</dc:creator>
		<pubDate>Fri, 04 Dec 2009 11:52:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.savvyadmin.com/?p=231#comment-794</guid>
		<description>Thanks a lot for your email...that has worked. You are great :)</description>
		<content:encoded><![CDATA[<p>Thanks a lot for your email&#8230;that has worked. You are great :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gmendoza</title>
		<link>http://savvyadmin.com/virtualbox-host-interface-networking-with-nat/comment-page-1/#comment-789</link>
		<dc:creator>gmendoza</dc:creator>
		<pubDate>Fri, 04 Dec 2009 03:09:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.savvyadmin.com/?p=231#comment-789</guid>
		<description>The tunctl command creates interfaces temporarily and are not remembered after a reboot.  To see if any exist, the following will work:

&lt;blockquote&gt;&lt;code&gt;&lt;strong&gt;ifconfig -a &#124; grep tap&lt;/strong&gt;
tap0      Link encap:Ethernet  HWaddr 52:da:12:03:e5:d5  
tap1      Link encap:Ethernet  HWaddr 9a:7e:d5:2c:84:64  
tap2      Link encap:Ethernet  HWaddr fa:ef:38:a0:b0:06  
tap3      Link encap:Ethernet  HWaddr 62:fd:aa:0b:e0:46&lt;/code&gt;&lt;/blockquote&gt;

As you can see, I have four tapX interfaces.  To remove them, use the &lt;code&gt;tunctl -d&lt;/code&gt; command like the following.

&lt;blockquote&gt;&lt;code&gt;&lt;strong&gt;sudo tunctl -d tap0&lt;/strong&gt;
Set &#039;tap0&#039; nonpersistent
&lt;strong&gt;sudo tunctl -d tap1&lt;/strong&gt;
Set &#039;tap1&#039; nonpersistent
&lt;strong&gt;sudo tunctl -d tap2&lt;/strong&gt;
Set &#039;tap2&#039; nonpersistent
&lt;strong&gt;sudo tunctl -d tap3&lt;/strong&gt;
Set &#039;tap3&#039; nonpersistent&lt;/code&gt;&lt;/blockquote&gt;

Hope this helps.  Thanks for visiting.</description>
		<content:encoded><![CDATA[<p>The tunctl command creates interfaces temporarily and are not remembered after a reboot.  To see if any exist, the following will work:</p>
<blockquote><p><code><strong>ifconfig -a | grep tap</strong><br />
tap0      Link encap:Ethernet  HWaddr 52:da:12:03:e5:d5<br />
tap1      Link encap:Ethernet  HWaddr 9a:7e:d5:2c:84:64<br />
tap2      Link encap:Ethernet  HWaddr fa:ef:38:a0:b0:06<br />
tap3      Link encap:Ethernet  HWaddr 62:fd:aa:0b:e0:46</code></p></blockquote>
<p>As you can see, I have four tapX interfaces.  To remove them, use the <code>tunctl -d</code> command like the following.</p>
<blockquote><p><code><strong>sudo tunctl -d tap0</strong><br />
Set 'tap0' nonpersistent<br />
<strong>sudo tunctl -d tap1</strong><br />
Set 'tap1' nonpersistent<br />
<strong>sudo tunctl -d tap2</strong><br />
Set 'tap2' nonpersistent<br />
<strong>sudo tunctl -d tap3</strong><br />
Set 'tap3' nonpersistent</code></p></blockquote>
<p>Hope this helps.  Thanks for visiting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: boulboul</title>
		<link>http://savvyadmin.com/virtualbox-host-interface-networking-with-nat/comment-page-1/#comment-788</link>
		<dc:creator>boulboul</dc:creator>
		<pubDate>Fri, 04 Dec 2009 02:55:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.savvyadmin.com/?p=231#comment-788</guid>
		<description>i have setup sp many onterfaces,,,how do i go about deleting all taps please...i am running debian lenny...thanks</description>
		<content:encoded><![CDATA[<p>i have setup sp many onterfaces,,,how do i go about deleting all taps please&#8230;i am running debian lenny&#8230;thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Денис Лебедев</title>
		<link>http://savvyadmin.com/virtualbox-host-interface-networking-with-nat/comment-page-1/#comment-487</link>
		<dc:creator>Денис Лебедев</dc:creator>
		<pubDate>Sat, 17 Oct 2009 15:06:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.savvyadmin.com/?p=231#comment-487</guid>
		<description>Занятно пишете, жизненно. Все-таки, для того, чтобы делать действительно интересный блог, нужно не только сообщать о чем-то, но и делать это в интересной форме:)</description>
		<content:encoded><![CDATA[<p>Занятно пишете, жизненно. Все-таки, для того, чтобы делать действительно интересный блог, нужно не только сообщать о чем-то, но и делать это в интересной форме:)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dent</title>
		<link>http://savvyadmin.com/virtualbox-host-interface-networking-with-nat/comment-page-1/#comment-418</link>
		<dc:creator>dent</dc:creator>
		<pubDate>Thu, 03 Sep 2009 17:50:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.savvyadmin.com/?p=231#comment-418</guid>
		<description>Nice write-up and just what the doctor ordered. For some reason vbox3&#039;s builtin port forwarding on natted interfaces is very flaky when running in headless mode. This is much nicer!</description>
		<content:encoded><![CDATA[<p>Nice write-up and just what the doctor ordered. For some reason vbox3&#8242;s builtin port forwarding on natted interfaces is very flaky when running in headless mode. This is much nicer!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marcello de Sales</title>
		<link>http://savvyadmin.com/virtualbox-host-interface-networking-with-nat/comment-page-1/#comment-396</link>
		<dc:creator>Marcello de Sales</dc:creator>
		<pubDate>Thu, 30 Jul 2009 13:05:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.savvyadmin.com/?p=231#comment-396</guid>
		<description>The search is over!!! VirtualBox 3.0.2 offers the networking with NAT out-of-the-box with Ubuntu as Host and Guests as Ubuntu and windows. See instructions! No commands, no scripts necessary!

http://distributed-agility.blogspot.com/2009/07/building-clustered-shared-subnetwork.html</description>
		<content:encoded><![CDATA[<p>The search is over!!! VirtualBox 3.0.2 offers the networking with NAT out-of-the-box with Ubuntu as Host and Guests as Ubuntu and windows. See instructions! No commands, no scripts necessary!</p>
<p><a href="http://distributed-agility.blogspot.com/2009/07/building-clustered-shared-subnetwork.html" rel="nofollow">http://distributed-agility.blogspot.com/2009/07/building-clustered-shared-subnetwork.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jorge</title>
		<link>http://savvyadmin.com/virtualbox-host-interface-networking-with-nat/comment-page-1/#comment-373</link>
		<dc:creator>Jorge</dc:creator>
		<pubDate>Mon, 13 Jul 2009 12:21:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.savvyadmin.com/?p=231#comment-373</guid>
		<description>Great post!

But with this configuration, udp broadcast don&#039;t work between client machines.
Can anyone have a hint to solve this problem?

Thanks in advance.

Jorge</description>
		<content:encoded><![CDATA[<p>Great post!</p>
<p>But with this configuration, udp broadcast don&#8217;t work between client machines.<br />
Can anyone have a hint to solve this problem?</p>
<p>Thanks in advance.</p>
<p>Jorge</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: edward</title>
		<link>http://savvyadmin.com/virtualbox-host-interface-networking-with-nat/comment-page-1/#comment-371</link>
		<dc:creator>edward</dc:creator>
		<pubDate>Thu, 02 Jul 2009 20:31:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.savvyadmin.com/?p=231#comment-371</guid>
		<description>With version 2.1.4 OSE of virtualbox you can just go to Settings -&gt; Network: and change the &quot;Attached to:&quot; from &quot;Nat&quot; to &quot;Host Interface&quot;. Then select your host machine&#039;s active network device from the list. Start up your guest and it should pick up an IP from your networks&#039; Dhcp server. If you have no DHCP server configure the guest with a static IP. Note, you may have to open a terminal and run dhclient3 as root or with sudo to get your guest to pick up an IP via dhcp. Otherwise it should just work. It did for me.

thanks
emk</description>
		<content:encoded><![CDATA[<p>With version 2.1.4 OSE of virtualbox you can just go to Settings -&gt; Network: and change the &#8220;Attached to:&#8221; from &#8220;Nat&#8221; to &#8220;Host Interface&#8221;. Then select your host machine&#8217;s active network device from the list. Start up your guest and it should pick up an IP from your networks&#8217; Dhcp server. If you have no DHCP server configure the guest with a static IP. Note, you may have to open a terminal and run dhclient3 as root or with sudo to get your guest to pick up an IP via dhcp. Otherwise it should just work. It did for me.</p>
<p>thanks<br />
emk</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: scott</title>
		<link>http://savvyadmin.com/virtualbox-host-interface-networking-with-nat/comment-page-1/#comment-367</link>
		<dc:creator>scott</dc:creator>
		<pubDate>Tue, 30 Jun 2009 19:14:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.savvyadmin.com/?p=231#comment-367</guid>
		<description>I have been using something similar I believe @ work, but the problem is it is updating the DNS with my NAT IP address.  Do one of the iptables rules above stop that from happening ?</description>
		<content:encoded><![CDATA[<p>I have been using something similar I believe @ work, but the problem is it is updating the DNS with my NAT IP address.  Do one of the iptables rules above stop that from happening ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Nicholas</title>
		<link>http://savvyadmin.com/virtualbox-host-interface-networking-with-nat/comment-page-1/#comment-361</link>
		<dc:creator>Mark Nicholas</dc:creator>
		<pubDate>Wed, 10 Jun 2009 20:28:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.savvyadmin.com/?p=231#comment-361</guid>
		<description>works great with Air Cards as well (ppp0) modify script from 
NAT_OUT=&quot;eth0 wlan0&quot;
to
NAT_OUT=&quot;eth0 wlan0 ppp0&quot;
and voila! life is good

thank you for the help!</description>
		<content:encoded><![CDATA[<p>works great with Air Cards as well (ppp0) modify script from<br />
NAT_OUT=&#8221;eth0 wlan0&#8243;<br />
to<br />
NAT_OUT=&#8221;eth0 wlan0 ppp0&#8243;<br />
and voila! life is good</p>
<p>thank you for the help!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Redirecionando portas para VirtualBox. @ Matheus Bratfisch</title>
		<link>http://savvyadmin.com/virtualbox-host-interface-networking-with-nat/comment-page-1/#comment-357</link>
		<dc:creator>Redirecionando portas para VirtualBox. @ Matheus Bratfisch</dc:creator>
		<pubDate>Mon, 18 May 2009 18:49:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.savvyadmin.com/?p=231#comment-357</guid>
		<description>[...] IPtables Tutorial IPTables Port Redirect VirtualBox, com nat VBoxManage Port Forward   Linux porta, redirecionamento, [...]</description>
		<content:encoded><![CDATA[<p>[...] IPtables Tutorial IPTables Port Redirect VirtualBox, com nat VBoxManage Port Forward   Linux porta, redirecionamento, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gmendoza</title>
		<link>http://savvyadmin.com/virtualbox-host-interface-networking-with-nat/comment-page-1/#comment-344</link>
		<dc:creator>gmendoza</dc:creator>
		<pubDate>Thu, 23 Apr 2009 16:58:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.savvyadmin.com/?p=231#comment-344</guid>
		<description>You run this script only when you need to start and use Virtualbox.  After finished with Virtualbox and it&#039;s all shut down, you can use it again with the stop option.  It should not affect your internet connection at all, but if you have firewall rules turned on your host computer, you may need more fine tuning of your rules.

You should know that if you just want to have your guests behind a NAT, this process has been made easier in the most recent versions of Virtualbox.</description>
		<content:encoded><![CDATA[<p>You run this script only when you need to start and use Virtualbox.  After finished with Virtualbox and it&#8217;s all shut down, you can use it again with the stop option.  It should not affect your internet connection at all, but if you have firewall rules turned on your host computer, you may need more fine tuning of your rules.</p>
<p>You should know that if you just want to have your guests behind a NAT, this process has been made easier in the most recent versions of Virtualbox.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gab</title>
		<link>http://savvyadmin.com/virtualbox-host-interface-networking-with-nat/comment-page-1/#comment-343</link>
		<dc:creator>gab</dc:creator>
		<pubDate>Thu, 23 Apr 2009 10:15:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.savvyadmin.com/?p=231#comment-343</guid>
		<description>Does it affect my current internet connection if I enable this script? I&#039;m directly connected to a cable modem..

Thanks for writing the steps. I appreciate your help!</description>
		<content:encoded><![CDATA[<p>Does it affect my current internet connection if I enable this script? I&#8217;m directly connected to a cable modem..</p>
<p>Thanks for writing the steps. I appreciate your help!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gmendoza</title>
		<link>http://savvyadmin.com/virtualbox-host-interface-networking-with-nat/comment-page-1/#comment-336</link>
		<dc:creator>gmendoza</dc:creator>
		<pubDate>Tue, 21 Apr 2009 16:10:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.savvyadmin.com/?p=231#comment-336</guid>
		<description>gab... my apologies for not explaining how to set up the script.  my reasoning is that if I explain how to set it up, it becomes redundant across all of my posts.

1. Save the script as a text file in a place you have &quot;write&quot; access to.  Your home directory should be fine.  Save it as &quot;tap-setup.sh&quot; or any other name you find appropriate.

2. Copy the script to a directory referenced in your $PATH variable.  I like to put my own custom scripts in &quot;/usr/local/bin/&quot;.  This allows you to just type in the name of the script at the command line without having to type it&#039;s absolute path.

3. Make the script executable.

&lt;blockquote&gt;&lt;code&gt;&lt;strong&gt;sudo chmod +x /usr/local/bin/tap-setup.sh&lt;/strong&gt;&lt;/pre&gt;&lt;/blockquote&gt;

4. Run the scripte from the command line.

&lt;blockquote&gt;&lt;code&gt;&lt;strong&gt;sudo tap-setup.sh start
sudo tap-setup.sh stop&lt;/strong&gt;&lt;/pre&gt;&lt;/blockquote&gt;</description>
		<content:encoded><![CDATA[<p>gab&#8230; my apologies for not explaining how to set up the script.  my reasoning is that if I explain how to set it up, it becomes redundant across all of my posts.</p>
<p>1. Save the script as a text file in a place you have &#8220;write&#8221; access to.  Your home directory should be fine.  Save it as &#8220;tap-setup.sh&#8221; or any other name you find appropriate.</p>
<p>2. Copy the script to a directory referenced in your $PATH variable.  I like to put my own custom scripts in &#8220;/usr/local/bin/&#8221;.  This allows you to just type in the name of the script at the command line without having to type it&#8217;s absolute path.</p>
<p>3. Make the script executable.</p>
<blockquote><p><code><strong>sudo chmod +x /usr/local/bin/tap-setup.sh</strong></code></p></blockquote>
<p>4. Run the scripte from the command line.</p>
<blockquote><p><code><strong>sudo tap-setup.sh start<br />
sudo tap-setup.sh stop</strong></code></p></blockquote>
]]></content:encoded>
	</item>
	<item>
		<title>By: gab</title>
		<link>http://savvyadmin.com/virtualbox-host-interface-networking-with-nat/comment-page-1/#comment-335</link>
		<dc:creator>gab</dc:creator>
		<pubDate>Tue, 21 Apr 2009 09:42:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.savvyadmin.com/?p=231#comment-335</guid>
		<description>How will i use the this script? can you guys provide some steps? many thanks!</description>
		<content:encoded><![CDATA[<p>How will i use the this script? can you guys provide some steps? many thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: z0n</title>
		<link>http://savvyadmin.com/virtualbox-host-interface-networking-with-nat/comment-page-1/#comment-331</link>
		<dc:creator>z0n</dc:creator>
		<pubDate>Thu, 09 Apr 2009 14:46:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.savvyadmin.com/?p=231#comment-331</guid>
		<description>After many late nights trying to get my wifi interface bridged for vbox, I run your script and everything just works - without a single dodgy if-up script or weird, mystical manual interface setting.

Excellent script, Dude - you must wear a beard, I&#039;m sure ;&gt;

Many thanks - you rule!</description>
		<content:encoded><![CDATA[<p>After many late nights trying to get my wifi interface bridged for vbox, I run your script and everything just works &#8211; without a single dodgy if-up script or weird, mystical manual interface setting.</p>
<p>Excellent script, Dude &#8211; you must wear a beard, I&#8217;m sure ;&gt;</p>
<p>Many thanks &#8211; you rule!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gmendoza</title>
		<link>http://savvyadmin.com/virtualbox-host-interface-networking-with-nat/comment-page-1/#comment-327</link>
		<dc:creator>gmendoza</dc:creator>
		<pubDate>Sat, 04 Apr 2009 13:35:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.savvyadmin.com/?p=231#comment-327</guid>
		<description>Sure thing!  Glad to have helped.</description>
		<content:encoded><![CDATA[<p>Sure thing!  Glad to have helped.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CyberThug</title>
		<link>http://savvyadmin.com/virtualbox-host-interface-networking-with-nat/comment-page-1/#comment-326</link>
		<dc:creator>CyberThug</dc:creator>
		<pubDate>Sat, 04 Apr 2009 05:17:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.savvyadmin.com/?p=231#comment-326</guid>
		<description>Great Tutorial, may repost in my Blog ? I want to share to my friend in Indonesia.</description>
		<content:encoded><![CDATA[<p>Great Tutorial, may repost in my Blog ? I want to share to my friend in Indonesia.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

