Thanks Murphy, I tried applying the changes from
"73fc9071b9d4f77b8314bf44fe4e5c6bccb480df" in destiny branch to the zaku branch
and now I can 'configure' successfully.
But I am still not able to compile NOX. When I 'make' I got this error message:
/bin/bash ../libtool --tag=CXX --mode=link g+
Hi,
Try changing src/include/openflow-default.hh. Hope this is what you
are looking for.
Regards
KK
On 20 October 2011 13:42, Candy Floss wrote:
> Thanks for the reply. I'm not running discovery module. The idle time out is
> set for 5 secs and the hard timeout is set to 0(i.e. permanent). The
Thanks for the reply. I'm not running discovery module. The idle time out is
set for 5 secs and the hard timeout is set to 0(i.e. permanent). These are
the parameters that are in the code by default. I have not changed anything.
Regards,
Candy
On Thu, Oct 20, 2011 at 1:39 PM, Kyriakos Zarifis wro
Hi,
are you running 'discovery' or any other application that has discovery as a
dependency?
If so, the packet_ins you see are most probably the control (LLDP) packets
sent by discovery to discover neighbors.
( http://noxrepo.org/noxwiki/index.php/Discovery )
the flow expiration time is set from
I have copnnected NOX and two switches. Sometimes when I connect the switch
to the NOX I see packet_in event in addition to datapath_join event. This is
happening randomly. Not able to find a pattern when this eaxctly happens but
it happens most of teh time. I'm not starting any flows but I still s
Hi,
I imagined that the steps were like you mentioned... well,
Firstly, s3 send packet_in to c0, and another moment s2 send packet_in
to s3that send to
c0...
Well, as you mentioned earlier, I need to set initial flow entries, that is,
I think that is the flow from s2 to s3
,.. one time initiate
Yes, that is possible. This is where in-band vs out-of-band control comes to
play: If the physical topology looks exactly like what you described then
control of sw1 can only been done in-band (meaning, the control packets are
using the same links as the data packets). In order for that to be possi
Hi,
Thanks for your reply.
It's possible openflow messages across several switches until achieve the
controller?
Such as host -> sw1 -> sw2 -> sw3 -> c0 or in a reverse way in linear
topology?
Consider that the host packet need to achieve a server connected to sw3 and
there are only
one controller
I think the answer to your question is something like:
In builtin/nox.cc is a loop, which uses lib/openflow.cc to read OpenFlow
messages off the wire. It then uses lib/openflow-event.cc to translate these
OpenFlow messages into NOX events, which it then dispatches.
Hope that helps.
-- Murphy
I believe I fixed this in the destiny branch some time ago. Give that a shot?
-- Murphy
On Oct 20, 2011, at 1:32 AM, Heryandi wrote:
> Hi all,
>
> I have previously compiled NOX successfully in ubuntu 10.04.
> Now, I am trying to compile NOX zaku in my ubuntu 11.10 VM, but it doesn't
> work.
Hi,
pyswitch itself is really not aware of any topology. It only stores state
that is relevant to switches separately (i.e. it stores a mapping of mac
addresses to local ports for a switch).
Now, whether a control packet (like a packet_in) will reach the controller
if it's not directly physically
Hi all,
what is the source file that implements the process waiting for OF messages
on port 6633? What is the first component generating a packet-int-event?
I need such information very much.
Thank you
--
Andrea Simeoni
___
nox-dev mailing list
nox-de
12 matches
Mail list logo
