Both from ftp.kernel.org and using exactly the same .config file. I'll try to get the time to test 2.6.32 to 2.6.36. Thanks! On Tue, Jan 25, 2011 at 12:36 AM, Amos Jeffries <squid3@xxxxxxxxxxxxx> wrote: > On Tue, 25 Jan 2011 00:24:43 -0200, Agua Emagrece <aguaemagrece@xxxxxxxxx> > wrote: >> Hello, Amos, how are you? >> >> I just did a test downgrading my kernel to 2.6.30 (downloaded from >> ftp.kernel.org), using the same kernel .config of the 2.6.37 I was >> using, and all the same iptables/ebtables/sysctl configuration. TPROXY >> just began to work perfectly. If I switch again to 2.6.37, everything >> stops. >> >> Can this really be a problem with newer kernel versions? Are there any >> specific configurations for these newer versions? >> >> Anybody here is using squid TPROXY with newer kernels (2.6.36-2.6.37) ? >> >> Thanks in advance for your reply and help!! >> > > There was some ebtables ICMP related breakage in 2.6.32 which got fixed > mid last year, I think that was fixed the .37 kernel though. Other than > that the only change was IPv6 TPROXY going into .37. > > Best bring this up with the netfilter mailing lists if you are sure its > only a kernel difference. > > BTW: was it a .37 kernel from ftp.kernel.org or a slackware patched one? > > Amos > >
