search for: shorewallrc

Hi, My main gateway is a router running on OpenWrt Barrier Breaker r37816/ Kernel Version3.10.4. I installed shorewall-lite from openwrt''s repo using opkg but while trying to start shorewall-lite I get the folowing errors: The first error i got was "scp: /var/lib/shorewall-lite: No such file or directory" simply resolved by making the folder "shorewall-lite"

...) and shorewall6(8) manpages. 10) Some redundant interface-option rules have been removed in configurations with multiple zones configured on a single interface. 11) Previously, when compiling for export, the compilation would fail if the setting of SHAREDIR in the firewall''s shorewallrc was different from the setting on the admin system. Such compilations now succeed. ---------------------------------------------------------------------------- I I. K N O W N P R O B L E M S R E M A I N I N G -----------------------------------------------------------------...

...) and shorewall6(8) manpages. 10) Some redundant interface-option rules have been removed in configurations with multiple zones configured on a single interface. 11) Previously, when compiling for export, the compilation would fail if the setting of SHAREDIR in the firewall''s shorewallrc was different from the setting on the admin system. Such compilations now succeed. ---------------------------------------------------------------------------- I I. K N O W N P R O B L E M S R E M A I N I N G -----------------------------------------------------------------...

I''m attaching a few changes that are specific to Arch Linux and are motivated by our recent switch to systemd. System V init scripts are no longer used/supported on Arch Linux and, therefore, the Arch Linux init scripts can be removed from Shorewall. The two patches that follow are based against master; if it''s possible to apply them to the upcoming Shorewall 4.5.13 as well,

...l with a syntax error. 2) A typographical error in the usage text produced by the -h command in the compiled firewall script has been corrected. 3) The handling of INITSOURCE is now uniform between the standard and the -lite installers. 4) Previously, when SYSCONFFILE was specified in shorewallrc, the installers would always install default.debian rather than the named file. That has been corrected. ---------------------------------------------------------------------------- I I. K N O W N P R O B L E M S R E M A I N I N G -------------------------------------------...

Hi all, I''m tring to convert some manually written iptables rules into a shorewall configuration but I''m facing some issue with mode statistic. In our outgoing smtp we balance the source IP address of outgoing connections originating from the firewall between 4 alias configured on eth0 interface: eth0 inet addr:xxx.xxx.xxx.18 Bcast:xxx.xxx.xxx.255 Mask:255.255.255.0 eth0:1

...the kernel and iptables did not support the Recent Match ''--reap'' option. A new REAP_OPTION capability has been added to work around this issue. 2) The Shorewall-core installer no longer reports an error from ''cp'' stating that it could not stat the shorewallrc file. New Feature: 1) Support has been added to the Shorewall-core configure scripts and installer for Ubuntu Raring. Thank you for testing. -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like W...

...now avoids combining such rules. While this is a long-standing defect in the optimizer, it was exposed by changes in Shorewall 4.5.6. 4) There were several cases where hard-wired directory names appeared in the tarball installers. These have been replaced with the appropriate shorewallrc variables. 5) A defect in RHEL 6.3 and derivatives causes ''shorewall show capabilities'' to leave an empty ipset in the configuration. The same defect can cause the Shorewall compiler to similarly leave an empty ipset behind. This Shorewall release has a work...

RC 2 is ready for testing. Problems corrected: 1) The 4.5.1 Shorewall Lite and Shorewall6 Lite installers install the wrong SysV init script on Debian and derivatives. That has been corrected. 2) The getparams program now reads the installed shorewallrc file rather than ~/.shorewallrc. 3) The ''load'' and ''reload'' now copy the ''save'' file to the correct remote directory. Previously, the file was always copied to /etc/$PRODUCT/. 4) ?IF, ?ELSE and ?ENDIF now work within embedded She...

RC 2 is ready for testing. Problems corrected: 1) The 4.5.1 Shorewall Lite and Shorewall6 Lite installers install the wrong SysV init script on Debian and derivatives. That has been corrected. 2) The getparams program now reads the installed shorewallrc file rather than ~/.shorewallrc. 3) The ''load'' and ''reload'' now copy the ''save'' file to the correct remote directory. Previously, the file was always copied to /etc/$PRODUCT/. 4) ?IF, ?ELSE and ?ENDIF now work within embedded She...

...sting. Problems Corrected: 1) Previously, the Shorewall and Shorewall6 install.sh scripts did two things wrong with respect to the /etc/shorewall[6]/routes file: - The existing file was unconditionally removed. - A skeleton file was not installed when SPARSE was not set in the shorewallrc file. Additionally, the installer would remove /etc/shorewall[6]/tcstart. 2) The Shorewall-init install.sh script previously refused to replace /sbin/ifup-local and /sbin/ifdown-local when those files has been installed by an earlier version of Shorewall-init. New Features: 1) Pri...

...sting. Problems Corrected: 1) Previously, the Shorewall and Shorewall6 install.sh scripts did two things wrong with respect to the /etc/shorewall[6]/routes file: - The existing file was unconditionally removed. - A skeleton file was not installed when SPARSE was not set in the shorewallrc file. Additionally, the installer would remove /etc/shorewall[6]/tcstart. 2) The Shorewall-init install.sh script previously refused to replace /sbin/ifup-local and /sbin/ifdown-local when those files has been installed by an earlier version of Shorewall-init. New Features: 1) Pri...