Skip to content

Latest commit

 

History

History
208 lines (168 loc) · 6.47 KB

CHANGELOG.md

File metadata and controls

208 lines (168 loc) · 6.47 KB
Raw

CHANGELOG

v1.2.1

April 27, 2022

This is a minor bug fix release following v1.2.0.

  • Fixes a typo in the new advertiser Route Information metric name

v1.2.0

April 26, 2022

  • A variety of new Prometheus metrics are supported, including
    • advertiser misconfigurations (such as an interface which advertises itself as a default router but is not forwarding IPv6 traffic)
    • advertiser DNS Search List lifetimes
    • advertiser Recursive DNS Servers lifetimes
    • advertiser Route Information lifetimes
    • monitor router advertisement flag states

v1.1.2

April 6, 2022

This is a minor bug fix release following v1.1.1.

  • CoreRAD will now verify inconsistent NDP Captive Portal options advertised by other routers on the same subnet. This was an oversight from when the captive portal option was introduced in v0.3.2.
  • More internal cleanups to use Go 1.18 features, including an updated version of github.com/mdlayher/ndp.

v1.1.1

March 20, 2022

This is a minor bug fix release following v1.1.0.

  • v1.1.0 switched to Go 1.18's net/netip library, and an upgrade to github.com/mdlayher/ndp resulted in IPv6 zone identifiers accidentally appearing in existing Prometheus metric labels. This is resolved and the previous behavior is restored.
  • Internal cleanups to use more Go 1.18 features and to enable testing with less reliance on the host environment.

v1.1.0

March 19, 2022

  • The interfaces.route.prefix option now supports automatic route advertisement for IPv6 destination routes configured on loopback interfaces by specifying a route of ::/0 or an empty string. This is similar to the ::/64 wildcard for prefix advertising and the :: wildcard for RDNSS servers.

Assume the following IPv6 routes are defined on Linux loopback interface lo. Note that these routes reside in Linux's "main" routing table.

$ ip -6 route show dev lo
::1 proto kernel metric 256 pref medium
unreachable fd9e:1a04:f01d::/48 proto static metric 1024 pref medium

Before:

[[interfaces]]
name = "eth0"
advertise = true
  [[interfaces.route]]
  prefix = "fd9e:1a04:f01d::/48"

After:

[[interfaces]]
name = "eth0"
advertise = true
  [[interfaces.route]]
  # No route options means "::/0". Equivalents are:
  # prefix = ""
  # prefix = "::/0"

v1.0.0

January 31, 2022

CoreRAD is now considered stable and ready for production use on Linux routers!

This project has been deployed and running on Matt Layher's Linux home router for more than 2 years with no problems. CoreRAD should work with reduced functionality on *BSD as well, but this has not been tested.

  • The configuration file format is now considered stable! Only additive changes will be made for the remainder of v1.x.x.
  • The valid lifetime of an IPv6 address is now taken into account when selecting a stable address for automatic prefix and RDNSS advertising.
  • All Go dependencies have been upgraded to their latest stable versions.

v0.3.4

September 3, 2021

Special thanks to @markpash for his help testing various features in this release.

  • CoreRAD will now operate on interfaces which do not have a MAC address, such as PPPoE interfaces. Monitor mode works on these interfaces, but advertise mode may still have subtle bugs. Feedback is welcome.
  • CoreRAD will now log errors when an interface is configured to advertise an IPv6 default route (interfaces.default_lifetime is non-zero) but is incapable of doing so due to IPv6 forwarding being disabled on the interface. This will notify the user that their configuration is invalid and they should either enable IPv6 forwarding or remove the interfaces.default_lifetime configuration to resolve the problem.
  • IPv6 addresses which are flagged as stable (manage temporary addresses, stable privacy, or EUI-64 address format) on Linux are now preferred for automatic prefix and RDNSS advertising.
  • IPv6 addresses which are flagged as non-stable (deprecated, temporary, or tentative) on Linux will no longer be considered candidates for automatic prefix and RDNSS advertising.
  • The interfaces.rdnss.servers and interfaces.dnssl.domain_names options now verify that all string array arguments are unique.

v0.3.3

July 20, 2021

  • CoreRAD now outputs a minimal configuration file when the -init flag is passed. The user must still adjust interface names for their router, but most users won't need to tweak the vast majority of router advertisement settings. A full reference configuration file remains available online.
  • Groups of interfaces can now be configured identically by specifying the interfaces.names option rather than interfaces.name. Note that these options are mutually exclusive. The following configurations are equivalent:

Before:

[[interfaces]]
name = "vlan0"
advertise = true

[[interfaces]]
name = "vlan1"
advertise = true

After:

[[interfaces]]
names = ["vlan0", "vlan1"]
advertise = true
  • The interfaces.prefix.prefix and interfaces.rdnss.servers options will now apply their most common default settings when these options are unset. The following configurations are equivalent:

Before:

[[interfaces]]
name = "eth0"
advertise = true
  [[interfaces.prefix]]
  prefix = "::/64"
  [[interfaces.rdnss]]
  servers = ["::"]

After:

[[interfaces]]
name = "eth0"
advertise = true
  [[interfaces.prefix]]
  [[interfaces.rdnss]]
  • The interfaces.rdnss.servers option's wildcard value of :: can be used to advertise a DNS server from the configured interfaces, in addition to zero or more statically defined DNS servers.
[[interfaces]]
name = "eth0"
advertise = true
  [[interfaces.rdnss]]
  servers = ["::", "2001:db8::1"]

v0.3.2

June 25, 2021

  • RDNSS now supports a :: wildcard syntax which will choose a suitable DNS server address from the same interface, preferring IPv6 Unique Local Addresses, then Global Unicast Addresses, then Link-Local Addresses.
  • New Captive Portal option for router advertisements, per RFC 8910, section 2.3.

v0.3.1

May 28, 2021

  • Prefixes advertised automatically via ::/64 are pulled from each configured interface and logged on startup
  • Additional checks to prevent the use of IPv6-mapped-IPv4 addresses

v0.3.0

January 3, 2021

  • It's stable and should work great for home use cases! Go forth and use it!