Kernel 2.4

LIMITATIONS OF USING A 2.4 KERNEL VS A 2.6 KERNEL

This program works with newer versions of both the 2.6 and the 2.4 linux kernels, but there are certain limitations when using a 2.4 kernel. With the 2.6 kernel you only see the interfaces that are currently up and running, but with the 2.4 kernel you see all interfaces whether they're running or not. Also, with the 2.4 kernel the program relies on shell calls to ifconfig and brctl while with the 2.6 kernel this is not the case. Having a lot of shell calls may be a security concern so when using a 2.6 kernel the program is slightly more secure.

If you set the Packet scheduler clock source to 'CPU cycle counter' in the kernel then you get a clock frequency of only 100Hz with the 2.4 kernel while the frequency is 1000Hz in the 2.6 kernel. This means the netem timer accuracy would only be to the nearest 10ms with 2.4 but 2.6 will be accurate to the nearest 1ms.

If you are still using Kernel 2.4, you have to change the kernel version
in config.inc.php to '2.4' or else the program won't work properly.