If it ended up seeming to work, I think the chances are good that it's fine.
But I'm interested in whatever the problem may have been if you care to help me
understand it a bit more.
Nothing stuck out at me after a quick glance at your attachments, and those
warnings are generally going to
From the log, it looks like the controller (FlowVisor?) is doing some weird
stuff, and I don't know what's up with that. As KK suggested, you might want
to look at a trace.
BUT, this shouldn't crash NOX, and I do think it points out a bug:
In src/builtin/nox.cc, the line immediately following
Thanks, I will try that.
I am in the process of getting wireshark up and running to look at a
tcpdump, if I get more info I will forward them to you.
--niky
James Murphy McCauley wrote:
From the log, it looks like the controller (FlowVisor?) is doing some weird
stuff, and I don't know
The usual cause for this is that you're out of memory. Any possibility that's
the case here? Also explains why sometimes it succeeds and sometimes it fails
without you changing anything obvious.
-- Murphy
On Oct 14, 2010, at 12:39 AM, Niky Riga wrote:
Hi,
Attached is the output of a
Hi,
I am using nox zaku and FV 0.4 beta4. I have been having problems with
a module that pokes periodically the switches for statistics.
In an effort to debug this, I made a clean installation of nox (zaku
release)
and run the default monitoring module of nox. And the problems persisted.
Hi Sachin
If you are looking to just create entries without writing any NOX
code, then you need to use dpctl. Please do following:
$ git clone git://openflowswitch.org/openflow.git
$ cd openflow
$ git checkout -b of1.0 origin/release/1.0.0
$ ./boot.sh; ./configure; make
$ cd utilities
$ ./dpctl
Nicky: are you by chance using envi as well?
There was a problem with table stats and envi, because envi was
packing its own packets and was not updated properly for openflow 1.0.
The result was that table stats messages were 2 (4? I forget) bytes
shorter than they should be.If you're using
[dropped openflow-discuss from the CC line; it's mostly overlap in
membership in any case]
So, I'm confused. Your original mail said your errors from wireshark were
for table stats messages, but you yourself are not using table stats? If
the table stats messages are not coming from you, why are
In the Monitor module crashes thead, I mentioned that I thought the
controller looked like it was doing weird stuff, but to be clear, I meant
FlowVisor and not NOX. It looks to me like FlowVisor is sending some things at
weird times (for example, sending something weird during handshaking is
