Carlos E. R. wrote:
On 23/12/2021 09.13, Per Jessen wrote:
Carlos E. R. wrote:
On 22/12/2021 23.43, Mathias Homann wrote:
if you want that, your VM has to be on the regular bridge as it is now, but then your VM needs to have an IP address from your real network.
Yes, that's exactly what I have now.
I would prefer to have connectivity between host and guest only, not from outside the host. I had that with vmware, but apparently it is not possible with virtualbox.
Just use a firewall to restrict what the guest is able to do.
I don't think that would work. A firewall on the host, when the guest is bridged on the same ethernet, bypasses the host firewall.
Depends on your setup of course, but it works for me (with xen). You could also look at using ebtables.
It would has to be a firewall in the guest, as any other independent machine. This is a bad idea when the guest is Windows, for example.
The vmware method is much better.
The guest is in an independent network interface, totally invisible from the LAN, only from the host.
The hypervisors all use the same networking, more or less - some of them just wrap it in GUIs or scripts. xen, for instance, does not provide any "method" at all, it's just standard networking setup. -- Per Jessen, Zürich (6.8°C)