I would generally expect that to work. Maybe you should show us more of your flow table.
On Mon, Oct 17, 2016 at 10:14:16AM -0700, Tom Gajewski wrote: > My bad, that was obviously suppose to include the MAC in question. So > one more time, in an attempt to set a static MAC table entry: > > Table entry: > > 13 744 so:me:ma:cc > > Flow: > > ovs-ofctl add-flow mybridge dl_dst=so:me:ma:cc,actions=output:13 > > I guess what I'm asking is, what should a static flow that says "MAC > so:me:ma:cc lives on port 13" look like? Again, goal is to have a > static table entry like behavior accomplished with this flow. > > Cheers, > > --Tom > > On Mon, Oct 17, 2016 at 9:12 AM, Ben Pfaff <b...@ovn.org> wrote: > > On Mon, Oct 17, 2016 at 02:45:06AM -0700, Tom Gajewski wrote: > >> Hi all, > >> > >> It is my understanding that one cannot modify the cam (well I guess in > >> openvswitch land the mac table ;] ) directly. As I'm trying to set up > >> static entries. Do I need to use flows to accomplish this, is there no > >> other way to just modify this table?? > >> > >> As for flows, I did try to add some copying an outdated entry from the > >> mac table that read > >> > >> 13 744 so:me:ma:cc > >> > >> like this --> > >> > >> ovs-ofctl add-flow mybridge dl_dst=,actions=output:13 > >> > >> but that just seemed to do nothing, in fact in breaks connectivity to > >> that destination completely even if that MAC is in the table. So if I > >> do have to use flows to do this could someone tell me where I'm being > >> stupid? > > > > There's no direct way to modify the MAC-learning table. > > > > I don't know a reason why the flow that you've showed us would cause > > such big problems. The command does omit the MAC address, but that > > would only cause an error from ovs-ofctl, so I guess that the actual > > command included the MAC. > > > > Maybe you should show us more of your flow table. _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
