Thanks for running this, it's good that more nodes are up that can send out 100mbps instead of the ~2mbps that most home connections can do. When Bitcoin picks a sad node to download the blockchain from, it delays the user getting caught up. A lot of people only run Bitcoin when they send money, requiring a day or weeks to be downloaded at once.
My main problem at home is that I cant get the cable modem/router to properly forward ports to the router I use to configure the network. They somehow "disabled" the DMZ I had. If I enter the URL directly I can still see the DMZ settings, but not change anything. Well some ISPs are just dicks when its their hardware -_-
You might as well do something interesting like put up an abe blockchain explorer if you are fronting the bill for services. Also
https://insight.bitpay.com/ is newer explorer software.
I dont think Ill run anything else there. The server is very limited (50GB disk, 2 GB ram), but I will consider it should I ever upgrade. I initially thought to make the node available via tor. Ill see how the server handles the node, cronjobs for the stats and apache first.
Are the stats for 26th and 27th you downloading the blockchain after installation? That seems like an awful lot of inbound traffic.
Yes, the 28th is so low because I didnt start bitcoind when I went to sleep as you can see from the stats below (made with vnstati).
Looks like one of the peers I have a connection to is also downloading the complete blockchain as its not yet fully synced (~290k/317k blocks)
Edit: Yes getpeerinfo confirms it. I have a connections to two other nodes that are at 224k and 228k blocks
$ bitcoind getpeerinfo | grep startingheight
-snip-
"startingheight" : 224207,
-snip-
"startingheight" : 288428,
-snip-
Next step is to get some nice graphs (currently reading into rrdtool[1]) for the number of connected peers and figure out how many of them the server can handle once fully synced.
[1]
www.cuddletech.com/articles/rrd/index.html