interfaces: introduce idassoc6 mode #9155
We're adding a bit of technical debt here for the simple reason
to decouple the track6 mode from automatic radvd and dhcpv6 runs.
Specifically avoid the "dhcpd6track6allowoverride" flag in this
mode but keep the data the same otherwise for interoperability.
interface: POC for multi-dhcp6c support
I'm not entirely sure why we settled for a single deamon of
dhcp6c back in the day, but there are certianly downsides to
it and I don't see something that wasn't fixed in the meantime
that makes this not work.
At the moment this splits off dhcp6c only but we need to
change the daemon's print a bit to avoid complaining about
"other" devices since the situation to ignore a non-listening
interface is normal and not "ignoring" something obvious as
the INFO log message suggests.
rtsold still needs to be split to allow for HUP reload of
a single interface instead of forcing a restart of all
DHCPv6 WAN clients at the same time.
interfaces: introduce idassoc6 mode #9155
We're adding a bit of technical debt here for the simple reason
to decouple the track6 mode from automatic radvd and dhcpv6 runs.
Specifically avoid the "dhcpd6track6allowoverride" flag in this
mode but keep the data the same otherwise for interoperability.
interfaces: decouple 'track6' mode magic in radvd/dhcpv6 #9155
The code always took the shortcut to "track6-interface" but since
we want a new mode without a side effect and keep the attributes
for common code cases the same switch this to explicit mode check.
interfaces: introduce idassoc6 mode
We're adding a bit of technical debt here for the simple reason
to decouple the track6 mode from automatic radvd and dhcpv6 runs.
Specifically avoid the "dhcpd6track6allowoverride" flag in this
mode but keep the data the same otherwise for interoperability.
net/frr: Changelog for v1.50 (#5133)
* net/frr: Changelog for v1.50
* Fix a helptext to be more generic and one string.
* Remove private AS should be advanced
net/frr: Add capability support for BGP neighbors (#5128)
* net/frr: Add capability support for BGP neighbors
I've recently tried to use OPNsense in an environment where the use of link-local addresses is required.
Since the link-local capability is not available, I was not able to use OPNsense then.
Obviously, there are some other with the same problem:
* [os-frr] wrong interface for IPv6 link-local used to connect to neighbor #4962
* https://forum.opnsense.org/index.php?topic=36088.0
So, I'd like to offer support for BGP capabilities.
* net/frr: Improve help string for BGP Capabilities as suggested by @Monviech
* net/frr: Fix typo as found by @Monviech
* net/frr: Remove not needed attribute as suggested by @Monviech
[5 lines not shown]
interface: POC for multi-dhcp6c support
I'm not entirely sure why we settled for a single deamon of
dhcp6c back in the day, but there are certianly downsides to
it and I don't see something that wasn't fixed in the meantime
that makes this not work.
At the moment this splits off dhcp6c only but we need to
change the daemon's print a bit to avoid complaining about
"other" devices since the situation to ignore a non-listening
interface is normal and not "ignoring" something obvious as
the INFO log message suggests.
rtsold still needs to be split to allow for HUP reload of
a single interface instead of forcing a restart of all
DHCPv6 WAN clients at the same time.
interface: POC for multi-dhcp6c support
I'm not entirely sure why we settled for a single deamon of
dhcp6c back in the day, but there are certianly downsides to
it and I don't see something that wasn't fixed in the meantime
that makes this not work.
At the moment this splits off dhcp6c only but we need to
change the daemon's print a bit to avoid complaining about
"other" devices since the situation to ignore a non-listening
interface is normal and not "ignoring" something obvious as
the INFO log message suggests.
rtsold still needs to be split to allow for HUP reload of
a single interface instead of forcing a restart of all
DHCPv6 WAN clients at the same time.
router advertisements: migrate to MVC/API (#9603)
Migrate router advertisements to its own space. Although
the data shifts around a bit the end result should be equivalent.
Of note is that we currently do not have visibility for automatic
interface tracking when not disabled, but they can be disabled
manually by adding the interface configuration and unchecking
the service enable.
Co-authored-by: Monviech <gitacc at pischem.com>
radvd: forgot one spot where we wanted to disable automatic tracking
This also means we should not migrate empty nodes that existed because
they were not disabled or DHCPv6 was enabled there once.
