May 2014 - Test - lists.nanog.org

indulgence satiated
by manning bill 28 May '14

28 May '14

Thanks All for taking the time to prod 2001:500:84::b Looks like it is reachable from many places… enough that we will proceed to augment the “B” root server with perhaps the last in a long line of IPv6 addresses that it has had over the last 15 years. Splay will increase over time. /bill /bill Neca eos omnes. Deus suos agnoscet.

1 0

Re: [dns-wg] crave your indulgence
by Daniel Karrenberg 28 May '14

28 May '14

On 28.05.14 8:55 , Daniel Karrenberg wrote: > ... you discover that local connectivity is through HE and Los Nettos. .... Ouch! I just got hit by my own wrong default of excluding hops with no response. There is no direct link to HE evident from the traceroutes. I wish ICMP "TTL Exceeded" responses were more reliable ... Correct graph with * hops included. Daniel

1 0

crave your indulgence
by manning bill 28 May '14

28 May '14

If you wouldn’t mind a quick tracerooute - Can you confirm reachability to the following: 2001:500:84::b Thanks in advance. /bill Neca eos omnes. Deus suos agnoscet.

10 9

Cogent / Internap issue ??
by Matthew Huff 27 May '14

27 May '14

We are having troubles reaching services on the other side of cogent/internap peering. Anyone else seeing issues? Basically 14607 -> 6128 -> 174 -> 14744. Type escape sequence to abort. Tracing the route to 72.5.52.199 VRF info: (vrf in name/id, vrf out name/id) 1 24.157.32.249 [AS 6128] 4 msec 4 msec 4 msec 2 24.38.117.6 [AS 6128] 4 msec 8 msec 4 msec 3 167.206.183.29 [AS 6128] 4 msec 4 msec 8 msec 4 * * * 5 * * * 6 154.54.47.17 [AS 174] 4 msec 154.54.47.29 [AS 174] 8 msec 154.54.44.69 [AS 174] 4 msec 7 66.28.4.202 [AS 174] 28 msec 28 msec 154.54.6.190 [AS 174] 28 msec 8 154.54.6.85 [AS 174] 40 msec 154.54.24.81 [AS 174] 36 msec 154.54.6.117 [AS 174] 40 msec 9 154.54.26.113 [AS 174] 52 msec 154.54.26.121 [AS 174] 52 msec 154.54.26.129 [AS 174] 48 msec 10 154.54.25.70 [AS 174] 64 msec 154.54.25.66 [AS 174] 60 msec 154.54.25.70 [AS 174] 60 msec 11 154.54.2.197 [AS 174] 92 msec 88 msec 84 msec 12 154.54.0.249 [AS 174] 80 msec 154.54.0.253 [AS 174] 80 msec 154.54.0.249 [AS 174] 84 msec 13 154.54.41.142 [AS 174] 152 msec 224 msec 92 msec 14 38.122.90.42 [AS 174] 84 msec 84 msec 38.104.124.82 [AS 174] 80 msec 15 63.251.160.18 [AS 14744] 76 msec 76 msec 72 msec 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * ---- Matthew Huff | 1 Manhattanville Rd Director of Operations | Purchase, NY 10577 OTA Management LLC | Phone: 914-460-4039

2 2

RIPE Atlas data parsing
by Ca By 27 May '14

27 May '14

Folks, Yes, RIPE Atlas is great. It generates output as JSON. Is there dummy tool for summarizing this JSON data and possibly visualizing it? I could write my own, but i imagine someone has already done this somewhere. No? CB

4 3

Re: crave your indulgence
by Hank Nussbacher 27 May '14

27 May '14

At 14:47 27/05/2014 -0400, Christopher Morrow wrote: >Measurement: 1666834 should be bill's measurement request... 50 >icmptraceroutes from around the globez. Or ring-ping and ring-trace: https://ring.nlnog.net/toolbox/ -Hank >On Tue, May 27, 2014 at 2:35 PM, Brian Rak <brak(a)gameservers.com> wrote: > > This seems like a perfect use for ATLAS: https://atlas.ripe.net/ > > > > > > On 5/27/2014 2:28 PM, manning bill wrote: > >> > >> If you wouldn't mind a quick tracerooute - Can you confirm reachability > >> to the following: > >> > >> 2001:500:84::b > >> > >> Thanks in advance. > >> > >> /bill > >> Neca eos omnes. Deus suos agnoscet. > >> > >

