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

Doesn't detect AC networks #1

Closed
EionRobb opened this issue Jul 13, 2014 · 9 comments
Closed

Doesn't detect AC networks #1

EionRobb opened this issue Jul 13, 2014 · 9 comments
Assignees

Comments

@EionRobb
Copy link

Hi there,

Wireless-AC networks just show up as 802.11 instead of 802.11ac which is how they show in the netsh command.

I tried looking for where the netsh command is parsed to see if it was just looking for one letter after the 802.11, but couldn't see where that code lives.

@acalcutt
Copy link
Owner

Vistumbler uses native wifi mode by default, so its results may not match
netsh by default. You can switch to netsh mode ( Uncheck Options --> Use
Native Wifi ) and the results should match netsh output.

Scanning code is located in Vistumbler.au3. For example. in the latest
stable release here (
https://github.com/RIEI/Vistumbler/blob/master/VistumblerMDB/Vistumbler.au3
) look for "Func _ScanAccessPoints()" on line 1784. If native wifi mode is
enable it runs the code on line 1788. If netsh mode is enabled it runs the
code on line 1916.

As for why native wifi mode does not display "802.11ac" I think it would
relate to "_Wlan_GetNetworkInfo" in "UDFs\NativeWifi.au3". This is a
function in a UDF written by another person that uses the microsoft native
wifi api. I looked at this function and found it uses "DOT11_PHY_TYPE" (
http://msdn.microsoft.com/en-us/library/windows/desktop/ms706015(v=vs.85).aspx).
There is a not on this page that a 802.11ac value was added in 8.1 and
server 2012...are you running one of these operating systems?

@EionRobb
Copy link
Author

Ah right, I did find the native wifi mode after I posted the issue, but
assumed that it wasn't used as everything else seemed to point to setting
up netsh

I am indeed using Windows 8.1

On 14 July 2014 14:44, acalcutt [email protected] wrote:

Vistumbler uses native wifi mode by default, so its results may not match
netsh by default. You can switch to netsh mode ( Uncheck Options --> Use
Native Wifi ) and the results should match netsh output.

Scanning code is located in Vistumbler.au3. For example. in the latest
stable release here (
https://github.com/RIEI/Vistumbler/blob/master/VistumblerMDB/Vistumbler.au3
) look for "Func _ScanAccessPoints()" on line 1784. If native wifi mode is
enable it runs the code on line 1788. If netsh mode is enabled it runs the
code on line 1916.

As for why native wifi mode does not display "802.11ac" I think it would
relate to "_Wlan_GetNetworkInfo" in "UDFs\NativeWifi.au3". This is a
function in a UDF written by another person that uses the microsoft native
wifi api. I looked at this function and found it uses "DOT11_PHY_TYPE" (

http://msdn.microsoft.com/en-us/library/windows/desktop/ms706015(v=vs.85).aspx
).
There is a not on this page that a 802.11ac value was added in 8.1 and
server 2012...are you running one of these operating systems?

Reply to this email directly or view it on GitHub
https://github.com/RIEI/Vistumbler/issues/1#issuecomment-48860987.

@acalcutt
Copy link
Owner

Netsh mode used to be the default mode, so that is why so much points to
netsh. Native wifi mode was made default in Vistumbler 10.3.

Based on your patch it looks like you found the cause of this problem. I
will try it out and merge it in if everything goes well.

-Andrew

On Sun, Jul 13, 2014 at 11:14 PM, Eion Robb [email protected]
wrote:

Ah right, I did find the native wifi mode after I posted the issue, but
assumed that it wasn't used as everything else seemed to point to setting
up netsh

I am indeed using Windows 8.1

On 14 July 2014 14:44, acalcutt [email protected] wrote:

Vistumbler uses native wifi mode by default, so its results may not match
netsh by default. You can switch to netsh mode ( Uncheck Options --> Use
Native Wifi ) and the results should match netsh output.

Scanning code is located in Vistumbler.au3. For example. in the latest
stable release here (

https://github.com/RIEI/Vistumbler/blob/master/VistumblerMDB/Vistumbler.au3
) look for "Func _ScanAccessPoints()" on line 1784. If native wifi mode
is
enable it runs the code on line 1788. If netsh mode is enabled it runs
the
code on line 1916.

As for why native wifi mode does not display "802.11ac" I think it would
relate to "_Wlan_GetNetworkInfo" in "UDFs\NativeWifi.au3". This is a
function in a UDF written by another person that uses the microsoft
native
wifi api. I looked at this function and found it uses "DOT11_PHY_TYPE" (

http://msdn.microsoft.com/en-us/library/windows/desktop/ms706015(v=vs.85).aspx
).
There is a not on this page that a 802.11ac value was added in 8.1 and
server 2012...are you running one of these operating systems?

Reply to this email directly or view it on GitHub
https://github.com/RIEI/Vistumbler/issues/1#issuecomment-48860987.


Reply to this email directly or view it on GitHub
https://github.com/RIEI/Vistumbler/issues/1#issuecomment-48862013.

@acalcutt
Copy link
Owner

I compiled the native wifi patch in the beta branch, but I don't have any
802.11ac access points to test with.

Can you give this beta vistumbler a try (
https://github.com/RIEI/Vistumbler/raw/beta/VistumblerMDB/Vistumbler.exe ).
Just replace your Vistumbler.exe with this one (or you can checkout the
beta branch on github)

On Mon, Jul 14, 2014 at 7:46 AM, Andrew Calcutt [email protected]
wrote:

Netsh mode used to be the default mode, so that is why so much points to
netsh. Native wifi mode was made default in Vistumbler 10.3.

Based on your patch it looks like you found the cause of this problem. I
will try it out and merge it in if everything goes well.

-Andrew

On Sun, Jul 13, 2014 at 11:14 PM, Eion Robb [email protected]
wrote:

Ah right, I did find the native wifi mode after I posted the issue, but
assumed that it wasn't used as everything else seemed to point to setting
up netsh

I am indeed using Windows 8.1

On 14 July 2014 14:44, acalcutt [email protected] wrote:

Vistumbler uses native wifi mode by default, so its results may not
match
netsh by default. You can switch to netsh mode ( Uncheck Options --> Use
Native Wifi ) and the results should match netsh output.

Scanning code is located in Vistumbler.au3. For example. in the latest
stable release here (

https://github.com/RIEI/Vistumbler/blob/master/VistumblerMDB/Vistumbler.au3
) look for "Func _ScanAccessPoints()" on line 1784. If native wifi mode
is
enable it runs the code on line 1788. If netsh mode is enabled it runs
the
code on line 1916.

As for why native wifi mode does not display "802.11ac" I think it would
relate to "_Wlan_GetNetworkInfo" in "UDFs\NativeWifi.au3". This is a
function in a UDF written by another person that uses the microsoft
native
wifi api. I looked at this function and found it uses "DOT11_PHY_TYPE" (

http://msdn.microsoft.com/en-us/library/windows/desktop/ms706015(v=vs.85).aspx
).
There is a not on this page that a 802.11ac value was added in 8.1 and
server 2012...are you running one of these operating systems?

Reply to this email directly or view it on GitHub
https://github.com/RIEI/Vistumbler/issues/1#issuecomment-48860987.


Reply to this email directly or view it on GitHub
https://github.com/RIEI/Vistumbler/issues/1#issuecomment-48862013.

@EionRobb
Copy link
Author

vistumbler 80211ac
Looking good :)

@acalcutt
Copy link
Owner

Great,

Now I just have to test that this still works with older versions of
windows...since that "dot11_phy_type_vht" was added in windows 8.1

On Wed, Jul 16, 2014 at 2:11 AM, Eion Robb [email protected] wrote:

[image: vistumbler 80211ac]
https://cloud.githubusercontent.com/assets/1063865/3595149/0da2213c-0cb0-11e4-92ef-619aa2380a69.PNG
Looking good :)


Reply to this email directly or view it on GitHub
https://github.com/RIEI/Vistumbler/issues/1#issuecomment-49127194.

@EionRobb
Copy link
Author

Did the change from #1 (comment) make its way in? Was the commit just not tagging this issue?

@acalcutt
Copy link
Owner

acalcutt commented Mar 10, 2021 via email

@acalcutt
Copy link
Owner

Just FYI, this looks like the commit it was added in. ffb1466#diff-04ff4e5936d2dd46946ec9a3d42e8955e1239cfbd7d2e4184dd9df1ca95eb5d6

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

3 participants