- This topic has 5 replies, 2 voices, and was last updated 1 year, 8 months ago by
.
-
Posts
-
Starting Wireguard tunnel…
Trying to make Wireguard tunnel network private…
Make Wireguard tunnel network private:
StdOut : ”
StdErr: ‘Get-NetConnectionProfile : ?? ???? ?? ??? ???? ?? ?? ??? ??????.
At line:1 char:19
+ $NetworkProfile = Get-NetConnectionProfile -InterfaceAlias “wiresock”
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (MSFT_NetConnectionProfile:root/StandardCi…nnectionProfile) [Get-NetConn
ectionProfile], CimException
+ FullyQualifiedErrorId : MI RESULT 1,Get-NetConnectionProfileThe property ‘NetworkCategory’ cannot be found on this object. Verify that the property exists and can be set.
At line:2 char:1
+ $NetworkProfile.NetworkCategory = “Private”
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [], RuntimeException
+ FullyQualifiedErrorId : PropertyNotFoundSet-NetConnectionProfile : Cannot validate argument on parameter ‘InputObject’. The argument is null. Provide a valid v
alue for the argument, and then try running the command again.
At line:3 char:41
+ Set-NetConnectionProfile -InputObject $NetworkProfile
+ ~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (:) [Set-NetConnectionProfile], ParameterBindingValidationException
+ FullyQualifiedErrorId : ParameterArgumentValidationError,Set-NetConnectionProfile‘
Err: exit status 1To the best of my recollection, there was a similar issue on Windows 7, although it did not impact the overall functionality of Wiresock VPN Gateway. However, configuring the VPN network adapter as a private network (which failed according to your log) can often provide greater convenience and ease of use.
With this in mind, may I kindly inquire as to which operating system you are currently using?
In addition, I am also considering the possibility of opening the source code for wg-quick-config to facilitate the analysis of such issues in the future. By making the source code more accessible and transparent, it will be easier for users to understand and diagnose potential issues, as well as contribute to the development of the project.
BTW,is it any quick method or tools to detect if the ISP blocks UDP or not,since some ISP may block the UDP protocol so wireguard won’t work at all.It would be nice to do so before to install wireguard.
It’s Windows Server 2016 X64
It is peculiar, but configuring the Network Category to Private can be beneficial, although it is not required.
BTW,is it any quick method or tools to detect if the ISP blocks UDP or not,since some ISP may block the UDP protocol so wireguard won’t work at all.It would be nice to do so before to install wireguard.
One possible solution to test whether UDP is blocked or not is to use performance measurement tools such as iperf3. These tools can help to determine if there are any issues with network performance that could be impacting the use of UDP. By conducting these tests prior to installing Wireguard, you can proactively identify any potential issues and take appropriate steps to address them.
- You must be logged in to reply to this topic.