Dustin b83e832df9 roles/dch-gw: Explicitly accept forwarded ports ... Marking packets matching port-forwarding rules, and then allowing traffic carrying that mark did not seem to work well. Often, packets seemed to get dropped for no apparent reason, and outside connections to NAT'd services was sometimes slow as a result. Explicitly listing every destination host/port in the `forward` table seems to resolve this issue.		2018-04-06 20:13:03 -05:00
..
forward.nft.j2	roles/dch-gw: Explicitly accept forwarded ports	2018-04-06 20:13:03 -05:00
incoming.nft.j2	roles/dch-gw: Configure the filter table	2018-03-29 10:06:30 -05:00
masquerade.nft.j2	dch-gw: Initial commit	2018-03-27 20:44:43 -05:00
outgoing.nft.j2	roles/dch-gw: Configure the filter table	2018-03-29 10:06:30 -05:00
port-forwards.nft.j2	roles/dch-gw: Explicitly accept forwarded ports	2018-04-06 20:13:03 -05:00
reject.nft.j2	roles/dch-gw: Configure the filter table	2018-03-29 10:06:30 -05:00