ons.
Thanks,
John
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jonathan
Crawford
Sent: Friday, November 16, 2007 10:08 AM
To: 'Tim Durack'; 'Cisco-nsp'
Subject: Re: [c-nsp] Level3/Cogent/HVDataNet specific routing problem
-looki
/Cogent/HVDataNet specific routing problem - looking
for suggestions
Having difficulties with routing through a Level3 circuit:
Traceroute using 67.99.58.158 source address:
RTR-3#traceroute 38.102.194.142
Type escape sequence to abort.
Tracing the route to
: Re: [c-nsp] Level3/Cogent/HVDataNet specific routing problem -
looking for suggestions
We get transit from Level3. I was hoping if I manipulate the right
community I could influence the Level3/Cogent peering making Cogent
less preferred.
Tim:>
On Nov 16, 2007 2:03 PM, Jonathan Crawford <
gt;
> -Jonathan
>
> -Original Message-
> From: Tim Durack [mailto:[EMAIL PROTECTED]
> Sent: Friday, November 16, 2007 10:27 AM
> To: Jonathan Crawford
> Cc: Cisco-nsp
> Subject: Re: [c-nsp] Level3/Cogent/HVDataNet specific routing problem -
> looking for suggest
them and get the
same effect.
-Jonathan
-Original Message-
From: Tim Durack [mailto:[EMAIL PROTECTED]
Sent: Friday, November 16, 2007 10:27 AM
To: Jonathan Crawford
Cc: Cisco-nsp
Subject: Re: [c-nsp] Level3/Cogent/HVDataNet specific routing problem -
looking for suggestions
I was hoping
On Nov 16, 2007 1:07 PM, Jonathan Crawford <[EMAIL PROTECTED]> wrote:
> The prepeding should have nothing to do with your lack of connectivity
> through Cogent. All the prepending would do is possibly make another route
> look more desireable due to the as-path. They already append their ASN when
>
Having difficulties with routing through a Level3 circuit:
Traceroute using 67.99.58.158 source address:
RTR-3#traceroute 38.102.194.142
Type escape sequence to abort.
Tracing the route to HudsonValleyDataNet.demarc.cogentco.com (38.102.194.142)
1 67.99.58.157 [AS 6395] 8 msec 4 msec 4 msec