Dhcpv6 related issues

1. Common sense problem:

What is the relationship between DHCPV4 options and DHCPv6 options, is it independent of each other, or is V that contains the relationship? For example: option 12 can be used in DHCPv6?

2. Configuration problem:

config interface 'wan_6'
	option device '@wan'
	option proto 'dhcpv6'
	option peerdns '0'
	option reqaddress 'try'
	option reqprefix 'auto'
	option clientid '00010001386cd300910052c0dC01'
	option sendopts '12:ztexxxx'
  1. CLIENTID has LLT, EN, LL type. Whether 00010001 in the above configuration represents type 1. If the default type 3 requires only Mac HexString later.

  2. After the Sendopts configuration, it is prompted to make an error, so whether it is DHCPv6 without option 12 or the configuration parameter is problematic.

Tue Oct 1 12:46:31 2023 daemon.notice netifd: wan_6 (28613): Usage: odhcp6c [options] <interface>
Tue Oct 1 12:46:31 2023 daemon.notice netifd: wan_6 (28613):
Tue Oct 1 12:46:31 2023 daemon.notice netifd: wan_6 (28613): Feature options:
Tue Oct 1 12:46:31 2023 daemon.notice netifd: wan_6 (28613): 	-S <time>	Wait at least <time> sec for a DHCP-server (0)
Tue Oct 1 12:46:31 2023 daemon.notice netifd: wan_6 (28613): 	-N <mode>	Mode for requesting addresses [try|force|none]

.......

They are independent of each other and there is a different program responsible for each DHCP version.

2 Likes
clientid:  Override client identifier in DHCP requests (Option 1). The odhcp6c default is 00030001 concatenated with the device MAC address - see RFC 8415

sendopts:  Space-separated list of additional DHCP options to send to the server. Syntax: option:value where option is either an integer code or a symbolic name such as hostname.

It may be the reason why there are not many use. The expression of the official documentation is easily confused

There's no relation of the numeric assignment of DHCP options between DHCPv4 and DHCPv6. When using option numbers to directly configure options that don't have a high-level alias, the relevant RFCs for DHCPv6 should be consulted, such as RFC8415.

1 Like

Thanks! But what I want to say here is that the official documentation steps in detail and ambiguity!