Opened 4 years ago

Closed 4 years ago

#1675 closed defect (not our bug)

i2p router console doesn't bind to IPv6 adresses after first restart

Reported by: Born2Be Owned by:
Priority: minor Milestone: n/a
Component: api/utils Version: 0.9.22
Keywords: Cc:
Parent Tickets:

Description

I place this string in my cliens.config:
clientApp.0.args=-s 7657 ::1,127.0.0.1,10.<mylocalnetipv4cutted>,2001:<myexternalipv6cutted> ./webapps/
just after fresh installation of i2prouter. At the first start everything seems ok and I can login to console using https://[2001:<myexternalipv6cutted>]:7657 but after the first restart I begin to get this error in my wrapper.log:
Unable to bind routerconsole to ::1 port 7657 for SSL: java.io.IOException: IPv6 addresses unsupported
You may ignore this warning if the console is still available at https://localhost:7657
Unable to bind routerconsole to 2001:<myexternalipv6cutted>] port 7657 for SSL: java.io.IOException: IPv6 addresses unsupported
You may ignore this warning if the console is still available at https://localhost:7657

And router console is binded only at IPv4 adresses. Nothing is changed except restarting the router.

Subtickets

Change History (1)

comment:1 Changed 4 years ago by zzz

  • Component changed from unspecified to api/utils
  • Milestone changed from undecided to n/a
  • Resolution set to not our bug
  • Status changed from new to closed

http://pastethis.i2p/show/9528/

<zzz> Born2Be, do you have IPv6 addresses in the output of java -cp $I2P/lib/i2p.jar net.i2p.util.Addresses ?
<Born2Be> zzz, no, I have not ipv6 adresses in that output.
<Born2Be> But the i2p user can see them in "ip a" for example
<zzz> Born2Be, so your Java does not have IPv6 enabled.
<Born2Be> zzz, strange because first of all as you can get in #1675 when router is started at the first time it binds to ipv6 successfully
<Born2Be> Can it bind if java has no ipv6 support?
<Born2Be> And the second, I have the same compiled java on other host and router successfully bind to ipv6. The two differences are: one system is hardened and other not, and in one icedtea was compiled with awt support and in other - not
<zzz> sorry, I don't know
<anonimal> Born2Be: I would suggest to start eliminating variables then. Build a vanilla kernel and then try, etc.
<Born2Be> zzz, the main question for you is why at the first run of the router everything is ok and when I restart it everything is broken?
<Born2Be> Without this - it was obviously fault of my java
<zzz> I can't help you further. I'll paste this info into the ticket, but if Java can't see the v6 addresses there's nothing we can do

Note: See TracTickets for help on using tickets.