Automatic selection of IP family

[slagiewka]

The default has been set in the initial commit:

ioredis/lib/redis/mixin/default_options.js

Line 11 in b8ea9b8

family: 'IPv4',

As a result, any project that that effectively uses ioredis defaults is only using IPv4 even when IPv6 is available. This gets worse when Redis is available in IPv6 only.

As an operator for OSS projects like Immich or Ghostfolio I can't get automatic upgrades to IPv6 - manual intervention is required. If the project is flexible around providing custom DSN this is only partially bad. If project only handles parts of connection settings - updating the project is required.

Database drivers (e.g. for PostgreSQL) or @redis/client don't suffer from this limitation and moving to IPv6 is hassle free.

[slagiewka]

It is worth noting that node,js has implemented RFC6724 via c-ares since node v14.

nodejs/node@4cfcaae

[slagiewka]

At the time of initial commit, node's docs have been informing users that there are two possible values: 4 and 6. This has been fixed since as this was not correct. nodejs/node@0777e09

Another honourable mention is autoSelectFamily implementing RFC8305 that gets completely ignored if family is not 0. The functionality is in node since v19 and also available in v18.

[slagiewka]

Honourable mentions of ioredis still confusing users:
https://cycle.io/community/threads/6837b669c09c5118b34d9be3/gotcha-with-redis-and-ipv6
https://community.n8n.io/t/allow-ipv6-to-use-redis-with-provider-internal-network/32439/3
https://station.railway.com/questions/private-network-issue-6e5aba86

[PavelPashov]

Hey @slagiewka, thank you for fixing this in #2028, we'll make sure to include it in the next release

[github-actions]

🎉 This issue has been resolved in version 5.8.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