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.

Sign up for GitHub

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

Jump to bottom

Improve/Fix WiFi Channels #366

Closed
3 of 4 tasks
BornToBeRoot opened this issue Nov 15, 2020 · 3 comments · Fixed by #418
Closed
3 of 4 tasks

Improve/Fix WiFi Channels #366

BornToBeRoot opened this issue Nov 15, 2020 · 3 comments · Fixed by #418
Labels
🎨 design 🐛 bug 🔍 need-more-infos 🚀 feature-request

Comments

@BornToBeRoot
Copy link
Owner

BornToBeRoot commented Nov 15, 2020 •
edited
Loading

Follow up #365 @terrorfisch

  • The y-axis is wrong. It 0dBm is more than -100dBm. This leads to weaker signals being plotted more prominently (besides being unphysical)
  • Channels 64 and 100 overlap in the plot although there is a gap in the frequency band.
  • The bandwidth is ignored. Some (older) 5GHz access points only use 20MHz.
  • There are issues when multiple APs habe the same SSID. I did not investigate it yet further.
@BornToBeRoot
Copy link
Owner Author

@terrorfisch

  1. I reversed the x-axis (and all data inside the view 😄)
  2. There is now some space between channel 64 and 100
  3. If you hover over the line of a channel, you will see a tooltip with all networks using this channel. This was already available.

image

What do you mean by "bandwidth is ignored"? Some apps/wifi tools display a possible bandwith like 180 Mbit/s. I don't know if/how you can caluclate it and it's not availabe in the api i am using: https://docs.microsoft.com/en-us/uwp/api/windows.devices.wifi.wifiavailablenetwork

BornToBeRoot added a commit that referenced this issue Dec 28, 2020
@BornToBeRoot
#366 - Fix y-axis, add space between channel 64 and 100
d4165a0
@BornToBeRoot BornToBeRoot mentioned this issue Dec 28, 2020
Merged
BornToBeRoot added a commit that referenced this issue Dec 28, 2020
@BornToBeRoot
Fix some WiFi - Channel issues #366 (#418)
37036a5 
* Fix 64 and 100 overlapping

* #366 - Fix y-axis, add space between channel 64 and 100

Co-authored-by: BornToBeRoot <BornToBeRoot@users.noreply.github.com>
@BornToBeRoot BornToBeRoot reopened this Dec 28, 2020
@BornToBeRoot
Copy link
Owner Author

BornToBeRoot commented Dec 28, 2020 •
edited
Loading

Preview:

Url: https://cloud.borntoberoot.net/s/sMCWRA5QMp4jRkd
PW: 2020Issue#366

Update will be in the next release.

@BornToBeRoot
Copy link
Owner Author

So i looked into the bandwith and i think i know what you mean. There are differences between 20, 40 and 80 mhz.

It's currently not possible to get this information from the Windows API (Windows.Devices.WiFi). I also looked into other apps like WiFi Analyzer (UWP App in the Microsoft Store) and they also don't provide this info, because it's not possible to get it ;(

If Microsoft updates the API i will implement it.

Currently I would leave it that way so that you can at least roughly see that the channels overlap. I will add this to the documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🎨 design 🐛 bug 🔍 need-more-infos 🚀 feature-request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix some WiFi - Channel issues #366 BornToBeRoot/NETworkManager
1 participant
@BornToBeRoot