3 ms·

Well, it's not working anymore.

by Sami_Lehtinen 11y ago

empressplay 11y ago
I guess we collectively blew it up =( This is why we can't have nice things...
- Sami_Lehtinen 11y ago
  I think they forgot rate limits. One of implementations were done using two actual routers and routing between those back and forth. Which means that it's really easy target to overload. I would have personally written light python script to fake it, instead of using hardware routers. It seems that pinging under 100 Kbit/s rate is enough to take it out of service, which is very little traffic. I would have liked to load test them up to double digit Gbit/s rate, but. This is disappointing. No challenge at all, single IP, no rate limits and poor capacity.
  - davidcollantes 11y ago
    Would love to see it, how can I encourage you to?
    - Sami_Lehtinen 11y ago
      I'm busy with other projects, so I won't do it. But that's trivial. It would be a good practical learning opportunity if you're trying to learn about IP protocol and packet handling. Just use raw sockets on Linux, get data, and send responses. Alternatively you could use multiple IP addresses on same host, then you don't need to fake packets and can traditionally listen on ping on every IP. But that takes it to bit higher level and it isn't so fun anymore. Or you can set your computer to listen in on routed traffic, if you got router which will route subnet to your 'software' router. There are multiple ways to do it. Of course using two hardware routers is also ok, if you want to learn about configuring those. Different goal, different means. All of these means still require you to be able to control that subnet and set required reverse DNS information or run your own AS and rDNS.
  - jlgaddis 11y ago
    If this is using a pair of low-end Cisco routers (as previous implementations did), it really doesn't take too many people doing this at once to "overload" them. Generating the responses is handled by the CPU (not the ASICs) and the processor in these devices is extremely underpowered, relative to, well, pretty much anything else with a processor in it. The processor in a Cisco 1841, for example, is an m68k at 250 MHz, if memory serves. Besides, I'm sure this was probably just something thrown together quickly for a good laugh and the responsible party likely didn't feel it was necessary to make this a highly available, fault-tolerant, geographically replicated service.
- Sami_Lehtinen 11y ago
  Also the latency between first hop of the story and last hop of the story tells about the system having very limited capacity. In case of the faking Script, delay difference between hops would be 0 ms. Now the numbers directly tell that there's plenty of latency and packet handling is taking a long time. -> Guaranteed to have a poor throughput & load characteristics.
dogma1138 11y ago
It does work it depends on your ISP's peering tho. 7 6 ms 6 ms 16 ms 40ge1-3.core1.lon2.he.net [195.66.224.21] 8 92 ms 73 ms 74 ms 100ge1-1.core1.nyc4.he.net [72.52.92.166] 9 87 ms 103 ms 89 ms 100ge7-2.core1.chi1.he.net [184.105.223.161] 10 95 ms 95 ms 95 ms 100ge10-1.core1.msp1.he.net [184.105.223.178] 11 95 ms 95 ms 95 ms ip-house.gigabitethernet3-6.core1.msp1.he.net [216.66.78.110] 12 97 ms 96 ms 96 ms c4500-1.mpls.iphouse.net [216.250.189.170] 13 96 ms 96 ms 96 ms egw-iphouse.mplsc1.mn.us.sn11.net [209.240.64.149] 14 100 ms 100 ms 100 ms sandwichnet.dmarc.lga1.atlanticmetro.net [208.68.168.214] 15 100 ms 100 ms 101 ms bad.horse [162.252.205.130] 16 105 ms 105 ms 105 ms bad.horse [162.252.205.131] 17 110 ms 110 ms 110 ms bad.horse [162.252.205.132] 18 115 ms 115 ms 115 ms bad.horse [162.252.205.133] 19 120 ms 120 ms 119 ms he.rides.across.the.nation [162.252.205.134] 20 125 ms 125 ms 124 ms the.thoroughbred.of.sin [162.252.205.135] 21 130 ms 129 ms 129 ms he.got.the.application [162.252.205.136] 22 136 ms 135 ms 135 ms that.you.just.sent.in [162.252.205.137] 23 140 ms 140 ms 140 ms it.needs.evaluation [162.252.205.138] 24 146 ms 144 ms 144 ms so.let.the.games.begin [162.252.205.139] 25 150 ms 150 ms 150 ms a.heinous.crime [162.252.205.140] 26 155 ms 155 ms 155 ms a.show.of.force [162.252.205.141] 27 161 ms 161 ms 160 ms a.murder.would.be.nice.of.course [162.252.205.142] 28 165 ms 165 ms 165 ms bad.horse [162.252.205.143] 29 169 ms 170 ms 170 ms bad.horse [162.252.205.144] 30 172 ms 175 ms 175 ms bad.horse [162.252.205.145]

Well, it's not working anymore.

empressplay 11y ago

I guess we collectively blew it up =( This is why we can't have nice things...

Sami_Lehtinen 11y ago
I think they forgot rate limits. One of implementations were done using two actual routers and routing between those back and forth. Which means that it's really easy target to overload. I would have personally written light python script to fake it, instead of using hardware routers. It seems that pinging under 100 Kbit/s rate is enough to take it out of service, which is very little traffic. I would have liked to load test them up to double digit Gbit/s rate, but. This is disappointing. No challenge at all, single IP, no rate limits and poor capacity.
- davidcollantes 11y ago
  Would love to see it, how can I encourage you to?
  - Sami_Lehtinen 11y ago
    I'm busy with other projects, so I won't do it. But that's trivial. It would be a good practical learning opportunity if you're trying to learn about IP protocol and packet handling. Just use raw sockets on Linux, get data, and send responses. Alternatively you could use multiple IP addresses on same host, then you don't need to fake packets and can traditionally listen on ping on every IP. But that takes it to bit higher level and it isn't so fun anymore. Or you can set your computer to listen in on routed traffic, if you got router which will route subnet to your 'software' router. There are multiple ways to do it. Of course using two hardware routers is also ok, if you want to learn about configuring those. Different goal, different means. All of these means still require you to be able to control that subnet and set required reverse DNS information or run your own AS and rDNS.
- jlgaddis 11y ago
  If this is using a pair of low-end Cisco routers (as previous implementations did), it really doesn't take too many people doing this at once to "overload" them. Generating the responses is handled by the CPU (not the ASICs) and the processor in these devices is extremely underpowered, relative to, well, pretty much anything else with a processor in it. The processor in a Cisco 1841, for example, is an m68k at 250 MHz, if memory serves. Besides, I'm sure this was probably just something thrown together quickly for a good laugh and the responsible party likely didn't feel it was necessary to make this a highly available, fault-tolerant, geographically replicated service.
Sami_Lehtinen 11y ago
Also the latency between first hop of the story and last hop of the story tells about the system having very limited capacity. In case of the faking Script, delay difference between hops would be 0 ms. Now the numbers directly tell that there's plenty of latency and packet handling is taking a long time. -> Guaranteed to have a poor throughput & load characteristics.

dogma1138 11y ago

It does work it depends on your ISP's peering tho. 7 6 ms 6 ms 16 ms 40ge1-3.core1.lon2.he.net [195.66.224.21] 8 92 ms 73 ms 74 ms 100ge1-1.core1.nyc4.he.net [72.52.92.166] 9 87 ms 103 ms 89 ms 100ge7-2.core1.chi1.he.net [184.105.223.161] 10 95 ms 95 ms 95 ms 100ge10-1.core1.msp1.he.net [184.105.223.178] 11 95 ms 95 ms 95 ms ip-house.gigabitethernet3-6.core1.msp1.he.net [216.66.78.110] 12 97 ms 96 ms 96 ms c4500-1.mpls.iphouse.net [216.250.189.170] 13 96 ms 96 ms 96 ms egw-iphouse.mplsc1.mn.us.sn11.net [209.240.64.149] 14 100 ms 100 ms 100 ms sandwichnet.dmarc.lga1.atlanticmetro.net [208.68.168.214] 15 100 ms 100 ms 101 ms bad.horse [162.252.205.130] 16 105 ms 105 ms 105 ms bad.horse [162.252.205.131] 17 110 ms 110 ms 110 ms bad.horse [162.252.205.132] 18 115 ms 115 ms 115 ms bad.horse [162.252.205.133] 19 120 ms 120 ms 119 ms he.rides.across.the.nation [162.252.205.134] 20 125 ms 125 ms 124 ms the.thoroughbred.of.sin [162.252.205.135] 21 130 ms 129 ms 129 ms he.got.the.application [162.252.205.136] 22 136 ms 135 ms 135 ms that.you.just.sent.in [162.252.205.137] 23 140 ms 140 ms 140 ms it.needs.evaluation [162.252.205.138] 24 146 ms 144 ms 144 ms so.let.the.games.begin [162.252.205.139] 25 150 ms 150 ms 150 ms a.heinous.crime [162.252.205.140] 26 155 ms 155 ms 155 ms a.show.of.force [162.252.205.141] 27 161 ms 161 ms 160 ms a.murder.would.be.nice.of.course [162.252.205.142] 28 165 ms 165 ms 165 ms bad.horse [162.252.205.143] 29 169 ms 170 ms 170 ms bad.horse [162.252.205.144] 30 172 ms 175 ms 175 ms bad.horse [162.252.205.145]