# Network Adapter Type pada Virtual Box

## Network Types <a href="#network-types" id="network-types"></a>

VBox provides us 6 options to fullfill kinds of requirements.

### Not attached <a href="#option-1-not-attached" id="option-1-not-attached"></a>

With ‘Not attached’, the client machine runs as a standalone computer that has a network adapter without network cable plugging in.

### Network Address Translation(NAT) <a href="#option-2-network-address-translationnat" id="option-2-network-address-translationnat"></a>

‘NAT’ is a default option when VBox is installed. VBox provides a NAT router and DHCP service for every client os.

<figure><img src="https://totozhang.github.io/2015-12-24-network-topology-in-virtualbox/2.png" alt=""><figcaption></figcaption></figure>

If the host os can access the Internetso does the client os. From the physical network point of view, all of the packets which actually come from the different client os, are all from the Vbox process. At the same time, it’s also show us that the NAT network can be recursive. Now, if any user from the physical network need to access any of the client os in VBox, port forwarding setting should be considered.

### NAT Network <a href="#option-3-nat-network" id="option-3-nat-network"></a>

In this mode, all of the clients on VBox share the same NAT router. It’s just like the wifi router used at home. And we must create a NAT network manually before using it. (Virtual Box > Preferences > Network > Create)

<figure><img src="https://totozhang.github.io/2015-12-24-network-topology-in-virtualbox/3.png" alt=""><figcaption></figcaption></figure>

The key difference between NAT Network and NAT option is that, in the NAT Network, clients share the same router and gateway.

### Bridged Networking <a href="#option-4-bridged-networking" id="option-4-bridged-networking"></a>

In this mode, client and host machine are bridged in the same ethernet segment. In other words, the clients are connected to the physical network directly. If there’s a DHCP server, the clients get IP addresses automatically. Theoretically, in the bridged mode, either the clients or the VBox itself can provide the DHCP service for the network, and it highly possible result unpredictable conflicts. It’s not recommended to do this.

<figure><img src="https://totozhang.github.io/2015-12-24-network-topology-in-virtualbox/4.png" alt=""><figcaption></figcaption></figure>

### Internal Networking <a href="#option-5-internal-networking" id="option-5-internal-networking"></a>

In the process of developing a network application, it’s inevitable to capture the network data packets for debuging or test. Most of the time, engineers prefer the bridged mode. Sometimes it’s more useful to choose the internal network mode. For instance, if the packets will impact the physical network, we should prevent this kind of situation in product environment, or, if we need excluding the unnecessory interference packets, to simplify the analysing process. Sometimes maybe we also need an extra internal network like the topology for the nodes to communication with each other with heatbeat packets.

<figure><img src="https://totozhang.github.io/2015-12-24-network-topology-in-virtualbox/5.png" alt=""><figcaption></figcaption></figure>

### Host-only Networking <a href="#option-6-host-only-networking" id="option-6-host-only-networking"></a>

In this mode, it’s just like the internal mode, the only difference is that the host machine is added into the internal network. In this mode, it’s optional whether the VBox provides the DHCP service or not.

<figure><img src="https://totozhang.github.io/2015-12-24-network-topology-in-virtualbox/6.png" alt=""><figcaption></figcaption></figure>

### **Comparison of VirtualBox Network Modes** <a href="#option-6-host-only-networking" id="option-6-host-only-networking"></a>

For more convenience, let’s summarize all information about network modes supported by VirtualBox in this table:

<figure><img src="https://2370299969-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MTchLGQ78eoG4OiLFnV%2Fuploads%2FArs4C2AiCeaptb8jqqdG%2Fimage.png?alt=media&#x26;token=9ff4449f-1650-4ac0-9c87-816f9550eede" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://notes.anggipradana.com/tutorial/network-adapter-type-pada-virtual-box.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.