- Test - lists.nanog.org

... with a hint of citrus ...
by bmanning＠vacation.karoshi.com 12 Aug '05

12 Aug '05

ok... now for the(*) subjective question of the day. (private replies requested) for those ASNs who touch one or more exchange points which are IN THE US, please rank order your five favorite IX's - with a brief one-liner as to why you like the particular IX. I'd like to compare notes :) (*) as if --bill

2 2

RE: Way OT: RE: @Home's 119 domain names up for sale
by Frank Coluccio 11 Aug '05

11 Aug '05

Responding to all previous messages in this and the original thread: I note that "Way OT" was added to my original subject heading, and indeed for good cause because this discussion has veered off the course it could have taken in some ways, and that's okay, too. My associating the name "access@home" and the news release about former cable ISP @Home's sale of its domain names was more a matter of curiosity than it was actually suggesting there was a connection between the two. Although, the timing of both leaves me wondering, still, because up to this past week I had not seen the name @home, or even @work for that matter, used in almost five or six years, anywhere outside the context of discussions that were historical in nature. IMO, there's more to be considered here than whether this is just another example of pork distribution, which I suspect it is, in the accepted vernacular. Meaning, the spending of funds that result from marathon congressional horse trading and voting in order to get rid of funds that have been allocated for certain (in some cases, new) causes, lest those funds be lost forever in the spirit of "use it or lost it," both now and forever more. Sometimes the ends to these rituals actually turn out to be noble, and sometimes they can be seen as a cause for outrage. In the case at hand I'm neither showering Rubin and Clinton with praise nor condemning their motivations in any way. Rather, I have serious questions as to what they are doing and how they have set out to accomplish their goals, and probably just as importantly, the fact that have they labeled their initiative as one that would bridge the digital divide. I see two issues I may want to pursue further --elsewhere of course, since this is indeed "Way OT" for this venue-- because they may prove detrimental to the cause of end-to-end networking, even if a relatively few more broadband lines do get built in the process. If you have been following the tightening noose around anything that smacks of being open lately, and view the timing of this action against the backdrop of recent FCC rulings, which are causing some ISPs to seriously begin wondering about their very survival and where they will get their next HSI lines from to provide to their customers, you must then conclude that the secondary beneficiaries of the initiative will at some point be incumbent service providers. For, who else will be left to provide fiber and cable services by the time these homes are built and ready to be inhabited, save for the small number of muninets that have already been built, and maybe to a similar degree, those of WISPs? When such an initiative is announced proclaiming that $1 Billion dollars will be spent on "bridging the digital divide," when in fact it is federal housing and urban development projects that happen to include the installation of residential inside wiring and an undisclosed plan for how "broadband" service providers would be paid, (without also mentioning that it will ensure that structural foundations, carpentry, plastering, plumbing, lighting and electrical work will also be covered), it gives cause to detractors of municipal networking to shoot down further, legitimate proposals that are relatively "undiluted" in comparative terms, efforts to promote Internet access. In effect, it gives the nay sayers of muninets something to point to when proclaiming "enough is enough", and that sufficient public funds have already been spent on such programs. As a consultant who at times receives feelers and RFIs from landlords of housing complexes, community leaders and apartment owners' boards of directors who are applying for local, state and federal development funding to upgrade their properties (which are sometimes nothing more than slums that they picked up for a song), I can state unequivocally that one of the first bullet points to appear in their executive summaries in order to receive meritorious recognition from those who hold the purse strings is the fact that their newly re-done units will be "Internet ready." Internet read is a euphemism that means that those units will be fully wired with Cat6 and coaxial cabling. It's gotten competitive to the point where some take it a step farther and enter into agreements with the incumbent telco and cable operators, or they go to both the telco and the National Cable Television Cooperative (NCTC) and create their own private cable companies (PCOs) to ensure that residents who desire triple play services can have it delivered to them at the stroke of a couple of keys and a credit check. Which leads me to my last point of skepticism in this post. Where and what percentage of the funds being allocated under this access@home initiative is the money going? I'd be surprised if the in-home wiring went above 1% of the total Billion cited. How much of it will be spent on recurring rental fees for broadband lines? Computer hardware and terminal gear? Will said funding lead to another round of abuses, such as the E-Rate abuses we've seen in the past? Will residents be given broadband access even if they don't have ample terminal gear to utilize it? Perhaps, even if they don't want or need it? After all, Luddites have rights, too. Comments here or via mail welcome. frank(a)fttx.org

