search for: merge_host

...ld Ping Handling. There won''t be any ''noping'' or ''forwardping'' interface options and there won''t be a FORWARDPING option in shorewall.conf. b) ''routestopped'' interface and hosts option. Use the routestopped file instead. c) MERGE_HOSTS. The only behavior available will be what MERGE_HOSTS=Yes provides in 1.3. -Tom -- Tom Eastep \ Shorewall - iptables made easy Shoreline, \ http://www.shorewall.net Washington USA \ teastep@shorewall.net

The first 1.4.0 Beta is now available at: http://www.shorewall.net/pub/shorewall/Beta ftp://ftp.shorewall.net/pub/shorewall/Beta Function from 1.3 that has been omitted from this version includes: 1) The MERGE_HOSTS variable in shorewall.conf is no longer supported. Shorewall 1.4 behavior is the same as 1.3 with MERGE_HOSTS=Yes. 2. Interface names of the form <device>:<integer> in /etc/shorewall/interfaces now generate an error. 3. Shorewall 1.4 implements behavior consistent with...

Hi! I have just upgraded from version 1.3.2 to 1.3.13 and noticed some strange things. On interface eth2 I have 4 different addresses 192.168.11.0/24, 192.168.13.0/24, 192.168.102.0/24, 192.168.130.0/24 in version 1.3.2 loc zone is defined like this: loc eth2: 192.168.11.0/24, .. but in version 1.3.13 0.0.0.0/0 is added at the end on all zones and because of that for example machine in

...posed content -- I''m looking for a Beta to start in the next week or so with release around the middle of next month. The main focus of 1.4 will be to provide external behavior similar to the upcoming 2.0 release. Function from 1.3 that has been omitted from this version includes: 1) The MERGE_HOSTS variable in shorewall.conf is no longer supported. Shorewall 1.4 behavior is the same as 1.3 with MERGE_HOSTS=Yes. 2. Interface names of the form <device>:<integer> in /etc/shorewall/interfaces now generate an error. 3. Shorewall 1.4 implements behavior consistent with...

...andidate is now available at: http://www.shorewall.net/pub/shorewall/Beta ftp://ftp.shorewall.net/pub/shorewall/Beta The only change between Beta 1 and RC1 is that the ''check'' command is back in RC1. Function from 1.3 that has been omitted from this version includes: 1) The MERGE_HOSTS variable in shorewall.conf is no longer supported. Shorewall 1.4 behavior is the same as 1.3 with MERGE_HOSTS=Yes. 2) Interface names of the form <device>:<integer> in /etc/shorewall/interfaces now generate an error. 3) Shorewall 1.4 implements behavior consistent with OL...

...now detected in the rules file. It is a good idea to use the ''shorewall check'' command before you issue a ''shorewall restart'' command be be sure that you don''t have any configuration problems that will prevent a successful restart. 2. Added MERGE_HOSTS variable in shorewall.conf to provide saner behavior of the /etc/shorewall/hosts file. 3. The time that the counters were last reset is now displayed in the heading of the ''status'' and ''show'' commands. 4. Added MUTEX_TIMEOUT variable in shorewall.conf an...

The second Beta is now available at: http://www.shorewall.net/pub/shorewall/Beta ftp://ftp.shorewall.net/pub/shorewall/Beta Function from 1.3 that has been omitted from this version includes: 1) The ''check'' command is no longer supported. 2) The MERGE_HOSTS variable in shorewall.conf is no longer supported. Shorewall 1.4 behavior is the same as 1.3 with MERGE_HOSTS=Yes. 3) Interface names of the form <device>:<integer> in /etc/shorewall/interfaces now generate an error. 4) Shorewall 1.4 implements behavior consistent with OL...

It is my plan that the upcoming release of Shorewall (1.3.14) will definitely be the last of the 1.3.x releases and will very probably be the last release of Shorewall 1.x.x. I will continue to support Shorewall 1.3 but will be making no more enhancements to it. I will be devoting my time to Shorewall 2. If anyone is interested in taking over the development of Shorewall 1, please let me