rns.recipes

Hello,

I hope I'm not on a wrong track here but something with propagated message sending in nomadnet really seems to be wrong. With any propagation node I try, including those that work well with sideband in the same moment, sending fails. Here is an example log (slightly redacted; always looks very similar):

[2026-09-09 06:52:16] [Verbose] Sending lxmf.delivery announce

[2026-09-09 06:52:35] [Debug] No stamp cost set on LXM to <7e3ecdcaf9c929d0363e9669ea983080>, autoconfigured to None, as required by latest announce

[2026-09-09 06:52:35] [Debug] Deferred stamp generation was requested for <LXMessage>, but outbound ticket was applied, processing immediately

[2026-09-09 06:52:35] [Debug] A ticket for <7e3ecdcaf9c929d0363e9669ea983080> was already delivered 23m and 26.69s ago, not including another ticket yet

[2026-09-09 06:52:35] [Debug] Generated stamp with outbound ticket 2b:c2:a4:42:db:10:8b:47:7a:6a:76:fb:e2:53:11:9e for <LXMessage 9635fbed039d0e0e812de958a125d833e78a60e504e5feebc6e521e56bbd816f>

[2026-09-09 06:52:36] [Debug] Received active propagation node announce from <2ee4eb045b55fa7daba9371393ee283f>

[2026-09-09 06:52:37] [Debug] Starting propagation stamp generation for <LXMessage 9635fbed039d0e0e812de958a125d833e78a60e504e5feebc6e521e56bbd816f>...

[2026-09-09 06:52:37] [Debug] Generating stamp with cost 16 for <caa62fad08b841f37fa22b9dadab9199c03cc5b3ec7512090a6bcf6800dc5ad5>...

[2026-09-09 06:52:37] [Debug] Starting 4 stamp generation workers

[2026-09-09 06:52:52] [Debug] Stamp with value 18 generated in 14.97s, 29808 rounds, 1991 rounds per second

[2026-09-09 06:52:52] [Debug] Generated stamp with outbound ticket 2b:c2:a4:42:db:10:8b:47:7a:6a:76:fb:e2:53:11:9e for <LXMessage 9635fbed039d0e0e812de958a125d833e78a60e504e5feebc6e521e56bbd816f>

[2026-09-09 06:52:52] [Debug] Propagation stamp generation completed for <LXMessage 9635fbed039d0e0e812de958a125d833e78a60e504e5feebc6e521e56bbd816f>

[2026-09-09 06:52:53] [Debug] Outbound processing for <LXMessage 9635fbed039d0e0e812de958a125d833e78a60e504e5feebc6e521e56bbd816f> to <7e3ecdcaf9c929d0363e9669ea983080>

[2026-09-09 06:52:53] [Debug] Attempting propagated delivery for <LXMessage 9635fbed039d0e0e812de958a125d833e78a60e504e5feebc6e521e56bbd816f> to <7e3ecdcaf9c929d0363e9669ea983080>

[2026-09-09 06:52:53] [Debug] No path known for propagation attempt 1 to <c2a469aa5151f67153e54616ef162b0e>. Requesting path...

[2026-09-09 06:52:53] [Debug] Outbound processing for <LXMessage 9635fbed039d0e0e812de958a125d833e78a60e504e5feebc6e521e56bbd816f> to <7e3ecdcaf9c929d0363e9669ea983080>

[2026-09-09 06:52:53] [Debug] Attempting propagated delivery for <LXMessage 9635fbed039d0e0e812de958a125d833e78a60e504e5feebc6e521e56bbd816f> to <7e3ecdcaf9c929d0363e9669ea983080>

[2026-09-09 06:52:53] [Debug] Establishing link to <c2a469aa5151f67153e54616ef162b0e> for propagation attempt 2 to <7e3ecdcaf9c929d0363e9669ea983080>

[2026-09-09 06:52:53] [Debug] Signalling link MTU of 262.14 KB for link

[2026-09-09 06:52:53] [Debug] Establishing link with mode AES_256_CBC

[2026-09-09 06:52:53] [Debug] Link request <143eacdb6b43b66a39a025dc00c1476b> sent to <lxmf.propagation.0635238b3f73e75b6706b7346e2b0b61:c2a469aa5151f67153e54616ef162b0e>

[2026-09-09 06:52:54] [Debug] Validating link request proof with mode AES_256_CBC

[2026-09-09 06:52:54] [Debug] Destination confirmed link MTU of 4.10 KB

[2026-09-09 06:52:54] [Debug] Link <143eacdb6b43b66a39a025dc00c1476b> established with <lxmf.propagation.0635238b3f73e75b6706b7346e2b0b61:c2a469aa5151f67153e54616ef162b0e>, RTT is 379ms and 750.97?s

[2026-09-09 06:52:54] [Debug] Outbound processing for <LXMessage 9635fbed039d0e0e812de958a125d833e78a60e504e5feebc6e521e56bbd816f> to <7e3ecdcaf9c929d0363e9669ea983080>

[2026-09-09 06:52:54] [Debug] Attempting propagated delivery for <LXMessage 9635fbed039d0e0e812de958a125d833e78a60e504e5feebc6e521e56bbd816f> to <7e3ecdcaf9c929d0363e9669ea983080>

[2026-09-09 06:52:54] [Debug] Starting propagation transfer of <LXMessage 9635fbed039d0e0e812de958a125d833e78a60e504e5feebc6e521e56bbd816f> to <7e3ecdcaf9c929d0363e9669ea983080> via <c2a469aa5151f67153e54616ef162b0e>

[2026-09-09 06:52:54] [Debug] Set compression support from app data to: True

[2026-09-09 06:52:57] [Debug] Outbound processing for <LXMessage 9635fbed039d0e0e812de958a125d833e78a60e504e5feebc6e521e56bbd816f> to <7e3ecdcaf9c929d0363e9669ea983080>

[2026-09-09 06:52:57] [Debug] Attempting propagated delivery for <LXMessage 9635fbed039d0e0e812de958a125d833e78a60e504e5feebc6e521e56bbd816f> to <7e3ecdcaf9c929d0363e9669ea983080>

[2026-09-09 06:52:57] [Debug] The link to <c2a469aa5151f67153e54616ef162b0e> was closed

This did not happen to me in the past. Am I the only one seeing this?

Reproduced with 1.4.0 and 1.4.1 during several days.

Is this across different propagation nodes, or just one? Have you tried changing it?

Rudi Mentaire wrote:

Reproduced with 1.4.0 and 1.4.1 during several days.

Change the prop node you are using. That node has disabled propagation. That's why the link closes immediately.

I see - you are correct of course.

What I had been doing in nomadnet was selecting "Use as default propagation node" in the node info area of nodes I trusted. But this is not a good idea in general it seems: most servers that announce a dedicated propagation node on their nomadnet page provide it under a different separate address. Random propagation node addresses might just refuse my requests.

So - thank you for your help. Hopefully I will only find real errors in the future (or better: none at all).