Is there a Linux kernel boot parameter to configure an IPv6 address?
Solution 1
Sorry, but if you want this, you'll have to build it yourself, or more likely, reuse someone else's implementation.
The ip=
command line option you've been using is actually part of the kernel's boot code for mounting an NFS root filesystem. It has never been extended for IPv6, and there is no kernel boot parameter for configuring IPv6 at boot time.
That said, some Linux distributions such as Red Hat have implemented their own ipv6=
boot parameter for their installation media. You may be able to reuse this code in your custom initramfs.
Solution 2
According to Fedora, the ip= parameter can be used with IPv4 or IPv6 addresses. IPv6 addresses must be enclosed in square brackets. If you need both, you can use multiple ip= options on the kernel line as in:
... ip=[2001:db8::dead:beef]::[2001:db8::cafe:babe]:64::eth0:none ip=192.0.2.5::192.0.2.1:255.255.255.0::eth0:none ...
Solution 3
All your boot parameters are available via /proc/cmdline after boot. So, you can just set up all needed options via custom mkinitcpio hook, which would parse cmdline in search for specific param. You can use ipv6= like ip= one.
Related videos on Youtube
aef
Erisian pope, Free software advocate, Domain-driven organization/software architect, Elixir/Ruby programmer, GNU/Linux administrator, Scrum/Nexus master, GDPR data protection officer, Gamer
Updated on September 18, 2022Comments
-
aef almost 2 years
I know there is a parameter named
ip
which lets you configure IPv4 addresses on the Linux kernel through the boot loader. That looks like the following:ip=192.0.2.1::192.0.2.62:255.255.255.192::eth0:none
I'm looking for an equal parameter for IPv6 configuration. I couldn't find anything about this in the kernel documentations.
Update: Because of a lot of you asked why I would need this: The idea to use a kernel configuration came up related to this problem. I suspect the regular boot-up interface configuration is not done, because the interfaces are already up. The reason for this could be that I'm using a pre-boot environment with a Dropbear SSH server to allow me to unlock my encrypted root partition. The IP addresses for this environment are configured through GRUB with the
ip=
parameter. There is no DHCP or Router Advertisement available on that Ethernet segment and as this is the uplink segment provided by a large hosting company, there is no way to change that fact. -
aef over 11 yearsYeah. I could build it myself, but that was not what I'm looking for. Still thanks for the idea.
-
kasperd about 9 yearsThis answer is contradicting the accepted answer. This may be due to the accepted answer being outdated. To remove any doubt about which answer is correct, it would be a good idea to include a link to the source of this information.
-
aef almost 9 yearsThis is probably an evolution of the thing RedHat implemented, which was mentioned in Michael Hampton's answer. I tested it in Debian Jessie and it didn't work. I am still looking for a generic Linux way to do it.