X-Git-Url: http://git.onelab.eu/?a=blobdiff_plain;f=FAQ;h=6c79efefb1c29e35d5864faec06631ee583af898;hb=6620f928738c745a050335e17bf8f7801f5500a5;hp=a08d65c23b240e68c4e288ff845547ee4d92581d;hpb=cd31d5001ebb500a75e814c17843da370fae49e5;p=sliver-openvswitch.git

diff --git a/FAQ b/FAQ
index a08d65c23..6c79efefb 100644
--- a/FAQ
+++ b/FAQ
@@ -1403,9 +1403,9 @@ A: Yes, OpenFlow requires a switch to ignore attempts to send a packet
    even be convenient, e.g. it is often the desired behavior in a flow
    that forwards a packet to several ports ("floods" the packet).
 
-   Sometimes one really needs to send a packet out its ingress port.
-   In this case, output to OFPP_IN_PORT, which in ovs-ofctl syntax is
-   expressed as just "in_port", e.g.:
+   Sometimes one really needs to send a packet out its ingress port
+   ("hairpin"). In this case, output to OFPP_IN_PORT, which in
+   ovs-ofctl syntax is expressed as just "in_port", e.g.:
 
        ovs-ofctl add-flow br0 in_port=2,actions=in_port