- NANOG - lists.nanog.org

Sprint problems?
by David M. Ramsey 13 Apr '02

13 Apr '02

Did anyone else out there have routing and/or BGP issues with AS1239 this afternoon (Saturday 13-April, ~11:30 EST - ~15:00 EST) ?? Sprint is one of our upstreams, and for about 3 hours today some remote users were unable to reach us via our Sprint connection. We heard complaints from Road Runner and BellSouth.net DSL users, among others. Sprint's NOC claims they had no issues, but suddenly it started working as I was on the telephone explaining the situation. Nothing changed on our side. It seems to be "over" now, but I'd like some idea of what happened? Thanks for any help/insight/advice/info, David Ramsey CT Communications Charlotte, NC

2 1

RE: genuity - any good?
by Kris Foster 13 Apr '02

13 Apr '02

Quick correct, they are extended access-lists > -----Original Message----- > From: Kris Foster [mailto:Kris.Foster@telus.com] > Sent: Friday, April 12, 2002 11:02 AM > To: 'Roy'; matthew zeier; nanog(a)merit.edu > Subject: RE: genuity - any good? > > > > > reasonable route for your prefixes. According to one of > > their top people, > > prefix-lists were unreliable new technology. We gave up and > > canceled the > > circuit. > > > > Genuity does use prefix lists (at least now). And, in my > experiences with > them is extremely fast in their turn around time to update these. > > Kris > >

3 2

Re: packet reordering at exchange points
by Peter Galbavy 13 Apr '02

13 Apr '02

> Gotta go with the old head scratch on that one... > > Imagine the packet zipping down a wire. It hits a router. It slows > down. Why? Because (until very recently) wire-speed != processing > speed != backplane speed... This is called 'blocking'. The packet > has to wait somewhere while the prior packet is being processed > and fed through the backplane. > > Very recently vendors started offloading tasks from a single processor > to sub-processors and ASICs in a more distributed manner. This has led > to routers that are faster than the wire (in contrast to the above > stated routers that were slower than the wire). In this situation, > buffering allows a greater port density: that is to say, more > channels at a slower speed (the speed of the wire) rather than > less channels at a higher speed (faster than the wire). Apart from the fact that I have been building these (PC/Sparc based) routers since the early '90s is neither here nor there. My point in general was to actualy try to make people explain why there is a 'marketing' relationship between the size of buffers and a magical bandwidth x delay product of (normally) line rate x one second. I fully understand (in case it appeared otherwise) the issues of interface contention when aggregating traffic and also the need for buffering in QoS implementations, but the perceived wisdom of 'you must have at least one seconds buffer on each *interface*' still seems very shoddy and marketing driven. Still haven't heard it (a good reason), but then again I haven't gone to read Van Jacobson's paper that was referenced in an earlier reply. And that paper probably makes too good a point and bears no relation to the marketing drivel we have been getting for many years. BTW The faster than line rate / slower than line rate forwarding engine stuff is an ongoing and iterative thing that has been the simple result of capacity growth and in turn a has spurred the development of each new generation of router - just like any growth industry - and this will continue until we run out of electrons and photons and god-knows-what-else to move around. Peter

1 0

RE: genuity - any good?
by Martin, Christian 13 Apr '02

13 Apr '02

I think the argument is not about route filtering - it is the implementation method. Genuity uses ip extended access-lists. Everyone else uses prefix-lists. To a purist, the former is more granular, but performs poorly because it is a linked list implementation. The later, while less granular, performs faster by using a trie. It also allows insertion without list rebuilding. Does this matter much? I'm sure there are some that have tested convergence between the two technologies, so I'd welcome comments out of curiosity. They are somewhat anal with their lists as well. If you have a /19, but you want to deaggregate for inbound BGP TE, you will need to send them EVERY route you will send. That can be 64 subnets. For a /16, it is waaayyy worse. Then again, it allows them to know exactly how many prefixes MAY be announced from their customers, which I suppose has its merits. chris >-----Original Message----- >From: neil(a)DOMINO.ORG [mailto:neil@DOMINO.ORG] >Sent: Friday, April 12, 2002 2:08 PM >To: garlic(a)garlic.com >Cc: matthew(a)velvet.org; nanog(a)merit.edu >Subject: Re: genuity - any good? > > > >> 1) Their BGP polices are not as good as others. They force you to >> register each route you want to advertise rather than >allowing you to >> advertise any reasonable route for your prefixes. According >to one of >> their top people, prefix-lists were unreliable new technology. We >> gave up and canceled the circuit. > >Man I don't know of a provider that doesn't do this - but the >fact is this is a good thing. >

4 3

RE: UUNET service
by Martin, Christian 12 Apr '02

12 Apr '02

> >In the cisco router, if you configure a aggregate route under >bgp, it will be pointing to null0 to prevent this senario from >happening. So my question( not related to attitude)is:Is this >because of the aggregation? > >-ns No. This is because the customer's router has no better way to get to their own network than to go to their default, which is UU. Were there an aggregate configured, with no contributing route remaining to the aggregate, the same behavior would occur because the aggregate would go away. Simple scenario - UU static to the customer for net X customer static default to UU customer link to net X fails customer router uses next best path, which is default to UU This is quite common, actually. chris > >-----Original Message----- >From: jlewis(a)lewis.org [mailto:jlewis@lewis.org] >Sent: 12 April 2002 4:21 PM >To: Bradley Corner >Cc: nanog(a)merit.edu >Subject: Re: UUNET service > > > >To me, that looks more like an outage (now fixed) on a >customer network. The 'loop' between >500.Serial2-11.GW4.BWI1.ALTER.NET and >core62007-gw.customer.alter.net, could likely be caused by >UU's customer advertising an aggregate route to UU, but not >actually having a route to the IP...so they default back to >UU, and UU sends it back to the customer. > >This was likely a problem on the customer's network, so why >should UUNet take a trouble report from you? Not only are you >not _the_ customer, you're not even a customer, and it's >likely not a problem they can do anything about. If it really >were a UUNet problem, they probably assume their customer will >report it. > >> | 37 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET >> | Baltimore, MD, USA | -05:00 | 161 | -x | UUNET >> Technologies, Inc. | >> | 38 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net >> | - | | 210 | --x | UUNET > > >On Fri, 12 Apr 2002, Bradley Corner wrote: > >> I tried to notify UUNET at their 800-900-0241 number that >there was a >> loop in their network. They told me that if I didn't have an account >> with them they were not interested in any information that I >may have >> had for them. I stated that I was just calling so that they >could pass >> the information onto an engineer. He repeated himself saying >if you do >> not have an account with us I will not do anything with the >> information. I guess they think they run the internet and us small >> ISPs couldn't possibly know anything... >> >> >> In case someone at UUNET reads this here is the traceroute. >> >> >> ================================================== >> === VisualRoute report on 12-Apr-02 3:04:18 PM === >> ================================================== >> >> Report for online.mmsi-usa.com [162.33.138.132] >> >> Analysis: The routing loop (65.195.230.218 / 162.33.130.4 / >> 162.33.128.249 / 205.197.182.201 / 162.33.138.129 / 65.195.230.217) >> starting in hops 12-17 is not allowing IP packets to get to their >> destination. >> >> >---------------------------------------------------------------------- >> -- >> >--------------------------------------------------------------- >--------- >> ----------------------------- >> | Hop | %Loss | IP Address | Node Name >> | Location | Tzone | ms | Graph | Network >> | >> >---------------------------------------------------------------------- >> -- >> >--------------------------------------------------------------- >--------- >> ----------------------------- >> | 0 | | 10.100.15.40 | BRADLEY.nefmls.com >> | ... | | | | (private use) >> | >> | 1 | | 209.12.49.1 | - >> | ?Jacksonville, FL 32256 | | 1 | x | Northeast >> Florida MLS | >> | 2 | | 206.222.124.121 | - >> | ?Herndon, VA 20165 | | 3 | x | e.spire >> Communications, Inc. | >> | 3 | | 206.222.126.77 | washing2-dc-a5-0-0-10.rt.espire.net >> | - | | 27 | x-- | e.spire >> Communications, Inc. | >> | 4 | | 206.222.127.118 | reston-va-1-pos0-0-0.rt.espire.net >> | - | | 37 | x--- | e.spire >> Communications, Inc. | >> | 5 | | 198.32.187.97 | mae-east-level3.com >> | Vienna, VA, USA | | 133 | --x- | >Exchange Point >> Blocks | >> | 6 | | 64.159.18.98 | ae0-54.mp2.Washington1.Level3.net >> | Washington, DC, USA | -05:00 | 137 | -x--- | Level 3 >> Communications, Inc. | >> | 7 | | 64.159.0.110 | >so-0-0-0.mp1.Philadelphia1.Level3.net >> | Philadelphia, PA, USA | -05:00 | 147 | -x------ | Level 3 >> Communications, Inc. | >> | 8 | | 64.159.0.150 | >> gige9-0.hsipaccess2.Philadelphia1.Level3.net | Philadelphia, >PA, USA | >> -05:00 | 137 | -x---- | Level 3 Communications, Inc. | >> | 9 | | 63.208.101.158 | unknown.Level3.net >> | - | | 147 | -x------- | Level 3 >> Communications, Inc. | >> | 10 | | 162.33.162.25 | 401n--30th-st--phily.coretel.net >> | ?Annapolis, MD 21401 | | 139 | --x---- | Core >> Communications, Inc. | >> | 11 | 10 | 162.33.162.29 | baltamtrak-p.highway.coretel.net >> | ?Annapolis, MD 21401 | | 146 | -x------ | Core >> Communications, Inc. | >> | 12 | | 65.195.230.218 | core62007-gw.customer.alter.net >> | - | | 142 | -x---- | UUNET >> Technologies, Inc. | >> | 13 | | 162.33.130.4 | i97.toad.net >> | ?Woodbridge, NJ 07095 | | 124 | --x-- | RAM >> Communications Consultants, Inc. | >> | 14 | | 162.33.128.249 | tiara-2-balto.ds1.toad.net >> | ?Woodbridge, NJ 07095 | | 134 | -x---- | RAM >> Communications Consultants, Inc. | >> | 15 | | 205.197.182.201 | max2.toad.net >> | ?Severna Park, MD 21146 | | 146 | -x-- | ToadNet, Inc. >> | >> | 16 | | 162.33.138.129 | mmsi-cpe.dsllan.toad.net >> | ?Woodbridge, NJ 07095 | | 198 | -x--- | RAM >> Communications Consultants, Inc. | >> | 17 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET >> | Baltimore, MD, USA | -05:00 | 147 | x-- | UUNET >> Technologies, Inc. | >> | 18 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net >> | - | | 154 | -x---- | UUNET >> Technologies, Inc. | >> | 19 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET >> | Baltimore, MD, USA | -05:00 | 154 | -x-- | UUNET >> Technologies, Inc. | >> | 20 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net >> | - | | 170 | --x--- | UUNET >> Technologies, Inc. | >> | 21 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET >> | Baltimore, MD, USA | -05:00 | 131 | -x-- | UUNET >> Technologies, Inc. | >> | 22 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net >> | - | | 150 | -x--- | UUNET >> Technologies, Inc. | >> | 23 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET >> | Baltimore, MD, USA | -05:00 | 159 | -x- | UUNET >> Technologies, Inc. | >> | 24 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net >> | - | | 171 | -x--- | UUNET >> Technologies, Inc. | >> | 25 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET >> | Baltimore, MD, USA | -05:00 | 169 | -x- | UUNET >> Technologies, Inc. | >> | 26 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net >> | - | | 188 | -x---- | UUNET >> Technologies, Inc. | >> | 27 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET >> | Baltimore, MD, USA | -05:00 | 169 | x-- | UUNET >> Technologies, Inc. | >> | 28 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net >> | - | | 191 | x----- | UUNET >> Technologies, Inc. | >> | 29 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET >> | Baltimore, MD, USA | -05:00 | 179 | x--- | UUNET >> Technologies, Inc. | >> | 30 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net >> | - | | 188 | -x---- | UUNET >> Technologies, Inc. | >> | 31 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET >> | Baltimore, MD, USA | -05:00 | 179 | -x-- | UUNET >> Technologies, Inc. | >> | 32 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net >> | - | | 163 | x | UUNET >> Technologies, Inc. | >> | 33 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET >> | Baltimore, MD, USA | -05:00 | 184 | -x- | UUNET >> Technologies, Inc. | >> | 34 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net >> | - | | 168 | -x | UUNET >> Technologies, Inc. | >> | 35 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET >> | Baltimore, MD, USA | -05:00 | 166 | -x | UUNET >> Technologies, Inc. | >> | 36 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net >> | - | | 185 | -x- | UUNET >> Technologies, Inc. | >> | 37 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET >> | Baltimore, MD, USA | -05:00 | 161 | -x | UUNET >> Technologies, Inc. | >> | 38 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net >> | - | | 210 | --x | UUNET >> Technologies, Inc. | >> | 39 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET >> | Baltimore, MD, USA | -05:00 | 152 | -x | UUNET >> Technologies, Inc. | >> | 40 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net >> | - | | 167 | -x | UUNET >> Technologies, Inc. | >> | 41 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET >> | Baltimore, MD, USA | -05:00 | 176 | -x | UUNET >> Technologies, Inc. | >> | 42 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net >> | - | | 164 | x | UUNET >> Technologies, Inc. | >> | 43 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET >> | Baltimore, MD, USA | -05:00 | 173 | x | UUNET >> Technologies, Inc. | >> | 44 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net >> | - | | 158 | -x | UUNET >> Technologies, Inc. | >> | 45 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET >> | Baltimore, MD, USA | -05:00 | 168 | x | UUNET >> Technologies, Inc. | >> | 46 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net >> | - | | 166 | x | UUNET >> Technologies, Inc. | >> | 47 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET >> | Baltimore, MD, USA | -05:00 | 159 | x | UUNET >> Technologies, Inc. | >> | 48 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net >> | - | | 140 | x- | UUNET >> Technologies, Inc. | >> | 49 | 60 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET >> | Baltimore, MD, USA | -05:00 | 145 | x- | UUNET >> Technologies, Inc. | >> | 50 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net >> | - | | 170 | -x | UUNET >> Technologies, Inc. | >> | 51 | 70 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET >> | Baltimore, MD, USA | -05:00 | 137 | x- | UUNET >> Technologies, Inc. | >> | 52 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net >> | - | | 133 | x- | UUNET >> Technologies, Inc. | >> | 53 | 60 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET >> | Baltimore, MD, USA | -05:00 | 142 | x- | UUNET >> Technologies, Inc. | >> | 54 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net >> | - | | 147 | x- | UUNET >> Technologies, Inc. | >> | 55 | 60 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET >> | Baltimore, MD, USA | -05:00 | 143 | x- | UUNET >> Technologies, Inc. | >> | 56 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net >> | - | | 156 | -x | UUNET >> Technologies, Inc. | >> | 57 | 60 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET >> | Baltimore, MD, USA | -05:00 | 167 | -x | UUNET >> Technologies, Inc. | >> | 58 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net >> | - | | 167 | -x | UUNET >> Technologies, Inc. | >> | 59 | 60 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET >> | Baltimore, MD, USA | -05:00 | 170 | -x | UUNET >> Technologies, Inc. | >> | 60 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net >> | - | | 174 | -x | UUNET >> Technologies, Inc. | >> | 61 | 70 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET >> | Baltimore, MD, USA | -05:00 | 173 | -x | UUNET >> Technologies, Inc. | >> | 62 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net >> | - | | 178 | -x | UUNET >> Technologies, Inc. | >> | 63 | 60 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET >> | Baltimore, MD, USA | -05:00 | 186 | -x | UUNET >> Technologies, Inc. | >> | 64 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net >> | - | | 183 | x- | UUNET >> Technologies, Inc. | >> | ... | | | >> | | | | | >> | >> | ? | | 162.33.138.132 | online.mmsi-usa.com >> | ?Woodbridge, NJ 07095 | | | | RAM >> Communications Consultants, Inc. | >> >---------------------------------------------------------------------- >> -- >> >--------------------------------------------------------------- >--------- >> ----------------------------- >> Roundtrip time to 65.195.230.218, average = 183ms, min = 152ms, max = >> 210ms -- 12-Apr-02 3:04:18 PM >> >> Bradley Corner >> Northeast Florida Multiple Listing Service, Inc. >> 7801 Deecreek Club Rd Ste 1 >> Jacksonville FL 32217 >> (904) 394-9494 >> >> > >-- >---------------------------------------------------------------------- > Jon Lewis *jlewis(a)lewis.org*| I route > System Administrator | therefore you are > Atlantic Net | >_________ http://www.lewis.org/~jlewis/pgp for PGP public key_________ > >

