I think this is a generic topic that could be one of the first things to solve within the AMPRnet. When we get new users, we immediately get the question "now that I am connected, what can I do?". Such a VPN server comes before that, but it is another case of information lookup. We could construct some website within AMPRnet where you can look for such information. What interesting websites are there to visit, who is offering SIP telephony, etc. Of course it can be done in a Wiki (it already exists), but such information quickly gets outdated. People post their new services, then they lose interest and the services stop working, but never update the information anymore. Also, access to the Wiki is often problematic: when open to everyone it will have to be monitored and corrected when things go wrong, when access control is used it adds the burden of creating and maintaining trusted user accounts and it is a hurdle for registering services. So we could come up with some way to keep such a services database with some form of automated maintenance. E.g. a user who wants to have his services in the database somehow creates a description in a standard format on some standard URL and submit this once to the central system, which then regularly queries this file and adds info to the listings, plus it automatically drops it when it cannot retrieve the data for some time. It should be easy to add information, but still it should be in a standard format so it can easily be shown in tables. Of course there already is HamnetDB but it is focused mainly on the network layer. Something similar could be made for services, plus it should guard against outdated information as mentioned before (HamnetDB also suffers from that problem) The wellknown WebSDR site "websdr.org" has an example of what I mean. The list of SDRs shown there is always actual. The sysop of the SDR puts its information in the configuration, and the running SDR sends it to the central system automatically (unless you turn that off). Rob