Changes between Version 2 and Version 3 of Ticket #2224, comment 4

May 31, 2018 11:27:29 AM (13 months ago)


  • Ticket #2224, comment 4

    v2 v3  
    365365  I2P is a work in progress. Lots of improvements and fixes are being
    366366  implemented, and, generally speaking, running the latest release will help
    367   your performance. If you haven't, install the latest release
     367  your performance. If you haven't, install the latest release.
     36918 - Bittorrent / I2PSnark / Azureus I2P Plugin Questions?
     371  > Current link points to i2pforum - remove this FAQ entry?
     37319 - How do I connect to IRC within I2P?
     375  A tunnel to the main IRC network within I2P, Irc2P, is created when I2P is
     376  installed (see the I2PTunnel configuration page), and is automatically
     377  started when the I2P router starts. To connect to it, configure your IRC
     378  client to connect to localhost on port 6668. HexChat-like client users can
     379  create a new network with the server localhost/6668 (remember to tick "Bypass
     380  proxy server" if you have a proxy server configured). Weechat users can use
     381  the following command to add a new network:
     383    /server add irc2p localhost/6668
     38520 - How can I access the web console from my other machines or password protect
     386     it?
     388  For security purposes, the router's admin console by default only listens for
     389  connections on the local interface.
     391  There are two methods for accessing the console remotely:
     392  (1) SSH Tunnel
     393  (2) Configuring your console to be available on a Public IP address with a
     394      username & password
     395  These are detailed below:
     397  (1) SSH Port Forwarding/Tunneling
     399      If you are running a Unix-like Operating System, this is the easiest
     400      method for remotely accessing your I2P console.
     401      (Note: SSH server software is available for systems running Windows, for
     402      example )
     404      Once you have configured SSH access to your system, the '-L' flag is
     405      passed to SSH with appropriate arguments - for example:
     407        ssh -L 7657:localhost:7657 <System_IP>
     409      where '<System_IP>' is replaced with your System's IP address. This
     410      command forwards port 7657 (the number before the first colon) to the
     411      remote system's (as specified by the string 'localhost' between the first
     412      and second colons) port 7657 (the number after the second colon). Your
     413      remote I2P console will now be available on your local system as
     414      'http://localhost:7657' and will be available for as long as your SSH
     415      session is active. If you would like to start an SSH session without
     416      initiating a shell on the remote system, you can add the '-N' flag:
     418        ssh -NL 7657:localhost:7657 <System_IP>
     420  (2) Configuring your console to be available on a Public IP address with a
     421      username & password
     423        1 -   Open ~/.i2p/clients.config and replace
     424                clientApp.0.args=7657 ::1, ./webapps/
     425              with
     426                clientApp.0.args=7657 ::1,,<System_IP> ./webapps/
     427              where you replace <System_IP> with your system's public IP
     428              address
     429        2 -   Go to http://localhost:7657/configui and add a console username
     430              and password if desired - Adding a username & password is highly
     431              recommended to secure your I2P console from tampering, which
     432              could lead to de-anonymization.
     433        3 -   Go to http://localhost:7657/index.jsp and hit "Graceful restart",
     434              which restarts the JVM and reloads the client applications
     436      After that fires up, you should now be able to reach your console
     437      remotely. Load the router console at http://<System_IP>:7657 and you will
     438      be prompted for the username and password you specified in step 2 above
     439      if your browser supports the authentication popup.
     441      Note: You can specify in the above configuration. This specifies
     442            an interface, not a network or netmask. means "bind to all
     443            interfaces", so it can be reachable on as well as
     444            any LAN/WAN IP. Be careful when using this option as the console
     445            will be available on ALL addresses configured on your system.