Opened 10 years ago

Closed 8 years ago

#24 closed defect (fixed)

I2P doen't accept option for Router I2CP port

Reported by: d3r3k4 Owned by: zzz
Priority: minor Milestone: 0.8.3
Component: router/general Version: 0.7.10
Keywords: Cc:
Parent Tickets: Sensitive: no

Description

I2P by default listens on 7654 for clients, there's option mentioned at http://www.i2p2.de/i2cp (i2cp.tcp.port) - i put it in router.conf but it is not taken by I2P.

Please correct this behavior. This would impact situations if one would like to run multiple I2P routers on same machine.

Subtickets

Change History (5)

comment:1 Changed 9 years ago by anonymous

Milestone: 0.7.11

comment:2 Changed 9 years ago by anonymous

Owner: set to zzz
Status: newassigned

I haven't tested it, but I think the problem is not that it doesn't listen on the configured ports, but that all the clients don't send to the configured port. Each client has its own configuration.

It would be nice if each client checked the router config. But it doesn't happen now. If you look in clients.config, i2ptunnel.config, i2psnark.config, etc., you will see 7654 everywhere. So it's a real pain to set up a second router that has clients.

One way if you are just doing console testing, for example, is to turn off all the clients but the console in the 2nd router. And set i2p.vmCommSystem=true to prevent it from connecting to the network. And disable I2CP completely. There's some howtos on zzz.i2p about it.

comment:3 Changed 9 years ago by anonymous

well, i would like to run 2 I2P instancies on one machine, for this reason i wanted to have i2cp.tcp.port working. (of course i would reconfigure all clients.)

i configured logger to have DEBUG:

logger.config:logger.defaultLevel=DEBUG

it from the log file it seems I2P doesn't check this i2cp.tcp.port at all. sorry but i'm not java programmer ;)

what can i check? all normal application can bind to specific port so there's no problem to run multiple instancies of the same application on one machine. then I2P should have same option…

it would be overkill to have another I2P in virtual machine or some 'container'…

comment:4 Changed 9 years ago by zzz

Milestone: 0.8.10.8.4
Version: 0.8

comment:5 Changed 8 years ago by zzz

Milestone: 0.8.40.8.3
Resolution: fixed
Status: assignedclosed
Version: 0.80.7.10
  • Config for router options is on configclients.jsp as of 0.8.3. You can now disable the external I2CP port completely, which makes multiple routers easier.
  • For several releases, all clients inside the same JVM as the router ignore the i2cp host and port settings, and connect internally. This makes things much easier.
  • Part of the confusion also is that the router uses the properties i2cp.hostname and i2cp.port. The clients use i2cp.tcp.host and i2cp.tcp.port. This isn't documented anywhere. But it mostly doesn't matter anymore now that there is GUI setup and internal clients ignore the settings.
Note: See TracTickets for help on using tickets.