[j-nsp] Route Precedence

Chris lists at blackhat.bz
Wed Jul 13 02:35:20 EDT 2011


On 13/07/2011 2:27 PM, Chris wrote:
> <snip>
>
To add to the already long email, here is some more examples of whats
happening:

>From the 10.10.10.100 device, trying to ping the 'acc-bdr1' (J6350)
device works:

traceroute to 99.99.99.242 (99.99.99.242), 30 hops max, 40 byte packets
 1  10.10.10.254 (10.10.10.254)  0.996 ms  0.699 ms  0.66 ms
 2  99.99.99.242 (99.99.99.242)  1.928 ms  1.589 ms  1.978 ms

Yet if I try it from a device that I CANT ping from acc-bdr1 (the source
being 10.10.10.30):

[root at acc-nx4cs ~]# traceroute -n 99.99.99.242
traceroute to 99.99.99.242 (99.99.99.242), 30 hops max, 40 byte packets
 1  10.10.10.254  4.021 ms  3.981 ms  3.958 ms
 2  * * *
 3  * * *
 4  * * *

It's like something is filtering certain IP's from getting out but the
config doesn't have anything like that in it so it has me stumped.

Any help is much appreciated!

Thanks


More information about the juniper-nsp mailing list