Did go through last time:

        -----Original Message----- 
        From: CHUNIKHIN Igor FTLD 
        Sent: Sun 2/1/2004 6:18 PM 
        To: '[EMAIL PROTECTED]'; Sean Donelan 
        Cc: [EMAIL PROTECTED] 
        Subject: RE: Did Wanadoo, French ISP, block access to SCO?
        
        

        Let me clarify: 

        1) Wanadoo is French domestic network, while Opentransit is international 
backbone. 
        2) Opentransit (AS 5511) didn't block www.sco.com. Your traceroute goes via 
Opentransit but dies on peering point with XO; it looks like they killed this host.


        Cheers, 
        Igor Chunikhin 
        Engineering Support Lead Engineer 
        FTLD IPTAC 
        +1 703 375 6154 (office) 


        > -----Original Message----- 
        > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of 
        > James Edwards 
        > Sent: Sunday, February 01, 2004 4:21 PM 
        > To: Sean Donelan 
        > Cc: [EMAIL PROTECTED] 
        > Subject: Re: Did Wanadoo, French ISP, block access to SCO? 
        > 
        > 
        > Here is a view from the west coast,  This is via 
        > Opentransit, which is my limited understanding of French 
        > indicates is owned/part of FranceTelecom: 
        > 
        > trace 216.250.128.12 
        > 
        > Type escape sequence to abort. 
        > Tracing the route to www.sco.com (216.250.128.12) 
        > 
        >   1 P12-0.PALBB2.Palo-alto.opentransit.net (193.251.240.26) 0 msec 0 
        > msec 0 msec 
        >   2  *  * 
        >     p5-0.IR1.PaloAlto-CA.us.xo.net (207.88.250.29) [AS 2828] !H 
        > 
        > >From Pastourelle, via Opentransit: 
        > 
        > trace 216.250.128.12 
        > 
        > Type escape sequence to abort. 
        > Tracing the route to www.sco.com (216.250.128.12) 
        > 
        >   1 P12-0.NYKCR3.New-york.opentransit.net (193.251.241.134) 144 msec 216 
        > msec 212 msec 
        >   2 P7-0.NYKBB3.New-york.opentransit.net (193.251.241.242) 76 msec 76 msec 
        > 76 msec 
        >   3  *  *  * 
        > 
        > 
        > 
        > 

Reply via email to