Hi Bernd,
this sounds like an interesting idea to me, and something that could be
proven useful.
One concern is that in the trip from the controller to switch A, switch B
and back to the controller, you have the propagation delay of the control
channels, the propagation delay between A<->B, but al
Hi Cayle,
The below part of the NOX code should take care of features reply messages
during the handshake. If you don't get the warning message, the reply was not
unexpected.
http://noxrepo.org/cgi-bin/gitweb.cgi?p=nox;a=blob;f=src/builtin/nox.cc;hb=HEAD#l1116
It is usual that the initial hello
I can't speak as to the particulars of the reference switch (you might try one
of the OpenFlow mailing lists).
However, the spec does state that part of the handshake sequence is that the
controller sends a features request when a connection is established. I don't
see this in your sequences o
Hi,
I am currently working on a component that needs a lot of statistical
information about the current network state.
In fact, I need the packet lLoss rate and the delay of single links
between OpenFlow-switches.
The PLR can be computed quite easily from the statistics that the switch
gives me
Are OpenFlow controllers expected to process unsolicited feature-reply messages?
I am running the following setup:
controller - ofprotocol - ofdatapath
Using wireshark I see the following sequence of messages:
#1 ofprotocol -> ofdatapath : hello
#2 ofprotocol -> controller : hello
#3 of
Hi there.
I am wondering if it is possible in the python API to find out
whether a packet matches any rule from the set of rules (even better
taking priorities into the consideration). I know it should be somehow
possible in the C++ as there is Classifier class and this mechanism is
internally use
