From 0c9328aa0204db820689c8eeef80c570f7760dca Mon Sep 17 00:00:00 2001 From: Florian Reimold <11774314+FlorianReimold@users.noreply.github.com> Date: Tue, 8 Aug 2023 12:43:59 +0200 Subject: [PATCH] Added linebreaks in very long line :) --- doc/rst/advanced/ecal_in_docker.rst | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/doc/rst/advanced/ecal_in_docker.rst b/doc/rst/advanced/ecal_in_docker.rst index 9c3b1e663e..f0b97cf471 100644 --- a/doc/rst/advanced/ecal_in_docker.rst +++ b/doc/rst/advanced/ecal_in_docker.rst @@ -239,7 +239,12 @@ In eCAL, you are able to set host belonging over network borders by utilizing th #. Configure the Host network - - eCAL is sending UDP messages to a multicast IP group ``239.0.0.0/24``, further information in :ref:`Getting Started Section `. The idea is now, to successfully receive those messages from your previously started container on your host. For that, you need to add a route to your routing table. By typing ``ifconfig`` in your shell, you can identify the right docker network. In our case, the prefix of the docker network is always ``br`` followed by random numbers. After identifying the right network, run following command. + - eCAL is sending UDP messages to a multicast IP group ``239.0.0.0/24``, further information in :ref:`Getting Started Section `. + The idea is now, to successfully receive those messages from your previously started container on your host. + For that, you need to add a route to your routing table. + By typing ``ifconfig`` in your shell, you can identify the right docker network. + In our case, the prefix of the docker network is always ``br`` followed by random numbers. + After identifying the right network, run following command. .. code-block:: bash