dhcpcd-discuss

Whether dhcpcd will support for Information-request packet type?

Puttaswamy, Rajesh

Tue Sep 29 16:15:46 2015

Hi,

I am executing the TAHI test cases of RFC 3736, and not able to send Information-request packets through dhcpcd client.

?  From the other dhcpv6 client like dhcp6c (wide-dhcp6), was able to send the DHCPv6 "Information-request" packet type to server for requesting options info while running the RFC3736 test cases

?  But, from the dhcpcd, these information-request options were sent as part of DHCPv6 Solicit packet type while running RFC3736 test cases

?  Since the RFC3736 TAHI test code is expecting the packet type as "Information-request" to request for options to the server and currently it is not getting it from dhcpcd, all the test cases in RFC3736 are failing

Below is my dhcpcd.conf content:

# 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.
# In this case, comment out duid and enable clientid above.
#duid
interface eth0
ia_na 1
ia_ta 2
# Persist interface configuration when dhcpcd exits.
#persistent
ipv6rs
ipv6ra_autoconf
# 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
# Most distributions have NTP support.
option ntp_servers

# Respect the network MTU.
# Some interface drivers reset when changing the MTU so disabled by default.
option interface_mtu
# A ServerID is required by RFC2131.
require dhcp_server_identifier
# Generate Stable Private IPv6 Addresses instead of hardware based ones
#slaac private
# A hook script is provided to lookup the hostname if not set by the DHCP
# server, but it should not be run by default.
nohook lookup-hostname


Can anyone, please let me know if dhcpcd will support for "Information-request" packet type or not. If yes, how to get the "Information-request" packet type in dhcpcd.
Thanks in advance.

Regards,
Rajesh M P

Follow-Ups:
Re: Whether dhcpcd will support for Information-request packet type?Roy Marples
Archive administrator: postmaster@marples.name