Supported Platforms
Related Documentation
- M, MX, SRX, T Series
- token
- MX Series
- Configuring Extended DHCP Local Server Dynamic Client Reconfiguration
Configuring a Token for DHCP Local Server Authentication
You can configure the local server to include a constant, unencoded token in the DHCP forcerenew message as part of the authentication option it sends to clients. The client compares the received token with a token already configured on the client. If the tokens do not match, the DHCP client discards the forcerenew message. Use of the token provides rudimentary protection against inadvertently instantiated DHCP servers.
(Optional) To configure the DHCP local server to include a token in the forcerenew message sent to the client, for all clients:
- Specify the token.
For DHCPv4:
[edit system services dhcp-local-server reconfigure]user@host# set token 8ysIU9E32k8rFor DHCPv6:
[edit system services dhcp-local-server dhcpv6 reconfigure]user@host# set token 8ysIU9E32k8r
To override the global configuration for a particular group of clients, include the statement at the [edit system services dhcp-local-server group group-name reconfigure] hierarchy level or the [edit system services dhcpv6 dhcp-local-server group group-name reconfigure] hierarchy level.
Related Documentation
- M, MX, SRX, T Series
- token
- MX Series
- Configuring Extended DHCP Local Server Dynamic Client Reconfiguration
Published: 2013-02-11
Supported Platforms
Related Documentation
- M, MX, SRX, T Series
- token
- MX Series
- Configuring Extended DHCP Local Server Dynamic Client Reconfiguration
