5 Apr
2024
5 Apr
'24
9:06 p.m.
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://kb3vwg-010.ampr.org
- 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.com8.
be3311.ccr42.dca01.atlas.cogentco.com be3309.ccr41.dca01.atlas.cogentco.com
be3308.ccr41.dca01.atlas.cogentco.com be3310.ccr42.dca01.atlas.cogentco.com9.
be3084.ccr41.iad02.atlas.cogentco.com be3083.ccr41.iad02.atlas.cogentco.com10.
ae-6.edge1.WashingtonDC111.Level3.net11. (waiting for reply)12.
CENIC.ear1.LosAngeles1.Level3.net13. dc-lax-agg8--lax-agg10-300g.cenic.net14.
dc-tus-agg8--lax-agg8-300g.cenic.net15. sand1-agg-01--tus-agg8--300g--01.cenic.net16.
ucsd--sand1-agg-01--100g--01.cenic.net17. nodem-core-6807-vlan2767-gw.ucsd.edu18.
sdsc-7710-7--mcore-vl2995-p2p.ucsd.edu19. amprgw.ucsd.edu20. (waiting for reply) #this hop
should be my router-firewalled21. kb3vwg-010.ampr.org
---
73,
LynwoodKB3VWG