VirtualBox

source: vbox/trunk/doc/manual/en_US/dita/topics/security-networking.dita

Last change on this file was 107390, checked in by vboxsync, 5 months ago

Docs: bugref:10705. bugref: 10829. The docs build has been modified to split generated refentry dita files and the user manual files and the following commits from doc's team git repo has been applied:

0946136c74dda0483704db891345cb39548b4e28 Started consolidating known issues and troubleshooting information
845b847e6a8e778b38a57867e25ee5e086a73800 Added individual topics for list of known issues, integrated into Troubleshooting section.
bb574836aac775889bd61e4a72f489617fcb7d18 Removed EFI firmware from experimental features for 7.2
6d2e68b244869991e713d170ecd239739d99ba56 Moved known issues into Known Issues section
e2630c896561587718b5c3197c384a38d07014d5 Merge branch 'VBP-1461_experimental-features' into 'main'
0512e2cce51f49ccdc56f3381a2a0c924f2bd278 Feedback on known issues
a77d6c980f6ff5cad9d32b2fb9290990093a03fa Restructured host and guest OS topics
988af5cc9628f5de0806531bc98686f691a911fd Updates with feedbback from Jacob
982a61c9f25b22b745ec483e763e3d88efe59c40 Included feedback from Jacob
93181c8c6cc2d9a26bcccb1145cb0423c0d9f4c9 Updated known issues with feedback from Klaus
8bc369561c383f09b409fe5e44f507440b3735fb Created Legacy Guest OS section
d7932f55accdab7a03666302d58b8c941cd48be2 Moved known issues to more appropriate places for the info
2a4aa094ba8a7ac6894d2a777316eabf41746580 Further moving of known issues
baeabd5308c5519a4dc26b4197be9b00e419a85a Updated links to cli_topics

  • Property svn:eol-style set to native
  • Property svn:keywords set to Author Date Id Revision
File size: 1.8 KB
Line 
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>
Note: See TracBrowser for help on using the repository browser.

© 2025 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette