colucci-web.it

Yes, the problem is indeed solved with 1.00.72. Thanks a lot!

No worries

Nevermind, the situation is the same as before. I only tested over cellular network this time. Since my smartphone is set up for 464-XLAT there, that will have caused the weird situation. Over wifi it is the same as before. I can only reach IPv6 destinations with the routes and addresses shown in th...

Could it be that something has been adjusted with the latest version (1.00.71)? Now IPv4 only domains work, but directly entering IPv4s fails (e.g. https://1.1.1.1/) https://test-ipv6.com says NAT64 detected? If I configure the official Wireguard app with only an IPv6 ULA and a corresponding route (...

I didn't expect it to be implemented so quickly.

I tested it and it seems to work exactly the way I wanted it to.

Thanks a lot! This saves me a lot of work!

Thank you, I would appreciate that very much!

Hi, if i create an WireGuard Profile with only an IPv6 Address (empty IPv4 Address) i lose the ability to access IPv4 Servers. A possible workaround is to enter a random IPv4 (not configured as a peer, ...) For example 10.0.0.1/32 After that i can connect to IPv4 only Servers again. I don't think th...

Hi, I would find it really helpful if I could enter more than one IP per WireGuard profile. For example, I would like to specify a global IPv6 and one, or sometimes more, ULAs. Sure, I could create more complex routing and firewall rules, but if I don't have to, I'd really like to avoid it. The offi...