Opened 4 years ago

Closed 4 years ago

#1629 closed defect (no response)

Tunnel has new b32 address

Reported by: guest Owned by:
Priority: major Milestone: undecided
Component: apps/i2ptunnel Version: 0.9.21
Keywords: New address Cc:
Parent Tickets:

Description

Hi,

after the upgrade to 0.9.21 one of my tunnels had all of a sudden a new b32 address.

This is the log:

I2P version: 0.9.21-0-1~deb7u+1
Java version: Oracle Corporation 1.7.0_65 (OpenJDK Runtime Environment 1.7.0_65-b32)
Wrapper version: 3.5.25
Server version: 8.1.17.v20150415
Servlet version: Jasper JSP 2.1 Engine
Platform: Linux i386 3.2.0-4-686-pae
Processor: Atom (atom)
Jbigi: Locally optimized native BigInteger? library loaded from file
Encoding: UTF-8
Charset: UTF-8

Is there any way to go back to the old address (I still know it) ?

Thanks

Subtickets

Change History (5)

comment:1 Changed 4 years ago by user

This is not the log, but only the information about your system.
Was that tunnel configured to have a persistent destination (address)?

It is normal that client tunnel's addresses change on restart of the tunnel.
If you have not set iz to be persistent, I'm afraid you cannot get it back.
Otherwise, its key was saved. If it changed anyway, then this is indeed a bug.
In that case you can only get it back if you still have a backup.

comment:2 Changed 4 years ago by user

  • Status changed from new to infoneeded_new

comment:3 Changed 4 years ago by user

  • Status changed from infoneeded_new to new

look for a file like this i2ptunnel8-privKeys.dat, with the number of the tunnel you had

comment:4 Changed 4 years ago by user

  • Status changed from new to infoneeded_new

What kind of tunnel was it?
Had you been using it already over various restarts?
What did you do? Only update and it was gone?

comment:5 Changed 4 years ago by zzz

  • Resolution set to no response
  • Status changed from infoneeded_new to closed
Note: See TracTickets for help on using tickets.