10 May
2024
10 May
'24
11:10 p.m.
I just wanted to add, the "few more ms delay" - is actually more like the
following:
---
root@OpenWrt:~# ping 44.1.1.44 -I wan -c 4PING 44.1.1.44 (44.1.1.44): 56 data bytes64
bytes from 44.1.1.44: seq=0 ttl=54 time=80.774 ms64 bytes from 44.1.1.44: seq=1 ttl=54
time=80.527 ms64 bytes from 44.1.1.44: seq=2 ttl=54 time=80.781 ms64 bytes from 44.1.1.44:
seq=3 ttl=54 time=80.752 ms
--- 44.1.1.44 ping statistics ---4 packets transmitted, 4 packets received, 0% packet
lossround-trip min/avg/max = 80.527/80.708/80.781 ms
root@OpenWrt:~# ping 44.1.1.44 -I tunl0 -c 4PING 44.1.1.44 (44.1.1.44): 56 data bytes64
bytes from 44.1.1.44: seq=0 ttl=50 time=200.975 ms64 bytes from 44.1.1.44: seq=1 ttl=50
time=200.664 ms64 bytes from 44.1.1.44: seq=2 ttl=50 time=200.784 ms64 bytes from
44.1.1.44: seq=3 ttl=50 time=200.830 ms
--- 44.1.1.44 ping statistics ---4 packets transmitted, 4 packets received, 0% packet
lossround-trip min/avg/max = 200.664/200.813/200.975 ms
---
I wouldn't consider that just "a few more". This is just Ping and
doesn't consider time in protocols where there's also the additional trip from the
server to the user.
- KB3VWG
On Friday, May 10, 2024 at 09:43:33 PM EDT, Mark Herson, N2MH via 44net
<44net(a)mailman.ampr.org> wrote:
On 5/10/24 07:26, Chris via 44net wrote:
This may not be entirely true for streaming services, especially voip
telephony. While a phone or its server is looking up a host name in DNS,
there will likely be no audio heard on the connection. The connection
will appear to have gone dead or have a momentary dropout until the DNS
responds. And, the longer the delay in getting that DNS response, the
longer will be that dropout period of time.
For streaming video, you will get no dropout, but you will see a frame
freeze.
For typical tcp services, such as web, there will be a slightly longer
response time when changing pages. Of course, smtp will not show anything.
73, Mark, N2MH
_______________________________________________
44net mailing list -- 44net(a)mailman.ampr.org
To unsubscribe send an email to 44net-leave(a)mailman.ampr.org
So instead of
me leaving MDC and my packet hopping a trans-Atlantic
fiber cable to you, it makes a round trip to California first before
doing so.
I don't understand why this is a problem - a few more ms delay on a
reliable fibre network will not adversely affect DNS lookups.