[SERVER-25836] net.ipv6 still used in 3.2.9 whereas doc says it's removed and useless. Created: 27/Aug/16 Updated: 20/Feb/17 Resolved: 31/Aug/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking |
| Affects Version/s: | 3.2.9 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Adrien Jarthon | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
I'm a bit confused here, there's not much information about using mongodb with ipv6 the only one I read in the doc seems to be wrong, here is what the doc (https://docs.mongodb.com/manual/reference/configuration-options/) says:
So as I'm using 3.2.9, I understand this option no longer exists and ipv6 is enabled by default. But ipv6 is not working for me, and when I tried setting this options after hours of debugging, I actually found it to be working ☹:
without the option
with the option
So what's the problem, did I misunderstood something ? is it a bug ? is the doc wrong or the code wrong ? I'll of course use this option in the meanwhile but I would like to save the next persons to have this issue a few hours of their life And I would also make sure that If I start using this option it won't break my config at some upgrade once it's removed for real. |
| Comments |
| Comment by Geert Hendrickx [ 20/Feb/17 ] |
|
@Thomas Schubert, Alternatively, isn't it about time to just enable IPv6 by default in mongod/mongos and shell as well? |
| Comment by Kelsey Schubert [ 06/Sep/16 ] |
|
Yes, that's correct, bigbourin@gmail.com. |
| Comment by Adrien Jarthon [ 31/Aug/16 ] |
|
Hi Thomas, Ok so this is just a documentation issue then, I can keep using this option without any risk? Thanks! |
| Comment by Kelsey Schubert [ 31/Aug/16 ] |
|
Thank you for bringing this to our attention. This is an issue with our documentation resulting from a change in Best regards, |