| Age | Commit message (Collapse) | Author |
|---|
|
Shorewall in jessie doesn't come with a proper unit file, and
as a result, it doesn't properly start with systemd.
To solve this, we provide the systemd unit file that comes with stretch,
add a systemd submodule that provides the exec resources needed for when
systemd units or configuration files are changed
Change-Id: I861fa951835928b4741abfbf969adcee4b8f147b
|
|
took out the last remaining virtualbox references
|
|
its configuration file (#3701)
Change-Id: Ib2dad30d53e5bf7539762eb3683430b10eb875ed
|
|
cases when shorewall doesn't properly come up, ensuring that it fails safe (#3339)
Change-Id: Id4f0bf6cf25f420aa2ad67635b37ae95f54e3d38
|
|
variables that are used in different places
to start with we setup the $interface variable, based on logic as defined in #2213
change the various places that were looking up this value to use site_config::params::interface instead
|
|
|
|
site_shorewall::defaults can be used on every host, it configures
a basic firewall, which blocks everything from outside except
ping + ssh, and allows outgoing traffic for http, git, dns.
|
|
|
|
from the shorewall-rules manpage:
"If no Section Headers appear in the file then all rules are assumed to be in the NEW section."
|
|
|
|
|
|
|
|
|
