- NANOG - lists.nanog.org

Re: hearing word of a fiber cut in virgina
by shields＠crosslink.net 17 Sep '98

17 Sep '98

In article <Pine.BSF.3.96.980917005255.2077E-100000@localhost>, SuperTaz <supertaz(a)mindspring.net> wrote: > I believe it was Bolling Green ;P~ No. > -Taz > > On Wed, 16 Sep 1998 steve(a)altrina.exodus.net wrote: > > > Hello, > > > > Seems to be a MFS fiber cut in Bowling Green, Virgina. This is all > > the information I have at this time. > > > > -- > > Steven O. Noble -- Sr. Backbone Engineer, Exodus Communications (EXDS) > > -- Work:408.346.2333 -- > > All my love to the Canadian Mooing Frog. > > > > -- Shields, CrossLink.

2 1

hearing word of a fiber cut in virgina
by steve＠altrina.exodus.net 17 Sep '98

17 Sep '98

Hello, Seems to be a MFS fiber cut in Bowling Green, Virgina. This is all the information I have at this time. -- Steven O. Noble -- Sr. Backbone Engineer, Exodus Communications (EXDS) -- Work:408.346.2333 -- All my love to the Canadian Mooing Frog.

2 1

RE: hearing word of a fiber cut in virgina
by Martin, Christian 17 Sep '98

17 Sep '98

Maybe with a gopher driving it... -----Original Message----- From: scott w [mailto:scott@digisle.net] Sent: Wednesday, September 16, 1998 11:55 PM To: Edward S. Marshall Cc: Craig Partridge; nanog(a)merit.edu Subject: Re: hearing word of a fiber cut in virgina I'll buy a few of them too... :) On Wed, 16 Sep 1998, Edward S. Marshall wrote: > On Wed, 16 Sep 1998, Craig Partridge wrote: > > More broadly, I had this idea for a NANOG T-shirt. Under the slogan, > > "Don't Get Mad, Get Even" -- the image of a backhoe lined up in the crosshairs > > of a weapon... > > Heh. Sign me up...I'll take a few. ;-) > > -- > -------------------. emarshal at logic.net .--------------------------------- > Edward S. Marshall `-----------------------' http://www.logic.net/~emarshal/ >

1 0

RE: quick question?
by Richard Parker 17 Sep '98

17 Sep '98

Kyle D. Smith wrote: > I have a customer who has a block of 62 ip addresses > (206.206.162.130 -> 206.206.162.190 and one for network/brodcast). > They are current expanding their network, and need around 30 more ip > addresses. I went ahead and allocated them the following IP address > pool (207.66.81.144 -> 207.66.81.174 with network/brodcast address.) > I attempted to use the new address on a Apple Macintosh (PowerMac > 6500/75) and it erturned an error message saying that the router was > not on the subnet, and that it could not use the new address. What kind of router is your customer using? Cisco routers allow you to define "secondary" IP addresses in addition to the primary IP address for an interface. You could use this feature to configure your router to have two logical subnets sharing your single physical subnet. Then on the Mac you can configure the Open Transport TCP/IP control panel to use either the primary or secondary router IP address for the "router address" field - depending on whether the Mac's IP address is in the subnet of the primary or secondary router IP address. -Richard

1 0

COM zone and serials
by Paul Thornton 17 Sep '98

17 Sep '98

Need I say more? More than half of them are running at least a day old, and the majority of those are running two days old. kate$ dig @a.root-servers.net SOA com. | grep serial 1998091500 ; serial kate$ dig @b.root-servers.net SOA com. | grep serial 1998091500 ; serial kate$ dig @c.root-servers.net SOA com. | grep serial 1998091300 ; serial kate$ dig @d.root-servers.net SOA com. | grep serial 1998091400 ; serial kate$ dig @e.root-servers.net SOA com. | grep serial 1998091300 ; serial kate$ dig @f.root-servers.net SOA com. | grep serial 1998091300 ; serial kate$ dig @g.root-servers.net SOA com. | grep serial 1998091300 ; serial kate$ dig @h.root-servers.net SOA com. | grep serial 1998091500 ; serial kate$ dig @i.root-servers.net SOA com. | grep serial 1998091300 ; serial kate$ dig @j.gtld-servers.net SOA com. | grep serial 1998091500 ; serial kate$ dig @k.gtld-servers.net SOA com. | grep serial 1998091300 ; serial Paul -- Paul Thornton Office Tel: +44 1733 705000 London Internet Exchange www.linx.net Mobile: +44 467 372205

5 5

Re: rwhois
by Ron Muir 17 Sep '98

17 Sep '98

