<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html><head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type"> </head><p>Sent from my BlackBerry Smartphone provided by Alltel</p><hr/><div><b>From: </b> Jim Butler <jimbutler1234567890@gmail.com>
</div><div><b>Date: </b>Tue, 14 Dec 2010 19:13:34 -0500</div><div><b>To: </b><ale@pcartwright.com></div><div><b>Subject: </b>Re: [ale] VirtualBox</div><div><br/></div>Actually, going to bridged mode was my next step, but I just wanted to resolve this..<br>Anyway, to go to bridge mode, will probably require manually editing the configs or a script. I say this because I am using virtualbox-ose_version1.6 and it doen't have bridging as an option in the gui. <br>
<br>While we're on the subject of VirtualBox, maybe someone can resolve a licensing question: I went to Oracles's website to download VirtualBox V3.2 and while there I checked in to the licensing. According to documents, there is no licensing fee to use version 3.2, but if you want support you have to pay and it's expensive.. I'm cool with that.. But then when I installed version 3.2 (on my other machine, not the one that I'm having the NATting issue with), it said it's a personal evaluation, limited, etc... So can someone give me the real story on VirtualBox, how many VMs I can deploy, and how much I'll have to pay if I want something of Production-Level quality??<br>
<br>Thanks,<br>Jim Butler<br><br><br><br><div class="gmail_quote">On Tue, Dec 14, 2010 at 6:58 PM, Paul Cartwright <span dir="ltr"><<a href="mailto:ale@pcartwright.com">ale@pcartwright.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On 12/14/2010 06:36 PM, Jim Butler wrote:<br>
> Hi Everyone..<br>
> I am trying to virtualize some servers, and I decided to use VirtualBox<br>
> to do it instead of VMWare. My problem is this: I got everything all set<br>
> up the way I wanted it, and installed three different virtual machines.<br>
> Everything was working fine until this morning when I went to use the<br>
> networking. Networking is set to NAT, and it worked fine before. Now,<br>
> all of my virtual machines still work fine, but when I try to ping the<br>
> host IP from the virtual machine, it is unable to reach the ip on the<br>
> host. On the icon bar at the bottom of the virtual machine window, it<br>
> shows network activity, and everything looks normal from within the<br>
> virtual machine it's self. Furthermore, I can ping outside of my host<br>
> box from within a host shell.. (that is, on the host (not the virtual<br>
</div>> machine) if I try to ping <a href="http://yahoo.com" target="_blank">yahoo.com</a> <<a href="http://yahoo.com" target="_blank">http://yahoo.com</a>> it works fine)..<br>
<div class="im">> It's just a problem either with the way that the virtual machine is<br>
> sending the packets, or with the way that the host machine recieves (or<br>
> doesn't recieve) the NATted packets.<br>
> If someone can help me with this, I would sure be appreciative.<br>
<br>
<br>
</div>I read a thread somewhere recently that said to change your networking<br>
default in Vbox to bridged mode.. that way all your other boxes see the<br>
Vbox server like it was on your local LAN...<br>
<font color="#888888"><br>
--<br>
Paul Cartwright<br>
Registered Linux user # 367800<br>
Registered Ubuntu User #12459<br>
<br>
</font></blockquote></div><br>
</html>