Marius,
1.) 44.60.44.10 was offline for about 60 minutes prior to this
email, that should have been verifiable by not being able to reach
the HTTP website. As I noted before, ping/traceroute my router at
44.60.44.1, as it should be online at all times. At this time, the
HTTP site is up, and 44.60.44.10 SHOULD be pingable on AMPR and the
Public Internet.
2.) We discussed this matter twice before; we are aware that we
cannot ping each other. Again, there was no resolution on your part.
I noted in previous weeks that some hosts on AMPR cannot be pinged,
I resolved that matter with all other stations, except yourself. I
last asked what Network Operating System are you using, I do not
recall your response being provided.
3.) I provide http://44.60.44.10/tools for the pruposes of having
users test and verify the same occurs at my station as theirs.
4.)
PING ve3zda.ampr.org (44.135.90.2) 56(84) bytes of data.
64 bytes from ve3zda.ampr.org (44.135.90.2): icmp_req=1 ttl=253
time=61.6 ms
64 bytes from ve3zda.ampr.org (44.135.90.2): icmp_req=2 ttl=253
time=60.3 ms
64 bytes from ve3zda.ampr.org (44.135.90.2): icmp_req=3 ttl=253
time=64.3 ms
64 bytes from ve3zda.ampr.org (44.135.90.2): icmp_req=4 ttl=253
time=65.7 ms
--- ve3zda.ampr.org ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 60.324/63.002/65.782/2.160 ms
5.) stecat.ampr.org and brklyn.ampr.org are invalid hostnames (I
also host a DNS Server at 44.60.44.3).
- Lynwood