Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wireguard Client IP invalid #1075

Closed
k6ccc opened this issue Jan 22, 2024 · 2 comments
Closed

Wireguard Client IP invalid #1075

k6ccc opened this issue Jan 22, 2024 · 2 comments
Labels

Comments

@k6ccc
Copy link

k6ccc commented Jan 22, 2024

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...

@k6ccc k6ccc added the bug Something isn't working label Jan 22, 2024
@aanon4
Copy link
Contributor

aanon4 commented Jan 23, 2024

Can you confirm the problem is fixed in the nightly?

@k6ccc
Copy link
Author

k6ccc commented Jan 23, 2024 via email

@aanon4 aanon4 closed this as completed Jan 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants