Hello mhirse, you mean using filtering traceroute? Then why it seems to show that as if boucing it? I was told once that traceroute required each router on the way to KNOW something whereas ping does not. I just can not recall what this something is and I am intend to find out. Any takers? tatsuya いつもお世話になっております かわさき@ giganetです。 かわさき = = = = = = 電話 03-3239-0607 fax 03-3239-2609 business network telecom http://www.giganet.net On Mon, 9 Mar 1998 mhirse@UU.NET wrote:

They seem to using access-list on their gateway routers. That would explain your problem.

Mohamed

Dear nanog,

could someone explain to me why I can ping but traceroute seems to have problem reaching it.

i.e. ping -s auth3.ipass.com. 64 bytes from holmes.ipass.com (204.198.128.102): icmp_seq=0. time=352. ms

yet traceroute

... 6 s2/2-decker-hi.digisle.net (167.216.156.57) 147 ms 149 ms 148 ms 7 s2/2-decker-hi.digisle.net (167.216.156.57) 205 ms * 147 ms 8 * s2/2-decker-hi.digisle.net (167.216.156.57) 152 ms * 9 s2/2-decker-hi.digisle.net (167.216.156.57) 148 ms * 159 ms 10 * s2/2-decker-hi.digisle.net (167.216.156.57) 148 ms * 11 s2/2-decker-hi.digisle.net (167.216.156.57) 177 ms * 161 ms ...

thnx in adv.

tatsuya

= = = = = = BEEOCB 03-3239-0607 fax 03-3239-2609 business network telecom http://www.giganet.net