Ah OK, I thought it was related to the new compat code, but that isn't the case. Your trace doesn't give much clues, except that it shows that iptables dies with a SIGSEGV, which might be a bug in userspace or in the kernel. Which was the last kernel that worked for you, and can you try that version again to rule out userspace bugs?
It's a fresh install in the new role with a new HDD and 2 NICs for a firewall so I have not tried earlier kernels with iptables. I do have sarge's 2.6.8 also working on that machine but not the kernels from testing and unstable (2.5.15 and 2.6.16) because the lack of prep support at the moment. I could problably compile some intermediate kernels but I haven't tested even the working 2.6.8 first with iptables yet.
I will be away tomorrow but can test some kernels the day after tomorrow. Only some of them because it's not a fast compile engine.
It only SIGSEGVs when ptraced and just gets Invalid Argument errors when not traced so this SEGV may be something different (perhaps ptrace related).
-- Meelis Roos ([EMAIL PROTECTED]) - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
