Open
Conversation
Owner
|
Does your patched variant work with IPv4 as well? |
Contributor
Author
|
As long as IPv6 hasn't been disabled in the kernel configuration, it should still "just work", even if no IPv6 addresses have been assigned to interfaces. I've found this to be true in my testing on raspberrian stretch (4.14.87), even when disabling IPv6 via sysctl https://www.techrepublic.com/article/how-to-disable-ipv6-on-linux/ A discussion of why this works is on https://unix.stackexchange.com/questions/237731/why-are-ipv4-tcp-connections-showing-as-tcp6 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I ran into an issue with streameye, where I could view the streams in a normal web browser, but adding them via hostname to motion wasn't working. Further investigation showed that adding the stream by IPv4 address did work, but that adding by hostname wasn't working because motion supports IPv6, and wasn't falling back to IPv4 as we web browser did.
I therefore present a trivial patch to support IPv6. If I really wanted to be fancy, I'd have added a command-line option to allow specifying IPv4 or IPv6, but it's simpler to just leave that to iptables or perhaps another patch.