You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have four Wireguard tunnels set on on my tunnel server. The first three are working properly, but the forth one is not. That forth one is showing a client IP of 172.31.231.254:5528. It appears that the WG tunnels are using a /31 address since each one is two IPs higher than the previous - so that may in fact be valid. However as I said, it is not working.
It gets better however. The next tunnel I set up is showing an Client IP of 172.31.231.256:5529. Last time I checked, .256 is not valid at all in IPv4...
The text was updated successfully, but these errors were encountered:
-----Original Message-----
From: "Tim Wilkinson" ***@***.***>
Sent: Monday, January 22, 2024 20:27
To: "aredn/aredn" ***@***.***>
Cc: "Jim Walls" ***@***.***>, "Author" ***@***.***>
Subject: Re: [aredn/aredn] Wireguard Client IP invalid (Issue #1075)
Can you confirm the problem is fixed in the nightly?
--
Reply to this email directly or view it on GitHub:
#1075 (comment)
You are receiving this because you authored the thread.
Message ID: ***@***.***>
I have four Wireguard tunnels set on on my tunnel server. The first three are working properly, but the forth one is not. That forth one is showing a client IP of 172.31.231.254:5528. It appears that the WG tunnels are using a /31 address since each one is two IPs higher than the previous - so that may in fact be valid. However as I said, it is not working.
It gets better however. The next tunnel I set up is showing an Client IP of 172.31.231.256:5529. Last time I checked, .256 is not valid at all in IPv4...
The text was updated successfully, but these errors were encountered: