- Test - lists.nanog.org

Vixie warns: DNS Changer ‘blackouts’ inevitable
by Henry Linneweh 24 May '12

24 May '12

http://www.theregister.co.uk/2012/05/17/dns_changer_blackouts/ -Henry

21 29

Qwest/CenturyLink implementing transparent proxies?
by Brielle Bruns 24 May '12

24 May '12

Hello All, A little off topic, but I was wondering if there's any Qwest/CenturyLink network engineers or techs lurking on this list that would contact me offlist? I won't bore people with the details, but I'm seeing what appears to be a transparent proxy on some sites when visited from multiple clients (all with Qwest DSL). When browsing on our non-Qwest circuits (such as the T1s), we do not see the same behaviors. Its concerning to say the least, and something I'd like to get a clear and straight answer about. Thanks! -- Brielle Bruns The Summit Open Source Development Group http://www.sosdg.org / http://www.ahbl.org

2 2

alcatel var/integrator
by Chris McDonald 24 May '12

24 May '12

does anyone have any experience with alcatel var's/integegrators they'd be willing to share? thanks chris

1 0

RIPE 65 Call for Presentations/Papers
by Todd Underwood 24 May '12

24 May '12

Fellow North American network-interested-and-involved folks: In September, RIPE will be back in Amsterdam and we're interested in presentations. Please see the appended Call for Presentations and let me/us know if you have an interesting idea for a presentation, panel, birds-of-a-feather sessions or a tutorial. thanks! Call for Presentations: RIPE 65 A RIPE Meeting is an open event where Internet Service Providers, network operators and other interested parties get together. Although the meeting is mostly technical, it is also a chance for people to meet and network with others in their field. RIPE 65 will take place on 24-28 September 2012 in Amsterdam, Netherlands. The RIPE Programme Committee (PC) is now seeking content proposals from the RIPE community for the Plenary, BoF and tutorial sessions at RIPE 65. The PC is looking for presentations covering topics of network engineering and operations, including but not limited to: - IPv6 deployment - Managing IPv4 scarcity in operations - Commercial transactions of IPv4 addresses - Data center technologies - Network and DNS operations - Internet governance and regulatory practices - Network and routing security - Content delivery - Internet peering and mobile data exchange Submissions Attendees of the RIPE meetings are quite sensitive to keeping presentations non-commercial, and product marketing talks are strongly discouraged. Repeated audience feedback shows that the most successful talks focus on operational experience, research results, or case studies. For example, presenters wishing to describe a commercial solution should focus on the underlying technology and not attempt a product demonstration. Presenters who are proposing a panel or BoF are encouraged to include speakers from several (perhaps even competing) companies and/or a neutral facilitator. In addition to presentations selected in advance for the Plenary, the RIPE PC also offers several time slots for “lightning talks” which are selected immediately before or during the conference. The following requirements apply: - Proposals for talks, BoFs and panels must be submitted for full consideration no later than 1 July 2012, using the meeting submission system at: https://meetings.ripe.net/pc/ Proposals submitted after this date will be considered on a space-available basis. - Presenters should indicate how much time they will require (30 minutes for talks is a common maximum duration, although some talks can be longer). - Proposals for talks will only be considered by the PC if they contain at least draft presentation slides (slides may be updated later on). For BoFs and panels proposals must contain a clear description as well as names of invited panelists/presenters. - Due to potential technical issues, it is expected that most if not all presenters/panelists will be physically present at the RIPE meeting. - Lightning talks should be submitted using the meeting submission system. They must be short (10 minutes maximum) and often involve more timely topics. They can be submitted at any time. The allocation of lightning talk slots will be announced one day prior to the relevant session. If you have any questions or requests concerning content submissions, please email pc [at] ripe [dot] net. ------ Todd Underwood for the RIPE Program(me) Committee toddunder(a)gmail.com

1 0

vixie, father of multitudes
by paul vixie 24 May '12

24 May '12

