First, a note that this is probably better suited for the pox-dev mailing list. 
(I've copied it; you might want to join it if you haven't already.)

On Apr 14, 2013, at 9:46 AM, Sunayana Iyer wrote:

> Hi all,
> 
> i am running pox in one terminal with this command $ ./pox.py 
> forwarding.l2_multi messenger.messenger gui_backend.monitoring
> 
> in another one i m running pox gui $ sudo python pox-gui.py -m 127.0.0.1
> 
> and in third i am running mininet pointing to pox,
> 
> my problem is that i m not seeing any topology nor any other information in 
> pox gui and there is repeated message in pox like this:
> 
> DEBUG:openflow.discovery:Dropping LLDP packet 412
> ERROR:openflow.of_01:[Con 1/4] OpenFlow Error:
> [Con 1/4] Error: header: 
> [Con 1/4] Error:   version: 1
> [Con 1/4] Error:   type:    1 (OFPT_ERROR)
> [Con 1/4] Error:   length:  28
> [Con 1/4] Error:   xid:     1221
> [Con 1/4] Error: type: OFPET_BAD_REQUEST (1)
> [Con 1/4] Error: code: OFPBRC_BUFFER_EMPTY (7)
> 
> Can anyone help me on this??

Kyriakos is by far the most familiar with this GUI, but I don't think he's 
really supporting it anymore.

Which branch/fork of POX are you using?  That GUI isn't included in recent 
versions, so I am guessing you're using the old master branch.  You might try 
switching to Kyriakos' POX fork, which has the most recently worked on version 
of this GUI.  You should be able to find it by looking at the list of fork from 
the main POX repository.

If you want to try to track down that specific error message... it looks like 
it's from trying to send (via packet_out or flow_mod) a buffer which has 
already been sent or has been thrown away.  You could snoop the control traffic 
with the OpenFlow WireShark dissector.  This could well be a bug in l2_multi, 
which may have been fixed since it looks like you're using old code.  Maybe try 
running l2_learning and see if things are any better?

Another option would be looking at POXDesk.  It's not officially supported and 
is very basic, but was probably worked on more recently than what you're using, 
and probably runs on a more recent version of POX.

-- Murphy

Reply via email to