IRRd 4.1.4

See https://irrd.readthedocs.io/en/stable/releases/4.1.4/

Note that upgrading to 4.1.3 or newer is strongly recommended for all 4.1.x users.

(This release was re-published a second time on GitHub due to a tag change. This only affected published documentation and not the source code. 4.1.4 was actually released on June 18th.)

IRRd 4.1.3

Upgrading strongly urged for all 4.1.x users. See https://irrd.readthedocs.io/en/stable/releases/4.1.3/

IRRd 4.2.0 beta 1

First beta of 4.2.0 https://irrd.readthedocs.io/en/latest/releases/4.2.0/

IRRd 4.1.2

See https://irrd.readthedocs.io/en/stable/releases/4.1.2/

IRRd 4.2.0 alpha 2

IRRd now cleanly terminates startup, if the whois or HTTP workers are unable to start, e.g. due to a missing database. See f378a67 and #451 for details. Systemd example also updated in docs.

https://irrd.readthedocs.io/en/latest/releases/4.2.0/

IRRd 4.2.0 alpha 1

This is the first alpha release of IRRd 4.2: https://irrd.readthedocs.io/en/latest/releases/4.2.0/

IRRd 4.1.1

https://irrd.readthedocs.io/en/v4.1.1/releases/4.1.1/

IRRd 4.1.0

https://irrd.readthedocs.io/en/v4.1.0/releases/4.1.0.html

IRRd 4.1.0 release candidate 4

Fix #394 - Fix handling of last-modified in irrd_database_update (#395)

CAUTION: if you are upgrading from a 4.1 version prior to rc3, also read the rc3 release notes
https://github.com/irrdnet/irrd/releases/tag/v4.1.0rc3

IRRd 4.1.0 release candidate 3

https://irrd.readthedocs.io/en/v4.1.0rc3/releases/4.1.0.html
4.1.0rc3 contains a new database migration, so you must run irrd_database_upgrade before starting IRRd.

CAUTION: if you have been running any 4.1 pre-release, you may need to forcibly reload certain sources.
This is required for sources where both of the following apply:

• You mirror over NRTM from another source.
• The source had RPKI and/or the scopefilter enabled at some point in time since the last full reload, but do not currently have it enabled, either because you later disabled RPKI or the scopefilter, or set rpki_excluded or scopefilter_excluded for the source.

These sources must be reloaded after upgrading to 4.1.0rc3, using the irrd_mirror_force_reload command. Failure due to so can lead to mysterious mirroring failures and missing data, which may or may not result in logged errors.

This issue does not apply:

• for upgrades from IRRd 4.0.x to 4.1.0rc3
• if you have never enabled RPKI and/or the scopefilter
• if RPKI and/or the scopefilter has been enabled in the past, and is still enabled for the same sources

Major changes since 4.1.0rc2:

• Authorisation now also looks at related objects for route(6) creations
• NRTM serials are automatically synchronised with the NRTM source, if the scope filter and RPKI are disabled (for that source, or all of IRRd)

Full changes since 4.1.0rc2:
2d4b6a7 Fix #384 - Run scopefilter update when exclusions change
efd609c Fix #127 - Extend authorisation for auth changes to related objects
51a7275 Minor code cleanup.
4d2874d Fix #385 - Assign correct exports to serials (#390)
b9c664b Fix #381 - Fix corrupt gzip files on OpenBSD (#391)
a16b62d Fix #382 - Use synchronised serials for NRTM where possible. (#383)
2a86156 Add OpenBSD to tested list
0ae3501 Ref #290 - Make changed: attributes optional now that last-modified is auto-set (#377)
9a9cbc6 Ref #4 - Restrict scopefilter to route(6) (#374)
3a0dfad Restrict rpki.notify_invalid_enabled requirement to setups with auth sources (#373)
82765bf Show current version number in docs index.