Security¶
Defaults¶
CleanWRT starts the way stock OpenWrt does:
- No root password at first. The first login happens over Ethernet, and LuCI asks you to set one.
- Wi-Fi is on, WPA2-PSK, with the default key
CleanWRT#40. Change it on the first login. - Every opt-in service is disabled. Nothing listens on your network until you enable it.
- LuCI is served over HTTPS; plain HTTP only redirects to it.
See First boot for the steps.
Before you expose the router remotely
Set your root password first. Otherwise a tunnel publishes an admin interface with no password to the internet.
Why the browser says "Not secure"¶
The admin UI uses a self-signed TLS certificate, generated on your router at first boot. Every router gets a different one and no public authority signed it, so browsers warn exactly as they do on stock OpenWrt. The connection is still encrypted. Click Advanced → Proceed.
If you own a domain, you can get a trusted certificate:
apk add acme-common luci-app-acme
Then issue a Let's Encrypt certificate with a DNS challenge (it works behind CGNAT).
Changing the password and the Wi-Fi key later¶
- Root password: System → Administration, or
passwdover SSH. - Wi-Fi key: Network → Wireless, edit the interface, Wireless Security.
No re-flash is needed.
Keeping services private¶
| Service | Reach | Advice |
|---|---|---|
| File sharing (SMB) | LAN | guest access is off; create users first |
qBittorrent web UI (:8080) |
LAN | the first start prints a temporary password to the log; set your own |
Syncthing GUI (:8384) |
LAN | set a GUI user and password before pairing |
AdGuard Home (:3000 wizard) |
LAN | choose a dashboard port other than 80/443 |
miniDLNA (:8200) |
LAN only | no login; do not expose it |
Reporting a problem¶
For a security problem, please open a private report from the repository's Security tab (Report a vulnerability) if it is enabled, or open an issue that does not include exploit details and ask for a private channel.
Common questions¶
Why does my browser say the OpenWrt router connection is not secure?
LuCI uses a self-signed certificate that your router creates at first boot. The connection is still encrypted, but no public authority signed the certificate. Click Advanced → Proceed, or install a trusted certificate with ACME if you own a domain.
What are the default passwords on CleanWRT?
There is no root password at first. The first login happens over Ethernet and LuCI asks you to set one. Wi-Fi is WPA2-PSK with the default key CleanWRT#40. Change both on the first login.
How do I get a trusted HTTPS certificate on the router?
Install acme-common and luci-app-acme, then issue a Let's Encrypt certificate with a DNS challenge. That works behind CGNAT because it needs no inbound connection.
Out of the box¶
| state | who wrote it | |
|---|---|---|
| LuCI over HTTPS, HTTP redirected | on | 46-cw-uhttpd-https |
| Root password | none, until you set one | 99-aw1000-defaults leaves it unset, as stock OpenWrt does |
| Wi-Fi | on, WPA2-PSK, key CleanWRT#40 |
the same script, and only when no key is already set |
| Firewall | stock zones and defaults, firewall4 and nftables |
OpenWrt |
| Opt-in apps | off, so nothing listens | each package's own default |
| The provisioning listener | open on port 8080, LAN only, private-network filtered, directory listings off, document root holding one directory | 49-cw-awvoice-provision-port |
| The SIP listener | closed until the AWvoice page's switch starts it | the switch |
| The browser audio port | opens with the phone line, bound to the LAN interface's address; a session on it needs a single-use token and only one page may hold it | awvoice.main.web_iface |
| Package pins | rewritten on every boot so apk upgrade cannot replace patched LuCI packages |
96-cw-apk-world-pin |
| Attended-sysupgrade UI | removed from the menu; the newer-version check stays | 48-cw-strip-asu-ui |
What is listening¶
The complete list, with the defaults, is in files, ports and paths. The short version on a new router: 443 and 80 for the admin interface, 8080 for the provisioning listener, the LAN-side DNS and DHCP, and SSH on the LAN. Nothing is forwarded from the cellular side, and there is no UPnP.
When it does not work¶
| symptom | what it means |
|---|---|
| The browser warns about the certificate | it is self-signed and created on your router. Expected. See the section above |
apk upgrade says a package is held back |
that is the pin working. See updating and pinning |
| A port you did not open answers on the LAN | check which app you enabled, and remember the provisioning listener on 8080 is opened by the image itself |
| LuCI says "This account may not do that" after an upgrade | grants are snapshotted at login. Log out and back in. See the API and who may call it |
Questions people ask¶
Is the AW1000 safe with CleanWRT on a 5G connection?
It is a router behind carrier NAT with nothing forwarded in, and this image opens no inbound service beyond the LAN-side admin interface and the local provisioning listener. What makes it unsafe is the same thing that makes any router unsafe: no root password, and the default Wi-Fi key still in place.