Chapter 19. Configuring Firewall-as-a-Service (FWaaS)
19.1. Overview of firewall-as-a-service (FWaaS)
The Firewall-as-a-Service (FWaaS) plug-in adds perimeter firewall management to OpenStack Networking (neutron). FWaaS uses iptables to apply firewall policy to all virtual routers within a project, and supports one firewall policy and logical firewall instance for each project.
FWaaS operates at the perimeter by filtering traffic at the OpenStack Networking (neutron) router. This distinguishes FWaaS from security groups, which operate at the instance level.
FWaaS is currently in Technology Preview; untested operation is not recommended. FWaaS is not available in future releases.
The following example diagram illustrates the flow of ingress and egress traffic for the VM2 instance:
Figure 1. FWaaS architecture
19.2. Enabling firewall-as-a-service (FWaaS)
Install the FWaaS packages:
# dnf install openstack-neutron-fwaas python-neutron-fwaas
Enable the FWaaS plugin in the
service_plugins = neutron.services.firewall.fwaas_plugin.FirewallPlugin
Configure FWaaS in the
[fwaas] driver = neutron.services.firewall.drivers.linux.iptables_fwaas.IptablesFwaasDriver enabled = True [service_providers] service_provider = LOADBALANCER:Haproxy:neutron_lbaas.services.loadbalancer.drivers.haproxy.plugin_driver.HaproxyOnHostPluginDriver:default
Enable the FWaaS dashboard management option in the local_settings.py file, usually located on the Controller node:
/usr/share/openstack-dashboard/openstack_dashboard/local/local_settings.py 'enable_firewall' = True
neutron-serverto apply the changes.
# systemctl restart neutron-server
19.3. Configuring firewall-as-a-service (FWaaS)
First, create the firewall rules and create a policy to contain them, then create a firewall and apply the policy:
Create a firewall rule:
$ neutron firewall-rule-create --protocol <tcp|udp|icmp|any> --destination-port <port-range> --action <allow|deny>
The CLI requires a protocol value. If the rule is protocol agnostic, you can use the value
Create a firewall policy:
$ neutron firewall-policy-create --firewall-rules "<firewall-rule IDs or names separated by space>" myfirewallpolicy
The order of the rules that you specify in the
neutron firewall-policy-createcommand is important. You can create an empty firewall policy and add rules later, either with the update operation (when adding multiple rules) or with the insert-rule operations (when adding a single rule).
FWaaS always adds a default deny all rule at the lowest precedence of each policy. Consequently, a firewall policy with no rules blocks all traffic by default.
19.4. Creating firewalls
openstack security group createcommand, to create a firewall:
$ openstack security group create <firewall-policy-uuid>
The firewall remains in
PENDING_CREATE state until you create an OpenStack Networking router and attach an interface.