Wifi Captive Portal Using IPv6 Only

The IPv6Spot project is the result of more than two years of continuous work, and I am excited to share the progress of this project with you. Our primary focus has been on addressing challenges related to handling temporary and multiple IPv6 addresses caused by the use of SLAAC. We successfully overcame these challenges by leveraging MAC addresses. This solution has proven to be highly effective, operating seamlessly and without any issues.

This project introduces a Captive Portal that operates entirely on IPv6, completely bypassing IPv4. I am pleased to announce that we have overcome all obstacles to ensure the smooth functionality of the Captive Portal using IPv6 without relying on a DHCP server. This is a significant advantage, especially since some systems, like Android, only support SLAAC and do not provide DHCP support for IPv6.

Some might ask: "Why switch from IPv4 to IPv6?" When using a Captive Portal with IPv4, it is relatively easy to exploit devices through their MAC addresses, allowing unauthorized internet access by hijacking the credentials of an active session. However, with IPv6,This is absolutely not possible. If two devices attempt to use the same MAC address on an IPv6 network, they will encounter a "network unreachable" error due to identical link-local addresses. This is an inherent security feature that prevents the use of duplicate MAC addresses on IPv6-enabled networks. As a result, this effectively prevents unauthorized internet access by hijacking the credentials of an active session.