Thanks Brian. I have no trouble getting to other 44 gateways via my tunnel including yours (after loading routes from encap.txt via ampr-ripd) so it's not a case of protocol 4 being blocked by my vdsl modem. Since last night I've logged over 10,000 ipip connections on my gateway - just nothing from amprgw.
I was expecting to get a form letter response from my service provider's helpdesk when I asked, but to my surprise it was escalated to their network engineering team who appear to have actually investigated before responding.
Testing from http://kb3vwg-010.ampr.org/tools/trace/php-trace44.php shows that my tunnel is reachable:
traceroute to 44.136.24.60 (44.136.24.60), 30 hops max, 60 byte packets 1 kb3vwg-001.ampr.org (44.60.44.1) 0.999 ms 1.021 ms 1.148 ms 2 vk2hff.ampr.org (44.136.24.60) 525.972 ms 548.696 ms 572.350 ms
Also from http://yo2tm.ampr.org/nettools.php:
traceroute to 44.136.24.60 (44.136.24.60), 30 hops max, 60 byte packets 1 router.yo2loj.ampr.org (44.182.21.254) 0.279 ms 2 net.vk2hff.ampr.org (44.136.24.60) 687.700 ms
I've tried connecting to a random selection of the gateways that had recently checked in to yo2tm's map and no issues there either.
Josh - VK2HFF
On 16/06/2017 11:25 AM, Brian wrote:
Josh;
On Fri, 2017-06-16 at 10:40 +1000, Josh wrote:
I've now confirmed with my service provider that they are not blocking traffic either to or from amprgw. About 12 hours ago I started logging inbound ipip connections on my wan interface, but so far have seen nothing from 169.228.34.84.
You may want to read my white page about being bitten by the dog. ISPs will *never* grant you the integrity of admitting to what they're doing as they feel it's not a customer's business what the ISP does on the ISPs network.
This is slowly becoming an epidemic globally with ISPs deploying CPEs with faulty firmware... deliberately. There are alternatives and tests to see if you are bitten. Considering you're having issues you may not be able to see the document but it's at: https://n1uro.ampr.org/linuxconf/amprcable.html
73 de Brian - N1URO/AFT1BR email: (see above) Web: http://www.n1uro.net/ Ampr1: http://n1uro.ampr.org/ Ampr2: http://nos.n1uro.ampr.org Linux Amateur Radio Services axMail-Fax & URONode http://uronode.sourceforge.net http://axmail.sourceforge.net AmprNet coordinator for: Connecticut, Delaware, Maine, Maryland, Massachusetts, New Hampshire, New Jersey, Pennsylvania, Rhode Island, and Vermont.