I may have found a bug with the new Error_event class you added
recently. I notice that when I set the xid of a flow mod, the xid in an
error event is different. Perhaps its not converted back from network
format? I'm not sure where that code is, but it is being converted to
network format on
This isn't just with the Error_event event -- it just behaves the same
as all the other Python events that currently keep the xid information,
and also the same as the C++ API which does not byte-swap header fields.
I agree it's probably not the most *desirable* behavior, but it is
*consistent*
Hi,
I tried running with --with-python=no and the result of that runs (and
connects to the switch). But that nox_core piece contains no application:
linux-ojon:/home/openflow/nox/nox-no-python/build # src/nox_core -v -i
ptcp:6364 packetdump
1|nox|INFO:Starting nox_core
Ah. Try running nox from its directory. cd src ; ./nox_core -i ptcp:6634 -v
-- Murphy
On Dec 17, 2010, at 7:03 PM, Stephen Wong wrote:
Hi,
I tried running with --with-python=no and the result of that runs (and
connects to the switch). But that nox_core piece contains no application:
