https://reticulum.network/manual/interfaces.html#announce-ra...
The manual has some documentation on some of the rate limiting features built into RNS
one malicious peer can have as many sources as they want. don't even need a botnet of IPs.
The link you posted seem to guard against flood of sinks on the distributed routing, but there's no mention of source flooding.
fwiw, those seem to apply to only a single destination, and any node can sybil up as many destinations as it wants, right? `announce_cap` seems more relevant
is there a place where you've written down the threat model reticulum is intended to defend against? it's hard for me to evaluate its security measures without that context
The threat model would be highly dependent on the carrier used. For example, if you're using LoRa an adversary would be using far different methods of disruption when compared to a traditional overlay network.
i think physical-layer disruption like lora jamming is kind of a separate consideration, but physical-layer traffic analysis might not be
i had misunderstood you to be saying that the second reticulum node ever was at your house, so i had assumed you were the author