On Wed, Oct 02, 2013 at 11:40:47PM +0530, Shyam Goud wrote: > On 02/10/13 01:22, Ben Pfaff wrote: > >Please don't drop the list. > > > >On Tue, Oct 01, 2013 at 09:44:28PM +0530, Shyam Goud wrote: > >>'qvo5271d2db-df' port is attached to my Service VM's eth0. > >> > >>- I am able to see traffic on mirrored ovs-port 'qvo5271d2db-df' > >> > >>- But I failed to see the same traffic on my Service VM's eth0. It > >>- should be seen on corresponding attached interface right ? > >You configured qvo5271d2db-df as the output port. Why you do think > >that packets sent out qvo5271d2db-df should also be visible on eth0? > > > eth0 of the service VM is attached to qvo5271d2db-df.
Oh, you mean in the guest. I didn't understand that before. I agree that if qvo5271d2db-df on the host is tied to eth0 in the guest, then I would expect the packets to be visible on eth0 in the guest. But I'm not sure how OVS could be getting in the way there. > Also, please help with these ovs clis, > 1. to see full config details of a particular ovs-port. ovs-vsctl list port <name> ovs-vsctl list interface <name> > 2. packet rx/tx stats on a particular ovs-port For a port that is a network device like this I usually use ifconfig. _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
