| 1 |
# FAQ |
| 2 |
|
| 3 |
## GNOME |
| 4 |
|
| 5 |
NetworkManager supports dynamically [mapping](config/section/zone.md) connections |
| 6 |
with firewall zones but graphical connection editor GNOME Control Center |
| 7 |
doesn't. There are two alternative ways to edit connections with zone support: |
| 8 |
|
| 9 |
* Use graphical `nm-connection-editor` (recommended) |
| 10 |
* Use command line `nmcli connection modify <connection-name> connection.zone <zone-name>` |
| 11 |
|
| 12 |
This needs to be done only when changing firewall zone for connection. All |
| 13 |
other edits can be done with GNOME Control Center. |
| 14 |
|
| 15 |
|
| 16 |
## DHCP |
| 17 |
|
| 18 |
To obtain an IP address with DHCP you must allow both outgoing `dhcp-server` |
| 19 |
request and incoming `dhcp-client` reply. Example: |
| 20 |
|
| 21 |
``` |
| 22 |
localhost-public { |
| 23 |
# Allow localhost's DHCP client to send a request to a DHCP server running |
| 24 |
# on public zone (discover/request a lease). |
| 25 |
dhcp-server |
| 26 |
dhcpv6-server |
| 27 |
} |
| 28 |
|
| 29 |
public-localhost { |
| 30 |
# Allow reply packet from public's DHCP server to localhost's client |
| 31 |
# (offer an IP address). |
| 32 |
dhcp-client |
| 33 |
dhcpv6-client |
| 34 |
} |
| 35 |
``` |
| 36 |
|
| 37 |
Similar rules are required if you run DHCP server on `localhost` serving IP |
| 38 |
leases to your `internal` zone clients: |
| 39 |
|
| 40 |
``` |
| 41 |
internal-localhost { |
| 42 |
# Allow incoming DHCP discover/request from internal's client to |
| 43 |
# DHCP server running on localhost. |
| 44 |
dhcp-server |
| 45 |
dhcpv6-server |
| 46 |
} |
| 47 |
|
| 48 |
localhost-internal { |
| 49 |
# Allow localhost's DHCP server to send an offer reply to internal's client. |
| 50 |
dhcp-client |
| 51 |
dhcpv6-client |
| 52 |
} |
| 53 |
``` |
| 54 |
|
| 55 |
|
| 56 |
## Proxy ARP |
| 57 |
|
| 58 |
See [discussions](https://github.com/FoobarOy/foomuuri/discussions/2) |
| 59 |
how to configure proxy ARP with Foomuuri using [hooks](config/section/hook.md). |
| 60 |
|
| 61 |
|
| 62 |
## Hairpin NAT / NAT Loopback |
| 63 |
|
| 64 |
See [issues](https://github.com/FoobarOy/foomuuri/issues/8) how to configure |
| 65 |
hairpin NAT with Foomuuri using [snat](config/section/snat.md) and |
| 66 |
[dnat](config/section/dnat.md). |
| 67 |
|
| 68 |
Usually it is better to do split DNS instead of hairpin NAT. Split DNS has |
| 69 |
locally served zone with local IP addresses and publicly served zone with |
| 70 |
public IP addresses. |
| 71 |
|
| 72 |
|
| 73 |
## fail2ban |
| 74 |
|
| 75 |
Foomuuri supports automatic IP address |
| 76 |
[banning](example/advanced.md#automatic-ip-address-banning) without any |
| 77 |
external programs. This is usually enough, no `fail2ban` is needed. Banning |
| 78 |
happens fully on packet path, native on nftables level. |
| 79 |
|
| 80 |
Alternatively, see [issues](https://github.com/FoobarOy/foomuuri/issues/9) |
| 81 |
how to integrate Foomuuri with `fail2ban` program. |
| 82 |
|
| 83 |
|
| 84 |
## Custom nftables chains |
| 85 |
|
| 86 |
See [discussions](https://github.com/FoobarOy/foomuuri/discussions/31) |
| 87 |
how to define custom nftables chains and how to jump to them. |
| 88 |
|
| 89 |
|
| 90 |
## QEMU/libvirt and vnet interfaces in a bridge |
| 91 |
|
| 92 |
See [discussions](https://github.com/FoobarOy/foomuuri/discussions/15) how |
| 93 |
to silently drop `OUTPUT REJECT IN= OUT=vnetXX` log entries. These lines |
| 94 |
are logged after bridge interface is added or removed. |
| 95 |
|
| 96 |
|
| 97 |
## Don't route private networks to public internet |
| 98 |
|
| 99 |
See [issues](https://github.com/FoobarOy/foomuuri/issues/24) how to block |
| 100 |
routing 10.0.0.0/8 and similar private networks to public internet. |