---
title: "Network limits per dedicated server port"
sidebar_label: "Network limits"
sidebar_position: 5
description: "Network limits per dedicated server port for MAC addresses and broadcast traffic"
---

import Formbricks from '@theme/MDXComponents/Formbricks'

# Network limits per dedicated server port

When ordering a dedicated server, limits are automatically applied to the network equipment. These limits work for both local ports and internet ports. For servers with [MC-LAG](/dedicated/networks/mc-lag.mdx), the limits apply to the entire aggregated interface (bond).

## MAC address quantity limits \{#mac-address-limits}

By default, every dedicated server is assigned a limit of 25 MAC addresses per switch port.

If the MAC address limit is exceeded on a server, you may experience partial loss of connectivity between this server and the internet or other machines in your local network.

Upon your request in a ticket, this limit can be increased to 100 MAC addresses.

A limit higher than 100 MAC addresses may be set if technically feasible; to clarify, [create a ticket](https://my.selectel.ru/tickets/create/).

## Broadcast traffic limits \{#broadcast-traffic-limits}

For a dedicated server, there are limits on broadcast traffic (broadcast, unknown-unicast, and multicast) of 10 MB/sec per port for each individual traffic type.

All traffic exceeding the specified limit is discarded by the network equipment.

The limit is most often exceeded in the following cases:

* if network exchange between machines involves a large volume of multicast traffic. In particular, network protocols such as OSPF, RIPv2, VRRP, and clustering solutions like Corosync often use multicast;
* if traffic between servers is strictly one-way. In this case, network equipment may classify the traffic as unknown-unicast.

<Formbricks />