1 0

Real-time WHOIS for .COM
by Florian Weimer 11 Aug '05

11 Aug '05

Is there some kind of real-time WHOIS for .COM (and friends) which allows you to determine at least the corresponding registrar? This is helpful if you have to pull a delegation in order to mitigate a particular threat. Going by the name servers listed in DNS isn't particularly helpful if it points to end-user dial-up space. 8-(

7 11

RE: Cisco crapaganda
by Hannigan, Martin 11 Aug '05

11 Aug '05

[ SNIP ] > But I found more. It seems that a guy using the name FX > has been publishing stuff about Cisco heap exploits for > years now. I found his slides from a presentation made > at BlackHat Las Vegas in 2002. Lots of juicy detail. And I > found a long document translated from Chinese about modern > information/economic warfare. If people want to be up to date, imagine the unimaginable. -M<

1 0

Fwd: Cisco crapaganda
by James Baldwin 11 Aug '05

11 Aug '05

On Aug 9, 2005, at 11:11 AM, Michael.Dillon(a)btradianz.com wrote: > They are not "Lynn's exploit techniques". The techniques were > published by someone else in considerable more detail than > Lynn along with source code. > What techniques are you referencing? The technique Lynn demonstrated has not been seen anywhere in the wild, as far as I know. He, nor ISS, ever made the source code available to anyone outside of Cisco, or ISS. What publication are you referring to? > You aren't safe just because your network runs on brand X > boxes. The only way to be safe is for your brand X vendors > to take software security and systemic security much more > seriously. I also believe that there are lessons to be > learned from the open source community's approach to security. > This doesn't mean that Cisco or any other Brand X vendor > should just run out and replace their box's OS with > OpenBSD or NetBSD or Linux. But they need to seriously > ask themselves what advantage they gain from inventing > their own wheel and rejecting the work of thousands of > highly skilled and dedicated people. > Quality control. The general operating systems are not designed with a specific goal of high availability routing in mind, and while they display and can compete on some levels with specialized operating systems, they will loose out in the end. In this regard it is not open source environments that present the benefit, but as you say "thousands of highly skilled and dedicated people". There are very few of those people who are experienced in the realm of high end routing systems. The general operating system can garner a large support base due to its broad market appeal, its use in both servers, low end routing hardware, and desktops. However, to develop strong support for a reduced feature set and circumscribed is difficult. The same number of dedicated developers will be reduced and the amount of time highly specialized developers will focus on that code base will be diminished. You can see examples of similar behavior in the subsets of Linux developed for embedded systems, like the WAP Linksys routers. That being said, who would continue to buy Cisco equipment if IOS was available elsewhere? The Chinese market is already flooded with Cisco knock-offs, the rest would most certainly follow if it was legal. Out of curiosity, what, in your opinion, is the open source community's approach to security? I have seen differing approaches from different groups, some which are downright despicable (methods, not people). > There really is no such thing as closed source. The people > building these exploits are fully capable of taking > code from ROM or flash memory and reading what it does. > I've had some experience with reverse engineering and disassembly, and while it is true that you can analyze an image of a running program and find what it does that is a long, long step to having the kind of understanding of a program you can gain through the actual source code. > It's all fine and well to have layers of security but > hiding your source code really shouldn't be counted > as a security layer. > Obscurity should never be counted on as a sole security layer, but it does add a level of difficulty. One of the major themes in the security industry is mitigation. Obscurity does not add a level of security, but it does reduce the number of people who can easily accomplish a task. It raises the bar and reduces the pool of attackers. > Even if someone managed to eliminate Lynn and all past > and current employees of ISS by exiling them to Cuba, > this would not stop the hackers who are exploiting > network device flaws. > Did anyone ever think that?

6 10

Re: UUNET connectivity in Minneapolis, MN
by Christopher L. Morrow 11 Aug '05

11 Aug '05

On Thu, 11 Aug 2005 interex(a)inetica.com wrote: > we had a loss of comercial power(coned) in the downers grove terminal. > terminal is up on generator power now. > that seems to map to the internal firedrill as well, anyone else hit by this event?

