5 ms·
Maybe we have very different use cases, but I almost never use bridged networking. Typically what I want is all outgoing connections to be NATed through the ho
by freedomben 7y ago
Maybe we have very different use cases, but I almost never use bridged networking. Typically what I want is all outgoing connections to be NATed through the host.
That said I agree, it should be an option. There are certainly use cases for it.
- oefrha 7y agoAt home I have a Hyper-V-based Ubuntu VM on a Windows workstation that runs almost all my LAN services. Not having bridged networking would be a complete deal breaker.
- freedomben 7y agoVery interesting. May I ask why you host them on a Windows workstation? Is it your desktop/gaming machine?
- oefrha 7y agoMy primary desktop is an iMac. I built the Windows workstation to very good specs though and only use it for the occasional cross-platform development on Windows or gaming, so all the compute power is idle most of the time. Hosting services on it is a good use of the resources.
- kenny_r 7y agoThey're marketing this as a "mini-cloud". If it can only network through NAT, that eliminates all use cases where the VM instances would act as a server. I'm a sysadmin, so I like tools like this to test out provisioning of servers with configuration management such as Ansible or Puppet. Running tests at the end where I actually test the endpoints of the deployed services would be really nice to have, but impossible to do through NAT. I guess that's a niche use case for this because Vagrant had the same issue for a long time, where setting up a bridged network was not possible or required some hacks.
- tomjakubowski 7y agoI'm missing something - even without bridged networking, the VMs should still be able to network with each other, and the VM host should also be able to reach each VM. So I don't see how the lack of bridged networking prevents you from testing the deployed VMs. Do you need to control the tests from somewhere outside the VM host?
- jsjohnst 7y agoNAT networking does not imply the host running Multipass can access ports exposed on the VMs, quite the opposite. Host only would imply that, but not typical NAT in a virtual machine. Not saying it’s not possible with Multipass, just saying it shouldn’t be assumed it does.
- mlyle 7y agoGenerally if you are on a router performing NAT, you have routes to the hosts behind the NAT. Whenever I've used VMs with NAT I've been able to interact with the NAT'd network from the actual hypervisor host.
- jsjohnst 7y agoWhich hypervisor are you using? As one example, VirtualBox[0] only allows host -> VM via port forwards when using NAT networking. [0] see table 6.1 here: https://www.virtualbox.org/manual/ch06.html https://www.virtualbox.org/manual/ch06.html
- mlyle 7y agoYes, VirtualBox is an exception, because it does its own weird NAT. VMware: > The host computer has an adapter on the NAT network (identical to the host-only adapter on the host-only network). This adapter allows the host and the virtual machines to communicate with each other for such purposes as file sharing. The NAT never forwards traffic from the host adapter. Libvirt/KVM: > By default, guests that are connected via a virtual network with <forward mode='nat'/> can make any outgoing network connection they like. Incoming connections are allowed from the host, and from other guests connected to the same libvirt network, but all other incoming connections are blocked by iptables rules. Hyper-V lets you connect from host to NAT'd guests, though the documentation doesn't explicitly say this. Parallels works this way too. Xen is a weird one, because it doesn't really do the NAT itself; if you follow the Linux instructions it'll work the way I describe.