- NANOG - lists.nanog.org

Re: OPERATIONAL : MCI - Kansas City hosed?
by Sean Donelan 22 Jul '98

22 Jul '98

>For the past 12 or so hours, we have been experiencing mediocre response >times through MCI's core in Kansas City... has anyone heard of any problems >there? I haven't been able to find out anything....(now...where's my >multi-homed link request form again???) MCI hasn't posted anything to their customer list, but if you go to their traffic monitoring site http://traffic.mci.com/ you'll find Independence isn't listed on the front page with the rest of the "green" sites. Go down a level to the "other cities" page and query various various destinations. Independence to several other cities on MCI's network reports a "red" and "yellow" delay statistic. Before a reporter takes this date point and turns it into a gory story, remember MCI is about the only major NSP making any data public about their network performance. If everything was always "green," people might wonder if it was rigged. I'm sure several other folks will also post the inevitable question, have you asked MCI's NOC about this? -- Sean Donelan, Data Research Associates, Inc, St. Louis, MO Affiliation given for identification not representation

1 0

Weird BGP Issue
by Jason L. Weisberger 22 Jul '98

22 Jul '98

Lets say ISP X is peering with Tier One's A and B, as well as buying transit from them. ISP Y also peers with A and B, in another geographic region. While all routes for Y are best through A for X, it seems that 75% of X's routes have a return path of A for Y to reach X and the other 25%, although annouced in the EXACT SAME MANNER, use B for the return. ISPs A and B both claim they are distributing all of the routes in the exact same manner, there is no difference between a route for one of my /17's and there is for one of my /19's - yet some of my traffic is taking a different return path than the rest of it. Assymetry is cool and all, but this boggles the mind. Basically: I announce 207.155.0.0/17 and 209.151.224.0/19 to A and B. ISP A and B annouce them to both to Y, making no discrimination between the two routes. ISP Y takes A for 207.155.0.0/17 and B for 209.151.224.0/19 Why doesn't take the route from A as best is 207.155.0.0/17 is best from A or why doesn't it choose B over A, as the 209.151.224.0/19 route appears better. I'd like to understand this c.p. and not just find an answer that is "prepend your routes to A and B will always be preferred." Any ideas? -- Jason Weisberger Chief Technology Officer SoftAware, Inc. - 310/305-0275 ...but the wicked shall do wickedly... --Daniel 12:10

2 3

ATTCANADA.NET
by John Fraizer 22 Jul '98

22 Jul '98

Will someone from network operations for AT&T Canada please contact me. ------- John Fraizer (root) | __ _ | The System Administrator | / / (_)__ __ ____ __ | The choice mailto:root@EnterZone.Net | / /__/ / _ \/ // /\ \/ / | of a GNU http://www.EnterZone.Net/ | /____/_/_//_/\_,_/ /_/\_\ | Generation A 486 is a terrible thing to waste...

1 0

OPERATIONAL : MCI - Kansas City hosed?
by kbrown＠primelink.com 22 Jul '98

22 Jul '98

For the past 12 or so hours, we have been experiencing mediocre response times through MCI's core in Kansas City... has anyone heard of any problems there? I haven't been able to find out anything....(now...where's my multi-homed link request form again???) Danke Kevin Brown Huber & Associates, Inc. Networking Technologies kbrown(a)primelink.com

1 0

Operational issue: Mae-east
by dlr＠bungi.com 21 Jul '98

21 Jul '98

According to MFS's network staff, the current mae-east outage (now at 1.5 hours and rising) is a scheduled maintence. According to the on-duty staff, no one was notified. Not even them. Sigh. No ETA of when it will be back up. Dave Rand -- Dave Rand dlr(a)bungi.com http://www.bungi.com

3 2

Stac compression ?
by HANGU JEONG 21 Jul '98

21 Jul '98

Hi ! I would like to know that the modem throghput concerned with stac compression. The most of users using 56K V90 modems in windows 95 environment. Does anyone have idea about stac compression? Thanks Regards Jeong

2 1

N-Base Vulnerability Advisory
by TTSG 21 Jul '98

21 Jul '98

Hello, I won't post it in its entirety, but if you have any N-Base equipment, you might want to check out : The Telecom Security Group http://www.ttsg.com/TTSG/ ** TTSG VULNERABILITY ADVISORY ** Summary: Date: July 20, 1998 Subject: N-Base vulnerability Contact Address: nbase(a)ttsg.com Result: Comprimise security of switch, or render inoperable

1 0

Stac compression ?
by HANGU JEONG 21 Jul '98

21 Jul '98

Hi ! I would like to know that the modem throghput concerned with stac compression. The most of users using 56K V90 modems in windows 95 environment. Does anyone have idea about stac compression? Thanks Regards Jeong

1 0

MCI, CA*Net, & ANS routeserver information
by Jason Lixfeld 20 Jul '98

20 Jul '98

I'm looking for a little information on these routeservers. Currently, I am posting all information to the RADB but I am not sure if I should also be sending objects to the aforementioned DBs aswell. My upstreams are UUNet (AS816), SprintLink via Rogers Network Services (AS6463), CA*Net via Bell Global Solutions (AS3804) and soon to be linked to Sprint Canada directly. Is RADB sufficient? If so, why? If not, why? If I need to post objects to other route servers where can I find documentation on where to send the objects (ie: RADB is auto-dbm(a)ra.net and dbm-admin(a)ra.net) Any help would be appreciated. -- Regards, Jason A. Lixfeld Network Engineer, iDirect Network Operations --------------------------------------------------------------------- TUCOWS Interactive Ltd. | Internet Direct Canada Inc. 5415 Dundas Street West | Suite 301, Toronto Ontario | (416) 233-6036 x 18 (T) M9B-1B5 CANADA | (416) 236-5804 (F) --------------------------------------------------------------------- jlixfeld(a)idirect.ca | jlixfeld(a)idirect.com ---------------------------------------------------------------------

2 1

Re: MCI, CA*Net, & ANS routeserver information
by Joe Provo - Network Architect 20 Jul '98

20 Jul '98

> I'm looking for a little information on these routeservers. I'd suggest re-visiting the IRR web data from the RA/Merit (http://www.merit.edu/radb/docs/irr.html) for another description, check the infopage.mci.net data. The IRR is the collection of all the Routing Registries. If your provider/IP registry has their own routing registry, they will generally expect you to use it, or make provisions with them to pull data from other RRs. All others (generally those of us in the US) go thru the RA's RR. > be sending objects to the aforementioned DBs aswell. My upstreams are > UUNet (AS816), SprintLink via Rogers Network Services (AS6463), CA*Net via > Bell Global Solutions (AS3804) and soon to be linked to Sprint Canada > directly. Check with "Bell Global Solutions" WRT their relation with the CA*Net RR. That's the only potential confusion in what you list. > If I need to post objects to other route servers where can I find > documentation on where to send the objects (ie: RADB is auto-dbm(a)ra.net > and dbm-admin(a)ra.net) Each registry will have their own methods. I'm curious what the ANS/MCI registries will consist of/who they will be used by with all the merges and acquisitions... Cheers, Joe Provo -- 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>

1 0