the TCP/IP protocol suite (rather than being general transport-layer
functions).

if the application wants to send data then it will have to use the normal
senddata() mechanism.

all servers.

there doing nothing when it's actually waiting for a DHCP reply.

concept demo that actually does something useful.

Parameter request list is yet another option that ISC dhcpd ignores
unless it's in the main options block.

Fix logic error in parsing file and sname fields.

default test to the DHCP test.

Added test code to configure the interface for IPv4 after DHCP.

cycle.  :)

doesn't seem to be required by the RFCs, but at least ISC dhcpd and
ethereal refuse to recognise it otherwise.

packets.

against value in header.

Temporarily disable RX checksumming; it's broken and is holding up
work on higher-layer protocols
.

(apart from the bad UDP checksum).

a pointer).

Use pkb_available() rather than pkb_len() (which will always return 0
on a freshly allocated buffer).

udp_send() should assume that the buffer has already been allocated.

functions that return status codes.

Zero the DHCP packet buffer *before* creating the options structures
inside it.

parsed DHCP responses.

1. Updated UDP send data code\
2. Corrected internet checksum\
3. Moved udp_buffer() and udp_buflen() to udp.c from udp.h

structure, and populating it with options.  This should allow us to
use the same basic options list for both DHCPDISCOVER and DHCPREQUEST,
plus making it much easier to set the non-constant parameters
(e.g. requested IP address) in request packets.

to search through all registered option blocks.

Move some static inlines that are likely to be used frequently into
dhcpopts.c as normal functions, to save space.

by SSL servers. Framework.c allows me to test the library against a given
https server.

derived is a 16-bit big-endian field, but htype is only 8 bits wide.

is a DHCP option" data structures.

We need this code in order to be able to return a DHCP packet to a PXE NBP
which reflects options from our multiple sources (e.g. NVS and DHCP
server).  This is expensive, but necessary.  Having paid this cost, we may
as well try to use the same code to generate our DHCP request packets,
since the process is similar.