- Test - lists.nanog.org

Re: NANOG Digest, Vol 60, Issue 113
by Brzozowski, John 31 Jan '13

31 Jan '13

----Original Message----- From: "nanog-request(a)nanog.org" <nanog-request(a)nanog.org> Reply-To: NANOG <nanog(a)nanog.org> Date: Wednesday, January 30, 2013 9:20 PM To: NANOG <nanog(a)nanog.org> Subject: NANOG Digest, Vol 60, Issue 113 >On Jan 30, 2013, at 7:52 PM, Mark Andrews <marka(a)isc.org> wrote: >The update you sent is lovely, except I can tell you that the one (also >an Arris, running DOCSIS 3.0) which was installed in late October in my >house in Washington simply does not run v6 with the pre-installed load. >Now, is there some firmware upgrade which could fix this? Maybe, but it >sure would be nice if the folks who answer the phone in support could >direct me to someone who has heard of this technology. So no, as I said >before, Comcast has *not* removed the v6 barrier here. I'd like it to >"just work", please. [jjmb] We are working on an image that will enable IPv6, it will not be long.

1 0

Re: NANOG Digest, Vol 60, Issue 113
by Brzozowski, John 31 Jan '13

31 Jan '13

This is news, it would be great if more details were available. Anyone? ========================================= John Jason Brzozowski Comcast Cable m) +1-609-377-6594 e) mailto:john_brzozowski@cable.comcast.com o) +1-484-962-0060 w) http://www.comcast6.net ========================================= -----Original Message----- From: "nanog-request(a)nanog.org" <nanog-request(a)nanog.org> Reply-To: NANOG <nanog(a)nanog.org> Date: Wednesday, January 30, 2013 9:20 PM To: NANOG <nanog(a)nanog.org> Subject: NANOG Digest, Vol 60, Issue 113 >Message: 1 >Date: Wed, 30 Jan 2013 22:16:40 -0500 (EST) >From: "Justin M. Streiner" <streiner(a)cluebyfour.org> >To: Cutler James R <james.cutler(a)consultant.com> >Cc: nanog(a)nanog.org >Subject: Re: "Programmers can't get IPv6 thus that is why they do not > have IPv6 in their applications".... >Message-ID: <Pine.LNX.4.64.1301302210440.4289(a)whammy.cluebyfour.org> >Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed > >On Wed, 30 Jan 2013, David Barak wrote: > >>Comcast removed the "no IPv6" excuse? That removal somehow skipped my >>house in Washington DC where they installed (last October) a router >>which does not even support it (an Arrus voice gateway- the one where >>you can't turn of the crummy 2.4g wireless radio) and none of the >>folks I've spoken to on the phone can tell me when or if it will be >>coming. > >I know Verizon is rolling out v6 in some areas of their FiOS footprint. >The router they provided supports it, but what I got from their customer >service people was that they ran into some sort of issue with their TV >set-top boxes working properly with IPv6 or at least in a dual-stack >environment. At least that's where things stand in Pittsburgh. > >I don't think they've provided training to their customer service people >on IPv6 yet. The rep I spoke with a few weeks ago told me I was the first >customer that has asked her about it. > >Looking forward to native v6 / dual-stack here... > >jms >

1 0

Re: NANOG Digest, Vol 60, Issue 111
by Brzozowski, John 31 Jan '13

31 Jan '13

