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

Post by btreecat » Wed, Jan 28, 2015, 5:33 PM UTC

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…

Post by api » Wed, Jan 28, 2015, 5:35 PM UTC

Spooky23 wrote: post #24

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…

Post by Freaky » Wed, Jan 28, 2015, 5:40 PM UTC

angersock wrote: post #33

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…

I take it you've seen core switches on fire off the Jupiter gate?

Post by wallflower » Wed, Jan 28, 2015, 5:56 PM UTC

Spooky23 wrote: post #24

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…

Post by farresito » Wed, Jan 28, 2015, 6:00 PM UTC