[Yandex Cloud documentation](../../index.md) > [Yandex BareMetal](../index.md) > [Concepts](index.md) > Network > Overview

# Network

The Yandex BareMetal network infrastructure includes public and private networks that ensure server connectivity with the internet and between each other.

![baremetal-network](../../_assets/baremetal/baremetal-network.svg)

## Public network {#public-network}

A [public network](public-network.md) is an internet-facing network to which all servers are physically connected. In public networks, [ephemeral](public-network.md#ephemeral-public-subnet) and [dedicated](public-network.md#public-subnet) public subnets are available.

For more information about public networks, see [Public network](public-network.md).

## Private network {#private-network}

A [private network](private-network.md) is a local network to which all servers from a single [pool](servers.md#server-pools) are connected. In private networks, [private subnets](private-network.md#private-subnet), [VRFs](private-network.md#vrf-segment), and [private connections to cloud networks](private-network.md#private-connection-to-vpc) are available.

For more information about private networks, see [Private network](private-network.md).

## MAC addresses of network interfaces {#mac-addresses}

You can [look up](../operations/servers/get-info.md) the MAC addresses of the BareMetal server network interfaces on the server information page under **Network interfaces**.

## Server routing table {#routing-table}

The BareMetal server’s OS must feature a [routing table](https://en.wikipedia.org/wiki/Routing_table) that sets traffic routes for the [public](#public-network) and [private](#private-network) networks at the same time.

The actual server routing table configuration depends on your OS; however, the routing table must follow this example:

```text
0.0.0.0/0 via <network_interface_in_public_network>
10.0.0.0/8 via <network_interface_in_private_network>
172.16.0.0/12 via <network_interface_in_private_network>
192.168.0.0/16 via <network_interface_in_private_network>
```

## Yandex BareMetal network traffic billing when communicating with other Yandex Cloud services {#traffic-pricing-pecs}

### Yandex Virtual Private Cloud {#vpc-traffic}

Traffic sent from Yandex Virtual Private Cloud to Yandex BareMetal public addresses is classified as outgoing traffic subject to the [VPC pricing policy](../../vpc/pricing.md#prices-traffic).

{% note info %}

To transfer large data volumes between Yandex Virtual Private Cloud and Yandex BareMetal, use [Yandex Cloud Interconnect](../../interconnect/index.md).

Traffic transmitted via Yandex Cloud Interconnect between private Yandex BareMetal and Yandex Virtual Private Cloud addresses in either direction is not billable.

{% endnote %}

### Yandex Object Storage {#storage-traffic}

Traffic between Yandex BareMetal and Yandex Object Storage is free of charge regardless of direction according to the [Object Storage pricing policy](../../storage/pricing.md#prices-traffic).

### Yandex Cloud Backup {#backup-traffic}

Traffic transmitted between Yandex BareMetal and [Yandex Cloud Backup](../../backup/index.md) is free of charge.

#### See also {#see-also}

* [Public network](public-network.md)
* [Private network](private-network.md)
* [DHCP in a Yandex BareMetal network](dhcp.md)
* [Reserving a BareMetal network connection using MC-LAG](mc-lag.md)
* [Restrictions in BareMetal networks](network-restrictions.md)