Sorry it took me a little longer to get back to you. Had a developer leave the project, need to re-allocate some work and offboard him. So let’s see…
It’s a drop-in folder where distribution maintainers (Whonix) and/or users can drop snippets…?
Well yes, in that there are places it looks for default configuration files and if you have an existing configuration in that directory it won’t generally interfere with those settings. If we have to touch one of your settings when we configure your router, we also have to publish something about why, couple examples, we had to reach in and enable “Tunnel Testing” in an update to the Java I2P router a few releases ago in order to avoid a conflict with
i2pd routers, and I had to change the update URL in the Easy-Install for Windows due to a conflict with de-coupled I2P routers(Easy-Install for Windows is a bundle). The point is, if you put a config file in the config directory, we don’t change the settings unless it’s really, really important.
- Whonix should stop telling users to edit
/var/lib/i2p/i2p-config/clients.config.d/00- net.i2p.router.web.RouterConsoleRunner-clients.config since there no need for it.
- Whonix should stop shipping the config-package-dev
/usr/share/i2p/router.config since there’s no need for that either.
- Whonix should drop its config snippet(s) into the
/var/lib/i2p/i2p-config folder? Any file name possible?
Yes to 2 and 3, if I understand correctly, but
2. Possibly put
3. You can either use
/var/lib/i2p/i2p-config/clients.config in which case the names matter, or you can use
/var/lib/i2p/i2p-config/clients.config.d in which case the directory names matter but any filename is OK as long as it ends in
3.a: If you use
/var/lib/i2p/i2p-config/clients.config simply make your edits* to the default config files and place them in the
/var/lib/i2p/i2p-config directory. They will be migrated on the first run to directory configs. Otherwise everything will function normally.
3.b: If you use
/var/lib/i2p/i2p-config/clients.config.d/, pre-populate it with all the config files you need, i.e. the migrated versions of the default clients tunnels. In these directories any file with a name ending in
.config will be read for a configuration.
Change from 127.0.0.1 to 127.0.0.2 .
Those would occur in
clients.config or the corresponding
clients.config.d directory, and
i2ptunnel.config or the corresponding
i2ptunnel.config.d directory. Change any value which you want to be reachable on a different address to that different address.