From f4d95fd9b9478724816b9679880ae6ab49a72598 Mon Sep 17 00:00:00 2001 From: Dimitri Papadopoulos <3234522+DimitriPapadopoulos@users.noreply.github.com> Date: Thu, 21 Jan 2021 14:08:55 +0100 Subject: [PATCH] Assign an IPv4 address from the link-local subnet While the 192.0.2.0/24 TEST-NET-1 block would avoid collisions, the 169.254.0.0/16 subnet described in RFC3927 has precisely been specified precisely for such cases. We should probably select "an address using a pseudo-random number generator with a uniform distribution in the range from 169.254.1.0 to 169.254.254.255 inclusive", as described in RFC3927. However, that would of course require more code and I'm lazy, but more importantly it had been reported that FortiClient uses 169.254.2.1. I'd rather use the same address as FortiClient. --- src/tunnel.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/tunnel.c b/src/tunnel.c index b384b2a3..2e9b7738 100644 --- a/src/tunnel.c +++ b/src/tunnel.c @@ -233,7 +233,7 @@ static int pppd_run(struct tunnel *tunnel) static const char *const v[] = { ppp_path, "230400", // speed - ":192.0.2.1", // : + ":169.254.2.1", // : "noipdefault", "noaccomp", "noauth",