Opened 18 years ago
Closed 17 years ago
#248 closed enhancement (fixed)
Configure Internal Network name through GUI
Reported by: | KhaoticMind | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 1.3.8 |
Keywords: | network internal gui | Cc: | |
Guest type: | other | Host type: | other |
Description
Yesterday i was playing with internal networking in VBox, and found if quite frustrating to have to configure the network names with the CLI. It would be good to be able to do it inside the GUI (VirtualBox.exe).
As i see it the most "natural" solution would be to allow the users to create a series of Internal Networks and, when configuring a VM, be able to select which internal network to attach a nic to, using a combobox.
Change History (4)
comment:1 by , 18 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
comment:2 by , 18 years ago
Resolution: | wontfix |
---|---|
Status: | closed → reopened |
Lol! I think you confused this request with the e-mail I sent to the mailing list earlier :)
I was asking SOMETHING on the lines you say on the e-mail, but this request is to be able to configure multiple internal networks on the GUI and let them work the EXACT same way they work today :)
I ask this so i don't have to do: vboxmanage modifyvm Node1 -intnet1 testnet vboxmanage modifyvm Node2 -intnet1 testnet2
This ticket is to allow me to create testnet and testnet2 in the GUI, and assign them as i see fit :)
comment:3 by , 18 years ago
Ah, sorry. Misunderstood "attach a nic to". Thought you were referring to a host NIC. Makes more sense now. Anyway, with current SVN you can already configure a NIC for internal networking (and it displays the network name in the config summary). So some progress has already been made.
However you cannot currently select which internal network to use with the GUI. It's in the works, but low priority, because those who use this feature regularly tend to use scripts to configure VMs anyway.
We will never allow this. Internal networking is a security feature, and guarantees that the host OS never sees the network frames in it's network stack.
It's another question whether host networking could be changed (especially on Windows, which supports at most one bridge), but that topic has seen some big discussions (but unfortunately no code contributions), e.g. in #18.