thanks to several folks who let me know this was going on. i hadn't even noticed that i wasn't getting nanog@. thanks to seclists.org for hosting an archive i could use. --- From: bmanning () vacation karoshi com Date: Wed, 23 May 2012 05:40:16 +0000 On Tue, May 22, 2012 at 10:07:52PM -0700, Michael J Wise wrote: On May 22, 2012, at 9:10 PM, bmanning () vacation karoshi com wrote: On Tue, May 22, 2012 at 08:52:52PM -0700, Michael J Wise wrote: On May 22, 2012, at 8:35 PM, Randy Bush wrote: father of bind? that's news. <http://boingboing.net/2012/03/29/paul-vixies-firsthand-accoun.html> He was there, and Put The Fix In, to down the network. Certainly news to Phil Almquist and the entire BIND development team at UCB. Paul was at DECWRL and cut his teeth on pre-existing code. While he (and ISC) have since revised, gutted, tossed all the orginal code, rebuilt it twice - and others have done similar for their DNS software, based on the BIND code base, implementation assumptions, and with little or no ISC code, and they call it BIND as well, it would be a HUGE leap of faith to call Paul Vixie the father of BIND - The Berkeley Internet Naming Daemon. Methinks we're talking at cross purposes. maybe... :) my comment was refering to the "father of bind" statement. i don't describe myself that way. i inherited bind at 4.8.3 and fixed stuff. i rewrote a lot of it for 4.9. we (mostly me but with huge work by robert halley and mark andrews) rewrote most of it for bind 8.1. (there was no 8.0.) other people (not me) wrote bind 9.x. other people (mostly not the same people) are writing bind 10. if my wikipedia entry is wrong in this regard i invite folks to fix it. last i heard it's disallowed for people to edit their own entries, so i have not tried. i am not the father of anything, except four healthy kids. i do sometimes call myself "the wierd uncle of the internet" but "father of bind" is not what i mean. As for being there and "Put The Fix In"... Makes for great PR but in actual fact, its a bandaid that is not going to stem the tide. An actual fix would really need to change the nature of the creaky 1980's implementation artifacts that this community loves so well. I don't think we're talking about the same thing at all. Paul was there to shut down the DNS changer system and replace it with something that restored functionality to the infected machines. And I gather Paul will be one of the people who will turn the lights out on it. yes, and yes. He didn't "shut down" DNS Changer, he put up an equivalent system to hijack DNS traffic and direct it to the "right" place... SO folks didn't see any problem and the DNS Changer infection grew and got worse. When he is legally required to take his "bandaide" out of service, then the problem will resolve by folks who will have to clean their systems. it's true, the fbi team who powered all that stuff off and loaded it into a u-haul truck are the ones who "shut down dns changer". or perhaps it was the police in estonia who arrested all those people. i'm not the shutter-downer. As for "turning the lights out" - that will only happen when the value of DNS hijacking drops. As it is now, ISC has placed DNS hijacking code into their mainstream code base... because DNS hijacking is so valuable to folks. In a modestly favorable light, ISC looks like an arms dealer (DNS redirection) to the bad guys -AND- (via DNSSEC) the good guys. Either way, they make money. well, no. but that seems off-topic. start a new thread if you care. (and, cc me!) And yes, I think I agree with you. Paul will be there to turn things off when they no longer make money for his company. well, no. when the court order runs out we will have to shut things down. but the money FBI is paying us for this is just to cover costs. and, it's not my company. isc is a 501(c)(3), basically a ward of the state of delaware, having no shares and therefore no shareholders. Your other comments are non-sequitur to the main issue. Perhaps I am not a member of the Paul Vixie cult of personality. so sad. When those servers are turned off, Customer Support folks at many ISPs will prolly want to take their accrued vacation. Amen. And there will be thousands more of them when the court order expires than existed when the Feds called him in. um. no. hundreds of thousands less than before the feds called ISC in. see dcwg.org. it's lovely to have so many fans. keep those cards and letters coming. (but, cc me!) paul

2 1

Any mail peeps from Rackspace?
by Mike Lyon 23 May '12

23 May '12

Howdy, Looking for a mail admin at Rackspace to help troubleshoot some issues. Please hit me up off-list. Thank You, Mike -- Mike Lyon 408-621-4826 mike.lyon(a)gmail.com http://www.linkedin.com/in/mlyon

1 0

Equinix Tyoko service provider
by Rodrick Brown 23 May '12

23 May '12

Can anyone recommended an Internet service provider with presence in Equinix-TKO. I'm looking to implement VPN access as means for backup access for a handful of collocated servers in this facility. I have a small branch office in Jersey City with about 10 users that would access this link for contingency purposes only. In terms of hardware I'm thinking an ASA5505 will fit the bill. Any pitfalls I should be aware of? Feel free to contact me off list. Thanks. Sent from my iPhone

1 0

Re: Current IPv6 state of US Mobile Phone Carriers
by Tina TSOU 23 May '12

