Displaying 3 results from an estimated 3 matches for "loc2fw_exists".
2002 May 14
4
Redirect loc::80 to fw::3128 not work
...------------------------------------
net Net Internet Blixer
loc Local Rete Locale Ivrea
dmz DMZ Demilitarized zone
@@@@@@@ this is a portions of debug of shorewall script ...
+ iptables -A loc2fw -m state --state ESTABLISHED,RELATED -j ACCEPT
+ eval loc2fw_exists=Yes
++ loc2fw_exists=Yes
+ ''['' www = none -o www = None -o '''' = none -o '''' = None -o '''' = none -o ''''
= No
ne -o '''' = none -o '''' = None '']''
++ separate_list...
2002 May 14
3
[Shorewall-users] Redirect loc::80 to fw::3128 not work (fwd)
...------------------------------------
net Net Internet Blixer
loc Local Rete Locale Ivrea
dmz DMZ Demilitarized zone
@@@@@@@ this is a portions of debug of shorewall script ...
+ iptables -A loc2fw -m state --state ESTABLISHED,RELATED -j ACCEPT
+ eval loc2fw_exists=Yes
++ loc2fw_exists=Yes
+ ''['' www = none -o www = None -o '''' = none -o '''' = None -o '''' = none -o ''''
= No
ne -o '''' = none -o '''' = None '']''
++ separate_list...
2003 Mar 23
12
Shorewall 1.4.1
This is a minor release of Shorewall.
WARNING: This release introduces incompatibilities with prior releases.
See http://www.shorewall.net/upgrade_issues.htm.
Changes are:
a) There is now a new NONE policy specifiable in
/etc/shorewall/policy. This policy will cause Shorewall to assume that
there will never be any traffic between the source and destination
zones.
b) Shorewall no longer