It is not required for the `peer_ip6` to be configured on babel
interfaces. IPv6 link local addresses are sufficient for routing.
However, setting `peer_ip` is still required until IPv4 routing with a
IPv6 nexthop is working. For this, a newer Kernel and support from Babel
is still required.
Signed-off-by: Johannes Kimmel <fff@bareminimum.eu>
So far peer ips were only distributed via babel if they happened to fall
into the predefined network ranges. Currently, these only contain the
prefixes from the private and ULA ranges. Specifying any other address,
e.g. a globally routed one, will not result in the router being
reachable via that address.
Now peer ips are added to the `loopback` interface and babel is
instructed to redistribute addresses from `lo`, so any peer ip is
redistributed and therefore the router is now reachable via these
addresses.
Another option could have been to dynamically add a redistribute filter
for the peer ips before this section:
```
config filter
option type 'redistribute'
option local 'true'
option action 'deny'
```
Sadly it almost impossible to do this in a reasonable manner with uci,
that doesn't involve iterating over all filter options or requiring this
specific section to be always named.
Adding the peer ips to `lo` is also the more conventional way to
configure an address "owned" by a router.
Signed-off-by: Johannes Kimmel <fff@bareminimum.eu>
Johannes Kimmel