Most Linux distributions ship with IPv6 enabled by default. That works fine until it does not. Legacy applications that choke on IPv6 addresses, VPN tunnels that only handle IPv4, or troubleshooting scenarios where you need a clean IPv4-only stack that don’t handle dual-stack networking, troubleshooting DNS resolution issues, or hardening a server that only needs IPv4 connectivity. This guide covers every method to disable IPv6 on Ubuntu 24.04\/22.04 and Rocky Linux 10\/AlmaLinux 10, from temporary runtime changes to permanent kernel-level configuration.<\/p>\n\n\n\n
Each method has trade-offs. Runtime sysctl changes are instant but lost on reboot. Persistent sysctl files survive reboots but can be overridden by NetworkManager. GRUB kernel parameters are the most bulletproof approach since IPv6 never loads in the first place. Pick the method that fits your use case.<\/p>\n\n\n\n
You need root or sudo access on your Linux system. These instructions are tested on:<\/p>\n\n\n\n
The commands work on other distributions in the same families (Debian 13\/12, RHEL 10, Fedora 42) with no changes.<\/p>\n\n\n\n
Before making changes, confirm whether IPv6 is currently active on your system. Run this command to check the kernel parameter:<\/p>\n\n\n\n
cat \/proc\/sys\/net\/ipv6\/conf\/all\/disable_ipv6<\/code><\/pre>\n\n\n\nA value of 0<\/code> means IPv6 is enabled. A value of 1<\/code> means it is disabled.<\/p>\n\n\n\nYou can also check for active IPv6 addresses on your interfaces:<\/p>\n\n\n\n
ip -6 addr show<\/code><\/pre>\n\n\n\nIf you see inet6<\/code> addresses listed (other than ::1<\/code> on loopback), IPv6 is active and in use.<\/p>\n\n\n\nMethod 1: Disable IPv6 Temporarily with sysctl (Runtime Only)<\/h2>\n\n\n\n
This method disables IPv6 immediately without a reboot, but the change is lost when the system restarts. It is useful for quick testing or troubleshooting.<\/p>\n\n\n\n
Disable IPv6 on all network interfaces:<\/p>\n\n\n\n
sudo sysctl -w net.ipv6.conf.all.disable_ipv6=1\nsudo sysctl -w net.ipv6.conf.default.disable_ipv6=1<\/code><\/pre>\n\n\n\nThe kernel applies the change instantly. Verify it took effect:<\/p>\n\n\n\n
cat \/proc\/sys\/net\/ipv6\/conf\/all\/disable_ipv6<\/code><\/pre>\n\n\n\nThe output should show 1<\/code>, confirming IPv6 is now disabled.<\/p>\n\n\n\nYou can also confirm no IPv6 addresses remain on your interfaces:<\/p>\n\n\n\n
ip -6 addr show<\/code><\/pre>\n\n\n\nThis should return empty output or only show the loopback address. Remember, this change reverts after a reboot. For a persistent solution, use Method 2 or Method 3.<\/p>\n\n\n\n
Method 2: Disable IPv6 Permanently via sysctl Configuration<\/h2>\n\n\n\n
Creating a sysctl configuration file makes the IPv6 disable setting persist across reboots. This is the most common approach for servers that need IPv4 only.<\/p>\n\n\n\n
Create a new sysctl configuration file:<\/p>\n\n\n\n
sudo vi \/etc\/sysctl.d\/70-disable-ipv6.conf<\/code><\/pre>\n\n\n\nAdd the following lines:<\/p>\n\n\n\n
net.ipv6.conf.all.disable_ipv6 = 1\nnet.ipv6.conf.default.disable_ipv6 = 1\nnet.ipv6.conf.lo.disable_ipv6 = 1<\/code><\/pre>\n\n\n\nSave the file and apply the settings without rebooting:<\/p>\n\n\n\n
sudo sysctl --system<\/code><\/pre>\n\n\n\nYou should see your settings being applied in the output. Verify the change:<\/p>\n\n\n\n
sysctl net.ipv6.conf.all.disable_ipv6<\/code><\/pre>\n\n\n\nThe output should confirm the value is set to 1<\/code>:<\/p>\n\n\n\nnet.ipv6.conf.all.disable_ipv6 = 1<\/code><\/pre>\n\n\n\nImportant note for NetworkManager systems<\/h3>\n\n\n\n
On systems running NetworkManager (default on Rocky Linux 10, AlmaLinux 10, and Ubuntu desktop), NetworkManager can re-enable IPv6 on managed interfaces even after setting the sysctl parameter. To prevent this, also disable IPv6 in NetworkManager for each connection.<\/p>\n\n\n\n
List your active connections:<\/p>\n\n\n\n
nmcli connection show --active<\/code><\/pre>\n\n\n\nThen disable IPv6 on the connection (replace ens18<\/code> with your actual connection name):<\/p>\n\n\n\nsudo nmcli connection modify ens18 ipv6.method disabled\nsudo nmcli connection up ens18<\/code><\/pre>\n\n\n\nThis ensures NetworkManager won’t override your sysctl settings.<\/p>\n\n\n\n
Method 3: Disable IPv6 via GRUB Kernel Parameter<\/h2>\n\n\n\n
The most reliable way to disable IPv6 is at the kernel level through GRUB boot parameters. This prevents the IPv6 kernel module from loading entirely, which means no process or service can re-enable it at runtime.<\/p>\n\n\n\n
Ubuntu 24.04\/22.04<\/h3>\n\n\n\n
Edit the GRUB configuration file:<\/p>\n\n\n\n
sudo vi \/etc\/default\/grub<\/code><\/pre>\n\n\n\nFind the line starting with GRUB_CMDLINE_LINUX<\/code> and add the IPv6 disable parameter. If the line already has values, append to them:<\/p>\n\n\n\nGRUB_CMDLINE_LINUX=\"ipv6.disable=1\"<\/code><\/pre>\n\n\n\nIf you have existing parameters, keep them and add ipv6.disable=1<\/code> at the end, separated by a space.<\/p>\n\n\n\nRegenerate the GRUB configuration:<\/p>\n\n\n\n
sudo update-grub<\/code><\/pre>\n\n\n\nReboot the system for the change to take effect:<\/p>\n\n\n\n
sudo reboot<\/code><\/pre>\n\n\n\nRocky Linux 10 \/ AlmaLinux 10<\/h3>\n\n\n\n
On RHEL-family distributions, edit the GRUB defaults:<\/p>\n\n\n\n
sudo vi \/etc\/default\/grub<\/code><\/pre>\n\n\n\nAdd ipv6.disable=1<\/code> to the GRUB_CMDLINE_LINUX<\/code> line:<\/p>\n\n\n\nGRUB_CMDLINE_LINUX=\"crashkernel=auto ipv6.disable=1\"<\/code><\/pre>\n\n\n\nKeep any existing parameters and append the IPv6 disable flag. Then regenerate the GRUB configuration. The command differs depending on your boot mode.<\/p>\n\n\n\n
For BIOS-based systems:<\/p>\n\n\n\n
sudo grub2-mkconfig -o \/boot\/grub2\/grub.cfg<\/code><\/pre>\n\n\n\nFor UEFI-based systems:<\/p>\n\n\n\n
sudo grub2-mkconfig -o \/boot\/efi\/EFI\/rocky\/grub.cfg<\/code><\/pre>\n\n\n\nOn AlmaLinux 10, replace rocky<\/code> with almalinux<\/code> in the UEFI path. Then reboot:<\/p>\n\n\n\nsudo reboot<\/code><\/pre>\n\n\n\nAfter the reboot, verify the kernel parameter was applied:<\/p>\n\n\n\n
cat \/proc\/cmdline<\/code><\/pre>\n\n\n\nYou should see ipv6.disable=1<\/code> in the output. This confirms IPv6 is disabled at the kernel level.<\/p>\n\n\n\nMethod 4: Disable IPv6 on a Specific Network Interface<\/h2>\n\n\n\n
Sometimes you only need to disable IPv6 on one interface while keeping it active on others. This is common on multi-homed servers where the internal interface should be IPv4-only but the external interface needs IPv6.<\/p>\n\n\n\n
Using sysctl for a single interface<\/h3>\n\n\n\n
To disable IPv6 on a specific interface at runtime (replace ens18<\/code> with your interface name):<\/p>\n\n\n\nsudo sysctl -w net.ipv6.conf.ens18.disable_ipv6=1<\/code><\/pre>\n\n\n\nTo make this persistent, create a sysctl configuration file:<\/p>\n\n\n\n
sudo vi \/etc\/sysctl.d\/70-disable-ipv6-ens18.conf<\/code><\/pre>\n\n\n\nAdd the following line (adjust the interface name as needed):<\/p>\n\n\n\n
net.ipv6.conf.ens18.disable_ipv6 = 1<\/code><\/pre>\n\n\n\nApply the configuration:<\/p>\n\n\n\n
sudo sysctl --system<\/code><\/pre>\n\n\n\nVerify IPv6 is disabled only on that interface:<\/p>\n\n\n\n
ip -6 addr show dev ens18<\/code><\/pre>\n\n\n\nThis should return no IPv6 addresses for ens18<\/code>, while other interfaces retain their IPv6 configuration.<\/p>\n\n\n\nUsing NetworkManager for a single interface<\/h3>\n\n\n\n
On systems with NetworkManager, you can disable IPv6 per connection profile:<\/p>\n\n\n\n
sudo nmcli connection modify ens18 ipv6.method disabled\nsudo nmcli connection up ens18<\/code><\/pre>\n\n\n\nConfirm the change by checking the connection details:<\/p>\n\n\n\n
nmcli connection show ens18 | grep ipv6.method<\/code><\/pre>\n\n\n\nThe output should show ipv6.method: disabled<\/code>.<\/p>\n\n\n\nHow to Re-enable IPv6<\/h2>\n\n\n\n
If you need to restore IPv6 after disabling it, reverse the steps from whichever method you used.<\/p>\n\n\n\n
Re-enable after sysctl (runtime)<\/h3>\n\n\n\n
Set the disable parameter back to 0:<\/p>\n\n\n\n
sudo sysctl -w net.ipv6.conf.all.disable_ipv6=0\nsudo sysctl -w net.ipv6.conf.default.disable_ipv6=0<\/code><\/pre>\n\n\n\nIPv6 addresses will reappear on your interfaces within seconds.<\/p>\n\n\n\n
Re-enable after persistent sysctl file<\/h3>\n\n\n\n
Remove the configuration file you created:<\/p>\n\n\n\n
sudo rm \/etc\/sysctl.d\/70-disable-ipv6.conf\nsudo sysctl --system<\/code><\/pre>\n\n\n\nIf you also disabled IPv6 in NetworkManager, re-enable it:<\/p>\n\n\n\n
sudo nmcli connection modify ens18 ipv6.method auto\nsudo nmcli connection up ens18<\/code><\/pre>\n\n\n\nThe interface will obtain an IPv6 address through SLAAC or DHCPv6, depending on your network configuration.<\/p>\n\n\n\n
Re-enable after GRUB kernel parameter<\/h3>\n\n\n\n
Edit \/etc\/default\/grub<\/code> and remove ipv6.disable=1<\/code> from the GRUB_CMDLINE_LINUX<\/code> line. Then regenerate the GRUB configuration.<\/p>\n\n\n\nOn Ubuntu:<\/p>\n\n\n\n
sudo update-grub<\/code><\/pre>\n\n\n\nOn Rocky Linux \/ AlmaLinux (BIOS):<\/p>\n\n\n\n
sudo grub2-mkconfig -o \/boot\/grub2\/grub.cfg<\/code><\/pre>\n\n\n\nReboot for the change to take effect. After reboot, IPv6 will be fully functional again.<\/p>\n\n\n\n
Verify IPv6 is Disabled<\/h2>\n\n\n\n
Regardless of which method you used, run these checks to confirm IPv6 is properly disabled.<\/p>\n\n\n\n
Check the kernel parameter value:<\/p>\n\n\n\n
sysctl net.ipv6.conf.all.disable_ipv6<\/code><\/pre>\n\n\n\nA value of 1<\/code> confirms IPv6 is disabled system-wide.<\/p>\n\n\n\nConfirm no IPv6 addresses are assigned to any interface:<\/p>\n\n\n\n
ip -6 addr show<\/code><\/pre>\n\n\n\nThis should return empty output when IPv6 is fully disabled.<\/p>\n\n\n\n
If you used the GRUB method, verify the kernel boot parameter:<\/p>\n\n\n\n
cat \/proc\/cmdline | grep ipv6<\/code><\/pre>\n\n\n\nYou should see ipv6.disable=1<\/code> in the kernel command line.<\/p>\n\n\n\nTest that IPv6 connectivity is actually gone by attempting a connection to an IPv6-only endpoint:<\/p>\n\n\n\n
ping -6 -c 2 ::1<\/code><\/pre>\n\n\n\nWith IPv6 disabled, this command will fail with “connect: Network is unreachable” or a similar error.<\/p>\n\n\n\n
Things to Watch Out For<\/h2>\n\n\n\n
Disabling IPv6 can have side effects that catch people off guard. Keep these in mind:<\/p>\n\n\n\n
\n- SSH may slow down<\/strong> – If your SSH config or DNS returns AAAA records, SSH will try IPv6 first and wait for it to time out. Add
AddressFamily inet<\/code> to \/etc\/ssh\/sshd_config<\/code> to force IPv4-only connections.<\/li>\n- DNS resolution issues<\/strong> – Some resolvers query for AAAA records even when IPv6 is disabled. If you see slow DNS lookups, configure your resolver to prefer IPv4.<\/li>\n
- Package managers<\/strong> – APT and DNF may try IPv6 mirrors if the mirror list includes AAAA records. This usually falls back to IPv4 automatically but adds latency.<\/li>\n
- Docker and containers<\/strong> – Docker uses IPv6 internally for some bridge networking features. Disabling IPv6 on the host can affect container networking. Test thoroughly before applying to production container hosts.<\/li>\n
- Localhost connections<\/strong> – Some applications bind to
::1<\/code> (IPv6 localhost) by default. With IPv6 disabled, those applications need to be configured to bind to 127.0.0.1<\/code> instead.<\/li>\n- NetworkManager overrides<\/strong> – On RHEL-family systems, NetworkManager can re-enable IPv6 on managed interfaces. Always disable IPv6 in both sysctl and NetworkManager to avoid conflicts.<\/li>\n<\/ul>\n\n\n\n
Frequently Asked Questions<\/h2>\n\n\n\nIs it safe to disable IPv6 on a production server?<\/h3>\n\n\n\n
Yes, as long as your applications and services don’t depend on IPv6 connectivity. Most server workloads still run on IPv4. Check that your application configs don’t bind to IPv6 addresses before disabling it.<\/p>\n\n\n\n
Which method is best for servers?<\/h3>\n\n\n\n
The GRUB kernel parameter method (Method 3) is the most reliable for production servers. It prevents the IPv6 stack from loading entirely, so no service or process can re-enable it. The sysctl file method (Method 2) is a close second and doesn’t require a reboot to apply.<\/p>\n\n\n\n
Will disabling IPv6 break my system?<\/h3>\n\n\n\n
Modern Linux distributions work fine without IPv6. The main risks are applications that bind exclusively to IPv6 addresses and SSH slowdowns if DNS returns AAAA records. Both are easy to fix with minor configuration changes.<\/p>\n\n\n\n
Can I disable IPv6 on one interface and keep it on another?<\/h3>\n\n\n\n
Yes, Method 4 covers exactly this. Use the per-interface sysctl parameter or NetworkManager’s per-connection setting to selectively disable IPv6 on specific interfaces.<\/p>\n\n","protected":false},"excerpt":{"rendered":"
Most Linux distributions ship with IPv6 enabled by default. That works fine until it does not. Legacy applications that choke on IPv6 addresses, VPN tunnels that only handle IPv4, or troubleshooting scenarios where you need a clean IPv4-only stack that don’t handle dual-stack networking, troubleshooting DNS resolution issues, or hardening a server that only needs … Read more<\/a><\/p>\n","protected":false},"author":3,"featured_media":2225,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[299,50,55],"tags":[36537,390,36538],"class_list":["post-2224","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-how-to","category-linux-tutorials","category-networking","tag-disable-ipv6-on-linux","tag-ipv6","tag-ipv6-on-linux"],"_links":{"self":[{"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/posts\/2224","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/comments?post=2224"}],"version-history":[{"count":2,"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/posts\/2224\/revisions"}],"predecessor-version":[{"id":164106,"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/posts\/2224\/revisions\/164106"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/media\/2225"}],"wp:attachment":[{"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/media?parent=2224"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/categories?post=2224"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/tags?post=2224"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}