Wireshark

  • Riverbed Technology
  • WinPcap
the world's foremost network protocol analyzer
  • Wireshark
    • About
    • Download
    • Blog
  • Get Help
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Bug Tracker
  • Develop
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds

Wireshark-dev: [Wireshark-dev] Analyze winpcap packets

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next


From: "Cedric Droin" <cedric.droin@xxxxxxxxxxx>
Date: Mon, 2 Oct 2006 11:42:24 +0200

Hi,
I'm currently trying to get and analyze the packets received on the Ethernet lynk of my PC. I've found "WinPCap Labview 0_6" on the National instrument website and it seems to work well as far as I know.
As I'd like to  automize the analysis of the packets with LabVIEW, I have to be able to "traduce" the 152 characters length word provided by this VI (ex : 01005e00000700163857cf3208004560054cdaf800001b11fcf30a45c908ef0000070e4513890538e95f8021e400bbdc65a2d1575dc24701271ac2241d53c7d66854e36d8c0fb0ffa4fc8a24).
My knowledge concerning packet and everything around IP is poor so I'd be grateful if someone could help me to get the packet info from this word as Ethereal can do (source, destination, protocol, length, info). 
 
Maybe DLLs are available...?

Thank you in advance for your answer.

 

 
  • Follow-Ups:
    • Re: [Wireshark-dev] Analyze winpcap packets
      • From: Gilbert Ramirez
  • Prev by Date: Re: [Wireshark-dev] [Wireshark-commits] rev 19372: /trunk/ /trunk/: Makefile.nmake
  • Next by Date: [Wireshark-dev] Tools Menu not available without HAVE_LUA_5_1
  • Previous by thread: Re: [Wireshark-dev] [Wireshark-commits] rev 19372: /trunk/ /trunk/: Makefile.nmake
  • Next by thread: Re: [Wireshark-dev] Analyze winpcap packets
  • Index(es):
    • Date
    • Thread

Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation