Opened 19 months ago

Last modified 17 months ago

#2150 infoneeded defect

Option bindAllInterfaces does not work

Reported by: darknetman Owned by:
Priority: major Milestone: undecided
Component: router/general Version: 0.9.33
Keywords: Cc:
Parent Tickets: Sensitive: no

Description

I want to access I2P running on my local server in the LAN with it's local IP.
So the configuration should be bind on it's local IP or is there an better option?
Perfect would it be to bind to the local LAN-IP to an special interface like eth1

So i tried this configuration hint ​https://geti2p.net/en/faq#remote_i2cp

But adding i2cp.tcp.bindAllInterfaces=true or i2np.tcp.bindAllInterfaces=true
does effect nothing.

Subtickets

#2151: Option for I2CP Interface is without any functionclosed

Change History (3)

comment:1 Changed 19 months ago by darknetman

Add a subticket #2151.

comment:2 Changed 19 months ago by zzz

Component: unspecified → router/general
Status: new → open

I just tested it and it works.

I2CP is a specialized interface for remote applications. You say you want to "access I2P" but don't say how.

I suspect you want to do web browsing from another machine? If so, the correct way to configure it is to change the "reachable by" address to your lan address or 0.0.0.0 in the Hidden Services Manager setting for the I2P HTTP Proxy, and change your proxy settings in your browser accordingly.

If it's for the console, the setting is for the router console on /configclients.

Yes our FAQ could be clearer and the configuration could be easier.

Please clarify what you're trying to do. You now have comment permissions.

comment:3 Changed 17 months ago by Eche|on

Status: open → infoneeded
Note: See TracTickets for help on using tickets.