[docker-dhcp-relay] Add server_vrf to the DHCPv6 relay YANG and config CLI#28171
Open
AnantKishorSharma wants to merge 2 commits into
Open
[docker-dhcp-relay] Add server_vrf to the DHCPv6 relay YANG and config CLI#28171AnantKishorSharma wants to merge 2 commits into
AnantKishorSharma wants to merge 2 commits into
Conversation
AnantKishorSharma
requested review from
dgsudharsan,
praveen-li and
venkatmahalingam
as code owners
June 30, 2026 17:18
Contributor
Author
Contributor
Author
|
@praveen-li @dgsudharsan @venkatmahalingam @qiluo-msft @lguohan - Please review when you have a chance. |
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
AnantKishorSharma
force-pushed
the
dhcp6relay-vrf-support
branch
from
July 1, 2026 08:03
26ee8a1 to
c0f0a5e
Compare
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
…y config at runtime Start dhcp6relay unconditionally instead of gating it on dhcpv6_servers, skip the dhcp_relay container restart on the IPv6 config path, and bound the per-interface readiness wait when has_sonic_dhcpv4_relay is set. Regenerate the affected goldens and make the cli-plugin tests version-aware. Signed-off-by: Anant Kishor Sharma <anant.kishor-sharma@hpe.com>
…g CLI Add the optional server_vrf leaf to sonic-dhcpv6-relay (with model tests) and a --server-vrf option to the v6 relay destination CLI. Relates to sonic-net/sonic-dhcp-relay#89. Signed-off-by: Anant Kishor Sharma <anant.kishor-sharma@hpe.com>
AnantKishorSharma
force-pushed
the
dhcp6relay-vrf-support
branch
from
July 13, 2026 20:46
c0f0a5e to
42b7322
Compare
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
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
2 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.
Why I did it
The SONiC-native DHCPv6 relay can now reach DHCPv6 servers through a non-default VRF (sonic-net/sonic-dhcp-relay#89 / sonic-net/sonic-dhcp-relay#117). This adds the
server_vrfknob in YANG and the config CLI so operators can configure it.How I did it
sonic-dhcpv6-relay): add the optionalserver_vrfleaf to theDHCP_RELAYlist — the VRF in which the configured DHCPv6 servers are reachable; the relay binds its upstream socket to it (SO_BINDTODEVICE). Added positive and invalid-value model tests.config dhcp_relay ipv6 destination add <vlan> <server> --server-vrf <vrf>): writeserver_vrftoDHCP_RELAY, validated against the VRF table; no container restart (the relay applies the change at runtime).How to verify it
sonic-yang-modelsmodel tests pass for the new leaf (valid + invalid-value cases).docker-dhcp-relayCLI plugin tests pass, including the new--server-vrfadd and invalid-VRF cases.Relates to sonic-net/sonic-dhcp-relay#89