"community1" Test Network Has Restarted, Join Us!

It is incredibly stable. Doesn’t someone want to stress test it? :slight_smile:

I have to stop watching this for now. See you tomorrow.

1 Like

Is there a thread or video that explains in layman’s terms ‘How to set up a vault’? I really want to get involved with the testing, but don’t quite understand what I’m doing.

hi bb,

you da man!!

22 in table and all is beautiful!!

will run until you give me fresh orders or need anything done… give shout!!

rup

1 Like

Good morning, @Yannis_Caff .What operating system are you running?

Hmm, 24 vaults in the table and rock-solid for the nearly 15 hours since I took the --first flag out.

1 Like

its a beautiful thing!

well done for persevering…

rup

1 Like
INFO 14:55:51.673519191 [routing::stats stats.rs:151] Stats - Sent 19500 messages in total, comprising 76580188 bytes, 134 uncategorised, routes/failed: [4900, 56, 38, 37, 36, 36, 36, 35]/33
INFO 14:55:51.673534286 [routing::stats stats.rs:158] Stats - Direct - NodeIdentify: 24, NewNode: 111, ConnectionUnneeded: 0
INFO 14:55:51.673543496 [routing::stats stats.rs:162] Stats - Hops (Request/Response) - GetNodeName: 5/16, ExpectCloseNode: 143, GetCloseGroup: 1680/3859, ConnectionInfo: 2743, Ack: 8088, GroupMessageHash: 724
INFO 14:55:51.673561209 [routing::stats stats.rs:172] Stats - User (Request/Success/Failure) - Get: 363/359/4, Put: 27/27/0, Post: 78/76/2, Delete: 0/0/0, GetAccountInfo: 0/0/0, Refresh: 1037

rup

Yannis - if you’ve not visited a safenet website, then see Documentation suggests three steps, although perhaps out of order: A proxy-setup; B SAFE Launcher; C Demo App. That let’s you visit sites and setup your own websites.

The vault then is similar… download a copy and extract it from the .zip then run the safe_vault that’s inside that.

The difference for the community network is simple the config files that sit alongside the safe_vault. So, the safe_vault.crust.config needs switching out for the config file suggested by bluebird. That then states the name of the network and the seed IPs, so it can then find other part of the network. It should also suggests a port that vault will listen to, and if you start many instances then it seems to be better those are each on their own port=tcp_acceptor_port … but I see that config file bluebird has null in the tcp_acceptor_port and I think that’s better where does suggest a port… so fix that to be 5483 or similar. Those config files open in any text editor.

If you’re successful, then you’re see a run of “Routing Table size: ##”. If you don’t put a firewall in the way and have the portforwarding from your router set to the tcp_acceptor_port in the configuration file, then you’ll have a better chance of allowing others to easily connect to you. If you’re successful then keep it running, put it up and taking it down just creates stress on the network that’s not useful.

If you’re not using Linux and then can’t use the binaries that bluebird’s created, then for now the Test4 versions likely still will work - https://github.com/maidsafe/safe_vault/releases/tag/0.9.0

If you then want to use the community network, then you need to replace the config file in the safe_launcher folder with exactly the same as used for the vault.

I see there’s a meetup in London on Friday. Unclear if there will be Test5 running or if this community network might be the example used.

Guess we’ll find out tomorrow evening the difference. In the case we continue this network, could do with more vaults for stability in case increased demand falls over my limited upload speeds.

Happy to see that a network can survive on such small resources, though obviously it’s not being stretched atm and perhaps demand can overwhelm any small node set.

If it wasn’t continuing, I’d be tempted to do a rolling shutdown and restart on the vaults here to see how vulnerable it is. I suspect, so long a new node can balance reasonably quickly before another vault goes offline, that it should remain stable but where vaults go offline before new ones can catch enough detail to compensate, then it loses sense of self and gets confused what data exists and forgets other data entirely.

Just realised I should be watching :soccer: … I got Iceland in the sweepstake too, so no excuse to be here!

Absolutely it is continuing! I have never given any reason to think it wouldn’t continue.

And there are additions in the works that might be online tomorrow.

You may rest assured that there will be something for the meetup people to play with.

Now I’ll let you get back to your truncated icosahedron watching, or is it C60 (you need very good glasses to see those :slight_smile: ).

EDIT: I suppose Testnet5 could be sprung on us, in which case the Meetup will get to play with that. we’ll see. What I meant was that this network will only go into recess when Testnet5 is running. My (totally wild) guess is that Testnet5 won’t happen quite so soon after Testnet4.

There’s a risk my IP will change at random moment… ISP or static on the phoneline etc.

So, we need more vaults running… always need more vaults…

Anyone who’s not setup a vault and not watching Iceland thrash England… give it a Goal!

As it happens, I am looking at the Linux dynamic DNS client, ddclient, for use in conjunction with a free DNS provider such as Zonomi. I haven’t used either of these before (years ago I used DynDNS free service and their Windows software agent, which worked well enough) so I can’t attest to their reliability. However, I see no reason why a (free) domain name could not be slotted into the config in place of an IP address.

