[Mnet-devel] private Mnet howto

[baka at baka.baka]

since someone was spewing less-than-true stuff recently about mnet 0.7.1
net-setup after having ignored repeated requests to peer-review
documentation on that topic that was written after he requested it ...

*shrug* ... here is the fifth unusable mnet-network-setup
documentation. someone send that into the main repo, after
improving it a little to make it actualy useful for users.

the problem is, i cant do that myself. there are a gazillion subtle
things about that setup that are PLAIN GLARING OBVIOUS to me, but
may be less so for a user who never tried this before.
in case anyone is interested in improving this documentation and has
questions about it, please show up on (currently) 
	irc://irc.freenode.net/mnet


New patches:

[added private-mnet howto
baka at baka.baka**20040804142512] {
addfile ./doc/private_network.txt
hunk ./doc/private_network.txt 1
+
+HowTo setup your own Mnet 0.7.1 network
+ -- by some baka
+
+this description is supposed to work with 0.7.1a8
+
+the parasitic bootpage-server is something that was supposed to be
+not documented in its current form since its a badness according to 
+the EGTPv2 design document. it works anyways and solves my immediate
+problem by allowing me to run a test network.
+
+this description requires editing the config, which was another
+reason to not document the process, the config system needs to be
+replaced, badly.
+
+get and build/install the 0.7.1 software. 
+how to do that is documented somewhere else. (the README?)
+
+the mnetcli commands in the following description assume you are
+NOT running any other mnet 0.7 nodes on the same host already.
+check with "./mnetcli scan" if you are not sure.
+if you are running additional nodes, you will need to modify all
+calls to mnetcli with the appropriate node-offset modifiers, and
+you are supposed to know how to do that if you run such a setup.
+
+to set up a MT, just start an Mnet node:
+	MNETCONFDIR=my-mt ./Mnet &> my-mt.log &
+and shut it down again:
+	./mnetcli exit
+edit my-mt/node.conf:
+	add a "METATRACKER:" section (non-indented)
+	in that section, add a "RUN_METATACKER: yes" entry
+	note that the "RUN_M.." needs to be indented BY A SINGLE TAB
+	i suggest to disable all other services on the MT-node by
+	setting the following to "no":
+		RUN_BLOCKSERVER
+		RUN_RELAYSERVER
+	choose a port your MT will run on, and set it in
+		TRANSACTION_MANAGER_ANNOUNCED_PORT
+		TRANSACTION_MANAGER_LISTEN_PORT
+	and set TRANSACTION_MANAGER_PICKY_PORT to yes.
+	now configure the bootpage-list:
+		add a "BOOTPAGE_URLS:" section
+		add a "0: http://127.0.0.1:3333/bootpage/" entry
+		you will need to adjust the IP and PORT in that URL
+		to whatever your IP and PORT (see above) is.
+save the config, restart the node.
+	MNETCONFDIR=my-mt ./Mnet &> my-mt.log &
+
+now check your MTs status with "./mnetcli sta", it should be like:
+'metatracker':       'knowing 0 nodes offering 0 distinct services'
+'blockserver':  'not running'
+'mtm':
+     '<Peer <i8hh7>>: m      @ <TCP sockless #2 to 212.84.194.13:3333>'
+     'running 0.7.1a8'
+        'connected nodes':  []
+        'known nodes':           
+           '<Peer <i8hh7>>: m      @ <TCP sockless #2 to 212.84.194.13:3333>'
+'relayserver':  'not running'
+
+the important parts are:
+	blockserver and relayserver are not running
+	metatracker is running, but doesnt know anyone yet
+	mtm knows itself
+
+now you have a all new and shiny single-node Mnet network.
+to that, you can connect other nodes, by just giving them the
+right bootpage URL.
+
+how you do that? just do the BOOTPAGE_URLS section/list thingie
+like above. you can also just make a node.conf fragment containing
+just these lines, and use it as startup node.conf for a new
+node, the rest will be added by the node on first startup.
+
+you can also just get the bootpage-info with a http-client of your choice
+and put it on a different webserver, and point the clients at THAT url.
+
+
+
+now i read this again, and realize no one will understand it, unless he
+already knows how this works. its the _fifth_ "how to run your own mnet"
+documentation i write, all have been different in approach to the
+problem, and none ever worked for any user. this is sooo great.
+
+
}



Context:

[try to catch late-fails
ash at ash.de**20040606141250] 
[Adding backup uri for dll2def.zip, point to darcs wiki
icepick at icepick.info**20040603183039] 
[added dll2def url/md5sum
ash at ash.de**20040602163328] 
[TAG 0.7.1a8
ash at ash.de**20040602102817]