Hopefully it's fixed in the repository now.
-- Murphy
On Oct 15, 2010, at 8:27 PM, Niky Riga wrote:
Hi,
Given that this bug is blocking one of the Gec9 plenary demos, I would like
to start debugging it.
Do you have an idea where should I start looking? In which file do you
believe the
Thanks, should I switch to the destiny branch, or this is fixed at the
head of the tree?
--niky
James Murphy McCauley wrote:
Hopefully it's fixed in the repository now.
-- Murphy
On Oct 15, 2010, at 8:27 PM, Niky Riga wrote:
Hi,
Given that this bug is blocking one of the Gec9 plenary
Fixed (hopefully!) in the main branch.
-- Murphy
On Oct 16, 2010, at 1:27 AM, Niky Riga wrote:
Thanks, should I switch to the destiny branch, or this is fixed at the head
of the tree?
--niky
James Murphy McCauley wrote:
Hopefully it's fixed in the repository now.
-- Murphy
On
Hi,
I am running FV 0.6 beta 5 and nox zaku
I am running a monitoring module that periodically pokes the switches
for stats, but the port stats reply (almost) never make it back to the
controller.
Replies for other type of stats (table, aggregate stats) are received.
I receive port stats
Updated and it seems to work just fine.
Thanks!
Niky
James Murphy McCauley wrote:
Fixed (hopefully!) in the main branch.
-- Murphy
On Oct 16, 2010, at 1:27 AM, Niky Riga wrote:
Thanks, should I switch to the destiny branch, or this is fixed at the head of
the tree?
--niky
James
On Fri, Oct 15, 2010 at 18:35, kk yap yap...@stanford.edu wrote:
rant
Actually in this case, Chui-Hui will not be able to anything if we
have went the tarball way. We are essentially not very customized to
CentOS. Tarballs are also particularly hard to update.
/rant
There doesn't have to
FYI, this problem was tracked down to a config problem, not a flowvisor or
nox bug ;-)
- Rob
.
On Sat, Oct 16, 2010 at 1:51 AM, Niky Riga nr...@bbn.com wrote:
Hi KK,
Attached are nox's log files.
* pathlet.out : the log file when I run the pathlet controller on the slice
* pyswitch.out :
Hi,
I was following the instruction for implementing the openflow network, and
when I came to the step setting up the controller, problem came when I try
to run it.
I did the make step and it ran well. But then something weird happened:
debian:/nox/build/src# ./nox_core -i ptcp:6633 routing
Nox
Can you post the output from configure and/or make?
On Oct 16, 2010 6:26 PM, Yu Yang, Calvin ee_...@stu.ust.hk wrote:
Hi,
I was following the instruction for implementing the openflow network, and
when I came to the step setting up the controller, problem came when I
try
to run it.
I did the
On Sat, Oct 16, 2010 at 18:25, Yu Yang, Calvin ee_...@stu.ust.hk wrote:
I followed exactly the instruction on the web:
http://www.openflowswitch.org/foswiki/bin/view/OpenFlow/Deployment/HOWTO/LabSetup#4_Controller_Setup
I suspect the problem is that those instructions tell you to just invoke
On Sat, Oct 16, 2010 at 21:03, Nicholas Bastin nbas...@stanford.edu wrote:
On Sat, Oct 16, 2010 at 18:25, Yu Yang, Calvin ee_...@stu.ust.hk wrote:
I followed exactly the instruction on the web:
I got the configure output off-list, and as expected, Python is disabled (and
therefore discovery). In this case, it's because Twisted isn't available,
which I have seen cause confusion before. When configuring with Python *not
disabled*, we should probably make that actually stop configure
On Sat, Oct 16, 2010 at 21:42, James Murphy McCauley jam...@nau.eduwrote:
I got the configure output off-list, and as expected, Python is disabled
(and therefore discovery). In this case, it's because Twisted isn't
available, which I have seen cause confusion before. When configuring with
13 matches
Mail list logo
