[opensuse] routing from host to virtual box guest machine.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I can't ping my virtual box VM machines, but I can from VM to host. cer@Telcontar:~> ping 10.0.2.15 PING 10.0.2.15 (10.0.2.15) 56(84) bytes of data. ^C - --- 10.0.2.15 ping statistics --- 5 packets transmitted, 0 received, 100% packet loss, time 4030ms cer@Telcontar:~> traceroute 10.0.2.15 traceroute to 10.0.2.15 (10.0.2.15), 30 hops max, 60 byte packets 1 router.valinor (192.168.1.1) 0.601 ms 0.581 ms 0.822 ms^C cer@Telcontar:~> It is using the default gateway to my router. How should I best handle this issue? I guess I should add another route, but should it be permanent, or only when starting VBox? VMware did add the needed routes. Another question is if I should use the 10.*.*.* network for VBOX, or use a 192.something instead as VMware does. I have the doubt because my ISP and the router use the 10.* network for something (not sure what, could be the VoIP network). And if I change this on VBOX, where. - -- Cheers Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlsOmm8ACgkQtTMYHG2NR9XIYQCdG3+lr5a836dcXR3yAwG0IjJS 7MwAn3qe0JO3NRgB+jSZ7Nllb/dr/Ukh =SJui -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, May 30, 2018 at 3:34 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
I can't ping my virtual box VM machines, but I can from VM to host.
cer@Telcontar:~> ping 10.0.2.15
This is user LAN address which is not visible on host at all. Traffic from VM ends up in virtualbox process which then sends it further on its behalf. You may consider virtualbox process as NAT router; you cannot connect from outside to systems inside of NATed network. It may be possible to forward individual ports inside VM, just like in normal NAT case, I do not remember whether VB supports it (qemu does). ...
How should I best handle this issue?
You may start with reading virtualbox documentation which describes possible network types and their restrictions and then decide which one suits better in your use case. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-05-30 14:44, Andrei Borzenkov wrote:
On Wed, May 30, 2018 at 3:34 PM, Carlos E. R. <> wrote:
Hi,
I can't ping my virtual box VM machines, but I can from VM to host.
cer@Telcontar:~> ping 10.0.2.15
This is user LAN address which is not visible on host at all. Traffic from VM ends up in virtualbox process which then sends it further on its behalf. You may consider virtualbox process as NAT router; you cannot connect from outside to systems inside of NATed network. It may be possible to forward individual ports inside VM, just like in normal NAT case, I do not remember whether VB supports it (qemu does).
I'm using NAT, the same as with vmware. Connection from host to guest worked fine: ethernet0.present = "TRUE" ethernet0.connectionType = "nat" ethernet0.virtualDev = "e1000"
...
How should I best handle this issue?
You may start with reading virtualbox documentation which describes possible network types and their restrictions and then decide which one suits better in your use case.
Ok :-) -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 05/30/2018 08:53 AM, Carlos E. R. wrote:
I'm using NAT, the same as with vmware. Connection from host to guest worked fine:
ethernet0.present = "TRUE" ethernet0.connectionType = "nat" ethernet0.virtualDev = "e1000"
You might try bridge mode. That way the VMs are on the same network as the rest of the LAN. It also works with both IPv4 & IPv6. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-05-30 14:56, James Knott wrote:
On 05/30/2018 08:53 AM, Carlos E. R. wrote:
I'm using NAT, the same as with vmware. Connection from host to guest worked fine:
ethernet0.present = "TRUE" ethernet0.connectionType = "nat" ethernet0.virtualDev = "e1000"
You might try bridge mode. That way the VMs are on the same network as the rest of the LAN. It also works with both IPv4 & IPv6.
Hum. Drawing from the router dhcp. A 192.168.*.* doesn't seem so large now, it is getting crowded. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
Carlos E. R. wrote:
On 2018-05-30 14:56, James Knott wrote:
On 05/30/2018 08:53 AM, Carlos E. R. wrote:
I'm using NAT, the same as with vmware. Connection from host to guest worked fine:
ethernet0.present = "TRUE" ethernet0.connectionType = "nat" ethernet0.virtualDev = "e1000"
You might try bridge mode. That way the VMs are on the same network as the rest of the LAN. It also works with both IPv4 & IPv6.
Hum. Drawing from the router dhcp. A 192.168.*.* doesn't seem so large now, it is getting crowded.
I would have thought there is still some room - 60'000 machines? :-) -- Per Jessen, Zürich (26.4°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-05-30 15:05, Per Jessen wrote:
Carlos E. R. wrote:
On 2018-05-30 14:56, James Knott wrote:
On 05/30/2018 08:53 AM, Carlos E. R. wrote:
I'm using NAT, the same as with vmware. Connection from host to guest worked fine:
ethernet0.present = "TRUE" ethernet0.connectionType = "nat" ethernet0.virtualDev = "e1000"
You might try bridge mode. That way the VMs are on the same network as the rest of the LAN. It also works with both IPv4 & IPv6.
Hum. Drawing from the router dhcp. A 192.168.*.* doesn't seem so large now, it is getting crowded.
I would have thought there is still some room - 60'000 machines? :-)
255 only. The first asterisk is a zero, fixed. 255.255.255.0 mask. Obviously I don't have even 255 machines, but the isp router dhcp range goes from 192.168.1.132 to 192.168.1.199 only. The 192.168.1.200 - 192.168.1.223 range is also reserved for something else. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 05/30/2018 09:42 AM, Carlos E. R. wrote:
Obviously I don't have even 255 machines, but the isp router dhcp range goes from 192.168.1.132 to 192.168.1.199 only. The 192.168.1.200 - 192.168.1.223 range is also reserved for something else.
Can you not change it? If you can't can you disable it and provide your own DHCP server? There's absolutely no reason to be stingy with the addresses. If all else fails, you can always manually configure a static address outside the DHCP range. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-05-30 15:56, James Knott wrote:
On 05/30/2018 09:42 AM, Carlos E. R. wrote:
Obviously I don't have even 255 machines, but the isp router dhcp range goes from 192.168.1.132 to 192.168.1.199 only. The 192.168.1.200 - 192.168.1.223 range is also reserved for something else.
Can you not change it? If you can't can you disable it and provide your own DHCP server?
Nope. I would have to add a second router, and might break TV. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 05/30/2018 09:01 AM, Carlos E. R. wrote:
You might try bridge mode. That way the VMs are on the same network as the rest of the LAN. It also works with both IPv4 & IPv6. Hum. Drawing from the router dhcp. A 192.168.*.* doesn't seem so large now, it is getting crowded.
Well, it's easy enough to change your network size. Of course, on IPv6, you'll have 18.4 billion, billion addresses available. Hopefully, that will be enough. ;-) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-05-30 15:06, James Knott wrote:
On 05/30/2018 09:01 AM, Carlos E. R. wrote:
You might try bridge mode. That way the VMs are on the same network as the rest of the LAN. It also works with both IPv4 & IPv6. Hum. Drawing from the router dhcp. A 192.168.*.* doesn't seem so large now, it is getting crowded.
Well, it's easy enough to change your network size.
No, it is impossible. ISP supplied router, changing that breaks other undocumented configs
Of course, on IPv6, you'll have 18.4 billion, billion addresses available. Hopefully, that will be enough. ;-)
No IPv6 in sight for the near future here. Don't try to convince me, convince my ISP. Good luck with that :-( -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 05/30/2018 09:45 AM, Carlos E. R. wrote:
Of course, on IPv6, you'll have 18.4 billion, billion addresses available. Hopefully, that will be enough. ;-) No IPv6 in sight for the near future here. Don't try to convince me, convince my ISP. Good luck with that :-(
-
I believe I had previously mentioned he.net, where you can tunnel IPv6 over IPv4. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-05-30 15:58, James Knott wrote:
On 05/30/2018 09:45 AM, Carlos E. R. wrote:
Of course, on IPv6, you'll have 18.4 billion, billion addresses available. Hopefully, that will be enough. ;-) No IPv6 in sight for the near future here. Don't try to convince me, convince my ISP. Good luck with that :-(
-
I believe I had previously mentioned he.net, where you can tunnel IPv6 over IPv4.
Yes, you did, but I have no real interest in getting such a thing. I'll wait till my ISP provides IPv6 somewhere in the next fifty years. IF. Unless at sometime I find the need to browse to some IPv6 URL, which is not the case yet. :-} So far, I only have curiosity about IPv6. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 2018-05-30 14:56, James Knott wrote:
On 05/30/2018 08:53 AM, Carlos E. R. wrote:
I'm using NAT, the same as with vmware. Connection from host to guest worked fine:
ethernet0.present = "TRUE" ethernet0.connectionType = "nat" ethernet0.virtualDev = "e1000"
You might try bridge mode. That way the VMs are on the same network as the rest of the LAN. It also works with both IPv4 & IPv6.
What I need is the equivalent in VBox of what vmware calls NAT but is not. Networking inside my host machine plus connection to internet. And connection from inside my lan, perhaps, on a different 192.168 range than my LAN (192.168.74.*, or perhaps 172.16.243.*). I have to read docs. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On Wed, May 30, 2018 at 3:53 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:
On 2018-05-30 14:44, Andrei Borzenkov wrote:
On Wed, May 30, 2018 at 3:34 PM, Carlos E. R. <> wrote:
Hi,
I can't ping my virtual box VM machines, but I can from VM to host.
cer@Telcontar:~> ping 10.0.2.15
This is user LAN address which is not visible on host at all. Traffic from VM ends up in virtualbox process which then sends it further on its behalf. You may consider virtualbox process as NAT router; you cannot connect from outside to systems inside of NATed network. It may be possible to forward individual ports inside VM, just like in normal NAT case, I do not remember whether VB supports it (qemu does).
I'm using NAT,
Yes, that is exactly what I mean. This is pure virtual LAN completely implemented inside of virtualbox process.
the same as with vmware. Connection from host to guest worked fine:
ethernet0.present = "TRUE" ethernet0.connectionType = "nat" ethernet0.virtualDev = "e1000"
I cannot parse this text at all, sorry. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-05-30 16:27, Andrei Borzenkov wrote:
On Wed, May 30, 2018 at 3:53 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:
On 2018-05-30 14:44, Andrei Borzenkov wrote:
On Wed, May 30, 2018 at 3:34 PM, Carlos E. R. <> wrote:
Hi,
I can't ping my virtual box VM machines, but I can from VM to host.
cer@Telcontar:~> ping 10.0.2.15
This is user LAN address which is not visible on host at all. Traffic from VM ends up in virtualbox process which then sends it further on its behalf. You may consider virtualbox process as NAT router; you cannot connect from outside to systems inside of NATed network. It may be possible to forward individual ports inside VM, just like in normal NAT case, I do not remember whether VB supports it (qemu does).
I'm using NAT,
Yes, that is exactly what I mean. This is pure virtual LAN completely implemented inside of virtualbox process.
the same as with vmware. Connection from host to guest worked fine:
ethernet0.present = "TRUE" ethernet0.connectionType = "nat" ethernet0.virtualDev = "e1000"
I cannot parse this text at all, sorry.
It is the section of the vmware virtual machine configuration file regarding network, showing that it is using NAT. And yet, network connections works in both directions, guest <-> host. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 05/30/2018 08:34 AM, Carlos E. R. wrote:
I can't ping my virtual box VM machines, but I can from VM to host.
Is the VM network adapter set to bridged or NAT? If NAT, it works the same as NAT routers, which means you can't access devices behind the NAT. I have mine set to bridge. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-05-30 14:47, James Knott wrote:
On 05/30/2018 08:34 AM, Carlos E. R. wrote:
I can't ping my virtual box VM machines, but I can from VM to host.
Is the VM network adapter set to bridged or NAT? If NAT, it works the same as NAT routers, which means you can't access devices behind the NAT. I have mine set to bridge.
NAT, same as with vmware; with vmware it worked in both directions just fine - which now that I think, it shouldn't. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On Wed, May 30, 2018 at 3:54 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:
On 2018-05-30 14:47, James Knott wrote:
On 05/30/2018 08:34 AM, Carlos E. R. wrote:
I can't ping my virtual box VM machines, but I can from VM to host.
Is the VM network adapter set to bridged or NAT? If NAT, it works the same as NAT routers, which means you can't access devices behind the NAT. I have mine set to bridge.
NAT, same as with vmware;
VMware NAT equivalent in VirtualBox is "NAT network", not "NAT". -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-05-30 16:28, Andrei Borzenkov wrote:
On Wed, May 30, 2018 at 3:54 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:
On 2018-05-30 14:47, James Knott wrote:
On 05/30/2018 08:34 AM, Carlos E. R. wrote:
I can't ping my virtual box VM machines, but I can from VM to host.
Is the VM network adapter set to bridged or NAT? If NAT, it works the same as NAT routers, which means you can't access devices behind the NAT. I have mine set to bridge.
NAT, same as with vmware;
VMware NAT equivalent in VirtualBox is "NAT network", not "NAT".
Ah! Thank you :-) Huh, it does not allow me to choose it. It says "Invalid settings, no Nat Network name is currently specified". There is a "Name" entry from a selection list that displays "not selected", and there are no choices available. Also, the OK button is greyed out. Same thing happens on a different VM. :-( -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
Отправлено с iPhone
30 мая 2018 г., в 21:49, Carlos E. R. <robin.listas@telefonica.net> написал(а):
On 2018-05-30 16:28, Andrei Borzenkov wrote: On Wed, May 30, 2018 at 3:54 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:
On 2018-05-30 14:47, James Knott wrote:
On 05/30/2018 08:34 AM, Carlos E. R. wrote: I can't ping my virtual box VM machines, but I can from VM to host.
Is the VM network adapter set to bridged or NAT? If NAT, it works the same as NAT routers, which means you can't access devices behind the NAT. I have mine set to bridge.
NAT, same as with vmware;
VMware NAT equivalent in VirtualBox is "NAT network", not "NAT".
Ah! Thank you :-)
Huh, it does not allow me to choose it. It says "Invalid settings, no Nat Network name is currently specified". There is a "Name" entry from a selection list that displays "not selected", and there are no choices available. Also, the OK button is greyed out.
There are no NAT network by default, you need to create it.
Same thing happens on a different VM.
:-(
-- Cheers / Saludos,
Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-05-30 22:17, Andrei Borzenkov wrote:
Отправлено с iPhone
30 мая 2018 г., в 21:49, Carlos E. R. <robin.listas@telefonica.net> написал(а):
On 2018-05-30 16:28, Andrei Borzenkov wrote: On Wed, May 30, 2018 at 3:54 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:
On 2018-05-30 14:47, James Knott wrote:
On 05/30/2018 08:34 AM, Carlos E. R. wrote: I can't ping my virtual box VM machines, but I can from VM to host.
Is the VM network adapter set to bridged or NAT? If NAT, it works the same as NAT routers, which means you can't access devices behind the NAT. I have mine set to bridge.
NAT, same as with vmware;
VMware NAT equivalent in VirtualBox is "NAT network", not "NAT".
Ah! Thank you :-)
Huh, it does not allow me to choose it. It says "Invalid settings, no Nat Network name is currently specified". There is a "Name" entry from a selection list that displays "not selected", and there are no choices available. Also, the OK button is greyed out.
There are no NAT network by default, you need to create it.
How? I just want to click on an option that does the same as "NAT" does in vmware player. Click and shoot. Done. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 2018-05-30 14:34, Carlos E. R. wrote: I found some info, but this mode is not what I want. It is not equivalent to vmware NAT mode. <https://www.thomas-krenn.com/en/wiki/Network_Configuration_in_VirtualBox> +++------------------------ NAT service Network Address Translation Service is a new NAT variant, which was newly introduced (experimental) with VirtualBox 4.3. The functionality is similar to a router. Direct access to the client systems from outside the network is prevented and the guest systems can communicate with TCP and UDP over IPv4 and IPv6 to each other and to the outside world. The NAT service is connected to an internal network. Virtual machines using this service should be connected to this internal network. The name of the internal network is selected when configuring the NAT service. The internal network will be recreated if it does not already exist. Example configuration of a static NAT network VBoxManage natnetwork add -t nat-int-network -n "192.168.15.0/24" -e natnetwork is the name of the internal network. 192.168.15.0/24 represents the network and subnet mask. 192.168.15.1 is the gateway address. Example configuration with DHCP server VBoxManage natnetwork add -t nat-int-network -n "192.168.15.0/24" -e -h on Adding a DHCP server later VBoxManage natnetwork modify -t nat-int-network -h on For more information and configuration options, see Network Address Translation Service (Virtualbox Manual). ------------------------++- +++------------------------ <https://www.virtualbox.org/manual/ch06.html#network_nat_service> 6.4. Network Address Translation Service The Network Address Translation (NAT) service works in a similar way to a home router, grouping the systems using it into a network and preventing systems outside of this network from directly accessing systems inside it, but letting systems inside communicate with each other and with systems outside using TCP and UDP over IPv4 and IPv6. A NAT service is attached to an internal network. Virtual machines which are to make use of it should be attached to that internal network. The name of internal network is chosen when the NAT service is created and the internal network will be created if it does not already exist. An example command to create a NAT network is: VBoxManage natnetwork add --netname natnet1 --network "192.168.15.0/24" --enable Here, "natnet1" is the name of the internal network to be used and "192.168.15.0/24" is the network address and mask of the NAT service interface. By default in this static configuration the gateway will be assigned the address 192.168.15.1 (the address following the interface address), though this is subject to change. To attach a DHCP server to the internal network, we modify the example as follows: VBoxManage natnetwork add --netname natnet1 --network "192.168.15.0/24" --enable --dhcp on ... ------------------------++- (What, no GUI setup? Astonishing) This is way more complex to setup than in vmware. There, I just clicked on "NAT" and everything was ready. It did have a DHCP server. But most importantly, communication from host machine to guest over ssh, for instance, just worked, contrary to what would happen from outside a nat router. What was blocked was communication from other computers in the home LAN, ie, outside the host machine. This is what I want, and I don't see the exact equivalent in the documentation I read. +++------------------------ Internal Networking Only those guest systems that have been connected to the same internal network will be able to communicate with each other in the internal network configuration. Communication with the host system or another network outside of VirtualBox will not be possible.[6] ------------------------++- No communication with the host? Then no. +++------------------------ Host-only Networking In this mode, communication between connected guest systems and the host system is possible.[7] Customized network interfaces will be used on the host system for the host-only network, such as: vboxnet0. The IP address on the host as well as the DHCP server for this network will be configured directly in VirtualBox: ------------------------++- I don't see clearly if communication between host and guests is possible, and what happens with Internet (in vmware this mode doesn't connect with internet). +++------------------------ Generic networking There are currently two possible sub-modes for Generic networking mode: UDP Tunnel[8] VDE (Virtual Distributed Ethernet) networking ------------------------++- I don't understand what this is. <https://www.virtualbox.org/manual/ch06.html#network_udp_tunnel> «This networking mode allows to interconnect virtual machines running on different hosts.» «Technically this is done by encapsulating Ethernet frames sent or received by the guest network card into UDP/IP datagrams, and sending them over any network available to the host.» Huh, no. I don't want this. <https://www.virtualbox.org/manual/ch06.html#network_vde> 6.9. VDE networking «Virtual Distributed Ethernet (VDE[32]) is a flexible, virtual network infrastructure system, spanning across multiple hosts in a secure way. It allows for L2/L3 switching, including spanning-tree protocol, VLANs, and WAN emulation. It is an optional part of VirtualBox which is only included in the source code.» «The basic building blocks of the infrastructure are VDE switches, VDE plugs and VDE wires which inter-connect the switches.» Wow, no way. +++------------------------ Bridged Networking In this mode, the guest system will receive direct access to the network, to which the host system has been connected. ------------------------++- Maybe, but on a different IP range. Is that possible? <https://www.virtualbox.org/manual/ch06.html#network_bridged> +++------------------------ 6.5. Bridged networking With bridged networking, VirtualBox uses a device driver on your host system that filters data from your physical network adapter. This driver is therefore called a "net filter" driver. This allows VirtualBox to intercept data from the physical network and inject data into it, effectively creating a new network interface in software. When a guest is using such a new software interface, it looks to the host system as though the guest were physically connected to the interface using a network cable: the host can send data to the guest through that interface and receive data from it. This means that you can set up routing or bridging between the guest and the rest of your network. For this to work, VirtualBox needs a device driver on your host system. The way bridged networking works has been completely rewritten with VirtualBox 2.0 and 2.1, depending on the host operating system. From the user perspective, the main difference is that complex configuration is no longer necessary on any of the supported host operating systems.[31] ------------------------++- Yes, this is similar to what vmware does on bridged mode... but this breaks the isolation between the guest and LAN. I do not like that. I want only communication between host and guest in both directions, and between other guests. Occasionally, I can change one machine to bridged to communicate with LAN, but this I did only once. So I'm very confused and don't know what mode to use to achieve it. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 2018-05-30 23:17, Carlos E. R. wrote:
On 2018-05-30 14:34, Carlos E. R. wrote:
+++------------------------ Host-only Networking
In this mode, communication between connected guest systems and the host system is possible.[7]
Customized network interfaces will be used on the host system for the host-only network, such as: vboxnet0. The IP address on the host as well as the DHCP server for this network will be configured directly in VirtualBox: ------------------------++-
I don't see clearly if communication between host and guests is possible, and what happens with Internet (in vmware this mode doesn't connect with internet).
I can ssh from host to guest, but not the reverse. And no internet. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On Thu, May 31, 2018 at 12:17 AM, Carlos E. R. <robin.listas@telefonica.net> wrote:
On 2018-05-30 14:34, Carlos E. R. wrote:
I found some info, but this mode is not what I want. It is not equivalent to vmware NAT mode.
Yes, I stay corrected. I was sure it worked this way, but rechecking "NAT network" is indeed not visible on host (and virtualbox documentation confirms that). Sorry. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Andrei Borzenkov -
Carlos E. R. -
James Knott -
Per Jessen