Merit Network
Can't find what you're looking for? Search the Mail Archives.
  About Merit   Services   Network   Resources & Support   Network Research   News   Events   Home

Discussion Communities: Merit Network Email List Archives

North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

RE: UUnet routing "problem"

  • From: Christopher L. Morrow
  • Date: Thu Sep 26 15:24:14 2002

If the owner of the ip address would like to contact the UUNET NOC in EU
and ask for: Mr. Beechey he can connect you with the person attempting to
contact you about this.

--Chris
(chris@uu.net)
#######################################################
## UUNET Technologies, Inc.                          ##
## Manager                                           ##
## Customer Router Security Engineering Team         ##
## (W)703-886-3823 (C)703-338-7319                   ##
#######################################################

On Thu, 26 Sep 2002, Michael Hallgren wrote:

>
> .ro -- try their London or Amsterdam guys. In an earlier life --
> Teleglobe -- I
> found them quite responsive (at least EU daytime :).
>
> Cheers
>
> mh
>
> -----Message d'origine-----
> De : owner-nanog@merit.edu [mailto:owner-nanog@merit.edu]De la part de
> Sorin Constantinescu
> Envoye : jeudi 26 septembre 2002 20:21
> A : dies
> Cc : nanog@merit.edu; tech@rdsnet.ro
> Objet : Re: UUnet routing "problem"
>
>
>
>
>
> Yes, we did. The e-mail was addressed to noc@uu.net and abuse@uu.net. We
> also called at  1-800-900-0241 option 2 3 1. All we got was some ticket
> numbers.
>
> Bye,
>
> On Thu, 26 Sep 2002, dies wrote:
>
> > Date: Thu, 26 Sep 2002 14:06:50 -0400 (EDT)
> > From: dies <dies@pulltheplug.com>
> > To: Sorin CONSTANTINESCU <adonay@rdsnet.ro>
> > Cc: nanog@merit.edu, tech@rdsnet.ro
> > Subject: Re: UUnet routing "problem"
> >
> >
> >
> >
> > Have you contacted 701?
> >
> >
> > On Thu, 26 Sep 2002, Sorin CONSTANTINESCU wrote:
> >
> > >
> > >
> > > Hi,
> > >
> > > This morning we've discovered that one of our IP's was routed somewhere
> > > towards an ALTER.NET customer.
> > >
> > > All the "experiments" i'm going to show you are done from
> > > route-server.exodus.net.
> > >
> > > a show ip bgp 193.231.236.41 show that the originator of the IP Block
> from
> > > where 193.231.236.41 belongs is AS8708 (RDSNET ROMANIA).
> > >
> > > BGP routing table entry for 193.231.224.0/20, version 4439795
> > > Paths: (8 available, best #1)
> > >   Not advertised to any peer
> > >   3561 701 702 8708, (aggregated by 8708 193.231.191.33)
> > >     209.1.40.63 from 209.1.40.63 (209.1.40.63)
> > >       Origin IGP, localpref 1000, valid, internal, atomic-aggregate,
> best
> > >   3561 701 702 8708, (aggregated by 8708 193.231.191.33)
> > >     209.1.40.129 from 209.1.40.129 (209.1.40.129)
> > >       Origin IGP, localpref 1000, valid, internal, atomic-aggregate
> > >   3561 701 702 8708, (aggregated by 8708 193.231.191.33)
> > >     209.1.220.242 from 209.1.220.242 (209.1.220.242)
> > >       Origin IGP, localpref 1000, valid, internal, atomic-aggregate
> > >   3561 701 702 8708, (aggregated by 8708 193.231.191.33)
> > >     209.1.220.134 from 209.1.220.134 (209.1.220.134)
> > >       Origin IGP, localpref 1000, valid, internal, atomic-aggregate
> > >   3561 701 702 8708, (aggregated by 8708 193.231.191.33)
> > >     209.1.40.141 from 209.1.40.141 (209.1.40.141)
> > >       Origin IGP, localpref 1000, valid, internal, atomic-aggregate
> > >   3561 701 702 8708, (aggregated by 8708 193.231.191.33)
> > >     209.1.220.7 from 209.1.220.7 (209.1.220.7)
> > >       Origin IGP, localpref 1000, valid, internal, atomic-aggregate
> > >   3561 701 702 8708, (aggregated by 8708 193.231.191.33)
> > >     209.1.220.7 from 209.1.220.84 (209.1.220.7)
> > >
> > > But, somewhere on the way,
> > >
> > > route-server.exodus.net>tr 193.231.236.41
> > >
> > > Type escape sequence to abort.
> > > Tracing the route to FuckingLiveShow.home.ro (193.231.236.41)
> > >
> > >   1 dcr01-p0-1.sntc08.exodus.net (209.1.169.182) 0 msec 0 msec 0 msec
> > >   2 ibr01-g0-0.sntc08.exodus.net (66.35.194.197) 0 msec 0 msec 0 msec
> > >   3 dcr2-so-3-0-0.SantaClara.cw.net (208.172.156.197) [AS 3561] 0 msec 0
> > > msec 4 msec
> > >   4 agr3-so-2-0-0.SantaClara.cw.net (208.172.156.138) [AS 3561] 4 msec
> > >     agr4-so-6-0-0.SantaClara.cw.net (208.172.156.158) [AS 3561] 0 msec
> > >     agr3-so-2-0-0.SantaClara.cw.net (208.172.156.138) [AS 3561] 4 msec
> > >   5 acr1-loopback.SanFrancisco.cw.net (206.24.210.61) [AS 3561] 4 msec 4
> > > msec 4 msec
> > >   6 bpr2.SanJoseEquinix.cw.net (206.24.210.27) [AS 3561] 4 msec 4 msec 8
> > > msec
> > >   7 cable-and-wireless-peering.SanJoseEquinix.cw.net (208.173.55.2) [AS
> > > 3561] 4 msec
> > >     cable-and-wireless-peering.SanJoseEquinix.cw.net (208.173.55.46) [AS
> > > 3561] 224 msec
> > >     cable-and-wireless-peering.SanJoseEquinix.cw.net (208.173.55.2) [AS
> > > 3561] 4 msec
> > >   8 POS2-0.XR2.SJC7.ALTER.NET (152.63.56.166) [AS 701] 8 msec 4 msec 4
> > > msec
> > >   9 POS5-0.XR2.SJC1.ALTER.NET (152.63.52.141) [AS 701] 8 msec 4 msec 4
> > > msec
> > >  10 0.so-0-0-0.XL2.SJC1.ALTER.NET (152.63.55.126) [AS 701] 8 msec 4 msec
> 4
> > > msec
> > >  11 0.so-3-0-0.TL2.SAC1.ALTER.NET (152.63.54.10) [AS 701] 8 msec 8 msec
> 8
> > > msec
> > >  12 0.so-4-0-0.TL2.DCA6.ALTER.NET (152.63.10.61) [AS 701] 84 msec 84
> msec
> > > 84 msec
> > >  13 0.so-6-0-0.XL2.DCA6.ALTER.NET (152.63.38.74) [AS 701] 88 msec 88
> msec
> > > 88 msec
> > >  14 0.so-7-0-0.XR2.DCA6.ALTER.NET (152.63.38.90) [AS 701] 88 msec 88
> msec
> > > 88 msec
> > >  15 284.at-2-0-0.CL2.IAD5.ALTER.NET (152.63.35.58) [AS 701] 88 msec 88
> > > msec 92 msec
> > >  16 501.ATM5-0.GW5.IAD5.ALTER.NET (152.63.43.141) [AS 701] 92 msec 92
> msec
> > > 88 msec
> > >  17 xa-gw2.customer.alter.net (157.130.13.70) [AS 701] 120 msec 92 msec
> 92
> > > msec
> > >  18 s1.home.ro (193.231.236.41) [AS 8708] 92 msec 92 msec 92
> > > msec
> > > route-server.exodus.net>
> > >
> > > Has anyone ever experienced this kind of problems? We've written to
> UUNET
> > > Europe, and they've answered to us that it's a problem at UUNET USA.
> It's
> > > been almost 8 hours since they replied to us, but the problem persists.
> > >
> > >
> > > PS: If there are any technicians from UUNET on this list, please give us
> > > a hand.
> > >
> > > Thank you,
> > > ---
> > > Sorin Constantinescu				Tel: +402 13 010 850
> > > Network Administrator				Fax: +402 13 010 892
> > > RDS Bucharest					Email: adonay@rdsnet.ro
> > >
> > > Privileged/Confidential Information may be contained in this message. If
> > > you are not the addressee indicated in this message (or responsible for
> > > delivery of the message to such person), you may not copy or deliver
> this
> > > message to anyone. In such a case, you should destroy this message and
> > > kindly notify the sender by reply e-mail.
> > >
> > >
> >
> >
>
>
>
>
> ---
> Sorin Constantinescu				Tel: +402 13 010 850
> Network Administrator				Fax: +402 13 010 892
> RDS Bucharest					Email: adonay@rdsnet.ro
>
> Privileged/Confidential Information may be contained in this message. If
> you are not the addressee indicated in this message (or responsible for
> delivery of the message to such person), you may not copy or deliver this
> message to anyone. In such a case, you should destroy this message and
> kindly notify the sender by reply e-mail.
>
>
>






Discussion Communities


About Merit | Services | Network | Resources & Support | Network Research
News | Events | Contact | Site Map | Merit Network Home


Merit Network, Inc.