July 2013 - Test - lists.nanog.org

Re: Office 365..? how Microsoft handed the NSA access to encrypted messages
by Scott Weeks 11 Jul '13

11 Jul '13

--- wbailey(a)satelliteintelligencegroup.com wrote: From: Warren Bailey <wbailey(a)satelliteintelligencegroup.com> Anyone else planning on bailing from office365? http://m.guardian.co.uk/world/2013/jul/11/microsoft-nsa-collaboration-user-… ---------------------------------------------------------- Bail on M$ period. If they give the data willingly this way, I'm sure they also do it in other currently unknown ways. Company culture and all that... scott

3 2

On topic of domains
by Jon Mitchell 11 Jul '13

11 Jul '13

After .nyc thread, thought this IAB announcement may be of interest. http://www.iab.org/documents/correspondence-reports-documents/2013-2/iab-st… -Jon

9 8

roadrunner takes a really long excursion
by Randy Bush 11 Jul '13

11 Jul '13

ryuu.psg.com:/Users/randy> traceroute wrt-tokyo.rg.net traceroute to wrt-tokyo.rg.net (210.138.216.50), 64 hops max, 52 byte packets 1 wrt-hawi.lan (192.168.0.1) 1.089 ms 0.838 ms 0.805 ms 2 cpe-72-130-240-1.hawaii.res.rr.com (72.130.240.1) 28.964 ms 27.591 ms 27.825 ms 3 tge7-5.klaohias-cer03.hawaii.rr.com (24.25.231.29) 40.011 ms 25.291 ms 48.273 ms 4 tge8-1.klaohias-cer02.hawaii.rr.com (72.129.46.144) 61.741 ms 62.058 ms 60.293 ms 5 tge0-4-0-2.kmlahi07-ccr01.hawaii.rr.com (72.129.46.128) 63.927 ms 74.082 ms 64.340 ms 6 agg31.tustcaft-ccr01.socal.rr.com (72.129.45.2) 71.929 ms 64.954 ms 64.037 ms 7 107.14.17.134 (107.14.17.134) 60.455 ms 65.103 ms 63.598 ms 8 ae-5-0.cr0.dca20.tbone.rr.com (66.109.6.3) 130.063 ms 133.030 ms 134.285 ms 9 107.14.17.178 (107.14.17.178) 133.206 ms ae-0-0.cr0.dca10.tbone.rr.com (66.109.6.30) 130.485 ms 107.14.17.178 (107.14.17.178) 132.164 ms 10 ae0.pr1.dca10.tbone.rr.com (107.14.17.200) 185.126 ms ae1.pr1.dca10.tbone.rr.com (107.14.17.202) 132.416 ms ae0.pr1.dca10.tbone.rr.com (107.14.17.200) 132.197 ms 11 209.48.38.225 (209.48.38.225) 153.804 ms 149.394 ms 152.942 ms 12 vb2000d2.rar3.washington-dc.us.xo.net (207.88.13.66) 158.140 ms 168.326 ms 168.755 ms 13 te-11-0-0.rar3.sanjose-ca.us.xo.net (207.88.12.69) 156.495 ms 160.694 ms 158.592 ms 14 207.88.14.226.ptr.us.xo.net (207.88.14.226) 158.936 ms 161.480 ms 149.665 ms 15 216.98.100.253 (216.98.100.253) 142.506 ms 141.179 ms 140.945 ms 16 sjc002bf02.iij.net (206.132.169.9) 141.301 ms 143.095 ms sea001bf00.iij.net (206.132.168.1) 157.606 ms 17 tky009bf01.iij.net (206.132.169.122) 409.387 ms tky008bf00.iij.net (206.132.169.110) 325.051 ms tky008bf01.iij.net (206.132.169.174) 248.289 ms 18 tky001bb11.iij.net (58.138.80.42) 259.764 ms tky001bb10.iij.net (58.138.80.10) 243.385 ms tky001bb11.iij.net (58.138.80.42) 352.163 ms 19 tky001lip20.iij.net (58.138.100.214) 409.185 ms 406.441 ms tky001lip20.iij.net (58.138.100.210) 409.536 ms 20 tokyo10-ntteast0.flets.2iij.net (210.149.34.98) 257.222 ms 409.180 ms 314.596 ms 21 tokyo10-f03.flets.2iij.net (210.149.34.158) 299.887 ms 306.765 ms 307.255 ms 22 50.216.138.210.bn.2iij.net (210.138.216.50) 409.697 ms 409.540 ms 409.365 ms well, i guess it could have gone through europe after dca to get to their xo peering. i guess the root cause is that roadrunner is poorly peered. are they not actually twt? randy

