Opened 12 months ago

Last modified 11 months ago

#2240 new defect

Preference for inbound IPv6 peers

Reported by: zzz Owned by: zzz
Priority: minor Milestone: undecided
Component: router/transport Version: 0.9.34
Keywords: Cc:
Parent Tickets:

Description

After the changes in 34 to improve things for IPv6-only peers, and IPv6 in general, I'm seeing a larger proportion of v6 connected peers (especially on NTCP) on a v6 router. I'm wondering if we should exempt incoming v6 connections from known v6-only peers, or have other adjustments, to ensure that v6 works well. IPv6-only routers may only connect to about 20% of the peers.

Subtickets (add)

Change History (2)

comment:1 Changed 12 months ago by zab

I'm wondering if we should exempt incoming v6 connections

Exempt them from what? The connection limit or something else?

comment:2 Changed 11 months ago by zzz

Haven't thought it through. Yeah conn limits, maybe not exempt but exempt from one of the lower limits, so between x and x+5 % only ipv6 inbound is allowed, for example. Another possibility is having idle timeout higher for ipv6. There's a few knobs that can be tweaked.

Note: See TracTickets for help on using tickets.