Hi,

Please clarify this behaviour.

Regards,
Ed

On Tue, Jul 3, 2012 at 9:30 AM, edward wilson
<[email protected]>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 <[email protected]> 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
[email protected]
http://openvswitch.org/mailman/listinfo/discuss

Reply via email to