[afnog] connection to www.cnn.com

[Mikisa Richard]

Geert Jan de Groot wrote:

>I can't traceroute back to 41.220.0.4, from here the last hop that works
>seems to be the remote end of a sat link:
>
>traceroute to 41.220.0.4 from 147.28.0.62, 64 hops max, 40 byte packets
>....
> 9  144.232.8.98  44.930 ms  47.414 ms  44.937 ms
>10  213.248.80.154  66.801 ms 213.248.80.74  67.271 ms  66.921 ms
>11  213.248.64.21  165.221 ms 213.248.82.102  164.101 ms 213.248.64.21  164.609 ms
>12  213.248.65.10  164.218 ms 213.248.65.18  163.975 ms 213.248.65.10  163.733 ms
>13  213.248.97.90  177.968 ms  181.594 ms  177.850 ms
>14  217.212.242.2  713.645 ms  709.773 ms  707.533 ms
>15  * * *
>16  * * *
>17  * *
>
>Are you perhaps filtering ICMP messages, breaking PMTU discovery?
>  
>
41.220.0.4 is indeed filtering ICMP, please use 41.220.0.254 for 
connectivity tests. No filters on that.

>If you can ping anything close (like the previous hop), try pinging
>with large packets (8K+) and see if the responses get back to you.
>
>Geert Jan
>  
>
 From 41.220.0.254 ..

name# ping -s 8000 217.212.242.1
PING 217.212.242.1 (217.212.242.1): 8000 data bytes
8008 bytes from 217.212.242.1: icmp_seq=0 ttl=254 time=545.556 ms
8008 bytes from 217.212.242.1: icmp_seq=1 ttl=254 time=543.763 ms
8008 bytes from 217.212.242.1: icmp_seq=2 ttl=254 time=543.201 ms
8008 bytes from 217.212.242.1: icmp_seq=3 ttl=254 time=542.284 ms
8008 bytes from 217.212.242.1: icmp_seq=4 ttl=254 time=546.402 ms
8008 bytes from 217.212.242.1: icmp_seq=5 ttl=254 time=545.922 ms
8008 bytes from 217.212.242.1: icmp_seq=6 ttl=254 time=542.686 ms         

-- 
Richard