On Thu, Feb 10, 2011 at 11:46:48PM +0530, Ramana Reddy wrote: > Assume that dp0 contains 4 ports: > $sudo ovs-dpctl show br0 > system@dp0: > flows: cur:15, soft-max:1024, hard-max:1048576 > ports: cur:5, max:1024 > groups: max:16 > lookups: frags:0, hit:2034975, missed:136958, lost:0 > queues: max-miss:100, max-action:100 > port 0: br0 (internal) > port 1: eth0 > port 2: br0.10 > port 3: br0.20 > > Now a vlan packet with tag = 10 is received to OVS, and the br0.10 is > configured as > > $sudo ovs-vsctl add-port br0 br0.10 tag=10 -- set interface br0.10 > type=internal > $sudo ifconfig br0.10 192.168.x.x ( similar set up has done for br0.20) > > > Now the default action taken place in OVS is : strip_vlan(10), output:2 > > Now the packet becomes non vlan packet after this actions. > > Now I want to write another flow rule, which takes this stripped vlan > packet > as input and apply this new rule on this packet and send to another port > (In this case port 3). > > In other way, applying the new flow rule on those packets which are > received at output > port of the previous action(s) ( in this case, the default action taken > by ovs).
An output action causes a packet to be sent out. It doesn't loop back into the flow table for further consideration. OVS doesn't support anything like that. You can probably do what you are trying to accomplish using OpenFlow rules, but you would have to write rules that do the whole job, instead of attempting to pick up after some other logic has already done part of it. _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org
