wireguard-ui icon indicating copy to clipboard operation
wireguard-ui copied to clipboard

ipv6 support for client configuration

Open campbellbs opened this issue 2 years ago • 6 comments

IPv6 for client configuration is now possible with or without specific port. Different configurations were tested manually, e.g.:

tests

campbellbs avatar Sep 17 '22 01:09 campbellbs

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] avatar Nov 22 '22 18:11 stale[bot]

Any reason this can't be merged? Thanks

foux avatar Jan 23 '23 12:01 foux

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] avatar Mar 24 '23 22:03 stale[bot]

I don't see the advantage to use an obscure library to verify an IPv6 address when one can simply use the net library and parse an address that way. It's more resilient and more widely used. Plus the various cases of the form "host:port", "host%zone:port", "[host]:port" or "[host%zone]:port" into host or host%zone and port don't all seem covered here.

There are also potentially cases when the IPv6::ffff:IPv4 forms may also arise.

systemcrash avatar Mar 25 '23 17:03 systemcrash

@ngoduykhanh: What do you think?

Neustradamus avatar Oct 09 '23 17:10 Neustradamus

Just test ipv6/4 using an OS library. There are a bunch of weird pathological cases accounted for there that naive test cases miss.

I

systemcrash avatar Oct 09 '23 20:10 systemcrash