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-users: Re: [Wireshark-users] [TCP Previous segment lost], TCP [TCP Dup ACK 125#1]

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


From: Nikolai Longolius <longolius@xxxxxxxxxxxxxx>
Date: Tue, 8 Sep 2009 15:23:03 +0200

Martin + Jeffrey,

thanks for your quick response. In the meantime I am in contact with the ISP who "produces" the packet loss. At least I hope its them. Its pretty hard to find out who's the bad guy in the chain. I did use mtr on my mac to trace + ping all hosts on the route but that didn't turn out any useful information to me.
Am I right, that from Wireshark capturing there is no way to reconstruct on what route a packet got lost?

Regards,
Nikolai

--
Nikolai Longolius
schnee von morgen webTV GmbH

Manteuffelstr 66
10999 Berlin
M +49 170 4777 477
  • Follow-Ups:
    • Re: [Wireshark-users] [TCP Previous segment lost], TCP [TCP Dup ACK 125#1]
      • From: dan meyer
    • Re: [Wireshark-users] [TCP Previous segment lost], TCP [TCP Dup ACK 125#1]
      • From: Wes
  • Prev by Date: [Wireshark-users] ansi_map.asn compile error
  • Next by Date: [Wireshark-users] RTP Capture filter
  • Previous by thread: [Wireshark-users] ansi_map.asn compile error
  • Next by thread: Re: [Wireshark-users] [TCP Previous segment lost], TCP [TCP Dup ACK 125#1]
  • Index(es):
    • Date
    • Thread

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