[ovs-discuss] Information in PORT STATUS message not correct

Ben Pfaff blp at nicira.com
Mon Jul 16 05:30:56 UTC 2012


I don't know whether it's a known bug or whether there is a fix.

On Mon, Jul 16, 2012 at 01:29:46PM +0800, YIMIN CHEN wrote:
> Hi Ben,
> 
> Thank you for your clarification! Now the log shows:
> 
> Jul 16 13:15:58|00134|vconn|DBG|tcp:127.0.0.1:6633: sent (Success):
> OFPT_PORT_STATUS (xid=0x0): ADD: 3(tap0): addr:4e:96:14:cd:a7:28
>      config:     0
>      state:      0
>      current:    10MB-FD COPPER
> 
> So I guess wireshark was mis-printing.
> 
> Is this a known bug in wireshark? Should I update to a newer wireshark
> version with fix?
> 
> Thanks!
> Yimin
> 
> On Fri, Jul 13, 2012 at 10:47 AM, Ben Pfaff <blp at nicira.com> wrote:
> 
> > On Fri, Jul 13, 2012 at 10:42:22AM +0800, YIMIN CHEN wrote:
> > > I am using openvswitch 1.4.2 with NOX-classic. I used wireshark to
> > capture
> > > the message and found content not matching with ovs-dpctl output:
> > >
> > > I started 3rd VM using kvm, with mac 00:aa:bb:00:00:03. ovs-dpctl shows
> > the
> > > openflow port is 15.
> > >
> > > jason at jason-laptop:~/ymchen/openvswitch-1.4.2$  sudo ovs-dpctl show br0
> > > system at br0:
> > > lookups: hit:2330 missed:883 lost:0
> > > flows: 0
> > > port 0: br0 (internal)
> > > port 1: eth0
> > > port 14: tap0
> > > port 15: tap1
> > > port 19: tap2
> > >
> > > However the port status content shows port = 0, mac
> > addr=00:00:00_13:a6:b9,
> > > port name is V\337Etap2. I have attached wireshark screen shot.
> >
> > What appears in the OVS log, if you use -vvconn?  I don't really trust
> > wireshark.
> >



More information about the discuss mailing list