Opened 2 years ago

Last modified 16 months ago

#2297 new defect

ipv6 only: weird effects with v4 inbound disabled

Reported by: jogger Owned by: zzz
Priority: minor Milestone: undecided
Component: router/transport Version: 0.9.35
Keywords: Cc:
Parent Tickets: Sensitive: no

Description

I have 2 routers set to ipv6 only. They have full ipv6 connctivity. From previous tests ipv4 disable inbound was still set. I expected that this would be disregarded.

This is not the case: There are displays of "firewalled" all over i2p. The routers work, but they make only very few (3-7) connections. Known peers never exceeded 20.

After removing the setting the routers correctly displayed: ipv4 disabled, ipv6 OK with more than a dozen activen peers and hundreds of known peers.

Subtickets

Change History (2)

comment:1 Changed 18 months ago by jogger

During network tests again ran "IPv6 only" with "ipv4 disable inbound" set. Now actually this ENABLES ipv4, coming up with an ipv4 SSU network address.

comment:2 Changed 16 months ago by zzz

Component: router/generalrouter/transport
Owner: set to zzz
Sensitive: unset
Note: See TracTickets for help on using tickets.