<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://ipxe.net/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="https://ipxe.net/feed.php">
        <title>iPXE - open source boot firmware howto</title>
        <description></description>
        <link>https://ipxe.net/</link>
        <image rdf:resource="https://ipxe.net/lib/tpl/doogiestpl/images/favicon.ico" />
       <dc:date>2026-04-15T19:43:11+0000</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://ipxe.net/howto/bisect?rev=1674208779&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/howto/chainloading?rev=1772810448&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/howto/dhcpd?rev=1613238835&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/howto/ec2?rev=1760373219&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/howto/fedora?rev=1731503186&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/howto/flatcar?rev=1740415320&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/howto/gce?rev=1760050652&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/howto/msdhcp?rev=1467802380&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/howto/pcap?rev=1287778308&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/howto/rh_san?rev=1613397938&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/howto/romburning?rev=1382914328&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/howto/sccm?rev=1678970166&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/howto/vmware?rev=1342308978&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/howto/wds_iscsi?rev=1768563790&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/howto/winpe?rev=1661290041&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://ipxe.net/lib/tpl/doogiestpl/images/favicon.ico">
        <title>iPXE - open source boot firmware</title>
        <link>https://ipxe.net/</link>
        <url>https://ipxe.net/lib/tpl/doogiestpl/images/favicon.ico</url>
    </image>
    <item rdf:about="https://ipxe.net/howto/bisect?rev=1674208779&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-01-20T09:59:39+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>howto:bisect</title>
        <link>https://ipxe.net/howto/bisect?rev=1674208779&amp;do=diff</link>
        <description>Finding a bug using git-bisect

git-bisect is a powerful tool for quickly tracking down the precise change that introduced a bug in iPXE.  If you are encountering a problem with the latest version of iPXE, and you know that an older version of iPXE does not have the same problem, then you can use</description>
    </item>
    <item rdf:about="https://ipxe.net/howto/chainloading?rev=1772810448&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-06T15:20:48+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>howto:chainloading</title>
        <link>https://ipxe.net/howto/chainloading?rev=1772810448&amp;do=diff</link>
        <description>Chainloading iPXE

If you have a large number of machines which already have a PXE implementation (such as network cards with an existing Intel PXE ROM), then you may want to avoid having to reflash each machine's network card individually.  You can achieve this by using chainloading.</description>
    </item>
    <item rdf:about="https://ipxe.net/howto/dhcpd?rev=1613238835&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-02-13T17:53:55+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>howto:dhcpd</title>
        <link>https://ipxe.net/howto/dhcpd?rev=1613238835&amp;do=diff</link>
        <description>Using ISC dhcpd

ISC dhcpd is the default DHCP server on most Linux distributions.  It can easily be configured to support iPXE.

ISC dhcpd is configured using the file /etc/dhcpd.conf.  You can instruct iPXE to boot using the filename directive:
  filename &quot;pxelinux.0&quot;;</description>
    </item>
    <item rdf:about="https://ipxe.net/howto/ec2?rev=1760373219&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-10-13T16:33:39+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>howto:ec2</title>
        <link>https://ipxe.net/howto/ec2?rev=1760373219&amp;do=diff</link>
        <description>iPXE in Amazon EC2

You can use iPXE to boot Amazon (AWS) EC2 instances using a public iPXE AMI.  You can use an iPXE script to direct the EC2 instance to boot via any means supported by iPXE.  For example, you could boot a set of diskless EC2 instances using HTTPS or iSCSI from a single server hosted in the same AWS region.</description>
    </item>
    <item rdf:about="https://ipxe.net/howto/fedora?rev=1731503186&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-11-13T13:06:26+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>howto:fedora</title>
        <link>https://ipxe.net/howto/fedora?rev=1731503186&amp;do=diff</link>
        <description>Network-booting Fedora

[Fedora logo]

You can use iPXE to boot into the Fedora Linux installer via HTTP.  You can then install Fedora to a local hard disk or to an iSCSI or FCoE SAN target.

These instructions should work for similar Linux distributions, such as Red Hat Enterprise Linux (RHEL) and</description>
    </item>
    <item rdf:about="https://ipxe.net/howto/flatcar?rev=1740415320&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-02-24T16:42:00+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>howto:flatcar</title>
        <link>https://ipxe.net/howto/flatcar?rev=1740415320&amp;do=diff</link>
        <description>Network-booting Flatcar Linux

[Flatcar logo]

You can use iPXE to boot into Flatcar Container Linux in order to run container payloads.  You can control the behaviour of Flatcar Linux by providing an Ignition configuration file generated by the Butane utility in order to configure networking, register</description>
    </item>
    <item rdf:about="https://ipxe.net/howto/gce?rev=1760050652&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-10-09T22:57:32+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>howto:gce</title>
        <link>https://ipxe.net/howto/gce?rev=1760050652&amp;do=diff</link>
        <description>iPXE in Google Cloud

