Rampant Nerdery
I mostly wanted to preserve this conversation for my own amusement.
[23:10] Fatespinner: Are you able to connect to EVE? I can't.
[23:10] Karelzarath: Looks like it's back up. They were hit by a DDoS, apparently. O.O
[23:10] Fatespinner: No, yeah, I knew that part.
[23:11] Fatespinner: But myself (and the rest of the Northeast) are still SOL.
[23:11] Fatespinner: Tracing route to 200.38.237.87.rev.ccp.cc [87.237.38.200]
over a maximum of 30 hops:
1 <1 ms 1 ms <1 ms THEMATRIX [192.168.0.1]
2 16 ms 10 ms 18 ms cable1-0.albynytry-ar401.nyroc.rr.com [72.231.14
4.1]
3 31 ms 37 ms 22 ms gig1-0.albynytry-rtr02.nyroc.rr.com [24.29.39.81
]
4 21 ms 24 ms 22 ms gig1-1-0.albynywav-rtr01.nyroc.rr.com [24.29.37.
45]
5 38 ms 23 ms 21 ms ge-4-0-0.albynywav-rtr03.nyroc.rr.com [24.24.7.2
5]
6 46 ms 57 ms 61 ms ae10-0.albynyyf-rtr000.nyroc.rr.com [24.24.21.21
8]
7 55 ms 53 ms 66 ms ae-5-0.cr0.nyc30.tbone.rr.com [66.109.6.74]
8 54 ms 48 ms 57 ms ae-1-0.pr0.nyc20.tbone.rr.com [66.109.6.163]
9 31 ms * 28 ms 107.14.16.14
10 * 107.14.16.14 reports: Destination host unreachable.
Trace complete.
[23:12] Karelzarath: Looks like I'm in.
[23:12] Fatespinner: There's a break in the NE backbone routing.
[23:12] Fatespinner: Other New Yorkers on the EVE forums are reporting the same issue.
[23:12] Fatespinner: (I'm the first one to post the probable cause.) ::whistles::
[23:13] Karelzarath: That's really really strange. I would think the transatlantic route would go through that area.
[23:13] Fatespinner: It does. I can get to the EVE server by way of a Level 3 router in Newark, NJ.
[23:13] Fatespinner: Routed through London, strangely.
[23:14] Fatespinner: But I can't tell the EVE client to do that. :)
[23:14] Karelzarath: Yeah, that's where the NOC is
[23:14] Fatespinner: "Use this route, you bastard."
[23:14] Karelzarath: Maybe if you keep sending traffic down that route, your local router will pick it up as a better route
[23:15] Fatespinner: No, because its the ISP routers that need to learn, not mine.
[23:15] Fatespinner: And all the trans-atlantic shit is probably static routed to cut overhead anyway.
[23:17] Karelzarath: Yeah, probably.
[23:18] Fatespinner: The burden of having the knowledge to solve a problem without the power to actually do it. :(
[23:18] Fatespinner: Sadness.
[23:18] Karelzarath: You should call up yout ISP and be all "You should add these routes to your routing tables." ;)
[23:19] Fatespinner: I suppose I could just call my ISP. "Route my traffic for destination XYZ through Level 3, IP address 212.187.160.62."
[23:19] Fatespinner: "Fuck the rest of New York, I just want MY shit to work. :P"
[23:19] Karelzarath: Your response would be seconds of silence and a "Huh?"
[23:19] Fatespinner: At which point I would ask to speak with Tier 4. :)
[23:20] Fatespinner: I have dealt on highly technical levels with this ISP before.
[23:20] Fatespinner: As part of my job. :)
[23:20] Karelzarath: Hell, then, do it! :D
[23:21] Fatespinner: I'm pretty sure tech support isn't available for residential customers at 11:30pm. :)
[23:26] Fatespinner: Ah well, they have 2 days, 23 hours, 43 minutes, and 40 seconds to figure shit out.
[23:28] Fatespinner: HAHAHAHA.
[23:28] Fatespinner: Someone on the forums is using an SSH tunnel to his University which has a VPN to a European campus. LAWL
[23:28] Fatespinner: So *he* can get on.
[23:28] Fatespinner: That is so epic.
[23:30] Karelzarath: That is frikkin awesome
[23:30] Fatespinner: Yeah, we have no such awesomeness at my office that I could take advantage of.
[23:33] Fatespinner: Ah, apparently CCP has temporarily blacklisted the ISPs identified in the DDoS attack.
[23:33] Karelzarath: Sensible precaution, I suppose
[23:34] Fatespinner: And when i was routing through Level 3, I was leaving my ISPs network and then coming BACK into Europe. And, of course, routers only see the source IP of the previous router, not the actual source IP until it reaches the destination.
[23:34] Fatespinner: Oh you wacky OSI model.
[23:34] Karelzarath: lol
[23:35] Karelzarath: So, your ISP is one of the blacklisted ones?
[23:35] Fatespinner: Apparently.
[23:35] Fatespinner: As is something called 'Eurorings' in... well, Europe.
[23:36] Karelzarath: Can't you just invisibly route your traffic through another ISP? They do it all the time on TV!
[23:36] * Karelzarath tsks
[23:36] Fatespinner: Yeeeaaaaaaah, maybe if I had vastly superior routing hardware here, like a Cisco ASA 5500.
[23:36] Fatespinner: But, alas, I have a Linksys E2000.
[23:37] Karelzarath: I bet you can't crack a password in 5 keystrokes, either. Geez. Why are they paying you? ;)
[23:38] Fatespinner: Actually, password cracking is a little beyond my skill unless I have physical access to the machine in question.
[23:38] Fatespinner: But yeah, it requires a few more than 5 keystrokes.
[23:38] Karelzarath: lol
[23:38] Fatespinner: Ctrl + Alt + Hax0r is not an option on standard keyboards.
[23:39] Karelzarath: It is in Linux.
[23:39] Fatespinner: Hehe, the 'Hax Lock' key.
[23:39] Karelzarath: lol!
[23:40] Fatespinner: Its funny seeing other people on the forums who clearly have NO IDEA what they're doing posting traceroutes.
[23:40] Fatespinner: Like this rockstar:
[23:40] Fatespinner: Yeah... TQ may be up for some of the playerbase, but it's not for me.
I've run a tracer and I get a beautiful TIME OUT for each and every hop.
C:\Users\Radu>tracert 87.237.38.200
Tracing route to 200.38.237.87.rev.ccp.cc [87.237.38.200]
over a maximum of 30 hops:
1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
[23:41] Fatespinner: His OWN ROUTER isn't returning anything. Makes me wonder how in the hell he managed to post to the forum!
[23:41] Karelzarath: That's totally full of important diagnostic information.
[23:41] Fatespinner: Absolutely. And we're all so very glad that he let it run the full 30 hops.
[23:41] Fatespinner: We might have missed critical info otherwise.
[23:42] Karelzarath: What if it had said something else at hop 29? You would totally have been in the dark without the previous 28 "Request timed out"
[23:42] Karelzarath: This guy should be working for the NSA.
[23:10] Fatespinner: Are you able to connect to EVE? I can't.
[23:10] Karelzarath: Looks like it's back up. They were hit by a DDoS, apparently. O.O
[23:10] Fatespinner: No, yeah, I knew that part.
[23:11] Fatespinner: But myself (and the rest of the Northeast) are still SOL.
[23:11] Fatespinner: Tracing route to 200.38.237.87.rev.ccp.cc [87.237.38.200]
over a maximum of 30 hops:
1 <1 ms 1 ms <1 ms THEMATRIX [192.168.0.1]
2 16 ms 10 ms 18 ms cable1-0.albynytry-ar401.nyroc.rr.com [72.231.14
4.1]
3 31 ms 37 ms 22 ms gig1-0.albynytry-rtr02.nyroc.rr.com [24.29.39.81
]
4 21 ms 24 ms 22 ms gig1-1-0.albynywav-rtr01.nyroc.rr.com [24.29.37.
45]
5 38 ms 23 ms 21 ms ge-4-0-0.albynywav-rtr03.nyroc.rr.com [24.24.7.2
5]
6 46 ms 57 ms 61 ms ae10-0.albynyyf-rtr000.nyroc.rr.com [24.24.21.21
8]
7 55 ms 53 ms 66 ms ae-5-0.cr0.nyc30.tbone.rr.com [66.109.6.74]
8 54 ms 48 ms 57 ms ae-1-0.pr0.nyc20.tbone.rr.com [66.109.6.163]
9 31 ms * 28 ms 107.14.16.14
10 * 107.14.16.14 reports: Destination host unreachable.
Trace complete.
[23:12] Karelzarath: Looks like I'm in.
[23:12] Fatespinner: There's a break in the NE backbone routing.
[23:12] Fatespinner: Other New Yorkers on the EVE forums are reporting the same issue.
[23:12] Fatespinner: (I'm the first one to post the probable cause.) ::whistles::
[23:13] Karelzarath: That's really really strange. I would think the transatlantic route would go through that area.
[23:13] Fatespinner: It does. I can get to the EVE server by way of a Level 3 router in Newark, NJ.
[23:13] Fatespinner: Routed through London, strangely.
[23:14] Fatespinner: But I can't tell the EVE client to do that. :)
[23:14] Karelzarath: Yeah, that's where the NOC is
[23:14] Fatespinner: "Use this route, you bastard."
[23:14] Karelzarath: Maybe if you keep sending traffic down that route, your local router will pick it up as a better route
[23:15] Fatespinner: No, because its the ISP routers that need to learn, not mine.
[23:15] Fatespinner: And all the trans-atlantic shit is probably static routed to cut overhead anyway.
[23:17] Karelzarath: Yeah, probably.
[23:18] Fatespinner: The burden of having the knowledge to solve a problem without the power to actually do it. :(
[23:18] Fatespinner: Sadness.
[23:18] Karelzarath: You should call up yout ISP and be all "You should add these routes to your routing tables." ;)
[23:19] Fatespinner: I suppose I could just call my ISP. "Route my traffic for destination XYZ through Level 3, IP address 212.187.160.62."
[23:19] Fatespinner: "Fuck the rest of New York, I just want MY shit to work. :P"
[23:19] Karelzarath: Your response would be seconds of silence and a "Huh?"
[23:19] Fatespinner: At which point I would ask to speak with Tier 4. :)
[23:20] Fatespinner: I have dealt on highly technical levels with this ISP before.
[23:20] Fatespinner: As part of my job. :)
[23:20] Karelzarath: Hell, then, do it! :D
[23:21] Fatespinner: I'm pretty sure tech support isn't available for residential customers at 11:30pm. :)
[23:26] Fatespinner: Ah well, they have 2 days, 23 hours, 43 minutes, and 40 seconds to figure shit out.
[23:28] Fatespinner: HAHAHAHA.
[23:28] Fatespinner: Someone on the forums is using an SSH tunnel to his University which has a VPN to a European campus. LAWL
[23:28] Fatespinner: So *he* can get on.
[23:28] Fatespinner: That is so epic.
[23:30] Karelzarath: That is frikkin awesome
[23:30] Fatespinner: Yeah, we have no such awesomeness at my office that I could take advantage of.
[23:33] Fatespinner: Ah, apparently CCP has temporarily blacklisted the ISPs identified in the DDoS attack.
[23:33] Karelzarath: Sensible precaution, I suppose
[23:34] Fatespinner: And when i was routing through Level 3, I was leaving my ISPs network and then coming BACK into Europe. And, of course, routers only see the source IP of the previous router, not the actual source IP until it reaches the destination.
[23:34] Fatespinner: Oh you wacky OSI model.
[23:34] Karelzarath: lol
[23:35] Karelzarath: So, your ISP is one of the blacklisted ones?
[23:35] Fatespinner: Apparently.
[23:35] Fatespinner: As is something called 'Eurorings' in... well, Europe.
[23:36] Karelzarath: Can't you just invisibly route your traffic through another ISP? They do it all the time on TV!
[23:36] * Karelzarath tsks
[23:36] Fatespinner: Yeeeaaaaaaah, maybe if I had vastly superior routing hardware here, like a Cisco ASA 5500.
[23:36] Fatespinner: But, alas, I have a Linksys E2000.
[23:37] Karelzarath: I bet you can't crack a password in 5 keystrokes, either. Geez. Why are they paying you? ;)
[23:38] Fatespinner: Actually, password cracking is a little beyond my skill unless I have physical access to the machine in question.
[23:38] Fatespinner: But yeah, it requires a few more than 5 keystrokes.
[23:38] Karelzarath: lol
[23:38] Fatespinner: Ctrl + Alt + Hax0r is not an option on standard keyboards.
[23:39] Karelzarath: It is in Linux.
[23:39] Fatespinner: Hehe, the 'Hax Lock' key.
[23:39] Karelzarath: lol!
[23:40] Fatespinner: Its funny seeing other people on the forums who clearly have NO IDEA what they're doing posting traceroutes.
[23:40] Fatespinner: Like this rockstar:
[23:40] Fatespinner: Yeah... TQ may be up for some of the playerbase, but it's not for me.
I've run a tracer and I get a beautiful TIME OUT for each and every hop.
C:\Users\Radu>tracert 87.237.38.200
Tracing route to 200.38.237.87.rev.ccp.cc [87.237.38.200]
over a maximum of 30 hops:
1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
[23:41] Fatespinner: His OWN ROUTER isn't returning anything. Makes me wonder how in the hell he managed to post to the forum!
[23:41] Karelzarath: That's totally full of important diagnostic information.
[23:41] Fatespinner: Absolutely. And we're all so very glad that he let it run the full 30 hops.
[23:41] Fatespinner: We might have missed critical info otherwise.
[23:42] Karelzarath: What if it had said something else at hop 29? You would totally have been in the dark without the previous 28 "Request timed out"
[23:42] Karelzarath: This guy should be working for the NSA.