NetPilot 1.2.2

NetPilot 1.2.2

The tunnel works but crawls — fixed. Plus the "Stop Service" button no longer fails silently.

Fixed — the tunnel was fragmenting every packet (Android)

The tunnel interface was created with MTU 4096. Nothing on a real network carries that:
the phone wrote packets up to 4 KB into the tunnel, they were IP-fragmented on the first hop,
and throughput collapsed into fragment reassembly. From the user's side it looked like "the
sharing works but the speed is bad".

The MTU is now 1400 — what WireGuard and the other mainstream Android tunnels use,
because it survives Wi-Fi, cellular, and a second encapsulation (a VPN inside the tunnel)
without fragmenting.

This is the single change most likely to be felt immediately. If the tunnel still feels slow
after this, the next things to look at are the relay's copy buffer and TCP_NODELAY on the
proxy's client socket.

Changed — "Stop Service" explains itself (Windows)

A failed Start used to be swallowed: the page simply sat at "stopped" with no reason, which
looks exactly like a dead button. Now:

• a bind that fails because the port is momentarily still held is retried (8 × 250 ms);
• and if it still cannot start, the reason is shown instead of nothing.

Note: on this machine the port is released instantly, so the original complaint could not be
reproduced here — the visibility fix stands on its own, but the underlying cause on the
reported machines is not yet confirmed. A screenshot of what the button does on one of those
machines would settle it.

Assets

File	What it is
NetPilot-Windows-1.2.2-Setup.exe	Installer, self-contained. Run as administrator.
NetPilot-1.2.2-release.apk	Android release build, versionCode 4, minSdk 26, universal APK.
NetPilot-Windows-1.2.2.exe	The desktop exe alone, for machines with the .NET 8 runtime.

Verification

62 Windows tests (4 new, driving the same Start/Stop calls the button makes), 92 Android unit
tests, lint.

Licence: MIT.