-
-
Notifications
You must be signed in to change notification settings - Fork 90
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
[FEAT] IPv6 Support #246
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
IPv6 support isn't related to the container but rather to the setup of your docker install. Nothing should need to be added to the container for it to work (unless tvheadend doesn't support it). |
The container (as I said) has an IPv6 address my setup is correct as I can ping it's IPv6 address from another container. Inside the container the tvheadend application is only listening on IPv4. I can run "nc -l6 -p 9123" inside the container and connect via IPv6 and see it's listening on IPv6. See below
|
Actually I've managed to make this work. I just had to pass a command line arg to the docker run to force tvheadend to listen on IPv6 in the container. Will close and leave here in the hope this is useful to someone else. Thanks for the attention. |
Is this a new feature request?
Wanted change
The container seems to support IPv6 (well the interfaces pick up an IPv6 addresses in the container) , but the application itself doesn't allow being connected to from IPv6. I also presume (though I don't really use this functionality) that outbound to the Internet from TVheadend will be IPv4.
Though I don't know if TVheadend itself supports IPv6, though I think it does.
Reason for change
Future proofing and consistency with every other application.There is also the minor issue that in an IPv6 environment IPv6 is always tried first by clients and they have to drop back to IPv4, this is slight slow down.
Proposed code change
No response
The text was updated successfully, but these errors were encountered: