On Mon, May 13, 2013 at 4:06 PM, Yussi <[email protected]> wrote:
> Now, there are two concepts which we need to clarify, with some > similar aspects, namely a mesh vs. darknet. > > A mesh network connects clients by "chaining" them in order from > source to destination, a wireless mesh does that over the wireless. > > suppose you have a fairly large mesh, and you run a service (a website > say) which is only accessible to people on that mesh network, this is > a local network service, it's also in a sense a darknet, if you employ > high encryption and VPN like routing in the mesh level, it's a darknet > proper. infact that's exactly how i2p works (worked), each client > holds a few VPNs, and services were encrypted on each hop (hop pair > really). > Actually, a darknet (and specially I2P) does not work like that: http://pastebin.com/gWzFwBiw I2P, Tor, Freenet, all work as a darknet in the sense they provide strong cryptography to ensure high anonymity and censorship resistance. CJDNS, OSLR, Batman, etc, they work by defining the best paths for creating routes in a lower level. Netsukuku is somewhere in-between. Obviously I'm oversimplificating things, but my point is that Netsukuku is unique. Throwing up the old C code was a bad idea IMO, the python port never lifted up and development stalled. I don't know what happened to the original developers (Alpt, etc) but the only person that was working on was Luca. He did get busy aswell and development of the Vala port stalled. I'd like to know if Alpt is around. Hopefuly we can get a roadmap started? -- Ricardo Lanziano To iterate is human, to recurse, divine.
_______________________________________________ Netsukuku mailing list [email protected] https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/netsukuku
