[ale] Problem with traceroute

Michael B. Trausch mike at trausch.us
Fri Jul 25 21:45:58 EDT 2008


On Fri, 2008-07-25 at 17:29 -0400, Jim Moore wrote:
> Here is to Yahoo:
>  traceroute 66.94.234.13
> traceroute to 66.94.234.13 (66.94.234.13), 30 hops max, 40 byte
> packets
>  1  wgt624 (192.168.1.97)  2.070 ms  1.862 ms  1.791 ms
>  2  launchmodem (192.168.1.254)  2.523 ms  2.683 ms  2.920 ms
>  3  * * *
>  4  * * *
>  5  * * *
>  6  * * *
>  
> 
> Here is to GTEI.net traceroute 4.2.2.2
> traceroute to 4.2.2.2 (4.2.2.2), 30 hops max, 40 byte packets
>  1  wgt624 (192.168.1.97)  1.909 ms  1.935 ms  1.823 ms
>  2  launchmodem (192.168.1.254)  2.596 ms  3.283 ms  2.584 ms
>  3  * * *
>  4  * * *
> 

Call your ISP and tell them that you'd like an unfettered connection.
Either the modem, or their policy at the network gateway, is doing
something nuts and... wait a minute.

You don't have a public IP address?  Your gateway seems to have a
192.168 address, as does your modem.  I would leave an ISP immediately
for that kind of idiocy.  It's bad enough that IPv6 isn't an option yet
and that they're still only handing out single public IPv4 addresses,
but handing out non-routable addresses?  That's just wrong.

Almost certainly, their NAT is dropping the packets.

	--- Mike

-- 
My sigfile ran away and is on hiatus.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://mail.ale.org/pipermail/ale/attachments/20080725/5ff2eadf/attachment.bin 


More information about the Ale mailing list