is there a release plan of tproxy patch for kernel 2.6.16 or 2.6.17
Hi, I'm currently using cttproxy-2.6.15-2.0.4.tar.gz for my 2.6.15 kernel and I'm planing to upgrade my kernel to 2.6.16 or 2.6.17, but I will not do so until the tproxy patch is ready for the new kernel. So, would anyone tell me whether there is a release plan of tproxy patch for kernel 2.6.16 or 2.6.17? The last 2.0.4 was released about 5 months ago. Thanks very much. Best regards, Zhuang Yuyao
Subject: [tproxy] is there a release plan of tproxy patch for kernel 2.6.16 or 2.6.17
HAHA Yes :-) (Krisztián will elaborate on that.) Jan Engelhardt --
Oh, that is really the fastest reply I have ever had :-) Would you please give me some more information about the release date and the target kenrel? On 7/28/06, Jan Engelhardt <jengelh@linux01.gwdg.de> wrote:
Subject: [tproxy] is there a release plan of tproxy patch for kernel 2.6.16 or 2.6.17
HAHA Yes :-) (Krisztin will elaborate on that.)
Jan Engelhardt --
Oh, that is really the fastest reply I have ever had :-)
Would you please give me some more information about the release date and the target kenrel?
Well I just verified that the newest code I got from Krisztián works the usual way on an Ethernet bridge. Should be shortly until a release. I hope. I'm preparing the squid3 patch ATM. Jan Engelhardt --
Great news. now all that I need is patience, patience, patience ...... :-) On 7/28/06, Jan Engelhardt <jengelh@linux01.gwdg.de> wrote:
Oh, that is really the fastest reply I have ever had :-)
Would you please give me some more information about the release date and the target kenrel?
Well I just verified that the newest code I got from Krisztin works the usual way on an Ethernet bridge. Should be shortly until a release. I hope.
I'm preparing the squid3 patch ATM.
Jan Engelhardt --
Great news. now all that I need is patience, patience, patience ...... :-)
If nothing happens, write again and I will release it. *hehe* PS: Please do not strip the mailing list from Cc. Jan Engelhardt --
Sorry Jan, i forgot to use 'reply to all' instead of 'reply'. Happy weekend. On 7/28/06, Jan Engelhardt <jengelh@linux01.gwdg.de> wrote:
Great news. now all that I need is patience, patience, patience ...... :-)
If nothing happens, write again and I will release it. *hehe*
PS: Please do not strip the mailing list from Cc.
Jan Engelhardt --
Hi, On Friday 28 July 2006 15.56, Zhuang Yuyao wrote:
I'm currently using cttproxy-2.6.15-2.0.4.tar.gz for my 2.6.15 kernel and I'm planing to upgrade my kernel to 2.6.16 or 2.6.17, but I will not do so until the tproxy patch is ready for the new kernel. So, would anyone tell me whether there is a release plan of tproxy patch for kernel 2.6.16 or 2.6.17? The last 2.0.4 was released about 5 months ago.
Sure, I'm already testing those releases. Unfortunately I still have git related problems with the linux-2.4 repository on kernel.org, so the 2.4 patch is still missing. That's why I did not release 2.0.5 today. For the impatient, however, there are pre-released patches for 2.6.16, 2.6.17, and 2.6.18-rc2. These patches have seen a limited amount of testing and generally seem to work OK: http://people.balabit.hu/hidden/tproxy2-2.6.16_20060727.tar.bz2 http://people.balabit.hu/hidden/tproxy2-2.6.17_20060727.tar.bz2 http://people.balabit.hu/hidden/tproxy2-2.6.18_20060727.tar.bz2 -- Regards, Krisztian Kovacs
Sure, I'm already testing those releases. Unfortunately I still have git related problems with the linux-2.4 repository on kernel.org, so the 2.4 patch is still missing. That's why I did not release 2.0.5 today.
Who is really using 2.4 these days? I know, all those sad souls who bought a long-time support Redhat contract some years ago. :-( But given that you need to patch the kernel anyhow makes the jump to 2.6 easy. (Like in this case.)
For the impatient, however, there are pre-released patches for 2.6.16, 2.6.17, and 2.6.18-rc2. These patches have seen a limited amount of testing and generally seem to work OK:
http://people.balabit.hu/hidden/tproxy2-2.6.16_20060727.tar.bz2 http://people.balabit.hu/hidden/tproxy2-2.6.17_20060727.tar.bz2 http://people.balabit.hu/hidden/tproxy2-2.6.18_20060727.tar.bz2
For the impatient, here is the squid3 patch (works with all versions of tproxy2): http://jengelh.hopto.org/f/squid-3.0-tproxy2.diff It requires that you ... 'somehow' give the squid user CAP_NET_ADMIN. That is left as an exercise to the user, but the multiadm kernel module (http://freshmeat.net/p/multiadm/ ) has a solution for this too, and it's even documented. squid 2.6 apparently seems to have tproxy support in mainline by now, but it does an icky way to get the CAP_NET_ADMIN thing, using prctl and thelike. I have no idea if and how it works, and I will not devote any time, for I really/only need squid3 (has better logging options!). Cheers, Jan Engelhardt --
thanks, I will test it on monday and happy weekend :-) On 7/28/06, KOVACS Krisztian <hidden@balabit.hu> wrote:
Hi,
On Friday 28 July 2006 15.56, Zhuang Yuyao wrote:
I'm currently using cttproxy-2.6.15-2.0.4.tar.gz for my 2.6.15 kernel and I'm planing to upgrade my kernel to 2.6.16 or 2.6.17, but I will not do so until the tproxy patch is ready for the new kernel. So, would anyone tell me whether there is a release plan of tproxy patch for kernel 2.6.16 or 2.6.17? The last 2.0.4 was released about 5 months ago.
Sure, I'm already testing those releases. Unfortunately I still have git related problems with the linux-2.4 repository on kernel.org, so the 2.4 patch is still missing. That's why I did not release 2.0.5 today.
For the impatient, however, there are pre-released patches for 2.6.16, 2.6.17, and 2.6.18-rc2. These patches have seen a limited amount of testing and generally seem to work OK:
http://people.balabit.hu/hidden/tproxy2-2.6.16_20060727.tar.bz2 http://people.balabit.hu/hidden/tproxy2-2.6.17_20060727.tar.bz2 http://people.balabit.hu/hidden/tproxy2-2.6.18_20060727.tar.bz2
-- Regards, Krisztian Kovacs
participants (3)
-
Jan Engelhardt
-
KOVACS Krisztian
-
Zhuang Yuyao