fwbuilder
http://www.fwbuilder.org/
Firewall Builder is a GUI firewall configuration and management tool that supports iptables (netfilter), ipfilter, pf, ipfw, Cisco PIX (FWSM, ASA) and Cisco routers extended access lists. Firewall Builder uses object-oriented approach, it helps administrator maintain a database of network objects and allows policy editing using simple drag-and-drop operations.
- Devel package for openSUSE:Factory
-
2
derived packages
- Links to openSUSE:Factory / fwbuilder
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout security/fwbuilder && cd $_ - Create Badge
Refresh
Refresh
Source Files
| Filename | Size | Changed |
|---|---|---|
| _link | 0000000144 144 Bytes | |
| fwbuilder-5.3.6.tar.bz2 | 0005921241 5.65 MB | |
| fwbuilder-5.3.7.tar.gz | 0007332419 6.99 MB | |
| fwbuilder.changes | 0000006741 6.58 KB | |
| fwbuilder.default | 0000000156 156 Bytes | |
| fwbuilder.init | 0000005284 5.16 KB | |
| fwbuilder.service | 0000000326 326 Bytes | |
| fwbuilder.spec | 0000005269 5.15 KB |
Revision 26 (latest revision is 44)
Marcus Meissner (msmeissn)
accepted
request 450449
from
Christian Wittmer (computersalat)
(revision 26)
update to 5.3.7
Comments 5
why are the service files 'incompatible' ?
The files generated by fwbuilder are not compatible with openSUSE, as they include for instance routing rules. This conflicts with routing handled by openSUSE (/etc/sysconfig/network/).
it 'can' include, but that depends on config of 'Managing interfaces and addresses'. I did switch off interface handling by fwbuilder. And there is NO conflict.
It's a systemV script, instead of systemd. Still includes, for instance:
load_modules "nat " configure_interfaces verify_interfaces
Even tough these functions don't do anything, when the "Configure interfaces of the firewall machine" and "Add virtual interfaces for NAT" are disabled.
Regarding, the previous service script. The name is always a specific name. The script name fwbuilder like the gui, this conflicts.
I don't think that openSUSE should provide a systemd script yet.
Because a user will standard compile rules with network interface etc settings and the standard name is not automatically choosen. OpenSUSE is Linux distro that can be used by users without in depth Linux knowledge.
Therefore I don't want to add the script for now.
User without in depth Linux knowledge should not make use of fwbuilder and should not install the gui on the firewall itself. And how do you start the firewall no matter if the script set network settings or not ? What is your real problem ?