Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Comcast: Simulating shitty network connections so you can build better systems

github.com

Post reply on HN
Print view View original

21–30 of 87 posts

Re: Comcast: Simulating shitty network connections so you can build better systems

#21

Post by lucb1e »

blueskin_ wrote: post #12

On linux, tc can do similar things, such as dropping a percentage of packets or adding random delays. http://linux.die.net/man/8/tc

As said in the readme:

> you can use tc which supports some additional options.

     $ tc qdisc add dev eth0 root netem delay 50ms 20ms distribution normal
     $ tc qdisc change dev eth0 root netem reorder 0.02 duplicate 0.05 corrupt 0.01
> To reset:

    $ tc qdisc del dev eth0 root netem

Re: Comcast: Simulating shitty network connections so you can build better systems

#22

Post by paulrosenzweig »

Fuxy wrote: post #20
chatmasta wrote: post #18

People talk about "fuck you money," meaning the amount of money you need to make before you can never work again. Personally, my "fuck you money" isn't money per se , but the fall of Comcast. When I build enough value in the world to displace Comcast, I will retire. We need to see more work in the areas of mesh networking, layer-3 routing, and consumer networking in general. This tool is a good step. Personally I'm h…

You know your company sucks when its name has become synonymous with high latency, dropped packets and a all round shitty network. Unfortunately i suspect they will just send a trademark claim to Github to get it removed.

This seems like satire to me. Could that save it like "Dumb Starbucks"?

https://en.wikipedia.org/wiki/Dumb_Starbucks

Re: Comcast: Simulating shitty network connections so you can build better systems

#23

Post by todd3834 »

paulrosenzweig wrote: post #22
Fuxy wrote: post #20

Earlier quoted context omitted.

You know your company sucks when its name has become synonymous with high latency, dropped packets and a all round shitty network. Unfortunately i suspect they will just send a trademark claim to Github to get it removed.

This seems like satire to me. Could that save it like "Dumb Starbucks"? https://en.wikipedia.org/wiki/Dumb_Starbucks

I don't think Dumb Starbucks was saved. They just didn't ride it out long enough to find out. Who knows what would have really happened though

Re: Comcast: Simulating shitty network connections so you can build better systems

#24

Post by Spooky23 »

api wrote: post #16

Nice. It'd be neat to include options to simulate other pathological conditions often encountered in the field like: - Multiple layers of NAT - overlapping un-synchronized timeouts are one thing ... but the REAL fun comes in when intermediate layers have the same IP ranges as IPs you are trying to reach on the "outside" of the NAT sandwich. All kinds of "interesting" things can happen, like the "software laser": http…

My favorite enterprise network pathologies:

- Randomly block specific ports "because security"

- Limit RPC port ranges to some random small number.

- Strange network optimizations. Example: Optimize TCP Window Size to support NT4 clients on 56k frame relay circuits.

- Very Slow DNS response

- Optimize core switching rules to fully utilize switch CPU. Avoid configurations that take place in an asic.

- Long DHCP Leases + Undersized DHCP scopes.

Re: Comcast: Simulating shitty network connections so you can build better systems

#25

Post by [deleted] »

api wrote: post #16

Nice. It'd be neat to include options to simulate other pathological conditions often encountered in the field like: - Multiple layers of NAT - overlapping un-synchronized timeouts are one thing ... but the REAL fun comes in when intermediate layers have the same IP ranges as IPs you are trying to reach on the "outside" of the NAT sandwich. All kinds of "interesting" things can happen, like the "software laser": http…

[deleted]

Re: Comcast: Simulating shitty network connections so you can build better systems

#27

Post by steventhedev »

api wrote: post #16

Nice. It'd be neat to include options to simulate other pathological conditions often encountered in the field like: - Multiple layers of NAT - overlapping un-synchronized timeouts are one thing ... but the REAL fun comes in when intermediate layers have the same IP ranges as IPs you are trying to reach on the "outside" of the NAT sandwich. All kinds of "interesting" things can happen, like the "software laser": http…

Don't forget jitter, and simulating an ISP that will shut off your DNS traffic at random (literally anything DNS, not just their own servers).

Re: Comcast: Simulating shitty network connections so you can build better systems

#29

Post by scott_karana »

blueskin_ wrote: post #12

On linux, tc can do similar things, such as dropping a percentage of packets or adding random delays. http://linux.die.net/man/8/tc

From TFA :)

> On Linux, we use iptables and tc. Comcast is merely a thin wrapper around these controls.

Re: Comcast: Simulating shitty network connections so you can build better systems

#30

Post by troymc »

cordite wrote: post #5

Would something like this be DMCA'd or taken down because of the name? (Not that it is violating copyright by its contents)

I was confused if this was something from the real Comcast, so it seems to be a clear case of trademark infringement (but it's not my call, and I may be wrong).

If GitHub agrees, then it would be a violation of their Terms of Service [1], section A.8:

"You may not use the Service for any illegal or unauthorized purpose. You must not, in the use of the Service, violate any laws in your jurisdiction (including but not limited to copyright or trademark laws)."

[1] https://help.github.com/articles/github-terms-of-service/

Post reply on HN