Re: [44net] Portal API: ampr routing based on portal info

Michael, You are right about that single point of failure. Now about the gateway - that was an unfortunate fire incident, which could affect any system with the same probability (which is low I would say). What I thougt was that the portal is the primary source of information regarding routing/encap. Somehow it would make sense to use that. And it would allow to update on demand via a standard protocol - http/tcp in his case. It was just an idea, after using Tom Hayward's Mikrotik script (which uses the portal API) for a while, with excelent results. Marius, YO2LOJ -----Original Message----- From: 44net-bounces+marius=yo2loj.ro(a)hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of Michael Fox (N6MEF) Sent: Friday, July 24, 2015 02:56 To: 'AMPRNet working group' Subject: Re: [44net] Portal API: ampr routing based on portal info (Please trim inclusions from previous messages) _______________________________________________ Marius, I'm curious, what would be the advantage? It seems to me that you'd be trading one single point of failure for another. And from what I've seen, the RIP broadcasts have been more reliable.