S5E11: "Quell Our Shorts"
        
            Posted
        
        
        
        
            Modified
        
        
        
        
        
            
                
                
                    Comments
                
                0
                
                    
                    
                
            
        
    
| Previous Episode | Next Episode | 
|---|---|
| S5E10: "Beer in the Back, Party in the Front" | S5E12: "Bad Developer! No Biscuit!" | 
| Recorded (UTC) | Aired (UTC) | Editor | 
|---|---|---|
| 2020-07-09 02:52:02 | 2020-07-19 15:24:08 | "Edita" | 
| Format | SHA256 | GPG | Audio File | 
|---|---|---|---|
| MP3 | cc421c02b13561915031d683feb8744c2334cd0df04a18d26e464675adaa437c | click | click | OGG | 4b8771aecae30063537d28e1544b18c3954e2e1ce3eee029ca29fedbf3aa8b70 | click | click | 
We talk about QoS (Quality of Service)/rate-limiting and optimizing your network traffic before it hits The Tubes™.
Just the Tip
- F5 has a pretty serious vuln, so patch your shit.
Notes
Starts at 15m31s.
I was drinking a Campo Viejo Rioja Tempranillo and a Castello del Poggio Sweet Red. Paden was drinking Coors Light. Jthan was drinking Labatt Blue Light.
- Quality-of-Service/Rate-limiting
	- A way to artificially manipulate network traffic to ensure the priority of other traffic.
- Jthan wanted to know why his network went to shit whenever he’d start uploading files.
- “There’s no distinction between a ‘corporate/professional’ network and a ‘home’ network.”
		- That’s a false dichotomy created by network hardware providers. The true distinction is between well-designed and well-executed networks, and those without a good design and/or execution.
- The latter usually don’t see a level of scale where the distinction is made, and thus any actual difference is just handwaving as “residential networking”.
 
- I suggested that it’s probably actually queueing/scheduling, which is very likely.
- He’s also using a wireless network, which will affect the throughput of the WAPs’ radio cards.
- But QoS would still perhaps help a little bit. Back on track…
- Quality-of-Services is an IEEE standard, 802.1e (and then rolled into P802.1p).
		- There is, of course, a wireless variant, 802.11e.
 
- QoS theory
		- Designing some/specific protocols to lower in priority in favor of another one. SIP is a good example.
 
- You can use “tc” to implement QoS.
- Speaking generally, on the network you want your downloads to be faster (or more reliable, to be accurate) than uploads. But on a host’s level, you typically want uploads prioritized.
 
15 Clams
In this segment, Jthan shares with you a little slice of life. The title is a reference to this video. (2m16s in)
Starts at 1h03m55s.
Jthan talks about Etherpad and Etherpad-lite, but then randomly switches the topic to dedicated-service hosting, so I have to teach him cost benefit analysis 101.
Errata
- The juggernaut, bitch.
- A “tacodemon“ (cacodemon) from Doom.
- Shoutout to The Admin Admin Podcast (and that guy).
- I can’t find a source for Paden’s thing about banning install of non-OEM OSes.
- The IP address Paden started rambling off was the beginning of an RFC 3927 address.
- I sometimes refer to “802.1e” as “802.11e” and vice versa, and forget to mention P802.1p. Oops!
- At the beginning of the 15 Clams, I say “30Mbps down”. I should have said “symmetric 15Mbps up” or something, oops.
Music
| Track | Title | Artist | Link | Copyright/License | 
|---|---|---|---|---|
| Intro | Kat Man Due | Hynamo | click | CC-BY-NC-ND 4.0 | Outro | pulled. | aspect. | click | CC-BY-NC-SA 4.0 | 
        
            Author
        
        
            
                r00t^2
            
        
        
        
            
            
                Categories
            
            
                Season Five
            
        
    
Comments
There are currently no comments on this article.
Comment...