Outbound tunnels aren't under a limit like inbound tunnels. i assumed snark caps you at 16, but no. Snark adjusts tunnels to about peers / 2, so with < 32 peers there is no benefit to increasing > 16. better off running more snarks. But with higher peer counts you can see substantial gains while using less tunnels/memory compared to running more snarks.
if you're dumb enough to do this: i2pd will take the abuse, but might get unstable. It could segfault if you're a dyslexic idiot and mix up outbound.length and outbound.quantity. Also i have a feeling doing this could accelerate some memory leak when using snark with i2pd. Java doesn't do that but you'll run up limits quicker probably.
The easiest way to do it is to edit the config file and restart it:
/i2psnark/i2psnark.config.d/i2psnark.config
make small number big
i2psnark.i2cpOptions= ..... outbound.quantity=69
If you want to adjust settings after through the gui it won't work right because >16 tunnels doesn't display correctly, so it'll bump your tunnels down to 1 if you change anything. You'll have to change it in the config again. But if not change setting much, leave it. Snark will reduce tunnels on its own
Turns out you CAN send a post request to snark and it accepts it, no need for restart that way. So i updated multisnark in TuckIt to do this. Settings can be changed from CLI across several snarks now and copied from one snark to another.
zzzi2p wrote
I can fix the display so if it's over the limit it still shows correctly.