A patch to support additional parameter passing via DHCP

[Ric Claus]

This set of modifications was produced a few years ago and I am not the author. However, they provide additional functionality to the basic DHCP support in RTEMS, which I figure someone else might find useful. If this appears to be of interest, we would welcome its being incorporated into RTEMS.

[Ric Claus]

DHCP parameter passing patch

[Ric Claus]

Replying to comment:2:

The addition of vendor options with a callback is nice. I do have some
questions.

1. The call dhcp_init has changed and I suspect this could break existing user

code. Should the dhcp_init call remain the same a new call added, eg
dhcp_init_ex or dhcp_init_vendor ?

Yes, on the face of it, I would agree. Perhaps dhcp_init could be a jacket around dhcp_init_ex...

2.
​https://www.rtems.org/bugzilla/attachment.cgi?id=1438&action=diff#a/cpukit/libnetworking/rtems/rtems_dhcp.c_sec24
: What are the '& 1' and '& 2' bits handling ? I would rather see define labels
for the bits.

Did you mean at here?
​https://www.rtems.org/bugzilla/attachment.cgi?id=1438&action=diff#a/cpukit/libnetworking/rtems/rtems_dhcp.c_sec31

Yes, Iagree, but would have to look into it. However, it's that way in the original, if we're talking about the same thing.

3.
​https://www.rtems.org/bugzilla/attachment.cgi?id=1438&action=diff#a/cpukit/libnetworking/rtems/rtems_dhcp.c_sec37
: Is this a new feature to handle more interfaces ?

Yes, that's what we used it for. I can provide example usage code and dhcp.conf snipptes, if you're interested.