As I said in a previous message am the network engineer for a co-location facility. I have lots of bandwidth and spare servers that I can install vmware on and offer different os and memory configs for.
> -----Original Message----- > From: devl-bounces at freenetproject.org [mailto:devl- > bounces at freenetproject.org] On Behalf Of Matthew Toseland > Sent: Saturday, February 26, 2011 2:55 PM > To: devl at freenetproject.org > Subject: [freenet-dev] The testnet returns! > > The testnet has returned! This is a separate network, incompatible with > Freenet, which has a separate repository, separate auto-update keys > etc. This is ABSOLUTELY NOT ANONYMOUS. It logs aggressively, and all > nodes connect to my central coordinator node. I can then request logs > for any period, along with a few other status indicators, from any > node. The network is intended for two tasks: > 1. Finding difficult bugs where you need to be able to see the logs > from both sides. Particularly in the packet transport code and other > fairly low level stuff, but also probably in requests etc. > 2. Testing potentially disruptive changes. > 3. Attack simulations, but only when explicitly authorised by me. (I.e. > if I'm debugging load management I don't want people DoSing it at the > same time just to prove it's vulnerable; obviously only well-behaved > hackers will respect this rule, those that aren't will just attack the > main network) > > To use the testnet, you need to download the installer: > > https://checksums.freenetproject.org/latest/TestnetInstaller.exe > https://checksums.freenetproject.org/latest/testnet_installer_offline.j > ar > > (It should be at least version 12) > > System requirements: > Minimum 5GB disk space requirement for logs Reasonable memory (it keeps > up to 100MB of logs in RAM) Logging may cause problems for those with > slow disks or a lot else running / latency requirements. > > Note that the testnet uses different ports for clients by default: > FCP on 19841. > Fproxy on 19484. > > Also, Fproxy will stubbornly declare on every generated page that you > are using the testnet. However there is no protection for FCP. > > Opennet *may* work, as my testnet node is a seednode and listed in the > testnet seednodes file. However it hasn't been tested yet. Also I > haven't yet tested the auto-update, and given experimental code may be > deployed, you may have to update your node manually from time to time. > However the adapted update scripts appear to work. > > Obviously, don't share anything illegal on the testnet. Logs will > sometimes include filenames of downloads etc. So we might discover > illegal files (by accident), and this would put us in a difficult > position, not to mention making you traceable! > > Don't share identities (FMS, site keys etc) between the testnet and > Freenet either, unless you want them to be traceable. > > The more technical folks might like to look into copying content from > one network to another via binary blobs; otherwise just insert stuff > etc. > > While the network is small it may be necessary to set the store > everything in the datastore option to make inserts work. > > (You shouldn't use Freenet itself for stuff illegal under US/UK law > either; if you tell us this we must refuse to give tech support, ban > you from IRC, lists etc; this is long-established policy, based on the > Grokster judgement). > > If we have a few hundred people on the testnet, it should make it > significantly easier to debug various low level bugs and test new > potentially disruptive code before deploying it. So please consider > installing a testnet node! Note that it may require some manual > maintenance, and is much more likely to break badly than the main > Freenet. Thanks.
