Shoreline Firewall is an iptables-based firewall for Linux systems
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.
- Developed at security:netfilter
- Sources inherited from project openSUSE:Factory
-
2
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout home:seife:Factory/shorewall && cd $_ - Create Badge
Refresh
Refresh
Source Files
| Filename | Size | Changed |
|---|---|---|
| README.openSUSE | 0000000879 879 Bytes | |
| init-4.4.14.patch | 0000000966 966 Bytes | |
| shorewall-4.4.22.rpmlintrc | 0000000682 682 Bytes | |
| shorewall-4.5.4.tar.bz2 | 0000394431 385 KB | |
| shorewall-core-4.5.4.tar.bz2 | 0000049401 48.2 KB | |
| shorewall-docs-html-4.5.4.tar.bz2 | 0003808879 3.63 MB | |
| shorewall-init-4.4.21_init_sh.patch | 0000000656 656 Bytes | |
| shorewall-init-4.5.2-install.patch | 0000000838 838 Bytes | |
| shorewall-init-4.5.4.tar.bz2 | 0000031892 31.1 KB | |
| shorewall-lite-4.5.2-init.patch | 0000001016 1016 Bytes | |
| shorewall-lite-4.5.4.tar.bz2 | 0000045695 44.6 KB | |
| shorewall.changes | 0000048807 47.7 KB | |
| shorewall.spec | 0000018167 17.7 KB | |
| shorewall6-4.5.2-init.patch | 0000001049 1.02 KB | |
| shorewall6-4.5.4.tar.bz2 | 0000188583 184 KB | |
| shorewall6-lite-4.5.2-init.patch | 0000001023 1023 Bytes | |
| shorewall6-lite-4.5.4.tar.bz2 | 0000045116 44.1 KB |
Revision 22 (latest revision is 125)
Stephan Kulow (coolo)
accepted
request 122613
from
Togan Muftuoglu (toganm)
(revision 22)
- Update to 4.5.4 For more details see changelog.txt and
releasenotes.txt
* When EXPORTMODULES=No in shorewall.conf, the error messages
have been eliminated
* If the configuration settings in the PACKET MARK LAYOUT section
of shorewall.conf (shorewall6.conf) had empty settings, the
'update' command would previously set them to their default
settings. It now leaves them empty.
* Previously, Shorewall used 'unreachable' routes to null-route
the RFC1918 subnets. This approach has two drawbacks:
- It can cause problems for IPSEC in that it can cause packets
to be rejected rather than encrypted and forwarded.
- It can return 'host unreachable' ICMPs to other systems that
attempt to route RFC1918 addresses through the firewall.
To eliminate these problems, Shorewall now uses 'blackhole'
routes.
Such routes don't interfere with IPSEC and silently drop
packets rather than return an ICMP.
* The 'default' routing table is now cleared if there are no
'fallback' providers.
* Tproxy implementation has been reworked. For more details
please consult the releasenotes.txt and changelog.txt
Comments 0