I have asked that a discussion of rwhois and ARIN's current and future support of rwhois be discussed at the next ARIN members meeting on October 16, 1998. This item has been added to the agenda for that meeting. I will be glad to present any questions/points/items about the future of rwhois, please email me privately with this information. Thanks, Ron |||||||||||||||||||||||||||||||||||||||||||||||||||\ Ron Muir IP Administration BellSouth.net .net 770-522-6363 ron.muir(a)bellsouth.net - ---------- > From: Leo Bicknell <bicknell(a)dimension.net> > To: nanog(a)merit.edu > Subject: rwhois > Date: Wednesday, September 16, 1998 8:16 PM > > > I know quite a few of you were interested in my rwhois > script, and I have exchanged a lot of e-mail with some of you > individually. I think it's time I gave a bit of a summary. > > First off, it's definately the right idea. Properly > executed this could provide a seamless, distributed method for > looking up whois data from all the registries. If we could get > past the problems below it would be a dream for network operators. > > Of course, there are problems. I'll enumerate these > in the order of importance in my mind, others may disagree. > > 1) Data is missing/inaccurate. root.rwhois.net only reliably > provides Internic data, and that data is older than whois > data. ARIN does not yet participate in rwhois, and as I > understand it RIPE and APNIC have not yet tied in. There > is no .US data in rwhois either. > > Without the right data in here it's useless, regarless of > all other problems. > > 2) The server is not completely developed. There are features > in the server that are not fully implemented. Nuff said. > > 3) There is no distributed scheme set up. The Internic runs > one "root" rwhois server. This is no better than whois. > There should be 5-10 distributed across the network to > provide redundancy. > > 4) The rwhois protocol needs a caching server. It should be > possible for any ISP to set up a caching/mirroring rwhois > server with a relatively few steps so they can have their > own local server to query. This allows scripts to pound > on the data without affecting people outside of that ISP. > > So, the net result is I don't see how an ISP could > use rwhois today. With one server at the same location as > the whois server it's no more "reliable", and the data is > definately behind. Plus they actually have tigher limits > (eg number of results returned) on the rwhois server than the > whois server. > > I really think some people should get behind rwhois > and push it forward, as it is a reasonable solution, and is > probably 90% of the way developed. If only it could be > deployed and supported. > > -- > Leo Bicknell - bicknell(a)dimension.net > Network Engineer (CCIE #3440) - Dimension Enterprises > 1-703-709-7500, fax, 1-703-709-7699

1 0

West Orange
by Sean Donelan 17 Sep '98

17 Sep '98

>http://www.state.nj.us/dep/srp/bust/ess.htm sez: > >Essex WEST ORANGE MCI TELECOMMUNICATIONS CORPORATION426 EAGLEROCK >AVE 94-08-01-1446 0205111 NFA-A BUSTC 12/6/9 DFB > >Sounds like a conspiracy to me. Is it any wonder the FBI is having fits over the EPA's plan to release toxic chemical site information? Underground fuel storage tanks often indicate "interesting" sites with large backup generators. Although the FBI's efforts are a bit late, anyone with a LEXIS account can do a property search and locate most 'owned' sites. Now that InternetMCI/C&W is a co-locate tenant, its actually harder to find their sites. Although for the near-term future it shouldn't be too hard to guess :-) Property easements for cable routes are on file too, but I don't know of a comprehensive commercial database for them yet. However, you can get a pretty good idea by picking up any atlas of railroad routes. On the other hand, now there is a single toll-free number you can call, and a helpful person will come out and mark their exact location at no charge. Both the EPA toxic information and the One-call cable marking are the result of laws passed by the US federal government. The law of unintended consequences takes on a whole new meaning. -- Sean Donelan, Data Research Associates, Inc, St. Louis, MO Affiliation given for identification not representation

1 0

Re: rwhois
by jprovo＠ma.ultranet.com 17 Sep '98

17 Sep '98

[snip] Leo, Have you been by http://www.rwhois.net/rwhois/ or the rwhois(a)rwhois.net mailing list? There exist a few different clients and servers. The current/draft spec is at http://www.rwhois.net/rwhois/rwhois1.5/rwhois-1.5.txt, if I recall correctly. Joe -- Joe Provo, Network Architect 508.229.8400 x3006 Commercial Internet Services Group Fax 508.229.2375 UltraNet Communications, Inc., an RCN Company <jprovo(a)ultra.net>

2 1

Error log of VIP board?
by Seon Kim 17 Sep '98

17 Sep '98

Hello forks! Does anyone know the meanning of below error log of Cisco VIP borad? I think this malfunction makes our border router to be restarted frequently. Any comment is greately appreciated. Thaks. Seon Kim/frogi(a)nuri.net --------------error log----------------- BR1>sh cont vip 1 logging

1 0

rwhois
by Leo Bicknell 17 Sep '98

17 Sep '98

I know quite a few of you were interested in my rwhois script, and I have exchanged a lot of e-mail with some of you individually. I think it's time I gave a bit of a summary. First off, it's definately the right idea. Properly executed this could provide a seamless, distributed method for looking up whois data from all the registries. If we could get past the problems below it would be a dream for network operators. Of course, there are problems. I'll enumerate these in the order of importance in my mind, others may disagree. 1) Data is missing/inaccurate. root.rwhois.net only reliably provides Internic data, and that data is older than whois data. ARIN does not yet participate in rwhois, and as I understand it RIPE and APNIC have not yet tied in. There is no .US data in rwhois either. Without the right data in here it's useless, regarless of all other problems. 2) The server is not completely developed. There are features in the server that are not fully implemented. Nuff said. 3) There is no distributed scheme set up. The Internic runs one "root" rwhois server. This is no better than whois. There should be 5-10 distributed across the network to provide redundancy. 4) The rwhois protocol needs a caching server. It should be possible for any ISP to set up a caching/mirroring rwhois server with a relatively few steps so they can have their own local server to query. This allows scripts to pound on the data without affecting people outside of that ISP. So, the net result is I don't see how an ISP could use rwhois today. With one server at the same location as the whois server it's no more "reliable", and the data is definately behind. Plus they actually have tigher limits (eg number of results returned) on the rwhois server than the whois server. I really think some people should get behind rwhois and push it forward, as it is a reasonable solution, and is probably 90% of the way developed. If only it could be deployed and supported. -- Leo Bicknell - bicknell(a)dimension.net Network Engineer (CCIE #3440) - Dimension Enterprises 1-703-709-7500, fax, 1-703-709-7699

2 1