44.56.53.x is my system wa4zlw.ampr.org
44.63.63.193 is who was being asked to test :-)
ni2o.ampr.org doesnt respond on DNS FYI
73 leon
On 2/23/2023 1:19 PM, Mark Phillips via 44net wrote:
Works here at ni2o.ampr.org - Wireguard VPN to hamgatepa.ampr.org
jnos@ni2o-wayne-bbs:~ $ ping 44.56.53.1
PING 44.56.53.1 (44.56.53.1) 56(84) bytes of data.
64 bytes from 44.56.53.1: icmp_seq=1 ttl=62 time=32.9 ms
64 bytes from 44.56.53.1: icmp_seq=2 ttl=62 time=30.1 ms
64 bytes from 44.56.53.1: icmp_seq=3 ttl=62 time=32.6 ms
64 bytes from 44.56.53.1: icmp_seq=4 ttl=62 time=29.0 ms
64 bytes from 44.56.53.1: icmp_seq=5 ttl=62 time=34.8 ms
^C
--- 44.56.53.1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 28.980/31.864/34.792/2.081 ms
On Thu, Feb 23, 2023 at 12:34 PM Leon Zetekoff via 44net <44net@mailman.ampr.org> wrote:
_______________________________________________Fails from here as well
C:\>tracert 44.63.63.193
Tracing route to 44.63.63.193 over a maximum of 30 hops
1 1 ms <1 ms <1 ms t40.wa4zlw.org [10.195.10.3]
2 1 ms 1 ms 1 ms core100.wa4zlw.ampr.org [44.56.53.1]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * ^C
C:\>
73 leon wa4zlw
On 2/17/2023 8:57 PM, Boudewijn (Bob) Tenty via 44net wrote:
That address can't be reached with icmp/ping and the same
for your commercial address. Gateway is here, VE3MCH.
Bob VE3TOK
Hamilton, ON
On 2023-02-17 20:40, Harold Kinchelow via 44net wrote:
Hello all.
Could I get someone to confirm if they can reach 44.63.63.193 please.I just transitioned over to a new gateway device.
Thanks all
HaroldK7ILO
44net mailing list -- 44net@mailman.ampr.org
To unsubscribe send an email to 44net-leave@mailman.ampr.org
_______________________________________________ 44net mailing list -- 44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org
