Re: [44net] RIP44... v 2???

Just to be the critic here... How do you know which peers to contact for elections if you do not have the list yet? Where do you get the peer list from if there is no designated acting AMPRGW yet? The IP protocol has (almost) no way to create a common media access channel to exchange data without knowing your peers first. So you still need the portal. And with such acting GWs... There has to be a gateway on the internet for 44.0.0.0/24 through which any external source could access any resource on 44net. That means that if that gateway changes, there has to be a BGP update in the global internet BGP table so that every router in the world would know the route. And this takes time. And at some point, half the public internet knows agout one gateway, the other half about another one. And that new gateway is probably in another AS. Which complicates things. So let me have my doubt about such dynamic gateway assignments from an external point of view. And from the internal one: Most hams have a hard time setting up our current IPIP implementation. Now let's assume they have to setup dynamic gatewaying in addition to that... Just to circumvent a possible gateway failure, which only manifests itself as the inability of non-ham users accessing a 44net ham resource. (And for important resources, we can always host them on BGP announced subnets if it is really necessary). I wonder if this is worth the effort. I would rather try to secure the portal and concentrate on a secondary RIP source. AMPRGW is not the weak spot. Missing RIP/encap updates is. Marius, YO2LOJ -----Original Message----- From: lleachii--- via 44Net Sent: Saturday, March 26, 2016 17:26 To: 44net(a)hamradio.ucsd.edu Cc: lleachii(a)aol.com Subject: [44net] RIP44... v 2??? (Please trim inclusions from previous messages) _______________________________________________ All, I considered that since we: - have a full mesh - and all those who use RIP44 will have a TRUE copy of all routes Perhaps consider ways that RIP44 could be updated: - to bootstrap one another in the case of a failure of AMPRGW (election of a master to send RIP44 announcements, participation in elections disabled by default) - allow possibility for addition of routes while 'acting AMPRGW' is offline (re-elections with time-stamping/flagging)? - ability to resume normal operations (AMPRGW is automatically elected/flagged/timestamps-recognized as master/signals send end of elections) Ideas? - KB3VWG _________________________________________ 44Net mailing list 44Net(a)hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net