-
Notifications
You must be signed in to change notification settings - Fork 344
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
Add IPv6 support to WebRTC #721
Comments
Turns out that 8554 is my mistake. That's the RTSP listener which works correctly for IPv6. |
This commit broke my go2rtc: I wonder why this commit was made..? |
This restore commit is unfortunately incomplete: 189f142 |
Yeah. In 2023 it's hard to get IPv6 working in my country. Never seen it working :) PS. Commit was made for saving resources on unnecessary IPv6 binding for simple home usage. |
confirmed webrtc doesn't work with ipv6. i was wondering why I was having issues! @AlexxIT perhaps a toggle to enable or disable ipv6 completely would be useful to save resources for certain situations? In my situation I would disable ipv4 completely =D |
I just need to find a way to test IPv6 live. I think go will only bind to available interfaces. Or you can use |
I don't think that currently works, [::] cannot bind if you ask for "tcp4" in webrtc.go |
@AlexxIT you can try tunnelbroker.net to get a free tunnel which will give you an ipv6 address you can use over an ipv4 connection, for your testing |
You can also test local IPv6 by setting up radvd to use a site-local prefix (for example fc42:a1e4:417::/64 ), to prevent it from setting a default route, set AdvDefaultLifetime to a value of 0. That way you get local IPv6 in your network, without it affecting other connections. Of course the tunnelbroker solution is a better one, that way you get full IPv6 access. |
If you need another tester for IPv6 related functionality i can assist aswell. I've got global IPv6 access from my ISP currently since a year and a half back :D |
You can test it if you want. This feature was fixed in previous releases |
I run go2rtc on an IPv6-only home assistant, and go2rtc webrtc port does not bind to IPv6 on port 8555, which it should in 2023, when the world has run out of IPv4 and I am definitely too poor for IPv4.
I've tried:
But it simply refuses to listen on IPv6 since 1.8.1.
The text was updated successfully, but these errors were encountered: