Opened 4 years ago

Closed 16 months ago

#1457 closed defect (no response)

Router announces only TCP on IPv6, but both on IPv4

Reported by: echelon Owned by:
Priority: minor Milestone: 0.9.28
Component: router/transport Version: 0.9.17
Keywords: Cc:
Parent Tickets:

Description (last modified by echelon)

My I2P 0.9.17-18 does only announce TCP on IPv6:

[RouterAddress?:

Type: SSU
Cost: 5
Options (4):

[caps] = [BC]
[host] = [80.110.99.228]
[key] = [Y36HpKusDhku1H~P26LLsY4p3o6ADx6cbZLUsOLxtNk=]
[port] = [49322]]

[RouterAddress?:

Type: NTCP
Cost: 9
Options (2):

[host] = [2a02:8388:e300:bd80:225:22ff:fef8:9d67]
[port] = [49322]]

[RouterAddress?:

Type: NTCP
Cost: 10
Options (2):

[host] = [80.110.99.228]
[port] = [49322]]

The current external IP address is not available.
TCP port 49322 was not forwarded by UPnP.
UDP port 49322 was not forwarded by UPnP.

I am after a carrier grade NAT for IPv4, but IPv6 is open reachable.

IP configuration is:

"UPnP active"

use all auto method for IP address
it shows only IPv6 and empty field in the "specify hostname or IP:" section
Prefer IPv6 over IPv4 is active
UDP is use auto-detected IP address (currently...)
Use the same port configured for UDP

It has the config for the last 10+x reboots at least.

echelon

Subtickets

Change History (4)

comment:1 Changed 4 years ago by echelon

  • Description modified (diff)

comment:2 Changed 3 years ago by str4d

  • Status changed from new to open

comment:3 Changed 2 years ago by zzz

  • Component changed from unspecified to router/transport
  • Milestone changed from undecided to 0.9.28
  • Status changed from open to infoneeded

@OP please report if this is still happening

comment:4 Changed 16 months ago by zzz

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