wireguard-monolithic-historical/src/tools, branch master

wg-quick: linux: use already configured addresses instead of in-memory

2019-12-17T13:18:09Z

The ADDRESSES array might not have addresses added during PreUp. But moreover, nft(8) and iptables(8) don't like ip addresses in the form somev6prefix::someipv4suffix, such as fd00::1.2.3.4, while ip(8) can handle it. So by adding these first and then asking for them back, we always get normalized addresses suitable for nft(8) and iptables(8). Reported-by: Silvan Nagl

tools: adjust wg.8 syntax for consistency in COMMANDS section

2019-12-13T15:22:19Z

Signed-off-by: Kai Haberzettl

wg-quick: linux: try both iptables(8) and nft(8) on teardown

2019-12-12T16:24:04Z

Daniel argues that technically a package manager could install nft(8) after previously having started wg-quick(8) using iptables(8). Suggested-by: Daniel Kahn Gillmor

wg-quick: linux: support older nft(8)

2019-12-12T11:24:05Z

Older nft(8), such as that on Ubuntu, does not accept the - parameter to the -f argument and doesn't accept symbolic priority names. So instead use the canonical numeric priority forms and use <(echo) instead of -.

global: fix up spelling

2019-12-12T11:24:05Z

Signed-off-by: Josh Soref

wg-quick: linux: add support for nft and prefer it

2019-12-12T11:24:05Z

If nft(8) is installed, use it. These rules should be identical to the iptables-restore(8) ones, with the advantage that cleanup is easy because we use custom table names.

wg-quick: linux: ignore save warnings for iptables-nft

2019-12-06T15:51:05Z

wg-quick: linux: suppress more warnings on weird kernels

2019-12-06T15:22:18Z

wg-quick: linux: some iptables don't like empty lines

2019-12-05T17:33:18Z

Reported-by: Kenneth R. Crudup

wg-quick: linux: iptables-* -w is not widely supported

2019-12-05T10:48:25Z