On Saturday, April 29, 2017, Jake <jake@spaz.org> wrote:
So let me get this straight- home nodes advertise their /26, which is how
the network knows how to get return traffic back to any given client?
Wouldn't giving clients ipv6 addresses result in the problems with many of
the ipv4 only protocols that were mentioned at the start of the thread?
Yes if we give them only IPv6 addresses but we want them to have both.
but if the mesh relied on IPV6 for everything, then couldn't the home nodes do
IPV4 masquerading to IPV6 and they wouldn't need their own /26 because you
could have identical IPV4 addresses on different home nodes that way?
meaning, the IPV4 address given by DHCP by a home node is only for that node to
talk to that client, and everything goes out over IPV6 from node to node and to
the exit node (where it does reverse masquerading to the internet for IPV4
traffic)
it wouldn't be masquerading, but if we mapped the entire ipv4 space to an ipv6 subnet at the home nodes and then reversed that mapping at the exit node while doing NAT then i think it would work, though i'm not sure the code is there to do this since the NAT code has to remember the original source ipv6 address while translating to its own source ipv4 address.
the obvious problem is that then ipv4 would not work on the mesh at all except when talking to the internet. not all software supports ipv6 and it would be annoying to handicap the mesh like that.
does this make sense? i know it would be a lot of work but maybe it's a good
path forward.. and it simplifies some things, for example no more need to
coordinate 100./26 IPV4 subnets between home nodes... you could use the home
node's MAC address for its IPV6 subnet.
it's not a bad idea, but i don't think it's worth the effort right now, especially since it might break in non-obvious ways and takes away features to make a slight improvement in initial configuration. We just need to get the nodes to auto-configure their ipv4 subnet on first boot, which is a work in progress. Ideally we move the ipv4 allocation server to ssb so anyone can run a copy.
-jake
_______________________________________________
mesh mailing list
mesh@lists.sudoroom.org
https://sudoroom.org/lists/listinfo/mesh