Anyone able to get guard dog working on 2.6.17 and up kernels w/ipv6 & ipv4 combo?

Kenny Z's linuxpackages "kmyfirewall" no worky either.

Even pulled down slack current testing kernel, and then did make old config to get it on 2.6.17.4 and no good.

I had the same problem with a 2.6.16 kernel. Someone told me that you have to recompile iptables to work with the new kernel. They said it's just dumb luck if iptables works with a new kernel. So I recompiled iptables, and now everything seems to work okay.

I'm sure you already included all the right modules in the kernel, but you might check again.

Here's the thread where I had my problem. It looks like I also compiled all the iptables stuff into the kernel instead of as modules.

thank you I will start reading that.

Hi all,

Hey pljvaldez you were 100% on, my iptables were bad.

The comment that the one person made in your thread, that 'ip tables' are compiled for one version and any upgrade is pure luck' is what caught my eye.

I then remembered that this happened to me before when I first started playing with kernels. Effectively I had this issue; but the symptoms were different then, I had no internet whatsoever. This issue that I had here was massive amounts of packet's being dropped.

So before I took the leap into making new ip-tables, I decided to boot up into slackware's stock 2.4.31 kernel on my 'package making only' partition, and compiled the kernel there, and installed it, and now it's fine.

Which now leads me to believe that for now on, I should always compile on whatever kernel my slackware is initially installed on; and leave the original symlink there for '/usr/src/linux' alone, and not re-create that symlink to my new kernel's even tho that is the popular philosophy.

It's seems that for me, for whatever reason, I can create a new symlink once for a new kernel, but not for a 3rd, 4th or 5th kernel. It seems ok if you slap in just one kernel and make /usr/src/linux point to the new running kernel, but no more.

I'm new, and I know there's a debate on this. And I'm not bringing it up to stir a debate, as this is my present thought based on what I'm seeing as I learn.

Thank you again, that was very intuitive of you.

Bye for now.

nope no good. i just turned on samba on the pc i did the new kernel on and it happened again. and I reloaded it too and same thing.

used slack testing config made another one, same thing, this is a bad kernel...or samba in 10.2 is not liking this kernel or something, i dont know, i put a different kernel in and be done with this