Steve,
I agree with your suggestion, I was simply making note that all hosts are not TNOS/JNOS based (therefore Telnet is not the best option), and that there is no simple way to determine if an allocated IP is not in use, or happened to simply be offline to the Public Internet or AMPR.
DHCP would not work for one major reason, it is a Layer 2 (Ethernet) implementation. IP-in-IP is a Layer 3 (IP) connection, therefore, at least one host would have to established the tunnel with a static IP and act as a DHCP relay, defeating the purpose of a Master DHCP Server. It also assumes all devices have a compiled and installed DHCP Client, and requires each station to have a DHCP Server.
Each station is independently capable of allocating their address space as is most convenient (either static or dynamic). From Brian's perspective and that of other stations, we simply need to know the valid route to the subnet.
The AMPR Terms of Service reads:
"The duration of this license is five (5) years, renewable upon Your request and consent to these Terms and Agreement and subject to the discretion of ARDC."
Therefore, under the current rules, there is already an expiration of allocations after a period of time, so the suggestions that each Station should be responsible for maintaining their own Portal account seems to work best
- Lynwood
On 03/12/2013 04:37 PM, lleachii@aol.com wrote:
44net-request@hamradio.ucsd.edu wrote:
My belief is that systems connected to the Internet should respond to ICMP Echo Requests, it is/was in the Host Requirements RFC I think. It's also so useful in an experimental network that I would not want to turn it off.
On the other hand, I strongly believe that allocation of static IP addresses should not *automatically* depend on whether a system is switched on 24/7, nor on whether the system responds to a ping. Static addresses need to be managed manually.
If address space is scarce, allocate it dynamically. That's what DHCP is for.
Best wishes and thanks to all who keep AMPRnet alive!
G4WSZ
Steve Platt