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]: Win 10 and 11 differences in getCurrentConnections #176

Open
2 tasks done
juanmartin opened this issue Jan 20, 2022 · 0 comments
Open
2 tasks done

[Bug]: Win 10 and 11 differences in getCurrentConnections #176

juanmartin opened this issue Jan 20, 2022 · 0 comments

Comments

@juanmartin
Copy link

Expected behavior

getCurrentConnections is inconsistent across different Windows versions.

Current behavior

Currently it returns the key/value mixed up:

See the output of .getCurrentConnections():
The odd one to me is the one coming from win11. win10 makes more sense.

Windows 11:

win11-get

Windows 10:

win10-get


This is the output of netsh wlan show interfaces for each version:

Windows 11:

win10

Windows 10:

win11

Which are the affected features

  • node API
  • CLI

Which is your operating system?

Windows

Environment

Windows 11 and 10.

Version of node-wifi

2.0.16

Steps to Reproduce

See the output of netsh wlan show interfaces
See the output of .getCurrentConnections()

Solutions

Maybe parsing the results differently according to the OS.
I see there's a difference in the number of results for the netsh command so maybe that's the issue as it offsets the parsing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant