1 | <?xml version='1.0' encoding='UTF-8'?>
|
---|
2 | <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
|
---|
3 | <topic xml:lang="en-us" id="security-networking">
|
---|
4 | <title>Networking</title>
|
---|
5 |
|
---|
6 | <body>
|
---|
7 | <p> The default networking mode for VMs is NAT which means that the VM acts like a computer
|
---|
8 | behind a router, see <xref href="network_nat.dita">Network Address Translation (NAT)</xref>.
|
---|
9 | The guest is part of a private subnet belonging to this VM and the guest IP is not visible
|
---|
10 | from the outside. This networking mode works without any additional setup and is sufficient
|
---|
11 | for many purposes. Remember that NAT allows access to the host operating system's loopback
|
---|
12 | interface. </p>
|
---|
13 | <p>
|
---|
14 | If bridged networking is used, the VM acts like a computer
|
---|
15 | inside the same network as the host, see
|
---|
16 | <xref href="network_bridged.dita">Bridged Networking</xref>. In this case, the guest has
|
---|
17 | the same network access as the host and a firewall might be
|
---|
18 | necessary to protect other computers on the subnet from a
|
---|
19 | potential malicious guest as well as to protect the guest from
|
---|
20 | a direct access from other computers. In some cases it is
|
---|
21 | worth considering using a forwarding rule for a specific port
|
---|
22 | in NAT mode instead of using bridged networking.
|
---|
23 | </p>
|
---|
24 | <p>
|
---|
25 | Some setups do not require a VM to be connected to the public
|
---|
26 | network at all. Internal networking, see
|
---|
27 | <xref href="network_internal.dita">Internal Networking</xref>, or host-only networking,
|
---|
28 | see <xref href="network_hostonly.dita">Host-Only Networking</xref>, are often sufficient
|
---|
29 | to connect VMs among each other or to connect VMs only with
|
---|
30 | the host but not with the public network.
|
---|
31 | </p>
|
---|
32 | </body>
|
---|
33 |
|
---|
34 | </topic>
|
---|