-
Notifications
You must be signed in to change notification settings - Fork 27
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
No discover protocol packets captured even other tools work on this host. #29
Comments
Please run Get-Module to verify that you are using PSDiscoveryProtocol 1.4.3. |
@AlpSantoGlobalMomentumLLC, did you find out what version you are on? |
@AlpSantoGlobalMomentumLLC |
@AlpSantoGlobalMomentumLLC |
What you see in Wireshark is DTP frames. Not CDP or LLDP. Don’t know why the other tool is able to capture the LLDP frames. Are you able to capture LLDP with Wireshark? |
@AlpSantoGlobalMomentumLLC
You can also try to use Convert lldp_test.etl to pcapng and open in Wireshark. Still no LLDP? |
@AlpSantoGlobalMomentumLLC |
@AlpSantoGlobalMomentumLLC
|
@AlpSantoGlobalMomentumLLC In PSDiscoveryProtocol I use the NetEventSession cmdlets that are built into Windows. I'm afraid there is nothing else I can do to help. If you need to be able to capture LLDP using NetEventSession cmdlets you will have to ask Microsoft for help. Maybe they can explain why tcpdump is able to capture while the builtin tools fail. |
Hello,
first of all. THANK YOU for sharing!
fFor some reasons it doesn't work on every Server.
I have for example 2 Windows Server with multiple NW Cards and it don't work for some.
Even other tools are capable to read the LLDP Infos.
Any ideas, how we could find out the root cause together?
The text was updated successfully, but these errors were encountered: