Belows IP's belong to SR3BBS gateway which _IS OFF LINE_ for a long time!
Then why is it in the table?
Maybe it should again be considered to add a mandatory field to a gateway registration with a net-44 IP that should be pingable via the tunnel (e.g. the IP of the gateway itself) and run some very infrequent ping to that address from a monitoring system that is also on the tunnel network (not amprgw as some people apparently choose not to tunnel to that system).
When e.g. one ping per hour is made and nothing is heard for 7 days or even more, the gateway can be marked down and removed from the encap.txt and RIP broadcast. The operator can then re-enable it via the portal.
Rob
Rob.
You're perfectly right. Such entry (gateway) is just useless _PLACEHOLDER_
Best regards.
FYI: my station only acknowledges 44. stations included in the encap.txt files and so if this comes to fruition the station doing the pinging will need to be included in that file.
73. Don - ve3zda
On Tue, Apr 25, 2017 at 5:13 AM SP2L SP2L@wp.pl wrote:
(Please trim inclusions from previous messages) _______________________________________________ Rob.
You're perfectly right. Such entry (gateway) is just useless _PLACEHOLDER_
Best regards.
-- Tom - SP2L
It is nice to be important. But it is more important to be nice!
On 25/04/17 11:04, Rob Janssen wrote:
Then why is it in the table?
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net