Disabling ipv6 on Fedora core 4 new install
After installing FC4, I found out that when I do #/sbin/ifconfig, it shows that IPv6 has been enabled on any eth interface on my box... see below..
eth0 Link encap:Ethernet HWaddr 0D:60:97:6A:98:F4
inet addr:2xx.xx.xxx.xx2 Bcast:2xx.xx.xxx.xx3 Mask:255.255.255.0
inet6 addr: f580::290:97ft:faaa:f6d4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:126557 errors:0 dropped:0 overruns:0 frame:0
TX packets:77565 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:155429479 (148.2 MiB) TX bytes:5770590 (5.5 MiB)
Interrupt:10 Base address:0xdc00
eth1 Link encap:Ethernet HWaddr D0:81:42:86:GD:84
inet addr:192.168.0.4 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe88::201:25f:f883:cd74/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:21897 errors:6 dropped:0 overruns:1 frame:9
TX packets:146 errors:0 dropped:0 overruns:0 carrier:0
collisions:24 txqueuelen:1000
RX bytes:5363531 (5.1 MiB) TX bytes:9099 (8.8 KiB)
Interrupt:11 Base address:0xe000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:201 errors:0 dropped:0 overruns:0 frame:0
TX packets:201 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:52924 (51.6 KiB) TX bytes:52924 (51.6 KiB)
So, in order to disable it, I have to add the ff. on /etc/modprobe.conf file. [note: I found the Idea by googling]
alias net-pf-10 off
alias ipv6 off
and then I rebooted, and here's the new result of #/sbin/ifconfig
eth0 Link encap:Ethernet HWaddr 0D:60:97:6A:98:F4
inet addr:2xx.xx.xxx.xx2 Bcast:2xx.xx.xxx.xx3 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:126557 errors:0 dropped:0 overruns:0 frame:0
TX packets:77565 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:155429479 (148.2 MiB) TX bytes:5770590 (5.5 MiB)
Interrupt:10 Base address:0xdc00
The inet6 address has gone :)
2 Comments:
Thanks for sharing your experience, I ran into the same problem and you saved me from doing all the work you did all over.
By Anonymous, at 10:57 AM
Just to (over)emphasize: It is _not_ enough to do a "service network restart" - you have to reboot.
/Hz
By Hz, at 10:22 AM
Post a Comment
<< Home