June 2011 - Test - lists.nanog.org

Why don't ISPs peer with everyone?
by rucasbrown＠hushmail.com 07 Jun '11

07 Jun '11

Hello, I wouldn't consider myself a network engineer, nor do I have any formal training, but why don't ISPs peer with every other ISP? It would only save EVERYONE money if they did this, no? Only issue I see is with possibly hijacked / malicious AS owners, but that's not very common to do without being caught. All the whole "don't peer with this guy" only makes your customers have worse latencies and paths to other people, making the Internet less healthy. Thanks, Rucas PS: sorry if I sent this twice; client lagged a bit.

27 33

Re: [v6z] Re: IPv6 day fun is beginning!
by fredrik danerklint 07 Jun '11

07 Jun '11

Sorry about this. When asked for the right thing it does resolv! $ dig aaaa www.facebook.com ;; QUESTION SECTION: ;www.facebook.com. IN AAAA ;; ANSWER SECTION: www.facebook.com. 30 IN AAAA 2620:0:1c08:4000:face:b00c:0:3 > That's because you're asking the wrong nameservers. The response you're > getting is pointing you to the correct nameservers (glb1/glb2.facebook.com) > which are defintely returning AAAA records for me : > > $ dig +short aaaa www.facebook.com @glb1.facebook.com > 2620:0:1c08:4000:face:b00c:0:3 > > Scott. > > > On Tue, Jun 7, 2011 at 5:04 PM, fredrik danerklint > > <fredan-nanog(a)fredan.se>wrote: > > This is from Sweden. > > > > $ dig any www.facebook.com @ns1.facebook.com > > > > ; <<>> DiG 9.7.3 <<>> any www.facebook.com @ns1.facebook.com > > ;; global options: +cmd > > ;; Got answer: > > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61742 > > ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 2 > > ;; WARNING: recursion requested but not available > > > > ;; QUESTION SECTION: > > ;www.facebook.com. IN ANY > > > > ;; AUTHORITY SECTION: > > www.facebook.com. 86400 IN NS glb1.facebook.com. > > www.facebook.com. 86400 IN NS glb2.facebook.com. > > > > ;; ADDITIONAL SECTION: > > glb1.facebook.com. 3600 IN A 69.171.239.10 > > glb2.facebook.com. 3600 IN A 69.171.255.10 > > > > ;; Query time: 58 msec > > ;; SERVER: 204.74.66.132#53(204.74.66.132) > > ;; WHEN: Wed Jun 8 02:01:37 2011 > > ;; MSG SIZE rcvd: 104 > > > > > > No AAAA records at the moment. Checked alll their nameservers. > > > > -- > > //fredan -- //fredan

1 0

v6 transit swaps harmful
by Jeff Wheeler 07 Jun '11

07 Jun '11

In case there are folks who missed this in the past few years, we will soon be past the point where IPv6 transit swaps and other incubation tools are acceptable to customers. How is it that Tiscali and Sprint can only get together via IIJ? Who is to blame? From my perspective, all three networks. I'll spare you the rest of my hand-waving and just paste the route: % host -t AAAA www.sprint.net www.sprint.net has IPv6 address 2600:: 2600::/29 AS path: 3257 2497 6175 1239 1239 1239 1239 1239 1239 1239 I % traceroute6 -q1 -f2 2600:: traceroute6 to 2600:: (2600::) from [redacted], 64 hops max, 12 byte packets Skipping 1 intermediate hops 2 xe-10-3-0.nyc20.ip6.tinet.net (2001:668:0:2::1:892) 10.896 ms 3 2001:504:1::a500:2497:1 (2001:504:1::a500:2497:1) 13.511 ms 4 sjc002bb01.iij.net (2001:48b0:bb00:8019::4008) 89.263 ms 5 sjc002ix02.iij.net (2001:48b0:bb03:f::4015) 87.075 ms 6 sl-bb1v6-sj-t-40.sprintv6.net (2001:440:eeee:ffcd::1) 92.491 ms 7 sl-crs2-sj-po0-1-4-0.v6.sprintlink.net (2600:0:2:1239:144:232:1:123) 89.333 ms 8 sl-crs1-sj-po0-9-5-0.v6.sprintlink.net (2600:0:2:1239:144:232:2:108) 95.966 ms 9 sl-crs2-ria-po0-3-5-0.v6.sprintlink.net (2600:0:2:1239:144:232:9:114) 97.788 ms 10 sl-crs2-fw-po0-13-2-0.v6.sprintlink.net (2600:0:2:1239:144:232:25:160) 173.331 ms 11 sl-crs1-fw-po0-12-0-0.v6.sprintlink.net (2600:0:2:1239:144:232:18:145) 165.577 ms 12 sl-crs3-fw-po0-7-0-0.v6.sprintlink.net (2600:0:2:1239:144:232:1:45) 167.203 ms 13 sl-crs3-atl-po0-2-0-0.v6.sprintlink.net (2600:0:2:1239:144:232:8:20) 169.195 ms 14 sl-crs1-atl-po0-11-0-0.v6.sprintlink.net (2600:0:2:1239:144:232:4:48) 170.922 ms 15 sl-crs1-ffx-po0-8-0-0.v6.sprintlink.net (2600:0:2:1239:144:232:18:119) 172.688 ms 16 sl-crs1-orl-po0-0-0-0.v6.sprintlink.net (2600:0:2:1239:144:232:19:251) 177.762 ms 17 sl-lkdstr2-p1-0.v6.sprintlink.net (2600:0:3:1239:144:223:33:32) 177.450 ms 18 www.sprint.net (2600::) 172.235 ms -- Jeff S Wheeler <jsw(a)inconcepts.biz> Sr Network Operator / Innovative Network Concepts

1 0

IPv6 day - Facebook announcements
by Jay Ashworth 07 Jun '11

07 Jun '11

