A default (CentOS) kernel doesn't have TPROXY support, which is needed if you want to it to behave as a transparant proxy. This is useful if you have a cluster set-up with one or more loadbalancers, but you still want each underlying node to see the original source IP from the request.
Without transparant proxy (TPROXY), all request would appear to come from the load balancer's IP address, instead of the actual client (which can mess up your logging, scripts, ...).
This article is derived from the "How To Compile a Kernel -- The CentOS way" pages at howtoforge.com, and the guides at LoadBalancer.org.
We will assume you have a running CentOS at this point (version 5.5 or later). First up, download the kernel source. Since the TPROXY patch isn't compatible with all Kernel versions, we're stuck with the 2.6.25 kernel. Please browse the Kernel Source Index, and pick the latest linux-2.6.25.* kernel work from. (if the version is no longer available for download, here's a local copy).
Now, unpack the source code, and symlink the resulting directory to 'linux' (will make things easier later on).
tar xzf linux-220.127.116.11.tar.gz
ln -s linux-18.104.22.168 linux
Next step is to download the TPROXY patch. (if the version is no longer available for download, here's a local copy)
tar xjf tproxy-kernel-2.6.25-20080519-165031-1211208631.tar.bz2
Now to apply the patch mentioned.
cat ../tproxy-2.6.25-20080519/00* | patch -p1 --dry-run
cat ../tproxy-2.6.25-20080519/00* | patch -p1
To start compiling the kernel, we'll first clean any leftovers that may exist.
make clean && make mrproper
And copy our current Kernel configuration to our local .config file. This will help in making sure our currently installed applications will continue working, and we don't modify the kernel too heavily.
cp /boot/config-`uname -r` ./.config
Make sure you have all the necessary developer-tools, to compile the kernel.
yum install make rpm-build gcc gcc-c++ ncurses-devel elfutils elfutils-libs libstdc++-devel
Let's pop up the kernel configuration menu, which will allow us to easily change configs.
Since we saved our currently running Kernel's configuration in the .config file, we will choose the "Load an alternative Configuration File" option, and enter .config as the filename.
menuconfig: load config
Let's enable TPROXY support. Navigate in the menu to
- > Networking support
- > Networking options
- > Network packet filtering framework (Netfilter)
- > Core Netfilter Configuration
Transparent proxying support (EXPERIMENTAL)
Netfilter Xtables support (required for ip_tables)
Netfilter Connection tracking
> Connection tracking flow accounting
> Connection mark tracking support
"TPROXY" target support (EXPERIMENTAL)
"socket" match support (EXPERIMENTAL)
Beware that you can check these options in 2 ways:
Try to select the options listed above as [M], so they are modules.
Then hit <ESC><ESC> a few times, to get back to the main menu, and navigate to General Setup > () Local version -- append to kernel release. Add a custom suffix there, to identify this kernel. I've choosen "-tproxy" as suffix (so I know it has tproxy support). It's important you add a version number if you try to reinstall the kernel again afterwards, or you'll end up with "this package is already installed" messages.
Once you've applied the above changes, exit the menu and confirm you want to save your changes.
Now start compiling the source and create the RPM install file.
This _will_ take a long time. If you're running this inside a virtual machine, consider adding more (virtual) CPU's to speed up this process. It's safe to assume this will run for at least 1 hour, probably more.
After it's been created, you will find the resulting Source RPM file in /usr/src/redhat/SRPMS/.
lb02.lab.mojah.be linux $ ls -al /usr/src/redhat/SRPMS/
drwxr-xr-x 2 root root 4096 Aug 21 17:31 .
drwxr-xr-x 7 root root 4096 Aug 21 16:20 ..
-rw-r--r-- 1 root root 63536285 Aug 21 17:27 kernel-22.214.171.124tproxy-1.src.rpm
And the binary RPM file in /usr/src/redhat/RPMS/i386/ (or x86_64 if you're running 64 bit).
lb02.lab.mojah.be linux $ ls -al /usr/src/redhat/RPMS/i386/
drwxr-xr-x 2 root root 4096 Aug 21 17:32 .
drwxr-xr-x 9 root root 4096 Aug 21 16:20 ..
-rw-r--r-- 1 root root 123002989 Aug 21 17:31 kernel-126.96.36.199tproxy-1.i386.rpm
Now it's time to install our custom kernel.
rpm -ivh --nodeps /usr/src/redhat/RPMS/i386/kernel-188.8.131.52tproxy-1.i386.rpm
And create the ramdisk for our system.
mkinitrd /boot/initrd-184.108.40.206-tproxy.img 220.127.116.11-tproxy
Let's see what files were made in the /boot partition. We'll need these filenames to edit the grub config later on.
lb02.lab.mojah.be linux $ ls -alh /boot/ | grep -i tproxy
-rw-r--r-- 1 root root 73K Aug 21 17:27 config-18.104.22.168-tproxy
-rw------- 1 root root 3.2M Aug 21 17:33 initrd-22.214.171.124-tproxy.img
-rw-r--r-- 1 root root 1015K Aug 21 17:27 System.map-126.96.36.199-tproxy
-rw-r--r-- 1 root root 1.9M Aug 21 17:27 vmlinuz-188.8.131.52-tproxy
And edit the menu-file.
And add the following snippet below the "hiddenmenu" line, and right above the first kernel declaration. This consists of copying an already existing boot-item, and modify the vmlinuz and initrd locations.
title CentOS-Tproxy (184.108.40.206-tproxy)
kernel /vmlinuz-220.127.116.11-tproxy ro root=/dev/VolGroup00/LogVol00
The /vmlinuz and /initrd should point to the filenames you discovered earlier. Please don't directly copy/paste the example above, but copy an entry from your file, and modify it (as to preserve the hard disk order and volume names).
Now reboot into your newly created kernel. Your boot screen would look a bit like this now, with a notice to the newly named kernel.
You can verify this once the server's booted up.
lb02.lab.mojah.be ~ $ uname -a
Linux lb02.lab.mojah.be 18.104.22.168-tproxy #1 SMP Sat Aug 21 17:22:41 CEST 2010 i686 i686 i386 GNU/Linux
Now we have our kernel with TPROXY support running, time to compile and patch our iptables to make use of it. To get started, download 1.4.0 iptables source. It's import you take the 1.4.0 version, newer versions won't work. (if the version is no longer available for download, here's a local copy).
tar xjf iptables-1.4.0.tar.bz2
Now also download the tproxy iptables patch. (if the version is no longer available for download, here's a local copy)
Apply the tproxy path.
cat ../tproxy-iptables-1.4*.patch | patch -p1
make && make install
Now you've installed both your kernel, and iptables, with the tproxy patch.
iptables 1.4.0.tar.bz: full iptables source code
linux-22.214.171.124.tar.gz: full kernel 126.96.36.199 source code
tproxy-iptables-1.4.0-20080521.patch: tproxy patch for iptables
tproxy-kernel-2.6.25-20080519.tar.bz2: tproxy patch for 2.6.25 kernel
.config: the .config file I used to compile my kernel (with all necessary modules checked)
kernel-188.8.131.52tproxy.i386.rpm: rpm install file for a 32-bit (i386) kernel with tproxy support. Follow the "mkinitrd" steps above to install & use this kernel. The kernel is named "184.108.40.206-tproxyfourteen".
Troubleshooting: unknown match socket
If you've done the above steps, and still get the UNKNOWN match `socket' message in your iptables, you've probably skipped a kernel module required for this to work.
Troubleshooting: bad exit status during kernel compile
You could run into something similar to the following when compiling your kernel.
LD [M] drivers/scsi/scsi_mod.o
error: Bad exit status from /var/tmp/rpm-tmp.48540 (%build)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.48540 (%build)
make: *** [rpm] Error 1
make: *** [rpm] Error 2
That will prevent you kernel from successfully compiling. It usually means you selected a kernel option with a certain dependency that wasn't checked. So it's dependent on an option, that's not being compiled.
Tricky part here is to track down which one, and I'm afraid to say I don't know how. Also, it's beyond the scope of this document. If you want to retry the compilation again, make sure to run:
cp .config .config_backup
make clean && make mrproper
to reset your current attempt, clear created files and reset the config back to zero. Your "broken" config can then still be found in the .config_backup file. In my experience, it's better to just start all over ...
You could also consider deleting the generated files in /usr/src/redhat/BUILD/kernel-* as they are obsolete now.