This is an experimental project. I plan to use wide-dhcp6-relay to support DHCPv6 relay, which may break the limitation of ISC DHCP on PPPoE interface.
- Difficulty level
- Unknown (require assessment)
- Why the issue appeared?
- Will be filled on close
- Is it a breaking change?
- Unspecified (possibly destroys the router)
I wonder why this is flagged only as refactoring bit you open an entire new CLI tree. I also wo der why this is now under the interface secrion and no longer under service.
Please explain in a more detailed manner.
I wonder why this is flagged only as refactoring bit you open an entire new CLI tree.
In fact, I designed it as fix at the beginning, but I found that it almost needs to modify the existing service logic (I can't reuse the old logic, I need to modify the CLI), so I changed it to refactoring
In fact, I don't know if it's appropriate, but I'm not implementing a new service or feature, but a new implementation of an existing service (whether it's configuration or template), so this is actually called refactoring
I also wo der why this is now under the interface secrion and no longer under service.
This is mainly because the configuration structure of the interface is convenient and friendly, and the PD configuration is in the same path. This is just a draft. If necessary, you can change the CLI
Traditionally, only one configuration is needed:
set interfaces ethernet eth0 dhcpv6-option dhcp6relay interface eth1
The above configuration takes eth0 as the upstream and provides services for eth1
The specific CLI and details may still need to be explored, so I call it a draft
The new implementation seems to have to open a service instance for each upstream interface, so it might be a good choice to place it under the interface