Applications that send large amounts of unnecessary path requests will very quickly get rate limited by transport nodes, and the entire system they are running on will not be able to resolve any paths on the network, until the burst subsides and hold period expires. Do not write applications like this. Only request paths for destinations you need to communicate with.

By default, Reticulum will handle this automatically, and ingress path request control will be enabled on interface where it is sensible to do so. It should generally not be neccessary to modify the ingress control configuration, but all the parameters are exposed for configuration if needed.

• The ingress_control option tells Reticulum whether or not to enable ingress control on the interface. Defaults to True.

• The ic_new_time option configures how long (in seconds) an interface is considered newly spawned. Defaults to 2*60*60 seconds. This option is useful on publicly accessible interfaces that spawn new sub-interfaces when a new client connects.

• The ic_pr_burst_freq_new option sets the maximum path request ingress frequency for newly spawned interfaces. Defaults to 3 path requests per second.

• The ic_pr_burst_freq option sets the maximum path request ingress frequency for other interfaces. Defaults to 8 path requests per second. If an interface exceeds its burst frequency, incoming path requests from that system will not traverse the network further.

• The egress_control option enables hard-limiting path request egress control per-interface. Defaults to False

• The ec_pr_freq option sets the hard limit for outbound path requests per second on a given interface.

All of the above settings can be configured both as instance-wide defaults under the [reticulum] section of the configuration file, or on a per- interface basis under the relevant interface configuration section.