I’d like to add aliases on my network interfaces fro VirtualBox guests systems, rather than using the internal NAT to the same interfaces.
Can anyone advise me of steps? Is there a simple way or just the messy way of adding through the ‘local’ startup file?
I created aliases under 11.3 & 12.1 but 12.3 looks a bit different …
Setup is 12.3 64bit on Intel with VirtualBox 4.2.16. Guests are Win Vista (32 bit) & Slackware 14.0 (also 32 bit).
Thanks
David
On Sun, 15 Sep 2013 13:16:02 +0000, jetojedno wrote:
> I’d like to add aliases on my network interfaces fro VirtualBox guests
> systems, rather than using the internal NAT to the same interfaces.
Can you explain what you mean here? Do you mean you want the guests’
network address to be on the same network as the host?
If that’s what you mean, then what you need is to use bridged networking.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
Although I’m not a VB user,
This is a common request and “extended feature”
You need to describe whether you’re using only VB to setup and manage your networks or if you’re using something else in addition to VB, eg libvirt’s vm manager or Vagrant.
Linux by itself does not support mapping aliases to virtual networks to Linux Bridge devices (I generally haven’t seen physical interfaces mapped to network names, but may exist), but various virtualization managers support this often requested feature.
TSU
I discovered the answer to my question - if I use bridging to the NIC, then the guest uses that NIC and gets it’s own IP address using DHCP. That’s what I wanted.
Why does the documentation suggest using NAT?
Thanks for your time,
David
On Sat, 21 Sep 2013 18:06:04 +0000, jetojedno wrote:
> Why does the documentation suggest using NAT?
You would have to ask the folks at VirtualBox.org as they “own” the
documentation. 
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C