# NR "needs" IPv6?

**URL:** <https://discourse.nodered.org/t/nr-needs-ipv6/74034>\
**Category:** General\
**Tags:** docker\
**Created:** [22 January 2023 05:06 UTC](https://discourse.nodered.org/t/nr-needs-ipv6/74034 "2023-01-22T05:06:55Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![LosinIt](https://avatars.discourse-cdn.com/v4/letter/l/439d5e/32.png) [@LosinIt](https://discourse.nodered.org/u/LosinIt)\
**Post date:** [22 January 2023 05:06 UTC](https://discourse.nodered.org/t/nr-needs-ipv6/74034/1 "2023-01-22T05:06:55Z")

</div>

I have been running NR in Docker for over 3 years and never once had a problem with outbound connections until today when I disabled IPv6 in the host's kernel. After doing so I found that all outbound IP connections from nodes AND the palette manager failed with a EAFNOSUPPORT error.

I searched for reasons this might happen with NR, Docker, and npm and found nothing. Re-enabling IPv6 in the kernel restored normal operations.

What is up with this?

I had disabled IPv6 on all 11 of my systems and this was the only case where it broke something.

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [22 January 2023 14:14 UTC](https://discourse.nodered.org/t/nr-needs-ipv6/74034/2 "2023-01-22T14:14:36Z")

</div>

Node-RED does not need IPv6 to the best of my knowledge. Much more likely that it is a Docker configuration issue I would think.

Node-RED is built using node.js and I've not found any specific IPv6 issues on node.js other than the issues that IPv6 itself brings to everything.

---

<div class="post-metadata">

**Author:** ![LosinIt](https://avatars.discourse-cdn.com/v4/letter/l/439d5e/32.png) [@LosinIt](https://discourse.nodered.org/u/LosinIt)\
**Post date:** [22 January 2023 14:34 UTC](https://discourse.nodered.org/t/nr-needs-ipv6/74034/3 "2023-01-22T14:34:47Z")

</div>

> [@TotallyInformation](#):
>
> Much more likely that it is a Docker configuration issue I would think.

I had the same thought but found nothing when I looked last night. This morning, being properly caffeinated, I find that it _was_ an issue a couple years ago but it shouldn't be at this point.

> <https://github.com/moby/moby/pull/42412>
>
> supersedes https://github.com/moby/moby/pull/42322
> closes https://github.com/mo…by/moby/pull/42322
> 
> Update libnetwork to make \`docker run -p 80:80\` functional again on environments
> with kernel boot parameter \`ipv6.disable=1\`.
> 
> full diff: https://github.com/docker/libnetwork/compare/b3507428be5b458cb0e2b4086b13531fb0706e46...64b7a4574d1426139437d20e81c0b6d391130ec8
> 
> \- fix port forwarding with ipv6.disable=1
> - fixes https://github.com/moby/moby/issues/42288 Docker 20.10.6: all containers stopped and cannot start if ipv6 is disabled on host
> - fixes https://github.com/moby/libnetwork/issues/2629 Network issue with IPv6 following update to version 20.10.6
> - fixes https://github.com/docker/for-linux/issues/1233 Since 20.10.6 it's not possible to run docker on a machine with disabled IPv6 interfaces
> - relates to https://github.com/nginx-proxy/nginx-proxy/issues/1589 \[BUG\] Latest image - ENABLE\_IPV6 not being honored?
> - relates to https://github.com/elabftw/elabftw/issues/2601 errors when restarting elabftw
> - relates to https://forums.docker.com/t/ipv6-disabled-on-my-computer-but-docker-network-seems-looking-for-it/107299
> - relates to https://github.com/jc21/nginx-proxy-manager/issues/1026 Docker 20.10.6 breaks IPV6
> - relates to https://github.com/aws/amazon-ecs-agent/issues/2870 Docker 20.10.6 IPv6 bindings shouldn't be mapped as network bindings for tasks for non IPv6 networks
> \- vendor: github.com/ishidawataru/sctp f2269e66cdee387bd321445d5d300893449805be
> \- Enforce order of lock acquisitions on network/controller, fixes #2632
> - fixes https://github.com/moby/libnetwork/issues/2632 Name resolution stuck due to deadlock between different network struct methods
> - fixes https://github.com/moby/moby/issues/42032 Docker deamon get's stuck, can't serve DNS requests
> 
> vendor: github.com/ishidawataru/sctp f2269e66cdee387bd321445d5d300893449805be
> 
> full diff: https://github.com/ishidawataru/sctp/compare/6e2cb1366111dcf547c13531e3a263a067715847...f2269e66cdee387bd321445d5d300893449805be
> 
> \- support SO\_SNDBUF/SO\_RCVBUF handling
> \- Support Go Modules
> \- license clarificaton
> \- ci: drop 1.6, 1.7, 1.8 support
> \- Add support for SocketConfig
> \- support goarch mips64le architecture.
> \- fix possible socket leak when bind fails
> 
> 
> \*\*- Description for the changelog\*\*
> \<!--
> Write a short (one line) summary that describes the changes in this
> pull request for inclusion in the changelog:
> \--\>
> 
> 
> \*\*- A picture of a cute animal (not mandatory but encouraged)\*\*

In the mean time, I changed my strategy for disabling IPv6. Instead of disabling in the kernel I've just disabled DHCPv6 service on OPNsense so only the default addresses get generated on each host.

If/when I find something more enlightening I'll post here.

Thanks for the replay, @TotallyInformation

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [23 March 2023 14:34 UTC](https://discourse.nodered.org/t/nr-needs-ipv6/74034/4 "2023-03-23T14:34:47Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.