unable to disable IPv6

Bug #158805 reported by MarianoAbsatz
2
Affects Status Importance Assigned to Milestone
linux-source-2.6.22 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: linux-image-2.6.22-14-server

I have three different gutsy computers.

One is a xen slice in slicehost.com (upgraded from dapper, to edgy, to feisty, to gutsy).

Another one is a plain desktop.

The last one is a server (installed from cd and upgraded from feisty to gutsy).

I tried to disable IPv6 in all of them. The first two worked just fine by simply creating a file /etc/modeprobe.d/blacklist.ipv6 with the following line:
blacklist ipv6

However, the last one (where the only difference I see is that the kernel version), insists on loading IPv6.

I tried several combinations of the instructions in:
https://help.ubuntu.com/community/WebBrowsingSlowIPv6IPv4
http://beranger.org/index.php?article=1127&page=3k
http://ralph.n3rds.net/index.php?/archives/177-How-to-Disable-IPV6-in-Ubuntu.html
and a handful of ubuntuforums.org threads to no avail...

uname -a yields:
Linux my_server 2.6.22-14-server #1 SMP Sun Oct 14 23:34:23 GMT 2007 i686 GNU/Linux

I don't know what other info might help here...

Tags: ipv6 kernel
Revision history for this message
Rui Bernardo (epimeteo) wrote :

Hi,

I add this problem too. I had a Ubuntu Feisty server working without ipv6 (blacklisted with "blaclist ipv6" on /etc/modprobe.d/blacklist). No ipv6 module was being loaded.

Then I've upgraded it to Gutsy and then the module started to be loaded, even with the ipv6 being blacklisted!

user@server:~$ lsmod|grep ipv6
ipv6 278916 24 nf_conntrack_h323

I've found that ipv6 was loaded by nf_conntrack_h323 module, and this one was used by nf_nat_h323. I don't know why this modules were being loaded (no SIP software installed on the server)

I was using shorewall firewall, so I had to explicitly add an empty module file (the file where you say which iptables modules you want to be loaded). This avoided that those modules from being loaded and ipv6 wasn't loaded since then.

I really think there is something wrong here. Even if shorewall had changed and loaded all iptables modules since Gutsy (wasn't happening in Feisty), with the ipv6 module being blacklisted it should not be loaded!

More info of this "adventure" here: http://ubuntuforums.org/showthread.php?p=3694365

Revision history for this message
MarianoAbsatz (el-baby) wrote :

Sorry,

I forgot to post a follow-up on this... I solved this...

The solution was actually one of the ones I tried (adding "blacklist ipv6" to one of the files in /etc/modprobe.d) '''and rebooting!!!''' (I did a lot of testing simply using {{{/etc/init.d/networking stop ; /etc/init.d/networking start}}} only to find out that ''that'' wasn't enough *sigh* :-(

FWIW, I had shorewall installed (version 4.0.5 from source, not the old package available from the repositories), but I don't see nf_conntrack_h323 or any other h323 related module.

Changed in linux-source-2.6.22:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.