Re: [squid-users] squid 2.7 TPROXY not working
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 21/10/2014 6:55 p.m., saleh madi wrote: Hello, I have compiled squid 2.7stable9 with TPROXY patch, but the TPROXY seem not working. Er, yes. The TPROXY patch is not a Squid patch, it is a Linux kernel patch adding TPROXY/cttproxy support to the extremely old Linux kernel v2.2 and v2.4. Squid-2.7 does not need any patching to work with kernels that have been appropriately patched, but does not work with any newer kernels. Please note that all the software you will need to play with to get Squid-2.7 to do TPROXY was obsoleted 5-10 years ago, including Squid-2.7. Finding people who even remember it is getting hard. You would do better to upgrade to TPROXYv4, which should be available in all modern Linux OS and is supported by current Squid-3 releases. http://wiki.squid-cache.org/Features/Tproxy4#Minimum_Requirements_.28IPv6_and_IPv4.29 If you really want to stick with the old version, good luck. The concepts outlined in the wiki page and Troubleshooting remain unchanged. Just the specific configuration details are very different. Amos -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJURfspAAoJELJo5wb/XPRj7aUIALPnNV3iI3vSKbGok9Kmtixj 2+KsKFVr+aebnZboMDOuWEBSmvXSc+jLMYtH8qacJXuJdRoN9ee8mKP6bZVDX7ZW IxcQrceQ3uX6JmINYU4ZKUoZYZwgotUBTj84d+CVEzvwbSNyauqCNpnbRBHdDLSp CZbDAYNF+eqym+I9FmARL2KrEY/cOU1c4sdSdl8llDq6qWwFp9i0CGNjVpU1yC2X scrdYQ2mkdgAS+KqpGE88die6M2q0sOQr/Y9T3y9v27vAI+tk63UGHLYXB+V0E/F A/EjhCGD8djcPGqDm73mqZL/P6JaJvA0o4j01nQLKO3If0H4G3ACU2EDKTuWe9c= =vw+9 -END PGP SIGNATURE- ___ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
Re: [squid-users] squid 2.7 TPROXY not working
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 21/10/2014 7:36 p.m., saleh madi wrote: Hello Amos, Many thanks for your reply. Before two years I have tested squid 2.7 it's very stable and in the high http traffic request is very stable no crash. But for squid-3 I see too many different releases 3.0.x , 3.1.x, 3.2.x, 3.3.x and the current 3.4.x. What is the stable release in squid-3, that work with TPROXY and can carry more high http traffic request without crash in compare with squid 2.7 and In summary: The latest you can get (aka 3.4.8) The long answer: http://www.squid-cache.org/Versions/ has the answers you seek about what Squid versions are most current stable. That page says Stable releases - 3.4, clicking the 3.4 link goes to a page saying: Latest 3.4 series release - 3.4.8. (** we are having trouble with some of our mirror servers at present, please check the final page says 3.4.8. If not refresh or use west.squid-cache.org domain name. **) Squid-3 has many packages because we have a monthly release schedule. All releases with two dots (x.y.z) are considered production ready stable releases. For any x.y series the higher the z number the better. So ... most of the time you should pick the one with latest number at the time when installing (the versions and package download pages can help there). Then can choose to stay with it (aka stable unchanging) until something major requires an upgrade, or you can follow the releases and stay on top of all sorts of small issues. Each month in the announcement I try to highlight what sort of criteria you need to consider when deciding. As of today the current stable is Squid-3.4.8, and there is also a Squid-3.5.0.1 beta for people wanting to try out some cool new features from the upcoming 3.5 series. Regarding your Question: * all the Squid versions 3.2 or later can handle more traffic than what Squid-2.7 could. Performance is a constant topic of ongoing improvement. * all releases since the *minimum* Squid package number (3.1.*) named in the TPROXYv4 wiki page support TPROXYv4. what is alternative for COSS in squid-3 for small index object for the high http traffic request. * Rock storage type has replaced COSS. That is a feature added in Squid-3.2 series. Although be aware the Squid-3.2 to Squid-3.4 series rock storage is limited by shared-memory design to only store 32KB or smaller objects. This is sufficient for most use-cases. If you have some important need for 32KB sized objects to be in the Rock store, you will need to use the 3.5 series (currently beta) where that limit has been removed. Amos -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJURhOCAAoJELJo5wb/XPRjdggIAMrDu/ARrUhRCFMFbuivv5kU VKMpv/hbrZqPTwskpAVZxu8hFbUIko+CEzurLEcY2ybBlqX0HBsHqo2pGYLFC3As 4RqenWsF7jCeJIK9OhNMNLy3gNIQzcV6QVfRNG8PmspThhg9JOAj1r8tOuXUzB8q OrtNCyYQO8R5eYKB9nzniNzJLWYcEy6F1z1F5d7+SPGb3evORwxiHhpo1yGiqh+6 aqXwxLYZkE3hLB8JPXsGta5c4cMdU1YZSwTGgeJQER3+oszjJTXfQJt7mHDZSbcD 3Jc5Lk71NnatJGDh8nDUieiahkLwE56vK0WtrMVknGTP2UC+wD+lpDC2cj/5hHo= =N8xe -END PGP SIGNATURE- ___ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
Re: [squid-users] squid 2.7 TPROXY not working
Hello Amos, For squid 3.4.8, In the server we have 2xssd 240GB and 4XHDD 2000GB, Internet bandwidth 600Mbits and four squid instances, please what is the suggestion settings for cache_dir for SSD and HDD to cover the high http traffic request. Thank you and Best Regards, Saleh - Original Message - From: Amos Jeffries squ...@treenet.co.nz To: saleh madi saleh.m...@hadara.ps Cc: squid-users@lists.squid-cache.org Sent: Tuesday, October 21, 2014 10:04:18 AM Subject: Re: [squid-users] squid 2.7 TPROXY not working -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 21/10/2014 7:36 p.m., saleh madi wrote: Hello Amos, Many thanks for your reply. Before two years I have tested squid 2.7 it's very stable and in the high http traffic request is very stable no crash. But for squid-3 I see too many different releases 3.0.x , 3.1.x, 3.2.x, 3.3.x and the current 3.4.x. What is the stable release in squid-3, that work with TPROXY and can carry more high http traffic request without crash in compare with squid 2.7 and In summary: The latest you can get (aka 3.4.8) The long answer: http://www.squid-cache.org/Versions/ has the answers you seek about what Squid versions are most current stable. That page says Stable releases - 3.4, clicking the 3.4 link goes to a page saying: Latest 3.4 series release - 3.4.8. (** we are having trouble with some of our mirror servers at present, please check the final page says 3.4.8. If not refresh or use west.squid-cache.org domain name. **) Squid-3 has many packages because we have a monthly release schedule. All releases with two dots (x.y.z) are considered production ready stable releases. For any x.y series the higher the z number the better. So ... most of the time you should pick the one with latest number at the time when installing (the versions and package download pages can help there). Then can choose to stay with it (aka stable unchanging) until something major requires an upgrade, or you can follow the releases and stay on top of all sorts of small issues. Each month in the announcement I try to highlight what sort of criteria you need to consider when deciding. As of today the current stable is Squid-3.4.8, and there is also a Squid-3.5.0.1 beta for people wanting to try out some cool new features from the upcoming 3.5 series. Regarding your Question: * all the Squid versions 3.2 or later can handle more traffic than what Squid-2.7 could. Performance is a constant topic of ongoing improvement. * all releases since the *minimum* Squid package number (3.1.*) named in the TPROXYv4 wiki page support TPROXYv4. what is alternative for COSS in squid-3 for small index object for the high http traffic request. * Rock storage type has replaced COSS. That is a feature added in Squid-3.2 series. Although be aware the Squid-3.2 to Squid-3.4 series rock storage is limited by shared-memory design to only store 32KB or smaller objects. This is sufficient for most use-cases. If you have some important need for 32KB sized objects to be in the Rock store, you will need to use the 3.5 series (currently beta) where that limit has been removed. Amos -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJURhOCAAoJELJo5wb/XPRjdggIAMrDu/ARrUhRCFMFbuivv5kU VKMpv/hbrZqPTwskpAVZxu8hFbUIko+CEzurLEcY2ybBlqX0HBsHqo2pGYLFC3As 4RqenWsF7jCeJIK9OhNMNLy3gNIQzcV6QVfRNG8PmspThhg9JOAj1r8tOuXUzB8q OrtNCyYQO8R5eYKB9nzniNzJLWYcEy6F1z1F5d7+SPGb3evORwxiHhpo1yGiqh+6 aqXwxLYZkE3hLB8JPXsGta5c4cMdU1YZSwTGgeJQER3+oszjJTXfQJt7mHDZSbcD 3Jc5Lk71NnatJGDh8nDUieiahkLwE56vK0WtrMVknGTP2UC+wD+lpDC2cj/5hHo= =N8xe -END PGP SIGNATURE- ___ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
Re: [squid-users] squid 2.7 TPROXY not working
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 21/10/2014 9:32 p.m., saleh madi wrote: Hello Amos, For squid 3.4.8, In the server we have 2xssd 240GB and 4XHDD 2000GB, Internet bandwidth 600Mbits and four squid instances, please what is the suggestion settings for cache_dir for SSD and HDD to cover the high http traffic request. Is this a quad-core machine? Try a single Squid-3 instance with directive workers 4 in the config file, and same cache_dir layout you had for Squid-2. Using appropriate min-size/max-size changes for the 32KB limit of Rock dirs (actually use 32000 bytes limit to be safe). (If you want a squid.conf audit please post it.) Amos -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJURh8AAAoJELJo5wb/XPRjG4cH/2bcQ6MRr1+CjJNOWsqt7kkB TG6+nUZV7GV1LusUJ/1T+9xNiYlWvp2htONYMrf/LY12jWiAuG/sGjkdvK6wVt5z 4EjT6IQCO5xjNOxkLSPGCzF8azlLOO7Jnp+ZiHgYI8g5SdsM69zAjNi8LIXK+sDE 8sxLqO/Gf66m2RRTyv4nfqil+znR8p5vZ3O7kRy3L+3KduVrQiGof6FlKdmOtGwk JSeRMZri595JkOm38cttrSCmXm0z9ZFVB3pE1ZPzbebE6SMgMyOYpg+z83HG74lt erUBSXTQnw4/0Sp3QNdygFloZf+dK0TRM3grCoWRtDSFxk7v5mTQFyeqyWToWb4= =9UcO -END PGP SIGNATURE- ___ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
