4.4 KiB
Install the experimental ARM release
Read RELEASE-NOTES.md for the measured results and unfinished functionality. Use a spare compatible ARM router. A first installation changes the trusted package signing key; stock Netinstall cannot install this package set.
First installation
- Download one release's Linux or Windows Netinstall archive, routeros, option, olsr, public-key.json and SHA256SUMS. Use the Wi-Fi NPK only if needed and if the complete package set fits. Keep official Netinstall/RouterOS for recovery.
- Verify downloaded files against SHA256SUMS and compare the key fingerprint with the release notes. Checksums detect corruption; the publisher's signing key defines which future packages this installation trusts.
- Connect the router's Etherboot port directly to a dedicated Ethernet adapter. Configure the adapter as 192.168.88.2/24. Enter Etherboot/Netinstall mode using the device's reset-button procedure.
- On Linux, extract the archive, then run the command below from the directory containing the NPKs. Substitute the device's Etherboot MAC address.
chmod +x netinstall-cli
sudo ./netinstall-cli -e -b --mac AA:BB:CC:DD:EE:FF --reboot \
-a 192.168.88.3 routeros-7.25.1-arm.npk option-7.25.1-arm.npk olsr-7.25.1-arm.npk
-e installs an empty configuration; it is not a default configuration. This
erases the previous configuration. Wait for successful installation and reboot.
Do not add -f to ignore insufficient space. Windows Netinstall is patched by
the same build, but its installation workflow has not been hardware-tested here.
- Connect through Winbox using MAC discovery. Configure your management IP, credentials, and appropriate management access. Empty configuration has no predefined bridge, DHCP server, or firewall. Enable the REST-capable web service on the management network (HTTPS when configured).
- Create the community VLAN/interface and assign your allocated node address. The project does not choose or allocate network addresses for you.
Configure OLSR
The initial native panel only implements service enable/disable. Download configure-device.py, or use tools/configure-device.py from this repository. Python 3 and its standard library are sufficient. Set the password without putting it into shell history:
read -rs -p 'RouterOS password: ' ROUTEROS_PASSWORD; echo
export ROUTEROS_PASSWORD
python3 configure-device.py --router https://ROUTER-MANAGEMENT-IP configure \
--interface YOUR-OLSR-VLAN --address YOUR-ALLOCATED-IP \
--accept-network 10.0.0.0/8 --enable
unset ROUTEROS_PASSWORD
Use an http URL only if your test router's management web service is HTTP.
For a lab account with an empty password, explicitly set ROUTEROS_PASSWORD=''.
The node address must already be assigned to the selected interface. Repeat
--accept-network for additional canonical IPv4 network prefixes. Default route
import is excluded. HNA advertisement configuration is not available yet.
Omit --enable to leave the service disabled after setup. Re-running configure
stops and reconfigures OLSR, so pass --enable again if you want it running.
After discovery converges, inspect IP > Routes in Winbox. Imported routes have comments OLSR or OLSR-link and are dynamic BGP routes. The local BGP bridge is an implementation detail; no BGP session is opened toward community neighbors. Use OLSR > Service (or System > Scheduler > OLSR) to enable/disable the service. Disabling should remove its routes within roughly eight seconds.
python3 configure-device.py --router https://ROUTER-MANAGEMENT-IP status
python3 configure-device.py --router https://ROUTER-MANAGEMENT-IP logs
python3 configure-device.py --router https://ROUTER-MANAGEMENT-IP disable
These commands also require ROUTEROS_PASSWORD. For more detailed daemon logs,
reconfigure with --debug 1; return to --debug 0 afterward. Logs are bounded
RAM buffers, not flash files, and disappear on reboot.
Later updates
Upload just a new compatible, same-key olsr NPK into the root of RouterOS Files, then reboot. Updating option is necessary only when runtime utilities change. Configuration is retained. Netinstall is not needed for every OLSR update. Check System > Packages and the system log after reboot. Keep flash headroom.
To use your own signing keys, follow README.md and docs/building.md. Another publisher's package or your newly generated key is not automatically trusted; use a coherent own-key system and add-on installation.