North American Network Operators Group|
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical
Re: simple question as always..
Hello mhirse, (B (Byou mean using filtering traceroute? (BThen why it seems to show that as if boucing it? (B (BI was told once that traceroute required each router on the (Bway to KNOW something whereas ping does not. (BI just can not recall what this something is and I am (Bintend to find out. (BAny takers? (B (Btatsuya (B (B $B$$$D$b$*@$OC$K$J$C$F$*$j$^$9(B $B$+$o$5$-([email protected] giganet$B$G$9!#(B (B (B (B (B $B$+$o$5$-(B (B (B (B= = = = = = $BEEOC(B 03-3239-0607 fax 03-3239-2609 (Bbusiness network telecom (Bhttp://www.giganet.net (B (BOn Mon, 9 Mar 1998 [email protected] wrote: (B (B> They seem to using access-list on their gateway routers. That would (B> explain your problem. (B> (B> Mohamed (B> (B> (B> (B> Dear nanog, (B> (B> could someone explain to me why I can ping but traceroute (B> seems to have problem reaching it. (B> (B> i.e. (B> ping -s auth3.ipass.com. (B> 64 bytes from holmes.ipass.com (126.96.36.199): icmp_seq=0. time=352. ms (B> (B> yet traceroute (B> (B> ... (B> 6 s2/2-decker-hi.digisle.net (188.8.131.52) 147 ms 149 ms 148 ms (B> 7 s2/2-decker-hi.digisle.net (184.108.40.206) 205 ms * 147 ms (B> 8 * s2/2-decker-hi.digisle.net (220.127.116.11) 152 ms * (B> 9 s2/2-decker-hi.digisle.net (18.104.22.168) 148 ms * 159 ms (B> 10 * s2/2-decker-hi.digisle.net (22.214.171.124) 148 ms * (B> 11 s2/2-decker-hi.digisle.net (126.96.36.199) 177 ms * 161 ms (B> ... (B> (B> thnx in adv. (B> (B> tatsuya (B> (B> (B> = = = = = = (B> BEEOCB 03-3239-0607 fax 03-3239-2609 (B> business network telecom (B> http://www.giganet.net (B>