core-extra/wiki/NamespaceKernels.wiki
2012-11-02 17:14:49 +00:00

36 lines
No EOL
2.1 KiB
Text

#summary List of known good/bad kernels.
This page lists known good/bad kernels for the [Namespaces] version of CORE.
Some part of the kernel not working well within namespaces? See the [CustomKernels] page also.
_*Note: these are incomplete lists!*_
= Known good kernels =
|| distro || kernel versions || notes ||
|| Ubuntu 10.04 || 2.6.32-21-generic i686,<br>2.6.32-39-generic i686 || stock kernel, updated kernel ||
|| || 2.6.33 || ||
|| Arch Linux || 2.6.35.7 || certain versions ||
|| Fedora 14 || || yum update from stock kernel ||
|| Fedora 15 || 2.6.40.3-0.fc15.x86_64, 2.6.41.10-3.fc15.i686 || yum update from stock kernel ||
|| Ubuntu 11.04 || 2.6.38-core || CORE patched kernel enables netfilter queuing, IPsec ||
|| Ubuntu 11.10 || 3.0.0-15-generic || ||
|| Fedora 16 || 3.1.0-7.fc16.x86_64 || stock kernel ||
|| Ubuntu 12.04 || 3.2.0-30-generic, 3.2.0-32-generic || ||
|| Fedora 17 || 3.5.3-1.fc17.x86_64 || ||
= Known bad kernels =
|| distro || kernel versions || problem || workaround/notes ||
|| Fedora 15 || 2.6.38.6-26.rc1.fc15.x86_64, 2.6.38.6-26.rc1.fc15.i686 || (1) IPv6 snooping bug || yum update to fix ||
|| Ubuntu 10.10 || 2.6.35-22 || crashes || use rc6 or newer from http://kernel.ubuntu.com/~kernel-ppa/mainline/ as workaround ||
|| Fedora 14, Ubuntu 10.10 || 2.6.34, 2.6.35, 2.6.35.6-45.fc14.i686, 2.6.35-22-generic || (2) IPv6 in namespaces || CORE has workaround ||
|| Ubuntu 10.04 || 2.6.32-32 || namespace support not enabled || ||
|| [http://www.4tiitoo.com/ WeTab Linux] || 2.6.42-66672.1.28-wetab || namespace support not enabled || ||
|| || 3.3 || unable to rename interface installed into namespace || see patch in CORE source ||
# IPv6 snooping bug - OSPFv3 hellos jump off the bridge
* Look at output of `netstat -s | grep invalid` to see "invalid headers"
# Problem with IPv6 addressing in namespaces (CORE SVN snapshot has workaround):
* 2.6.34 and 2.6.35 seem to have problems ([http://www.spinics.net/lists/netdev/msg137122.html possibly related problem]) as reported by users [http://pf.itd.nrl.navy.mil/pipermail/core-users/2010-September/000269.html here].