Patches to add flexibility to odhcpd's Route Info Option handling#33
Open
janakj wants to merge 2 commits intoopenwrt:masterfrom
janakj:master
Open
Patches to add flexibility to odhcpd's Route Info Option handling#33janakj wants to merge 2 commits intoopenwrt:masterfrom janakj:master
janakj wants to merge 2 commits intoopenwrt:masterfrom
janakj:master
Conversation
In RA server mode, odhcpd parses the routing table for unreachable routes and announces such routes on the interface via IPv6 RA Route Info Options. On a router an unreachable route typically represents the prefix assigned to the router via prefix delegation or some other mechanism. Announcing the unreachable route via RA makes all the prefixes of the router reachable from auto-configured hosts. This patch makes this feature configurable via the new configuration option ra_unreachable (turned on by default).
In some network scenarios it may be necessary to announce manually configured routes via the IPv6 Route Info Option. This patch implements a new configuration option called ra_route which makes this possible. The option is a list of IPv6 network prefixes to announce, optionally followed by a space-delimited preference identifier (low/medium/high). For example, the following configuration: list ra_route 'fd00::/16' list ra_route '2008:1234::/32 high' Would add two more Route Info Options to the RA message (in addition to any RI options automatically generated odhcpd) with the specified routes. The second route will be announced with pref=high.
|
ping @dedeckeh |
|
Why has this never been merged? This would implement RFC4191 (https://tools.ietf.org/html/rfc4191) from what I understand. |
|
This is an useful feature, why not merge it for this long time? |
|
any news? |
Contributor
|
@Alphix I think at least statically defining some routes could be a useful feature here. We'd have to pick this in ourselves since the source repo is gone. |
Author
Unfortunately, I no longer have the source repository after such a long time. But you can still view the contents of the patches here on GitHub. It should not be hard to re-create the commits. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
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