[Feature Request] Allow separate Interface ID configuration for GUA and ULA
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 37
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
Currently, network.lan.ip6ifaceid applies the same Interface ID policy to both GUA and ULA addresses.
I think GUA and ULA should have separate Interface ID configuration because they serve different purposes:
- GUA is publicly routable, so a randomized Interface ID is desirable for privacy and reducing address predictability.
- ULA is intended for local communication and infrastructure services, where a stable and simple address such as
fdxx:xxxx:xxxx::1is more useful.
For example, it would be useful to support:
option ip6ifaceid 'random' # GUA
option ip6ulaifaceid '::1' # ULA
This would allow GUA to use a privacy-oriented Interface ID while keeping the router's ULA address stable and easy to remember, for example as a local DNS server address.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the existing network.lan.ip6ifaceid option is applied to GUA and ULA addresses. Define separate configuration behavior for GUA and ULA, including the example ip6ulaifaceid value, and verify that randomized GUA addressing and a stable ULA address can coexist.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100