- Test - lists.nanog.org

Re: Concerning 192.x.x.x and routing
by Jeff Olenchek 08 Jan '96

08 Jan '96

There is no problem anymore. Please drop this. Thanks, jeff

1 0

Re: Concerning 192.x.x.x and routing
by Joe Provo 08 Jan '96

08 Jan '96

Just looks like a case of someone believing different DBs in whatever order they choose. Not sure why it would 'suddenly' manifest, but MCI is telling it loudly enough for sprint to believe it [appended] and for it to work. I don't know other 192.x.x.x hit [none were listed], but 192.108.186.0/24 (one of my customers) seems just peachy from BBN-land. Fireless smoke or a transient? Cheers, Joe Provo Network Operations Center UltraNet Communications, Inc. --- % whorad 192.135.135.0 route: 192.135.135.0/24 descr: Washington High School descr: 2525 N. Sherman Blvd descr: Milwaukee descr: WI 53210, USA origin: AS2381 comm-list: COMM_NSFNET advisory: AS690 1:3561(27) 2:3561(218) 3:3561(147) 4:3561(11) 5:3561(144) mnt-by: MAINT-AS2381 changed: nsfnet-admin(a)merit.edu 950411 source: RADB route: 192.0.0.0/2 descr: See aut-num for AS0 origin: AS0 advisory: AS690 1:0 mnt-by: ANS changed: selina(a)ans.net 951003 source: ANS route: 192.135.135.0/24 descr: WHS-DOM descr: Washington High School descr: 2525 N. Sherman Blvd descr: Milwaukee, WI 53210 descr: USA origin: AS2381 advisory: AS690 1:3561 mnt-by: CICNET-NS changed: tko(a)cic.net 950410 source: MCI --- %trac 192.135.135.1 traceroute to 192.135.135.1 (192.135.135.1), 30 hops max, 40 byte packets 1 core-7.ultra.net (199.232.56.27) 5 ms 3 ms 4 ms 2 sl-pen-5-S3/0-T1.sprintlink.net (144.228.65.73) 62 ms 44 ms 37 ms 3 sl-pen-2-F0/0.sprintlink.net (144.228.60.2) 76 ms 77 ms 157 ms 4 sprintnap.mci.net (192.157.69.11) 58 ms 54 ms 60 ms 5 border2-hssi1-0.NewYork.mci.net (204.70.45.5) 61 ms 54 ms 95 ms 6 core-fddi-1.NewYork.mci.net (204.70.3.17) 56 ms 36 ms 56 ms 7 core1-hssi-2.WestOrange.mci.net (204.70.1.98) 74 ms 52 ms 67 ms 8 core1-hssi-3.NorthRoyalton.mci.net (204.70.1.101) 84 ms 115 ms 132 ms 9 core-hssi-2.Chicago.mci.net (204.70.1.93) 118 ms 80 ms 63 ms 10 border2-fddi-0.Chicago.mci.net (204.70.3.82) 66 ms 66 ms 78 ms 11 cicnet.Chicago.mci.net (204.70.25.10) 69 ms 72 ms 61 ms 12 dgf-fddi1.cic.net (192.217.0.4) 54 ms 61 ms 65 ms 13 dgc-fddi0.cic.net (131.103.1.18) 74 ms 56 ms 74 ms 14 mke-dgc.cic.net (131.103.26.226) 277 ms 92 ms 290 ms 15 wiscnet.csd.uwm.edu (129.89.6.3) 154 ms 317 ms 141 ms 16 marquette-milwaukee.wiscnet.net (140.189.32.2) 127 ms 119 ms 477 ms 17 csdnb.csd.mu.edu (134.48.1.80) 222 ms 134 ms 189 ms 18 192.135.135.9 (192.135.135.9) 508 ms 1063 ms 432 ms 19 192.135.135.1 (192.135.135.1) 316 ms 373 ms 453 ms -- # [ end of file]

1 0

Concerning 192.x.x.x and routing
by postel＠ISI.EDU 08 Jan '96

08 Jan '96

