[Bug 1229458] Re: grubnetx64.efi tftp client does not work over ipv6

[Mike Pontillo]

I'm curious if there is any change in behavior when using a hostname
that resolves to a AAAA record instead of an IP address. Browsing the
grub source code, it looks like if it has an IP address, it assumes IPv4
and generates that (tftp,x.x.x.x) string you saw.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/1229458

Title:
  grubnetx64.efi tftp client does not work over ipv6

Status in grub2 package in Ubuntu:
  Confirmed

Bug description:
  Testing using the pre-built grubnetx64.efi, I am not able to use the
  tftp client support within grub2 to load configs (/kernels/initrds)
  over the network.  This works fine if using IPv4.

  grubnetx64.efi is being loaded over the network (via shim no less), so
  the firmware's network stack is definitely up and working.  But when
  grub tries to load grub.cfg via the default path, it fails with:

    error: couldn't send network packet.

  This message is repeated, approximately once every three seconds.  It
  looks to be an infinite loop; at least, the message is repeated more
  than 100 times.  But sometimes, when I've not been paying close
  attention to the boot, I get a grub shell instead.  In that case, the
  grub shell shows:

  grub> echo $root
  tftp,0.5.0.24
  grub> set
  [...]
  net_default_server=
  net_efinet2_boot_file=8:23f::2]/bootx64.efi
  net_efinet2_ip=0.0.0.0
  net_efinet2_mac=02:3f:00:00:00:00
  [...]
  prefix=(tftp,0.5.0.24)/grub
  pxe_default_server=
  root=tftp,0.5.0.24
  [...]
  grub>

  The actual server IP is 2001:1938:23f::2.

  I've booted a locally-generated (self-signed) grubnetx64.efi with
  grub-bootstrap.cfg modified to call 'set' first, and I get identical
  output for all of the network-related variables.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1229458/+subscriptions