5 5

roadrunner takes a really long excursion
by Randy Bush 11 Jul '13

11 Jul '13

ryuu.psg.com:/Users/randy> traceroute wrt-tokyo traceroute to wrt-tokyo.rg.net (210.138.216.50), 64 hops max, 52 byte packets 1 wrt-hawi.lan (192.168.0.1) 1.089 ms 0.838 ms 0.805 ms 2 cpe-72-130-240-1.hawaii.res.rr.com (72.130.240.1) 28.964 ms 27.591 ms 27.825 ms 3 tge7-5.klaohias-cer03.hawaii.rr.com (24.25.231.29) 40.011 ms 25.291 ms 48.273 ms 4 tge8-1.klaohias-cer02.hawaii.rr.com (72.129.46.144) 61.741 ms 62.058 ms 60.293 ms 5 tge0-4-0-2.kmlahi07-ccr01.hawaii.rr.com (72.129.46.128) 63.927 ms 74.082 ms 64.340 ms 6 agg31.tustcaft-ccr01.socal.rr.com (72.129.45.2) 71.929 ms 64.954 ms 64.037 ms 7 107.14.17.134 (107.14.17.134) 60.455 ms 65.103 ms 63.598 ms 8 ae-5-0.cr0.dca20.tbone.rr.com (66.109.6.3) 130.063 ms 133.030 ms 134.285 ms 9 107.14.17.178 (107.14.17.178) 133.206 ms ae-0-0.cr0.dca10.tbone.rr.com (66.109.6.30) 130.485 ms 107.14.17.178 (107.14.17.178) 132.164 ms 10 ae0.pr1.dca10.tbone.rr.com (107.14.17.200) 185.126 ms ae1.pr1.dca10.tbone.rr.com (107.14.17.202) 132.416 ms ae0.pr1.dca10.tbone.rr.com (107.14.17.200) 132.197 ms 11 209.48.38.225 (209.48.38.225) 153.804 ms 149.394 ms 152.942 ms 12 vb2000d2.rar3.washington-dc.us.xo.net (207.88.13.66) 158.140 ms 168.326 ms 168.755 ms 13 te-11-0-0.rar3.sanjose-ca.us.xo.net (207.88.12.69) 156.495 ms 160.694 ms 158.592 ms 14 207.88.14.226.ptr.us.xo.net (207.88.14.226) 158.936 ms 161.480 ms 149.665 ms 15 216.98.100.253 (216.98.100.253) 142.506 ms 141.179 ms 140.945 ms 16 sjc002bf02.iij.net (206.132.169.9) 141.301 ms 143.095 ms sea001bf00.iij.net (206.132.168.1) 157.606 ms 17 tky009bf01.iij.net (206.132.169.122) 409.387 ms tky008bf00.iij.net (206.132.169.110) 325.051 ms tky008bf01.iij.net (206.132.169.174) 248.289 ms 18 tky001bb11.iij.net (58.138.80.42) 259.764 ms tky001bb10.iij.net (58.138.80.10) 243.385 ms tky001bb11.iij.net (58.138.80.42) 352.163 ms 19 tky001lip20.iij.net (58.138.100.214) 409.185 ms 406.441 ms tky001lip20.iij.net (58.138.100.210) 409.536 ms 20 tokyo10-ntteast0.flets.2iij.net (210.149.34.98) 257.222 ms 409.180 ms 314.596 ms 21 tokyo10-f03.flets.2iij.net (210.149.34.158) 299.887 ms 306.765 ms 307.255 ms 22 50.216.138.210.bn.2iij.net (210.138.216.50) 409.697 ms 409.540 ms 409.365 ms well, i guess it could have gone through europe after dca to get to their xo peering in san jose. randy

1 0

File transfer speed between Hong Kong and Johannesburg, South Africa
by Luan Nguyen 11 Jul '13

11 Jul '13

Hello folks, Does anyone know what's the average speed for windows file transferring (SMB2) between Hong Kong and Johannesburg? Any guide on how to calculate/estimate this? Thanks. Regards, -Luan

10 13

Typical link speeds between COs
by Jean-Francois Mezei 11 Jul '13

11 Jul '13

What are the typical speeds used on fibre links between COs in North American and elsewhere ? I realise that there are special cases, such as Shaw using WDM to reach 400gigabits/sec in a link in Western Canada. But what are the most common speeds ? Is WDM in common use to multiplex multiple 10gbps, 40gbps links ? Or is that used mostly for intercity trunks and intra-city trunks tend to not bother with WDM because of ample supply of fibre ? Do telcos typically quickly upgrade fibre strands to newer speeds, or are there still many strands handling only 100mbps or 1gbps between COs because telcos never got around to upgrading legacy equipment/services (such as ATM etc) ? Also in terms of costing WDM, would one typically have a card that has the multiple colours in the card and outputs a single multi-colour signal or would one typically have separate cards for each colour and then use a WDM "filter" to combine/separate colours onto the single strand ?

2 1

verizon postmaster
by John Zettlemoyer 11 Jul '13

11 Jul '13

Could someone from Verizon Postmaster please contact me off list? Thank you John Zettlemoyer Sr. Director of I.T. Infrastructure WCiT - West-Canaan LLC john(a)wcit.net

1 0

Re: File transfer speed between Hong Kong and Johannesburg, South Africa
by Clayton Zekelman 11 Jul '13

11 Jul '13

It all depends on the air speed velocity of an unladen swallow, and varies if it is African or Eurpoean. In all seriousness, you need to know the speed and latency of the link before that question can be answered. At 10:04 AM 11/07/2013, Luan Nguyen wrote: >Hello folks, > >Does anyone know what's the average speed for windows file transferring >(SMB2) between Hong Kong and Johannesburg? >Any guide on how to calculate/estimate this? > >Thanks. > >Regards, > >-Luan --- Clayton Zekelman Managed Network Systems Inc. (MNSi) 3363 Tecumseh Rd. E Windsor, Ontario N8W 1H4 tel. 519-985-8410 fax. 519-985-8409

1 0

whois.internic.net / whois.crsnic.net IPv6 timeouts
by Stephen Frost 10 Jul '13

10 Jul '13

