Legacy Networking | dhcp request includes host name option even if hostname is zero length. (#13)

[Trac Migrate (@tracmigrate)]

Trac Migrate created an issue: https://gitlab.rtems.org/rtems/pkg/rtems-net-legacy/-/issues/13

Assignee: Trac Migrate

Original author: timcussins

DHCP requests add the hostname option in dhcp_request_req() - this is cool, except that the dhcp spec requires that this option has a length >= 1 char.

http://www.networksorcery.com/enp/rfc/rfc2132.txt

3.14. Host Name Option

<snip>
The code for this option is 12, and its minimum length is 1.
</snip>

At present, the hostname is added regardless. This appears to trigger a bug in a specific Netgear router that causes it's dhcp process to lock up.

* [0001-libnetworking-rtems_dhcp.c-Fix-improper-hostname-han.2.patch](/assets/tracmigration/ticket_attachments/0001-libnetworking-rtems_dhcp.c-Fix-improper-hostname-han.2.patch)
* [0001-libnetworking-rtems_dhcp.c-Fix-improper-hostname-han.patch](/assets/tracmigration/ticket_attachments/0001-libnetworking-rtems_dhcp.c-Fix-improper-hostname-han.patch)
* [dhcp_hostname_option.patch](/assets/tracmigration/ticket_attachments/dhcp_hostname_option.patch)


-- 
View it on GitLab: https://gitlab.rtems.org/rtems/pkg/rtems-net-legacy/-/issues/13
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20250131/5064477b/attachment.htm>