1 Like

or if the vault complains, then the real IP address of that domain name. It complains malformed if there’s no port suggested, so it might only recognise ip:port atm.

=>
http://hello.safenet
http://test.bluebird.safenet
http://odyssey.safenet
+?

1 Like

I set up a test host (not part of community1) with dynu.com (because Zonomi don’t give free domain names). Ddclient using dynu.com was easy to set up and I could ping the domain name straight away!

However, safe_vault fails to start when I put the domain name in the config, with this error:

thread ‘’ panicked at 'Unable to start crust::Service ConfigFileHandler(JsonDecoderError(ApplicationError(“Failed to decode SocketAddr: invalid IP address syntax”

That’s with a config like this:

{
  "hard_coded_contacts": [
    "91.121.173.204:5483",
    "185.16.37.156:5483",
    "109.147.231.101:5483",
    "blahblah.dynu.net:5483"
  ],
  "tcp_acceptor_port": 5483,
  "service_discovery_port": null,
  "bootstrap_cache_name": null,
  "network_name": "community1"
}

So that’s a dead end. Let’s hope your router doesn’t restart. :slight_smile:

EDIT: It is worth nothing that domestic ADSL services sometimes have fixed IPs anyway, even if you haven’t paid extra for a fixed IP. It is worth checking rather than assuming that ones IP is dynamic.

Hi, Im on windows 10.

hi men,

i’ll get another seeder vault up tomoz…

79.78.134.73

now we have recipe that works i hope it won’t take more than 5 mins to get it up and ready to boogie…

hope this helps…

rup

oh… lol…

if anyone whats to know the time…

there’s a strat 1 ntp server on 79.78.134.71

ntp.btl.io

nite!

rup

Hi, please do this:

To run a vault:

  1. Download the official release for Windows: https://github.com/maidsafe/safe_vault/releases/download/0.9.0/safe_vault-v0.9.0-win-x64-updated.zip

  2. Unzip the download.

  3. Download this file and put it in the folder from step 2 (overwrite the file of the same name already there): http://91.121.173.204/configs/safe_vault.crust.config

  4. Now you run the safe_vault.exe, either by double-clicking on it in Explorer (which gives less information if it exits with an error) or by open a DOS prompt, navigating to the folder and giving the command “safe_vault.exe”

  5. Ideally you will see something like this:

INFO 23:35:15.010900741 [routing::core core.rs:1032] Client(0cf08d..) Running listener.
INFO 23:35:15.163032499 [routing::core core.rs:1555] Client(0cf08d..) Sending GetNodeName request with: PublicId(name: 0cf08d..). This can take a while.
INFO 23:35:15.576096302 [routing::core core.rs:1371] Client(2329cd..) Added 37b23f.. to routing table.
INFO 23:35:15.579258444 [routing::core core.rs:411]  --------------------------------------------------------- 
INFO 23:35:15.579319031 [routing::core core.rs:413] | Node(2329cd..) PeerId(403b..) - Routing Table size:   1 |
INFO 23:35:15.579381963 [routing::core core.rs:414]  --------------------------------------------------------- 
INFO 23:35:16.580190142 [routing::core core.rs:396] Node(2329cd..) - Indirect connections: 1, tunneling for: 0
INFO 23:35:16.753665247 [routing::core core.rs:396] Node(2329cd..) - Indirect connections: 0, tunneling for: 0
INFO 23:35:16.754024362 [routing::core core.rs:1371] Node(2329cd..) Added a20132.. to routing table.
INFO 23:35:16.754055575 [routing::core core.rs:411]  --------------------------------------------------------- 
INFO 23:35:16.754065625 [routing::core core.rs:413] | Node(2329cd..) PeerId(403b..) - Routing Table size:   2 |
INFO 23:35:16.754072493 [routing::core core.rs:414]  --------------------------------------------------------- 
INFO 23:35:17.967500361 [routing::core core.rs:1371] Node(2329cd..) Added e35180.. to routing table.
INFO 23:35:17.967560818 [routing::core core.rs:411]  --------------------------------------------------------- 
INFO 23:35:17.967579334 [routing::core core.rs:413] | Node(2329cd..) PeerId(403b..) - Routing Table size:   3 |
INFO 23:35:17.967601600 [routing::core core.rs:414]  --------------------------------------------------------- 

and so on up to a “Routing table size” of maybe 20.

Sometimes it will stick at the " This can take a while" step for some minutes. Occasionally it will not progress at all and a ctrl-c to exit and running it again is needed.

To run the launcher and demo app: have you done that previously, say on an official testnet, or do you need detailed guidance?

The launcher does not require a vault to be run. They function separately, but running a vault helps to build our network.

For the launcher, the main difference is to remember to download this file: http://91.121.173.204/configs/safe_launcher.crust.config
and copy it into the launcher program folder before running the launcher. That will allow the launcher to connect to the community1 network.

We will soon have daily builds for Windows of the latest safe_vault (and eventually, the launcher and demo app) but for now you need to use the official release along with the customized configs as listed above.

Thanks, Rupert! …