search

danielmilner / netprofiles

Automatically exported from code.google.com/p/netprofiles
0 stars 0 forks source link

Wireless profile selection keeps changing profile #2

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Netprofiles is supposed to "automatically activate wireless profiles when
specified wireless connections are detected." While the detection does
work, netprofiles then tries to set the profile again every few seconds.

What steps will reproduce the problem?
1. Activate SSID discovery
2. Be in the reach of a known SSID

What is the expected output? What do you see instead?
Expected: Discover SSID -> set corresponding profile -> done
Seen: Deoscpver SSID -> set profile -> set profile -> set profile -> ...

What version of the product are you using? On what operating system?
2.1.5 on XP, SP3

Please provide any additional information below.

Original issue reported on code.google.com by potofcoffee@gmail.com on 15 May 2009 at 6:30

GoogleCodeExporter commented 9 years ago 
Identified the problem:

In sub GetConnectedSSIDs(), globals.vb, lines 515ff:

line 540 tries to exclude packet schedulers:
If Not (TheName.Contains("Packet Scheduler") then ...

However, packet schedulers might be named differently, especially in non-English
Windows versions (mine is named "Paketplaner" in German XPSP3). So, for the 
moment, I
fixed this by adding two more keywords (Miniport and Paketplaner). However, this
might still not work for all systems and languages.

Does anybody know of a way to recognize packet schedulers programmatically 
without
having to include a large list of keywords?

This fix is in SVN.

Original comment by potofcoffee@gmail.com on 15 May 2009 at 8:29

GoogleCodeExporter commented 9 years ago 
Just found a better solution:
NP now exludes packet schedulers by querying WMI for physical network adapters. 
This
solution is language-independent.

Fix is in SVN.

Original comment by potofcoffee@gmail.com on 18 May 2009 at 2:01

GoogleCodeExporter commented 9 years ago 
I trust that potofcoffe's fix works as I did not experience this problem 
personally.

Original comment by dmil...@gmail.com on 22 May 2009 at 7:50