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
group 'proxy' and changed the init
script so it launched the process with the group as 'proxy' . still
the redirect loop is happening for this apt-cacher-ng process
Thanks,
Anshuman
On 4 July 2012 19:53, Tom Eastep teas...@shorewall.net wrote:
On 07/04/2012 03:33 AM, Anshuman Aggarwal wrote:
Hi
compressed shore wall dump
Thanks,
Anshuman
On 5 July 2012 03:08, Tom Eastep teas...@shorewall.net wrote:
On 7/4/12 11:50 AM, Tom Eastep wrote:
On 7/4/12 11:35 AM, Anshuman Aggarwal anshuman.aggar...@gmail.com
wrote:
I have allowed port 80 to all users and the redirect works.
Problem is I
Reply-To: Shorewall Users shorewall-users@lists.sourceforge.net
Anshuman Aggarwal wrote:
I have the following setup
ISP1ISP2
||
Shorewall Shorewall
Server 1 --Server 2
10.0.0.1 10.0.0.2
All,
I'd appreciate any suggestions for my Multi Isp setup outlined below.
I have the following setup
ISP1ISP2
||
Shorewall Shorewall
Server 1 --Server 2
10.0.0.1 10.0.0.2
\ /
LAN
I
Hi,
Is there a shore wall rule (or iptables fallback) that will allow block a
user from connecting to the listening ports of another user on the fire
walled machine itself.
I've successfully blocked a user from connecting to any local ports on the
firewall itself using but I want the user to be
