-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Labels:
-
0.25
Summary
Setting net.ipv6 directs the mongod/mongos to generally support IPv6 addressing, such as resolving DNS hostnames to IPv6 or outgoing connections to remove IPv6 hosts (e.g. other replica set members).
However, the mongod/mongos will *not* auto-bind to any local IPv6 addresses or interfaces. If user's want the mongod/mongos to listen on an IPv6 interface, they must set
net.ipv6 to true and set at least one valid IPv6 address in net.bindIp (or set net.bindIpAll : true.
One caveat - if the user wants the mongod/mongos to listen on a link-local address fe80::/10, when specifying the address they must append a % followed by the network adapter name associated to that address (fe80::a00:27ff:fee0:1fcf%enp0s3.
Original Description
According to changes going in for DOCSP- , jonathan.balsano indicated that if a user sets net.ipv6 for a MongoDB deployment, they also need to set net.bindIp (or, presumably, net.bindIpAll.
Please add that condition to net.ipv6.
Scope of changes
Update documentation for net.bindIp with basic instructions on setting IPv6 addressing and relationship with net.ipv6.
Update documentation on net.ipv6 to explicitly state that it does not automatically direct the mongod/mongos to accept incoming connections via IPv6 addresses.