[ovs-discuss] Scary flow forwarding packets across ovs bridges

Chen Weiwen chenww at hotmail.com
Sat Aug 29 21:25:30 UTC 2015


I Think I figured out the reason and will work on it as peer port are configured on switch. No need help for this issue now.
Thanks

-weiwen
From: chenww at hotmail.com
To: discuss at openvswitch.org; chenww at hotmail.com
Subject: Scary flow forwarding packets across ovs bridges
Date: Sat, 29 Aug 2015 14:40:19 -0600




Dear Experts,
Need your help on OVS to explain this scary flow forwarding on Debian OS with OVS 2.3. You can see a SNAP packet
received on br-ex bridge port 2 got forwarded to br-int and br-data bridges below.
How could this happen?

 

# ovs-dpctl dump-flows

skb_priority(0),in_port(2),eth(src=00:9c:02:79:1b:75,dst=01:14:c2:44:1e:cc),eth_type(0/0xffff),
packets:0, bytes:0, used:never, actions:1,3,5,4

 

# ovs-dpctl show

system at ovs-system:

        lookups: hit:0
missed:3913 lost:0

        flows: 0

        masks:
hit:2009 total:0 hit/pkt:0.51

        port 0:
ovs-system (internal)

        port 1: br-ex
(internal)

        port 2: eth4

        port 3: br-int
(internal)

        port 4:
br-data (internal)

        port 5: eth3

 

# ovs-vsctl show

f53f59be-9e8b-4e65-bc96-8334b25a3510

    Bridge br-ex

        Port br-ex

            Interface
br-ex

                type:
internal

        Port phy-br-ex

            Interface
phy-br-ex

                type:
patch

               
options: {peer=int-br-ex}

        Port
"eth4"

            Interface
"eth4"

    Bridge br-data

        Port
phy-br-data

            Interface
phy-br-data

                type:
patch

               
options: {peer=int-br-data}

        Port
"eth3"

            Interface
"eth3"

        Port br-data

            Interface
br-data

                type:
internal

    Bridge br-int

        fail_mode:
secure

        Port int-br-ex

            Interface
int-br-ex

                type: patch

               
options: {peer=phy-br-ex}

        Port
int-br-data

            Interface
int-br-data

                type:
patch

               
options: {peer=phy-br-data}

        Port br-int

            Interface
br-int

                type:
internal

    ovs_version:
"2.3.0"

 

# ifconfig eth4

eth4      Link encap:Ethernet  HWaddr 52:54:00:5f:13:49

          inet6 addr:
fe80::5054:ff:fe5f:1349/64 Scope:Link

          UP BROADCAST
RUNNING MULTICAST  MTU:1500  Metric:1

          RX
packets:3730 errors:0 dropped:10 overruns:0 frame:0

          TX
packets:79 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0
txqueuelen:1000

          RX
bytes:262680 (256.5 KiB)  TX bytes:6518
(6.3 KiB)

 

# ifconfig eth3

eth3      Link
encap:Ethernet  HWaddr 52:54:00:29:b8:4f

          inet6 addr:
fe80::5054:ff:fe29:b84f/64 Scope:Link

          UP BROADCAST
RUNNING MULTICAST  MTU:1500  Metric:1

          RX
packets:308 errors:0 dropped:28 overruns:0 frame:0

          TX
packets:3672 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0
txqueuelen:1000

Thanks a lot!-weiwen


          RX bytes:24032
(23.4 KiB)  TX bytes:258738 (252.6 KiB) 		 	   		   		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20150829/1050d277/attachment-0002.html>


More information about the discuss mailing list