In addition to themselves announcing this, NASA.gov and Markertek.com have announced there that they're participating with their websites; I'll reply to this posting if I see any others (and if anyone better positioned to report on their success posts, I'll pass it along). Cheers, -- jr 'yes; just to prove I know the difference' a -- Jay R. Ashworth Baylink jra(a)baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII St Petersburg FL USA http://photo.imageinc.us +1 727 647 1274

1 0

Spare part handling in the LA area
by Simon Allard 07 Jun '11

07 Jun '11

Hi Nanog We are an ISP/ASP in New Zealand, but we have a presence in Equinix LA1. We are looking for a services company that can store spare router/mux parts in the LA area, and who can deliver with a good SLA to the Equinix LA1 site. We will eventually be looking for the same type of service in the San Jose area, so a company that has a wide presence would be preferred. Please contact me off list if you have suggestions/recommendations Happy ipv6 day! J Regards Simon Allard Head of Networks Orcon

1 0

automated router config back up
by Jon Heise 07 Jun '11

07 Jun '11

Aside from rancid, what methods do people have for doing automated backups and diffing of router configs ? - Jon Heise

10 9

ipv6 day DDoS threat?
by Mark Pace 07 Jun '11

07 Jun '11

I got an interesting contact from a large company that I will leave un-named for the moment. They said that they heard specific "chatter" about DDoS of IPv6 day participant sites and even more specifically about our website. Of course they have also offered to assist us in preventing this from affecting our site. I'm very skeptical about even calling said company at this point. I'm really feeling like this is a shakedown and was wondering if anyone else had been approached in a similar fashion? Mark Pace

9 9

RE: ipv6 day DDoS threat?
by 1qaz 2wsx 07 Jun '11

07 Jun '11

We too just received this phone call. The company was Verisign, felt an awful lot like a protection racket. Very unwelcomed phone call. Buyer Beware. ^1qaz2wsx^

1 0

Cogent?
by Ryan Finnesey 07 Jun '11

07 Jun '11

Does cogent have a true carrier/wholesale team? Cheers Ryan Sent from my Windows Phone

3 4

v6 proof of life
by Paul Vixie 07 Jun '11

07 Jun '11

it's been a while since i looked at the query stream still hitting {rbl,dul}.maps.vix.com. this was the world's first RBL but it was renamed from maps.vix.com to mail-abuse.org back in Y2K or so. i have not sent anything but NXDOMAIN in response to one of these queries for at least ten years, yet the queries just keep coming. here's a histogram of source-ip. feel free to remove yourself :-). it's just a half hour sample. i'll put this up on a web page soon. importantly and happily, there's a great deal of IPv6 happening here. re: 524 200.59.134.164 492 2001:288:8201:1::14 455 209.177.144.50 418 193.124.83.73 392 140.144.32.205 360 143.54.204.171 355 208.76.170.121 282 2403:2c00:1::5 262 2001:1a80:103:5::2 225 2001:288:8201:1::2 195 2604:3500::ad:1 186 2001:288:8201:1::10 174 209.157.254.10 167 2001:b30:1:100::100 158 12.47.198.68 142 2001:288:0:2::60 125 2002:d58e:8901::d58e:8901 118 77.72.136.2 115 140.118.31.99 113 66.240.198.100 102 2001:9b0:1:601:230:48ff:fe8a:c7f4 100 2001:888:0:24:194:109:20:107 99 212.73.100.132 92 2405:d000:0:100::214 86 202.177.26.107 83 2405:d000:0:100::228 82 195.101.253.253 77 210.175.244.210 77 2001:558:1014:f:69:252:96:24 76 64.168.228.129 76 2001:2c0:11:1::c02 71 2001:b30:1::190 68 2001:558:1014:f:68:87:76:185 68 2001:4dd0:100:1020:53:2:0:1 67 2001:558:1014:f:69:252:96:22 67 2001:558:1014:f:68:87:76:189 63 2001:558:1014:f:69:252:96:25 57 2607:f758:6000:13::e4 56 2001:558:1014:f:68:87:76:181 55 212.234.229.242 52 2607:f758:e000:13::e4 51 2607:fdb8:0:b:2::2 51 208.188.98.249 51 2001:558:1014:f:68:87:76:190 49 66.192.109.211 45 2001:558:1014:f:69:252:96:23 44 2001:db8::230:48ff:fef2:f340 44 2001:db8::230:48ff:fef0:1de 42 213.171.61.117 41 201.116.43.232 40 2607:fdb8:0:b:1::2 40 2001:470:1f0a:c1b::2 40 190.82.65.243 38 190.169.30.2 36 2605:d400:0:27::3 35 2001:d10:2:3::1:2 31 2605:d400:0:27::7 30 220.110.24.250 28 84.55.220.139 28 2a00:1db0:16:2::347:2 23 2607:f2e0::1:3:2 23 2001:15c8:8::2:1 22 218.44.167.26 22 2001:6c8:2:100::53 22 2001:6b0:1::201 21 193.169.45.5 20 2607:f470:1003::3:3 19 2a01:8c00:ff60:2:230:48ff:fe85:d47e 19 221.133.36.229 19 213.178.66.2 19 202.169.240.10 19 2001:c28:1:1:dad3:85ff:fee1:30ec 19 163.29.248.1 18 195.58.224.34 17 2a02:460:4:0:250:56ff:fea7:23d 17 221.245.76.99 17 2001:c28:1:1:dad3:85ff:fee0:4f68 16 2001:630:200:8120::d:1 15 2a01:1b8::1 15 218.44.236.98 15 2001:ad0:: 15 2001:41d8:1:8028::54 14 2a00:1b50::2:2 14 192.149.202.9 13 200.74.222.140 12 98.130.2.250 12 2a00:1eb8:0:1::1 12 2600:c00:0:1::301 12 2001:c28:1:1:dad3:85ff:fee0:3f20 12 2001:380:124::4 12 2001:218:4c0:1:2e0:81ff:fe55:a018 12 2001:12d0::3 12 195.228.156.150 12 194.42.134.132 11 66.111.66.240 11 2607:f010:3fe:100:0:ff:fe00:1 11 211.25.195.236 11 210.162.229.210 11 2001:c28:1:1:dad3:85ff:fee0:be80 11 2001:a10:1:ffff::2:c918

8 8