https://ipxe.net/ 2026-04-30T03:07:25+0000 https://ipxe.net/ https://ipxe.net/lib/tpl/doogiestpl/images/favicon.ico text/html 2013-07-15T20:59:30+0000 Anonymous (anonymous@undisclosed.example.com) https://ipxe.net/dev/drvtest/dhcp?rev=1373921970&do=diff Driver test: basic DHCP Rationale Obtaining an IPv4 address via DHCP is probably the simplest test of the complete transmit and receive datapath. This test should therefore be attempted before any of the more complex datapath tests. [A network card] Test sequence text/html 2013-07-15T20:59:06+0000 Anonymous (anonymous@undisclosed.example.com) https://ipxe.net/dev/drvtest/link?rev=1373921946&do=diff Driver test: link detection Rationale Users expect link state errors to be reported as such, rather than having to be inferred from DHCP timeouts etc. Drivers should therefore update the link state in response to external link up and link down events (e.g. disconnecting or reconnecting a network cable). text/html 2013-07-15T21:01:00+0000 Anonymous (anonymous@undisclosed.example.com) https://ipxe.net/dev/drvtest/linkresume?rev=1373922060&do=diff Driver test: link interruption Rationale Downloading a large file via HTTP provides an opportunity to test the ability of the card to cope with a temporary link loss. [A network card] Preparation Create a 512MB file containing pseudo-random data, using e.g.: dd if=/dev/urandom of=512mb bs=1M count=512 text/html 2013-04-03T15:03:21+0000 Anonymous (anonymous@undisclosed.example.com) https://ipxe.net/dev/drvtest/loopback?rev=1365001401&do=diff Driver test: loopback Rationale The lotest command allows the correct operation of both the receive and transmit datapaths to be verified independently under high packet load and with no dependency on external servers or network components. Additionally, it is one of the few tests capable of detecting whether or not the receive datapath is correctly stripping the CRC. text/html 2013-07-15T21:00:19+0000 Anonymous (anonymous@undisclosed.example.com) https://ipxe.net/dev/drvtest/md5sum?rev=1373922019&do=diff Driver test: large file transfer correctness Rationale Downloading a large file via HTTP provides an easy test of the complete transmit and receive datapath under a sustained high packet load. The md5sum and sha1sum commands can be used to verify that a file was downloaded correctly. text/html 2013-04-03T15:22:59+0000 Anonymous (anonymous@undisclosed.example.com) https://ipxe.net/dev/drvtest/mtuloopback?rev=1365002579&do=diff Driver test: high-MTU loopback Rationale To support operation as a VLAN trunk device, drivers should be able to support a frame size of 1518 bytes (excluding the Ethernet CRC), which corresponds to an MTU of 1504 bytes. The lotest command allows an arbitrary MTU to be specified, and so can easily be used to test operation with an MTU of 1504. text/html 2013-07-15T20:59:52+0000 Anonymous (anonymous@undisclosed.example.com) https://ipxe.net/dev/drvtest/reopen?rev=1373921992&do=diff Driver test: close and reopen Rationale Closing and reopening an interface is an uncommon action, and problems are unlikely to be discovered during normal operation. The ifclose commands can be used to verify that a card continues to work after being closed and reopened. text/html 2013-07-15T21:00:40+0000 Anonymous (anonymous@undisclosed.example.com) https://ipxe.net/dev/drvtest/speed?rev=1373922040&do=diff Driver test: large file transfer speed Rationale Downloading a large file via HTTP provides an easy test of the complete transmit and receive datapath under a sustained high packet load. The time command can be used to verify that the expected throughput was maintained during the download. text/html 2021-01-23T11:36:30+0000 Anonymous (anonymous@undisclosed.example.com) https://ipxe.net/dev/drvtest/undiapi?rev=1611401790&do=diff Driver test: UNDI API Rationale iPXE normally operates in polling mode with interrupts disabled. Drivers may choose to support the use of interrupts, but this is not required. Interrupt-based operation can be tested by using iPXE to boot into the text/html 2013-07-15T11:59:56+0000 Anonymous (anonymous@undisclosed.example.com) https://ipxe.net/dev/drvtest/vlanloopback?rev=1373889596&do=diff Driver test: VLAN loopback Rationale iPXE expects network cards to provide transparent transmit and receive datapaths. Some network cards provide no way to disable their VLAN offload features and will always strip the VLAN tag from a received packet, reporting this tag via the receive descriptor. Drivers for such cards must use special handling to deliver the received packet directly to the appropriate VLAN device.