-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable IPv6 support by default #167
Comments
Yeah, this was in my long TODO list. Ideally we should detect if IPv6 support is available on the system and enable it accordingly at configure time. Shouldn't be too hard to do. Either way, we may want to allow users to disable IPv6 in the dillorc configuration at runtime, as it may cause connection delays while we fallback to IPv4 in some networks that don't support IPv6. |
Thank you; I'm sorry to dump more on but figured we could at least track it as an eventual TODO. Great work on getting the new release out the door! A runtime switch might be even better; we could have it on by default (or at least easily switchable without needing to rebuild). Thanks! |
Please don't implement this via configure automagic. IPv6 is one of those features that should just be turned on by default, relying on runtime logic to determine whether or not IPv6 is suitable. |
I don't mean to detect if IPv6 is enabled in the network if that is your worry. By "available on the system" I mean if At runtime, I plan on adding a switch in the dillorc configuration file, as sometimes it is required to turn off IPv6, even if it is available. I need to do more testing to determine if we can switch it on by default at runtime (at build time there is no problem), as I remember this could cause an unexpected long delay on the DNS resolver until if fails back to IPv4, and novice users will have a hard time figuring out this is caused by IPv6. |
This is a feature enhancement request. I am using a device (macOS) that is IPv6-only, and testing Dillo as installed with homebrew. Homebrew uses the default compilation options, which do not include IPv6 (
configure.ac
requires a flag to enable IPv6, and this is not on by default).With IPv6 becoming more prevalent (and in Apple's case, mandatory), could you invert the configuration so that IPv6 is enabled by default, and can only be disabled by passing a flag? That would prevent downstream package managers from having to add the flag to each of their build scripts.
If IPv6 support is not fully tested or ready for default deployment, then I completely understand and I can build my own manually with support enabled.
The text was updated successfully, but these errors were encountered: