On Monday 07 April 2008, Richard Andrews wrote:
> >From my running notes on n2n.
>
> Definite issues
> - password on edge command line is a security flaw.
yes... in fact I would move everything to a config file, so you just
have to type ./edge -f <file>. A daemonize option should be good too.
Also, configurable hello/registration timers would be good.
> - only /24 n2n networks supported.
I was thinking about the current algorithm, and perhaps it could be
improved to reduce the bandwith needed. If my understand is correct,
everytime a new edge register at the supernode, the
supernode "broadcast" the new edge to every other edge. Each edge then
tries to register with the new node (in fact, every edge tries to
register with every other edge, am I right?). So in the end you get a
fully meshed network, wich is good, but not desirable, as you spend
bandwith registering/acking. Imagine what should happen in a bigger
network!
Is it possible to trigger the registration between two nodes only when
they want to talk with each other?
--
Christian Lyra
POP-PR - RNP
http://lyra.soueu.com.br
I will make sure I have a clear understanding of who is responsible for
what in my organization. For example, if my general screws up I will
not draw my weapon, point it at him, say "And here is the price for
failure," then suddenly turn and kill some random underling.
The Top Things I'd Do
If I Ever Became an Evil Overlord
_______________________________________________
Ntop-dev mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop-dev