Hmm, sorry. We’re definitely seeing reduced open connections in most cases.
No luck for me either. I’ve sent you the log file on Discord @chriso
looks like a lot of incoming connnection errors, could it be a mismatch of 0.5.0 antnodes?
my antnode1 in the past hour bottom of the log file
[2024-12-22T02:33:20.991584Z ERROR ant_networking::event::swarm 565] IncomingConnectionError from local_addr:?/ip4/94.130.221.176/udp/50384/quic-v1/p2p/12D3KooWPEivW3qNVtQiZ3rfhKJ6ntxoPb3E4WaydFmwyo9B4HSB/p2p-circuit, send_back_addr /p2p/12D3KooWJ43FtcEaNh3AKqSLn7A7oAsNmxfSF3JX1VVP92E9LbMV on ConnectionId(213489) with error Transport(Other(Custom { kind: Other, error: Left(Left(Right(Apply(Io(Custom { kind: UnexpectedEof, error: “eof” }))))) }))
[2024-12-22T02:33:21.110937Z ERROR ant_networking::event::swarm 565] IncomingConnectionError from local_addr:?/ip4/65.108.107.123/udp/49970/quic-v1/p2p/12D3KooWQ6dUyDA2XsemET34yTdzPkTd8Et6B7HQoMhM4CDEiVMQ/p2p-circuit, send_back_addr /p2p/12D3KooWJ43FtcEaNh3AKqSLn7A7oAsNmxfSF3JX1VVP92E9LbMV on ConnectionId(213490) with error Transport(Other(Custom { kind: Other, error: Left(Left(Right(Apply(Io(Custom { kind: UnexpectedEof, error: “eof” }))))) }))
[2024-12-22T02:33:21.127064Z ERROR ant_networking::event::swarm 565] IncomingConnectionError from local_addr:?/ip4/94.130.221.176/udp/50384/quic-v1/p2p/12D3KooWPEivW3qNVtQiZ3rfhKJ6ntxoPb3E4WaydFmwyo9B4HSB/p2p-circuit, send_back_addr /p2p/12D3KooWA8C5fYzmiTekRAHrgWJT3Pxe2X86TjJVkhAKudxqefDL on ConnectionId(213493) with error Transport(Other(Custom { kind: Other, error: Left(Left(Right(Apply(Io(Custom { kind: UnexpectedEof, error: “eof” }))))) }))
[2024-12-22T02:33:21.127104Z ERROR ant_networking::event::swarm 565] IncomingConnectionError from local_addr:?/ip4/148.251.194.232/udp/53912/quic-v1/p2p/12D3KooWEi1Jq1WLTQE2NuVQr5GWewtFmZeVdA7dDsaHkgdnmnHL/p2p-circuit, send_back_addr /p2p/12D3KooWA8C5fYzmiTekRAHrgWJT3Pxe2X86TjJVkhAKudxqefDL on ConnectionId(213492) with error Transport(Other(Custom { kind: Other, error: Left(Left(Right(Apply(Io(Custom { kind: UnexpectedEof, error: “eof” }))))) }))
@qi_ma I thought that the client was paying 3 nodes for each chunk. That’d be 24 attos to upload 8 chunks.
Have i read the information on the changes to payments wrong?
@qi_ma @Shu I heard from Chriso that it’s you working on the dial error.
Can you confirm that the issue is not resolved in the latest hotfix and if so when a new hotfix is expected? I’m currently not sure if it’s a node related issue or if I should continue to look for errors in my setup.
Could that also affect API Client?
Maybe the node itself should not (try to) start so many connections immediately. How about adding 10ms - 100ms delay between connection attempts?
The nodes are designed to stay online for a long time… and specially if there are some hole punching, the large amount of concurrent connection starts might interfere each others.
I was referring to this at my previous post.
Many of the connections is traversing the network to get the nodes that are in the close and far neighbourhood. So many hops for each one. To introduce a significant delay would be to take hours for this process. But it is also dynamic in that nodes are coming and leaving (eg your nodes are coming into the network) and to take too long may mean a few broken paths. More work, more traffic as it retries more often. (talking here about initial setting up of routing table)
Also remember that when my node here contacts ones from Europe for instance it is 300mS to get a response. Your 10mS only gets you to your ISP typically, and 100mS gets you perhaps 1/5th the way around the world.
To add a delay that would achieve what you are suggesting, it would have to be a few times 200mS (IE 1 second) and that would mean building the routing would take 1/2 hour to 3 hours. But it is also trying to handle normal network protocol without being shunned. 1/2 hour and it would be getting shunned by the first lot of nodes it added to the routing table.

