IPV6 Link-local Support

[daylight-hub]

Hello! I found your project and find the concept to be fascinating and just what I am looking for. However, I am trying to use it with a program called Reticulum that runs on a raspberry pi which is connected to a device called an Rnode, which is for lora mesh networks. I want to access Reticulum on the raspberry pi using an Android phone app called Sideband, which also uses reticulum. The only requirement is that network peer discovery support IPV6.

Is this supported with your router script or if not, would you consider adding it?

Here is some more information about this fascinating mesh networking project:

https://github.com/markqvist/Reticulum
https://reticulum.network/manual/interfaces.html#interfaces-tcpc

The AutoInterface enables communication with other discoverable Reticulum nodes over any kind of local Ethernet or WiFi-based medium. Even though it uses IPv6 for peer discovery, and UDP for packet transport, it does not need any functional IP infrastructure like routers or DHCP servers, on your physical network.

As long as there is at least some sort of switching medium present between peers (a wired switch, a hub, a WiFi access point or similar, or simply two devices connected directly by Ethernet cable), it will work without any configuration, setup or intermediary devices.

For AutoInterface peer discovery to work, it’s also required that link-local IPv6 support is available on your system, which it should be by default in all current operating systems, both desktop and mobile.

[RaspberryConnect]

Hi

That's sounds interesting setup. My requirements for my script is quite simple so I have not used IPv6.

This Repository is for my Older script AutoHotspot, as I'm sure you are aware as I also see you have left me a comment on my website for my newer script, but I will answer here.
So referring to the Newer AccessPopup script (which I will be adding to Github soonish.)
https://www.raspberryconnect.com/projects/65-raspberrypi-hotspot-accesspoints/203-automated-switching-accesspoint-wifi-network

As that uses Network Manager IPv6 can be added to the AccessPopup Hotspot by enabling IPv6 in the Network Manager GUI.
Or using nmcli;
sudo nmcli con mod AccessPopup ipv6.method shared
nmcli con reload

If your setup works with that modification then I can look at adding it in to the setup, either by default or as an 'enable IPv6' option. Like I say I have not used IPv6 so I don't currently know any issues that may cause if any.

One thing to note is that the AccessPopup profile is only created when the Access Point is required for the first time, so use; sudo accesspopup -a
to activate it. Then sudo accesspopup can be used to go back to a local wifi network.
Now add the mod above and hopefully it will work.
If the script has any issues using the AccessPopup profile in future it will delete it and recreate it with the default values, so be aware that the IPv6 setup will be lost at that point.

Also the default Wifi device is wlan0 this can be changed in /usr/bin/accesspopup in the variables at the top.
I have an update that includes using the correct wifi device name but that is not ready for release yet.

If this is of any use let me know and I will consider including it in the next update.

[daylight-hub]

Thank you for your help! I have been testing your hotspot between two android phones running the Sideband app which uses Reticulum. I ran the 2 commands you recommended, sudo nmcli con mod AccessPopup ipv6.method shared and sudo nmcli con reload before running sudo accesspopup -a. The messages are being sent and received although it is not as fast as using my home router. It seems the messages don't go right through but are instead stored in the propagation node of the Reticulum firmware housed on the raspberry pi. Eventually they come through when the phone sync occurs. I also enabled IPV6 in Network Manager sudo nmtui(see the attached picture). I think IPv6 would be a great optional feature to include in your next release.