Discussed in #1355
Originally posted by NiKiZe December 5, 2024
Observed behaviour
When booting in UEFI with IPv6 no IP is seen in the boot path, no cwurl can be created and no autoexec.ipxe attempt is done.
Is this just a boot path thing in the firmware I have used, or is it something that maybe haven't been tested?
Could the firmware issues somehow be mitigated if dhcpcache supported dhcpv6?
I would like to have given more details and tested more, but my environment just doesn't want to play nice today.
This was seen while documenting IPv6 boot, notes at
https://gist.github.com/NiKiZe/3da6bbc9bd54c79645d833b9ed271ef9
Other example from the discussion:
dhcp4:
dhcp6:
dhcp6, with following script embedded:
#!ipxe
dhcp -c ipv6
chain --replace --autofree tftp://[2001:912:1480:310:2400::1]/autoexec.ipxe
Note: this is real hardware, not a VM.
Discussed in #1355
Originally posted by NiKiZe December 5, 2024
Observed behaviour
When booting in UEFI with IPv6 no IP is seen in the boot path, no cwurl can be created and no autoexec.ipxe attempt is done.
Is this just a boot path thing in the firmware I have used, or is it something that maybe haven't been tested?
Could the firmware issues somehow be mitigated if dhcpcache supported dhcpv6?
I would like to have given more details and tested more, but my environment just doesn't want to play nice today.
This was seen while documenting IPv6 boot, notes at
https://gist.github.com/NiKiZe/3da6bbc9bd54c79645d833b9ed271ef9
Other example from the discussion:
dhcp4:
dhcp6:
dhcp6, with following script embedded:
Note: this is real hardware, not a VM.