24 Jan
2020
24 Jan
'20
11:47 a.m.
Hi,
Just been looking through https://gw.ampr.org/private/pkterrors.txt and I noticed
there's entries for the external IP for the net I run.
I'm running 44.131.170.0/30 with a RaspberryPi on 44.131.170.1 using IPIP with amprd,
external IP address 90.155.50.1
The errors are like:
90.155.50.1 51.89.173.198 2 [19] dropped: non-44 inner source address
What does this mean? And I can't seem to ping to 44.131.170.1 from the big bad
internet, is this related?
Thanks. Bill (M1BKF)
24 Jan
24 Jan
7:34 p.m.
Bill,
What does your start script with your ip routes and ip rules look
like? Something is wrong in there. What Lynwood said, that error
means a non-44 ip is leaking over your tunnel. And the ucsd router is
dropping it (a good thing)
Can you get a reply ping from 44.92.21.50?
This is a host of mine that is only reachable via an amprnet tunnel
And 44.92.21.35 should be reachable from everywhere
Feel free to use either for testing.
Steve
On Fri, Jan 24, 2020 at 10:49 AM W.B.Hill via 44Net
<44net(a)mailman.ampr.org> wrote:
Hi,
Just been looking through https://gw.ampr.org/private/pkterrors.txt and I noticed
there's entries for the external IP for the net I run.
I'm running 44.131.170.0/30 with a RaspberryPi on 44.131.170.1 using IPIP with amprd,
external IP address 90.155.50.1
The errors are like:
90.155.50.1 51.89.173.198 2 [19] dropped: non-44 inner source address
What does this mean? And I can't seem to ping to 44.131.170.1 from the big bad
internet, is this related?
Thanks. Bill (M1BKF)
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
25 Jan
25 Jan
10:09 a.m.
On 25/01/2020 00:34, Steve L via 44Net wrote:
Bill,
What does your start script with your ip routes and ip rules look
like? Something is wrong in there. What Lynwood said, that error
means a non-44 ip is leaking over your tunnel. And the ucsd router is
dropping it (a good thing)
Hi, Thanks for looking. Here's my startup:
#!/bin/sh
/usr/local/sbin/amprd
sleep 15
iptables -A INPUT -iampr0 -ptcp --dport 22 -j ACCEPT
iptables -A INPUT -iampr0 -ptcp --dport 80 -j ACCEPT
iptables -A INPUT -iampr0 -ptcp --dport 119 -j ACCEPT
iptables -A INPUT -iampr0 -picmp -j ACCEPT
iptables -A INPUT -iampr0 -j DROP
exit 0
And the /etc/amprd.conf:
[ampr0]
prefix = 44.131.170.1
rip_receive = yes
rip_save = yes
rip_password =
rip_ignore = 90.155.50.1
call_home = M1BKF@JO02pp
Can you get a reply ping from 44.92.21.50?
This is a host of mine that is only reachable via an amprnet tunnel
And 44.92.21.35 should be reachable from everywhere
The interface, ifconfig ampr0:
ampr0: flags=4291<UP,BROADCAST,RUNNING,NOARP,MULTICAST> mtu 1500
inet 44.131.170.1 netmask 255.0.0.0 broadcast 44.255.255.255
inet6 fe80::9061:b6ff:fe6e:dfe prefixlen 64 scopeid 0x20<link>
ether 92:61:b6:6e:0d:fe txqueuelen 1000 (Ethernet)
RX packets 332930 bytes 112896180 (107.6 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 75117 bytes 5880354 (5.6 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Some pings:
ping -c3 -Iampr0 44.92.21.50
PING 44.92.21.50 (44.92.21.50) from 44.131.170.1 ampr0: 56(84) bytes of data.
--- 44.92.21.50 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2042ms
ping -c3 -Iampr0 44.92.21.35
PING 44.92.21.35 (44.92.21.35) from 44.131.170.1 ampr0: 56(84) bytes of data.
--- 44.92.21.35 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2080ms
ping -c3 -Ieth0 44.92.21.35
PING 44.92.21.35 (44.92.21.35) from 192.168.1.2 eth0: 56(84) bytes of data.
64 bytes from 44.92.21.35: icmp_seq=1 ttl=51 time=211 ms
64 bytes from 44.92.21.35: icmp_seq=2 ttl=51 time=211 ms
64 bytes from 44.92.21.35: icmp_seq=3 ttl=51 time=213 ms
--- 44.92.21.35 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 211.747/212.304/213.251/0.673 ms
ping -c3 -Iampr0 44.0.0.1
PING 44.0.0.1 (44.0.0.1) from 44.131.170.1 ampr0: 56(84) bytes of data.
64 bytes from 44.0.0.1: icmp_seq=1 ttl=62 time=145 ms
64 bytes from 44.0.0.1: icmp_seq=2 ttl=62 time=145 ms
64 bytes from 44.0.0.1: icmp_seq=3 ttl=62 time=145 ms
--- 44.0.0.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 145.258/145.636/145.984/0.531 ms
And the routing:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
44.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 ampr0
44.94.17.129 192.168.1.1 255.255.255.255 UGH 0 0 0 eth0
44.130.104.1 192.168.1.1 255.255.255.255 UGH 0 0 0 eth0
44.130.105.1 192.168.1.1 255.255.255.255 UGH 0 0 0 eth0
44.130.106.1 192.168.1.1 255.255.255.255 UGH 0 0 0 eth0
44.130.107.1 192.168.1.1 255.255.255.255 UGH 0 0 0 eth0
vk4aa.ampr.org 192.168.1.1 255.255.255.255 UGH 0 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
So something's not right, and I thought this was working!
Bill (M1BKF)
26 Jan
26 Jan
5:20 p.m.
Bill,
Regarding you not being able to ping 44.92.21.1 and 44.92.21.50...
The issue seems on the way to the gateway.
I tried ping/trace from my VPS (44.182.21.1) and it seems the gateway
(174.97.191.155) is not reachable:
root@vps62907:~# traceroute 174.97.191.155
traceroute to 174.97.191.155 (174.97.191.155), 30 hops max, 60 byte packets
1 89.33.44.1 (89.33.44.1) 0.129 ms 0.111 ms 0.192 ms
2 95.77.57.97 (95.77.57.97) 0.828 ms 0.823 ms 0.737 ms
3 ro-cj01a-rd3-ae-32-1851.aorta.net (84.116.187.77) 130.540 ms
130.552 ms 130.580 ms
4 de-fra02a-rc1-ae-12-0.aorta.net (84.116.131.53) 129.618 ms 129.685
ms 129.714 ms
5 de-fra01b-rc1-ae-22-0.aorta.net (84.116.135.62) 129.667 ms 146.609
ms 129.493 ms
6 nl-ams17b-rc1-lag-105-0.aorta.net (84.116.130.65) 129.345 ms
129.501 ms 129.472 ms
7 us-was02a-rd2-ae-105-0.aorta.net (84.116.130.66) 130.719 ms
130.662 ms 130.640 ms
8 us-was03a-ri1-ae-10-0.aorta.net (84.116.130.174) 130.236 ms
130.216 ms 130.253 ms
9 0.xe-3-3-1.pr0.dca10.tbone.rr.com (66.109.10.165) 140.730 ms
140.710 ms 140.686 ms
10 66.109.5.116 (66.109.5.116) 168.129 ms 168.321 ms 166.389 ms
11 0.ae3.pr1.dfw10.tbone.rr.com (107.14.17.238) 163.621 ms 163.577 ms
165.298 ms
12 bu-ether12.nycmny837aw-bcr00.tbone.rr.com (66.109.6.27) 168.383 ms
66.109.5.138 (66.109.5.138) 164.618 ms
bu-ether12.nycmny837aw-bcr00.tbone.rr.com (66.109.6.27) 161.270 ms
13 so-0-0-0.ar1.cdp01.tbone.rr.com (66.109.6.95) 167.257 ms
bu-ether12.chcgildt87w-bcr00.tbone.rr.com (66.109.6.25) 165.039 ms
so-0-0-0.ar1.cdp01.tbone.rr.com (66.109.6.95) 162.215 ms
14 66.109.6.205 (66.109.6.205) 166.387 ms 169.953 ms 167.213 ms
15 ae1.deprwi0202h.midwest.rr.com (65.31.112.171) 172.566 ms 172.342
ms 172.296 ms
16 ae2.deprwi0205m.new.rr.com (24.164.240.246) 168.233 ms 168.332 ms
168.390 ms
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
So maybe the problem is not on your side.
Marius, YO2LOJ
On 25.01.2020 17:09, W.B.Hill via 44Net wrote:
On 25/01/2020 00:34, Steve L via 44Net wrote:
Bill,
What does your start script with your ip routes and ip rules look
like? Something is wrong in there. What Lynwood said, that error
means a non-44 ip is leaking over your tunnel. And the ucsd router is
dropping it (a good thing)
Hi, Thanks for looking. Here's my startup:
#!/bin/sh
/usr/local/sbin/amprd
sleep 15
iptables -A INPUT -iampr0 -ptcp --dport 22 -j ACCEPT
iptables -A INPUT -iampr0 -ptcp --dport 80 -j ACCEPT
iptables -A INPUT -iampr0 -ptcp --dport 119 -j ACCEPT
iptables -A INPUT -iampr0 -picmp -j ACCEPT
iptables -A INPUT -iampr0 -j DROP
exit 0
And the /etc/amprd.conf:
[ampr0]
prefix = 44.131.170.1
rip_receive = yes
rip_save = yes
rip_password =
rip_ignore = 90.155.50.1
call_home = M1BKF@JO02pp
Can you get a reply ping from 44.92.21.50?
This is a host of mine that is only reachable via an amprnet tunnel
And 44.92.21.35 should be reachable from everywhere
The interface, ifconfig ampr0:
ampr0: flags=4291<UP,BROADCAST,RUNNING,NOARP,MULTICAST> mtu 1500
inet 44.131.170.1 netmask 255.0.0.0 broadcast 44.255.255.255
inet6 fe80::9061:b6ff:fe6e:dfe prefixlen 64 scopeid 0x20<link>
ether 92:61:b6:6e:0d:fe txqueuelen 1000 (Ethernet)
RX packets 332930 bytes 112896180 (107.6 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 75117 bytes 5880354 (5.6 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Some pings:
ping -c3 -Iampr0 44.92.21.50
PING 44.92.21.50 (44.92.21.50) from 44.131.170.1 ampr0: 56(84) bytes of data.
--- 44.92.21.50 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2042ms
ping -c3 -Iampr0 44.92.21.35
PING 44.92.21.35 (44.92.21.35) from 44.131.170.1 ampr0: 56(84) bytes of data.
--- 44.92.21.35 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2080ms
ping -c3 -Ieth0 44.92.21.35
PING 44.92.21.35 (44.92.21.35) from 192.168.1.2 eth0: 56(84) bytes of data.
64 bytes from 44.92.21.35: icmp_seq=1 ttl=51 time=211 ms
64 bytes from 44.92.21.35: icmp_seq=2 ttl=51 time=211 ms
64 bytes from 44.92.21.35: icmp_seq=3 ttl=51 time=213 ms
--- 44.92.21.35 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 211.747/212.304/213.251/0.673 ms
ping -c3 -Iampr0 44.0.0.1
PING 44.0.0.1 (44.0.0.1) from 44.131.170.1 ampr0: 56(84) bytes of data.
64 bytes from 44.0.0.1: icmp_seq=1 ttl=62 time=145 ms
64 bytes from 44.0.0.1: icmp_seq=2 ttl=62 time=145 ms
64 bytes from 44.0.0.1: icmp_seq=3 ttl=62 time=145 ms
--- 44.0.0.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 145.258/145.636/145.984/0.531 ms
And the routing:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
44.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 ampr0
44.94.17.129 192.168.1.1 255.255.255.255 UGH 0 0 0 eth0
44.130.104.1 192.168.1.1 255.255.255.255 UGH 0 0 0 eth0
44.130.105.1 192.168.1.1 255.255.255.255 UGH 0 0 0 eth0
44.130.106.1 192.168.1.1 255.255.255.255 UGH 0 0 0 eth0
44.130.107.1 192.168.1.1 255.255.255.255 UGH 0 0 0 eth0
vk4aa.ampr.org 192.168.1.1 255.255.255.255 UGH 0 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
So something's not right, and I thought this was working!
Bill (M1BKF)
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
5:25 p.m.
Additional info...
Somehow, it seems that that gateway filters out icmp responses, so it is
not clear to me where to start since it is thus untraceable.
It responds on the http port (I can see it runs CentOS), but more than
that, I don't know.
On 27.01.2020 00:20, Marius Petrescu via 44Net wrote:
Bill,
Regarding you not being able to ping 44.92.21.1 and 44.92.21.50...
The issue seems on the way to the gateway.
I tried ping/trace from my VPS (44.182.21.1) and it seems the gateway
(174.97.191.155) is not reachable:
root@vps62907:~# traceroute 174.97.191.155
traceroute to 174.97.191.155 (174.97.191.155), 30 hops max, 60 byte
packets
1 89.33.44.1 (89.33.44.1) 0.129 ms 0.111 ms 0.192 ms
2 95.77.57.97 (95.77.57.97) 0.828 ms 0.823 ms 0.737 ms
3 ro-cj01a-rd3-ae-32-1851.aorta.net (84.116.187.77) 130.540 ms
130.552 ms 130.580 ms
4 de-fra02a-rc1-ae-12-0.aorta.net (84.116.131.53) 129.618 ms
129.685 ms 129.714 ms
5 de-fra01b-rc1-ae-22-0.aorta.net (84.116.135.62) 129.667 ms
146.609 ms 129.493 ms
6 nl-ams17b-rc1-lag-105-0.aorta.net (84.116.130.65) 129.345 ms
129.501 ms 129.472 ms
7 us-was02a-rd2-ae-105-0.aorta.net (84.116.130.66) 130.719 ms
130.662 ms 130.640 ms
8 us-was03a-ri1-ae-10-0.aorta.net (84.116.130.174) 130.236 ms
130.216 ms 130.253 ms
9 0.xe-3-3-1.pr0.dca10.tbone.rr.com (66.109.10.165) 140.730 ms
140.710 ms 140.686 ms
10 66.109.5.116 (66.109.5.116) 168.129 ms 168.321 ms 166.389 ms
11 0.ae3.pr1.dfw10.tbone.rr.com (107.14.17.238) 163.621 ms 163.577
ms 165.298 ms
12 bu-ether12.nycmny837aw-bcr00.tbone.rr.com (66.109.6.27) 168.383 ms
66.109.5.138 (66.109.5.138) 164.618 ms
bu-ether12.nycmny837aw-bcr00.tbone.rr.com (66.109.6.27) 161.270 ms
13 so-0-0-0.ar1.cdp01.tbone.rr.com (66.109.6.95) 167.257 ms
bu-ether12.chcgildt87w-bcr00.tbone.rr.com (66.109.6.25) 165.039 ms
so-0-0-0.ar1.cdp01.tbone.rr.com (66.109.6.95) 162.215 ms
14 66.109.6.205 (66.109.6.205) 166.387 ms 169.953 ms 167.213 ms
15 ae1.deprwi0202h.midwest.rr.com (65.31.112.171) 172.566 ms 172.342
ms 172.296 ms
16 ae2.deprwi0205m.new.rr.com (24.164.240.246) 168.233 ms 168.332
ms 168.390 ms
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
So maybe the problem is not on your side.
Marius, YO2LOJ
On 25.01.2020 17:09, W.B.Hill via 44Net wrote:
On 25/01/2020 00:34, Steve L via 44Net wrote:
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net Bill,
What does your start script with your ip routes and ip rules look
like? Something is wrong in there. What Lynwood said, that error
means a non-44 ip is leaking over your tunnel. And the ucsd router is
dropping it (a good thing)
Hi, Thanks for looking. Here's my startup:
#!/bin/sh
/usr/local/sbin/amprd
sleep 15
iptables -A INPUT -iampr0 -ptcp --dport 22 -j ACCEPT
iptables -A INPUT -iampr0 -ptcp --dport 80 -j ACCEPT
iptables -A INPUT -iampr0 -ptcp --dport 119 -j ACCEPT
iptables -A INPUT -iampr0 -picmp -j ACCEPT
iptables -A INPUT -iampr0 -j DROP
exit 0
And the /etc/amprd.conf:
[ampr0]
prefix = 44.131.170.1
rip_receive = yes
rip_save = yes
rip_password =
rip_ignore = 90.155.50.1
call_home = M1BKF@JO02pp
Can you get a reply ping from 44.92.21.50?
This is a host of mine that is only reachable via an amprnet tunnel
And 44.92.21.35 should be reachable from everywhere
The interface, ifconfig ampr0:
ampr0: flags=4291<UP,BROADCAST,RUNNING,NOARP,MULTICAST> mtu 1500
inet 44.131.170.1 netmask 255.0.0.0 broadcast 44.255.255.255
inet6 fe80::9061:b6ff:fe6e:dfe prefixlen 64 scopeid
0x20<link>
ether 92:61:b6:6e:0d:fe txqueuelen 1000 (Ethernet)
RX packets 332930 bytes 112896180 (107.6 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 75117 bytes 5880354 (5.6 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Some pings:
ping -c3 -Iampr0 44.92.21.50
PING 44.92.21.50 (44.92.21.50) from 44.131.170.1 ampr0: 56(84) bytes
of data.
--- 44.92.21.50 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2042ms
ping -c3 -Iampr0 44.92.21.35
PING 44.92.21.35 (44.92.21.35) from 44.131.170.1 ampr0: 56(84) bytes
of data.
--- 44.92.21.35 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2080ms
ping -c3 -Ieth0 44.92.21.35
PING 44.92.21.35 (44.92.21.35) from 192.168.1.2 eth0: 56(84) bytes of
data.
64 bytes from 44.92.21.35: icmp_seq=1 ttl=51 time=211 ms
64 bytes from 44.92.21.35: icmp_seq=2 ttl=51 time=211 ms
64 bytes from 44.92.21.35: icmp_seq=3 ttl=51 time=213 ms
--- 44.92.21.35 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 211.747/212.304/213.251/0.673 ms
ping -c3 -Iampr0 44.0.0.1
PING 44.0.0.1 (44.0.0.1) from 44.131.170.1 ampr0: 56(84) bytes of data.
64 bytes from 44.0.0.1: icmp_seq=1 ttl=62 time=145 ms
64 bytes from 44.0.0.1: icmp_seq=2 ttl=62 time=145 ms
64 bytes from 44.0.0.1: icmp_seq=3 ttl=62 time=145 ms
--- 44.0.0.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 145.258/145.636/145.984/0.531 ms
And the routing:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref
Use Iface
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
44.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 ampr0
44.94.17.129 192.168.1.1 255.255.255.255 UGH 0 0 0 eth0
44.130.104.1 192.168.1.1 255.255.255.255 UGH 0 0 0 eth0
44.130.105.1 192.168.1.1 255.255.255.255 UGH 0 0 0 eth0
44.130.106.1 192.168.1.1 255.255.255.255 UGH 0 0 0 eth0
44.130.107.1 192.168.1.1 255.255.255.255 UGH 0 0 0 eth0
vk4aa.ampr.org 192.168.1.1 255.255.255.255 UGH 0 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
So something's not right, and I thought this was working!
Bill (M1BKF)
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
10:56 p.m.
Sorry guys, I swapped out some gear not long ago, and I can see it has
that nice keep-alive socket bug (self closing) when forwarding
protocol 4.
I have now reconfigured, and I'd like to think everything here should
be reachable again (i.e. 44.92.21.1, 44.92.21.50 and 44.92.21.35)
Steve, KB9MWR
On Sun, Jan 26, 2020 at 4:27 PM Marius Petrescu via 44Net
<44net(a)mailman.ampr.org> wrote:
Additional info...
Somehow, it seems that that gateway filters out icmp responses, so it is
not clear to me where to start since it is thus untraceable.
It responds on the http port (I can see it runs CentOS), but more than
that, I don't know.
On 27.01.2020 00:20, Marius Petrescu via 44Net wrote:
> Bill,
>
> Regarding you not being able to ping 44.92.21.1 and 44.92.21.50...
>
> The issue seems on the way to the gateway.
>
> I tried ping/trace from my VPS (44.182.21.1) and it seems the gateway
> (174.97.191.155) is not reachable:
>
> root@vps62907:~# traceroute 174.97.191.155
> traceroute to 174.97.191.155 (174.97.191.155), 30 hops max, 60 byte
> packets
> 1 89.33.44.1 (89.33.44.1) 0.129 ms 0.111 ms 0.192 ms
> 2 95.77.57.97 (95.77.57.97) 0.828 ms 0.823 ms 0.737 ms
> 3 ro-cj01a-rd3-ae-32-1851.aorta.net (84.116.187.77) 130.540 ms
> 130.552 ms 130.580 ms
> 4 de-fra02a-rc1-ae-12-0.aorta.net (84.116.131.53) 129.618 ms
> 129.685 ms 129.714 ms
> 5 de-fra01b-rc1-ae-22-0.aorta.net (84.116.135.62) 129.667 ms
> 146.609 ms 129.493 ms
> 6 nl-ams17b-rc1-lag-105-0.aorta.net (84.116.130.65) 129.345 ms
> 129.501 ms 129.472 ms
> 7 us-was02a-rd2-ae-105-0.aorta.net (84.116.130.66) 130.719 ms
> 130.662 ms 130.640 ms
> 8 us-was03a-ri1-ae-10-0.aorta.net (84.116.130.174) 130.236 ms
> 130.216 ms 130.253 ms
> 9 0.xe-3-3-1.pr0.dca10.tbone.rr.com (66.109.10.165) 140.730 ms
> 140.710 ms 140.686 ms
> 10 66.109.5.116 (66.109.5.116) 168.129 ms 168.321 ms 166.389 ms
> 11 0.ae3.pr1.dfw10.tbone.rr.com (107.14.17.238) 163.621 ms 163.577
> ms 165.298 ms
> 12 bu-ether12.nycmny837aw-bcr00.tbone.rr.com (66.109.6.27) 168.383 ms
> 66.109.5.138 (66.109.5.138) 164.618 ms
> bu-ether12.nycmny837aw-bcr00.tbone.rr.com (66.109.6.27) 161.270 ms
> 13 so-0-0-0.ar1.cdp01.tbone.rr.com (66.109.6.95) 167.257 ms
> bu-ether12.chcgildt87w-bcr00.tbone.rr.com (66.109.6.25) 165.039 ms
> so-0-0-0.ar1.cdp01.tbone.rr.com (66.109.6.95) 162.215 ms
> 14 66.109.6.205 (66.109.6.205) 166.387 ms 169.953 ms 167.213 ms
> 15 ae1.deprwi0202h.midwest.rr.com (65.31.112.171) 172.566 ms 172.342
> ms 172.296 ms
> 16 ae2.deprwi0205m.new.rr.com (24.164.240.246) 168.233 ms 168.332
> ms 168.390 ms
> 17 * * *
> 18 * * *
> 19 * * *
> 20 * * *
> 21 * * *
> 22 * * *
> 23 * * *
> 24 * * *
> 25 * * *
> 26 * * *
> 27 * * *
> 28 * * *
> 29 * * *
> 30 * * *
>
> So maybe the problem is not on your side.
>
> Marius, YO2LOJ
27 Jan
27 Jan
6:45 a.m.
On 27/01/2020 03:56, Steve L via 44Net wrote:
I have now reconfigured, and I'd like to think
everything here should
be reachable again (i.e. 44.92.21.1, 44.92.21.50 and 44.92.21.35)
Steve, KB9MWR
Just to confirm, all three IPs are ping-able from 44.131.170.1
Bill (M1BKF)
9:39 a.m.
Can ping 44.92.21.1 and 44.92.21.35
All packets lost for 44.92.21.50
From 107.203.196.169
Eloy
On Jan 26, 2020, at 10:56 PM, Steve L via 44Net
<44net(a)mailman.ampr.org> wrote:
Sorry guys, I swapped out some gear not long ago, and I can see it has
that nice keep-alive socket bug (self closing) when forwarding
protocol 4.
I have now reconfigured, and I'd like to think everything here should
be reachable again (i.e. 44.92.21.1, 44.92.21.50 and 44.92.21.35)
Steve, KB9MWR
On Sun, Jan 26, 2020 at 4:27 PM Marius Petrescu via 44Net
<44net(a)mailman.ampr.org> wrote:
11:50 a.m.
44.92.21.50 has no DNS entry, and thus is only reachable from a 44.x address.
On Mon, Jan 27, 2020 at 8:40 AM eritter via 44Net
<44net(a)mailman.ampr.org> wrote:
Can ping 44.92.21.1 and 44.92.21.35
All packets lost for 44.92.21.50
From 107.203.196.169
Eloy
On Jan 26, 2020, at 10:56 PM, Steve L via 44Net
<44net(a)mailman.ampr.org> wrote:
Sorry guys, I swapped out some gear not long ago, and I can see it has
that nice keep-alive socket bug (self closing) when forwarding
protocol 4.
I have now reconfigured, and I'd like to think everything here should
be reachable again (i.e. 44.92.21.1, 44.92.21.50 and 44.92.21.35)
Steve, KB9MWR
On Sun, Jan 26, 2020 at 4:27 PM Marius Petrescu via 44Net
<44net(a)mailman.ampr.org> wrote:
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
1572
days inactive
1575
days old
8 comments
4 participants
participants (4)
-
eritter -
Marius Petrescu -
Steve L -
W.B.Hill