Connect, understand and support NODIF.

Before installing

• Obtain a compatible subscription link from your VPN provider. NODIF cannot create or extend the subscription.
• Use only the official NODIF download. For direct APK installation, compare the published SHA-256.
• Keep the device date/time automatic; incorrect time can break HTTPS and signed provider-profile validation.
• Remove or stop another active VPN before connecting. Two system VPN tunnels normally cannot own the default route together.

Add a subscription

1. Open NODIF and choose the subscription/add action.
2. Paste or open the provider’s subscription link. Treat it like a password—do not screenshot or send it to support.
3. Wait for the provider response and route discovery. HWID-enabled subscriptions may register the device.
4. Confirm the displayed provider and subscription status. If signed branding cannot be verified, NODIF falls back to a safe default rather than trusting arbitrary response content.
5. Refresh when your provider changes routes or account limits. Replace/remove the subscription before transferring a device to another person.

Connect and choose a route

Smart Route

Smart Route evaluates eligible provider-supplied paths. It does not search the internet for unauthorized servers or alter provider credentials. NODIF combines current handshake time, latency, jitter, packet loss, throughput, recent failures, route stability and the cost of switching. It changes route only when the expected improvement is strong enough to justify interruption.

Check routes

Runs bounded reachability and quality probes against candidate paths. It is broader than a simple ping and may briefly use network and battery. The result is a ranking estimate, not a guarantee of future performance.

Speed test

Uses real transfer measurements through candidate routes. It consumes data and can momentarily interrupt or stress the connection, so run it intentionally—not continuously. Mobile plans and limited subscriptions may be charged by the provider.

Manual server selection

Use the Servers screen when support asks for a specific provider route or when diagnosing a region. Disable Smart Route temporarily if you need the selection to remain fixed during a controlled test.

Connection quality glossary

Android setup and problems

1. Allow installation from the browser/file manager only for the verified direct APK, then turn that temporary permission off.
2. Accept Android’s VPN connection dialog. If denied, NODIF cannot create the system tunnel.
3. On heavily restricted devices, allow background operation and exclude NODIF from aggressive battery optimization if the tunnel is being killed.
4. When switching Wi‑Fi/mobile networks, allow a short recovery period before forcing repeated reconnects.
5. Captive portals must be completed before the VPN can reliably connect.

If Android shows another always-on VPN or lockdown conflict, change the system VPN setting only if the user understands the security impact and organizational policy permits it.

Windows TUN and adapter support

Common stages include “adapter did not become ready”, “could not configure the TUN interface address”, and “tunnel did not finish starting”. Use this order:

1. Disconnect other VPNs and stop software that installs competing packet filters or virtual adapters.
2. Confirm the current NODIF build and Windows version/architecture.
3. Restart NODIF; if policy allows, retry with the required administrative/service privileges.
4. Check that the expected tunnel adapter exists and is not disabled in Windows network adapters.
5. Reboot after driver or Windows networking changes.
6. Capture the stable error stage/code and UTC time from NODIF’s local diagnostic timeline—never the subscription or raw configuration.

Do not repeatedly delete arbitrary adapters or reset all Windows networking as a first step. Escalate with evidence if the bounded checks do not isolate the conflict.

HWID and device limits

HWID is controlled by the VPN provider. When enabled, NODIF sends a bounded device identifier accepted by Remnawave. Typical outcomes:

• Not supported: the provider expected a supported device identity but did not accept one.
• Maximum devices reached: remove an old device in the provider account or contact provider support.
• Subscription returns 404: a provider may intentionally hide an HWID failure; support should inspect the provider-side device state without requesting the user’s raw token.

Safe diagnostics

NODIF keeps a small rotating local diagnostic timeline for up to seven days. It contains coded tunnel stages, timings, state changes and redacted error categories. It excludes browsing activity, credentials, subscription links, raw server addresses and packet content.

Optional service-improvement telemetry

“Help improve NODIF” is off by default. Declining does not disable the VPN. After opt-in, NODIF may send typed connection stages, bounded quality measurements, route categories, app/OS version, and stable error categories. The source IP may be used momentarily before VPN connection to derive coarse network context, then discarded rather than stored. Turning telemetry off clears the encrypted pending queue, revokes the random telemetry identity and requests deletion of associated raw events.