The client half of the private BOOTP pair — where the machine being installed receives its boot reply.
IANA registers 1068 as instl-bootc (formerly instl_bootc), the client-side counterpart to 1067. In HP's Ignite-UX the booting client sends from and receives on 1068 while the server's instl_bootd answers from 1067, mirroring the standard BOOTP 67/68 relationship on a private port pair so installation traffic stays isolated from the site's DHCP. As with 1067, live traffic is UDP; the TCP registration is bookkeeping. On a host scan, seeing 1068 bound is normally a machine mid-provision or an Ignite-UX client daemon left running.
Do not expose
Part of an unauthenticated OS-provisioning exchange — keep the whole 1067/1068 pair inside the provisioning network.
$ sudo tcpdump -ni any udp port 1068Seen this on your network? Beige Box scans your Wi-Fi and shows every open port on every device — and its Ports tool links straight back here.
Get Beige Box →also available as JSON · Markdown
Corrections or a missing port? Reply @rimrocksystems.