20 Jan
2013
20 Jan
'13
11:41 a.m.
I don't know what to say Lynwood..
I've just tried to telnet from 12 other stations to 44.60.44.1 and got no
response from any but one and that one came back as busy.
All of the ones I tried from have not had their internet ip changed in
weeks.
It could be that 44.60.44.1 is the router and not actually any software and
that's why it's not possible to ping or telnet to it?
From my own I tried to ping from 44.60.44.1 to
44.60.44.10 and got no
response from any of them.
73, Don
On Sun, Jan 20, 2013 at 11:42 AM, <lleachii(a)aol.com> wrote:
(Please trim inclusions from previous messages)
______________________________**_________________
Charles and Don (and thanks Jerry),
Charles, I can ping you as well.
Don, I confirm I am encapsulating; but, for testing purposes, I removed
the default route - but this would imply routes are stale or absent on one
end, we all confirm that's not the case. Further, others are initiating
pings and receiving them, this would also imply that the default route
works form them, or somehow that your specific route is not being used to
reach your station.
I also want to verify that all who have contributed were noting that they
pinged 44.60.44.0/24 over AMPR. As of 16:00 UTC Sunday, I removed the
default route from my 44.60.44.1 router (for testing purposes). At that
time, I stopped receiving routes, at 16:15 UTC, I manually added:
ip route add 44.0.0.1 via 169.228.66.251 dev tunl0 onlink window 840
Routes then repopulated, I am still accessible over and can reach AMPR
stations.
73,
Lynwood
KB3VWG
______________________________**___________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/**mailman/listinfo/44net<http://hamradio.ucsd.e…
http://www.ampr.org/donate.**html <http://www.ampr.org/donate.html>