22 May
2013
22 May
'13
11:54 p.m.
If anyone is feeling generous, please pledge to cjdns support for openwrt
and windows...
http://fund.meshwith.me/
--
Alcides Gutierrez
http://e64.us
23 May
23 May
12:21 a.m.
Would it be helpful to Sudo Mesh if we had one of the routers offered? I
might be willing to get one for us if it's a good idea.
On Wed, May 22, 2013 at 11:54 PM, Alcides Gutierrez <alcides888(a)gmail.com>wrote;wrote:
If anyone is feeling generous, please pledge to cjdns
support for openwrt
and windows...
http://fund.meshwith.me/
--
Alcides Gutierrez
http://e64.us
_______________________________________________
mesh mailing list
mesh(a)lists.sudoroom.org
http://lists.sudoroom.org/listinfo/mesh
10:11 a.m.
Just expanding on my brief email last night:
When using CJDNS you need to find at least one peer to access the network,
in this case, Hyperboria. So the router comes preconfigured with peers.
I plan on configuring my laptop to be a node today. If I get it done in
time, I'll bring it to the meeting tonight and we can travel to Hyperboria.
CJDNS emphasizes privacy through built-in encryption for the protocol. It
also promotes sociability and encourages trust via the peer requirement.
Currently only working on Linux and Mac OS(?). Support for Openwrt and
Windows would open this mesh protocol to a lot more people.
Please ask questions and I'll try my best to answer for find answers.
Alcides Gutierrez
http://e64.us
On May 23, 2013 12:21 AM, "Ryan Evans" <ryanlyleevans(a)gmail.com> wrote:
Would it be helpful to Sudo Mesh if we had one of the
routers offered? I
might be willing to get one for us if it's a good idea.
On Wed, May 22, 2013 at 11:54 PM, Alcides Gutierrez <alcides888(a)gmail.com>wrote;wrote:
If anyone is feeling generous, please pledge to
cjdns support for openwrt
and windows...
http://fund.meshwith.me/
--
Alcides Gutierrez
http://e64.us
_______________________________________________
mesh mailing list
mesh(a)lists.sudoroom.org
http://lists.sudoroom.org/listinfo/mesh
24 May
24 May
8:56 p.m.
On Thu, May 23, 2013 at 10:11 AM, Alcides Gutierrez <alcides888(a)gmail.com>wrote;wrote:
Just expanding on my brief email last night:
When using CJDNS you need to find at least one peer to access the network,
in this case, Hyperboria. So the router comes preconfigured with peers.
I plan on configuring my laptop to be a node today. If I get it done in
time, I'll bring it to the meeting tonight and we can travel to Hyperboria.
Does anyone know how CJDNS actually works? I read the whitepaper and there
seems to be no discussion of any of the core concerns of mesh networking
protocols. My initial reaction is that it seems like it's a bit of a naive
approach, and that the people involved didn't learn from existing projects
like BATMAN, OLSR and Babel in designing their protocol. I realize that
their goals are different from those projects, but I haven't seen any
calculations or simulations of how a large CJDNS network would function.
Perhaps CJDNS is just not being developed as a mesh protocol? It seems that
the Seattle Meshnet people feel otherwise though, and are actually using it
as a meshnet protocol.
Someone please tell me why I/we should care about CJDNS. What problem does
it solve that is related to mesh networks? Point to point encryption? Is
that it?
--
Marc
10:02 p.m.
So, from my initial understanding, cjdns nodes are obligated to stay in
touch with physically close nodes and address-close nodes.
I asked cjd to clarify a bit. "With others there is only one layer, each
node makes a decision to route to one of it's directly connected neighbors
and that is the end." Whereas cjdns can have routers and switches
(non-nodes) in between and still calculate quality links. Calculations are
done by number of hops and latency.
So, if all computers installed cjdns and became nodes, routers wouldn't
need to become nodes themselves. However if routers became nodes, non-node
clients of the router would be able to access the cjdns network via NAT66.
On Fri, May 24, 2013 at 8:56 PM, Marc Juul <marcjc(a)gmail.com> wrote:
On Thu, May 23, 2013 at 10:11 AM, Alcides Gutierrez
<alcides888(a)gmail.com>wrote;wrote:
--
Alcides Gutierrez
http://e64.us
Just expanding on my brief email last night:
When using CJDNS you need to find at least one peer to access the
network, in this case, Hyperboria. So the router comes preconfigured with
peers.
I plan on configuring my laptop to be a node today. If I get it done in
time, I'll bring it to the meeting tonight and we can travel to Hyperboria.
Does anyone know how CJDNS actually works? I read the whitepaper and there
seems to be no discussion of any of the core concerns of mesh networking
protocols. My initial reaction is that it seems like it's a bit of a naive
approach, and that the people involved didn't learn from existing projects
like BATMAN, OLSR and Babel in designing their protocol. I realize that
their goals are different from those projects, but I haven't seen any
calculations or simulations of how a large CJDNS network would function.
Perhaps CJDNS is just not being developed as a mesh protocol? It seems that
the Seattle Meshnet people feel otherwise though, and are actually using it
as a meshnet protocol.
Someone please tell me why I/we should care about CJDNS. What problem does
it solve that is related to mesh networks? Point to point encryption? Is
that it?
--
Marc
10:05 p.m.
Here's an older video interview...
http://youtu.be/zINQYkl01N8
On Fri, May 24, 2013 at 10:02 PM, Alcides Gutierrez <alcides888(a)gmail.com>wrote;wrote:
So, from my initial understanding, cjdns nodes are
obligated to stay in
touch with physically close nodes and address-close nodes.
I asked cjd to clarify a bit. "With others there is only one layer, each
node makes a decision to route to one of it's directly connected neighbors
and that is the end." Whereas cjdns can have routers and switches
(non-nodes) in between and still calculate quality links. Calculations are
done by number of hops and latency.
So, if all computers installed cjdns and became nodes, routers wouldn't
need to become nodes themselves. However if routers became nodes, non-node
clients of the router would be able to access the cjdns network via NAT66.
On Fri, May 24, 2013 at 8:56 PM, Marc Juul <marcjc(a)gmail.com> wrote:
--
Alcides Gutierrez
http://e64.us
On Thu, May 23, 2013 at 10:11 AM, Alcides
Gutierrez <alcides888(a)gmail.com
--
Alcides Gutierrez
http://e64.us
wrote:
Just expanding on my brief email last night:
When using CJDNS you need to find at least one peer to access the
network, in this case, Hyperboria. So the router comes preconfigured with
peers.
I plan on configuring my laptop to be a node today. If I get it done in
time, I'll bring it to the meeting tonight and we can travel to Hyperboria.
Does anyone know how CJDNS actually works? I read the whitepaper and
there seems to be no discussion of any of the core concerns of mesh
networking protocols. My initial reaction is that it seems like it's a bit
of a naive approach, and that the people involved didn't learn from
existing projects like BATMAN, OLSR and Babel in designing their protocol.
I realize that their goals are different from those projects, but I haven't
seen any calculations or simulations of how a large CJDNS network would
function. Perhaps CJDNS is just not being developed as a mesh protocol? It
seems that the Seattle Meshnet people feel otherwise though, and are
actually using it as a meshnet protocol.
Someone please tell me why I/we should care about CJDNS. What problem
does it solve that is related to mesh networks? Point to point encryption?
Is that it?
--
Marc
4542
days inactive
4544
days old
5 comments
3 participants
participants (3)
-
Alcides Gutierrez -
Marc Juul -
Ryan Evans