Configuration revisions

{{#LIVE_ALL}}Live matches latest · {{LIVE_N}} of {{LIVE_M}} fragments{{/LIVE_ALL}} {{#LIVE_SOME}}Live matches latest · {{LIVE_N}} of {{LIVE_M}} fragments{{/LIVE_SOME}} {{#LIVE_NONE}}Nothing recorded yet{{/LIVE_NONE}} {{#LIVE_NOCMP}}Live matches latest · no fragment compared{{/LIVE_NOCMP}}

{{ERROR}}{{#ERROR_REV}} Show revision {{ROLLBACK_REV_SHORT}}{{/ERROR_REV}}

Rolling back…

The stored revision is being re-applied to the live router; this can take a few minutes.

You can view revisions and diffs. Rolling a revision back requires the revision:rollback permission (administrator).

No revisions recorded yet. Apply a configuration change to stamp the first revision.

Last change

Fragments recorded

Live matches latest

{{LIVE_N}} of {{LIVE_M}}

Retention

{{KEEP_PER_KEY}} per fragment

older revisions are pruned automatically

Revisions

Showing the newest {{SHOWN}} of {{TOTAL}} revisions. The list is capped at {{LIST_MAX}} revisions or {{LIST_BYTE_KIB}} KiB, whichever comes first; OgmaProtect keeps the last {{KEEP_PER_KEY}} revisions of each fragment on disk.

When (UTC)	Fragment	Kind	By	Note	State	Actions
{{GROUP_LABEL}} · UTC
{{#HAS_WHEN}}{{REV_WHEN}}{{/HAS_WHEN}}{{^HAS_WHEN}}—{{/HAS_WHEN}} {{REV_SHORT}}	{{#HAS_FRAG}}{{REV_FRAG}}{{/HAS_FRAG}}	{{KIND_LABEL}}	{{REV_ACTOR}}	{{REV_NOTE}}	{{#HAS_STATE}}{{STATE_LABEL}}{{/HAS_STATE}}	{{#CAN_ROLLBACK}} {{/CAN_ROLLBACK}}{{#NO_ROLLBACK_FRAG}} No rollback for {{REV_FRAG}}{{/NO_ROLLBACK_FRAG}}{{#NO_ROLLBACK_PLAIN}} No rollback{{/NO_ROLLBACK_PLAIN}}
{{#CAN_READ}} Show changes (vs live) Open this with JavaScript enabled to load the changes. {{/CAN_READ}}{{#CAN_ROLLBACK}} Roll back to this revision A rollback re-applies this revision's stored configuration through the backup pipeline (mandatory route re-assert). It is confirm-gated and creates a new "rollback" revision. {{#IS_NET}} Rolling back the network fragment can change interface addresses and sever the management path. Ensure you have console access; tick "Accept management-path risk". {{/IS_NET}} Confirm rollback Accept destructive changes (removed addresses/rules) Stop any routing domain's resolver this revision does not keep (a dns rollback is refused by name otherwise){{#IS_NET}} Accept management-path risk{{/IS_NET}} {{/CAN_ROLLBACK}}

About revisions

Every successful apply stamps one immutable revision of one configuration fragment (net, pf, dns and so on) with who made it, when, and a note. A revision marked Live is byte-identical to what the router is running now; Same as live is an older identical copy; Not live means the newest recorded revision of that fragment is not what is running.

"Show changes" diffs the stored revision against the live fragment (or against the previous revision of the same fragment). Lines starting with + are in the revision, lines starting with − are in the base.

Use Explain above to show or hide this help.

Rollback rules

Rollback is available for these fragments: {{ROLLBACK_KEYS}}. Other fragments are recorded for reference and diffing only.

Rolling back net can change addresses on the interface you are connected through; keep console access and tick the management-path acknowledgement. Every rollback also re-asserts the live net fragment, so a second "rollback" revision of net is recorded alongside the one you chose.

Rolling back dns restores every routing domain's resolver as it was in that revision. A rollback that would stop a routing domain's running resolver is refused and names the domains; tick "Stop any routing domain's resolver this revision does not keep" to proceed.

Budgets per account: {{ROLLBACK_BUDGET}} rollbacks or backup imports per hour, {{DIFF_BUDGET}} diffs per hour. OgmaProtect keeps the last {{KEEP_PER_KEY}} revisions of each fragment; older ones are pruned automatically.

Revision summary

Revisions