Formula to set up and configure ufw
Table of Contents
See the full SaltStack Formulas installation and usage instructions.
If you are interested in writing or contributing to formulas, please pay attention to the Writing Formula Section.
If you want to use this formula, please pay attention to the FORMULA
file and/or git tag
,
which contains the currently released version. This formula is versioned according to Semantic Versioning.
See Formula Versioning Section for more details.
Commit message formatting is significant!!
Please see :ref:`How to contribute <CONTRIBUTING>` for more details.
Installs and configures the ufw package.
Installs the ufw package.
This state manages the file ufw.conf
under /etc/ufw
(template found in "ufw/files"). The configuration is populated by values in "ufw/map.jinja" based on the package's default values (and RedHat, Debian, Suse and Arch family distribution specific values), which can then be overridden by values of the same name in pillar.
All the configuration for the firewall is done via pillar (pillar.example).
Enable firewall, applying default configuration:
ufw:
enabled: True
Allow 80/tcp (http) traffic from only two remote addresses:
ufw: services: http: protocol: tcp from_addr: - 10.0.2.15 - 10.0.2.16
Allow 443/tcp (https) traffic from network 10.0.0.0/8 to an specific local ip:
ufw: services: https: protocol: tcp from_addr: - 10.0.0.0/8 to_addr: 10.0.2.1
Allow from a service port:
ufw: services: smtp: protocol: tcp
Allow from an specific port, by number:
ufw: services: 139: protocol: tcp
Allow from a range of ports, udp:
ufw: services: "10000:20000": protocol: udp
Allow from a range of ports, tcp and udp
ufw: services: "10000:20000/tcp": to_port: "10000:20000" protocol: tcp "10000:20000/udp": to_port: "10000:20000" protocol: udp
Allow from two specific ports, udp:
ufw: services: "30000,40000": protocol: udp
Allow an application defined at /etc/ufw/applications.d/:
ufw: applications: - OpenSSH
Linux testing is done with kitchen-salt
.
Creates the docker instance and runs the template
main state, ready for testing.
Runs the inspec
tests on the actual instance.
Removes the docker instance.
Runs all of the stages above in one go: i.e. destroy
+ converge
+ verify
+ destroy
.
Gives you SSH access to the instance for manual testing.