Skip to content

Add routed port support to dhcp_relay#2276

Open
devesh-nexthop wants to merge 5 commits into
sonic-net:masterfrom
nexthop-ai:dhcp_relay_routed_ports
Open

Add routed port support to dhcp_relay#2276
devesh-nexthop wants to merge 5 commits into
sonic-net:masterfrom
nexthop-ai:dhcp_relay_routed_ports

Conversation

@devesh-nexthop

@devesh-nexthop devesh-nexthop commented Apr 1, 2026

Copy link
Copy Markdown
  • Added DHCP Relay support for routed ports.
  • For DHCP v4 add custom Circuit ID support
  • Updates to CLI and yang models.

Code changes PR:
[sonic-dhcp-relay] sonic-net/sonic-dhcp-relay#102
[sonic-buildimage] sonic-net/sonic-buildimage#26897
[sonic-mgmt] sonic-net/sonic-mgmt#24117

@mssonicbld

Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines

Copy link
Copy Markdown
No pipelines are associated with this pull request.

@mssonicbld

Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines

Copy link
Copy Markdown
No pipelines are associated with this pull request.

@devesh-nexthop
devesh-nexthop force-pushed the dhcp_relay_routed_ports branch from dce99b6 to 0131de2 Compare April 2, 2026 00:44
@mssonicbld

Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines

Copy link
Copy Markdown
No pipelines are associated with this pull request.

@devesh-nexthop
devesh-nexthop force-pushed the dhcp_relay_routed_ports branch from 0131de2 to f0e7e4e Compare April 2, 2026 01:18
@mssonicbld

Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines

Copy link
Copy Markdown
No pipelines are associated with this pull request.

@devesh-nexthop
devesh-nexthop marked this pull request as ready for review April 2, 2026 01:18
@ronan-nexthop

Copy link
Copy Markdown

@devesh-nexthop can we get some reviewers tagged here who have been involved in the discussion

@mssonicbld

Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command.

@rajesh-kumar-raju rajesh-kumar-raju left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My Understanding is

  • PORT | EthernetX contains dhcp_servers/dhcpv6_servers .
  • INTERFACE|EthernetX| makes EthernetX a routed L3 Interface
  • A Plain L2 PORT Without IP should not be treated as valid DHCP relay Interface.

Can we document whether this invalid case is rejected by config/YANG validation, ignored by dhcp_relay, or logged as an error?

Comment thread doc/DHCPv4_relay/DHCPv4-relay-agent-High-Level-Design.md
Comment thread doc/DHCPv4_relay/DHCPv4-relay-agent-High-Level-Design.md
Comment thread doc/DHCPv4_relay/DHCPv4-relay-agent-High-Level-Design.md
Comment thread doc/DHCPv6_relay/DHCPv6-relay-agent-High-Level-Design.md
- [5.1.3 Interop with Port-Based DHCP Server](#513-interop-with-port-based-dhcp-server)
- [5.1.4 DHCP Monitor](#514-dhcp-monitor)
- [5.1.5 Dual-Tor Support](#515-dual-tor-support)
- [5.1.6 Routed Port Support](#516-physical-port-support)

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Like we discussed in the meeting, please clarify whether the same support is available for port-channel interfaces and routed VLAN subinterfaces as well. If it is not supported, it would be better to explicitly document this limitation and explain why the same support cannot be provided.

@mssonicbld

Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines

Copy link
Copy Markdown
No pipelines are associated with this pull request.

rck-innovium and others added 3 commits June 16, 2026 18:55
Signed-off-by: Devesh Pathak <250206677+devesh-nexthop@users.noreply.github.com>
…-net#2072)

NO-ISS: MACsec gearbox: Deterministic MACsec backend selection for gearbox ports
Signed-off-by: Devesh Pathak <250206677+devesh-nexthop@users.noreply.github.com>
Signed-off-by: Devesh Pathak <250206677+devesh-nexthop@users.noreply.github.com>
@devesh-nexthop
devesh-nexthop force-pushed the dhcp_relay_routed_ports branch from 3b6893c to 5797254 Compare June 16, 2026 18:55
@mssonicbld

Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command.

@mssonicbld

Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines

Copy link
Copy Markdown
No pipelines are associated with this pull request.

Signed-off-by: Devesh Pathak <250206677+devesh-nexthop@users.noreply.github.com>
@mssonicbld

Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines

Copy link
Copy Markdown
No pipelines are associated with this pull request.

"dhcpv4_servers": ["10.0.0.1", "10.0.0.2"],
"circuit_id_format": "custom",
"circuit_id": "CustomCircuitID",
"max_hop_count": "10"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How is this entry set?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants