Re: [44net] 44.192.0.0/10 sale

The problem is that the new proposal will not work as smoothly and will be much more difficult to implement when the old system is to be left in place. That is because the new system is to be using automatic routing (with BGP or maybe OSPF when others can convince my that would work better), while the old system uses manual static routing managed by the portal. service. / *you* are not supposed to be spending that money. It is to be spent by those that deploy the VPN servers. Hopefully ARDC. volunteers /> >/to host an echolink proxy farm, there were like 10 volunteers that would /> >/do (and did) it for free. It is likely that they would add such a VPN /> >/server feature to their already existing hosted system, if we would kindly /> >/ask it to them. / But NONE of those volunteers were from the Netherlands!! (they did not need to be, because I already host such a proxy farm in the Netherlands and the call for volunteers was to get more of them running across the world) The spread of volunteers was not as good as it could have been, but there were several from California, from Canada, from Australia, etc. Probably there are not so affected by backward internet connectivity (or lack of money) as you are. I don't know if they end up spending the $5/month for the benefit of amateur radio or if they got their hosting for free as part of some other deal. But they do offer the service! Voluntarily, without complaining. Because I think it is a waste of money (or a waste of time) to do a lot of research do potentially get a new product or another innovation started, for a community that is not interested in innovation and will make up any motivation to resist it. (including age, expense, "lack of reliability of the new system", and so on) You very well know that a system like the proposed one is operating in many other places, and the only proposed change is to interconnect those systems and make more of them, to replace the old and static system with something more flexible and more usable. Maybe you are mostly stuck in the usage scenario where AMPRnet is mostly used to emulate the old packet radio system, e.g. for BBS forwarding, DX cluster, telnet chat, etc. However, most new users who already know the internet want to do other things, like WebSDR, audio and video streaming (e.g. to YouTube), running amateur-oriented web services like a Mattermost server, etc. Internet connectivity is a must for most of these. But you can at least try! I remember seeing the questions here about having an IPIP gateway with more than one external address (e.g. using two different ISP links) to have redundancy at that level. Not possible, Sir! An IPIP tunnel endpoint has no way of seeing that the other side is down. With the newly proposed system this function would be no problem. BGP sees that a link is down and switches over to the alternate. Even within a second, when you configure BFD with it. But as long as the IPIP advocates get it their way, this will not happen. I could deploy it to my home, but I have no need to do that. I already have a 5GHz WiFi link to our nearby (5 miles) access point so I get my AMPRnet over radio, thank you very much. And I have a VPN as a backup in case it somehow fails. In fact I have backup in 2 directions: when my VDSL connection fails, I can still surf the web via my amateur radio connection. If only to check the ISP website to see if there are any known interruptions. And there are several other stations here with the same setup. Not only do they have the above advantages, their systems also provide backup to the links between the access points. When the interlink to my accesspoint fails (another radio link), it would be automatically backed up via my own VPN and radio link. BGP does all that. The IPIP system can't. Rob