I2P Bugtracker: Ticket #2378: Updated configurations on /configtunnels do not reflect on /i2ptunnelmgr and vice versa.https://trac.i2p2.de/ticket/2378
<p>
I currently ran an eepsite and found that the configurations (e.g., numer of tunnels, number of hops, or number of backup tunnels) I set on either <tt>/configtunnels</tt> or <tt>/i2ptunnelmgr</tt> do not carry over to other.
</p>
en-usI2P Bugtrackerhttps://trac.i2p2.de/chrome/site/i2plogo.pnghttps://trac.i2p2.de/ticket/2378
Trac 1.0.5zzzTue, 15 Jan 2019 18:33:40 GMTstatus changed; resolution sethttps://trac.i2p2.de/ticket/2378#comment:1
https://trac.i2p2.de/ticket/2378#comment:1
<ul>
<li><strong>status</strong>
changed from <em>new</em> to <em>closed</em>
</li>
<li><strong>resolution</strong>
set to <em>not a bug</em>
</li>
</ul>
<p>
/configtunnels says right at the top:
</p>
<p>
Exploratory tunnel setting changes are stored in the router.config file. Client tunnel changes are temporary and are not saved. To make permanent client tunnel changes see the i2ptunnel page.
</p>
<p>
In the other direction, changes in i2ptunnelmgr are reflected on /configtunnels, except perhaps if the tunnel is configured for reduce-on-idle. I just retested and verified it works fine.
</p>
Ticket