You can use iPXE to boot Google Cloud Compute Enigne (GCE) instances using a public iPXE image.  You can use an iPXE script to direct the GCE instance to boot via any means supported by iPXE.  For example, you could boot a set of diskless GCE instances using HTTPS or iSCSI from a single server hosted in the same Google Cloud region.</description>
    </item>
    <item rdf:about="https://ipxe.net/howto/msdhcp?rev=1467802380&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2016-07-06T10:53:00+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>howto:msdhcp</title>
        <link>https://ipxe.net/howto/msdhcp?rev=1467802380&amp;do=diff</link>
        <description>Using the Microsoft DHCP server

The Microsoft DHCP server is the default DHCP server on Microsoft Windows.  It can be configured to support iPXE.  It cannot easily be used to support some of the more advanced iPXE options; if you have the choice then you may find it easier to use</description>
    </item>
    <item rdf:about="https://ipxe.net/howto/pcap?rev=1287778308&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-10-22T20:11:48+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>howto:pcap</title>
        <link>https://ipxe.net/howto/pcap?rev=1287778308&amp;do=diff</link>
        <description>Capturing a packet trace

When diagnosing problems, it can be useful to capture a packet trace.  This allows other users to see exactly what is happening on your network, and can greatly reduce the time taken to fix a problem.

How to capture

The easiest way to capture a packet trace is to use</description>
    </item>
    <item rdf:about="https://ipxe.net/howto/rh_san?rev=1613397938&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-02-15T14:05:38+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>howto:rh_san</title>
        <link>https://ipxe.net/howto/rh_san?rev=1613397938&amp;do=diff</link>
        <description>Installing RHEL / CentOS / Fedora to a SAN target

You can use iPXE to install Red Hat Enterprise Linux (RHEL), CentOS and Fedora from a diskless computer directly to an iSCSI or FCoE SAN target.

This tutorial uses CentOS as an example but should work equally well for both RHEL and Fedora.

Creating the installation script</description>
    </item>
    <item rdf:about="https://ipxe.net/howto/romburning?rev=1382914328&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2013-10-27T22:52:08+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>howto:romburning</title>
        <link>https://ipxe.net/howto/romburning?rev=1382914328&amp;do=diff</link>
        <description>Burning iPXE into ROM

For a permanent deployment of iPXE, you can burn it into your network card's expansion ROM, as a replacement for the card's legacy PXE ROM.  Most modern network cards store their expansion ROMs in flash memory, and most manufacturers will provide a utility to allow you to reflash the expansion ROM.</description>
    </item>
    <item rdf:about="https://ipxe.net/howto/sccm?rev=1678970166&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-03-16T12:36:06+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>howto:sccm</title>
        <link>https://ipxe.net/howto/sccm?rev=1678970166&amp;do=diff</link>
        <description>Booting SCCM via HTTP

System Center Configuration Manager (SCCM), formerly known as Systems Management Server (SMS), is a Microsoft product used to deploy and manage large groups of Windows computers.  If you are using iPXE, then you can boot an SCCM client using HTTP, which is much faster and more reliable than the default TFTP protocol.  Over a Gigabit Ethernet network, a typical 200MB SCCM image should download in less than two seconds.</description>
    </item>
    <item rdf:about="https://ipxe.net/howto/vmware?rev=1342308978&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-07-14T23:36:18+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>howto:vmware</title>
        <link>https://ipxe.net/howto/vmware?rev=1342308978&amp;do=diff</link>
        <description>Using iPXE in VMware

You can replace the default VMware PXE ROM with an iPXE ROM, which will enable you to boot your virtual machine via HTTP, iSCSI, AoE, or any other protocol supported by iPXE.

Selecting the network adapter

VMware is capable of emulating several network adapters:</description>
    </item>
    <item rdf:about="https://ipxe.net/howto/wds_iscsi?rev=1768563790&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-01-16T11:43:10+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>howto:wds_iscsi</title>
        <link>https://ipxe.net/howto/wds_iscsi?rev=1768563790&amp;do=diff</link>
        <description>Installing to an iSCSI target using WDS

Windows Deployment Services (WDS) is the component of Windows Server that allows you to install Windows over the network.  If you are using iPXE, then you can use Windows Deployment Services to install Windows Server 2008, Windows Server 2012, Windows 7, Windows 8, or Windows 10 directly to an iSCSI target on your network.</description>
    </item>
    <item rdf:about="https://ipxe.net/howto/winpe?rev=1661290041&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-08-23T21:27:21+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>howto:winpe</title>
        <link>https://ipxe.net/howto/winpe?rev=1661290041&amp;do=diff</link>
        <description>Network-booting Windows PE

Windows PE (WinPE) is the Windows Preinstallation Environment, used for installation and repair of Windows computers.

Using iPXE and wimboot, you can boot into Windows PE via HTTP.  You can then connect to a standard Windows file server to install a full version of Windows to the local hard disk (or to an iSCSI target).</description>
    </item>
</rdf:RDF>
