Hi Ben, I feel like I'm missing something, my action simply stores 5 packets, but shouldn't two "buffering" flows installed on two different switches be 2 separate instances of that action, i.e. both store 5 different packets? What happens is 2 switches that use that buffering action (in two separate flows) add the packets to the same buffer.
From: Ben Pfaff<mailto:b...@ovn.org> Sent: Monday, July 6, 2020 18:33 To: Luca Mancini<mailto:luca.manc...@outlook.com> Cc: ovs-discuss@openvswitch.org<mailto:ovs-discuss@openvswitch.org> Subject: Re: [ovs-discuss] different flow actions overlap On Mon, Jul 06, 2020 at 11:08:16AM +0000, Luca Mancini wrote: > Hello, > > I have two different flows on the same switch: > > ovs-ofctl add-flow s1 > in_port=1,dl_type=2048,nw_proto=17,nw_dst=10.0.0.4,action=buffer:3 > ovs-ofctl add-flow s1 > in_port=1,dl_type=2048,nw_proto=17,nw_dst=10.0.0.2,action=buffer:2 > > these flows are supposed to buffer packets meant for the destination > specified by nw_dst, and send the whole buffer as a new packet through the > port specified (3 or 2) . My problem is that the packets that hit the > different flows end up in the same buffer, shouldn’t hitting a different flow > create a new instance of that action? > > If it helps diagnose the issue, the buffer action is implemented in > ofproto-dpif-xlate.c, so only works in userspace. This seems like an odd question. "buffer" is an action that you invented and implemented, I think, so it can only do what you made it do. If it's not doing what you want, then maybe your code has a bug? I don't know what an "instance" of an action is.
_______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
