Hi,
Murphy and Andrea are right. The structure is designed to store a
tree, thanks to my need for a "multicast" tree in OpenFlow. So, it is
the output and reference to the next switch and the corresponding
input port at the next switch.
Regards
KK
On 6 October 2011 07:42, andrea simeoni wrote
Hi Murphy,
I think it should be the outport to the next hop too. I run some code that
prints the value stored in such variable for each hop on a route, and I get
always a 0 value; that maybe means that the variable is never initialized.
Maybe it is a bug? I don't know
2011/10/6 Murphy McCauley
.. do you mean uint16_t?
KK is the one to ask, but I believe this is the port number -- I believe the
pair is:
(port-number, next-hop-out-that-port)
-- Murphy
On Oct 6, 2011, at 5:28 AM, andrea simeoni wrote:
> Hi guys,
>
> I'm using the "hop" struct defined in the file "network-graph.hh". I
Guess: the hash code from the .cc file?
http://noxrepo.org/cgi-bin/gitweb.cgi?p=nox;a=blob;f=src/lib/network_graph.cc;h=356a7f7dff66f5658a8cd7c7456dc7cceb0deac1;hb=zaku
Regards,
Zoltan.
From: nox-dev-boun...@noxrepo.org [mailto:nox-dev-boun...@noxrepo.org] On
B
Hi guys,
I'm using the "hop" struct defined in the file "network-graph.hh". I was
able to navigate the structure, and I've well understood its recursive
nature.
But I have a question: for what stands the uint64_t field in the
std::list > next_hops ?
Thank you
--
Andrea Simeoni
