So, until Dynamic DNS (or similar) is implemented, the dynamic address could have a fixed (but not personally identifiable) DNS name. It could be related to the station that is offering up the dynamic address. (The DHCP addresses in my home network work this way.)
This is another reason that more automation is needed, not just for simplifying registration, but for enabling more advanced technology - ham radio isn't about 'standing still'.
A maxim at my $WORK is that "Those who dislike change are *really* going to detest irrelevancy."
To say that change is hard, therefore we shouldn't do it - I have to say: change is necessary, therefore we *must* do it - or be replaced.
For the mesh network being developed for the NW Digital radios, we're moving to IPv6 - the 44 net becomes awkward to interface with - unless it modernises. It would be useful to use 44 net addresses for IPv4 for interconnect, but that's only going to be practical if the current system is willing to adapt.
BTW - I wrote the front end code for the world's first TNC - I'm not adverse to new technology or change. ;-)
- Richard, VE7CVS
On 1/17/16 12:22 PM, R P wrote:
The problem of dynamic address is that in order to pass the 44 Net Router you need too have a DNS name and the AMPR.ORG dns have no system of DHCP update or any kind of "quick" update so the whole business is irrelevant until such a system will be implemented Rone - 4Z4ZQ http://www.ronen.org