From: "David Fernández" <davidfdzp@gmail.com>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Packet losses in a router
Date: Fri, 4 Nov 2022 13:54:26 +0100 [thread overview]
Message-ID: <CAC=tZ0q8HYHFDAV-h3gQxiR-5J-v4iR9M0Cvk=LmVJXL7YD1sA@mail.gmail.com> (raw)
FYI: The issue with packet losses was solved after the router was
properly synchronized using NTP, reaching up to 100 pps during 60 s
without losses and latency < 20 ms.
> Date: Tue, 25 Oct 2022 11:30:31 +0200
> From: David Fernández <davidfdzp@gmail.com>
> To: "starlink@lists.bufferbloat.net" <starlink@lists.bufferbloat.net>
> Subject: Re: [Starlink] Packet losses in a router
> Message-ID:
> <CAC=tZ0p9Eo3Gsn-C1nEYuMwoSq7n=8uCHWmx2W5NdsTwb6aC0Q@mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> Well, asking for a friend. I will let you know the outcome, if any.
>
> I have confirmed with your answers what I was suspecting, that this is
> not normal (acceptable), even though probably you can live with it.
>
> Thanks!
>
> 2022-10-24 22:22 GMT+02:00, Jeff Tantsura <jefftant@gmail.com>:
>> If this is a 1G interface, dropping 1 packet out of (50 * 60) and with
>> load
>> below 10%, something is really wrong (I assume you are not doing SW
>> switching?)
>>
>>
>>
>> Cheers,
>>
>> Jeff
>>
>>
>>
>> From: David Fernández via Starlink
>> Sent: Monday, October 24, 2022 1:13 PM
>> To: starlink@lists.bufferbloat.net
>> Subject: [Starlink] Packet losses in a router
>>
>>
>>
>> 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 reply other threads:[~2022-11-04 12:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 12:54 David Fernández [this message]
2022-11-05 12:05 ` Gert Doering
2022-11-07 8:34 ` David Fernández
-- strict thread matches above, loose matches on Subject: below --
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
2022-10-24 21:21 ` David Lang
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='CAC=tZ0q8HYHFDAV-h3gQxiR-5J-v4iR9M0Cvk=LmVJXL7YD1sA@mail.gmail.com' \
--to=davidfdzp@gmail.com \
--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