Shoreline Firewall is an iptables-based firewall for Linux systems

Edit Package shorewall

The Shoreline Firewall, more commonly known as "Shorewall", is a Netfilter
(iptables) based firewall that can be used on a dedicated firewall system,
a multi-function gateway/ router/server or on a standalone GNU/Linux system.

Refresh
Refresh
Source Files
Filename Size Changed
0001-remote_fs.patch 0000000548 548 Bytes
0001-required-stop-fix.patch 0000000617 617 Bytes
README.openSUSE 0000000879 879 Bytes
shorewall-4.4.22.rpmlintrc 0000000682 682 Bytes
shorewall-4.5.10.tar.bz2 0000430224 420 KB
shorewall-core-4.5.10.tar.bz2 0000066306 64.8 KB
shorewall-docs-html-4.5.10.tar.bz2 0004019919 3.83 MB
shorewall-init-4.5.10.tar.bz2 0000047906 46.8 KB
shorewall-init-4.5.2-install.patch 0000000684 684 Bytes
shorewall-lite-4.5.10.tar.bz2 0000061224 59.8 KB
shorewall.changes 0000068822 67.2 KB
shorewall.spec 0000024932 24.3 KB
shorewall6-4.5.10.tar.bz2 0000218067 213 KB
shorewall6-lite-4.5.10.tar.bz2 0000060684 59.3 KB
Revision 38 (latest revision is 125)
Stephan Kulow's avatar Stephan Kulow (coolo) accepted request 144824 from Togan Muftuoglu's avatar Togan Muftuoglu (toganm) (revision 38)
- Update to 4.5.10 For more details see changelog.txt and
  releasenotes.txt
  * This release includes all defect repair included in
    4.5.9.1-4.5.9.3.
  * Under rare circumstances, optimize level 16 could produce
    invalid iptables-restore input which would cause start/restart
    to fail.
  * Before this release, the 'started' script was run prior to
    copying the temporary script file (e.g., /var/lib/shorewall/.start)
    to /var/dir/shorewall/firewall. If the script failed, the copy
    would not take place even though the firewall had started
    successfully. The script is now copied before running the
    'started' script.
    If you compare the script generated by this release with one
    generated by a prior release, We suggest that you ignore
    whitespace changes (e.g., use the '-w' option in diff); that way,
    you can see the actual change more clearly.
  * AUTOCOMMENT=No now works correctly; previously, it behaved the
    same as AUTOCOMMENT=Yes.
  * A harmless extraneous comma has been deleted from the rule
    generated by action.RST. (forwarded request 144821 from toganm)
Comments 0
openSUSE Build Service is sponsored by