What's in 9.11.1
TOD 9.11.1 fixes device rename hangs and initial device naming. It requires no new database migration or configuration change from 9.11.0.
Device rename hangs
#15: A device edit could hold a row lock while waiting for an audit insert on a separate database connection. Renames now write their audit entries in the edit transaction. A savepoint prevents a failed audit insert from aborting the edit. Independent audit calls have a five-second database lock timeout.
Initial device names
#14: Leave Display Name blank to use the RouterOS identity returned by the authenticated adoption probe. If identity is unavailable, TOD uses the IP address. Explicit names take precedence. Manual add, subnet imports and credential-profile imports follow this rule. Duplicate inferred names fail only their own credential-profile import entry; later entries can continue.
Updating an existing installation
Back up first, retain your existing environment file and data directories, and update the API and frontend images or rebuild them from source. Use the same Compose files and environment file as your installation. Recreate the containers with docker compose up -d using those options. No reinstall is required. See the update instructions.
When upgrading from before 9.11.0, also update the Compose files to include the API firmware-cache mount and make its host directory writable by UID 1001. Pulling images alone does not add that mount. See the firmware-cache instructions.
Verification
The original rename code timed out in both super_admin and operator regression tests. The fixed code passed 13 real PostgreSQL tests using the application database role, including repeated HTTP renames, separate device writes, audit rollback and failure isolation, the five-second lock limit, inferred names and both bulk-import paths. The local frontend suite passed 70 tests, including blank-name submission checks.
Authenticated probe replies were controlled test outcomes for the naming regressions. This patch did not receive a new physical-router adoption test or browser workflow test. The firmware downgrade and upgrade hardware results belong to the separate 9.11.0 release report.