On Wed, May 28, 2014 at 02:03:42PM +0200, Ricardo Schmidt wrote: > On Tue, May 27, 2014 at 6:22 PM, Ben Pfaff <[email protected]> wrote: > > > On Tue, May 27, 2014 at 06:06:14PM +0200, Ricardo Schmidt wrote: > > > We couldn't find supporting material about the following problem on > > google. > > > Maybe some in the list is able to help us. We are using Ryu with OpenFlow > > > 1.3 and OVS 2.1.2. > > > > > > We are not really sure why we received the following message: > > > - error type: OFPET_PORT_MOD_FAILED > > > - error code: OFPPMFC_BAD_HW_ADDR > > > > In accordance with the OF1.3 spec, OVS sends this error if the hardware > > address in a port-mod message does not match the port's hardware > > address. > > > > Actually, that's the part we don't understand. Are we supposed to send a > port-mod message? We don't send it. In the example codes we found, none of > them implement the port-mod message.
That doesn't make sense. Let me repeat my previous advice: I suggest using transaction ids to match the error messages you are receiving to the requests you are sending. Then you can tell exactly why OVS sends those errors. _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
