Here are the files that need to change. Firstly, the post-install script. If "ifupdown" is configured, use it instead. Secondly, the config file. Many networks are IPv4-only, especially college networks. So you should still use "clientid". ------ Please limit your reply to 7-bit ASCII.
# A sample configuration for dhcpcd. # See dhcpcd.conf(5) for details.
# Allow users of this group to interact with dhcpcd via the control socket. #controlgroup wheel # Inform the DHCP server of our hostname for DDNS. hostname # Use the hardware address of the interface for the Client ID. #clientid # or # Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361. # Some non-RFC compliant DHCP servers do not reply with this set. ####Suggestion: IPv6 is still unpopular in China.#### ####Many IPv4-only networks will only use clientid.#### ####Better be safe than sorry.#### clientid #duid # Persist interface configuration when dhcpcd exits. persistent # Rapid commit support. # Safe to enable by default because it requires the equivalent option set # on the server to actually work. option rapid_commit # A list of options to request from the DHCP server. option domain_name_servers, domain_name, domain_search, host_name option classless_static_routes # Respect the network MTU. This is applied to DHCP routes. option interface_mtu # Most distributions have NTP support. #option ntp_servers # A ServerID is required by RFC2131. require dhcp_server_identifier # Generate SLAAC address using the Hardware Address of the interface #slaac hwaddr # OR generate Stable Private IPv6 Addresses based from the DUID slaac private
dhcpcd5.postinst
Description: Binary data
publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