1 0

RE: UUNET service
by Shi, Ning 12 Apr '02

12 Apr '02

In the cisco router, if you configure a aggregate route under bgp, it will be pointing to null0 to prevent this senario from happening. So my question( not related to attitude)is:Is this because of the aggregation? -ns -----Original Message----- From: jlewis(a)lewis.org [mailto:jlewis@lewis.org] Sent: 12 April 2002 4:21 PM To: Bradley Corner Cc: nanog(a)merit.edu Subject: Re: UUNET service To me, that looks more like an outage (now fixed) on a customer network. The 'loop' between 500.Serial2-11.GW4.BWI1.ALTER.NET and core62007-gw.customer.alter.net, could likely be caused by UU's customer advertising an aggregate route to UU, but not actually having a route to the IP...so they default back to UU, and UU sends it back to the customer. This was likely a problem on the customer's network, so why should UUNet take a trouble report from you? Not only are you not _the_ customer, you're not even a customer, and it's likely not a problem they can do anything about. If it really were a UUNet problem, they probably assume their customer will report it. > | 37 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET > | Baltimore, MD, USA | -05:00 | 161 | -x | UUNET > Technologies, Inc. | > | 38 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net > | - | | 210 | --x | UUNET On Fri, 12 Apr 2002, Bradley Corner wrote: > I tried to notify UUNET at their 800-900-0241 number that there was a > loop in their network. They told me that if I didn't have an account > with them they were not interested in any information that I may have > had for them. I stated that I was just calling so that they could pass > the information onto an engineer. He repeated himself saying if you do > not have an account with us I will not do anything with the information. > I guess they think they run the internet and us small ISPs couldn't > possibly know anything... > > > In case someone at UUNET reads this here is the traceroute. > > > ================================================== > === VisualRoute report on 12-Apr-02 3:04:18 PM === > ================================================== > > Report for online.mmsi-usa.com [162.33.138.132] > > Analysis: The routing loop (65.195.230.218 / 162.33.130.4 / > 162.33.128.249 / 205.197.182.201 / 162.33.138.129 / 65.195.230.217) > starting in > hops 12-17 is not allowing IP packets to get to their destination. > > ------------------------------------------------------------------------ > ------------------------------------------------------------------------ > ----------------------------- > | Hop | %Loss | IP Address | Node Name > | Location | Tzone | ms | Graph | Network > | > ------------------------------------------------------------------------ > ------------------------------------------------------------------------ > ----------------------------- > | 0 | | 10.100.15.40 | BRADLEY.nefmls.com > | ... | | | | (private use) > | > | 1 | | 209.12.49.1 | - > | ?Jacksonville, FL 32256 | | 1 | x | Northeast > Florida MLS | > | 2 | | 206.222.124.121 | - > | ?Herndon, VA 20165 | | 3 | x | e.spire > Communications, Inc. | > | 3 | | 206.222.126.77 | washing2-dc-a5-0-0-10.rt.espire.net > | - | | 27 | x-- | e.spire > Communications, Inc. | > | 4 | | 206.222.127.118 | reston-va-1-pos0-0-0.rt.espire.net > | - | | 37 | x--- | e.spire > Communications, Inc. | > | 5 | | 198.32.187.97 | mae-east-level3.com > | Vienna, VA, USA | | 133 | --x- | Exchange Point > Blocks | > | 6 | | 64.159.18.98 | ae0-54.mp2.Washington1.Level3.net > | Washington, DC, USA | -05:00 | 137 | -x--- | Level 3 > Communications, Inc. | > | 7 | | 64.159.0.110 | so-0-0-0.mp1.Philadelphia1.Level3.net > | Philadelphia, PA, USA | -05:00 | 147 | -x------ | Level 3 > Communications, Inc. | > | 8 | | 64.159.0.150 | > gige9-0.hsipaccess2.Philadelphia1.Level3.net | Philadelphia, PA, USA | > -05:00 | 137 | -x---- | Level 3 Communications, Inc. | > | 9 | | 63.208.101.158 | unknown.Level3.net > | - | | 147 | -x------- | Level 3 > Communications, Inc. | > | 10 | | 162.33.162.25 | 401n--30th-st--phily.coretel.net > | ?Annapolis, MD 21401 | | 139 | --x---- | Core > Communications, Inc. | > | 11 | 10 | 162.33.162.29 | baltamtrak-p.highway.coretel.net > | ?Annapolis, MD 21401 | | 146 | -x------ | Core > Communications, Inc. | > | 12 | | 65.195.230.218 | core62007-gw.customer.alter.net > | - | | 142 | -x---- | UUNET > Technologies, Inc. | > | 13 | | 162.33.130.4 | i97.toad.net > | ?Woodbridge, NJ 07095 | | 124 | --x-- | RAM > Communications Consultants, Inc. | > | 14 | | 162.33.128.249 | tiara-2-balto.ds1.toad.net > | ?Woodbridge, NJ 07095 | | 134 | -x---- | RAM > Communications Consultants, Inc. | > | 15 | | 205.197.182.201 | max2.toad.net > | ?Severna Park, MD 21146 | | 146 | -x-- | ToadNet, Inc. > | > | 16 | | 162.33.138.129 | mmsi-cpe.dsllan.toad.net > | ?Woodbridge, NJ 07095 | | 198 | -x--- | RAM > Communications Consultants, Inc. | > | 17 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET > | Baltimore, MD, USA | -05:00 | 147 | x-- | UUNET > Technologies, Inc. | > | 18 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net > | - | | 154 | -x---- | UUNET > Technologies, Inc. | > | 19 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET > | Baltimore, MD, USA | -05:00 | 154 | -x-- | UUNET > Technologies, Inc. | > | 20 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net > | - | | 170 | --x--- | UUNET > Technologies, Inc. | > | 21 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET > | Baltimore, MD, USA | -05:00 | 131 | -x-- | UUNET > Technologies, Inc. | > | 22 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net > | - | | 150 | -x--- | UUNET > Technologies, Inc. | > | 23 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET > | Baltimore, MD, USA | -05:00 | 159 | -x- | UUNET > Technologies, Inc. | > | 24 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net > | - | | 171 | -x--- | UUNET > Technologies, Inc. | > | 25 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET > | Baltimore, MD, USA | -05:00 | 169 | -x- | UUNET > Technologies, Inc. | > | 26 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net > | - | | 188 | -x---- | UUNET > Technologies, Inc. | > | 27 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET > | Baltimore, MD, USA | -05:00 | 169 | x-- | UUNET > Technologies, Inc. | > | 28 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net > | - | | 191 | x----- | UUNET > Technologies, Inc. | > | 29 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET > | Baltimore, MD, USA | -05:00 | 179 | x--- | UUNET > Technologies, Inc. | > | 30 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net > | - | | 188 | -x---- | UUNET > Technologies, Inc. | > | 31 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET > | Baltimore, MD, USA | -05:00 | 179 | -x-- | UUNET > Technologies, Inc. | > | 32 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net > | - | | 163 | x | UUNET > Technologies, Inc. | > | 33 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET > | Baltimore, MD, USA | -05:00 | 184 | -x- | UUNET > Technologies, Inc. | > | 34 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net > | - | | 168 | -x | UUNET > Technologies, Inc. | > | 35 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET > | Baltimore, MD, USA | -05:00 | 166 | -x | UUNET > Technologies, Inc. | > | 36 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net > | - | | 185 | -x- | UUNET > Technologies, Inc. | > | 37 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET > | Baltimore, MD, USA | -05:00 | 161 | -x | UUNET > Technologies, Inc. | > | 38 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net > | - | | 210 | --x | UUNET > Technologies, Inc. | > | 39 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET > | Baltimore, MD, USA | -05:00 | 152 | -x | UUNET > Technologies, Inc. | > | 40 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net > | - | | 167 | -x | UUNET > Technologies, Inc. | > | 41 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET > | Baltimore, MD, USA | -05:00 | 176 | -x | UUNET > Technologies, Inc. | > | 42 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net > | - | | 164 | x | UUNET > Technologies, Inc. | > | 43 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET > | Baltimore, MD, USA | -05:00 | 173 | x | UUNET > Technologies, Inc. | > | 44 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net > | - | | 158 | -x | UUNET > Technologies, Inc. | > | 45 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET > | Baltimore, MD, USA | -05:00 | 168 | x | UUNET > Technologies, Inc. | > | 46 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net > | - | | 166 | x | UUNET > Technologies, Inc. | > | 47 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET > | Baltimore, MD, USA | -05:00 | 159 | x | UUNET > Technologies, Inc. | > | 48 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net > | - | | 140 | x- | UUNET > Technologies, Inc. | > | 49 | 60 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET > | Baltimore, MD, USA | -05:00 | 145 | x- | UUNET > Technologies, Inc. | > | 50 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net > | - | | 170 | -x | UUNET > Technologies, Inc. | > | 51 | 70 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET > | Baltimore, MD, USA | -05:00 | 137 | x- | UUNET > Technologies, Inc. | > | 52 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net > | - | | 133 | x- | UUNET > Technologies, Inc. | > | 53 | 60 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET > | Baltimore, MD, USA | -05:00 | 142 | x- | UUNET > Technologies, Inc. | > | 54 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net > | - | | 147 | x- | UUNET > Technologies, Inc. | > | 55 | 60 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET > | Baltimore, MD, USA | -05:00 | 143 | x- | UUNET > Technologies, Inc. | > | 56 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net > | - | | 156 | -x | UUNET > Technologies, Inc. | > | 57 | 60 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET > | Baltimore, MD, USA | -05:00 | 167 | -x | UUNET > Technologies, Inc. | > | 58 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net > | - | | 167 | -x | UUNET > Technologies, Inc. | > | 59 | 60 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET > | Baltimore, MD, USA | -05:00 | 170 | -x | UUNET > Technologies, Inc. | > | 60 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net > | - | | 174 | -x | UUNET > Technologies, Inc. | > | 61 | 70 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET > | Baltimore, MD, USA | -05:00 | 173 | -x | UUNET > Technologies, Inc. | > | 62 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net > | - | | 178 | -x | UUNET > Technologies, Inc. | > | 63 | 60 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET > | Baltimore, MD, USA | -05:00 | 186 | -x | UUNET > Technologies, Inc. | > | 64 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net > | - | | 183 | x- | UUNET > Technologies, Inc. | > | ... | | | > | | | | | > | > | ? | | 162.33.138.132 | online.mmsi-usa.com > | ?Woodbridge, NJ 07095 | | | | RAM > Communications Consultants, Inc. | > ------------------------------------------------------------------------ > ------------------------------------------------------------------------ > ----------------------------- > Roundtrip time to 65.195.230.218, average = 183ms, min = 152ms, max = > 210ms -- 12-Apr-02 3:04:18 PM > > Bradley Corner > Northeast Florida Multiple Listing Service, Inc. > 7801 Deecreek Club Rd Ste 1 > Jacksonville FL 32217 > (904) 394-9494 > > -- ---------------------------------------------------------------------- Jon Lewis *jlewis(a)lewis.org*| I route System Administrator | therefore you are Atlantic Net | _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________

