The OVS support for MPLS isn't complete. Perhaps you are running into a rough edge.
On Sat, Sep 21, 2013 at 11:05:24PM -0400, Feixiong Zhang wrote: > HI, > > actually I have tried this and there is no luck. the flow insertion > succeeds while the matching fails. Thanks anyway. > > > On Sat, Sep 21, 2013 at 9:46 PM, NS Srinivasa Murthy-B37840 < > [email protected]> wrote: > > > ** ** > > > > Hi,**** > > > > ** ** > > > > When IP Addresses are to be specified as match fields, it is a pre > > requisite to include the match field OFPXMT_OFB_ETH_TYPE with a value of > > 0x800 (IP Protocol.)**** > > > > ** ** > > > > Thanks**** > > > > -ns murthy**** > > > > ** ** > > > > *From:* [email protected] [mailto: > > [email protected]] *On Behalf Of *Feixiong Zhang > > *Sent:* Sunday, September 22, 2013 6:46 AM > > *To:* [email protected] > > *Subject:* [ovs-discuss] flow table question**** > > > > ** ** > > > > Hi, all > > > > I am trying to insert two flows in table0 and table 1 separately. The > > first flow entry tries to pop the MPLS header and the second entry will > > match the rest of the packet, like dl_src,dl_dst, nw_src ... fields. The > > following are my flows: > > > > table0: > > priority=0,mpls,in_port=2,**** > > > > mpls_label=3 > > ,actions=pop_mpls:0x0800,load:0xe->OXM_OF_METADATA[],resubmit(,1) > > > > table1: > > priority=32786,tcp,metadata=0xe,in_port=2,dl_src=90:e2:ba:3d:c0:f8,dl_dst=90:e2:ba:28:e6:98,nw_src=10.0.3.4,nw_dst=10.0.1.4 > > actions=output:3 > > > > But the matching will fail if nw_src and nw_dst field are set in the > > table1 flow rule, while there is no problem if only ethernet header is set. > > Does anyone have any idea about what's going on here. I would appreciate > > your help a lot. Thanks.**** > > > _______________________________________________ > discuss mailing list > [email protected] > http://openvswitch.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
