Hi Richard,
I was surprised that each node AMPR-Net should have a complete and updated map of the network routing. And I asked about what kind of network topology is now.
just replayed by Marius.
By the way, in my opinion, JNOS too, in a sense, the "stone age". Well, or "bronze". I guess now no one uses AX.25 or NETROM.
The AX.25, the Netrom, and even the Rose are currently used by ham community nowadays together with the Flexnet, INP3 etc.; and the actual JNOS2 was improved enough by featuring the B1F and the B2F compression protocols, the INP3 and several packet drivers too; furthermore it can speak to linux machine by means the 'tun0' tunnel and through the very improved AXIP/AXUDP methods allowing a full operation (as for my concerns) to any ham site operating with a dynamic IP address! :)
Why for routing of tunnels used very specific daemon, which duplicate the functionality of the operating system? (It I about JNOS.)
Owning a commercial IP address, the actual JNOS2 is able, per se, to automatically catch the ucsd RIP2 broadcast and manage them by the venerable standard 'encap' interface and so automatically manage the *encap routes* without any other external daemon... TNX to Maiko.
Linux and rip44d daemons make the same things allowing the dynamic IP address owners to participate to the 44-net mesh: TNX to Heikki/Hessu and Marius for their good jobs!
Why spend so much each user forces on obtaining technical information, which only need a router of backbone? (It I about file encap.txt and his updating through a variety of extraordinary ways.)
Replyed by Marius, too
73, gus i0ojj