There is a lot more to come this year, so stay tuned. ;) John -----Original Message----- From: "nanog-request(a)nanog.org" <nanog-request(a)nanog.org> Reply-To: NANOG <nanog(a)nanog.org> Date: Wednesday, January 30, 2013 7:01 PM To: NANOG <nanog(a)nanog.org> Subject: NANOG Digest, Vol 60, Issue 111 >Message: 1 >Date: Thu, 31 Jan 2013 11:52:39 +1100 >From: Mark Andrews <marka(a)isc.org> >To: David Barak <thegameiam(a)yahoo.com> >Cc: nanog(a)nanog.org >Subject: Re: "Programmers can't get IPv6 thus that is why they do not > have IPv6 in their applications".... >Message-ID: <20130131005239.C2DE52E9423D(a)drugs.dv.isc.org> > > >In message <1359591223.5270.YahooMailMobile(a)web31809.mail.mud.yahoo.com>, >David >Barak writes: >>Comcast removed the "no IPv6" excuse? That removal somehow skipped my >>house >>in Washington DC where they installed (last October) a router which does >>not >>even support it (an Arrus voice gateway- the one where you can't >>turn of >>the crummy 2.4g wireless radio) and none of the folks I've spoken to >>on t >>he phone can tell me when or if it will be coming. >>I look forward to Comcast giving me native v6 at home. >>David Barak > >Firstly fix your mail client. What's this "'" garbage in text/plain? > >Deployment Update > >Published on Tuesday, October 23, 2012 > >IPv6 has been launched on all Arris DOCSIS 3.0 C4 CMTSes, covering >over 50% our network. We are targeting completion of the rest of >the network by mid-2013. Our progress has led to nearly 2.5% of our >Xfinity Internet customers actively using native dual stack. >Additionally, IPv6 traffic has increased 375% since World IPv6 Day >in June 2011. Following World IPv6 Launch in June 2012 Comcast >also observed that approximately 6% of the 2012 Olympics served >over YouTube to Comcast customers was over IPv6. > >http://www.comcast6.net >-- >Mark Andrews, ISC >1 Seymour St., Dundas Valley, NSW 2117, Australia >PHONE: +61 2 9871 4742 INTERNET: marka(a)isc.org > > >

1 0

Re: NANOG Digest, Vol 60, Issue 110
by Brzozowski, John 31 Jan '13

31 Jan '13

-----Original Message----- From: "nanog-request(a)nanog.org" <nanog-request(a)nanog.org> Reply-To: NANOG <nanog(a)nanog.org> Date: Wednesday, January 30, 2013 5:13 PM To: NANOG <nanog(a)nanog.org> Subject: NANOG Digest, Vol 60, Issue 110 >Message: 9 >Date: Wed, 30 Jan 2013 16:13:43 -0800 (PST) >From: David Barak <thegameiam(a)yahoo.com> >To: Cutler James R <james.cutler(a)consultant.com>, nanog(a)nanog.org >Subject: Re: "Programmers can't get IPv6 thus that is why they do not > have IPv6 in their applications".... >Message-ID: > <1359591223.5270.YahooMailMobile(a)web31809.mail.mud.yahoo.com> >Content-Type: text/plain; charset=us-ascii > >Comcast removed the "no IPv6" excuse? That removal somehow skipped my >house in Washington DC where they installed (last October) a router which >does not even support it (an Arrus voice gateway- the one where you >can't turn of the crummy 2.4g wireless radio) and none of the folks >I've spoken to on the phone can tell me when or if it will be coming. [jjmb] feel free to contact me offline, your device will soon be enabled with IPv6 support. I can add you to early trials for the same if you are interested. > >I look forward to Comcast giving me native v6 at home. [jjmb] IPv6 is launched in your area across our broadband network, we did not enable IPv6 for the device you have for a variety of reasons. See my other email about managing customer experience, the last thing I imagine you would want me to do is carelessly deploy software with issues. > >David Barak

1 0

Re: NANOG Digest, Vol 60, Issue 110
by Brzozowski, John 31 Jan '13

31 Jan '13

-----Original Message----- From: "nanog-request(a)nanog.org" <nanog-request(a)nanog.org> Reply-To: NANOG <nanog(a)nanog.org> Date: Wednesday, January 30, 2013 5:13 PM To: NANOG <nanog(a)nanog.org> Subject: NANOG Digest, Vol 60, Issue 110 >Message: 7 >Date: Thu, 31 Jan 2013 10:00:22 +1100 >From: Mark Andrews <marka(a)isc.org> >To: Michael Thomas <mike(a)mtcc.com> >Cc: NANOG list <nanog(a)nanog.org> >Subject: Re: "Programmers can't get IPv6 thus that is why they do not > have IPv6 in their applications".... >Message-ID: <20130130230022.E74BD2E9390C(a)drugs.dv.isc.org> > > >In message <51099C0F.5040507(a)mtcc.com>, Michael Thomas writes: >>On 01/30/2013 01:51 PM, Cutler James R wrote: >>> On Jan 30, 2013, at 12:43 PM, joel jaeggli <joelja(a)bogus.com> wrote: >>> >>>> As a product of having a motorola sb6121 and a netgear wndr3700 both >>>>of wh >>ich I bought at frys I have ipv6 in my house with dhcp pd curtesy of >>commcast >>. If it was any simpler somebody else would have had to install it. >>>> >>> Except that Apple Airport Extreme users must have one of the newer >>>hardware >> versions, that is my experience as well. >>> >>> And, even before Comcast and new AEBS, Hurricane Electric removed all >>>other >> excuses for claiming "no IPv6". >>"Remove excuses" != "Create incentive". There are an infinite number of >>things I can do to "remove excuses". Unless they're in my face (read: >>causing >>me headaches), they do not "create incentive". My using my or my >>company's >>software which doesn't work in my own environment (= work, home, phone, >>etc) >>"creates incentive". Lecturing me about how I can get a HE tunnel and >>that if >>I don't i'm ugly and my mother dresses me funny, otoh, just "creates >>vexation >>". >>Mike >> > >Just having IPv6 doesn't create incentives to make their code work >with IPv6. People just trundle along using IPv4. Turning off IPv4 >creates incentives. Reducing IPv4's capabilities creates incentives. >Being told this needs to work and be tested with IPv6 creates >incentives. [jjmb] turning off IPv4 is not realistic at this time and there are other ways to encourage the use and adoption of IPv6. Enabling by default, requesting upgrades for existing products that introduce support for IPv6. Enabling IPv6 alone is a significant statement especially when your business relies on the same. The absence of IPv6 or broken IPv6 when your business relies on it are no longer options. > >Broken networks get people to fix things. Unfortunately most >developers don't test with broken networks. If they did "Happy >Eyeballs" would not have happened. The applications would have >coped with only some address of a multi-homed server working. > >Mark >-- >Mark Andrews, ISC >1 Seymour St., Dundas Valley, NSW 2117, Australia >PHONE: +61 2 9871 4742 INTERNET: marka(a)isc.org > >

1 0

Re: NANOG Digest, Vol 60, Issue 107
by Brzozowski, John 31 Jan '13

31 Jan '13

See below. John -----Original Message----- From: "nanog-request(a)nanog.org" <nanog-request(a)nanog.org> Reply-To: NANOG <nanog(a)nanog.org> Date: Wednesday, January 30, 2013 11:18 AM To: NANOG <nanog(a)nanog.org> Subject: NANOG Digest, Vol 60, Issue 107 >Date: Wed, 30 Jan 2013 09:43:10 -0800 >From: joel jaeggli <joelja(a)bogus.com> >To: "Dobbins, Roland" <rdobbins(a)arbor.net>, NANOG list > <nanog(a)nanog.org> >Subject: Re: "Programmers can't get IPv6 thus that is why they do not > have IPv6 in their applications".... >Message-ID: <51095BAE.2020708(a)bogus.com> >Content-Type: text/plain; charset=ISO-8859-1; format=flowed > >On 11/28/12 4:17 PM, Dobbins, Roland wrote: >>On Nov 29, 2012, at 3:04 AM, Tony Hain wrote: >> >>>Getting the cpe vendors to ship in quantity requires the ISP >>>engineering organizations to say in unison "we are deploying IPv6 and >>>will only recommend products that pass testing". >>Do you see any evidence of that occurring? I don't. [jjmb] I do, where I have control and/or influence over products we absolutely require this or the device (or software) does not get deployed or enabled. There are cases where we deploy software that supports IPv6 but it is disabled. This is largely to ensure that my customers are not adversely impacted or have a poor customer experience. I admit getting quality implementations is not a trivial exercise even where good specifications are available. I view this as part of my job as such we are looking at techniques to streamline this process. >> >>Also, a lot of broadband consumers and enterprise organizations buy and >>deploy their own CPE. Do you see a lot of IPv6 activity there? >As a product of having a motorola sb6121 and a netgear wndr3700 both of >which I bought at frys I have ipv6 in my house with dhcp pd curtesy of >commcast. If it was any simpler somebody else would have had to install >it. [jjmb] this is our goal simple and seamless. >> I don't, excepting an IPv6 RFP checkbox for enterprises, which >>doesn't have any formal requirements and is essentially meaningless >>because of that fact. [jjmb] an IPv6 check box on an RFP means almost nothing, IPv6 has never been a one check box item. The rubber meets the road when a company chooses to buy based on IPv6 functionality or better yet swaps products out due to lack of IPv6 functionality. >>>You claim to be looking for the economic incentive, but are looking >>>with such a short time horizon that all you see are the 'waste' >>>products vendors >>>are pushing to make a quick sale, knowing that you will eventually come >>>back for yet-another-hack to delay transition, and prop up your >>>expertise in a >>>legacy technology. >>No. >> >>What I am looking for is an economic incentive which will justify the >>[IMHO] wildly overoptimisitic claims which some are making in re >>ubiquitous end-to-end native IPv6 deployment. >> >>Otherwise, I believe it will be a much more gradual adoption curve, as >>you indicate. [jjmb] ubiquitous IPv6 deployment and use requires work, it is not going to happen automatically and will require effort. >> >>>The same thing happened with the SNA faithful 15 years ago, and history >>>shows what happened there. >>You attribute circumstances and motivations to me which do not apply. >> >>----------------------------------------------------------------------- >>Roland Dobbins <rdobbins(a)arbor.net> // <http://www.arbornetworks.com> >> >> Luck is the residue of opportunity and design. >> >> -- John Milton >> >> >> >

1 0

TOR fiber patch panels
by Chuck Anderson 31 Jan '13

31 Jan '13

I'm looking for better Top-Of-Rack fiber patch panels than the ones I've been using up to this point. I'm looking for something that is 1U, holds 12 to 24 strands of SC, ST, or LC, has fiber jumper management rings, and has a door that doesn't interfere with the U below (a server might be mounted immediately below the fiber patch panel). I prefer one that doesn't have a sliding mechanism, because I've had issues with fiber installers not installing those properly, causing fiber to be crunched and broken when the tray is slid out/in during patching. Of course, I would still like one that is easy to get your fingers into to install and remove fiber jumpers. Does such a thing exist? What are people's favorite fiber patch panels? Thanks.

4 3

OOB core router connectivity wish list
by Mikael Abrahamsson 31 Jan '13

31 Jan '13

I have together with some other people, collected a wish list for OOB support, mainly aimed for core routers. This is to replace the legacy serial port usually present on core routing equipment and to move/collapse all its functionality to an ethernet only port. Some equipment already have an mgmt ethernet port, but usually this can't do "everything", meaning today one has to have OOB ethernet *and* OOB serial which just brings more pain than before. I would like to post it here to solicit feedback on it. Feel free to use it to tell your vendor account teams you want this if you feel it useful. I've already sent it to one vendor. http://swm.pp.se/oob.txt Priorities: [P1] -> must have, otherwise not useful [P2] -> would be very useful, to most operators [P3] -> nice to have, useful to some >From the OOB ethernet port it should be possible to: [P1]: Powercycle the RP, switchfabrics and linecards (hard, as in they might be totally dead and I want to cut power to it via the back plane. Also useful for FPGA upgrades). [P1]: Connect to manage the RP(s) and linecards (equivalent of todays "connect" on GSR and ASR9k or connecting to RP serial port). [P2]: It should be possible to connect to the OOB from the RP as well (to diagnose OOB connectivity problems). [P2]: Upload software to the RP or otherwise make information available to the RP (for later re-install/turboboot for example). RP should have access to local storage on the OOB device to transfer configuration or software from the OOB device to the RP). [P2]: Read logs and other state of the components in the chassis (displays and LEDs) plus what kind of card is in each slot. [P1]: The OOB port should support (configurable), telnet, ssh and optionally [P3] https login (with a java applet or equivalent to give CLI access in the browser) with ACLs to limit wherefrom things can be done. OOB should support ssh key based logins to admin account. [P1]: The IP address of the OOB port should be set via DHCP/DHCPv6/SLAAC and should have both IPv4 and IPv6 support. If not both, then IPv6 only. [P1]: It should be possible to transfer data using tftp, ftp and scp (ftp client on the OOB device, scp being used to transfer data *to* the device (OOB being scp server). [P2]: OOB device should have tacacs and radius and [P1] local user/password database support for authentication. [P3] OOB should support ssh-key based authentication. [P3] Chassis should have a character display or LEDs with configurable blink pattern from OOB, to aid remote hands identification. [P3] OOB should have two USB ports, one to use to insert storage to transfer files to/from device. The other should be USB port that presents itself as ether USB serial port, or USB ethernet port, where the OOB device would have built in DHCP/DHCPv6 server to give IPv4v6 access to a laptop connected to the OOB so the onsite engineer can then use ssh/telnet to administrate the OOB. Optionally this port could be ethernet port (compare todays CON and AUX ports). [P2] OOB should have procedure to factory default its configuration, perhaps physical button that can be pressed and held for duration of time. The fact that this is done should be logged to the RP. [P3] OOB should have possibility to show power supply and environmental state. [P3] The factory default configuration should not include an empty or obvious login password. The factory-default login password should be the MAC address (without punctuation) of the OOB ethernet interface, which should be printed on the chassis next to the OOBE port. -- Mikael Abrahamsson email: swmike(a)swm.pp.se

29 85

box against dos/ddos
by Piotr 31 Jan '13

31 Jan '13

Hi, I looking some box (vendor, model), which i can put out of the main/product network, which can analyze packets netflow,sflow,syslog from bgp router(s) and after discover some anomaly it can do some action, for example: - Box have bgp session with bgp router and advertise attacked ip prefix with some community. Bgp router set next-hop for this prefix to /dev/null Normal traffic via bgp router is about 1G/s in and 10G/s out What is worth of looking and what you suggest ? thanks for help, Piotr

7 7

HSRP vs VRRP for IPv6 on IOS-XE - rekindling an old flame
by -Hammer- 31 Jan '13

31 Jan '13

A while back I brought up a discussion about IPv6 and I mentioned having some HSRP issues. Not end of the world, just adjusting to IPv6. Several folks went offline to tell me that I should dump "legacy" HSRP and go to VRRP. While I never did find anyone who could explain how HSRP is a sunset feature in IOS, I did agree with a few folks to look into VRRP for IPv6. Well I'm just now getting around to it and there is literally nothing out there. I found a few older articles implying that it's not there yet and of course I found the usual docs about RAs and SLAC and whatnot. But nothing recent. So, for those who criticized me previously about using HSRP (or anyone else) instead of VRRP, do you have VRRP up and running on Cisco IOS-XE and if so how? Can anyone provide a link or a document explaining how this is accomplished? Sample configs? Usually if you can't find it on Google or CCO it's not promising. I'm also reaching out to our AS team for guidance on the subject. PS: I'm not taunting here. It's just that several folks made the effort to go offline with me and tell me how wrong I was with HSRP and that I need to progress to VRRP and I can't find a single doc on the subject now that I look. Were these folks mistaken or am I missing something? Any help would be appreciated. -- -Hammer- "I was a normal American nerd" -Jack Herer

6 12