VPN Fusion can route selected clients through a supported VPN profile; it is not the same as running an inbound VPN server.
Before you change anything
This is a diagnostic entry point. The source supports the general check, not a confirmed root cause for your device.
What to check first
What exact model, device role, indicator position and firmware are involved?
Record the exact model, hardware revision, firmware and recent change before adjusting settings. If you cannot answer the question, keep the cause open.
Narrow the likely path
| Observation | Next check |
|---|---|
| Light or app says offline | Use the correct model and role chart; color alone is inconclusive. |
| Node will not join | Check the specific mesh family and parent/child setup sequence. |
| Feature menu differs | Compare the current firmware and hardware revision with the vendor guide. |
Decision after the first test
Confirm the ASUS model, firmware and protocol, then check which devices are assigned to the profile before treating a partial VPN route as failure.
Use a documented next step
Verify before escalating
After each change, repeat the exact failed task. If the result is unchanged, restore the previous setting and use the official support link for your exact hardware revision. Don’t assume a menu or capability from a related model.
Official sources
- ASUS WireGuard client via VPN Fusion (full_text; checked 2026-11-01)
Check your exact US model, hardware revision, and firmware on the linked support page before changing settings.