Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
en.osm.town is one of the many independent Mastodon servers you can use to participate in the fediverse.
An independent, community of OpenStreetMap people on the Fediverse/Mastodon. Funding graciously provided by the OpenStreetMap Foundation.

Administered by:

Server stats:

251
active users

en.osm.town: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

#bufferbloat

2 posts2 participants1 post today
Public
NGI Zero open source funding

In a new #podcast episode we talk to team members of @LibreQoS. The software helps ISPs fight #bufferbloat & distribute traffic fairly. In a lively conversation they talk about the vital importance of stable internet connections and their reasons for open sourcing LibreQoS: they hoped it would help a few small ISPs that bring internet access to under-served communities. But to their surprise LibreQoS has become very popular with deployments in 58 countries.
podcast.nlnet.nl/@NGIZero/epis
#FOSS #NGI0

Public
T_X

Yaiy, found some detailed #RFC|s which seem to describe how to handle #FEC and how to associate them to their primary stream. Was looking for this for #RaptorQ / #SDP / #SAP / #multicast / #Freifunk. Lot's of reading to catch up with - too tired to do this today though, will have to do that later :D.

#bufferbloat #meshnetworks

datatracker.ietf.org/doc/html/
datatracker.ietf.org/doc/html/
datatracker.ietf.org/doc/html/
datatracker.ietf.org/doc/html/
rfc-editor.org/rfc/rfc2198.htm
rfc-editor.org/rfc/rfc6354.htm
datatracker.ietf.org/doc/html/

IETF DatatrackerRFC 8872: Guidelines for Using the Multiplexing Features of RTP to Support Multiple Media StreamsThe Real-time Transport Protocol (RTP) is a flexible protocol that can be used in a wide range of applications, networks, and system topologies. That flexibility makes for wide applicability but can complicate the application design process. One particular design question that has received much attention is how to support multiple media streams in RTP. This memo discusses the available options and design trade-offs, and provides guidelines on how to use the multiplexing features of RTP to support multiple media streams.
Public
Bill Woodcock
I need to save this, in case I need to explain to people why #bufferbloat is bad. Hellenic Telecom, I'm looking to you for _transit_, not _warehousing_.

woody$ traceroute 9.9.9.9
traceroute to 9.9.9.9 (9.9.9.9), 64 hops max, 40 byte packets
1 192.168.178.1 (192.168.178.1) 39.414 ms 3.798 ms 2.919 ms
2 172.22.1.1 (172.22.1.1) 8.043 ms 13.366 ms 20.248 ms
3 195.167.84.129 (195.167.84.129) 8.449 ms 13.196 ms 7.881 ms
4 109.8.205.212.static.otenet.gr (212.205.8.109) 8.584 ms 13.657 ms 13.341 ms
5 79.128.234.220 (79.128.234.220) 14.570 ms 8.442 ms 8.604 ms
6 nyma-asr99b-chan-asr99b.backbone.otenet.net (79.128.234.157) 15.412 ms
reth-asr9ka-hera-asr9ka.backbone.otenet.net (79.128.230.22) 15.880 ms
79.128.224.185 (79.128.224.185) 22.141 ms
7 79.128.226.31 (79.128.226.31) 16.966 ms
79.128.226.116 (79.128.226.116) 31.696 ms
79.128.226.19 (79.128.226.19) 14.142 ms
8 79.128.227.219 (79.128.227.219) 15.292 ms
79.128.226.19 (79.128.226.19) 14.912 ms
79.128.226.243 (79.128.226.243) 14.118 ms
9 dns9.quad9.net (9.9.9.9) 14.841 ms 14.971 ms 14.495 ms

