Bad torrenting performance when using mirage-fw

[Euwiiwueir]

@Euwiiwueir

Perhaps the community can work up some guidelines for NAT table sizing and memory assignment for mirage-fw qubes of different use cases. It’s common to include multiple firewall qubes in a netvm topology; some of them could be the standard 5000/32 and others sized up for their expected purpose.

FYI, I kicked this off over here:

Mirage-firewall memory assignment

Following on from: Here, to start, are some lightly tested mirage firewall configurations that have been working well for me. Use case: firewall qube as netvm for LAN-only utilities: qvm-prefs sys-m-firewall-lan memory 32 (i.e. the recommended default) I use this firewall to isolate access to the 192.168.*.* subnet. It’s only for intra-LAN ssh and configuring my router over its web admin frontend. Use case: firewall qube as netvm for several light-use WAN browser qubes: qvm-prefs sys-m-f…