my vault doesn’t connect anymore .___.
we might need the bug-fixed version of vaults to run a stable network 
ps:
INFO 18:05:07.462882777 [routing::states::bootstrapping bootstrapping.rs:251] Bootstrapping(d21bfe…) Connection failed: Proxy node needs a larger routing table to accept clients.
INFO 18:05:08.926589241 [routing::states::node node.rs:1240] Node(d21bfe…()) Requesting a relocated name from the network. This can take a while.
Yeah, probably. Having said that I just restarted my vault and while it took a long time thinking about it, it did connect in the end
My node also crashed. And no possibility to reconnect because proxy node needs a larger routing table.
Raw estimates of data uploaded: 20 nodes * 6GB / 8 (duplication factor) = 15 GB.
Someone added giga bytes of data. What is the interest of doing this? It’s such an easy attack without safecoins (just create several accounts to overcome the PUT limit).
Until safecoins are ready, the PUT limit needs to be drastically lowered to slow this kind of attack.
one of my vaults stopped too, and doesn’t restart, because of too small a routing table too.
Seems we stalled the plane folks…
My Vault was still online, but I just took it off. it was pumping MB’s per second up and down filling up with almost 7 GB of chunks. There are 2 limitations right now for a successful community network:
I guess we’ll see TEST 12c this week, after that we can always start a community net again. Maybe even lowering the 6 Mbit to 1 Mbit to see what happens. That we we test something different than Maidsafe. Would be very interesting.
But I did have fun last 24H as we learned to start a community net with resource proof enabled as well 
.
1 of my 2 vaults is still running at the moment and I see in the logging that there are 12 nodes now.
I suppose the 12 remaining ones are not all seeding ones, so we don’t manage to restart the thing.
I just pulled everything off, but I’d be glad to restart if we manage to get 8 seeders again.
It was very insightfull to see things from inside, I learned quite a lot too. Very interesting to see how a small net is very vulnerable.
There is loss of data… safe://hello css file is there but the index.html not.
Reboot by renaming network as community_network_12_b ?
sure,
count me in with :
108.61.165.170:5483
That suggests then… if the same seed vaults are reset
{
"hard_coded_contacts": [
"35.167.139.205:5483",
"35.157.19.255:5483",
"35.156.88.83:5483",
"52.65.136.52:5483",
"138.197.235.128:5483",
"108.61.165.170:5483",
"185.16.37.149:5483",
"78.46.181.243:5483",
"31.151.192.2:5483",
"52.59.206.28:5483",
"86.164.140.138:5483"
],
"bootstrap_whitelisted_ips": [],
"tcp_acceptor_port": 5483,
"service_discovery_port": null,
"bootstrap_cache_name": null,
"network_name": "community_network_12_b"
}
okay - restarted with your suggested name
ERROR 19:18:57.265290179 [crust::main::bootstrap mod.rs:184] Failed to Bootstrap: (InvalidNameHash) Network name mismatch.
ah yes we need one of us to start with :
safe_vault /f
so a new network name is created.
I’m not ready yet, so I pass my turn ( dinner 
)
Done for 52.59.206.28.
Fyi: I was still able to see my video, posted yesterday on network ‘user_network_12_b’, some 15 minutes ago.
But every step (authentication etc…) was slow to very slow and there were some hitches in the video.
Routing Table size: 1
ps: looks nicer that way 
Routing Table size: 2 – edit haha you beat me
“Network name mismatch.”
Can someone (that’s in the routing table) please post his config file please? I’m getting an error.
some one will have to edit the OP, btw
{
“hard_coded_contacts”: [
“108.61.165.170:5483”,
“35.167.139.205:5483”,
“35.157.19.255:5483”,
“35.156.88.83:5483”,
“52.65.136.52:5483”,
“138.197.235.128:5483”,
“185.16.37.149:5483”,
“78.46.181.243:5483”,
“31.151.192.2:5483”,
“52.59.206.28:5483”,
“86.164.140.138:5483”
],
“bootstrap_whitelisted_ips”: ,
“tcp_acceptor_port”: 5483,
“service_discovery_port”: null,
“bootstrap_cache_name”: null,
“network_name”: “community_network_12_b”
}
i did put @nice on top of the list 
nothing else changed (thought that might make sense because that will probably be the first to be contacted and is in the new network)
I’m getting kicked off from that network due to “Network name mismatch” so no luck here with these settings.