23 May '12

For DHCPv6 client, there is no GUI. Tina On May 23, 2012, at 4:24 AM, "Alvaro Vives" <alvaro.vives(a)consulintel.es> wrote: > DHCPv6 client

1 0

SNMP/TCP probes from critical.io
by Raoul Bhatia [IPAX] 23 May '12

23 May '12

hi! during the last couple of days, i noticed probes from some hosts that present themselves as critical.io probe hosts, including but not limited to, the following IP addresses: * 184.154.42.194 / critical.io * 69.64.43.135 / research1.critical.io * 69.64.43.137 / research2.critical.io * 69.64.43.142 / research3.critical.io * 50.116.22.209 The systems present the following information via http: > This system is coordinating an internet-wide survey of open TCP > ports, service banners, SNMP system descriptions, and NetBIOS name > queries. The results of this survey will be used to uncover > systematic vulnerabilities in the equipment provided by ISPs to their > customers. Have you noticed these probes and what are your thoughts on them? Cheers, Raoul -- ____________________________________________________________________ DI (FH) Raoul Bhatia M.Sc. email. r.bhatia(a)ipax.at Technischer Leiter IPAX - Aloy Bhatia Hava OG web. http://www.ipax.at Barawitzkagasse 10/2/2/11 email. office(a)ipax.at 1190 Wien tel. +43 1 3670030 FN 277995t HG Wien fax. +43 1 3670030 15 ____________________________________________________________________

2 1

RE: Current IPv6 state of US Mobile Phone Carriers
by David Hubbard 23 May '12

23 May '12

I have the "4GLTE" LG VL600 usb modem from Verizon on a consumer data-only $50/month plan and it gives my Windows 7 laptop a v6 address on both 3G and "4G" connections. I noticed it recently when I was logged into the ARIN website since their site puts a banner across the top when you're accessing via ipv6; then I tried other sites to confirm it was working. David > -----Original Message----- > From: Randy Carpenter [mailto:rcarpen@network1.net] > Sent: Tuesday, May 22, 2012 10:07 PM > To: PC > Cc: nanog(a)nanog.org > Subject: Re: Current IPv6 state of US Mobile Phone Carriers > > > Not only does Verizon *not* have IPv6 on their LTE network, > they also do *not* have IPv4, except for double-NATed rfc1918 > crap that changes your IP address every couple minutes. The > only way to get a stable connection is to pay them $500 to > get a static public IP address. > > thanks, > -Randy > > > ----- Original Message ----- > > IPV6 is present, to my knowledge, on all devices on the Verizon IPV6 > > LTE network. I noticed its using it to communicate to Google for > > many > > of it's services when I ran a netstat. I believe they mandated > > support for it from any certified device. > > > > Unfortunately, it's still firewalled. > > > > > > On Tue, May 22, 2012 at 5:40 PM, Paul Graydon > > <paul(a)paulgraydon.co.uk> wrote: > > > On 05/22/2012 01:21 PM, Cameron Byrne wrote: > > >> > > >> On May 22, 2012 4:00 PM, "Paul Porter"<paul.porter(a)gree.co.jp> > > >> wrote: > > >>> > > >>> Hi NANOG, > > >>> > > >>> I'm looking for some information on the four largest US mobile > > >>> phone > > >>> carriers and the current state of their IPv6 infrastructure. > > >>> Specifically, > > >>> we are trying to figure out: > > >>> > > >>> 1. How much of the carrier core and edge for AT&T, Verizon. > > >>> T-Mobile, > > >>> and > > >>> Sprint are on IPv6 now? > > >> > > >> Hi, > > >> > > >> T-Mobile USA has native ipv6 to all subscribers in all of it's > > >> coverage > > >> area. But, less than 1% of subscribers use IPv6 because they do > > >> not have > > >> an > > >> IPv6 capable phone. The Nexus S and Galaxy Nexus work well. > > >> > > >> This device challenge will improve in time. Samsung is doing a > > >> good job > > >> of > > >> bringing IPv6 to Android devices. More info here > > > > > > That's interesting. I have a Galaxy Nexus on T-Mobile USA and it > > > doesn't > > > get an IPv6 address, only IPv4. Works fine with IPv6 over my > > > wireless > > > network at home. Doesn't seem to be anything obvious in the > > > settings to > > > enable or disable that. > > > > > > Paul > > > > > > > > > > > >

1 0