1 0

UUNET service
by Bradley Corner 12 Apr '02

12 Apr '02

I tried to notify UUNET at their 800-900-0241 number that there was a loop in their network. They told me that if I didnt have an account with them they were not interested in any information that I may have had for them. I stated that I was just calling so that they could pass the information onto an engineer. He repeated himself saying if you do not have an account with us I will not do anything with the information. I guess they think they run the internet and us small ISPs couldnt possibly know anything... In case someone at UUNET reads this here is the traceroute. ================================================== === VisualRoute report on 12-Apr-02 3:04:18 PM === ================================================== Report for online.mmsi-usa.com [162.33.138.132] Analysis: The routing loop (65.195.230.218 / 162.33.130.4 / 162.33.128.249 / 205.197.182.201 / 162.33.138.129 / 65.195.230.217) starting in hops 12-17 is not allowing IP packets to get to their destination. ------------------------------------------------------------------------ ------------------------------------------------------------------------ ----------------------------- | Hop | %Loss | IP Address | Node Name | Location | Tzone | ms | Graph | Network | ------------------------------------------------------------------------ ------------------------------------------------------------------------ ----------------------------- | 0 | | 10.100.15.40 | BRADLEY.nefmls.com | ... | | | | (private use) | | 1 | | 209.12.49.1 | - | ?Jacksonville, FL 32256 | | 1 | x | Northeast Florida MLS | | 2 | | 206.222.124.121 | - | ?Herndon, VA 20165 | | 3 | x | e.spire Communications, Inc. | | 3 | | 206.222.126.77 | washing2-dc-a5-0-0-10.rt.espire.net | - | | 27 | x-- | e.spire Communications, Inc. | | 4 | | 206.222.127.118 | reston-va-1-pos0-0-0.rt.espire.net | - | | 37 | x--- | e.spire Communications, Inc. | | 5 | | 198.32.187.97 | mae-east-level3.com | Vienna, VA, USA | | 133 | --x- | Exchange Point Blocks | | 6 | | 64.159.18.98 | ae0-54.mp2.Washington1.Level3.net | Washington, DC, USA | -05:00 | 137 | -x--- | Level 3 Communications, Inc. | | 7 | | 64.159.0.110 | so-0-0-0.mp1.Philadelphia1.Level3.net | Philadelphia, PA, USA | -05:00 | 147 | -x------ | Level 3 Communications, Inc. | | 8 | | 64.159.0.150 | gige9-0.hsipaccess2.Philadelphia1.Level3.net | Philadelphia, PA, USA | -05:00 | 137 | -x---- | Level 3 Communications, Inc. | | 9 | | 63.208.101.158 | unknown.Level3.net | - | | 147 | -x------- | Level 3 Communications, Inc. | | 10 | | 162.33.162.25 | 401n--30th-st--phily.coretel.net | ?Annapolis, MD 21401 | | 139 | --x---- | Core Communications, Inc. | | 11 | 10 | 162.33.162.29 | baltamtrak-p.highway.coretel.net | ?Annapolis, MD 21401 | | 146 | -x------ | Core Communications, Inc. | | 12 | | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 142 | -x---- | UUNET Technologies, Inc. | | 13 | | 162.33.130.4 | i97.toad.net | ?Woodbridge, NJ 07095 | | 124 | --x-- | RAM Communications Consultants, Inc. | | 14 | | 162.33.128.249 | tiara-2-balto.ds1.toad.net | ?Woodbridge, NJ 07095 | | 134 | -x---- | RAM Communications Consultants, Inc. | | 15 | | 205.197.182.201 | max2.toad.net | ?Severna Park, MD 21146 | | 146 | -x-- | ToadNet, Inc. | | 16 | | 162.33.138.129 | mmsi-cpe.dsllan.toad.net | ?Woodbridge, NJ 07095 | | 198 | -x--- | RAM Communications Consultants, Inc. | | 17 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 147 | x-- | UUNET Technologies, Inc. | | 18 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 154 | -x---- | UUNET Technologies, Inc. | | 19 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 154 | -x-- | UUNET Technologies, Inc. | | 20 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 170 | --x--- | UUNET Technologies, Inc. | | 21 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 131 | -x-- | UUNET Technologies, Inc. | | 22 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 150 | -x--- | UUNET Technologies, Inc. | | 23 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 159 | -x- | UUNET Technologies, Inc. | | 24 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 171 | -x--- | UUNET Technologies, Inc. | | 25 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 169 | -x- | UUNET Technologies, Inc. | | 26 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 188 | -x---- | UUNET Technologies, Inc. | | 27 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 169 | x-- | UUNET Technologies, Inc. | | 28 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 191 | x----- | UUNET Technologies, Inc. | | 29 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 179 | x--- | UUNET Technologies, Inc. | | 30 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 188 | -x---- | UUNET Technologies, Inc. | | 31 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 179 | -x-- | UUNET Technologies, Inc. | | 32 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 163 | x | UUNET Technologies, Inc. | | 33 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 184 | -x- | UUNET Technologies, Inc. | | 34 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 168 | -x | UUNET Technologies, Inc. | | 35 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 166 | -x | UUNET Technologies, Inc. | | 36 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 185 | -x- | UUNET Technologies, Inc. | | 37 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 161 | -x | UUNET Technologies, Inc. | | 38 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 210 | --x | UUNET Technologies, Inc. | | 39 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 152 | -x | UUNET Technologies, Inc. | | 40 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 167 | -x | UUNET Technologies, Inc. | | 41 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 176 | -x | UUNET Technologies, Inc. | | 42 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 164 | x | UUNET Technologies, Inc. | | 43 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 173 | x | UUNET Technologies, Inc. | | 44 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 158 | -x | UUNET Technologies, Inc. | | 45 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 168 | x | UUNET Technologies, Inc. | | 46 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 166 | x | UUNET Technologies, Inc. | | 47 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 159 | x | UUNET Technologies, Inc. | | 48 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 140 | x- | UUNET Technologies, Inc. | | 49 | 60 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 145 | x- | UUNET Technologies, Inc. | | 50 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 170 | -x | UUNET Technologies, Inc. | | 51 | 70 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 137 | x- | UUNET Technologies, Inc. | | 52 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 133 | x- | UUNET Technologies, Inc. | | 53 | 60 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 142 | x- | UUNET Technologies, Inc. | | 54 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 147 | x- | UUNET Technologies, Inc. | | 55 | 60 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 143 | x- | UUNET Technologies, Inc. | | 56 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 156 | -x | UUNET Technologies, Inc. | | 57 | 60 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 167 | -x | UUNET Technologies, Inc. | | 58 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 167 | -x | UUNET Technologies, Inc. | | 59 | 60 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 170 | -x | UUNET Technologies, Inc. | | 60 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 174 | -x | UUNET Technologies, Inc. | | 61 | 70 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 173 | -x | UUNET Technologies, Inc. | | 62 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 178 | -x | UUNET Technologies, Inc. | | 63 | 60 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 186 | -x | UUNET Technologies, Inc. | | 64 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 183 | x- | UUNET Technologies, Inc. | | ... | | | | | | | | | | ? | | 162.33.138.132 | online.mmsi-usa.com | ?Woodbridge, NJ 07095 | | | | RAM Communications Consultants, Inc. | ------------------------------------------------------------------------ ------------------------------------------------------------------------ ----------------------------- Roundtrip time to 65.195.230.218, average = 183ms, min = 152ms, max = 210ms -- 12-Apr-02 3:04:18 PM Bradley Corner Northeast Florida Multiple Listing Service, Inc. 7801 Deecreek Club Rd Ste 1 Jacksonville FL 32217 (904) 394-9494

4 3

RE: UUNET service
by Borchers, Mark 12 Apr '02

12 Apr '02

A thought-provoking issue to be sure, but it is already chronicled in the Archives of NANOG. > Also sprach jlewis(a)lewis.org > >To me, that looks more like an outage (now fixed) on a customer > >network. The 'loop' between 500.Serial2-11.GW4.BWI1.ALTER.NET and > >core62007-gw.customer.alter.net, could likely be caused by UU's > >customer advertising an aggregate route to UU, but not > actually having > >a route to the IP...so they default back to UU, and UU sends > it back to > >the customer. > > That was my thought when I saw the (mangled) traceroute. > > >This was likely a problem on the customer's network, so why should > >UUNet take a trouble report from you? > > This is a really crappy attitude...but its one I hear from a lot of > Internet providers, and that I frequently hear from telco's > too. I make > the argument that its *not* in the provider's best interest > to take this > attitude. > > Basically, what you are saying is that you really don't care of your > network actually *works* or not. > > I'll take a credible trouble report about my network from > anyone. (Note > the use of the term "credible" there) If my network is operating in > some sub-standard way, I want to know about it, and I don't care of I > find out about it from a customer or from some random person halfway > around the globe. > > To be quite honest, the mindset of "You're not our customer, I won't > take your report about our network being screwed up," boggles my mind. > > Like I said...I get the same attitude from telco's (particularly > BellSouth that I deal with a lot), and it blows my mind. > BellSouth has > *NO* way for me, as someone that deals with the PSTN a *LOT*, and has > the ability to correlate reports of problems and determine where there > are likely significant problems, to report problems to them > because "I'm > not the customer." They would rather calls not be completely > than to be > pointed to where their network is broken by a non-customer. Where is > the logic in that? The most recent example of this was that we were > having customer from 2 CO's (actually, one CO and one remote node off > that CO) that were unable to complete ISDN data calls to us. It took > BellSouth over 3 days to fix this when they could've had it fixed in > less than 2 hours if they had just taken my trouble report. > > I can even extend this to equipment vendors. I've had more than one > equipment vendor that refused to take a bug report from me (even a > blatent security vulnerability in one case!) because I didn't have a > support contract. > > *blink* > > I'm doing your work for you, and you refuse to accept my gift of my > troubleshooting time and effort. > > > So...in this case with uu.net. Take the report, it takes about 2 > seconds to come to the conclusion that we have here. That being, this > is likely a customer with a default pointed back...nothing we can do > about. Then you dump the report in the circular file and go > about your > merry way. > -- > Jeff McAdams Email: jeffm(a)iglou.com > Head Network Administrator Voice: (502) 966-3848 > IgLou Internet Services (800) 436-4456 >

