On Mon, 2013-12-23 at 15:32 +0000, John Wiseman wrote:
I'm planning to add support for the gateway to my BPQ32/LinBPQ ax.25 node software, but after searching the web, I can't find any info on how the Amprnet Gateway handles dynamic dns.
LinBPQ handles 44-net fine as it is now with the exception of how it handles ARP from what I see. Windows however is a totally different story all it's own. There is no native ip protocol 4 support in windows. XRouter/XR32 claim to handle it, but I have yet to see it work properly. You may want to consider a pseudo nic for Windows for ipencap (similar to linux's tunl0 interface) to handle this. It may also be a can of worms you may not want to open.
Does the gateway re-resolve each hostname before sending out each rip44 update? Or is the name just resolved to an address when it is added to the portal?
I believe hourly, however Chris and/or Brian Kantor can verify.
Is there any mechanism for uses to send RIP messages back to the gateway when their addresses change?
When the gateway is configured properly in the portal, there's no need to send RIP back. The portal will do the hostname resolutions prior to building a new encap.txt and rip table.
Is it possible to get a version of encap.txt that lists hoatnames instead of IP addresses, so uses can resolve them themselves?
If there's a need for users to resolve dynamic commerical IPs themselves, then something is wrong with the user's config. Just like with a phone, internet routes via a series of numbers. A hostname is for human-use moreso than for routing. If we were to eliminate DNS online, i don't think ampr.org would have any routing but 44/8 does.