Patches to add flexibility to odhcpd's Route Info Option handling #33
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
While working on a moderately complex IPv6 network setup, I ran into issues with odhcpd's handling of the RA Route Info Option. By default, odhcpd generates a Route Info Option in RAs based on the existence of unreachable routes on the router and this behavior cannot be changed. This pull request implements two new configuration options which make it possible to change odhcpd's behavior somewhat.
The option "ra_unreachable" makes it possible to disable the auto-generated Route Info Option. This is useful, for example, if the router contains multiple unreachable routes or if the route's prefix is different from what should be announced via RA.
The second option "ra_route" makes it possible to manually configure additional routes to be announced in /etc/config/dhcp. This is a per-interface option, different routes can be configured for different interfaces. It's a list option with the following value format:
The preference field is optional (medium by default). Here's an example:
--Jan