<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openslx-ng/ipxe.git/src/net, branch v0.9.4</title>
<subtitle>Fork of ipxe; additional commands and features</subtitle>
<id>https://git.openslx.org/openslx-ng/ipxe.git/atom/src/net?h=v0.9.4</id>
<link rel='self' href='https://git.openslx.org/openslx-ng/ipxe.git/atom/src/net?h=v0.9.4'/>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/'/>
<updated>2008-09-25T00:35:15+00:00</updated>
<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>[iscsi] Change default initiator name prefix to "iqn.2000-01.org.etherboot:"</title>
<updated>2008-09-19T16:46:07+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2008-09-19T16:46:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=0e408658b9139c346b684d08134111fbc8159ca0'/>
<id>urn:sha1:0e408658b9139c346b684d08134111fbc8159ca0</id>
<content type='text'>
The domain etherboot.org was actually registered on 2000-01-09, not
2000-09-01.  (To put it another way, it was registered on 1/9/2000 (US
date format) rather than 1/9/2000 (sensible date format); this may
illuminate the cause of the error.)

"iqn.2000-09.org.etherboot:" is still valid as per RFC3720, but may be
surprising to users, so change it to something less unexpected.

Thanks to the anonymous contributor for pointing this one out.
</content>
</entry>
<entry>
<title>[undi] Fill in ProtType correctly in PXENV_UNDI_ISR</title>
<updated>2008-08-20T02:21:37+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2008-08-20T02:21:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=30fb3b3810409a4971adf9abf00e0842f88d87d8'/>
<id>urn:sha1:30fb3b3810409a4971adf9abf00e0842f88d87d8</id>
<content type='text'>
Determine the network-layer packet type and fill it in for UNDI
clients.  This is required by some NBPs such as emBoot's winBoot/i.

This change requires refactoring the link-layer portions of the
gPXE netdevice API, so that it becomes possible to strip the
link-layer header without passing the packet up the network stack.
</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>[iSCSI] Add support for mutual CHAP</title>
<updated>2008-08-11T02:43:12+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2008-08-11T02:12:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=5d4839b577e6b6836bd4828ab3ab5d7d2f5ae779'/>
<id>urn:sha1:5d4839b577e6b6836bd4828ab3ab5d7d2f5ae779</id>
<content type='text'>
Allow initiator to verify target authentication using CHAP.
</content>
</entry>
<entry>
<title>[pxe] If no ProxyDHCPACK exists, use DHCPACK for the fake ProxyDHCPACK packet</title>
<updated>2008-08-02T02:03:42+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2008-08-02T02:03:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=f178436bb1be3cb312e9904da89ab42ccb3a976b'/>
<id>urn:sha1:f178436bb1be3cb312e9904da89ab42ccb3a976b</id>
<content type='text'>
WinPE seems to have a bug that causes it to always use the TFTP server
IP address and filename from the ProxyDHCPACK packet, even if the
ProxyDHCPACK packet doesn't exist.  This causes it to end up
attempting to fetch a file such as

  tftp://0.0.0.0/bootmgr.exe

If we don't have a ProxyDHCPACK to use, we pretend that it was a copy
of the DHCPACK packet.  This works around the problem, and hopefully
won't surprise any NBPs.
</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>[ftp] Terminate processing after receiving an error</title>
<updated>2008-07-30T19:27:09+00:00</updated>
<author>
<name>Sergey Vlasov</name>
</author>
<published>2008-07-30T19:27:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=e6cd16946a2c52f39d3ea308ab1fb80a85c9d0a3'/>
<id>urn:sha1:e6cd16946a2c52f39d3ea308ab1fb80a85c9d0a3</id>
<content type='text'>
When an error reply (not 1xx, 2xx or 3xx) was received, ftp_reply()
invoked ftp_done() to close connections, but did not return, and the
rest of code in this function could try to send commands to the closed
control connection.

Signed-off-by: Sergey Vlasov &lt;vsu@altlinux.ru&gt;
</content>
</entry>
<entry>
<title>[ftp] Cope with RETR completion prior to all data received</title>
<updated>2008-07-30T19:22:49+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2008-07-30T19:22:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=8f4c2b4a4c5c3a3d29a102a758e75b65cadf9946'/>
<id>urn:sha1:8f4c2b4a4c5c3a3d29a102a758e75b65cadf9946</id>
<content type='text'>
Based on a patch contributed by Sergey Vlasov &lt;vsu@altlinux.ru&gt; :

  In my testing with "qemu -net user" the 226 response to RETR was
  often received earlier than final packets of the data connection;
  this caused the received file to become truncated without any error
  indication.  Fix this by adding an intermediate state FTP_TRANSFER
  between FTP_RETR and FTP_QUIT, so that the transfer is considered to
  be complete only when both the end of data connection is encountered
  and the final reply to the RETR command is received.
</content>
</entry>
</feed>
