diff options
| author | axel@tripier.fr <axel@tripier.fr> | 2018-04-27 16:59:50 +0200 |
|---|---|---|
| committer | Ben Pfaff <blp@ovn.org> | 2018-05-09 14:33:39 -0700 |
| commit | aef264f315e098fce1a412a9b6a28f84485040ff (patch) | |
| tree | cdb9722696558ec50254c14a89728b25ffc0af5a /Documentation/tutorials | |
| parent | 35b2520a9c5ed3e2593423f01486b8fd86a64235 (diff) | |
| download | openvswitch-aef264f315e098fce1a412a9b6a28f84485040ff.tar.gz | |
Doc: Fix commands not being shown in code blocks
Some commands are not shown in code blocks in the Advances Features
tutorial, they are shown as variable width text because of a missing ":"
to designate them as code blocks.
Signed-off-by: Axel Tripier <axel@tripier.fr>
Signed-off-by: Ben Pfaff <blp@ovn.org>
Diffstat (limited to 'Documentation/tutorials')
| -rw-r--r-- | Documentation/tutorials/ovs-advanced.rst | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/tutorials/ovs-advanced.rst b/Documentation/tutorials/ovs-advanced.rst index 992182d0e..db8a53ebc 100644 --- a/Documentation/tutorials/ovs-advanced.rst +++ b/Documentation/tutorials/ovs-advanced.rst @@ -730,7 +730,7 @@ which ought to show roughly the following, with extraneous details removed:: The other way is to inject a packet to take advantage of the learning entry. For example, we can inject a packet on p2 whose destination is the MAC address -that we just learned on p1: +that we just learned on p1:: $ ovs-appctl ofproto/trace br0 \ in_port=2,dl_src=90:00:00:00:00:01,dl_dst=f0:00:00:00:00:01 -generate @@ -767,7 +767,7 @@ the learned port ``p1`` into register ``0``:: If you read the commands above carefully, then you might have noticed that they simply have the Ethernet source and destination addresses exchanged. That -means that if we now rerun the first ``ovs-appctl`` command above, e.g.: +means that if we now rerun the first ``ovs-appctl`` command above, e.g.:: $ ovs-appctl ofproto/trace br0 \ in_port=1,dl_vlan=20,dl_src=f0:00:00:00:00:01,dl_dst=90:00:00:00:00:01 \ @@ -930,7 +930,7 @@ Now, if we rerun our first command:: -generate ...we can see that the result is no longer a flood but to the specified learned -destination port ``p4``: +destination port ``p4``:: Datapath actions: pop_vlan,4 |