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

Show disabled interfaces #169

Closed
delirium26 opened this issue Jan 29, 2019 · 4 comments
Closed

Show disabled interfaces #169

delirium26 opened this issue Jan 29, 2019 · 4 comments

Comments

@delirium26
Copy link

Unfortunately GetAllNetworkInterfaces() function doesn't list disabled interfaces.
I almost done this feature with wmi Query. Soon I`ll can do pull request.
Also, did we need ability to enable/disable interface in Interface Configuration tab? It seems pretty usefull for me.

@BornToBeRoot
Copy link
Owner

Disable/Enable a network adapter would be great.

Changing a network adapter (disable/enable) requires administrative rights. I would call a PowerShell as Admin with a command to enable/disable the adapter. (like the interface configuration)

Thus NETworkManager itself does not have to be started as admin.

https://github.com/BornToBeRoot/NETworkManager/blob/99f7a44ccf76827200110992a84dd97b99536c82/Source/NETworkManager/Utilities/PowerShellHelper.cs

Via netsh.exe or Windows 10 has build in PowerShell commands to do this:
Get-NetAdapter
Enable-NetAdapter
Disable-NetAdapter


Once .NET Core 3 (or .NET Framework 4.8) is released, i want to migrate the project (there is already a pull request) and start with Version 2.0.0.0

This has the advantage that we can use the Windows 10 API (aka WinRT).

  • NativeWiFi --> Show/Configure WiFi Networks

Maybe there are new functions for the network adapters...

But... Windows 7, 8.1 are no longer supported then...

@delirium26
Copy link
Author

delirium26 commented Jan 30, 2019

Changing a network adapter (disable/enable) requires administrative rights. I would call a PowerShell as Admin with a command to enable/disable the adapter. (like the interface configuration)
Thus NETworkManager itself does not have to be started as admin.
https://github.com/BornToBeRoot/NETworkManager/blob/99f7a44ccf76827200110992a84dd97b99536c82/Source/NETworkManager/Utilities/PowerShellHelper.cs

I just thought about it yesterday, thanks for the tip.

But... Windows 7, 8.1 are no longer supported then...

It's a pity. I use Windows 10 almost everywhere. But according to this http://gs.statcounter.com/windows-version-market-share/desktop/worldwide the percentage of windows 10 usage is slightly above 50%.
Also it will impossible to run on Windows Server 2008 R2?

Anyway, long time I wanted develop tool like NetworkManager, but a little bit lightweighted. So it another cause to do it.

@BornToBeRoot
Copy link
Owner

It won't run on Server 2008 R2... but you can still download the latest version 1.9.x.x which can run under Windows 7 / 2008 R2.

Only newer features requires Windows 10...

@BornToBeRoot
Copy link
Owner

@delirium26

I added a button "Network connections..." which opens Control Panel > Network and Internet > Network Connections

image

If no adapter is enabled, this message is shown on all tabs:

image

The status of this pages are changing as soon as a network adapter is enabled/disabled.

If you want, you can still add the feature to disable/enable a adapter...

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

2 participants