Displaying 7 results from an estimated 7 matches for "forward_clear_mark".
2010 Oct 23
0
Shorewall 4.4.14 RC 1
RC 1 is now available for testing.
Problems corrected:
1) All sample .conf files have been changed to specify
FORWARD_CLEAR_MARK=
rather than
FORWARD_CLEAR_MARK=Yes
That way, systems without MARK support will still be able to
install the sample configurations and FORWARD_CLEAR_MARK will
default to Yes on systems with MARK support.
2) The install scripts in the tarballs now correctly create init...
2010 Oct 23
0
Shorewall 4.4.14 RC 1
RC 1 is now available for testing.
Problems corrected:
1) All sample .conf files have been changed to specify
FORWARD_CLEAR_MARK=
rather than
FORWARD_CLEAR_MARK=Yes
That way, systems without MARK support will still be able to
install the sample configurations and FORWARD_CLEAR_MARK will
default to Yes on systems with MARK support.
2) The install scripts in the tarballs now correctly create init...
2012 May 08
19
Shorewall, TPROXY, Transparent Squid and Multiples ISP
Hello,
I wonder if someone could use the TPROXY with Shorewall and
transparent Squid with using the routing rules on shorewall
(tcrules) for hosts / networks (LAN) with multiples providers (WANs)
directly from the internal network on port 80 (with TPROXY
transparent squid or REDIRECT).
On this issue, the routing rules is not work propertly because the
source is the
2010 Jul 09
0
Shorewalll 4.4.11 RC 1
RC 1 is now available for testing. This version corrects several
problems in Beta 3:
1) Release notes now correctly refer to FORWARD_CLEAR_MARK rather than
CLEAR_FORWARD_MARK.
2) The NET3 column in /etc/shorewall/netmap now works correctly.
3) A missing closing quote in the generated script when using
REQUIRE_INTERFACE=Yes has been corrected.
4) The compiler now correctly detects the "fwmark route mask" capability.
In additio...
2010 Jul 09
0
Shorewalll 4.4.11 RC 1
RC 1 is now available for testing. This version corrects several
problems in Beta 3:
1) Release notes now correctly refer to FORWARD_CLEAR_MARK rather than
CLEAR_FORWARD_MARK.
2) The NET3 column in /etc/shorewall/netmap now works correctly.
3) A missing closing quote in the generated script when using
REQUIRE_INTERFACE=Yes has been corrected.
4) The compiler now correctly detects the "fwmark route mask" capability.
In additio...
2013 Jun 13
3
"Multiple Internet Connections" with four interfaces
Hi,
I was reading document http://shorewall.net/MultiISP.html#idp3634200.
Inspired by the document I was trying to establish the following changes:
* one additional interface: COMA_IF
* COM[A,B,C]_IF interfaces request IP address via DHCP
* all non-RFC 1918 destined trafic is NATed from INT_IF to COMA_IF
* all non-RFC 1918 destined trafic from GW is routed via COMB_IF by default
* non-RFC 1918
2013 Sep 10
6
lsm configuration issues...
...lter
ADD_IP_ALIASES=Yes
ADD_SNAT_ALIASES=No
ADMINISABSENTMINDED=Yes
AUTO_COMMENT=Yes
AUTOMAKE=No
BLACKLISTNEWONLY=Yes
CLAMPMSS=No
CLEAR_TC=Yes
COMPLETE=No
DELETE_THEN_ADD=Yes
DETECT_DNAT_IPADDRS=No
DISABLE_IPV6=Yes
DONT_LOAD=
DYNAMIC_BLACKLIST=Yes
EXPAND_POLICIES=Yes
EXPORTMODULES=Yes
FASTACCEPT=No
FORWARD_CLEAR_MARK=
IMPLICIT_CONTINUE=Yes
IPSET_WARNINGS=Yes
IP_FORWARDING=On
KEEP_RT_TABLES=No
LEGACY_FASTSTART=Yes
LOAD_HELPERS_ONLY=No
MACLIST_TABLE=filter
MACLIST_TTL=
MANGLE_ENABLED=Yes
MAPOLDACTIONS=No
MARK_IN_FORWARD_CHAIN=No
MODULE_SUFFIX=ko
MULTICAST=No
MUTEX_TIMEOUT=60
NULL_ROUTE_RFC1918=No
OPTIMIZE=0
OPTIM...