It is for home but I don't mind paying more to get something more customizable. I am kinda a devop.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Show posts MenuQuote from: Otanx on April 10, 2020, 05:24:21 PMI ping ispdomain.com -t
Ping time isn't an issue. Ping is the first thing to get delayed by a box if it has other things to do. So if you are sending a lot of data ping response will go up.
How do you know you are dropping packets?
Quote from: Otanx on April 10, 2020, 05:24:21 PM1 in ten lines average.
How many?
Quote from: Otanx on April 10, 2020, 05:24:21 PMIt is the ISP itself so I can say direct link or one hop inside their networks at most.
What does the network look like between the source and dest?
Quote from: Otanx on April 10, 2020, 05:24:21 PM
If this is peer to peer do all peers drop packets, just one? What are you sending between the clients? What port and protocol are you using? The final answer might just be that packet loss is just a fact of the internet. Anything that runs over it needs to be able to deal with it.
-Otanx
Quote from: ristau5741 on April 11, 2020, 07:04:54 AMQuote from: siavoshkc on April 10, 2020, 04:31:07 PM
I am familiar with Wireshark. I can track conversations on the wire and see who tells whom what. But I can't see how can I use it to see why I have dropped packets.
check the timestamp on the conversation. example: if you have say a 800ms delay between SYN and SYN-ACK response, the destination has issue.
if you receive SYN-ACK right away and there is delay with return ACK the sender has issues, assuming TCP