From: Ricky Mok <cskpmok@caida.org>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Packet losses in a router
Date: Mon, 24 Oct 2022 14:15:48 -0700 [thread overview]
Message-ID: <3810e66c-5107-a15c-20aa-44a893393a21@caida.org> (raw)
In-Reply-To: <CAC=tZ0rJJkhbi7jVR7LO4+Mj4PpvdY2D6RSK2b3s2Ni2UwaR_A@mail.gmail.com>
Couple plausible reasons that I encountered.
e.g., the NIC on the host simply went bad.
The cable (copper) got loose. Dirt may get into the fiber optics port.
Ricky
On 10/24/2022 1:13 PM, David Fernández via Starlink wrote:
> Dear participants of this list,
>
> If you had a router that in lab conditions, with Gigabit Ethernet
> interfaces, that losses 1 or 2 out of a few thousands of UDP packets
> of a few hundreds of bytes each one, during a test of 1 minute, at
> only 50 packets/s using iperf2, I am sure that you would investigate
> why, wouldn't you?
>
> Or it is not worth it? Just live with it?
>
> Thank you in advance for any answer!
>
> Regards,
>
> David
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
next prev parent reply other threads:[~2022-10-24 21:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 20:13 David Fernández
2022-10-24 20:22 ` Jeff Tantsura
2022-10-25 9:30 ` David Fernández
2022-10-24 20:54 ` Gert Doering
2022-10-24 21:15 ` Ricky Mok [this message]
2022-10-24 21:21 ` David Lang
2022-11-04 12:54 David Fernández
2022-11-05 12:05 ` Gert Doering
2022-11-07 8:34 ` David Fernández
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3810e66c-5107-a15c-20aa-44a893393a21@caida.org \
--to=cskpmok@caida.org \
--cc=starlink@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox