buscseik/wifitools

A set of tools that can simplify handle Wi-Fi profiles, connection. Also additional tools that closely related to networking and Wi-Fi.

wifitools's Issues

Check if Wifi Profile SSID is Hidden

Maybe add another additional property for it.

Get-PublicIP does not work since the API it uses is no longer available: ipv4bot.whatismyipaddress.com

Calling 'Get-PublicIP' results in an exception (see error record below).

Module used 1.8.3
Platform used: Windows PowerShell 5.1 running on Win10 64-bit 21H2

Exception : System.Net.WebException: The remote name could not be resolved: 'ipv4bot.whatismyipaddress.com' at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.GetResponse(WebRequest request) at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.ProcessRecord() TargetObject : System.Net.HttpWebRequest CategoryInfo : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebException FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand ErrorDetails : InvocationInfo : System.Management.Automation.InvocationInfo ScriptStackTrace : at Get-PublicIP, C:\Program Files\WindowsPowerShell\Modules\WifiTools\1.8.3\WifiTools.ps1: line 258 at <ScriptBlock>, <No file>: line 1 PipelineIterationInfo : {} PSMessageDetails :

See WhatIsMyIPAddress's explanation for the removal of their API service(s): https://whatismyipaddress.com/api

Importing module give error The term 'Import-WifiProfiles' is not recognized as the name of a cmdlet, function, script file,

When I import this module on my system, I get this error message

Import-WifiProfiles : The term 'Import-WifiProfiles' is not recognized as the name of a cmdlet, function, script file,
or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and
try again.

Error importing on Powershell 7

Running Install-Module wifitools -scope currentuser gives:

Install-Package: C:\program files\powershell\7\Modules\PowerShellGet\PSModule.psm1:9685
Line |
9685 |  … talledPackages = PackageManagement\Install-Package @PSBoundParameters
     |                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | The following commands are already available on this system:'Join-String'. This module 'WifiTools' may
     | override the existing commands. If you still want to install this module 'WifiTools', use -AllowClobber
     | parameter.

I don't see any reference to Join-String in your script, so maybe this is a powershell bug, but I thought I'd start here.

Connect-WiFi(): It does not connect to all WiFi Profiles

Good evening

Thank you very much for your work and Tools!,
it's a real shame that M$ is not supporting you / is not offering this kind of Library.

Connect-WiFi(): It does not connect to all WiFi Profiles

If we use Get-WifiProfiles() to list all Profiles, then we get two Profiles listed.
But Connect-WiFi() connects only to one profile, on the other, it displays an Argument Validation Exception:

Connect-WiFi : Cannot validate argument on parameter 'ProfileName'. 
The argument "xxx" does not belong to the set "yyy" specified by the ValidateSet attribute. 
Supply an argument that is in the set and then try the command again.
+ Connect-WiFi -ProfileName xxx
+                           ~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidData: (:) [Connect-WiFi], ParameterBindingValidationException
    + FullyQualifiedErrorId : ParameterArgumentValidationError,Connect-WiFi

It would be very useful if Connect-WiFi() could be used to connect to all available WiFi profiles.

Thanks a lot, kind regards,
Thomas

Can't script connection to profile created with module

Running Win10 22H2, PowerShell 5.1.

2023-06-15_17:07:18 -06:00 [kurt.buff @ ITKURT2LT] C:\scripts

create-wifiprofile -wlanname MyWifi -passwd -wpa

Profile MyWifi is added on interface LaptopWi-Fi.

2023-06-15_17:07:43 -06:00 [kurt.buff @ ITKURT2LT] C:\scripts

connect-wifi -profilename MyWifi -interfacename laptopwi-fi

The network specified by profile "MyWifi" is not connectible.
Reason: Capability matching failed at profile (auth not found).

2023-06-15_17:08:01 -06:00 [kurt.buff @ ITKURT2LT] C:\scripts

connect-wifi -profilename MyWifi

There is no such wireless interface on the system.

2023-06-15_17:09:01 -06:00 [kurt.buff @ ITKURT2LT] C:\scripts
list-wifiprofiles

Profiles on interface LaptopWi-Fi:

Group policy profiles (read only)

<None>

User profiles

All User Profile     : MyWifi

I tried creating and connecting to profiles on both Meraki and Cambium WAPs, with the same result each time.

If I manually make the connection in the GUI, I can use connect-wifi to disconnect and reconnect with the profile.

I also tried disabling and enabling the interface, but that didn't change the outcome.

Am I missing a switch, or using any of the commands incorrectly?

Thanks,
Kurt

anyway this can support creating wifi profile of WPA2-enterprise profile with PEAP

anyway this can support creating wifi profile of WPA2-enterprise profile with PEAP? it seems there appears to be no way to so without using the native windows GUI?

Scan-WifiAps should let you specify InterfaceName as a parameter

'netsh wlan show networks' can accept interface as a parameter so it should be possible.

Not sure if there are issues making it work with the forced scan.

Thanks for your great tool.