As Murphy said, that is due to an architectural change in NOX. OpenFlow support is no more built into the core of NOX. Instead a component (OpenFlow Manager) is in charge of handling OpenFlow connections. Without any component passed as an argument to NOX, it is only left with the built-in connection manager listening to and accepting connections without a handler to handle them.
Cheers, Amin On Thu, Jul 5, 2012 at 9:59 PM, Murphy McCauley <[email protected]> wrote: > Yes, this is due to an architectural change in the new NOX. > > I don't see how it makes much of a difference -- running NOX without any > components that work with OpenFlow isn't likely to be much use whether it > handles handshaking or not. If there's a usecase, one could create a "dummy" > component... > > -- Murphy > > On Jul 5, 2012, at 6:54 PM, YIMIN CHEN wrote: > >> Hi Murphy, >> >> Thank you for pointing that out! I will try that. One thought I have: >> NOX classic runs fine with no components specified, it can at least do >> handshake and echo with OVS. This is new requirement in new NOX? >> >> >> Thanks! >> Yimin >> >> On Thu, Jul 5, 2012 at 4:42 PM, Murphy McCauley >> <[email protected]> wrote: >>> On Jul 4, 2012, at 7:29 PM, YIMIN CHEN wrote: >>> >>>> Am I missing some steps >>>> in invoking nox_core? ./nox_core -v -i ptcp:6633 >>> >>> Indeed you are, and I believe that's the problem. Nothing is grabbing the >>> connection because you're not running any components that care about the >>> connection! >>> >>> Try: >>> ./nox_core -v -i ptcp: switch >>> >>> -- Murphy >