2 1

re: Contact for Road Runner
by Nick Olsen 27 May '14

27 May '14

Hey Faisal, We use to have peering with Road Runner (Bright House Networks) ~6 years ago. At that time, They created a RR object (RADB) for our AS that specifically said ROAD RUNNER. Which caused all kinds of havoc as some databases would pull that over the "AS NAME" when listing our network. They even updated the registry a couple of times in the years following our termination of their service. Emails to their RADB email, As well as to their direct support went completely unanswered. The solution for me was asking Merit (RADB's Parent company..whatever they are). To forcibly remove the entry, They did so about two hours after my email to them and were extremely helpful. Nick Olsen Network Operations (855) FLSPEED x106 ---------------------------------------- From: "Faisal Imtiaz" <faisal(a)snappytelecom.net> Sent: Tuesday, May 27, 2014 9:52 AM To: "NANOG" <nanog(a)nanog.org> Subject: Contact for Road Runner Hello, I am looking to get in touch with anyone who is responsible for Routing Registry Objects at Road Runner Cable. Can you please reply back to me off list. (We need to have an older ASN RR Object Created by rr.com to be removed please). Thanks. Faisal Imtiaz Snappy Internet & Telecom 7266 SW 48 Street Miami, FL 33155 Tel: 305 663 5518 x 232 Help-desk: (305)663-5518 Option 2 or Email: Support(a)Snappytelecom.net

1 0

Contact for Road Runner
by Faisal Imtiaz 27 May '14

27 May '14

Hello, I am looking to get in touch with anyone who is responsible for Routing Registry Objects at Road Runner Cable. Can you please reply back to me off list. (We need to have an older ASN RR Object Created by rr.com to be removed please). Thanks. Faisal Imtiaz Snappy Internet & Telecom 7266 SW 48 Street Miami, FL 33155 Tel: 305 663 5518 x 232 Help-desk: (305)663-5518 Option 2 or Email: Support(a)Snappytelecom.net

1 0

Re: Large DDoS, small extortion
by Larry Sheldon 25 May '14

25 May '14

On 5/24/2014 11:29 AM, Anne P. Mitchell, Esq. wrote: > >> Law enforcement and victims have different objectives. Law >> enforcement wants to find the criminal, gather sufficient evidence >> to prove their guilt, then prosecute them. More attacks helps law >> enforcement. >> >> The victims, in general, want the attacks to stop. > > Actually, our experience in this particular case (it is the same > person(s) hitting all of the targets, even using the same email > addresses, etc.) is that the victims want to find the guy too. In > fact, I can say with a fair degree of certainty that the coordinated > efforts of a dedicated group of "victims", who have come together > without regards to the fact that they are otherwise 'competitors' in > business, and who have furnished the agencies with useable technical > information about the attacks, have given the agencies a substantial > leg up in the investigation. All that from a far greater authority than I. But lest my weak words be misunderstood, I have no objection what ever to providing technical information (and facilities, even)--it is ONLY the paying of ransom that I object to. And I think I would say that if I were the captive. I think over the long haul the odds are that if you DO pay the ransom, the victim will be dead anyway. -- Requiescas in pace o email Two identifying characteristics of System Administrators: Ex turpi causa non oritur actio Infallibility, and the ability to learn from their mistakes. (Adapted from Stephen Pinker)

1 0

Linkedin Peering Contact
by Faisal Imtiaz 24 May '14

24 May '14

Hello, I am trying to contact the folks responsible for Linkedin Peering. Can you please send me you contact info off list. (emails to addresses listed in peeringdb are being bounced back by the mail server) Thanks Faisal Imtiaz Snappy Internet & Telecom 7266 SW 48 Street Miami, FL 33155 Tel: 305 663 5518 x 232 Help-desk: (305)663-5518 Option 2 or Email: Support(a)Snappytelecom.net

1 1