/etc/i2pd/i2pd.conf contains number of listening ports configuration (actually 10 or more when you look for “port”). Which ones should I open in firewall so other people can connect my node? Excluding ones that are meant for management of my node. I manage the node only locally.

So far I have only open/forwarded one port, one that is set a few lines below the line “## Port to listen for connections” that certainly allows relaying traffic for other I2P peers per the http://127.0.0.1:7070/ traffic stats.

Services HTTP Proxy	Enabled
SOCKS Proxy	Enabled
BOB	Disabled
SAM	Enabled
I2CP	Enabled
I2PControl	Disabled
  • sp3ctre@feddit.org
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    22 days ago

    I didn’t open any ports in my home router and connections are working good. It also says “firewalled” in my webconsole. Not sure, what the benefits are with opening ports.

    • hetzlemmingsworld@lemmings.worldOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      22 days ago

      My assumption is that forwarding port allows peers (other I2P users) to connect you even they are behind the firewall. Two firewalled peers can not connect in a bittorrent, but I2P is not bittorrent… But when it warns you about being “firewalled” it suggests some negative impact to me and suggests there may be similar connectivity issue like with bittorrent. Ports needs to be forwarded on router device (if applicable) or DMZ(if you are able to lock down your connectivity using your computer firewall - DENY/block policy by default and whitelist only listening ports of I2P, torrent client and similar), on VPN server, and opened in your firewall (if applicable).