User run network based on test 12b binaries


#1

We have started a user run network based on test 12b binaries

To join the network as a node you will need to change the vault crust config file to this

{
  "hard_coded_contacts": [
    "35.167.139.205:5483",
    "108.61.165.170:5483",
    "52.65.136.52:5483", 
    "206.116.50.52:5483",
    "99.199.170.208:5483",
    "31.151.192.2:5483",
    "86.184.57.178:5483",
    "13.80.119.160:5483",
    "85.93.19.51:5483",
    "35.157.162.33:5483",
    "185.16.37.149:5483",
    "35.156.220.253:5483"  
  ],
  "bootstrap_whitelisted_ips": [],
  "tcp_acceptor_port": 5483,
  "service_discovery_port": null,
  "bootstrap_cache_name": null,
  "network_name": "community_network_12_b"
}

Ensure you ONLY change the values in hard_coded_contacts and the network_name fields to what is shown above.

If you can keep your vault running 24/7 then I will add it to the “seed” nodes above


The launcher config file will also require the above changes so the launcher can connect to the network


Currently my node is using the free tier instance (VM) that aws provides for 1 year so that their services can be tested.


Here are the download links for Test 12b that are being used for this user run network:

Make the above changes after unpacking the files


IP Addresses starting with 192.168.xxx.xxx are non routable addresses used for NAT etc, so I cannot have then in the config file


Is there a farming client already?
MaidSafe Dev Update - March 2, 2017 - Test 12c
SAFE Network - Test 12b (Network offline, end of test)
#2

Tell us the IP address:port for your node if you can keep it running all the time so I can add it to the above list.

I’d say we need 20 “seed” nodes to make everything smooth.

Happy SAFEing everyone.


#3

I dont have the speed to be a node but would like to upload files. I’ve found the launcher config file but have nothing to open it with on a mac… any suggestions? :grin:


#4

TextEdit should work (and it comes pre-installed)


#5

Does this look right? cant connect?


#6

Seems like the tcp_acceptor_port should be null, not 5483 for the launcher config file

Did you change it? or was it like that when you downloaded it?


#7

Also I just looked at the log file and it is complaining about the network not being large enough yet

“Proxy needs a larger routing table to accept clients”

So I guess we need more people to run nodes before we can consider the network usable. Which is reasonable enough when you consider you want a secure network before uploading data/files


#8

I changed it. :laughing:


#9

And is not easier to continue with the current test? It still works very well.


#10

Yes it would. But I thought

Meant maidsafe took down their seed nodes.


#11

Yes, I forgot the seed nodes.

Pity, now is working better than ever. I just uploaded 363MB. Total upload speed 172KB/seg. Download Speed About 500KB/seg.


#12

Have a look at your crust cache file and maybe we can create a seed list from that

EDIT: I just tried the launcher using the original config fike and can still connect so that it seems that the seed nodes must still be running - but for how long?


#13

Seems that Test12B is finish. Launcher can’t connect.

I try with your network.


#14

Yes the nodes are down now. Those two bugs are serious enough that they possibly cannot be repaired by the network itself. So we do need to close them out. I hope it’s not long till we see another iteration, but it’s in parallel with some pretty big work as well. We also so not want to annoy the community with to many iterations either, so a fine balance. At least we are showing the network works in terms of the big picture, but need to clean up a few small parts for stability.

Thanks again though


#15

@dirvine, do you know how many nodes are needed before the proxies have enough entries in their routing table. Even if you know how many nodes in the routing table before the proxy will allow connections to pass through

The launcher will not connect with the error “not enough nodes in routing table”


#16

You will need at least 8 IIRC. So enough to create a minimum section.


#17

There are 7 nodes left :-). Still fully functional network even most data are lost ;-).
You may connect to this IP:port

xxx.xxx.xxx.xxx:5483

Just edit for Launcher.crust.config for Launcher. Not sure how long the owner of this node will keep the node online.

EDIT. Removed node’s IP address as network is not functional any more. My guess too few nodes left (5 total). Trying to add more vaults getting message:

[routing::states::bootstrapping bootstrapping.rs:251] Bootstrapping(e38fab…) Connection failed: Proxy node needs a larger routing table to accept clients.


#18

Which network is that. This topic really is for the user run one. Just don’t want confusion over which network thats all


#19

this is what is left from 12b network :slight_smile:

“network_name”: “test_network_12_b”


#20

@neo, I try to connect several times with the new network but the the resource proof fail. I have 300/300Mb. connexion so I don’t think is my fault.