On Wed, Apr 09, 2014 at 04:55:51PM +0100, Rafael Gomes wrote:
> I am using the topology that I sent you in the attached file. I'm trying to
> ping between host 1 and host 2, encapsulating the traffic of each host in a
> vlan, more specifically vlan 100. For that I created four flows to make the
> ping work but it doesn't, because the rules are not applied. With wireshark I
> can see the traffic enter the switch 01 two ARP one with vlan_id=100 and
> without vlan_id but it doesn't come out on any port. The ARP traffic without
> vlan_id had mac_source the controller Opendaylight.
Did you read the FAQ?
Q: My OpenFlow controller doesn't see the VLANs that I expect.
A: The configuration for VLANs in the Open vSwitch database (e.g. via
ovs-vsctl) only affects traffic that goes through Open vSwitch's
implementation of the OpenFlow "normal switching" action. By
default, when Open vSwitch isn't connected to a controller and
nothing has been manually configured in the flow table, all traffic
goes through the "normal switching" action. But, if you set up
OpenFlow flows on your own, through a controller or using ovs-ofctl
or through other means, then you have to implement VLAN handling
yourself.
You can use "normal switching" as a component of your OpenFlow
actions, e.g. by putting "normal" into the lists of actions on
ovs-ofctl or by outputting to OFPP_NORMAL from an OpenFlow
controller. In situations where this is not suitable, you can
implement VLAN handling yourself, e.g.:
- If a packet comes in on an access port, and the flow table
needs to send it out on a trunk port, then the flow can add
the appropriate VLAN tag with the "mod_vlan_vid" action.
- If a packet comes in on a trunk port, and the flow table
needs to send it out on an access port, then the flow can
strip the VLAN tag with the "strip_vlan" action.
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
