Page MenuHomeVyOS Platform

Support wide-dhcp6-relay
Closed, WontfixPublicFEATURE REQUEST

Description

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.

Details

Version
-
Is it a breaking change?
Perfectly compatible
Issue type
Internal change (not visible to end users)

Event Timeline

jack9603301 claimed this task.
jack9603301 created this object in space S1 VyOS Public.
jack9603301 moved this task from Open to In Progress on the VyOS 1.4 Sagitta board.
jack9603301 changed the subtype of this task from "Task" to "Feature Request".Jun 2 2021, 4:46 PM
jack9603301 changed the subtype of this task from "Feature Request" to "Bug".Jun 3 2021, 10:45 AM
jack9603301 changed the subtype of this task from "Bug" to "Feature Request".Jun 3 2021, 11:21 AM

Hi Jack,

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.

@c-po

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

@c-po You haven't replied for a long time, please let me know if you have any other questions

dmbaturin triaged this task as Wishlist priority.Jan 9 2024, 5:15 PM
dmbaturin edited projects, added VyOS 1.5 Circinus; removed VyOS 1.4 Sagitta.
dmbaturin set Issue type to Unspecified (please specify).
dmbaturin edited projects, added VyOS Rolling; removed Restricted Project.Oct 14 2024, 11:16 AM
dmbaturin changed Is it a breaking change? from Unspecified (possibly destroys the router) to Perfectly compatible.
dmbaturin changed Issue type from Unspecified (please specify) to Internal change (not visible to end users).
syncer claimed this task.
syncer subscribed.

There is no business case for this feature