<html><head><style>
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph {
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst, p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle, p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast {
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
line-height:115%;
}
</style></head><body><div style="font-family:Calibri,'Segoe UI',Meiryo,'Microsoft YaHei UI','Microsoft JhengHei UI','Malgun Gothic','Khmer UI','Nirmala UI',Tunga,'Lao UI',Ebrima,sans-serif;font-size:16px">
<div>It has been a while for me, but back when the VMware server product was made free to use (VMware GSX based) I found that when using it in Linux, it would use the standard bridging and routing modules from the Linux kernel - so you could set up port forwarding/NAT and routing in IPTABLES even if the product did not support it.</div>
<div> </div><div>I haven’t used virtualbox on Linux to see if this is similar or not, but in Windows you don’t have that flexibility, as it creates virtual networking on it’s own stack.</div><div> </div><div> </div><div> </div>
<div style="border-top-color:rgb(225,225,225);border-top-width:1px;border-top-style:solid"> <strong>From:</strong> Boris Borisov <<a href="mailto:bugyatl@gmail.com">bugyatl@gmail.com</a>><br> <strong>Sent:</strong> March 19, 2013 8:04 AM<br>
<strong>To:</strong> Atlanta Linux Enthusiasts <<a href="mailto:ale@ale.org">ale@ale.org</a>><br> <strong>Subject:</strong> Re: [ale] virtualbox and network ip's<br> </div> <div> </div>I've been playing with vmware way back and learning networking with<br>
it. I created three VM's all on one internal network and second<br>
network adapter on the one of VM connected to the PC's NIC. So I had<br>
"real" network to practice with routing, traffic management, etc. Even<br>
full diskless install LTSP for testing. Very handy when you want to<br>
test something before to deploy.<br>
<br>
On Mon, Mar 18, 2013 at 7:02 PM, Brian Mathis<br>
<<a tabindex="-1" href="mailto:brian.mathis%2Bale@betteradmin.com">brian.mathis+ale@betteradmin.com</a>> wrote:<br>
> Virtualbox networking is confusing. When you create a NAT network, it<br>
> creates a different network for every VM, and they all get the same IP<br>
> address. They are not on the same subnet so they can't see each<br>
> other, and VirtualBox knows how to route things internally to the<br>
> correct VM. I have not setup port forwarding with vbox, but this is<br>
> likely the reason you don't see the IP address as part of the options.<br>
><br>
> Here is an explanation of each of the network types you can select:<br>
> <a tabindex="-1" href="http://www.virtualbox.org/manual/ch06.html#networkingmodes" target="_blank">http://www.virtualbox.org/manual/ch06.html#networkingmodes</a><br>
><br>
> With vbox, I often setup multiple network adapters on the VMs -- a NAT<br>
> one to allow Internet access, and a host-only one so I can ssh into<br>
> the machine directly. If it meets your needs, you might want to use a<br>
> bridged network instead which will give your VMs an IP on your real<br>
> home network.<br>
><br>
><br>
> VMware is different. It creates a subnet that acts like a home<br>
> network and attaches all VMs to it. Then VMware acts like a<br>
> router/NAT box. In this setup, VMs on the NAT subnet can see each<br>
> other. I think the VMware method makes more sense, though I still use<br>
> VirtualBox because it's open source (VMware Player is also free but<br>
> not open source).<br>
><br>
><br>
> ❧ Brian Mathis<br>
><br>
><br>
> On Fri, Mar 15, 2013 at 12:07 PM, Narahari 'n' Savitha<br>
> <<a tabindex="-1" href="mailto:savithari@gmail.com">savithari@gmail.com</a>> wrote:<br>
>> Hello:<br>
>><br>
>> I run virtualbox on my windows 7 computer.<br>
>><br>
>> I run two virtualbox machines at the same time(for two sep environments)<br>
>><br>
>> Both are NAT.<br>
>><br>
>> I do port forwarding for port 22 (from 28 on host to 22 on guest).<br>
>><br>
>> The port forwarding software does not take ip but only the port.<br>
>><br>
>> Pics are here.<br>
>> <a tabindex="-1" href="http://i.imgur.com/vyT51n9.jpg" target="_blank">http://i.imgur.com/vyT51n9.jpg</a> (first VM)<br>
>> <a tabindex="-1" href="http://i.imgur.com/Aqf4t6V.jpg" target="_blank">http://i.imgur.com/Aqf4t6V.jpg</a> (second VM)<br>
>><br>
>> What I dont understand is why two vm's get the same ip from the Virtualbox<br>
>> DHCP server ?<br>
>><br>
>> Kindly advise.<br>
>><br>
>> -Narahari<br>
>><br>
>> _______________________________________________<br>
>> Ale mailing list<br>
>> <a tabindex="-1" href="mailto:Ale@ale.org">Ale@ale.org</a><br>
>> <a tabindex="-1" href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
>> See JOBS, ANNOUNCE and SCHOOLS lists at<br>
>> <a tabindex="-1" href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
>><br>
><br>
> _______________________________________________<br>
> Ale mailing list<br>
> <a tabindex="-1" href="mailto:Ale@ale.org">Ale@ale.org</a><br>
> <a tabindex="-1" href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
> See JOBS, ANNOUNCE and SCHOOLS lists at<br>
> <a tabindex="-1" href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
<br>
_______________________________________________<br>
Ale mailing list<br>
<a tabindex="-1" href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a tabindex="-1" href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a tabindex="-1" href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
</div></body></html>