Skip to content
Snippets Groups Projects
Commit b334dbf2 authored by Adrián Rošinec's avatar Adrián Rošinec Committed by Ing. Klára Moravcová
Browse files

MTU details

parent 4c4d4efc
No related branches found
No related tags found
1 merge request!111MTU details
...@@ -40,10 +40,44 @@ Furthermore, IP addresses allocated from *public-muni-147-251-124-GROUP* and *pu ...@@ -40,10 +40,44 @@ Furthermore, IP addresses allocated from *public-muni-147-251-124-GROUP* and *pu
using only *public-cesnet-78-128-251-GROUP* and *private-muni-10-16-116* for group projects. using only *public-cesnet-78-128-251-GROUP* and *private-muni-10-16-116* for group projects.
Follow instructions at [changing the external network](/cloud/network) in order to change your public network. Follow instructions at [changing the external network](/cloud/network) in order to change your public network.
## Issues with network stability in Docker ## Issues with network MTU (Docker, kubernetes, custom network overlays)
OpenStack instances use 1442 bytes MTU (maximum transmission unit) instead of standard 1500 bytes MTU. The instance itself can set up correct MTU with its counterpart via Path MTU Discovery. Docker needs MTU set up explicitly. Refer documentation for setting up OpenStack compute server instances should use 1442 bytes MTU (maximum transmission unit) instead of the standard 1500 bytes MTU. The instance itself can set up the correct MTU with its counterpart via Path MTU Discovery. Docker needs MTU set up explicitly. Refer documentation for setting up 1442 MTU in [Docker](https://docs.docker.com/v17.09/engine/userguide/networking/default_network/custom-docker0/) or [Kubernetes](https://docs.projectcalico.org/v3.5/usage/configuration/mtu) or change the configuration with the steps below.
1442 MTU in [Docker](https://docs.docker.com/v17.09/engine/userguide/networking/default_network/custom-docker0/) or
[Kubernetes](https://docs.projectcalico.org/v3.5/usage/configuration/mtu). ### Changes in Docker daemon
```sh
# edit docker configuration
sudo vi /etc/docker/daemon.json
# MTU 1442 or lower
{
"mtu": 1442
}
# then restart docker
sudo systemctl restart docker
```
### MTU detection
You can use following bash function to detect end-to-end maximum packet size without packet fragmentation.
```sh
# detect_mtu <host>
# measure end-to-end MTU
function detect_mtu() {
local endpoint_host="$1"
for i_mtu in `seq 1200 20 1500` `seq 1500 50 9000`; do
if ping -M do -s $(( $i_mtu - 28 )) -c 5 "${endpoint_host}" >/dev/null; then
echo "Packets of size ${i_mtu} work as expected"
else
echo "Packets of size ${i_mtu} are blocked by MTU limit on the path to destination host ${endpoint_host}!"
break
fi
done
}
# execute
detect_mtu www.nic.cz
```
## Issues with proxy in private networks ## Issues with proxy in private networks
OpenStack instances can either use public or private networks. If you are using a private network and you need to access the internet for updates etc., OpenStack instances can either use public or private networks. If you are using a private network and you need to access the internet for updates etc.,
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment