Skip to content

MTU detection and restoration ​

Open Network diagnostics → MTU detection. MTU is an interface's packet-size limit. This tool tests the path from one selected adapter to one IPv4 target, not bandwidth, and does not guarantee a speed improvement.

Before testing ​

Stop the HypoMux network service. Select a physical adapter with IPv4 and a target that answers ICMP. Keep the adapter configuration and network stable. VPNs, routing changes, and ICMP filtering can affect results.

MTU page before testing, with the current value
MTU page before testing, with the current valueReal HypoMux 2.7.0 Chinese interface. Only the current value was read; no test or setting change was performed. 1500 is not a universal recommendation.

Test without changing settings ​

  1. Choose the adapter and inspect Current MTU. Refresh its value if needed.
  2. Enter a target IPv4 address, not a URL or hostname. It must answer ICMP.
  3. Select Detect recommended MTU. Probing and verification can take about 50 seconds and can be cancelled.
  4. Read the recommendation. Testing does not apply it automatically.
ResultAction
Current MTU passed; no change neededKeep it. Values above the current interface MTU were not tested
A smaller value is recommendedVerify this is the path being diagnosed before applying; do not copy it to other adapters
Timeout, filtering, cancellation, or no resultCheck the target and path, then retest; failure is not evidence to reduce MTU
Expired result or changed configurationObtain a fresh result

Apply and restore ​

Apply recommendation shows the adapter and old/new values before administrator Core changes and verifies the setting. Connections may briefly drop; avoid active remote sessions, meetings, and important downloads.

The original value is saved before modification. If needed, stop the network service and choose Restore original for the same adapter. Restoration records remain available after reopening the app. Results older than five minutes or changed adapter identity, source address, or MTU require a new test.

This version modifies the selected interface's active IPv4 configuration, not IPv6 or persistent system configuration. Rebooting returns to system configuration. If applying fails, refresh the current value and preserve the error instead of repeatedly applying blindly.

How the diagnostics differ ​

  • Link health: bound-egress reachability, latency, jitter, and loss.
  • NAT type: IPv4 UDP mapping and filtering.
  • MTU: packet size on one path, not NAT type or an optimum for every website.

See network checks, NAT, and troubleshooting.

HypoMuxReleased under the AGPL-3.0 licenseFree code signing for HypoMux is provided by SignPathCertificate by SignPath Foundation.