What does HackerNews think of comcast?

Simulating shitty network connections so you can build better systems.

Language: Go

#15 in Go
macOS command-line tools you might not know about | Jun 2023
Expand Context ↕
[Comcast](https://github.com/tylertreat/comcast) also does this for macOS, BSD, and Linux. And it's _brilliantly_ named.
Ask HN: How do I force network failures during development against remote APIs? | Jul 2022
Take a look at https://github.com/tylertreat/comcast

> Comcast is a tool designed to simulate common network problems like latency, bandwidth restrictions, and dropped/reordered/corrupted packets

The Deadlock Empire | Dec 2021
Expand Context ↕
I don't doubt someone has built something like that for testing, though perhaps not as a library. I'm reminded of a networking service that does the same at a higher level, given its easy to remember name : https://github.com/tylertreat/comcast
Toxiproxy is a framework for simulating network conditions | Nov 2021
While yours is more fully featured, I submit that https://github.com/tylertreat/comcast had the better name.
Surprisingly Slow | Apr 2021
Expand Context ↕
https://github.com/tylertreat/comcast
Volkswagen – detects when your tests are run in a CI server, and makes them pass | Sep 2018
Expand Context ↕
comcast (https://github.com/tylertreat/comcast) is really helpful for simulating poor network connections. Particularly nice when used in Docker to do network simulations.
Securing Web Sites Made Them Less Accessible | Aug 2018
Expand Context ↕
> Is there was a really easy way of mimicking all the effects of this type of latency so I could periodically test the stuff I set up?

Your browser's developer tools can simulate latency and constrained bandwidth, at least in Firefox and Chrome. Firefox instructions: https://developer.mozilla.org/en-US/docs/Tools/Responsive_De...

At a system level, Clumsy (https://jagt.github.io/clumsy/), Comcast (https://github.com/tylertreat/comcast), and Network Link Conditioner (https://nshipster.com/network-link-conditioner/) are relatively user-friendly and work at a lower level. Okay, Comcast isn't as user friendly, but it has a really cheeky name. Also, the GIF on Clumsy's homepage is brilliantly well-done.

Apparently Charles (https://www.charlesproxy.com/) and Fiddler (https://www.telerik.com/fiddler) can also simulate bad connections, if you're already using one of those tools.

> Also, if it is just HTTPS, then it is possible to proxy through something that downgrades the protocol, but it feels dirty.

Not necessarily. Consider HSTS, HPKP, Expect-CT, etc.
Manually Throttle the Bandwidth of a Linux Network Interface | Apr 2017
The tc command is great except for the weird command structure. I really like the comcast tool as a wrapper for tc: https://github.com/tylertreat/comcast

It makes it much easier to do throttle the way you want.

I've Just Liberated My Modules | Mar 2016
Expand Context ↕
This was what I was thinking while reading the post.

Also, I recently checked and https://github.com/tylertreat/comcast is still alive and well.
Show HN: Tcconfig – Simple tc wrapper, easy to set up network traffic control | Mar 2016
Comcast[0] is a nice alternative if you're looking to simulate poor network conditions.

[0] https://github.com/tylertreat/comcast

Tcpdive – A TCP Performance Profiling Tool | Jan 2016
And to simulate a degraded connection, the colorfully-named comcast tool works well:

https://github.com/tylertreat/comcast