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

Use Network List Manager 1.0 Type Library? #3

Open
raspi opened this issue Apr 26, 2016 · 0 comments
Open

Use Network List Manager 1.0 Type Library? #3

raspi opened this issue Apr 26, 2016 · 0 comments

Comments

@raspi
Copy link
Owner

raspi commented Apr 26, 2016

Currently all adapters are looped through and LLDP packets are sent to those adapters which are up and are not loopback devices.

Control Panel -> All Control Panel Items -> Network and Sharing Center uses Network List Manager which you can listen to and it emits events like "Cable is plugged in".

If you go and see for example VMware player virtual adapter in Network and Sharing Center you can see these these:

  • Connection
    • IPv4 Connectivity: No network access
    • IPv6 Connectivity: No network access
    • Media State: Enable
    • Duration: 1 day 01:00:00
    • Speed: 100.0 Mbps

And still my virtual machine in bridged mode in VMWare player works fine and can send it's own LLDP packets.

So why use it?

Notice the IPv4 Connectivity: No network access and IPv6 Connectivity: No network access.

Now all adapters that are up have also that Media State: Enable. But in reality they are not really up, because those adapters do not have IPv4/IPv6 connectivity.

So by using Network List Manager all adapters could be dropped from the looped list which do not have actual working IPv4 and/or IPv6 connectivity.

You can also get the adapter uptime from using this also instead of using for example whole machine's uptime. This could information could be added to Port Description field.

Found via https://stackoverflow.com/a/28415777/71964

Next question is, which Windows versions supports this or is there other ways to remove "fake" adapters.

You can list physical adapters with WMI but it's slow and there are some minor and sometimes major differences between Windows version when querying information via WMI. So I wouldn't count it as reliable source.

@raspi raspi added this to the Future milestone May 2, 2016
@raspi raspi self-assigned this May 2, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant