- Test - lists.nanog.org

Re: MCI
by Wolfgang Henke 19 Mar '96

19 Mar '96

> What kinds of routers can route at near wire speeds a bunch of ports at > 155Mb ATM? None right now. Gigarouter can handle it theoretically, but... I'm being picky, but it's a moot question since doing wirespeed OC3c using ATM is impossible in of itself. Hell, mapping of SONET framings to ATM cells take off about 6 mbps right there. Anyway, until then you have a router that can do this, there always are ATM switches + cluster of routers. True, Netstars's Gigarouter is the fastest one shipping now. Its aggregate advertised bandwidth is 16 Gbps using a 16x16 matrix of non-blocking crosspoint switches. I have assembled a list of several best effort packet routers including known research efforts: http://www.whnet.com/wolfgang/giga.html Corrections and additions are welcome. Wolfgang Wolfgang Henke wolfgang(a)whnet.com . http://www.whnet.com/wolfgang/ WH Networks ... ftp.whnet.com /pub/wolfgang 2672 Bayshore Parkway Suite 503 ....... +1 415 390 9316 Mountain View CA 94043 ................... fax +1 415 390 9317

1 0

Re: AS path length?
by Scott Huddle 19 Mar '96

19 Mar '96

Andrew Partan (asp(a)uunet.uu.net) writes > > 690 1128 1128 5400 137 5441 5445 5446 i > > Humm - I have 2 routes with this path: > 2885 690 1128 1128 5400 137 5441 5445 5446 3230 > It's not the size of the path, it's what you do with it. -scott

1 0

Re: MCI/MAE-East/PSI losses unacceptable
by sgoldste＠nsf.gov 19 Mar '96

19 Mar '96

At 6:05 PM 3/18/96, William Allen Simpson wrote: >What is going on out at MAE-East? From Michigan, I'm seeing a >tremendous loss there, all day (since 10 am) between >mae-east-plusplus.Washington.mci.net. and mae-east.psi.net. It is >completely impossible to POP3 my email. SUNOS just times out the TCP >connection after about 10KB in 1/2 hour. > I don't want to sound like the fly that was doing the elephant and asked, "Does this hurt?" But... NSF (the organization, the building, and not the networking division) in its infinite wisdom decided to change ISPs from SURANET (bbn Planet) to PSInet. The Computer and Information Science and Engineering Directorate, to which our networking division belongs, has its own "high-speed LAN" (HSL). NSF, the building, has still not changed over its connection to PSInet, but our HSL has. The building is apparently not going to switch over until it gets its firewall on-line. So, to get to color printers and other organizational resources, our packets go through PSInet via MAE-E and back via SURA/bbn (MCI circuits) to the main LANs. Yesterday was a very busy day, shipping scads of graphics files to the color printers getting ready for big presentation schedule. Did it hurt? --SG ____________________________________________ Steve Goldstein, National Science Foundation +1(703)306-1949 Ext. 1119 "Let's not procrastinate until next week!"

1 0

Re: AS path length?
by Brett D. Watson 19 Mar '96

19 Mar '96

this is the longest i could find on such short notice: * 192.107.51.0 192.41.177.140 128 80 0 690 1128 1128 5400 13 7 5441 5445 5446 i we have quite a lot of 192.* address with this as path. -brett > > And now for something completly different. > > What is the longest AS path that people see? > > > -- > --bill

2 1

Re: Allocation of IP Addresses
by Paul Ferguson 19 Mar '96

19 Mar '96

At 09:09 AM 3/18/96 -0500, Robert Moskowitz wrote: > >BTW, there are 'rumours' floating around that China wants a couple of A's or >so... > There is also a train of thought that China should simply use RFC-1918 addressing and some type of network address translation, since they control explicit points of entry & exit to the global Internet from/to the country, and are determined to isolate themselves from the remainder of the Internet community anyway. But I digress. - paul

2 1

RE: NET99 sabotages IGC's routes NOW: The facts
by Ted Linnenkamp 19 Mar '96

19 Mar '96

New mail package, forgot new sig. Thanks, Ted L. *** Speaking solely for myself unless otherwise noted *** >---------- >From: Michael Dillon[SMTP:michael@memra.com] >Sent: Monday, March 18, 1996 5:03 PM >To: Ted Linnenkamp >Cc: 'Peter Kline, Sr. Network Engineer'; 'David ``Joel Katz'' >Schwartz'; 'nanog(a)merit.edu' >Subject: RE: NET99 sabotages IGC's routes NOW: The facts > >On Mon, 18 Mar 1996, Ted Linnenkamp wrote: > >> Please take this crap off of nanog. Resolve your pissing match somewhere >> else. >> >> Thanks in advance, > >Aren't you supposed to insert a disclaimer here about the opinions of >Microsoft? Or are these actually official opinions? :-) > > >Michael Dillon Voice: >+1-604-546-8022 >Memra Software Inc. Fax: >+1-604-546-3049 >http://www.memra.com E-mail: >michael(a)memra.com > >

1 0

RE: NET99 sabotages IGC's routes NOW: The facts
by Ted Linnenkamp 19 Mar '96

19 Mar '96

Please take this crap off of nanog. Resolve your pissing match somewhere else. Thanks in advance, Ted L. >

2 1

AS path length?
by bmanning＠isi.edu 19 Mar '96

19 Mar '96

And now for something completly different. What is the longest AS path that people see? -- --bill

1 0

MCI/MAE-East/PSI losses unacceptable
by William Allen Simpson 18 Mar '96

18 Mar '96

What is going on out at MAE-East? From Michigan, I'm seeing a tremendous loss there, all day (since 10 am) between mae-east-plusplus.Washington.mci.net. and mae-east.psi.net. It is completely impossible to POP3 my email. SUNOS just times out the TCP connection after about 10KB in 1/2 hour. Pinging every 2 seconds for over 20 minutes: Recording Mon Mar 18 22:27:16 GMT 192.41.177.245 sent rcvd % rtt avg mdev max min 390 199 51 532 480 73 1185 291 391 200 51 317 460 96 1185 291 392 201 51 411 454 84 1185 291 396 202 51 453 454 63 1185 291 Recording Mon Mar 18 22:26:54 GMT 204.70.74.102 sent rcvd % rtt avg mdev max min 328 261 80 253 265 25 520 219 330 262 79 238 262 26 520 219 332 263 79 251 261 22 520 219 333 264 79 249 260 20 520 219 Of course, there is a 20% loss on MCI net alone. Seems to be after West Orange. 8: 204.70.2.81 core-fddi-0.Chicago.mci.net. (271 ms) (203 ms) (452 ms) 9: 204.70.1.94 core1-hssi-2.NorthRoyalton.mci.net. (216 ms) (209 ms) (232 ms) 10: 204.70.1.102 core1-hssi-3.WestOrange.mci.net. (226 ms) (273 ms) (214 ms) 11: 204.70.1.106 core2-hssi-2.Washington.mci.net. (243 ms) (379 ms) (240 ms) 12: 204.70.74.52 borderx1-fddi-1.Washington.mci.net. (325 ms) (281 ms) (250 ms) 13: 204.70.74.102 mae-east-plusplus.Washington.mci.net. (251 ms) *** (284 ms) 14: *** *** 192.41.177.245 mae-east.psi.net. (363 ms) Whatever happened to the Chicago NAP? What can we do to fix this problem? WSimpson(a)UMich.edu Key fingerprint = 17 40 5E 67 15 6F 31 26 DD 0D B9 9B 6A 15 2C 32

1 0

Addr: NET99 sabotages IGC's routes
by rwoundy＠vnet.IBM.COM 18 Mar '96

18 Mar '96

*** Resending note of 03/18/96 12:43 Folks, May I inject some list-relevant discussion to this cat-fight? >> Fortunately, MCI was able to reconfigure our access lists at their >>router to allow us to broadcast competing more specific routes for each >>individual class C in the CIDR block. Thus (more or less) restoring IGC's >>net connectivity. >More specifics aren't competing. They take precedence. Sometimes it's >better to be silent and thought dumb... I don't care to choose sides in this dispute. But as a consequence of this dispute, the size of the standard default-free route tables has grown as a result of the IGC/MCI de-aggregation of routes. This is a bad thing, right? Looking at IBM/Advantis's router at MAE-East, for example, I see 205.198/16 from (AS3830), 205.198.244/22 from (AS3561 AS5799), and 205.198.244/24 from (AS3561 AS5799). AS3830 == Net99, AS3561 == MCI, and AS5799 == IGC. Seems like the rest of the Internet is the long-term victim here... -- Richard Woundy, (not speaking for) IBM

1 0