Files
feedc0de 5bb6e0fe55
Check source / check (push) Successful in 16s
Initial version (not finished, work in progress)
2026-11-18 10:10:39 +01:00

5.0 KiB

ARM hardware validation

The first hardware test uses RouterOS, option, and olsr only. Do not add Wi-Fi packages until the installed free space has been measured. The development 7.25.1 set totals 13,410,367 bytes of NPK files; this is a transfer-size estimate, not a guarantee about usable flash or upgrade headroom.

Install with an empty configuration

Build the packages with the same signing key as the patched installer. Connect the computer directly to ether1 and assign the computer 192.168.88.2/24. From the directory containing the unpacked Linux installer and three NPKs:

sudo ./netinstall-cli -e -b --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 applies an empty configuration. There is no default firewall, bridge, DHCP server, or configured management IP. -b removes removable branding. Do not use -f to bypass a storage failure. Netinstall's temporary boot address is not the router's management address after installation.

Put the router into Netinstall mode and wait for completion and reboot. Connect using MAC Winbox over the directly connected Ethernet link. Set an administrator password and add a management address in the RouterOS terminal:

/ip address add address=192.168.88.1/24 interface=ether1

Check /system package print, /system license print, and /system resource print. Record whether the original hardware license is recognized. Our patcher retains the original license-verification key; that does not recover a license that was previously deleted or replaced.

Test executable loading before starting routing

The option package contains a source-built BusyBox with a bash entry point expected by the official login program. SSH developer-shell access is a hardware test requirement, not yet a validated guarantee on the official-derived image. If ssh devel@192.168.88.1 works, run:

/pckg/option/bin/busybox uname -a
/pckg/olsr/bin/olsrd -v

The second command prints the daemon version and exits. It must not start neighbor discovery or change routes. If either fails, record the exact error before changing firmware or configuration. A successful version check establishes executable loading only; startup, UI controls, neighbor formation, forwarding, and route cleanup still require separate tests.

hAP ac2 integration results, 2026-11-18

Own-key RouterOS 7.25.1, option and OLSR installed on RBD52G. Original license level 4 remained available. Updating the option and OLSR NPKs through Files/FTP followed by reboot worked without Netinstall, even with the same RouterOS version. A later OLSR-only update worked too. Configuration survived.

OLSRv1 discovered two symmetric neighbors on a VLAN with a /32 node address. The local BIRD bridge imported protocol 100 from private kernel table 201 and exported it over loopback BGP to RouterOS. Approximately 700 routes became active, dynamic BGP routes in RouterOS; three neighbor pings succeeded. The import filter currently permits 10.0.0.0/8 only, so other learned prefixes are not installed into RouterOS's main table. No default route is imported.

Direct neighbors appear in the OLSR kernel table with their own IP as gateway. The BGP export filter must identify /32 routes where gateway equals destination, mark those with community 64513:1, and let RouterOS resolve them directly on the OLSR interface. All other exported routes carry community 64513:698 and resolve through those neighbor routes. Without this distinction, routes were dynamic but inactive.

The supervisor now starts in a separate session using a small double-fork launcher. Disabling the OLSR scheduler withdrew all native BGP routes and cleared the private OLSR routes in 7.49 seconds during the measured test. Re-enabling rediscovered neighbors and restored hundreds of active routes. Logs stay in bounded 32 KiB RAM files. Free flash after the update was about 1.34 MiB.

An experimental .jg UI descriptor was followed by Winbox crashes after login. Removing that descriptor restored login. Because routing also stopped during that rollback, the initial observation alone does not isolate the cause. Routing was re-enabled without the descriptor for a controlled comparison. The native OLSR UI remains unvalidated and is excluded from release generation. The separate web control page is a development aid, not the requested native UI.

Follow-up crash analysis: Winbox 4.5 on Linux recorded its first SIGSEGV at 09:50:54 CET, before BGP integration was configured at 09:51:19. Its faulting instruction dereferenced a null object in code containing SLOTREF diagnostics. The removed descriptor placed a slot: Name predicate on the menu itself, where no row object exists. This is a stronger explanation than route volume; 701 active routes were subsequently observed without that descriptor. A reduced native Service descriptor removes the predicate and uses the official scheduler handler/field IDs. It remains an explicit experimental build, awaiting client validation, and does not implement the other requested controls yet.