This is a little guide to show you how to setup a small container dedicated to an i2p router such as i2pd. This allows for a central router for all your clients on your LAN for example.


Read the guide

i2pd Alpine Setup Script

  • Strict3443OP
    link
    fedilink
    English
    arrow-up
    2
    ·
    8 months ago

    Update 2023-10-26

    Script was fixed and now correctly copies the reseed certificates from the repo to the data directory. Running the script on a fresh alpine container now results in a working i2pd router with no config necessary. This fixes the “Firewall Status: Unknown” issue.

      • Meldrik@lemmy.wtf
        link
        fedilink
        English
        arrow-up
        1
        ·
        8 months ago

        What about the Router console? Is this something that’s only available with i2p, or does it also exist with i2pd?

        • Strict3443OP
          link
          fedilink
          English
          arrow-up
          2
          ·
          8 months ago

          That is i2p-java and i2p+ only. i2pd is only the router which is why it is so small and fast.

          • Meldrik@lemmy.wtf
            link
            fedilink
            English
            arrow-up
            1
            ·
            8 months ago

            Okay, so i2pd is the lightweight version and all the configs happens in the config file available.

            Is there a way to test that i2pd is actually working?

            • Strict3443OP
              link
              fedilink
              English
              arrow-up
              2
              ·
              edit-2
              8 months ago

              Step 5 from the guide shows how to test if i2pd is running on your Alpine container. If you are using i2pd on another machine, similar commands will work as well.

              For the Alpine Container:

              • Run ps command to see if the i2pd program is running
              • Run service i2pd status to see that status. Ex. * status: started
              • Find your container’s local IP address with ip -4 a and navigate to the i2pd web console at http://:7070
              • Meldrik@lemmy.wtf
                link
                fedilink
                English
                arrow-up
                1
                ·
                edit-2
                8 months ago

                Thanks, I’ve done that and I can access the i2pd webconsole, but it doesn’t seem to run correctly. I’ve had it run for over 20 hours now and it just says Network status: Unknown.

                • Strict3443OP
                  link
                  fedilink
                  English
                  arrow-up
                  2
                  ·
                  8 months ago

                  Can your container reach the internet? If you shell into your container can you ping anything outside your network?

    • Possibly linux@lemmy.zip
      link
      fedilink
      English
      arrow-up
      2
      ·
      8 months ago

      You need to setup the proxy setting in i2p and Firefox. Keep in mind that you can’t just browse the web like a normal we browser as you can only visit i2p sites.

      In i2p go into settings and allow proxy traffic from lan.

      In Firefox go into your proxy settings and point your browser to i2p. I forgot what port but you can look it up online.

      Sorry for the vague instructions but I haven’t done this in a while.

      • CAVOK@lemmy.worldM
        link
        fedilink
        English
        arrow-up
        2
        ·
        8 months ago

        Semi-true. There is an outproxy available so you can surf the normal Web, if you want. With a manual setup you might have to configure your machine for it though.