1 0

Washington --> New Jersey problem?? (fwd)
by doug＠safeport.com 12 Apr '02

12 Apr '02

I can not communicate with a client in New Jersey. traceroute to 68.37.47.199 (68.37.47.199), 64 hops max, 40 byte packets 1 safeport (204.156.12.1) 2.719 ms 1.989 ms 2.379 ms 2 209.70.214.197 (209.70.214.197) 22.066 ms 12.234 ms 32.890 ms 3 ge-6-0.r00.mclnva02.us.bb.verio.net (129.250.30.161) 30.560 ms 32.956 ms 40.688 ms 4 p4-4-0-0.r02.mclnva02.us.bb.verio.net (129.250.5.250) 38.828 ms 31.111 ms 18.621 ms 5 p16-6-0-0.r02.asbnva01.us.bb.verio.net (129.250.2.181) 16.315 ms 24.823 ms 25.398 ms 6 verio-gw.wswdc.ip.att.net (192.205.32.209) 44.775 ms 29.096 ms 34.562 ms 7 gbr4-p50.wswdc.ip.att.net (12.123.9.54) 14.349 ms 20.566 ms 73.020 ms 8 gbr2-p20.phlpa.ip.att.net (12.122.2.86) 55.108 ms 65.419 ms 24.909 ms 9 * gar1-p370.phlpa.ip.att.net (12.123.137.25) 45.046 ms 16.430 ms 10 * * * 11 68.39.224.165 (68.39.224.165) 114.784 ms 101.466 ms 31.370 ms 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * This is a known problem? Anyone with any information? _____ Douglas Denault doug(a)safeport.com Voice: 301-469-8766 Fax: 301-469-0601

1 0

Good & resonably priced bandwidth provider in Las Vegas for trade-show connectivity?
by Michael L. Barrow 12 Apr '02

12 Apr '02

Does anyone have any pointers or recommendations for a provider in Las Vegas, NV, US that can do trade-show connectivity of about 6 to 10Mbps? I'm having a bear of a time finding one. So far, folks want me to sign a 1 year contract or wants to rape me on the price. Send email to me personally so as not to froach the list.... Thanks! -- Michael L. Barrow <michael(a)mlbarrow.com> P: 805-566-0885

1 0