I'm actually running both squid and apt-cacher-ng. Squid uses
apt-cacher-ng internally as a parent, only for deb packages to save
bandwidth since apt-cacher handles that better than squid...and both
do it transparently.
Here is how it's supposed to work and was working earlier before I
upgraded to
Shorewall 4.5.6 RC 1 is now available for testing.
Problems corrected since Beta 4:
1) In the generated script, the logic for handling wildcard interfaces
with the 'wait=n' option was incorrect. For each matching interface,
the script would check its readiness n times in rapid
succes
On 7/4/12 11:50 AM, Tom Eastep wrote:
> On 7/4/12 11:35 AM, "Anshuman Aggarwal"
> wrote:
>
>> I have allowed port 80 to all users and the redirect works.
>>
>> Problem is I have a apt-cacher-ng proxy process which is run as
>> apt-cacher-ng with group apt-cacher-ng which proxies the debian
>> pac
On 7/4/12 11:35 AM, "Anshuman Aggarwal"
wrote:
>I have allowed port 80 to all users and the redirect works.
>
>Problem is I have a apt-cacher-ng proxy process which is run as
>apt-cacher-ng with group apt-cacher-ng which proxies the debian
>packages and which I want to access port 80 directly. Fo
On 7/4/12 11:25 AM, "Tom Eastep" wrote:
>On 7/4/12 7:23 AM, "Tom Eastep" wrote:
>
>>When I try that, I don't get a forwarding loop; but it doesn't work and
>>I'm seeing this:
>>
>>Jul 4 07:09:19 gateway fw-net REJECT IN= OUT=eth1 SRC=70.90.191.121
>>DST=127.0.0.1 LEN=60 TOS=00 PREC=0x00 TTL=64
I have allowed port 80 to all users and the redirect works.
Problem is I have a apt-cacher-ng proxy process which is run as
apt-cacher-ng with group apt-cacher-ng which proxies the debian
packages and which I want to access port 80 directly. For this process
to be excluded, I made its primary grou
On 7/4/12 7:23 AM, "Tom Eastep" wrote:
>On 07/04/2012 03:33 AM, Anshuman Aggarwal wrote:
>> Hi,
>> I have the following rules to transparently redirect all port 80
>> traffic (including that originating on the firewall itself) to my
>> firewall+proxy server while not going into a redirect loop
On 07/04/2012 03:33 AM, Anshuman Aggarwal wrote:
> Hi,
> I have the following rules to transparently redirect all port 80
> traffic (including that originating on the firewall itself) to my
> firewall+proxy server while not going into a redirect loop for the
> processes running on the server its
Hi,
I have the following rules to transparently redirect all port 80
traffic (including that originating on the firewall itself) to my
firewall+proxy server while not going into a redirect loop for the
processes running on the server itself (by excluding using !:group).
However, a local process r
