Location: Germany (NRW) Remote: Yes Willing to relocate: No Technologies: Embedded, C++ 11/14/17, QT, Yocto, Linux, Python, Networks, IPv6, willing to learn new stuff Résumé/CV:…
On Android the problem is the same. The Client only resolves the IP once. When the server gets a new ip, no connections can be made, although the client seem to be still connected.
Beware all examples in this don't cover ipv6. Should you have an ipv6 address, you are not using the vpn for most of your connections. Sadly most Wireguard howtos don't cover ipv6.
What bothers me in the Article, the official documentation and almost all guides for wireguard is that they ignore ipv6 completely. They either result in a leaking vpn or bad working one where all ipv6 connections fail.
Location: Germany (NRW) Remote: Yes Willing to relocate: No Technologies: Embedded, C++ 11/14/17, QT, Yocto, Linux, Python, Networks, IPv6, willing to learn new stuff Résumé/CV:…
On Android the problem is the same. The Client only resolves the IP once. When the server gets a new ip, no connections can be made, although the client seem to be still connected.
Beware all examples in this don't cover ipv6. Should you have an ipv6 address, you are not using the vpn for most of your connections. Sadly most Wireguard howtos don't cover ipv6.
What bothers me in the Article, the official documentation and almost all guides for wireguard is that they ignore ipv6 completely. They either result in a leaking vpn or bad working one where all ipv6 connections fail.