cs4026
commented
5 years ago Update:
The use of IPv6 address can be done but only if an IPv4 address is used. This leads to an issue with IPv4 collisions.
What will need to happen will be a randomly generated Ipv4 will have to be created in the range of 172.16.0.0 – 172.31.255.255. It does not seem that it will be possible to use CJDNS address' for the IPv6 address alone.
This maybe the solution we will use, but that is still undecided at this point, so I'll leave this issue open.
Issue:
Ad-hoc mode with IPv6 addresses does not work on Raspberry Pi Zero W.
Background:
Ad-hoc mode on the Raspberry Pi Zero W is a mode that allows the pi's to connect to other devices in its wifi range thus enabling it to create a mesh network.
Currently, the configuration I was able to get the Ad-hoc mode to work in relies on static IPv4 addresses. To connect to an existing network one would set their device in Ad-hoc mode and specify a static IP address.
Where the issue comes into play is when you attempt to configure the Ad-hoc in IPv6 mode. Following this configuration link, I can get a.h. to work. However when I change 'inet' to 'inet6' along with other required changes, as suggested by this (post)[https://raspberrypi.stackexchange.com/questions/63045/using-raspberry-pi-2-3-in-wireless-ad-hoc-networks-using-ipv6-addresses] the a.h. mode does not work.
Rationale:
As it currently stands we're using CJDNS as the base of our routing protocol. CJDNS uses IPv6 addresses to identify each node in the network. Being able to use the CJDNS address would make it simpler to choose a static IP for each node and prevent IP collisions when first connecting to the network.
Possible Solutions:
The solution seems to lie in the use of /etc/dhcpcd.conf and /etc/wpa/etc/wpa_supplicant/wpa_supplicant.conf as the files to configure the network instead of using /etc/network/interfaces