# System requirements

> What the wizard needs from your browser, and what your router needs before the generated config will run.

Source: https://joinnasnet.com/en/guides/nasnet-connect/system-requirements/
Last updated: 2026-08-17

---

## Overview

Nasnet Connect has an unusual shape for a router tool: it never touches your
router. The wizard runs entirely in your browser and produces a `.rsc` file that
you apply yourself. So there are two sets of requirements, one for the machine
running the wizard, and a much more important one for the MikroTik that will
run the result.

Nothing is installed anywhere. If your browser can open the site and your router
is a supported model, you have everything you need.

## To run the wizard

| Requirement | Value |
| ----------- | ----- |
| Browser | Any current mainstream browser, with JavaScript enabled |
| Network | Enough connectivity to load [connect.starlink4iran.com](https://connect.starlink4iran.com/en/star/) |
| Account | None, because there is no sign-up and no login |
| Router access | Not needed by the wizard itself |

Because the wizard neither connects to your router nor stores your answers on a
server, you can fill it in from a phone on mobile data and apply the result
later from a laptop plugged into the router.

## To apply the config

| Requirement | Value |
| ----------- | ----- |
| Router | MikroTik running RouterOS v7 |
| Model | One of the 17 built-in models, or the custom-router option |
| Access | WinBox, WebFig or SSH to the router |
| Physical access | Strongly recommended, since it is how you recover if the router becomes unreachable |
| A backup | Taken before you apply anything |

The generated script is a **complete configuration, not a patch**. It rewrites
addressing, bridges, firewall rules and services in one pass. Take a backup
first:

```routeros
/system backup save dont-encrypt=yes name="backup-filename"
```

## Supported devices

The **Router Model** step ships with 17 models built in, grouped by family. The
model you pick decides which interfaces the later steps offer, so it has to
match the device in front of you.

| Family | Models |
| ------ | ------ |
| hAP Series | hAP ax3, hAP ax2, hAP ax lite, hAP ax lite LTE6, hAP ac3, hAP ac2 |
| Chateau Series | Chateau 5G R17 ax, Chateau PRO ax, Chateau LTE18 ax, Chateau LTE6 ax |
| cAP Series | cAP ax, cAP XL ac, cAP ac |
| RB Series | RB5009UPr+S+IN, L009UiGS-2HaxD-IN |
| Other | Audience, wAP ax |

If yours is not listed, the **Custom Router** option lets you describe the
interfaces yourself, and the wizard generates from that description instead. A
device running RouterOS v7 will accept the generated script whether or not its
model is built in.

| Device class | Supported | Notes |
| ------------ | --------- | ----- |
| MikroTik, RouterOS v7 | Yes | What every generated script targets. |
| MikroTik, RouterOS v6 | No | The generated syntax assumes v7. |
| A second MikroTik as an access point | Yes | Configured as a slave router in Advanced Mode. |
| Non-MikroTik routers | No | The output is RouterOS script, not portable configuration. |

## What you need to know before starting

The wizard asks for details you cannot guess, so gather them first:

- Which upstream links you have, domestic, foreign, or both.
- Which physical interface each link arrives on.
- PPPoE credentials, an LTE APN, or a Wi-Fi SSID and password, if a link needs
  them.
- Your VPN provider's config file, if the router itself should dial a VPN.
  WireGuard, OpenVPN, L2TP, PPTP, SSTP and IKEv2 are all accepted.

## Running the wizard yourself

The project is open source, so you can run it locally instead of using the
hosted site.

| Requirement | Value |
| ----------- | ----- |
| Node.js | 18.17.0 or newer |
| Package manager | pnpm (or npm) |

## Related

- [What you need](/en/guides/nasnet-connect/before-you-start/)
- [Applying the config to your router](/en/guides/nasnet-connect/applying-the-config/)
- [Architecture](/en/guides/nasnet-connect/architecture/)