All, Don't know if it'll help or if this is simply old news to most, but the whois systems (whois.internic.net/whois.crsnic.net) have AAAA records and happily answer TCP/43 requests w/ the usual blurb, but all the servers I've hit then fail to actually provide data and instead the whois client (Ubuntu 13.04) simply time-outs. sfrost@tamriel:/home/sfrost> whois -h 2001:503:5ae2:1060::74 networksolutions.com Whois Server Version 2.0 Domain names in the .com and .net domains can now be registered with many different competing registrars. Go to http://www.internic.net for detailed information. Timeout. Servers that I've tried so far (all IPv6 addresses I got through running 'host whois.crsnic.net'): 2001:503:5419:1060::74 2001:503:3227:1060::74 2001:503:6810:1060::74 2001:503:bfb0:1060::74 2001:500:30ff:1060::74 2001:503:7bbf:1060::74 2001:502:be98:1060::74 2001:502:8c25:1060::74 Anyone from NetSol care? It's not the end of the world, but it certainly is quite annoying.. Judging by some complaints on the 'net, looks to be a rather long-standing issue too (there's a Debian bug #683187 which mentions similar issues from nearly a year ago..). Thanks, Stephen

4 5

google troubles?
by Mike Jackson 10 Jul '13

10 Jul '13

I can see the Google IP space (64.71.240.0/20) from Verizon/AS701, but not from Rogers/AS812 in Toronto. I've done a few other test traceroutes through Rogers to verify that they didn't filter UDP/ICMP. At this point nothing would surprise me from Rogers. AS701 ===== TOR2-CORE-R1#traceroute www.google.com Translating "www.google.com"...domain server (8.8.8.8) [OK] Type escape sequence to abort. Tracing the route to www.google.com (74.125.26.99) VRF info: (vrf in name/id, vrf out name/id) 1 x.x.x.x [AS701] 4 msec 0 msec 0 msec 2 0.ge-11-0-0.XT4.TOR2.ALTER.NET (152.63.133.78) [AS 701] 4 msec 0 msec 4 msec 3 0.so-4-0-3.XT2.NYC4.ALTER.NET (152.63.0.73) [AS 701] 16 msec 16 msec 16 msec 4 TenGigE0-7-1-0.GW8.NYC4.ALTER.NET (152.63.21.125) [AS 701] 20 msec TenGigE0-5-1-0.GW8.NYC4.ALTER.NET (152.63.21.73) [AS 701] 16 msec TenGigE0-5-4-0.GW8.NYC4.ALTER.NET (152.63.18.206) [AS 701] 20 msec 5 72.14.238.232 [AS 15169] 16 msec 16 msec 20 msec 6 72.14.236.208 [AS 15169] [MPLS: Label 680976 Exp 4] 16 msec 16 msec 72.14.236.206 [AS 15169] [MPLS: Label 533197 Exp 4] 20 msec 7 209.85.249.11 [AS 15169] [MPLS: Label 16668 Exp 4] 24 msec 72.14.239.93 [AS 15169] [MPLS: Label 14644 Exp 4] 24 msec 209.85.249.11 [AS 15169] [MPLS: Label 13978 Exp 4] 24 msec 8 209.85.243.114 [AS 15169] [MPLS: Label 568789 Exp 4] 32 msec 209.85.241.222 [AS 15169] [MPLS: Label 632535 Exp 4] 32 msec 32 msec 9 216.239.48.159 [AS 15169] 36 msec 32 msec 216.239.48.59 [AS 15169] 32 msec 10 www.google.com (74.125.26.147) [AS 15169] 32 msec 32 msec 32 msec AS812 (Rogers Looking Glass https://supernoc.rogerstelecom.net/lg/) =================================================== *Query:* *tr 64.71.249.45* Type escape sequence to abort. Tracing the route to 64.71.249.45 1 64.71.255.62 0 msec 0 msec 0 msec 2 ge-4-3-0.gw02.ym.phub.net.cable.ROGERS.com (66.185.82.237) 4 msec 4 msec 4 msec 3 69.63.250.189 4 msec 4 msec 4 msec 4 69.63.250.174 4 msec 4 msec 4 msec 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * Cheers, - MJ -----Original Message----- > From: Grant Ridder [mailto:shortdudey123@gmail.com] > Sent: July-10-13 10:57 AM > To: John York > Cc: nanog(a)nanog.org > Subject: Re: google troubles? > > Does anyone have traceroutes showing where the issues are? > > -Grant > > On Wed, Jul 10, 2013 at 7:45 AM, John York > <johny(a)griffintechnology.com>wrote: > > > We saw the same thing, but seems to be cleared up now. All our > > providers that routed to Google addresses in ATL had the issue. We > > have one provider that lands on Google addresses in DFW, and it was > working. > > > > ...And now I see that it isn't completely resolved. Some Google apps > > are still inaccessible via the Atlanta routes. > > > > > > > > > > On Wed, Jul 10, 2013 at 9:28 AM, Blair Trosper > > <blair.trosper(a)gmail.com > > >wrote: > > > > > Seeing lots of reports of people unable to get to many Google > services. > > > Seems to be affecting Comcast users disproportionately. It's fine > > > for > > me, > > > but a lot of my staff are basically out of luck...but according to > > > the Google Apps Status page, everything is fine. > > > > > > It's anecdotal, but it would seem like there's an issue based on > > > these reports. > > > > > > Oh, and this: > > > http://www.cnn.com/2013/07/10/tech/web/google-down/index.html > > > > > > Anyone know what's up? Fiber cut? DC outages? > > > > > > -- blair > > > > > > > > > > > -- > > > > John York > > > > Information Technology | Network Administrator > > > > Phone: 615-399-7000 x:333 > > > > Griffin Technology > > 2030 Lindell Avenue Nashville, TN 37203 USA > > > > This message and any attachments should be treated as confidential > > information of Griffin Technology, Inc. > > > > > >

2 7