Why is depends attempting to build a test file when it's supposed to be cross compiling? paste.debian.net/1354741 The host is x86_64 ubuntu 20.04, ran command is make HOST=aarch64-apple-darwin11 inside of contrib/depends.

and HEAD of release-v0.18 is checked out

<o​frnxmr:xmr.mx> what happens when you run `make depends target=aarch64-apple-darwin11` from the root dir

same exact log

<o​frnxmr:xmr.mx> You have all dependencies installed?

<o​frnxmr:xmr.mx> I'll try in 15mins

yup

woodser: does 9820 solve your test issue without increasing max connections per ip?

<w​oodser:monero.social> selsa I still see the issue with 9820 without using `--max-connections-per-ip 10`

<w​oodser:monero.social> *selsta

what happens when you set it to 2?

<w​oodser:monero.social> selsta I see the same issue with `--max-connections-per-ip 2`, and actually I see the problem with even `--max-connections-per-ip 1000` on the current release-v0.18 branch with or without 9820 now. maybe I did something wrong in my previous testing, unless something since changed

<w​oodser:monero.social> so basically the current release branch has me broken and I don’t have a way to fix it currently

woodser what's your use case?

<w​oodser:monero.social> running haveno tests, it creates 2 traders and executes ~10 trades in parallel, so ~33 wallets syncing with to 2 local monerods

woodser: just to confirm, did you double check that it compiled the correct version? because i'm confused why it worked before

<w​oodser:monero.social> I double checked today, so maybe I tested incorrectly before. I will triple check the compiled version

<v​tnerd:monero.social> woodser: is this an RPC issue? Because the relevant command flag is _not_ --max-connections-per-ip

<w​oodser:monero.social> that's the startup flag I'm using with the monerods

<o​frnxmr:xmr.mx> for p2p connections, right?

<o​frnxmr:xmr.mx> theres 4 flags `--max-connections-per-ip --rpc-max-connections-per-public-ip --rpc-max-connections-per-private-ip --rpc-max-connections`

<o​frnxmr:xmr.mx> The latter 3 for rpc

<w​oodser:monero.social> I'm not using the latter 3 startup flags

<w​oodser:monero.social> just these: github.com/haveno-dex/haveno/blob/4…710d899f0cd33e5c43b087/Makefile#L63

<o​frnxmr:xmr.mx> Shouldnt need them unless your tests are using > 3 rpc connections

<o​frnxmr:xmr.mx> Is --hide-my-port interfering, maybe?

it's about p2p transaction propagation

so it should be --max-connections-per-ip

<w​oodser:monero.social> I just tested again and confirmed that 0cd7456 (which I tested last time) works if and only if `--max-connections-per-ip 1000` flag is used

<w​oodser:monero.social> if I don't use that flag I get test failures and warnings in the non-primary monerod:

<w​oodser:monero.social> ```

<w​oodser:monero.social> 2025-02-25 16:28:20.443 E Unable to send transaction(s) via Dandelion++ stem

<w​oodser:monero.social> 2025-02-25 16:28:20.443 W Unable to send transaction(s), no available connections

<w​oodser:monero.social> ```

<w​oodser:monero.social> but current release branch (02328399) does not work with or without `--max-connections-per-ip 1000`, with slightly different failure but also relating to txs not being confirmed

<v​tnerd:monero.social> well the obvious question - what `status` indicate for your incoming+outgoing connections?

<v​tnerd:monero.social> it says you have none presumably?

<r​ucknium:monero.social> ofrnxmr: Are those last 3 flags missing from the docs website? docs.getmonero.org/interacting/monerod-reference

<o​frnxmr:xmr.mx> They arent released yet