X-Git-Url: http://git.onelab.eu/?a=blobdiff_plain;f=tutorial%2FTutorial;h=0506a20751efc5eb3ba78b189505d2930f3f6b8a;hb=ec988646afe6aee6a63d6894a3e9b50f715d5941;hp=b8dfc5488e841a56c6f6c360dce82223e7ebbf52;hpb=eeecce05e14a6c62ff531801c0f27e54131a545c;p=sliver-openvswitch.git

diff --git a/tutorial/Tutorial b/tutorial/Tutorial
index b8dfc5488..0506a2075 100644
--- a/tutorial/Tutorial
+++ b/tutorial/Tutorial
@@ -253,7 +253,7 @@ A switch should also not forward IEEE 802.1D Spanning Tree Protocol
 packets with reserved multicast protocols:
 
     ovs-ofctl add-flow br0 \
-        "table=0, dl_dst=01:08:c2:00:00:00/ff:ff:ff:ff:ff:f0, actions=drop"
+        "table=0, dl_dst=01:80:c2:00:00:00/ff:ff:ff:ff:ff:f0, actions=drop"
 
 We could add flows to drop other protocols, but these demonstrate the
 pattern.
@@ -277,7 +277,7 @@ one way or another, perhaps with common network testing tools like
 difficult with our simulated switch, since it's not visible to the
 operating system.
 
-Bur our simulated switch has a few specialized testing tools.  The
+But our simulated switch has a few specialized testing tools.  The
 most powerful of these tools is "ofproto/trace".  Given a switch and
 the specification of a flow, "ofproto/trace" shows, step-by-step, how
 such a flow would be treated as it goes through the switch.
@@ -287,12 +287,12 @@ such a flow would be treated as it goes through the switch.
 
 Try this command:
 
-    ovs-appctl ofproto/trace br0 in_port=1,dl_dst=01:08:c2:00:00:05
+    ovs-appctl ofproto/trace br0 in_port=1,dl_dst=01:80:c2:00:00:05
 
 The output should look something like this:
 
-    Flow: metadata=0,in_port=1,vlan_tci=0x0000,dl_src=00:00:00:00:00:00,dl_dst=01:08:c2:00:00:05,dl_type=0x0000
-    Rule: table=0 cookie=0 dl_dst=01:08:c2:00:00:00/ff:ff:ff:ff:ff:f0
+    Flow: metadata=0,in_port=1,vlan_tci=0x0000,dl_src=00:00:00:00:00:00,dl_dst=01:80:c2:00:00:05,dl_type=0x0000
+    Rule: table=0 cookie=0 dl_dst=01:80:c2:00:00:00/ff:ff:ff:ff:ff:f0
     OpenFlow actions=drop
 
     Final flow: unchanged
@@ -315,11 +315,11 @@ interesting here.
 
 Try another command:
 
-    ovs-appctl ofproto/trace br0 in_port=1,dl_dst=01:08:c2:00:00:10
+    ovs-appctl ofproto/trace br0 in_port=1,dl_dst=01:80:c2:00:00:10
 
 The output should be:
 
-    Flow: metadata=0,in_port=1,vlan_tci=0x0000,dl_src=00:00:00:00:00:00,dl_dst=01:08:c2:00:00:10,dl_type=0x0000
+    Flow: metadata=0,in_port=1,vlan_tci=0x0000,dl_src=00:00:00:00:00:00,dl_dst=01:80:c2:00:00:10,dl_type=0x0000
     Rule: table=0 cookie=0 priority=0
     OpenFlow actions=resubmit(,1)
 
@@ -511,7 +511,7 @@ Here's how you can interpret each part of the "learn" action above:
         Make the flow that we add to flow table 10 match the same VLAN
         ID that the packet we're currently processing contains.  This
         effectively scopes the MAC learning entry to a single VLAN,
-        which is the ordinary behavior for a VLAN-aware siwtch.
+        which is the ordinary behavior for a VLAN-aware switch.
 
     NXM_OF_ETH_DST[]=NXM_OF_ETH_SRC[]