OK, someone's apparently been messing with the HamWAN routing table again ... traceroute to 44.225.56.72 (44.225.56.72), 30 hops max, 38 byte packets 1 5shpn-1_dmz (192.168.44.254) 0.436 ms 0.259 ms 0.253 ms 2 dhcp-44-24-240-161.paine-s2.hamwan.net (44.24.240.161) 54.989 ms 50.222 ms 4.484 ms 3 ptp2-shoreline.paine.hamwan.net (44.24.240.135) 4.955 ms 4.338 ms 4.001 ms 4 w0.paine.k7nvh.hamwan.net (44.24.242.11) 62.214 ms 21.459 ms 51.757 ms 5 ipip1.seattle-er1.hamwan.net (44.24.242.16) 877.546 ms 360.904 ms 113.455 ms 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * *
We're sending packets out properly, but my guess is they're not returning properly. Do you have any information / control over that remote site's routing? --Bart On 6/11/2014 5:19 PM, Dean Gibson AE7Q wrote:
OK, someone's apparently been messing with the HamWAN routing table again ...
traceroute to 44.225.56.72 (44.225.56.72), 30 hops max, 38 byte packets 1 5shpn-1_dmz (192.168.44.254) 0.436 ms 0.259 ms 0.253 ms 2 dhcp-44-24-240-161.paine-s2.hamwan.net (44.24.240.161) 54.989 ms 50.222 ms 4.484 ms 3 ptp2-shoreline.paine.hamwan.net (44.24.240.135) 4.955 ms 4.338 ms 4.001 ms 4 w0.paine.k7nvh.hamwan.net (44.24.242.11) 62.214 ms 21.459 ms 51.757 ms 5 ipip1.seattle-er1.hamwan.net (44.24.242.16) 877.546 ms 360.904 ms 113.455 ms 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * *
_______________________________________________ PSDR mailing list PSDR@hamwan.org http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org
I should have mentioned, it's not just that site. Here's a partial list of ampr.org sites I can't get a reply from: http://web.db0avh.ampr.org/ http://db0dah.ampr.org/ http://db0eeo.ampr.org/ http://db0res-svr.ampr.org/ http://44.225.56.72/cms25 http://srv.db0lj.ampr.org/ It may not be at the HamWAN end of things, but if it is more general than HamWAN, I'm surprised there's not been a fuss on 44net. There's no urgency on my need to connect, but since a day had gone by without it being fixed, I thought it was worth mentioning ... On 2014-06-12 02:11, Bart Kus wrote:
We're sending packets out properly, but my guess is they're not returning properly. Do you have any information / control over that remote site's routing?
--Bart
On 6/11/2014 5:19 PM, Dean Gibson AE7Q wrote:
OK, someone's apparently been messing with the HamWAN routing table again ...
traceroute to 44.225.56.72 (44.225.56.72), 30 hops max, 38 byte packets 1 5shpn-1_dmz (192.168.44.254) 0.436 ms 0.259 ms 0.253 ms 2 dhcp-44-24-240-161.paine-s2.hamwan.net (44.24.240.161) 54.989 ms 50.222 ms 4.484 ms 3 ptp2-shoreline.paine.hamwan.net (44.24.240.135) 4.955 ms 4.338 ms 4.001 ms 4 w0.paine.k7nvh.hamwan.net (44.24.242.11) 62.214 ms 21.459 ms 51.757 ms 5 ipip1.seattle-er1.hamwan.net (44.24.242.16) 877.546 ms 360.904 ms 113.455 ms 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * *
_______________________________________________ PSDR mailing list PSDR@hamwan.org http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org
_______________________________________________ PSDR mailing list PSDR@hamwan.org http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org
It looks like the AMPR encap file doesn't have a route to us, so they can't route back. I'm not sure why this went away, but this is under EO_'s AMPR portal account, so we'll have to wait for him to re-add it. Nigel K7NVH
participants (3)
-
Bart Kus -
Dean Gibson AE7Q -
Nigel Vander Houwen