Troubleshooting
The problems that come up most, and how to report one so it can be fixed.
Overview
Most problems with Nasnet Connect fall into two groups: something in the wizard will not let you continue, or the generated script did not do what you expected once applied. The first group is almost always a validation rule doing its job; the second usually traces back to an answer given earlier in the wizard.
Troubleshooting
A step will not complete. Every sub-step has completion conditions, and the main stepper only marks a step done when all of its sub-steps are satisfied. Look for a red validation message on the screen, because the wizard names the field or the rule that is blocking you.
An interface you need is not in the list. Interfaces are offered once. If a port was claimed by a WAN link, or by the trunk to an access point, it will not appear on the LAN step, and it will be shown as Not Available with a note about what is using it. Change the earlier assignment to free it.
“Subnet Conflicts Detected”. Two networks were given overlapping ranges on the Network Subnets screen. The banner names the conflict. See Network Subnets.
“Certificate required.” You enabled SSTP, OpenVPN or IKEv2 as a VPN server. Those need an SSL certificate, so configure one under Useful Services.
“No Common Wireless Bands Available.” The two routers you selected for a wireless trunk do not support the same band. Use a wired trunk, or change one of the models.
The wireless trunk option is greyed out. One of your selected routers has no Wi-Fi. The warning box lists which.
You cannot reach the router after applying the script. If you changed service ports on the Services step, you must use the new ports. If you cannot get in at all, restore the backup you took, or factory-reset the router. See Applying the config to your router.
A game is not reachable. The port data on the Game screen comes from portforward.com and is provided without verification. Check the ports against the game’s own documentation.
Firmware updates. The project’s guidance: check for updates monthly and apply stable releases; always back up before updating, and test in a non-production environment first.
Getting help
Report problems either on GitHub Issues or in the Telegram group. When you report one, include:
- A description of the problem and the steps to reproduce it.
- What you expected to happen.
- Screenshots, if relevant.
- Your environment, meaning operating system and browser.
- The router configuration file, with sensitive data removed.
- The state history log from the Debug Tools panel, with sensitive data removed.
Strip passwords, IP addresses and personal data before you attach anything.