Re: [ovs-discuss] actions=in_port behavior
On Mon, Dec 10, 2018 at 07:20:03PM +, Sachin Sharma wrote: > Hi Flavio, > > Thanks for your reply! > The packet counter in the flow-stats (using dump-flows) is increasing very > rapidly. > I have just sent 1 packet. If I dump traffic through tcpdump, there are > lots of packets appearing. I think that the same packet is looping back. Oh, sounds like you have a network loop. Can't help more without knowing all the relevant connection details. fbl > > Kind Regards, > Sachin. > > On Mon, Dec 10, 2018 at 7:01 PM Flavio Leitner wrote: > > > On Fri, Dec 07, 2018 at 12:24:02PM +, Sachin Sharma wrote: > > > Hi all, > > > I have created a setup of two nodes : VMa-VMb. I ran ovs in VMb and > > > added the following flow entry in vmb: ovs-ofctl add-flow vmb in_port=1, > > > actions=in_port. > > > I now sent a ping message from VMa towards VMb. As I have a flow entry > > at > > > VMb with actions= in_port, I expect that the same packet should be > > received > > > by VMa. However, this is not happening. > > > > > > Currently, packets are looping back at VMb without even going to VMa > > > (similar to hair pin). Is this the correct behavior of the above flow > > > entry? or should VMa receive the packet which it has sent it before to > > VMb? > > > > What do you mean by 'looping back at VMb?' > > > > actions=in_port is a special output syntax where you tell OVS that it > > should send the packet on the ingress port. > > > > Check the flow stats - ovs-ofctl dump-flows ovsbr0 > > and see if the rule is being used while you run the test. > > > > -- > > Flavio > > > > -- Flavio ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] actions=in_port behavior
Hi Flavio, Thanks for your reply! The packet counter in the flow-stats (using dump-flows) is increasing very rapidly. I have just sent 1 packet. If I dump traffic through tcpdump, there are lots of packets appearing. I think that the same packet is looping back. Kind Regards, Sachin. On Mon, Dec 10, 2018 at 7:01 PM Flavio Leitner wrote: > On Fri, Dec 07, 2018 at 12:24:02PM +, Sachin Sharma wrote: > > Hi all, > > I have created a setup of two nodes : VMa-VMb. I ran ovs in VMb and > > added the following flow entry in vmb: ovs-ofctl add-flow vmb in_port=1, > > actions=in_port. > > I now sent a ping message from VMa towards VMb. As I have a flow entry > at > > VMb with actions= in_port, I expect that the same packet should be > received > > by VMa. However, this is not happening. > > > > Currently, packets are looping back at VMb without even going to VMa > > (similar to hair pin). Is this the correct behavior of the above flow > > entry? or should VMa receive the packet which it has sent it before to > VMb? > > What do you mean by 'looping back at VMb?' > > actions=in_port is a special output syntax where you tell OVS that it > should send the packet on the ingress port. > > Check the flow stats - ovs-ofctl dump-flows ovsbr0 > and see if the rule is being used while you run the test. > > -- > Flavio > > ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] actions=in_port behavior
On Fri, Dec 07, 2018 at 12:24:02PM +, Sachin Sharma wrote: > Hi all, > I have created a setup of two nodes : VMa-VMb. I ran ovs in VMb and > added the following flow entry in vmb: ovs-ofctl add-flow vmb in_port=1, > actions=in_port. > I now sent a ping message from VMa towards VMb. As I have a flow entry at > VMb with actions= in_port, I expect that the same packet should be received > by VMa. However, this is not happening. > > Currently, packets are looping back at VMb without even going to VMa > (similar to hair pin). Is this the correct behavior of the above flow > entry? or should VMa receive the packet which it has sent it before to VMb? What do you mean by 'looping back at VMb?' actions=in_port is a special output syntax where you tell OVS that it should send the packet on the ingress port. Check the flow stats - ovs-ofctl dump-flows ovsbr0 and see if the rule is being used while you run the test. -- Flavio ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
