RTEMS / Packages / Legacy Networking

Go to Issues or rtems/pkg/rtems-net-legacy-merges

Merge Requests Summary

Issues

18 - DHCP request includes host name option even if hostname is zero length (opened)

Id

18

State

opened

Type

ISSUE

Author

Trac Migrate

Assignee(s)

Trac Migrate

Created

2018-10-27T19:57:18.000Z

Updated

2025-09-19T01:45:34.545Z

Milestone

5.4

Labels

network::legacy, priority::normal, tickettype::defect, version::5

Link

https://gitlab.rtems.org/rtems/pkg/rtems-net-legacy/-/issues/18

Merges

0

Original author: Sal

DHCP requests add the hostname option in dhcp_request_req() without checking its length, so the hostname can be of any length. This is a defect because the DHCP spec (​https://tools.ietf.org/html/rfc2132) requires the hostname to have a minimum length of 1 char. This appears to trigger a bug in a specific Netgear router that causes it’s DHCP process to lock up and could affect other things as well.

This bug can be solved applying the patch made by Aun-Ali Zaidi in the original ticket reporting this defect (​https://devel.rtems.org/ticket/1405) that was never applied. I’ve been able to compile the code with the patch applied and it didn’t raise any warnings.

Original ticket: ​https://devel.rtems.org/ticket/1405

Author: Kinsey Moore

2025-01-31T18:25:05.267Z

assigned to @tracmigrate

Author: Trac Migrate

2018-11-13T22:52:26.000Z

Original author: Sal

Patch to check the length of the hostname, therefore to solve the bug.

Author: Kinsey Moore

2025-01-31T18:25:05.983Z

moved from rtems/rtos/rtems#3574

Author: Chris Johns

2025-09-19T01:45:34.619Z

changed the description