Charles,
It's unclear what you mean by your response "Nope. It dies before amprgw.ucsd.edu". Your trace is not using port 80/tcp. As my trace shows - using 80/tcp and not ICMP or UDP as other tools such as 'tracert', I'm able to reach AMPRGW thru to my HTTP server 44.60.44.10 from numerous ISP and cell networks.
I agree that it seems ingressing ICMP and UDP are having issues (and all egressing traffic), but I'm attempting to note that 80/tcp is working. Have you tested the HTTP links to 44.60.44.10 a normal cellular phone data connection, your, home ISP, etc.?
--- - Lynwood
On Friday, April 5, 2024 at 10:21:12 PM EDT, Charles Hargrove via 44net 44net@mailman.ampr.org wrote:
Nope. It dies before amprgw.ucsd.edu.
Microsoft Windows [Version 10.0.19045.4170] (c) Microsoft Corporation. All rights reserved.
C:\Users\n2nov>tracert 44.68.41.1
Tracing route to n2nov.ampr.org [44.68.41.1] over a maximum of 30 hops:
3 lag-53.nycrnydf01h.netops.charter.com [68.173.201.236] 4 lag-131.nyclnyrg01r.netops.charter.com [68.173.197.0] 5 lag-29.nwrknjmd67w-bcr00.netops.charter.com [107.14.19.24] 6 lag-20.nycmny837aw-bcr00.netops.charter.com [66.109.5.138] 7 lag-12.chcgildt87w-bcr00.netops.charter.com [66.109.6.25] 8 lag-11.snvacaid17w-bcr00.netops.charter.com [66.109.6.14] 9 lag-11.snjucacl67w-bcr00.netops.charter.com [66.109.6.8] 10 lag-0.pr1.sjc10.netops.charter.com [66.109.5.133] 11 eqix-sv5.cenic.com [206.223.117.118] 12 dc-svl-agg8--svl-agg10-300g.cenic.net [137.164.11.81] 13 dc-lax-agg8--svl-agg8--100ge--2.cenic.net [137.164.11.20] 14 dc-tus-agg8--lax-agg8-300g.cenic.net [137.164.11.83] 15 sand1-agg-01--tus-agg8--300g--01.cenic.net [137.164.11.85] 16 ucsd--sand1-agg-01--100g--01.cenic.net [137.164.23.177] 17 nodem-core-6807-vlan2767-gw.ucsd.edu [132.239.254.61] 18 sdsc-7710-7--mcore-vl2995-p2p.ucsd.edu [132.239.255.50] 19 Request timed out. 20 Request timed out. 21 Request timed out. 22 Request timed out. 23 Request timed out. 24 Request timed out. 25 Request timed out. 26 Request timed out. 27 Request timed out. 28 Request timed out. 29 Request timed out. 30 Request timed out.
Trace complete.
C:\Users\n2nov>
On 4/5/2024 10:06 PM, lleachii@aol.com wrote:
All,
I observed something interesting. I'm still able to access my web server 44.60.44.10 from a client on the Public Internet.
* http://whatismyip.ampr.org http://whatismyip.ampr.org/ * http://kb3vwg-010.ampr.org http://kb3vwg-010.ampr.org * http://44.60.44.10 http://44.60.44.10
Despite that, like others I also cannot initiate traffic from my AMPRLAN to the Internet - the trace stops at my AMPR router. Another user mentioned an issue the other day, I tested and was still able to use a normal client PC/laptop to browse the Internet - I cannot do so any longer.
Using the software My Traceroute (mtr) and selecting port 80/tcp yielded results. The following trace is from the ISP Cogent Communications (the first hops removed for privacy).
`mtr 44.60.44.10 -T -P 80`
7. be4109.agr22.dca01.atlas.cogentco.com be4108.agr21.dca01.atlas.cogentco.com 8. be3311.ccr42.dca01.atlas.cogentco.com be3309.ccr41.dca01.atlas.cogentco.com be3308.ccr41.dca01.atlas.cogentco.com be3310.ccr42.dca01.atlas.cogentco.com 9. be3084.ccr41.iad02.atlas.cogentco.com be3083.ccr41.iad02.atlas.cogentco.com 10. ae-6.edge1.WashingtonDC111.Level3.net 11. (waiting for reply) 12. CENIC.ear1.LosAngeles1.Level3.net 13. dc-lax-agg8--lax-agg10-300g.cenic.net 14. dc-tus-agg8--lax-agg8-300g.cenic.net 15. sand1-agg-01--tus-agg8--300g--01.cenic.net 16. ucsd--sand1-agg-01--100g--01.cenic.net 17. nodem-core-6807-vlan2767-gw.ucsd.edu 18. sdsc-7710-7--mcore-vl2995-p2p.ucsd.edu 19. amprgw.ucsd.edu 20. (waiting for reply) #this hop should be my router-firewalled 21. kb3vwg-010.ampr.org
73,
Lynwood KB3VWG