<?xml version="1.0" encoding="UTF-8"?>
<xliff xmlns="urn:oasis:names:tc:xliff:document:1.1" version="1.1">
  <file original="NoName" source-language="en" datatype="plaintext" target-language="en">
    <body>
      <trans-unit xml:space="preserve" approved="no" id="9ff486bbb45cddd8" weblate-flags="read-only">
        <source>Local Area Networks: The Spanning Tree Protocol and Virtual LANs</source>
        <target state="translated">Local Area Networks: The Spanning Tree Protocol and Virtual LANs</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/lan.rst</context>
          <context context-type="linenumber">5</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="1d97688b164b9577" weblate-flags="read-only">
        <source>Exercises</source>
        <target state="translated">Exercises</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/lan.rst</context>
          <context context-type="linenumber">18</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="6954c122d3addddd" weblate-flags="read-only">
        <source>Consider the switched network shown in Fig. 1. What is the spanning tree that will be computed by 802.1d in this network assuming that all links have a unit cost ? Indicate the state of each port.</source>
        <target state="translated">Consider the switched network shown in Fig. 1. What is the spanning tree that will be computed by 802.1d in this network assuming that all links have a unit cost ? Indicate the state of each port.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/lan.rst</context>
          <context context-type="linenumber">20</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="e6d9af465a2267c1" weblate-flags="read-only">
        <source>Fig. 1. A small network composed of Ethernet switches</source>
        <target state="translated">Fig. 1. A small network composed of Ethernet switches</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/lan.rst</context>
          <context context-type="linenumber">26</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="7541808e29dcb791" weblate-flags="read-only">
        <source>Consider the switched network shown in Fig. 1. In this network, assume that the LAN between switches S3 and S12 fails. How should the switches update their port/address tables after the link failure ?</source>
        <target state="translated">Consider the switched network shown in Fig. 1. In this network, assume that the LAN between switches S3 and S12 fails. How should the switches update their port/address tables after the link failure ?</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/lan.rst</context>
          <context context-type="linenumber">28</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="8aa4003520975735" weblate-flags="read-only">
        <source>Consider the switched network shown in the figure below. Compute the Spanning Tree of this network.</source>
        <target state="translated">Consider the switched network shown in the figure below. Compute the Spanning Tree of this network.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/lan.rst</context>
          <context context-type="linenumber">31</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="e80581b1e44bdc0c" weblate-flags="read-only">
        <source>Many enterprise networks are organized with a set of backbone devices interconnected by using a full mesh of links as shown in Fig.2. In this network, what are the benefits and drawbacks of using Ethernet switches and IP routers running OSPF ?</source>
        <target state="translated">Many enterprise networks are organized with a set of backbone devices interconnected by using a full mesh of links as shown in Fig.2. In this network, what are the benefits and drawbacks of using Ethernet switches and IP routers running OSPF ?</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/lan.rst</context>
          <context context-type="linenumber">56</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="924360147a8ceb54" weblate-flags="read-only">
        <source>Fig. 2. A typical enterprise backbone network</source>
        <target state="translated">Fig. 2. A typical enterprise backbone network</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/lan.rst</context>
          <context context-type="linenumber">62</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="9c560ddac15d7ef3" weblate-flags="read-only">
        <source>In the network depicted in Fig. 3, the host `H0` performs a traceroute toward its peer `H1` (designated by its name) through a network composed of switches and routers. Explain precisely the frames, packets, and segments exchanged since the network was turned on. You may assign addresses if you need to.</source>
        <target state="translated">In the network depicted in Fig. 3, the host `H0` performs a traceroute toward its peer `H1` (designated by its name) through a network composed of switches and routers. Explain precisely the frames, packets, and segments exchanged since the network was turned on. You may assign addresses if you need to.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/lan.rst</context>
          <context context-type="linenumber">64</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="9225623d969533c2" weblate-flags="read-only">
        <source>Fig. 3. Host `H0` performs a traceroute towards its peer `H1` through a network composed of switches and routers</source>
        <target state="translated">Fig. 3. Host `H0` performs a traceroute towards its peer `H1` through a network composed of switches and routers</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/lan.rst</context>
          <context context-type="linenumber">70</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="eb437fd4cd9b0845" weblate-flags="read-only">
        <source>In the network represented in Fig. 4, can the host `H0` communicate with `H1` and vice-versa? Explain. Add whatever you need in the network to allow them to communicate.</source>
        <target state="translated">In the network represented in Fig. 4, can the host `H0` communicate with `H1` and vice-versa? Explain. Add whatever you need in the network to allow them to communicate.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/lan.rst</context>
          <context context-type="linenumber">77</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="ba4e7d6dfb5c8db5" weblate-flags="read-only">
        <source>Fig. 4. Can `H0` and `H1` communicate ?</source>
        <target state="translated">Fig. 4. Can `H0` and `H1` communicate ?</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/lan.rst</context>
          <context context-type="linenumber">83</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="aa8dd4a4fe187e51" weblate-flags="read-only">
        <source>Consider the network depicted in Fig. 5. Both of the hosts `H0` and `H1` have two interfaces: one connected to the switch `S0` and the other one to the switch `S1`. Will the link between `S0` and `S1` ever be used? If so, under which assumptions? Provide a comprehensive answer.</source>
        <target state="translated">Consider the network depicted in Fig. 5. Both of the hosts `H0` and `H1` have two interfaces: one connected to the switch `S0` and the other one to the switch `S1`. Will the link between `S0` and `S1` ever be used? If so, under which assumptions? Provide a comprehensive answer.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/lan.rst</context>
          <context context-type="linenumber">85</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="2aa13b6004d45daa" weblate-flags="read-only">
        <source>Fig. 5. Will the link between `S0` and `S1` ever be used?</source>
        <target state="translated">Fig. 5. Will the link between `S0` and `S1` ever be used?</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/lan.rst</context>
          <context context-type="linenumber">91</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="e2c7d55015278b58" weblate-flags="read-only">
        <source>Most commercial Ethernet switches are able to run the Spanning tree protocol independently on each VLAN. What are the benefits of using per-VLAN spanning trees ?</source>
        <target state="translated">Most commercial Ethernet switches are able to run the Spanning tree protocol independently on each VLAN. What are the benefits of using per-VLAN spanning trees ?</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/lan.rst</context>
          <context context-type="linenumber">93</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="ce4d33d6b9051951" weblate-flags="read-only">
        <source>Testing the Spanning Tree with IPMininet</source>
        <target state="translated">Testing the Spanning Tree with IPMininet</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/lan.rst</context>
          <context context-type="linenumber">115</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="b5d855d23067b79f" weblate-flags="read-only">
        <source>IPMininet_ can also be used to configure the Spanning Tree protocol on Linux hosts that act as Ethernet switches. Let us consider the simple Ethernet network shown in the figure below.</source>
        <target state="translated">IPMininet_ can also be used to configure the Spanning Tree protocol on Linux hosts that act as Ethernet switches. Let us consider the simple Ethernet network shown in the figure below.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/lan.rst</context>
          <context context-type="linenumber">117</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="2a5acb96f4610fed" weblate-flags="read-only">
        <source>This network can be launched with the IPMininet_ script shown below. The entire script is available from :download:`/exercises/ipmininet_scripts/stp.py`.</source>
        <target state="translated">This network can be launched with the IPMininet_ script shown below. The entire script is available from :download:`/exercises/ipmininet_scripts/stp.py`.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/lan.rst</context>
          <context context-type="linenumber">140</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="64c85461b7e7f8c4" weblate-flags="read-only">
        <source>The ``addSwitch`` method creates an Ethernet switch. It assigns a random MAC address to each switch and we can configure it with a priority that is used in the high order bits of the switch identifier. We add one IP address to each switch so that we can connect to them on mininet_. In practice, IPMininet_ configures the :manpage:`brtcl(8)` software that implements the Spanning Tree protocol on Linux. We can then create the links, configure their cost if required and launch tcpdump_ to capture the Ethernet frames that contain the messages of the Spanning Tree protocol.</source>
        <target state="translated">The ``addSwitch`` method creates an Ethernet switch. It assigns a random MAC address to each switch and we can configure it with a priority that is used in the high order bits of the switch identifier. We add one IP address to each switch so that we can connect to them on mininet_. In practice, IPMininet_ configures the :manpage:`brtcl(8)` software that implements the Spanning Tree protocol on Linux. We can then create the links, configure their cost if required and launch tcpdump_ to capture the Ethernet frames that contain the messages of the Spanning Tree protocol.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/lan.rst</context>
          <context context-type="linenumber">193</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="5816ab8b6e70e3bf" weblate-flags="read-only">
        <source>The network contains five nodes and six links.</source>
        <target state="translated">The network contains five nodes and six links.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/lan.rst</context>
          <context context-type="linenumber">195</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="b1c67f0b52e248c9" weblate-flags="read-only">
        <source>By using :manpage:`brtcl(8)`, we can easily observe the state of the Spanning Tree protocol on the different switches. Let us start with ``s3``, i.e. the root of the Spanning Tree.</source>
        <target state="translated">By using :manpage:`brtcl(8)`, we can easily observe the state of the Spanning Tree protocol on the different switches. Let us start with ``s3``, i.e. the root of the Spanning Tree.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/lan.rst</context>
          <context context-type="linenumber">211</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="67ca31c33557f4af" weblate-flags="read-only">
        <source>The first part of the output of the :manpage:`brctl(8)` command shows the state of the Spanning Tree software on the switch. The identifier of this switch is ``0003.f63545ab5f79`` and the root switch is itself. There is no root port on this switch since it is the root. The path cost is the cost of the path to reach the root switch, i.e. 0 on the root. Then the switch reports the different timers.</source>
        <target state="translated">The first part of the output of the :manpage:`brctl(8)` command shows the state of the Spanning Tree software on the switch. The identifier of this switch is ``0003.f63545ab5f79`` and the root switch is itself. There is no root port on this switch since it is the root. The path cost is the cost of the path to reach the root switch, i.e. 0 on the root. Then the switch reports the different timers.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/lan.rst</context>
          <context context-type="linenumber">246</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="efbdec64a8b9e394" weblate-flags="read-only">
        <source>The second part of the output provides the state of each switch port. Port ``s3-eth1`` is active and forwards data frames (state is set to `forwarding`). This port is a `designated` port. The cost of ``1`` is the cost associated to this interface. The same information is found for port ``s3-eth2``.</source>
        <target state="translated">The second part of the output provides the state of each switch port. Port ``s3-eth1`` is active and forwards data frames (state is set to `forwarding`). This port is a `designated` port. The cost of ``1`` is the cost associated to this interface. The same information is found for port ``s3-eth2``.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/lan.rst</context>
          <context context-type="linenumber">248</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="00b7e48f24d72d5c" weblate-flags="read-only">
        <source>The state of switch ``s9`` is different. The output of :manpage:`brctl(8)` indicates that the root identifier is ``0003.f63545ab5f79`` which is at a distance of ``1`` from switch ``s9``. The root port on ``s9`` is port `1`, i.e. ``s9-eth1``. Two of the ports of this switch forward data packets, the root port and the ``s9-eth3`` which is a designated port. The ``s9-eth2`` port is a blocked port.</source>
        <target state="translated">The state of switch ``s9`` is different. The output of :manpage:`brctl(8)` indicates that the root identifier is ``0003.f63545ab5f79`` which is at a distance of ``1`` from switch ``s9``. The root port on ``s9`` is port `1`, i.e. ``s9-eth1``. Two of the ports of this switch forward data packets, the root port and the ``s9-eth3`` which is a designated port. The ``s9-eth2`` port is a blocked port.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/lan.rst</context>
          <context context-type="linenumber">250</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="ce3b51f002a7b208" weblate-flags="read-only">
        <source>:manpage:`brctl(8)` also maintains a MAC address table that contains the Ethernet addresses that have been learned on each switch port.</source>
        <target state="translated">:manpage:`brctl(8)` also maintains a MAC address table that contains the Ethernet addresses that have been learned on each switch port.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/lan.rst</context>
          <context context-type="linenumber">293</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="93cb30abb9fb8305" weblate-flags="read-only">
        <source>Thanks to the traces collected by tcpdump_, we can easily analyze the messages exchanged by the switches. Here is the fist message sent by switch ``s3``.</source>
        <target state="translated">Thanks to the traces collected by tcpdump_, we can easily analyze the messages exchanged by the switches. Here is the fist message sent by switch ``s3``.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/lan.rst</context>
          <context context-type="linenumber">310</context>
        </context-group>
      </trans-unit>
    </body>
  </file>
</xliff>
