-
Notifications
You must be signed in to change notification settings - Fork 13
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
Not support Teaming #25
Comments
Hi @raspi any update on this issue? |
Unfortunately I lack the network gear for testing LAGG stuff. |
Here is the function which I collect this information using ansible
|
@raspi I have many machines with multiple NICs can test for you. someone got the same issue too: |
In C++, I used the GetIfTable2 function to get a list of all interfaces. |
Submission type
Used version of operating system
In case of bug report: Is machine connected to Active Directory?
In case of bug report: Version the issue has been seen with
In case of bug report: Capture library used
In case of bug report: PowerShell information
PowerShell version used
What are your execution policies?
In case of bug report: Expected behaviour you didn't see
In case of bug report: Steps to reproduce the problem
Where is the problem:
problem in the WinLLDPService/LLDPBase/Base.cs file line 66
The physical interfaces included in the LAG do not have NetworkInterfaceComponent.IPv * components.
Only the "Microsoft Network Adapter Multiplexor Protocol" is enabled, in addition to npcap
In case of bug report: Additional details
The text was updated successfully, but these errors were encountered: