One oddity is that you are using 11:22:33:44:55:66 as an Ethernet source address when that's invalid as a source address (the multicast bit is set). I'd expect the NORMAL action to just drop such packets.
Beyond that I really don't understand what you're reporting. The distinction among access ports, trunks, etc., happens after the flow table look-up, so of course your incoming packets are being processed through the flow table. As I said, the default behavior (including VLAN types) is implemented in the "normal" action, not any time before that. On Thu, Jul 05, 2012 at 08:48:53AM +0530, edward wilson wrote: > Hi Ben, > > If you see my two flow entries made earlier both are having action "NORMAL" > but then also if I am making vnet port as access port with vlan 3 then all > tag packets are passing through this port and hitting the flow entry in > bridge. > > > cookie=0x0, duration=263.359s, table=0, n_packets=1, n_bytes=60, > ip,dl_vlan=3,dl_src=11:22:33:44:55:66 actions=NORMAL > > cookie=0x0, duration=65.157s, table=0, n_packets=1, n_bytes=60, > ip,dl_src=11:22:33:44:55:66 actions=NORMAL > > Regards, > Ed > > On Thu, Jul 5, 2012 at 3:13 AM, Ben Pfaff <b...@nicira.com> wrote: > > > The default behavior of the OVS switch is implemented through an action > > called "normal". If you write a flow that doesn't execute this action, > > then it is up to you to implement the VLAN behavior that you want. > > > > On Tue, Jul 03, 2012 at 09:30:44AM +0530, edward wilson wrote: > > > Hi Ben, > > > > > > > > > > > > Thanks for the quick response. > > > > > > But really sorry that I didn't get you fully. > > > > > > > > > > > > Is that mean this default behavior works for any switch except OVS or if > > my > > > understanding is wrong then please clarify how I can check the default > > > behavior of access port in OVS. > > > > > > > > > > > > 1. For me " Bridge should not get tag (any tag) packet from its access > > > port". Currently tag packet is coming out from access port and entry is > > > hitting in bridge but it should not. > > > > > > 2. And it is very strange that vlan 4 packet is coming from vlan 3 access > > > port to the switch (vlan 4 entry get hit on bridge) , this also I am not > > > able to understand. > > > > > > > > > > > > Please clarify both above issues. > > > > > > > > > > > > Regards, > > > > > > Ed > > > > > > > > > On Mon, Jul 2, 2012 at 10:25 PM, Ben Pfaff <b...@nicira.com> wrote: > > > > > > > On Mon, Jul 02, 2012 at 01:32:55PM +0530, edward wilson wrote: > > > > > I need to understand access port functionality in OVS and matching > > with > > > > > flow entry created on switch > > > > > As mentioned in man-page :- > > > > > > > > > > "Any packet with an 802.1Q header that ingresses on an access port is > > > > > dropped, regardless of whether the VLAN ID in the header is the > > access > > > > > port’s VLAN ID." > > > > > > > > > > > > > > > > > > > > But when I have vnet1 (VM attached to bridge) as access port( vlan > > 3) by > > > > > following command and created a below flow entries in bridge. > > > > > > > > The manpage is describing the default behavior when OpenFlow features > > > > are not in use, which is also the behavior of the "OFPP_NORMAL" > > > > action. When you write OpenFlow rules by hand, you override this > > > > default behavior. > > > > > > _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