----- Begin Included Message ----- From: "John S. Pinnow" <jspinnow(a)allmalt.cs.uwm.edu> Subject: Concerning 192.x.x.x and routing To: paul.weber(a)mci.com, jeff(a)UWM.EDU, EJNORMAN(a)MACC.WISC.EDU, hostmaster(a)cic.net, JKRey(a)ISI.EDU Date: Sat, 6 Jan 1996 14:29:30 -0600 (CST) Cc: jspinnow(a)allmalt.cs.uwm.edu (John S. Pinnow) I am trying to reach 192.135.135.1 and I know it is up. They are trying to get out with no success. Now every time I trying to telnet,rlogin,ftp to this place. The packets are sent down the wrong route. 192.135.135.1 is supposed to hop on to wiscnet.net and make its way to csdnb.csd.mu.edu and then route over via that server. This is not happening. >From serveral accounts I tried. Each funneling the packets down mci net. Interesting enough I tried random destinations on the 192.x.x.x network and they all want to wrote the same way. I think something is funny here. Someone along the line has some weird mask set that is funneling the whole 192 net down a pipe that it may not have to travel threw. traceroute to csdnb.csd.mu.edu. It makes it fine. Thats where the 192.135.135.x packets are destined for, but they never get there. Now... I ask you kindly to research this. I already got a message to contact whois 192.135.135. Now don't give me that. I know the administrator and he is just as puzzled as I am about this mess. They can't get out and I can't get back in. I am a bit frustrated. If you kindly give me information on who to contact to get this routing mess back under control, I would greatly appreciate it. Thank you for assistance! -- John S. Pinnow `net:jspinnow@cs.uwm.edu ` Home Voice: [414] 761-1537 My opinions are not that of UWM, I am not operating in any official compacity ----- End Included Message ----- ----- Begin Included Message ----- From: John Stewart Pinnow <jspinnow(a)winternet.com> Subject: Why? To: JKRey(a)ISI.EDU Date: Wed, 3 Jan 1996 21:09:18 -0600 (CST) Content-Type: text Content-Length: 838 %/usr/etc/traceroute 192.135.135.1 traceroute to 192.135.135.1 (192.135.135.1), 30 hops max, 40 byte packets 1 winternet-gw.winternet.com (198.174.169.254) 8 ms 24 ms 41 ms 2 mrnet-Winternet1.MR.Net (137.192.18.1) 55 ms 13 ms 34 ms 3 MIXNet-gw.MR.Net (137.192.241.254) 49 ms 69 ms 41 ms 4 192.168.168.5 (192.168.168.5) 43 ms 56 ms 55 ms 5 border3-hssi1-0.Chicago.mci.net (204.70.26.5) 177 ms 189 ms 162 ms 6 * Why is 192.135.135.x routing down threw MCINET????? it should be routing to wiscnet and then to csdnb.csd.mu.edu -- John S. Pinnow|net:jspinnow@cs.uwm.edu |Home Voice: [414] 761-1537 <=T=> TR <=R=>| jspinnow(a)world.std.com|Voice Mail: [414] 287-5252 Milwaukee, WI | jspinnow@winternet.com|http://www.uwm.edu/~jspinnow Disclaimer----> The views expressed are not necessarily those of U.W.M ----- End Included Message -----

4 3

NANOG Meeting February 15 & 16
by Pam Ciesla 08 Jan '96

08 Jan '96

Will be is San Diego at the Supercomputing Center in the auditorium at the Institute of the Americas. Meeting times are Thursday, 2/15 9:00AM - 5:00PM and Friday, 2/16 9:00AM - 1:00PM both days are preceeded with a continental breakfast at 8:30AM. Rooms have been blocked at the Residence Inn #(619) 587-1770 located at 8901 Gilman Dr. La Jolla, CA 92037. Other hotel info will follow later. All info will be put on the WEB Page as soon as possible. Registration will be available on the WEB Page or my sending e-mail to me (pam(a)merit.edu) Sorry for the delay in getting info out, but due to holiday time, vacations and illness info has been slow. Please feel free to send any questions regarding nanog to me. Thanks Pam Ciesla

1 0

Re: Info (fwd)
by sob＠academ.com 08 Jan '96

08 Jan '96

Try this URL: http://nic.merit.edu/routing.arbiter/NANOG/NANOG.html -- Stan | Academ Consulting Services |internet: sob(a)academ.com Olan | For more info on academ, see this |uucp: {mcsun|amdahl}!academ!sob Barber | URL- http://www.academ.com/academ |Opinions expressed are only mine.

1 0

Info (fwd)
by Patrick J. Chicas 08 Jan '96

08 Jan '96

Aloha, I am trying a somewhat broad aproach this time. My first message to nanog was returned from some bbn planet site.. Patrick J. Chicas, CIO * Hawaii OnLine * Hawaii's Statewide Internet Service ---------------------------------------------------------------------------- http://www.aloha.net http://www.planet-hawaii.com http://www.aloha.net/~pjc ---------- Forwarded message ---------- Date: Sun, 7 Jan 1996 14:51:26 -1000 (HST) From: Patrick J. Chicas <pjc(a)aloha.net> To: nanog(a)merit.edu Subject: Info Aloha, Could you provide information on the NANOG group for my clarification, i.e. purpose, objectives, next meeting? Mahalo Patrick J. Chicas, CIO * Hawaii OnLine * Hawaii's Statewide Internet Service ---------------------------------------------------------------------------- http://www.aloha.net http://www.planet-hawaii.com http://www.aloha.net/~pjc

1 0

Info
by Patrick J. Chicas 08 Jan '96

08 Jan '96

Aloha, Could you provide information on the NANOG group for my clarification, i.e. purpose, objectives, next meeting? Mahalo Patrick J. Chicas, CIO * Hawaii OnLine * Hawaii's Statewide Internet Service ---------------------------------------------------------------------------- http://www.aloha.net http://www.planet-hawaii.com http://www.aloha.net/~pjc

1 0

Transportation to NANOG
by owen＠DeLong.SJ.CA.US 05 Jan '96

05 Jan '96

I was wondering if anyone else going to NANOG from the Bay Area was interested in flying a small plane down. Specifically, I'm hoping to find an Instrument rated Pilot. I'm a private pilot, but do not hold an Instrument rating. Planes available to me are PA28 series, including Warrior (PA28-161), Archer (PA28-181), Dakota (PA28-236) and Arrow (PA28R-201). By that time, I should also have access to a couple of T-tail Arrows (PA28RT-201) as well. Even if you are not a pilot, but are interested in sharing expenses, this can probably work out. My plan is to leave around 3PM on Wednesday, and return during daylight hours after the meeting. The schedule on the return can be somewhat flexible. Please respond by email to owen(a)delong.sj.ca.us. Thanks, Owen

1 0

Re: Question on % of good routes and plea for an RA mail list was Re: Routing registry was Re: Sprint BGP filters in 207.x.x.x?
by Steven J. Richardson 05 Jan '96

05 Jan '96

>From list-admin(a)merit.edu Thu Jan 4 05:03:27 1996 >Message-Id: <9601040929.AA14593(a)ncc.ripe.net> >To: hwb(a)upeksa.sdsc.edu (Hans-Werner Braun) >Cc: nanog(a)merit.edu, RIPE Routing WG <routing-wg(a)ripe.net> >Subject: Question on % of good routes and plea for an RA mail list was Re: Routing registry was Re: Sprint BGP filters in 207.x.x.x? >In-Reply-To: Your message of Wed, 03 Jan 1996 15:21:50 PST. > <199601032321.PAA24966(a)upeksa.sdsc.edu> >References: <199601032321.PAA24966(a)upeksa.sdsc.edu> >From: Daniel Karrenberg <Daniel.Karrenberg(a)ripe.net> >Date: Thu, 04 Jan 1996 10:29:49 +0100 >Sender: Daniel.Karrenberg(a)ripe.net >The early NSFnet one was done to configure a single backbone. Remember >that EGP was the state-of-the-art. NSFNet provided last resort routing >and everyone was happy. More complex registries were not needed to keep >track of this even when "back doors" appeared. > >In Europe the situation was not like that at all. Despite great efforts >we were never blessed with a single pan-European backbone or even a >last-resort routing service. This is why RIPE developed a routing >registry that was capable of being useful in a general topology of >indepoendent ISPs. FYI: Lest anyone think that the PRDB was single-backbone-specific in _design_ or capability (it pretty much was in terms of data), let me note that, when Andy Adams and I rewrote the PRDB from a SPIRES DB to a RDBMS (with help from Tom Libert and Sue Hares), we explicitly designed in the ability to include data from other backbones. This was initially done to support both the T1 and T3 backbones, but it could easily have supported other backbones as well. >Daniel Steve Richardson/Merit

2 1

None
by Robert F. Oyler 05 Jan '96

05 Jan '96

subscribe bob oyler Bob Oyler INTERNET KANSAS oyler(a)ixks.com IXKS.Inc. Voice 913-842-966 FAX 913-842-3888

1 0