CLI commands doesnt has GUI effects

[anonymous maybe]

when i try to disable a function in the router , the router will respond to it as its disabled, but when i check the i2pconsole its still active.

e.g:

sudo sed -i '/^.*tunnel\.0\.\(proxyList\|option\.i2ptunnel\.httpclient\.SSLOutproxies\)/d' "/var/lib/i2p/i2p-config/i2ptunnel.config"

this should remove the out-proxy 4444 , but when i visit the console still there.

another example if i disable the upnp through adding

i2np.upnp.enable=false

to

/var/lib/i2p/i2p-config/router.config

the I2Pconsole will still show that upnp is active/with tick mark.

this is dangerous in one side , that the GUI might overcome the CLI effect thus manipulating it. and vise versa.

[zzz]

i2ptunnel does not check for changes in i2ptunnel.config and reload it. You would have to stop and restart i2ptunnel (or the whole router) for changes to take effect.

The router, however, does periodically check for changes in router.config and reload it. Even so, not all setting changes will take effect. As it says on /configadvanced, some changes require a restart.

Even for the router, we don't really promote changing the config file while running. It's a very-advanced feature.

So I don't see what the bug is here. Apparently the behavior doesn't match your expectations, but I'm not sure how to fix that or where we should put some additional explanations. Any ideas?

[anonymous maybe]

well actually these commands run before I2P was running , and same result as well I2P doesnt really show that its turned off when you open i2pconsole through firefox (graphically).

[zzz]

If you make changes before i2p starts, then they will take effect, of course. So either you're doing it wrong or changing the wrong file or not really doing it before i2p starts. /var/lib/i2p/i2p-config/router.config is used for I2P running as a Linux service only. You're looking at the results on the correct running router?