It is still killing my router, but hopefully it is working well for others.
Just to update, I’m still getting router issues, even when not uploading via the CLI client.
I’ve had to stop my nodes for now. I’m not sure what has changed, but it’s definitely putting pressure on my Fritzbox 7530, despite having a 500/70mbit fibre connection.
Hi All,
Seasons greetings
Has anyone got some test files on the current network, for which they wouldn’t mind sharing the public address.
I’ve been trying to download for the past few days, and it’s either timing out, or throwing a client panick and I’m wondering if there’s an issue with my uploads that I’ve been testing.
TYVM
Jad
@aatonnomicc has beg blag & friends
some i managd earlier im still failing with linux mint but ill retry my way to victory eventually
ant file download 7a8554af57f3664c1f7896cae2394119d8ead2d49e736b060d8a66fc6a2befa1 . # BegBlag.mp3
ant file download 751ee9710e65c0ad751dbbda9fcc660279b85a675b7eefce3574d71c65501e7a . # autonomi.mp4
ant file download 8baa15a5f1b80dcbc2eb54ddfd1223b5eb04935e2f93bad478619f2c24ad59ff . # Best_CD_Ever.mp3
ant file download 21aa171fe59bee10d88b10e26f43f4fcddf838d93aee88e18a1690dea8856753 . # Patosh-RoughNight.mp3
ant file download da95b19058e1dc6eb811eab9c0153259a17ad453b215867595ab16bec8976c34 . # Deep_Feelings_Mix.mp3
ant file download 7b86dbf4ce68edff5fc3840c88c10763004fbd94b10a751fe520a0ebd4f671ec . # AnarchyInTheSouthside.mp3
ant file download 8ea1c3916136208065f7d2e0a6a12ee8301c07fe15a88565841d59a73fc9db55 . # An_Introduction_To_The_SafeNetwork.mp4
For folk not closely following discord.
FYI
Week1 is only 4.5 days and over from what I understand.
As long as you have 2 attos earned on the wallet starting Dac 18 and before 11.59PM UK Sunday 22nd you will have qualified for requirements of week 1.

some i managd earlier
tyvm will give those a go.

3 nodes for each chunk. That’d be 24 attos to upload 8 chunks.
might be uploaded in private mode?
Hence the 3 chunks of meta
got generated and counted, but not uploaded.

Can you confirm that the issue is not resolved in the latest hotfix and if so when a new hotfix is expected?
the latest hotfix 12.1.3 shall got vast number of un-necessary dial back avoided, hence reduce the dial error
appearance.
However, it is a valid
error, say dialing a dead peer, or the connection got dropped.
Hence, I won’t expect the dial error
disappear at all.
ps. the s3 network-contact and bootstrap_json_list fetched does contains certain outdated
peers, which will result in certain amount of dial error
during the intitial startup.

might be uploaded in private mode?
Hence the 3 chunks ofmeta
got generated and counted, but not uploaded.
Yes, that one was in private mode.
Has the contacts file gone offline? https://sn-testnet.s3.eu-west-2.amazonaws.com/network-contacts
I was just trying to bootstrap sn_httpd and it’s failing.
My ant CLI still seems to work, so guessing there is a new way to connect too? EDIT: Unless that has cached them somewhere…
I think I’m right in saying the contacts file has been deprecated in favour of bootstrap cache. feat: impl bootstrap cache by RolandSherwin · Pull Request #2487 · maidsafe/autonomi · GitHub . I have a file at ~/.local/share/autonomi/bootstrap_cache/bootstrap_cache_1_0.3.json