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

[xfl12345]

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]

And it can not PING echo other.

[yabinma]

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]

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]

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

[xfl12345]

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

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]

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]

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.