Unless I’m mistaken, --no-upnp is required if using port forwarding.
2 Likes
If you do not have upnp available then there is a no upnp option/flag you can set on antctl IIRC
EDIT: @born2build beat me to it lol
2 Likes
Aaaargh! Something has changed then because this is what used to work perfectly with the last version:-
antctl add --count 100 --node-port 12401-12100 --rewards-address <redacted> evm-arbitrum-one
I’ve never had to put the --no-upnp flag in before.
I thought the only difference was that I was trying to use metrics this time and that is what was bunging it up but I was thinking there was something odd going on because even just this wasn’t working:-
antctl add --node-port 14001 --rewards-address <redacted> evm-arbitrum-one
Thanks guys! Happy now!
1 Like
Yes it came in the last version
2 Likes
I have a problem downloading an Ubuntu.iso uploaded by @aatonnomicc. Any views what this might be about?
time ant file download e7bb1b87c1f0e07cdb76ba5e82a425a8da712940c2d3553aa6791494e92aa54d ubuntu-16.04.6-desktop-i386.iso
Logging to directory: "/home/toivo/.local/share/autonomi/client/logs/log_2025-04-03_18-42-06"
🔗 Connected to the Network
Fetching file: "ubuntu-16.04.6-desktop-i386.iso"...
⠉ [00:34:59] [----------------------------------------] 0/1
1 errors while downloading data at: e7bb1b87c1f0e07cdb76ba5e82a425a8da712940c2d3553aa6791494e92aa54d
["Failed to fetch file \"ubuntu-16.04.6-desktop-i386.iso\": General networking error: GetRecordError(QueryTimeout)",]
3 Likes
This keeps on repeating, already three times:
"Failed to fetch file \"ubuntu-16.04.6-desktop-i386.iso\": General networking error: GetRecordError(RecordNotFound)",
3 Likes
Hmm, seems ok for me:
$ time ant file download e7bb1b87c1f0e07cdb76ba5e82a425a8da712940c2d3553aa6791494e92aa54d ubuntu-16.04.6-desktop-i386.iso
Logging to directory: "/home/autonomi/.local/share/autonomi/client/logs/log_2025-04-03_19-57-18"
🔗 Connected to the Network Fetching file: "ubuntu-16.04.6-desktop-i386.iso"...
⠐ [00:00:39] [----------------------------------------] 0/1 Successfully downloaded data at: e7bb1b87c1f0e07cdb76ba5e82a425a8da712940c2d3553aa6791494e92aa54d
real 2m31.459s
user 2m1.294s
sys 1m5.617s
Edit: 1.6GB in 2m 30s is pretty impressive too! 
about 70mbit/s real time.
5 Likes
Might be my router… Would be cool to be able to limit the thing that is overloading it with a download of this size.
3 Likes
wow, more surprised how @aatonnomicc managed to upload such a large file?
was it done with the new release or sometime earler?
and how many re-attempts experienced ?
7 Likes
was done a while ago posibley 2 weeks ago and it was done over many many many attempts 
although iv never managed to brute force Linux mint @ 3gb onto the network.
edit ---------------
i uploaded it on 27/02/2025 with what ever release was latest at that point if info is of any use i think it actually went up in one go
5 Likes
I forgot to time this but I’m guessing I got fairly similar performance.
This is most encouraging.
8 Likes
oh, might be with the 1.2.6 release.
must be super lucky to got it through in just one go.
3 Likes
id actually forgotten about this upload glad @Toivo brought it back to our attention 
4 Likes
iv got a cloud oracle vps that I only use for uploading and downloading no nodes on it so if anything has a good chance its that vps 
3 Likes
ah, right, yeah, a super good connection service does prove will affect the upload success rate a lot..
8 Likes
and no node runners use oracle as its expensive so its in a super good spot and no nodes running in the same data centre its my lucky vps
5 Likes
I’m still not able to download it.
And in fact it seems that my repeated trials jammed our connection so, that our LAN (wifi and ethernet) got totally jammed because of it. I downloaded over ethernet. I had to reboot the router. It’s not top notch router, but has been working fine for your typical home use, watching videos with a couple devices, video calls etc.
I don’t think this is a top priority issue at the moment, but something needs to be done to it at some point. It’s going to affect much larger audience than those running nodes.
Is it maybe because the large files have so many nodes holding chunks, that the amount of connections is just too much for common consumer routers?
6 Likes
I recognized that on my smallish development-vps with only ~3GB of spare memory the system kills the process at some point because RAM is becoming sparce not because the data wouldn’t arrive
very nice to see the network improving (in spite of the scale)
5 Likes
Looking good from here too Maidsafe folk. nice work !!! 
Flipped the switch from Notwork to Network.
10 Likes