I'm trying to access one of Brian's help documents but the connection attempt to http://n1uro.ampr.org/linuxconf/amprnat.txt times out. Is there an issue somewhere that might impact on my attempts?
Ray vk2tv
I do not have any problem accessing http://n1uro.ampr.org/linuxconf/amprnat.txt I have attached that document for you.
On Thu, May 18, 2017 at 10:24 PM, vk2tv vk2tv@exemail.com.au wrote:
(Please trim inclusions from previous messages) _______________________________________________ I'm trying to access one of Brian's help documents but the connection attempt to http://n1uro.ampr.org/linuxconf/amprnat.txt times out. Is there an issue somewhere that might impact on my attempts?
Ray vk2tv
On Thu, May 18, 2017 at 10:27:28PM -0500, Kyle Jones, KF5JWC wrote:
I do not have any problem accessing http://n1uro.ampr.org/linuxconf/amprnat.txt I have attached that document for you.
Note that this mailing list doesn't allow attachments. It was discarded.
Please send such things directly to the requestor rather than to 500+ people on the list who didn't ask for it. - Brian
I can successfully connect to http://n1uro.ampr.org. What address are you attempting to connect from? - Brian
On Fri, May 19, 2017 at 01:24:12PM +1000, vk2tv wrote:
I'm trying to access one of Brian's help documents but the connection attempt to http://n1uro.ampr.org/linuxconf/amprnat.txt times out. Is there an issue somewhere that might impact on my attempts?
Ray vk2tv
220.233.167.221
On 19/05/17 13:28, Brian Kantor wrote:
(Please trim inclusions from previous messages) _______________________________________________ I can successfully connect to http://n1uro.ampr.org. What address are you attempting to connect from?
- Brian
Ray, I can't ping that address from amprgw. A traceroute shows that the path dies after a router at address 203.208.177.130, which is not registered. From the round trip delay on the traceroute packets, the loss is on the Pacific/Asia side of the link from the USA. It looks like there's a routing problem at one of the intermediate network nodes between here and there.
You might try a ping and a traceroute from 220.233.167.221 to 169.228.66.251 to see if you have a path. Without that path, you won't be able to reach amprgw and then in turn won't be able to connect to N1URO's site. - Brian
On Fri, May 19, 2017 at 01:36:22PM +1000, vk2tv wrote:
220.233.167.221
On 19/05/17 13:28, Brian Kantor wrote:
I can successfully connect to http://n1uro.ampr.org. What address are you attempting to connect from?
- Brian
Brian,
I've just enabled ping in my router so that might resolve the dead path issue. I can ping 169.228.66.151 with ping times of about 210mS, about normal times for the US from here.
203.208.177.130 belongs to Singtel in Singapore, and my ISP, Exetel, uses Singtel (trading as Optus in Australia) links to get to the US.
Ray vk2tv
On 19/05/17 13:45, Brian Kantor wrote:
(Please trim inclusions from previous messages) _______________________________________________ Ray, I can't ping that address from amprgw. A traceroute shows that the path dies after a router at address 203.208.177.130, which is not registered. From the round trip delay on the traceroute packets, the loss is on the Pacific/Asia side of the link from the USA. It looks like there's a routing problem at one of the intermediate network nodes between here and there.
You might try a ping and a traceroute from 220.233.167.221 to 169.228.66.251 to see if you have a path. Without that path, you won't be able to reach amprgw and then in turn won't be able to connect to N1URO's site.
- Brian
Yes, I'm now able to ping you.
You might try connecting to N1URO again. I'm able to telnet to his web port ('telnet 44.88.0.9 80') just fine so you should be able to connect and fetch that file you wanted. - Brian
On Fri, May 19, 2017 at 02:15:37PM +1000, vk2tv wrote:
I've just enabled ping in my router so that might resolve the dead path issue. I can ping 169.228.66.151 with ping times of about 210mS, about normal times for the US from here.
203.208.177.130 belongs to Singtel in Singapore, and my ISP, Exetel, uses Singtel (trading as Optus in Australia) links to get to the US.
Ray vk2tv
The connection is still failing. A traceroute gets me to ucsd ....
vk2tv@gizmo:~$ traceroute n1uro.ampr.org traceroute to n1uro.ampr.org (44.88.0.9), 30 hops max, 60 byte packets 1 192.168.1.254 (192.168.1.254) 0.501 ms 0.740 ms 1.082 ms 2 203.1.233.220.static.exetel.com.au (220.233.1.203) 32.992 ms 42.720 ms 42.707 ms 3 161.43.102.1 (161.43.102.1) 180.094 ms 180.139 ms 180.187 ms 4 * * * 5 * * * 6 * * * 7 59.154.18.24 (59.154.18.24) 147.322 ms 59.154.18.16 (59.154.18.16) 40.319 ms 59.154.18.22 (59.154.18.22) 32.862 ms 8 203.208.190.17 (203.208.190.17) 192.911 ms 203.208.190.69 (203.208.190.69) 197.681 ms 197.678 ms 9 203.208.173.138 (203.208.173.138) 202.587 ms 203.617 ms 203.208.172.234 (203.208.172.234) 204.719 ms 10 * * * 11 dc-svl-agg4--paix-px1-10g.cenic.net (137.164.47.21) 205.239 ms 210.206 ms 209.101 ms 12 dc-lax-agg6--svl-agg4-100ge.cenic.net (137.164.11.0) 212.898 ms 194.861 ms 204.845 ms 13 dc-tus-agg3--lax-agg6-100ge.cenic.net (137.164.11.7) 209.737 ms 211.968 ms 201.818 ms 14 dc-sdg-agg4--tus-agg3-100ge.cenic.net (137.164.11.9) 210.213 ms 205.401 ms 218.037 ms 15 dc-ucsd-1--sdg-agg4.cenic.net (137.164.23.54) 205.082 ms 206.745 ms 205.535 ms 16 nodem-core-6807-vlan2767-gw.ucsd.edu (132.239.254.61) 201.903 ms 205.907 ms 205.947 ms 17 ebu3b-6509-720-vlan910-gw1.ucsd.edu (132.239.255.131) 223.875 ms 223.870 ms 223.944 ms 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * vk2tv@gizmo:~$
Ray vk2tv
On 19/05/17 14:43, Brian Kantor wrote:
(Please trim inclusions from previous messages) _______________________________________________ Yes, I'm now able to ping you.
You might try connecting to N1URO again. I'm able to telnet to his web port ('telnet 44.88.0.9 80') just fine so you should be able to connect and fetch that file you wanted.
- Brian
Not to worry. I think the other Brian lurks about here, so he might chime in.
Thanks.
Ray vk2tv
On 19/05/17 15:37, Brian Kantor wrote:
(Please trim inclusions from previous messages) _______________________________________________ Well, unless N1URO has your address 220.233.167.221 blocked for some reason, I don't know what the problem is. I'm stumped. Sorry.
- Brian
-
Brian Kantor -
Kyle Jones, KF5JWC -
vk2tv