Protect the addresses native applications can read
An ISP-assigned public IPv6 address can remain on a physical adapter. Even when the tunnel rejects IPv6 packets, a native application may enumerate adapters, read that address and send it through another permitted connection. godusevpn addresses both traffic routing and locally available address information within the same connection lifecycle.
Disabling IPv6 on manageable Windows, Linux and macOS adapters reduces opportunities for native applications to obtain those adapters’ public IPv6 addresses. For people who use desktop software every day, protection reaches the system information applications can actually access. The connection indicator becomes part of a deeper, practical protection process.
Five layers cover different parts of the connection
With IPv6 disabled by default, DNS uses an ipv4_only strategy, fake-ip assigns IPv4 addresses, and core rules reject IPv6 destinations. TUN still captures IPv6 traffic so the core can explicitly drop it, narrowing routes around the intended path. The fifth layer reaches physical adapters on supported platforms to reduce local address exposure.
Each layer handles a different problem, coordinated through the same client settings. Users do not have to assemble DNS rules, tunnel routes and adapter commands themselves. The client connects these controls from domain resolution to the system interface, while the layer-by-layer explanation makes their purpose easy to inspect.
See what your platform is actually protecting
Windows, Linux and macOS can apply adapter-level controls when system permissions allow. Android does not provide equivalent adapter-management access and uses the first four layers. godusevpn makes these differences visible, helping users understand which protections their device can apply instead of relying on an ambiguous status icon.
Unmanageable interfaces and bridged virtual machines have their own limits. When checks find a protection gap, the client reports the state and warning, then continues repair where supported. Seeing both the mechanism and its actual state gives users a clearer basis for everyday use and troubleshooting.
Protect while connected, restore the previous state on disconnect
Adapter protection also needs to respect existing system settings. godusevpn applies the relevant controls during the connection and attempts to restore the recorded previous state when you deliberately disconnect. An independent network recovery entry remains available when, for example, the background service cannot start.
Bringing these operations into the connection lifecycle is a practical advantage: less manual setup when starting, visible protection when investigating an issue, and a clear recovery route when leaving. System-level privacy protection should make everyday operation easier to understand as well as more capable.