`ip=` for IPv6

[SchoolGuy]

I believe this is a bug report, but maybe it is a feature request.

When attempting to use an IPv6 network with Fireactions (https://github.com/hostinger/fireactions), the chosen IPv6 address is not enclosed in square brackets, resulting in an incorrect configuration.

According to https://dracut-ng.github.io/dracut-ng/man/dracut.cmdline.7.html#_network, IPv6 addresses have to be put into square brackets.

Sadly, https://docs.kernel.org/admin-guide/nfs/nfsroot.html says nothing about the format of the ip= parameter that would help with the syntax of the IP address, but I guess that we need square brackets since this is the delimiter for the ip= parameter.

Since I am not an expert, I wanted to ask/discuss what the best way forward is. My best guess is that a patch is needed for vmconf.go for the method IPBootParam. Is this enough or even the right place?

[Shubhranshu153]

Hi @SchoolGuy ,

Reading the codebase ipv6 is not supported as part firecracker go sdk networking stack. So its more like a feature request.

firecracker-go-sdk/network.go

Line 528 in ed6ff32

return fmt.Errorf("invalid ip, only ipv4 addresses are supported: %+v", ip)

[SchoolGuy]

@Shubhranshu153 Actually thanks to a colleague we got it working. :)

Edit: I'll explain once I am in the office.

[SchoolGuy]

After talking to a few colleagues who are knowledgeable in the Linux Kernel Networking stack, it seems that the ip= parameter doesn't support IPv6 itself. However, that can be fixed with either using an initrd (undesired because slow) or just letting the userspace set up networking (aka network manager). With a small patch from one of the aforementioned colleagues and a small userspace script, it is possible to make this fully work.

This, of course, is not upstream, and I would love to get this to work without patches. So, in summary, this is indeed a feature request.