Excelent question, Bryan.
IMHO the fact that not everybody can BGP announce their subnets could be a reason. In that case you can not differentiate between legitimate ampr traffic to your network and public traffic, since the access to your subnet has to be done via public IPs. But as long as you don't offer any network services which are specific for to the non-BGP announced ham community, there is not needed to support the mesh network. Your network is in this case just another IP range on the internet.
73s de Marius, YO2LOJ
-----Original Message----- From: 44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of Bryan Fields Sent: Friday, June 12, 2015 18:22 To: AMPRNet working group Subject: Re: [44net] Strange Broadcasts... ______________________________________________ On 6/12/15 11:06 AM, Marc, LX1DUC wrote:
I do think that regardless of the OS it is much more important that anybody using 44net addresses shall support the IPIP mesh
Why?
I announce subnets via BGP, that should be enough. I maintain the single end point for the 44 network (UCSD gw) is a bad idea, and it's not my fault it has broken routing for more specific networks.
-- Bryan Fields