Rob;
n1uro@n1uro.ampr.org:/uronode$ ping pe1chl
ICMP Echo request sent to: 44.137.40.1
ICMP Echo reply received from: 44.137.40.1
Ping completed in: 113ms (ttl=62)
n1uro@n1uro.ampr.org:/uronode$ tra
Executing command...
what IP or HOSTName do you wish to trace? pe1chl
Please wait while we trace to pe1chl...
traceroute to pe1chl (44.137.40.1), 30 hops max, 60 byte packets
1
gw.ct.ampr.org (44.88.0.1) 7.411 ms 7.762 ms 7.758 ms
2
sys2.pe1chl.ampr.org (44.137.40.2) 115.385 ms 116.427 ms 122.728
ms
3
pe1chl.ampr.org (44.137.40.1) 126.044 ms 128.015 ms 129.829 ms
Tracing complete.
URONode tracer v1.3 - TraceRoute utility by N1URO.
Goodbye.
Returning you to the shell...
n1uro@n1uro.ampr.org:/uronode$
Seems to work for me fine.
On Mon, 2015-08-03 at 21:08 +0200, Rob Janssen wrote:
> (Please trim inclusions from previous messages)
> _______________________________________________
> > Subject:
> > Re: [44net] New Linux Boot Scripts for Testing
> > From:
> > "Marius Petrescu" <marius(a)yo2loj.ro>
> > Date:
> > 08/03/2015 01:45 PM
> >
> > To:
> > "'AMPRNet working group'" <44net(a)hamradio.ucsd.edu>
> >
> >
> > Ok. It seems I got that wrong.
> > Actually there is no reply via tunnel. I can ping your system only via the
> > public internet.
> >
> > Marius
>
> Same for me, Marius!
> I did (just as for N1URO) detailed tracing of the network traffic and although there
is outgoing encapsulated IPIP
> traffic to his advertised gateway, there is no reply whatsoever.
>
> It is still unclear to me if there is some problem with the operation of the network,
or a systematic bug in the
> scripts that some people use. This time I thought I could download a script and
have a look, maybe I see
> some problem, but I cannot access the site from any address I tried... :-(
>
> Rob
>