1 0

UUNET connectivity in Minneapolis, MN
by Erik Amundson 11 Aug '05

11 Aug '05

Anyone else having issues with UUNET connectivity in MSP? We were seeing slowness, now we see no traffic flow at all...we make it one hop, then nothin'. Erik Amundson A+, N+, CCNA, CCNP IT and Network Manager Open Access Technology Int'l, Inc. mailto:erik.amundson@oati.net CONFIDENTIAL INFORMATION: This email and any attachment(s) contain confidential and/or proprietary information of Open Access Technology International, Inc. Do not copy or distribute without the prior written consent of OATI. If you are not a named recipient to the message, please notify the sender immediately and do not retain the message in any form, printed or electronic.

5 4

Looking Glass failure in DC
by David Lesher 11 Aug '05

11 Aug '05

Hi: Atlantech.net reports that their ongoing DC region outage is a Looking Glass issue; and LG has troops on the way. I don't know if it is limited to Atlantech only, or other providers are also afflicted. -- A host is a host from coast to coast.................wb8foz(a)nrk.com & no one will talk to a host that's close........[v].(301) 56-LINUX Unless the host (that isn't close).........................pob 1433 is busy, hung or dead....................................20915-1433

1 0

IPv6 Address Planning
by Cody Lerum 11 Aug '05

11 Aug '05

Currently we are in the process of planning our IPv6 addressing schema for our network. We are a service provider with around 20 core routers, and several hundred enterprise customers. These customers currently connect back to our core via a separate VLANs or channelized DS1/DS3/OC-X type interfaces. Thus currently lots of /30 IPv4 blocks. Our address allocation is 2001:1940::/32 Here is our current plan, but we are looking for suggestions from people who have been down this road before. The plan is to break out a /48 for our organization. Then break out the first /64 for loopbacks, and the next /64 for point-to-point connections. The PTP /64 then breaks out further into 1 /80 for core links, and 1 /80 for each of our distribution sites. Within these /80's are individual /112's for PTP links. What this will allow us to do is aggregate each sites PTP connections into /80's within our IGP. Looks something like this. 2001:1940::/48 - TransAria 2001:1940::/64 - Loopbacks/NMS/ETC 2001:1940::1/128 - Router 1 2001:1940::2/128 - Router 2 2001:1940:0:1::/64 - PTP Links 2001:1940:1::/80 - Core Links (non-aggergratable) 2001:1940:0:1::/112 - Core Link 1 2001:1940:0:1::1 - Router A 2001:1940:0:1::2 - Router B 2001:1940:0:1::1:1/112 - Core Link 2 2001:1940:0:1::1:1 - Router A 2001:1940:0:1::1:2 - Router B 2001:1940:0:1:1::/80 - Distribution Site 1 2001:1940:0:1:1::/112 - Customer Link 1 2001:1940:0:1:1::1 - Dist Router 2001:1940:0:1:1::2 - Customer Equipment 2001:1940:0:1:1:0:1:0/112 - Customer Link 2 2001:1940:0:1:1:0:1:1 - Dist Router 2001:1940:0:1:1:0:1:2 - Customer Equipment 2001:1940:0:1:2::/80 - Distribution Site 2 2001:1940:0:1:2:::/112 - Customer Link 1 2001:1940:0:1:2::1 - Dist Router 2001:1940:0:1:2::2 - Customer Equipment 2001:1940:0:1:2:0:1:0/112 2001:1940:0:1:2:0:1:1 - Dist Router 2001:1940:0:1:2:0:1:1 - Customer Equipment 2001:1940:1::/48 - Customer 1 Assignment 2001:1940:2::/48 - Customer 2 Assignment 2001:1940:3::/48 - Customer 3 Assignment Thoughts? Thanks! Cody

15 33

Weird traffic from data393.net [AS29863]?
by Fergie (Paul Ferguson) 11 Aug '05

11 Aug '05

Sent e-mails, etc. Anyone else seen "BGP probe" traffic claiming to be from Savvis? - ferg -- "Fergie", a.k.a. Paul Ferguson Engineering Architecture for the Internet fergdawg(a)netzero.net or fergdawg(a)sbcglobal.net ferg's tech blog: http://fergdawg.blogspot.com/

1 0