woody$ ping 9.9.9.9
PING 9.9.9.9 (9.9.9.9): 56 data bytes
...some lines omitted...
64 bytes from 9.9.9.9: icmp_seq=30 ttl=56 time=8471.102 ms
64 bytes from 9.9.9.9: icmp_seq=31 ttl=56 time=9622.876 ms
64 bytes from 9.9.9.9: icmp_seq=32 ttl=56 time=11320.716 ms
64 bytes from 9.9.9.9: icmp_seq=33 ttl=56 time=12535.773 ms
64 bytes from 9.9.9.9: icmp_seq=34 ttl=56 time=13479.652 ms
64 bytes from 9.9.9.9: icmp_seq=35 ttl=56 time=14776.024 ms
64 bytes from 9.9.9.9: icmp_seq=36 ttl=56 time=15775.719 ms
64 bytes from 9.9.9.9: icmp_seq=37 ttl=56 time=16997.679 ms
64 bytes from 9.9.9.9: icmp_seq=38 ttl=56 time=16974.287 ms
64 bytes from 9.9.9.9: icmp_seq=39 ttl=56 time=18149.947 ms
Request timeout for icmp_seq 40
64 bytes from 9.9.9.9: icmp_seq=41 ttl=56 time=18433.061 ms
64 bytes from 9.9.9.9: icmp_seq=42 ttl=56 time=18977.357 ms
64 bytes from 9.9.9.9: icmp_seq=43 ttl=56 time=20256.393 ms
64 bytes from 9.9.9.9: icmp_seq=44 ttl=56 time=21846.190 ms
64 bytes from 9.9.9.9: icmp_seq=45 ttl=56 time=22274.975 ms
64 bytes from 9.9.9.9: icmp_seq=46 ttl=56 time=21926.807 ms
64 bytes from 9.9.9.9: icmp_seq=47 ttl=56 time=21956.825 ms
64 bytes from 9.9.9.9: icmp_seq=48 ttl=56 time=22866.450 ms
64 bytes from 9.9.9.9: icmp_seq=49 ttl=56 time=22764.079 ms
64 bytes from 9.9.9.9: icmp_seq=50 ttl=56 time=22932.184 ms
64 bytes from 9.9.9.9: icmp_seq=51 ttl=56 time=22751.198 ms
64 bytes from 9.9.9.9: icmp_seq=52 ttl=56 time=23050.991 ms
64 bytes from 9.9.9.9: icmp_seq=53 ttl=56 time=23449.608 ms
64 bytes from 9.9.9.9: icmp_seq=54 ttl=56 time=24239.924 ms
Request timeout for icmp_seq 55
64 bytes from 9.9.9.9: icmp_seq=56 ttl=56 time=25671.654 ms
Request timeout for icmp_seq 57
Request timeout for icmp_seq 58
Request timeout for icmp_seq 59
64 bytes from 9.9.9.9: icmp_seq=60 ttl=56 time=22470.379 ms
64 bytes from 9.9.9.9: icmp_seq=61 ttl=56 time=22938.439 ms
64 bytes from 9.9.9.9: icmp_seq=62 ttl=56 time=23631.650 ms
64 bytes from 9.9.9.9: icmp_seq=63 ttl=56 time=24062.791 ms
64 bytes from 9.9.9.9: icmp_seq=64 ttl=56 time=23723.215 ms
64 bytes from 9.9.9.9: icmp_seq=65 ttl=56 time=23585.544 ms
64 bytes from 9.9.9.9: icmp_seq=66 ttl=56 time=23802.193 ms
64 bytes from 9.9.9.9: icmp_seq=67 ttl=56 time=24429.611 ms
64 bytes from 9.9.9.9: icmp_seq=68 ttl=56 time=24479.928 ms
64 bytes from 9.9.9.9: icmp_seq=69 ttl=56 time=24351.231 ms
64 bytes from 9.9.9.9: icmp_seq=70 ttl=56 time=24210.547 ms
Request timeout for icmp_seq 71
Request timeout for icmp_seq 72
64 bytes from 9.9.9.9: icmp_seq=73 ttl=56 time=23917.609 ms
64 bytes from 9.9.9.9: icmp_seq=74 ttl=56 time=24481.414 ms
64 bytes from 9.9.9.9: icmp_seq=75 ttl=56 time=25157.445 ms
64 bytes from 9.9.9.9: icmp_seq=76 ttl=56 time=26257.238 ms
64 bytes from 9.9.9.9: icmp_seq=77 ttl=56 time=26989.712 ms
64 bytes from 9.9.9.9: icmp_seq=78 ttl=56 time=27329.260 ms
64 bytes from 9.9.9.9: icmp_seq=79 ttl=56 time=28227.827 ms
64 bytes from 9.9.9.9: icmp_seq=80 ttl=56 time=28909.874 ms
64 bytes from 9.9.9.9: icmp_seq=81 ttl=56 time=29858.149 ms
64 bytes from 9.9.9.9: icmp_seq=82 ttl=56 time=30297.285 ms
64 bytes from 9.9.9.9: icmp_seq=83 ttl=56 time=31001.889 ms
64 bytes from 9.9.9.9: icmp_seq=84 ttl=56 time=30927.453 ms
64 bytes from 9.9.9.9: icmp_seq=85 ttl=56 time=30136.748 ms
64 bytes from 9.9.9.9: icmp_seq=86 ttl=56 time=29231.370 ms
64 bytes from 9.9.9.9: icmp_seq=87 ttl=56 time=28358.744 ms
64 bytes from 9.9.9.9: icmp_seq=88 ttl=56 time=27409.612 ms
64 bytes from 9.9.9.9: icmp_seq=89 ttl=56 time=26482.402 ms
64 bytes from 9.9.9.9: icmp_seq=90 ttl=56 time=25536.722 ms
...some lines omitted...
^C
--- 9.9.9.9 ping statistics ---
136 packets transmitted, 124 packets received, 8.8% packet loss
round-trip min/avg/max/stddev = 15.933/13743.625/31001.889/10126.308 ms
woody$
Public
njoseph :fbx:

FLOSS Weekly Episode 774: Let’s Get Rusty
hackaday.com/2024/03/13/floss-

I listened to this episode twice. The book mentioned is available on the O'Reilly Learning platform. I went through the first tutorial "flappy dragon" already.

LibreQoS project is quite interesting. I restart my router once every month due to buffer bloat. It's great to see that there is a real solution to this problem and it is free software.

Hackaday · FLOSS Weekly Episode 774: Let’s Get RustyThis week, Jonathan Bennett chats with Herbert Wolverson about Rust! Is it really worth the hype? Should you have written that in Rust? What’s up with “if let some” anyways? And w…
#podcast#rust#bufferBloat
ExploreLive feeds
About