Question / Help No IPv6 support?

[MadMakz]

It looks like OBS and OBS-Studio can't handle IPv6 connections?

I recive a

Problem accessing the DNS. (addr: <IPv6 only Domain>, error: 11004)

Error.

Is it planned to have IPv6 support any time in the future?
There are a lot Internet-over-Cable Companies using a Technologie called DualStack-Lite where the IPv4 is tunneled over IPv6 with a NATed/Shared IPv4 endpoint due to the fact they don't have anough IPv4 adresses anymore.

However, on some providers this is complete crap as these AFTR-Routers/technology are mostely overloaded or the Tunnel is damn unstable makeing it impossible to stream without drops.
The Companies don't care since "you don't loose the complete internet". So it's not covered by their SLAs
On the other hand,IPv6 runs native an thus is stable, Transparent, and dedicated to a single Client only.

But aside from this Problem, it think IPv6 should be natively in OBS anyway since it became a normal internet standart like IPv4.

 

[R1CH]

This will be included at some point, it does involve some reworking of librtmp however. I'll try to work in this in OBS when I have some free time.

 

[MadMakz]

Thanks for the fast response R1CH :)

I and probably many other streamers, at least in my country, hope this'll be sooner than later.

 

[R1CH]

You're in luck :). https://github.com/jp9000/OBS/commit/9f0503a

 

[MadMakz]

Holy crap hell! That was awesome fast! That's some unique effort there :O Thanks a lot :)

Now we just need to wait for a new build^^

 

[MadMakz]

Just wanted to let you know that IPv6 is working fine so far :)

 

[R1CH]

Thanks for the update, I couldn't find any IPv6 services to stream to so I wasn't able to make a good test.

 

[gdlk]

Thanks for the update, I couldn't find any IPv6 services to stream to so I wasn't able to make a good test.

Hello,
I have a problem using ipv6 address in FMS URL:
rtmp://[2002:5f44:fdf5:1::1]:1935/transcode
Then i start streaming i'm getting message:
06:10:31: librtmp error: Could not resolve [2002: ���� ���� ����������. (11001)
06:10:31: Connection to rtmp://[2002:5f44:fdf5:1::1]:1935/transcode failed: Could not connect to server

However if i'm using hosts file to define name for ipv6 all working fine. Something like that:
Hosts:
2002:5f44:fdf5:1::1 ipv6server
FMS URL: rtmp://ipv6server:1935/transcode all working fine.

 

[gdlk]

Hello,
I have a problem using ipv6 address in FMS URL:
rtmp://[2002:5f44:fdf5:1::1]:1935/transcode
Then i start streaming i'm getting message:
06:10:31: librtmp error: Could not resolve [2002: ���� ���� ����������. (11001)
06:10:31: Connection to rtmp://[2002:5f44:fdf5:1::1]:1935/transcode failed: Could not connect to server

However if i'm using hosts file to define name for ipv6 all working fine. Something like that:
Hosts:
2002:5f44:fdf5:1::1 ipv6server
FMS URL: rtmp://ipv6server:1935/transcode all working fine.

Maybe i'm using wrong url then i'm trying ipv6 address?

 

[Boildown]

Do you have to have the square brackets around the IPv6 address? Just a guess.

 

[R1CH]

The IPv6 support requires hostnames for now, it does not parse literal IPv6 addresses.

 

[gdlk]

Do you have to have the square brackets around the IPv6 address? Just a guess.

Yes ipv6 URL requires brackets around. RFC 2732 (https://www.ietf.org/rfc/rfc2732.txt):

2. Literal IPv6 Address Format in URL's Syntax

To use a literal IPv6 address in a URL, the literal address should be
enclosed in "[" and "]" characters. For example the following
literal IPv6 addresses:

FEDC:BA98:7654:3210:FEDC:BA98:7654:3210
1080:0:0:0:8:800:200C:4171
3ffe:2a00:100:7031::1
1080::8:800:200C:417A
::192.9.5.5
::FFFF:129.144.52.38
2010:836B:4179::836B:4179

would be represented as in the following example URLs:

http://[FEDC:BA98:7654:3210:FEDC:BA98:7654:3210]:80/index.html
http://[1080:0:0:0:8:800:200C:417A]/index.html
http://[3ffe:2a00:100:7031::1]
http://[1080::8:800:200C:417A]/foo
http://[::192.9.5.5]/ipng
http://[::FFFF:129.144.52.38]:80/index.html
http://[2010:836B:4179::836B:4179]

The IPv6 support requires hostnames for now, it does not parse literal IPv6 addresses.

Thank you for answer! Hope it will be in later builds.

 

[Boildown]

Yes ipv6 URL requires brackets around. RFC 2732 (https://www.ietf.org/rfc/rfc2732.txt):

Fascinating, I hadn't heard of this before, thanks!