<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openslx-ng/ipxe.git/src/net/udp, branch v0.9.6</title>
<subtitle>Fork of ipxe; additional commands and features</subtitle>
<id>https://git.openslx.org/openslx-ng/ipxe.git/atom/src/net/udp?h=v0.9.6</id>
<link rel='self' href='https://git.openslx.org/openslx-ng/ipxe.git/atom/src/net/udp?h=v0.9.6'/>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/'/>
<updated>2008-11-19T19:33:05+00:00</updated>
<entry>
<title>[x86_64] Fix assorted 64-bit compilation errors and warnings</title>
<updated>2008-11-19T19:33:05+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2008-11-19T19:33:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=0ebbbb95fa03622423154a3e56251dd58832654d'/>
<id>urn:sha1:0ebbbb95fa03622423154a3e56251dd58832654d</id>
<content type='text'>
Remove various 32-bit assumptions scattered throughout the codebase.
The code is still not necessarily 64-bit clean, but will at least
compile.
</content>
</entry>
<entry>
<title>[settings] Add the notion of a "tag magic" to numbered settings</title>
<updated>2008-10-30T21:47:14+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2008-10-29T18:17:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=0a6c66a83018c64d961ee4e8601ae8950cbee00b'/>
<id>urn:sha1:0a6c66a83018c64d961ee4e8601ae8950cbee00b</id>
<content type='text'>
Settings can be constructed using a dotted-decimal notation, to allow
for access to unnamed settings.  The default interpretation is as a
DHCP option number (with encapsulated options represented as
"&lt;encapsulating option&gt;.&lt;encapsulated option&gt;".

In several contexts (e.g. SMBIOS, Phantom CLP), it is useful to
interpret the dotted-decimal notation as referring to non-DHCP
options.  In this case, it becomes necessary for these contexts to
ignore standard DHCP options, otherwise we end up trying to, for
example, retrieve the boot filename from SMBIOS.

Allow settings blocks to specify a "tag magic".  When dotted-decimal
notation is used to construct a setting, the tag magic value of the
originating settings block will be ORed in to the tag number.
Store/fetch methods can then check for the magic number before
interpreting arbitrarily-numbered settings.
</content>
</entry>
<entry>
<title>[tftp] Add EUNIQ_xx values to differentiate the many EINVAL errors</title>
<updated>2008-10-21T22:00:13+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2008-10-21T22:00:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=cbf9003d665577ab637b122929ce1f21e71418c4'/>
<id>urn:sha1:cbf9003d665577ab637b122929ce1f21e71418c4</id>
<content type='text'>
</content>
</entry>
<entry>
<title>[dhcp] Accept BOOTP as well as DHCP</title>
<updated>2008-09-25T00:35:15+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2008-09-25T00:35:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=aa8d97258154216896567a901156e7ef4eef399f'/>
<id>urn:sha1:aa8d97258154216896567a901156e7ef4eef399f</id>
<content type='text'>
</content>
</entry>
<entry>
<title>[dhcp] Do not restrict minimum retry time for ProxyDHCPREQUEST</title>
<updated>2008-08-13T20:51:53+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2008-08-13T20:51:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=a1d0f6ed2e8ad7c04615db405cffb3eec4ae139a'/>
<id>urn:sha1:a1d0f6ed2e8ad7c04615db405cffb3eec4ae139a</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>[retry] Added configurable timeouts to retry timer</title>
<updated>2008-08-12T00:05:26+00:00</updated>
<author>
<name>Andrew Schran</name>
</author>
<published>2008-08-12T00:05:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=ff2b6a512d7a4f351e48dc9a042099a1010342a3'/>
<id>urn:sha1:ff2b6a512d7a4f351e48dc9a042099a1010342a3</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>[dhcp] Work around a bug in Altiris RDP</title>
<updated>2008-08-01T20:49:11+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2008-08-01T20:49:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=ed73d535032c39914b2dbdfeff7259f15938f15b'/>
<id>urn:sha1:ed73d535032c39914b2dbdfeff7259f15938f15b</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>[dhcp] Verify DHCP server source port</title>
<updated>2008-07-10T03:11:09+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2008-07-10T03:11:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=6f39dfe6c0853f409519279fc1babaf2dc02dc9b'/>
<id>urn:sha1:6f39dfe6c0853f409519279fc1babaf2dc02dc9b</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>[tftp] Strip the initial '/' to keep Windows TFTP servers happy.</title>
<updated>2008-07-02T22:01:25+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2008-07-02T22:01:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=227bb05a50f1f15073bd051f2bb5b6d3f7270f2b'/>
<id>urn:sha1:227bb05a50f1f15073bd051f2bb5b6d3f7270f2b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>[dhcp] Verify server identifier on ProxyDHCPACKs</title>
<updated>2008-07-01T00:56:37+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2008-07-01T00:56:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=fdb8481de1d8e307760d2ff39a7f0c39a9518e7c'/>
<id>urn:sha1:fdb8481de1d8e307760d2ff39a7f0c39a9518e7c</id>
<content type='text'>
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.
</content>
</entry>
</feed>
