Can you try with a simple small file and see how that goes. Large files are not gonna work here at the moment.
2 Likes
Vdash seems to be recording errors only for me at the moment. I doubt my node successfully connected but that might be all expected due to NAT traversal feature still a work in progress:
Will circle back in a few hours if the network is still up and play with other safe CLI commands.
FWIW, I tried with --port 12000 and without it, and opened up a large range of UDP continous ports for NAT port forwarding mappings on the router, but that may still not have helped the node connect.
What exact message confirms proper connectivity to the network in safe node logs with this latest iteration?
3 Likes
Sorry, seems the files got lost during the copy/paste around.
The hex string for the testnet.exe could from an old build, and may not exist in this testnet.
As you already succeeded in upload your own file, you can actually try
cargo run --bin safe --release -- --peer /ip4/178.128.166.245/udp/36572/quic-v1/p2p/12D3KooWPuaKwn7rFNn4oj1ABDpikVZ7scHs29ZNCHBveLHgCmak files download -- wallpaper.jpeg 89bf86508e7054781eb0db7cd32a11aa26cd9ea22d300d80a00965e252727ad7
Which I managed to do here, and see your shared wonderful picture of ink like landsape with safe logo on. 
5 Likes
It was interesting for me to try files other people uploaded.
But ok, here is my test file (which I can download): safe --peer=/ip4/178.128.166.245/udp/36572/quic-v1/p2p/12D3KooWPuaKwn7rFNn4oj1ABDpikVZ7scHs29ZNCHBveLHgCmak files download -- file 2cee232f0cf383960ac375e090a647e2afd4ebeb12b4cecb1bf91c2e0f4b3408
What I noticed, it was stored not in client\downloaded_files, but just in client.
I just used name and address from your command and confirm that it works. Good.
7 Likes
Yes, no NAT traversal here yet.
2 Likes
yeah,
file downloaded via uploaded_files will be put under client\downloaded_files
file downloaded via direct name & address will be put under client directly
7 Likes
Yaaaay!! Lets show the world!!
9 Likes
Looks like instead of safe files ... download should be safe ... files download.
Can you check corresponding command in the first post? I suspect it may be wrong. But not sure.
3 Likes
I’ve managed to connect a node to the network under multiple NATs - VM → Laptop → internal router → external router. I can see I’m connected to peers and the node has worked out my external IP correctly.
Mixed results on uploading. Was successful with small files (12 bytes!), though re-upload of the same files hasn’t always been successful. No successes with larger files (1MB - 8MB). Moderate success with 1k - 64k files.
Have had some success using an external peer for upload, and also my own node as the peer, so the nuts and bolts of the network are definitely working!
11 Likes
yeah, seems a mis-insertion when update the peer info for public net.
I cann’t modify the first post.
someone with the update right will correct it once available
8 Likes
Yes vdash will only show chunks as errors for the past few days.
2 Likes
I see, so does this indicate successful storage of chunks:
[2023-05-04T17:01:46.494976Z DEBUG safenode::node::api] That's a store chunk in for :e30dd0(11100011)..
Vdash does show ‘connected’ so maybe its working just fine 
.
4 Likes
Yes I think so
vdash is reporting false negatives - not @happybeing’s fault - it wwas working OK last week then some code change borked it.
3 Likes
The log message may have changed since the last update so I will look into it again later or tomorrow.
I’m getting the same vdash display as you at the moment, running a node in the cloud.
5 Likes
Same question.
I know how to poke TCP port from outside, but not UDP.
I doubt if I need to setup firewall or node already works fine.
1 Like
Here is a download of a moderately sized file
safe --peer /ip4/178.128.166.245/udp/36572/quic-v1/p2p/12D3KooWPuaKwn7rFNn4oj1ABDpikVZ7scHs29ZNCHBveLHgCmak files download -- contracts.md 926d667ae690ba7357d2148b6d273464c9ea6bf24e1971dfc265a43f42beaf1f
Starting logging to directory: "/tmp/safe-client.log"
Instantiating a SAFE client...
Downloading file "contracts.md" with address 926d667ae690ba7357d2148b6d273464c9ea6bf24e1971dfc265a43f42beaf1f
Successfully got file contracts.md!
Writing 1155303 bytes to "/home/willie/.safe/client/contracts.md"
1 Like
I also see my WAN ip in the ‘observed_addr’ key tag in the safe node logs. I take that as a positive sign.
6 Likes
where did you place safe am I being dense? can it be run from anywhere?
3 Likes
For the past few weeks I have been copying all the binaries to /usr/local/bin
So, yes, effectively I can run safe from anywhere
4 Likes
If anyone can post example log messages for GET and PUT that will save some time.
2 Likes