search

chall32 / LDWin

Link Discovery for Windows
404 stars 51 forks source link

No packets #2

Closed gramoerpsel closed 10 years ago

gramoerpsel commented 10 years ago

I tried this tool with Win7 (64 x) on a HP EliteBook (different models). In any possibility it says that it can't get pakets. I do not know why... Is there any logfile or erorr messages to search in? What can I do?

chall32 commented 10 years ago

It's possible that the network switch you are connected to is not broadcasting any link discovery data. If that is the case then LDWin will not pick up any data to display.

chall32 commented 10 years ago

Please can you try https://github.com/chall32/LDWin/wiki/What-To-Do-If-LDWin-Captures-No-Data and letting me have the returned data?

Thanks

gramoerpsel commented 10 years ago

I am sure that the switch is casting LLDP information and when I do a tcp dump I get it. I enclose the output of the tcp dump. (Replaced the Sys-name, IP address and MAC address with <>, they were correct)

tcpdump: listening on \Device{ABE23CEF-F489-4E87-9FF4-A900E2240817} 07:34:03.601768 LLDP, length 163 Chassis ID TLV (1), length 7 Subtype MAC address (4): <> Port ID TLV (2), length 3 Subtype Local (7): 44 Time to Live TLV (3), length 2: TTL 120s Port Description TLV (4), length 2: 44 System Name TLV (5), length 17: <> System Description TLV (6), length 87 ProCurve J9089A Switch 2610-48-PWR, revision R.11.98, ROM R.10.06 (/sw/code/build/nemo) System Capabilities TLV (7), length 4 System Capabilities Bridge, Router Enabled Capabilities Bridge Management Address TLV (8), length 12 Management Address length 5, AFI IPv4 (1): <> Interface Index Interface Numbering (2): 0 Organization specific TLV (127), length 9: OUI IEEE 802.3 Private (0x00120f) MAC/PHY configuration/status Subtype (1) autonegotiation supported, enabled PMD autoneg capability 10BASE-T hdx, 10BASE-T fdx, 100BASE-TX hdx, 100BASE-TX fdx MAU type 100BASETX fdx (0x0010) End TLV (0), length 0 1 packet captured 678 packets received by filter 0 packets dropped by kernel

chall32 commented 10 years ago

Thank you for the tcpdump info.

I've tracked down the LLDP detection problem and have double checked that LDWin will detect and return the tcpdump info correctly. To this end, I've just released a new version, v2.1 that I hope will work for you.

Please feel free to go ahead and test again using LDWin v2.1 and let me know if it works OK for you.

As always, feedback is much appreciated!

gramoerpsel commented 10 years ago

Yeah! Now it works fine! Thank you very mutch for your help. :) Only of curiosity: what was the problem? (If you want to tell...)

chall32 commented 10 years ago

Excellent! No problem! Thank you for sticking with me and testing again with the updated version! The issue was a simple fix. Some how I had left out the LLDP detection part from the tcpdump.exe command line. A silly mistake that had somehow crept in between v1.0 & v2.0... Anyway, all fixed now.

Thanks again.