Re: [nox-dev] Openflow Error

2008-11-24 Thread Justin Pettit
My guess is that your controller is running v0.8.2, but your switch is running the version from noxrepo.org (v0.9.0~b1). You can check this by running both the switch and controller with the "--version" flag. If they are running v0.8.2, you should see something like: [EMAIL PROTEC

Re: [nox-dev] Signals (SIGHUP) sent to applications?

2008-11-24 Thread Teemu Koponen
On Nov 25, 2008, at 24:16 , Glen Gibb wrote: Actually, this specific problem doesn't have a cure in our local branch, but one can work around it using the reactor.callFromThread call which executes a function within the reactor's thread. The example below worked just fine on our local bran

Re: [nox-dev] Signals (SIGHUP) sent to applications?

2008-11-24 Thread Glen Gibb
Actually, this specific problem doesn't have a cure in our local branch, but one can work around it using the reactor.callFromThread call which executes a function within the reactor's thread. The example below worked just fine on our local branch and it *should* work with the noxrepo.org ve

Re: [nox-dev] Signals (SIGHUP) sent to applications?

2008-11-24 Thread Ben Pfaff
Martin Casado <[EMAIL PROTECTED]> writes: > You could always register a handler in C++ if you don't mind a > temporary hack you can just add it to src/nox_main.cc There is no need for a temporary hack, from C++. Just use Signal_group, defined in src/include/threads/signals.hh. But nox.cc

[nox-dev] Openflow Error

2008-11-24 Thread Adil Razzaq
Hi I was trying to connect a "user space openflow switch" with the "openflow controller(sample controller provided with the openflow switch)" running on two separate machines on Debian Linux. But i was getting the following error message on the controller Received openflow version 91 != expect