[ale] virtualbox and network ip's

Matt Hessel matt.hessel at gmail.com
Tue Mar 19 19:08:08 EDT 2013


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.

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.



 *From:* Boris Borisov <bugyatl at gmail.com>
*Sent:* ‎March‎ ‎19‎, ‎2013 ‎8‎:‎04‎ ‎AM
*To:* Atlanta Linux Enthusiasts <ale at ale.org>
*Subject:* Re: [ale] virtualbox and network ip's

I've been playing with vmware way back and learning networking with
it. I created three VM's all on one internal network and second
network adapter on the one of VM connected to the PC's NIC. So I had
"real" network to practice with routing, traffic management, etc. Even
full diskless install LTSP for testing. Very handy when you want to
test something before to deploy.

On Mon, Mar 18, 2013 at 7:02 PM, Brian Mathis
<brian.mathis+ale at betteradmin.com> wrote:
> Virtualbox networking is confusing.  When you create a NAT network, it
> creates a different network for every VM, and they all get the same IP
> address.  They are not on the same subnet so they can't see each
> other, and VirtualBox knows how to route things internally to the
> correct VM.  I have not setup port forwarding with vbox, but this is
> likely the reason you don't see the IP address as part of the options.
>
> Here is an explanation of each of the network types you can select:
>     http://www.virtualbox.org/manual/ch06.html#networkingmodes
>
> With vbox, I often setup multiple network adapters on the VMs -- a NAT
> one to allow Internet access, and a host-only one so I can ssh into
> the machine directly.  If it meets your needs, you might want to use a
> bridged network instead which will give your VMs an IP on your real
> home network.
>
>
> VMware is different.  It creates a subnet that acts like a home
> network and attaches all VMs to it.  Then VMware acts like a
> router/NAT box.  In this setup, VMs on the NAT subnet can see each
> other.  I think the VMware method makes more sense, though I still use
> VirtualBox because it's open source (VMware Player is also free but
> not open source).
>
>
> ❧ Brian Mathis
>
>
> On Fri, Mar 15, 2013 at 12:07 PM, Narahari 'n' Savitha
> <savithari at gmail.com> wrote:
>> Hello:
>>
>> I run virtualbox on my windows 7 computer.
>>
>> I run two virtualbox machines at the same time(for two sep environments)
>>
>> Both are NAT.
>>
>> I do port forwarding for port 22 (from 28 on host to 22 on guest).
>>
>> The port forwarding software does not take ip but only the port.
>>
>> Pics are here.
>> http://i.imgur.com/vyT51n9.jpg (first VM)
>> http://i.imgur.com/Aqf4t6V.jpg (second VM)
>>
>> What I dont understand is why two vm's get the same ip from the
Virtualbox
>> DHCP server ?
>>
>> Kindly advise.
>>
>> -Narahari
>>
>> _______________________________________________
>> Ale mailing list
>> Ale at ale.org
>> http://mail.ale.org/mailman/listinfo/ale
>> See JOBS, ANNOUNCE and SCHOOLS lists at
>> http://mail.ale.org/mailman/listinfo
>>
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://mail.ale.org/mailman/listinfo/ale
> See JOBS, ANNOUNCE and SCHOOLS lists at
> http://mail.ale.org/mailman/listinfo

_______________________________________________
Ale mailing list
Ale at ale.org
http://mail.ale.org/mailman/listinfo/ale
See JOBS, ANNOUNCE and SCHOOLS lists at
http://mail.ale.org/mailman/listinfo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ale.org/pipermail/ale/attachments/20130319/69e15be6/attachment.html>


More information about the Ale mailing list