client-id (DHCP Relay Agent)
Syntax
client-id <exclude-headers> <use-automatic-ascii-hex-encoding>;
Hierarchy Level
[edit forwarding-options dhcp-relay authentication username-include], [edit forwarding-options dhcp-relay group group-name authentication username-include], [edit forwarding-options dhcp-relay dhcpv6 group group-name authentication username-include], [edit forwarding-options dhcp-relay dhcpv6 authentication username-include], [edit forwarding-options dhcp-relay dual-stack-group group-name authentication username-include], [edit logical-systems logical-system-name forwarding-options dhcp-relay dhcpv6 ...], [edit logical-systems logical-system-name routing-instances routing-instance-name forwarding-options dhcp-relay dhcpv6 ...], [edit routing-instances routing-instance-name forwarding-options dhcp-relay dhcpv6 ...]
Description
Specify that the client identifier (DHCP option 61) is concatenated with the username during the subscriber authentication or client authentication process.
Options
| exclude-headers |
By default, all headers that are part of the client identifier format in
option 61 are included in the username string used for RADIUS
authentication. Configure the |
| use-automatic-ascii-hex-encoding |
By default, all components of the client identifier are converted to
ASCII hex to encode the username. Configure the
Use this option instead of the |
Required Privilege Level
interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Release 11.4.