<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Solutions on Justin Carmony</title>
		<link>https://www.justincarmony.com/tags/solutions/</link>
		<description>Recent content in Solutions on Justin Carmony</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Mon, 22 Mar 2010 06:32:43 +0000</lastBuildDate>
		
			<atom:link href="https://www.justincarmony.com/tags/solutions/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>VirtualBox Networking Setup</title>
				<link>https://www.justincarmony.com/2010/03/22/virtualbox-networking-setup/</link>
				<pubDate>Mon, 22 Mar 2010 06:32:43 +0000</pubDate>
				<guid>https://www.justincarmony.com/2010/03/22/virtualbox-networking-setup/</guid>
				<description>&lt;p&gt;Every time I go to set up VirtualBox and several VMs I always forget how I setup the networking for them. Once again, I went through the pain of trying to figure it all out, so I might as well document it for future use.&lt;/p&gt;&#xA;&lt;h3 id=&#34;the-problem&#34;&gt;The Problem&lt;/h3&gt;&#xA;&lt;p&gt;When creating virtual machines, especially virtual linux servers, I want them to be able to do the following things:&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;Connect to the Internet&lt;/li&gt;&#xA;&lt;li&gt;Connect over SSH from my Host Machine to the Guest Machine&lt;/li&gt;&#xA;&lt;li&gt;Have the servers connect to each other on a private internal network&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;p&gt;Out of the box, a VM is configured for #1, however it cannot do #2 and #3. There are some solutions that do some &lt;a href=&#34;http://mydebian.blogdns.org/?p=148&#34;&gt;archaic port forwarding&lt;/a&gt; by issuing special commands from the Terminal. This is just painful, and if you just want &lt;em&gt;&lt;strong&gt;one&lt;/strong&gt;&lt;/em&gt; port to work, that&amp;rsquo;s manageable, but what if you want ssh, ftp, myql, http, https, etc? Any on multiple VMs? What a nightmare! What is painful is when googling for a solution, almost &lt;em&gt;&lt;strong&gt;every&lt;/strong&gt;&lt;/em&gt; &amp;ldquo;answer&amp;rdquo; is this crazy port forwarding method. There is a much cleaner, better way!&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
