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

[Bug]: v0.24.1 netclient for windows amd64 report IPv6 address as endpoints IPv4 address #2947

Open
1 task done
xfl12345 opened this issue May 17, 2024 · 8 comments
Open
1 task done
Assignees
Labels
bug Something isn't working

Comments

@xfl12345
Copy link

Contact Details

[email protected]

What happened?

Make client use IPv6 Only network.

Version

v0.24.1

What OS are you using?

Windows

Relevant log output

No response

Contributing guidelines

  • Yes, I did.
@xfl12345 xfl12345 added the bug Something isn't working label May 17, 2024
@xfl12345
Copy link
Author

netmaker_0 24 1_ipv6_only_bug_4
netmaker_0 24 1_ipv6_only_bug_3
netmaker_0 24 1_ipv6_only_bug_2
netmaker_0 24 1_ipv6_only_bug_1

@xfl12345
Copy link
Author

And it can not PING echo other.

@yabinma
Copy link
Collaborator

yabinma commented May 17, 2024

ipv4 field shows ipv6 address is an known issue and it's fixed already.
Your netclient a brand new install? Or upgrade from old version?

@xfl12345
Copy link
Author

ipv4 field shows ipv6 address is an known issue and it's fixed already. Your netclient a brand new install? Or upgrade from old version?

Is the new install one.

@yabinma
Copy link
Collaborator

yabinma commented May 17, 2024

have not re-produced the issue, UI show properly address as shown,
image

@xfl12345
Copy link
Author

xfl12345 commented May 17, 2024

have not re-produced the issue, UI show properly address as shown, image

OK... I can offer some re-produced details...
First. Make the client working under dual-stack network. (Would be better to run the command netclient pull)
Second. Disable the IPv4 protocol of the net card which is used for surfing Internet. (Would be better to run the command netclient pull once again)

BUG will happen.

@yabinma
Copy link
Collaborator

yabinma commented May 17, 2024

OK. If disabling IPv4 is after the installation, it would be good to run a restart(winsw restart netclient on Windows). pull might not be able to recognize all the system changes. Try a restart or install the netclient after ipv4 is disabled.

@yabinma
Copy link
Collaborator

yabinma commented May 17, 2024

I reproduced the issue, the ipv4 field shows an ipv6 address, after ipv4 is disabled and then a restart followed. A PR is opened for the fix.

@xfl12345 xfl12345 changed the title [Bug]: v0.24.1 netclient for windows amd64 report IPv6 address as endpoint IPv4 address [Bug]: v0.24.1 netclient for windows amd64 report IPv6 address as endpoint's IPv4 address May 17, 2024
@xfl12345 xfl12345 changed the title [Bug]: v0.24.1 netclient for windows amd64 report IPv6 address as endpoint's IPv4 address [Bug]: v0.24.1 netclient for windows amd64 report IPv6 address as endpoints IPv4 address May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants