Sponsored Content
Special Forums IP Networking [ipv6_test] Kernel is not compiled with IPv6 support Post 302890570 by postcd on Thursday 27th of February 2014 12:43:17 PM
Old 02-27-2014
[ipv6_test] Kernel is not compiled with IPv6 support

Hello, i tried to enable IPv6 networking and after service network restart i seen these messages:

Code:
FATAL: Error inserting ipv6 (/lib/modules/2.6.18-348.16.1.el5.028stab108.1/kernel/net/ipv6/ipv6.ko): Device or resource busy
CRITICAL : [ipv6_test] Kernel is not compiled with IPv6 support
Bringing up loopback interface:                            [  OK  ]
Bringing up interface eth0:  FATAL: Error inserting ipv6 (/lib/modules/2.6.18-348.16.1.el5.028stab108.1/kernel/net/ipv6/ipv6.ko): Device or resource busy
CRITICAL : [ipv6_test] Kernel is not compiled with IPv6 support
                                                           [  OK  ]

Code:
ping6 ipv6.google.com

returns:
Quote:
socket: Address family not supported by protocol
Im amateur, can you please suggest how to fix this IPv6 support kernel issue? Please if you get idea on commands i need to do, i will do it.

Code:
[root@CentOS-58-64-minimal /]# cat vi /etc/sysconfig/network | grep 6;
cat: vi: No such file or directory
HOSTNAME=CentOS-58-64-minimal
NETWORKING_IPV6=yes
IPV6FORWARDING=yes
IPV6_DEFAULTDEV=eth0
IPV6_DEFAULTGW=2a01:04f8:0191:4150:0000:0000:0000:0000
# defaultgw was 2a01:4f8:191:4150::2/64
IPV6_AUTOCONF=yes
[root@CentOS-58-64-minimal /]# cat /etc/sysconfig/network-scripts/ifcfg-eth0 | grep 6;
HWADDR=50:46:5d:9f:f8:bf
IPADDR=144.76.40.81
SCOPE="peer 144.76.40.65"
IPV6INIT=yes
IPV6ADDR=2a01:4f8:191:4150::2/64
IPV6_DEFAULTGW=fe80::1
IPV6_DEFAULTDEV=eth0
[root@CentOS-58-64-minimal /]# cat /etc/sysctl.conf | grep 6;
# ipv6 settings (no autoconfiguration)
net.ipv6.conf.default.autoconf=0
net.ipv6.conf.default.accept_dad=0
net.ipv6.conf.default.accept_ra=0
net.ipv6.conf.default.accept_ra_defrtr=0
net.ipv6.conf.default.accept_ra_rtr_pref=0
net.ipv6.conf.default.accept_ra_pinfo=0
net.ipv6.conf.default.accept_source_route=0
net.ipv6.conf.default.accept_redirects=0
net.ipv6.conf.default.forwarding=1
net.ipv6.conf.all.autoconf=0
net.ipv6.conf.all.accept_dad=0
net.ipv6.conf.all.accept_ra=0
net.ipv6.conf.all.accept_ra_defrtr=0
net.ipv6.conf.all.accept_ra_rtr_pref=0
net.ipv6.conf.all.accept_ra_pinfo=0
net.ipv6.conf.all.accept_source_route=0
net.ipv6.conf.all.accept_redirects=0
net.ipv6.conf.all.forwarding=1
net.ipv6.conf.all.proxy_ndp=1
net.ipv6.bindv6only=1
net.ipv4.ip_conntrack_max=32760
[root@CentOS-58-64-minimal /]# uname -a
Linux CentOS-58-64-minimal 2.6.18-348.16.1.el5.028stab108.1 #1 SMP Tue Aug 27 13:02:53 MSD 2013 x86_64 x86_64 x86_64 GNU/Linux


Last edited by postcd; 02-27-2014 at 01:59 PM..
 

9 More Discussions You Might Find Interesting

1. IP Networking

DNS Server with IPv6 support

Hello, i have a problem with a dns server. It is running bind 9.4.1 (compiled with "-enable-ipv6") on an AIX 5.3 system. The server starts without any errors or warnings. I am also able to lookup names for IPv4 adresses. But with IPv6 i have a strange problem. When i execute the following dig... (3 Replies)
Discussion started by: skanatiker
3 Replies

2. Ubuntu

Does Posix support kernel level threading?

Hi All, Please let me know the following. 1) Does POSIX lib support kernel threads? if yes, please let me know what are the specific function calls used to create/manage kernel threads. 2) Is Posix scalable? 3) Does POSIX take the advantage of multiprocessor systems? your help is much... (4 Replies)
Discussion started by: jayfriend
4 Replies

3. UNIX for Dummies Questions & Answers

Kernel Support

Hi, I want to learn that all the family of x86 processors are supported by kernel. I want to buy a board, which has VIA ESP10K processor and CHIPSET: VIA CN333 north bridge & VIA VT8237R south bridge Where can I find this? Thanks. (5 Replies)
Discussion started by: yildiz.a
5 Replies

4. UNIX for Dummies Questions & Answers

Script to automatically reboot to newly compiled kernel with fallback

Hi, I'm new here. Just started playing around with kernel compilation. I need a little bit of advice. I'm trying to do a bash script to automatically compile a kernel package and reboot to that new kernel by default, with fallback to the old kernel. So far, I'm getting stuck at the part... (0 Replies)
Discussion started by: tridus_08
0 Replies

5. Solaris

NTP server to support IPv4 and IPv6 client

Hi I am looking to have an NTP server that will support both ipv4 and ipv6 clients. Is there anything specific about the configuration that I should be looking at? (7 Replies)
Discussion started by: eeisken
7 Replies

6. UNIX for Dummies Questions & Answers

Make sure kernel was compiled with NFS server support

Hi there, I have a Debian Squeeze server. How can I check if my kernel was compiled with NFS server support? Extra question: if it is not, how do I enable NFS support in my kernel? Thanks for your help. Santiago (3 Replies)
Discussion started by: chebarbudo
3 Replies

7. Ubuntu

Phenom II support in kernel

Does anyone know at which kernel version support for Phenom II x6 first appeared? (7 Replies)
Discussion started by: Varsel
7 Replies

8. Solaris

Older OS support in Kernel zones

folks, I have a query. Can we create Kernel zone with the earlier Solaris OS? More precisely Can i create kernel zone with any different OS than that of OS in global zone. As of now in sol11U2 if we create kernel zone, there will be sol11u2 OS in kernel zone since the same is in global. But... (4 Replies)
Discussion started by: Vaishey
4 Replies

9. UNIX for Dummies Questions & Answers

Assigning ipv6 to bonding interface - getting old as well as changed ipv6 in ifconfig output

Hi, I have created a bonding bond1 interface with 6 Eth , mode=4. Recently i have changed my old ipv6 to new one and tried to restart as well as reload network service. Post which i can see old as well as changed ipv6 in ifconfig command output. Below are few files and command output for your... (1 Reply)
Discussion started by: omkar.jadhav
1 Replies
IFSYSCTL(5)						       Network configuration						       IFSYSCTL(5)

NAME
ifsysctl[-<interface name>] - per network interface sysctl settings SYNOPSIS
/etc/sysconfig/network/ifsysctl /etc/sysconfig/network/ifsysctl-<interface name> DESCRIPTION
These files are intended to contain sysctl settings, that should be applied when a network interface is created. This are usually interface specific settings, like: net.ipv6.conf.eth0.use_tempaddr = 1 or net.ipv4.conf.eth0.rp_filter = 0 The settings are applied by the /etc/sysconfig/network/scripts/ifup-sysctl script executed via /etc/udev/rules.d/77-network.rules rule (see udev(7)), after the creation and after the rename of the interface name to its persistent name (when applicable), but before the ifup <interface name> -o hotplug may be executed to configure the interface. The settings are not applied by default when the NetworkManager is active (NETWORKMANAGER=yes), except when the IFSYSCTL_NETWORKMANAGER=yes variable is set in the /etc/sysconfig/network/config file. Settings from the ifsysctl- file are applied every time an interface has been created. Settings from the ifsysctl-interface name file are applied when the interface with the corresponding interface name has been created. SYNTAX
The sysctl(8) utility is required to apply the settings. It supports two separator characters for sysctl keywords: a "." in default format and a "/" in the alternate format. Therefore the syntax is basically same to the /etc/sysctl.conf file. Interface names may contain a ".". In the default sysctl format using a "." as separator, that is any "." in the interface name of the key- word, has to be replaced with a "/". In the alternate sysctl format with "/" as separator, normal interface names can be used. Optionally, the ifsysctl files may contain also the $INTERFACE and the $SYSCTL_IF variables, that are automatically replaced with the cur- rent interface name usable in the alternate format and with the sysctl-quoted interface name for the default format, before the settings are passed to the sysctl utility. Note also, that settings with variables in the ifsysctl (without the -<interface name> suffix), will be applied for every interface! Further, files with variables are not compatible to the /etc/sysctl.conf file. EXAMPLES
Settings for "eth0" and "eth0.1" interfaces # using "." as separator: net.ipv6.conf.eth0.use_tempaddr = 1 net.ipv6.conf.eth0/1.use_tempaddr = 1 # using "/" as separator: net/ipv6/conf/eth0/use_tempaddr = 1 net/ipv6/conf/eth0.0/use_tempaddr = 1 Settings with variables: # using "." as separator: net.ipv6.conf.$SYSCTL_IF.use_tempaddr = 1 # using "/" as separator: net/ipv6/conf/$INTERFACE/use_tempaddr = 1 To test your ifsysctl-eth0 or ifsysctl file, use: /etc/sysconfig/network/scripts/ifup-sysctl eth0 -o debug BUGS
Please report bugs at <https://bugzilla.novell.com/> AUTHOR
Marius Tomaschewski <mt@suse.de> SEE ALSO
ifup(8) ifcfg(5) sysctl(8) sysconfig December 2009 IFSYSCTL(5)
All times are GMT -4. The time now is 05:03 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy