mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-09-19 22:21:27 +00:00
afbd1bb89e
The iptables backend (which was used as the model for the nftables backend) used the same "filter" and "nat" tables used by other services on the system (e.g. firewalld or any other host firewall management application), so it was possible that one of those other services would be blocking DNS, DHCP, or TFTP from guests to the host; we added our own rules at the beginning of the chain to allow this traffic no matter if someone else rejected it later. But with nftables, each service uses their own table, and all traffic must be acepted by all tables no matter what - it's not possible for us to just insert a higher priority/earlier rule that will override some reject rule put in by, e.g., firewalld. Instead the firewalld (or other) table must be setup by that service to allow the traffic. That, along with the fact that our table is already "accept by default", makes it possible to eliminate the individual accept rules for DHCP, DNS, and TFTP. And once those rules are eliminated, there is no longer any need for the guest_to_host or host_to_guest tables. Signed-off-by: Laine Stump <laine@redhat.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com> |
||
|---|---|---|
| .. | ||
| base.iptables | ||
| base.nftables | ||
| nat-default-linux.iptables | ||
| nat-default-linux.nftables | ||
| nat-default.xml | ||
| nat-ipv6-linux.iptables | ||
| nat-ipv6-linux.nftables | ||
| nat-ipv6-masquerade-linux.iptables | ||
| nat-ipv6-masquerade-linux.nftables | ||
| nat-ipv6-masquerade.xml | ||
| nat-ipv6.xml | ||
| nat-many-ips-linux.iptables | ||
| nat-many-ips-linux.nftables | ||
| nat-many-ips.xml | ||
| nat-no-dhcp-linux.iptables | ||
| nat-no-dhcp-linux.nftables | ||
| nat-no-dhcp.xml | ||
| nat-tftp-linux.iptables | ||
| nat-tftp-linux.nftables | ||
| nat-tftp.xml | ||
| route-default-linux.iptables | ||
| route-default-linux.nftables | ||
| route-default.xml | ||