Fork of ipxe; additional commands and features https://git.openslx.org/openslx-ng/ipxe.git/atom/src/net/udp?h=v0.9.5 2008-09-25T00:35:15+00:00 2008-09-25T00:35:15+00:00 Michael Brown 2008-09-25T00:35:15+00:00 urn:sha1:aa8d97258154216896567a901156e7ef4eef399f 2008-08-13T20:51:53+00:00 Michael Brown 2008-08-13T20:51:53+00:00 urn:sha1:a1d0f6ed2e8ad7c04615db405cffb3eec4ae139a The ProxyDHCPREQUEST is a unicast packet, so the first request will almost always be lost due to not having the IP address in the ARP cache. If the minimum retry time is set to one second (as per commit ff2b6a5), then ProxyDHCP will time out and give up before managing to successfully transmit a request. The DHCP timers need to be reworked anyway, so this mild hack is acceptable for now. 2008-08-12T00:05:26+00:00 Andrew Schran 2008-08-12T00:05:26+00:00 urn:sha1:ff2b6a512d7a4f351e48dc9a042099a1010342a3 New min_timeout and max_timeout fields in struct retry_timer allow users of this timer to set their own desired minimum and maximum timeouts, without being constrained to a single global minimum and maximum. Users of the timer can still elect to use the default global values by leaving the min_timeout and max_timeout fields as 0. 2008-08-01T20:49:11+00:00 Michael Brown 2008-08-01T20:49:11+00:00 urn:sha1:ed73d535032c39914b2dbdfeff7259f15938f15b Altiris erroneously cares about the ordering of DHCP options, and will get confused if we don't construct them in the order it expects. This is observed (so far) only when attempting to deploy 64-bit Win2k3. 2008-07-10T03:11:09+00:00 Michael Brown 2008-07-10T03:11:09+00:00 urn:sha1:6f39dfe6c0853f409519279fc1babaf2dc02dc9b Verifying server ID and DHCP transaction ID is insufficient to differentiate between DHCPACK and ProxyDHCPACK when the DHCP server and Proxy DHCP server are the same machine. 2008-07-02T22:01:25+00:00 Michael Brown 2008-07-02T22:01:25+00:00 urn:sha1:227bb05a50f1f15073bd051f2bb5b6d3f7270f2b 2008-07-01T00:56:37+00:00 Michael Brown 2008-07-01T00:56:37+00:00 urn:sha1:fdb8481de1d8e307760d2ff39a7f0c39a9518e7c Perform the same test for a matching DHCP_SERVER_IDENTIFIER on ProxyDHCPACKs as we do for DHCPACKs. Otherwise, a retransmitted DHCPACK can end up being treated as the ProxyDHCPACK. I have a vague and unsettling memory that this test was deliberately omitted, but I can't remember why, and can't find anything in the VC logs. 2008-06-11T12:16:02+00:00 Michael Brown 2008-06-11T12:16:02+00:00 urn:sha1:c3811d4a1339c29254db1ce04810259448840bcc Add the definition of SLAM_MAX_BLOCKS_PER_NACK, which is roughly equivalent to a TCP window size; it represents the maximum number of packets that will be requested in a single NACK. Note that, to keep the code size down, we still limit ourselves to requesting only a single range per NACK; if the missing-block list is discontiguous then we may request fewer than SLAM_MAX_BLOCKS_PER_NACK blocks. 2008-06-11T08:41:31+00:00 Michael Brown 2008-06-11T08:41:31+00:00 urn:sha1:5d36ec6721070e4efe817a853612837535019718 On any fast network, or with any driver that may drop packets (e.g. Infiniband, which has very small RX rings), the traditional usage of the SLAM protocol will result in enormous numbers of packet drops and a consequent large number of retransmissions. By adapting the client behaviour, we can force the server to act more like a multicast TFTP server, with flow control provided by a single master client. This behaviour should interoperate with any traditional SLAM client (e.g. Etherboot 5.4) on the network. The SLAM protocol isn't actually documented anywhere, so it's hard to define either behaviour as compliant or otherwise. 2008-06-11T05:20:49+00:00 Michael Brown 2008-06-11T05:20:49+00:00 urn:sha1:3a2c8a269029495c20b2c660642651a9705ffbb8 A missing test for dhcp->dhcpoffer in dhcp_timer_expired() was causing the client to transition to DHCPREQUEST after timing out on waiting for ProxyDHCP even if no DHCPOFFERs had been received.