Dear Murphy!
I have enabled DEBUG mode by the following command:./pox.py log.level --DEBUG
web messenger messenger.log_service messenger.ajax_transport
openflow.of_service poxdesk poxdesk.terminal
In POX log, I can see the following DEBUG messages from
web.webcore.server:DEBUG:web.webcore.server:/:"GET /favicon.gif HTTP/1.1" 200
-DEBUG:web.webcore.server:/_jrpcmsg/:"POST /_jrpcmsg/?nocache=1392016877693
HTTP/1.1" 200 -DEBUG:web.webcore.server:/_jrpcmsg/:"POST
/_jrpcmsg/?nocache=1392016878239 HTTP/1.1" 200
-DEBUG:web.webcore.server:/_jrpcmsg/:"POST /_jrpcmsg/?nocache=1392016878251
HTTP/1.1" 200 -DEBUG:web.webcore.server:/_jrpcmsg/:"POST
/_jrpcmsg/?nocache=1392016878258 HTTP/1.1" 200 -
I dont know if these are errors or just messages.
I then also included "openflow.discovery" component in the command. And then
ran the following topology from inside the POXDesk Terminal window:
sudo mn --controller remote --mac --topo linear,3
But the TopoViewer is still blank and not displaying anything. However the
other windows like TableViewer etc. are working fine.
Subject: Re: POXDesk Terminal is Unable to Connect
From: murphy.mccau...@gmail.com
Date: Fri, 7 Feb 2014 12:22:25 -0800
CC: pox-dev@lists.noxrepo.org
To: u_r_wel...@hotmail.com
I expect that problem is that tinytopo requires the openflow.discovery module
(and I would imagine there are errors in the POX log which would indicate
this?).
-- Murphy
On Feb 7, 2014, at 2:44 AM, Rizwan Jamil <u_r_wel...@hotmail.com> wrote:Dear
Murphy!
The POXDesk Terminal problem is solved by appending "poxdesk.terminal" at the
end of the command, as per your suggestion. Thanks alot for that.
But another problem is that the TopoViewer window in POXDesk was and is still
blank and does not show the diagram of topology created whether in POXDesk
terminal window or in the normal VM terminal window. I have tried by appending
"poxdesk.tinytopo" at the end of the mentioned command (just like appending
"poxdesk.terminal"), but no success.
Any suggestion(s)?
Subject: Re: POXDesk Terminal is Unable to Connect
From: murphy.mccau...@gmail.com
Date: Thu, 6 Feb 2014 23:08:20 -0800
CC: pox-dev@lists.noxrepo.org
To: u_r_wel...@hotmail.com
It wouldn't. I am not even sure how you're viewing POXDesk at all given the
commandline you're using. You probably need to run at least the web,
messenger, messenger.ajax_transport and poxdesk components for poxdesk.terminal
to work.
In short: start with the suggested commandline and *add*
poxdesk.terminal:./pox.py samples.pretty_log web messenger
messenger.log_service messenger.ajax_transport openflow.of_service poxdesk
poxdesk.terminal
-- Murphy
On Feb 6, 2014, at 10:35 PM, Rizwan Jamil <u_r_wel...@hotmail.com> wrote:Dears!
I am using Mininet VM installed on my VMWare Workstation on Windows XP SP3. In
my Mininet VM, I have successfully followed all instructions mentioned
on:https://github.com/MurphyMc/poxdesk/wiki/Getting-Started
But when opened, the Terminal window in POXDesk GUI displays the following
message:Connecting to channel terminalbA5ZZVC...........
Moreover, when I run the command "./pox.py poxdesk.terminal" from the Mininet
terminal, the following is displayed:POX 0.1.0 (betta) / Copyright 2011-2013
James McCauley, et al.Traceback (most recent call last): File
"/home/mininet/pox/pox/boot.py", line 459, in boot if _do_launch(argv):
File "/home/mininet/pox/pox/boot.py", line 199, in _do_launch f(**params)
File "/home/mininet/pox/ext/poxdesk/terminal.py", line 122, in launch
core.registerNew(TerminalMaster) File "/home/mininet/pox/pox/core.py", line
356, in registerNew obj = __componentClass(*args, **kw) File
"/home/mininet/pox/ext/poxdesk/terminal.py", line 44, in __init__
core.MessengerNexus.default_bot.add_bot(TerminalBot) File
"/home/mininet/pox/pox/core.py", line 530, in __getattr__ raise
AttributeError("'%s' not registered" % (name,))AttributeError: 'MessengerNexus'
not registered
Please Help!
