Packet fully supports netboot.xyz with its Custom iPXE operating system.
Select the “Custom iPXE” operating system from the portal, or the
slug when using the API.
Put the netboot.xyz URL in the text field that appears in the portal, or use the
ipxe_script_url parameter when creating the device via the API.
Press “Deploy” to provision your device. It will take 2-3 minutes for the device
to become active. Once it’s online, connect to Packet’s out-of-band serial-over-SSH
service (S.O.S.) using the device’s
id and the facility where the device was
The current list of facilities is here. The netboot.xyz iPXE menu will appear and you can complete installation from there.
Please Note: By default, devices are set to boot from the local disk. During provisioning, Packet sets the next boot to PXE. This happens once, which means that if you don’t install an operating system before rebooting, it won’t reload the netboot.xyz menu. However, you can set your device to always boot to iPXE first by enabling that option under ‘server actions’ through the customer portal.
Devices that are provisioned via Custom iPXE will be able to DHCP for the life of the device; however, Packet recommends configuring networking statically. IP address information can be found by querying https://metadata.packet.net/metadata from the host.
More information on how Packet configures bonding can be found here.
Nameservers should be configured as:
nameserver 220.127.116.11 nameserver 18.104.22.168