Opened 3 years ago

Closed 3 years ago

#1829 closed defect (fixed)

Peertest IPv6-only 0.9.26-8 gives warning with ipv4 address

Reported by: nextloop Owned by:
Priority: minor Milestone: 0.9.28
Component: router/transport Version: 0.9.26
Keywords: ipv6, peertest Cc: dg, zzz
Parent Tickets: Sensitive: no

Description

08.08.16 13:52:41 ^^^ 1 similar message omitted ^^^
08.08.16 14:00:06 WARNUNG  [leTimer2 4/4] .transport.udp.PeerTestManager: We are already running a test: PeerTest 800600926 as ALICE; Bob: /someIPv6:PORT; last send after 0; pkts relayed: 1, aborting test with bob = /IPv6
08.08.16 14:01:31 WARNUNG  [ handler 1/1] .transport.udp.PeerTestManager: Invalid address in PeerTest: IPv4:PORT
08.08.16 14:01:39 ^^^ 1 similar message omitted ^^^
08.08.16 14:18:04 WARNUNG  [ handler 1/1] .transport.udp.PeerTestManager: Invalid address in PeerTest: IPv4:PORT
08.08.16 14:18:14 ^^^ 2 similar messages omitted ^^^
08.08.16 14:26:14 WARNUNG  [ handler 1/1] .transport.udp.PeerTestManager: Invalid address in PeerTest: IPv4:PORT
08.08.16 14:26:24 ^^^ 2 similar messages omitted ^^^
08.08.16 14:26:40 WARNUNG  [leTimer2 3/4] .transport.udp.PeerTestManager: We are already running a test: PeerTest 800600926 as ALICE; Bob: /IPv6:PORT; last send after 0; pkts relayed: 1, aborting test with bob = /IPv6
08.08.16 14:41:59 ^^^ 1 similar message omitted ^^^

I censored all IPs and ports, if you need them just let me know.

Someone on IRC meant that this could come from i2pd-peers.

Subtickets

Change History (1)

comment:1 Changed 3 years ago by zzz

Component: router/generalrouter/transport
Milestone: 0.9.270.9.28
Resolution: fixed
Status: newclosed

the messages will probably continue until the 0.9.28 release is out, but the version bug was fixed in 0.9.27-1, see #1861

Note: See TracTickets for help on using tickets.