Dean,
I've just tried a traceroute from the cell at Paine, and it looks like it's connecting through ok. It's possible that something was funny with the IPIP tunnel, though I haven't changed anything there, so I'd guess it would be on the remote end. If it's continuing to not work for you, then something funny is going on.
[nigel@Paine-s2] > /tool traceroute 44.225.56.72
# ADDRESS LOSS SENT LAST AVG BEST WORST STD-DEV STATUS
1 44.24.240.136 0% 70 0.3ms 0.4 0.3 1.7 0.2
2 44.24.242.7 0% 70 39.1ms 22.5 3 69.6 16.9
3 44.24.242.8 0% 70 84.6ms 68.9 36.5 183.1 28
44.24.242.4
4 44.130.60.100 0% 70 232.3ms 237.7 204.9 800.1 240
5 44.130.60.101 1.4% 70 221.3ms 236.5 203.1 342.3 234
6 44.224.2.5 0% 70 245ms 247.9 216.9 359.2 249.1
7 44.224.2.18 1.4% 70 266.5ms 252.6 218.2 575.3 240.4
8 44.224.53.158 0% 69 220.2ms 252.3 220.1 364.3 252.5
9 44.224.24.59 0% 69 247.4ms 263.9 231 390.8 252.7
10 44.225.56.72 0% 69 276.8ms 263.8 226 383.8 253
On Mar 28, 2014, at 8:08 AM, Dean Gibson AE7Q <hamwan@ae7q.net> wrote:
I currently can't connect to ANY in the list (someone else gave me as valid) below. Previously (about a week ago), I only tried a few in the list below, but those connected. A DNS lookup today on a few of them, returns an address in the 44 block, so I doubt it's DNS.
Here's a "traceroute" to 44.225.56.72 (in the list below):
traceroute to 44.225.56.72 (44.225.56.72), 30 hops max, 38 byte packets
1 5shpn-1_ext (192.168.3.251) 0.437 ms 0.255 ms 0.237 ms
2 44.24.240.161 (44.24.240.161) 56.927 ms 66.802 ms 10.479 ms
3 44.24.240.136 (44.24.240.136) 5.019 ms 26.476 ms 8.432 ms
4 44.24.242.7 (44.24.242.7) 37.010 ms 31.064 ms 8.447 ms
5 44.24.242.4 (44.24.242.4) 49.188 ms 64.406 ms 51.113 ms
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
On 2014-03-27 22:29, Nigel Vander Houwen wrote:
Can you give an example of something you were trying to access that's giving you issues?
Nigel K7NVH
On Mar 27, 2014, at 9:30 PM, Dean Gibson AE7Q
<hamwan@ae7q.net>
wrote:
Today I tried to access a number of 44.x.x.x/8 web sites that I was perfectly able to access a week ago, but cannot tonight. A "traceroute" shows that these accesses are leaving the 44.x.x.x/8 network and coming back in at UCSD. That of course could explain what is happening.
http://web.db0avh.ampr.org
http://db0bi.ampr.org
http://db0dah.ampr.org
http://db0eeo.ampr.org
http://db0end.ampr.org
http://db0fhn.ampr.org
http://db0res-svr.ampr.org
http://db0gos.ampr.org
http://db0dz.ampr.org
http://db0ii.ampr.org
http://db0iuz.ampr.org
http://44.225.56.72/cms25
http://db0kwe.ampr.org
http://srv.db0lj.ampr.org
http://db0nis.ampr.org
http://db0ovn.ampr.org
http://44.225.60.2
http://db0sda.ampr.org
http://db0ach.ampr.org
http://db0pra.ampr.org
http://websrv.db0pdf.ampr.org
http://db0wet.ampr.org
http://db0ham.ampr.org
http://44.143.10.90
http://web.oe2xzr.at.ampr.org
http://dm0ha.ampr.org
http://dm0zgw.ampr.org
http://db0erf.ampr.org
http://web.oe5xbl.at.ampr.org
http://web.oe7xci.ampr.at
http://44.168.12.11
http://server.db0anf.ampr.org
http://www.db0fuz.ampr.org
http://linux.db0zeh.ampr.org
http://monitor.db0mhb.ampr.org
http://db0bul.ampr.org
http://rpt.db0pob.ampr.org
http://db0kpg.ampr.org
http://db0lip.ampr.org
http://44.225.76.161
http://db0zdf-srv01.db0zdf.ampr.org
http://raspberry.db0abz.ampr.org
http://db0fc.ampr.org
http://cloud.db0fc.ampr.org
http://db0oha.ampr.org
http://dk0mav.ampr.org