<div dir="ltr"><div><div>Virtualbox NAT networking acts like there's a NAT firewall inside your computer. Every guest that you connect to the NAT network gets its own private network, and multiple guests receive the same IP (10.0.2.x), but there is no conflict because they are all internally on a different network (and cannot talk to each other either).<br>
<br>Virtualbox 4.3 has introduced another NAT mode called "NAT Network" which acts as if all of the guests on that network are connected to the same NAT firewall, instead of separate ones per guest.<br><br></div>
If you want to expose the VM to the same network your computer is using, then you need to use the bridged network. This will act like there's another cable connected to your network switch, and you would need to assign an IP just like it's any other physical machine on the network.<br>
<br></div>There is a full description of each of the Virtualbox network types here:<br> <a href="https://www.virtualbox.org/manual/ch06.html#networkingmodes">https://www.virtualbox.org/manual/ch06.html#networkingmodes</a><br>
<div><div><div><div><div><br></div><div>For what you are doing, I would use the bridged Virtualbox network as there's one fewer level of translation going on. That should make it easier, but keep in mind that you are nesting VM technologies, so things may get complex/confusing quickly.<br>
</div><div><br><div class="gmail_extra"><br clear="all"><div>❧ Brian Mathis</div>
<br><br><div class="gmail_quote">On Mon, Jan 6, 2014 at 4:46 PM, Narahari 'n' Savitha <span dir="ltr"><<a href="mailto:savithari@gmail.com" target="_blank">savithari@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">If I set up a NAT adapter at the VirtualBox level, I always get the 10.0.2.15 ip address inside the VirtualBox (aka inside the guest OS) if I type ip addr.<div><br></div><div>I also tried the Bridge mode at the VirtualBox level and the guest os gets the ip that the router dishes out 192.168.0.x</div>
<div><br></div><div>The question is related to the NAT point made above. If I set up the network to be NAT at the VirtualBox level, can I still set up the network inside the guest ok aka my Linux as bridge and what does it mean to do so. The reason I want to do the bridge approach is because ArchLinux starts the whole LXC thing with the first step being bridge mode network configuration.</div>
<div><br></div><div>At this time I am confused with LXC vs docker difference ?</div><div>I am also confused with BridgeMode inside the guest os while VirtualBox is set to NAT.</div><span class=""><font color="#888888"><div>
<br></div><div>
-Narahari</div></font></span></div><div class=""><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jan 6, 2014 at 4:04 PM, Boris Borisov <span dir="ltr"><<a href="mailto:bugyatl@gmail.com" target="_blank">bugyatl@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><p dir="ltr">Virtual box virtual adapters also can be set in bridge/nat/or isolated network also internal network for box. Easy way to test this is with live Linux image. Run it in vbox with different adaptor settings and see results. Nothing better than experience even sometimes you reinvent the wheel :-) </p>
<div><div>
<div style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Actually what I am trying to understand is, in a real physical Linux box, connected to my router, the ip of 192.168.0.42 is dished out by the router.<div>
If I install LXC in there, according to instructions for LXC, the eth0 network interface is to be bridged to the LXC container and the network ip to the LXC gets assigned by the router again in the 192.168.0.x range.</div>
<div><br></div><div>I also understand that you can set the LXC to get the IP dished out from the hardware box's eth0 in a NAT format so they can get the ip in the 192.168.100.x series. (It is convoluted to do it with Arch but it is doable)</div>
<div><br></div><div>==============</div><div><br></div><div>Now drawing analogy to that in the VirtualBox world of things,</div><div><br></div><div>VirtualBox is the equivalent of the hardware box. The OS inside that is the Linux os and the router is also the VirtualBox which dishes out the IP to the Linux OS. Now, to install LXC inside the Linux(which is the guest os) I am confused with the bridge approach and I am struggling there.</div>
<div><br></div><div>I am trying to draw analogies so I can better understand how diff is a VirtualBox env where Linux runs compared to a hardware box where Linux runs.</div><div><br></div><div>Should I treat the VirtualBox as the router that dishes out the IP in the 10.0.2.x range and if LXC is installed with bridge, will the LXC then get the IP from the VirutalBox in the 10.0.2.x range ?</div>
<div><br></div><div>I know my questions are confusing too but I am confused, hence the questions are confused.</div><div><br></div><div>-N</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Mon, Jan 6, 2014 at 12:09 AM, Michael Strickland <span dir="ltr"><<a href="mailto:michael@ipxcore.com" target="_blank">michael@ipxcore.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
I think he wants multiple IPs assigned to the VM so each container can<br>
have an IP. I never figured out how to do that with virtualbox, I<br>
always found the networking to be too much of a pain.<br>
<br>
- --Michael Strickland<br>
<div><div><br>
On 1/6/2014 12:00 AM, Boris Borisov wrote:<br>
> Bridge is like pluging two cables in the same switch/network. NAT<br>
> is the way to deliver internet in your office with 20 computers but<br>
> you have only one IP from your provider. I'm not proud of my<br>
> explanation :-) but all depends of your needs. Tell us more On Jan<br>
> 5, 2014 11:52 PM, "Narahari 'n' Savitha" <<a href="mailto:savithari@gmail.com" target="_blank">savithari@gmail.com</a>><br>
> wrote:<br>
><br>
>> Friends:<br>
>><br>
>> Happy New Year to all.<br>
>><br>
>> Thank you for your help in advance.<br>
>><br>
>> I am running Arch Linux 64 bit under VirtualBox as a guest OS on<br>
>> a Mac host. It works well.<br>
>><br>
>> Allocated 4GB RAM to the guest OS.<br>
>><br>
>> When Virtualbox allocates network, I have setup a NAT config and<br>
>> the Arch Linux gets 10.0.2.15 ip.<br>
>><br>
>> The host hardware box gets ip in the 192.168.x.x from the<br>
>> physical router, but the virtualbox software dishes out 10.0.2.15<br>
>> to guest os inside virtualbox. I presume the virtualbox software<br>
>> is doing that.<br>
>><br>
>> Do I have to use bridge mode for installing lxc on the guest OS<br>
>><br>
>> Regards, -N<br>
>><br>
>> _______________________________________________ Ale mailing list<br>
>> <a href="mailto:Ale@ale.org" target="_blank">Ale@ale.org</a> <a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a> See JOBS,<br>
>> ANNOUNCE and SCHOOLS lists at<br>
>> <a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
>><br>
>><br>
><br>
><br>
><br>
> _______________________________________________ Ale mailing list<br>
> <a href="mailto:Ale@ale.org" target="_blank">Ale@ale.org</a> <a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a> See JOBS,<br>
> ANNOUNCE and SCHOOLS lists at <a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
><br>
<br>
<br>
</div></div>-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.1 (MingW32)<br>
Comment: Using GnuPG with Thunderbird - <a href="http://www.enigmail.net/" target="_blank">http://www.enigmail.net/</a><br>
<br>
iQEVAwUBUso6ck57vLMARVTwAQLt7ggAyNEWc9ums9RgtUHkIoVE6DlBlLChOyJ3<br>
ylUbn1sQnUIGA8VqTy7tXE05KSSt73xeVj3b/khYjvP3uohvBbK4pvDxpA5V2ZUO<br>
NM9Y6sL2fqQx8kaUoU7h1pLpDM6X7A8W1FPsb10HouTbL3KLIgWSZo2Ixk2DAC9Y<br>
Ff1T6gxiKdhj3TmFCY0dTuIG/dZOCFFSrkAetf4me7GJBUg5vL4Dal7nkhRe5frs<br>
zkbYOB7mEPM9sLFLJ9D32q0hvhj2fYxM/x/qSCczTdRVHbGrBDO+annNKytBRoP9<br>
BTZuLm8HIW3JjA7uRmImaAbpQh35aRPI9wLMTkuM+hszXX15073DcQ==<br>
=W2cw<br>
-----END PGP SIGNATURE-----<br>
<br>
---<br>
This email is free from viruses and malware because avast! Antivirus protection is active.<br>
<a href="http://www.avast.com" target="_blank">http://www.avast.com</a><br>
<div><div><br>
_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org" target="_blank">Ale@ale.org</a><br>
<a 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 href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
</div></div></blockquote></div><br></div>
<br>_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org" target="_blank">Ale@ale.org</a><br>
<a 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 href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
<br></div>
</div></div><br>_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org" target="_blank">Ale@ale.org</a><br>
<a 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 href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a 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 href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
<br></blockquote></div><br></div></div></div></div></div></div></div>