You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I tried to import this into the Android WireGuard (v 1.0.20220516 (492)) app, it gave me an unable to import error saying that the Endpoint was unparsable. I edited the config file to instead be Endpoint = [2603:a870:810:10::a0f:6001]:56935 as I have seen using brackets with IPv6 to distinguish it from the port number before. When I imported this to the app it did not complain at all and I was able to make a connection to the server. I am not experienced enough yet to tell if this fixed the issue for IPv6 or simply hid the issue, as I do not have an IPv6 IP address when connected.
Although I cannot be confident enough in my solution to contribute it to the codebase, I thought I would post this here to let the maintainers know the issue I had and the workaround I made for.
The text was updated successfully, but these errors were encountered:
After running the install script (wonderful script by the way), it generated the IPv6 peer as (with different actual values of course):
When I tried to import this into the Android WireGuard (v 1.0.20220516 (492)) app, it gave me an unable to import error saying that the Endpoint was unparsable. I edited the config file to instead be
Endpoint = [2603:a870:810:10::a0f:6001]:56935
as I have seen using brackets with IPv6 to distinguish it from the port number before. When I imported this to the app it did not complain at all and I was able to make a connection to the server. I am not experienced enough yet to tell if this fixed the issue for IPv6 or simply hid the issue, as I do not have an IPv6 IP address when connected.Although I cannot be confident enough in my solution to contribute it to the codebase, I thought I would post this here to let the maintainers know the issue I had and the workaround I made for.
The text was updated successfully, but these errors were encountered: