The VideoLAN Forums

Looks like the url parser in live555.cpp is confused by the square-brackets of an ipv6 address (thinks its the password or something) causing a bad url to be generated, which cannot be connected to. live555 debug: version 2016.11.28 live555 debug: connection timeout live555 error: Failed to connect ...

Further information: VLC is using the "satip" demux for IPv6 addresses like the one I entered above, which seems to be some kind of pseudo-RTSP protocol. Not sure why it thinks this though.

Sorry but I still do not understand. Are you saying this syntax is not compatible, somehow:

rtsp://[2002:4998:30:1e1:b6e7:50e5:8443:8bef]:12345/camera

which is identical to a valid http url except for the scheme. Or do you mean something else for the protocol syntax?

How so, exactly, is it incompatible? RFC 2326 mentions IPv6 and there are no explicit differences called out.
The Live555 server works on IPv6 (see http://live555.com/mediaServer/release.html), for example, as does my server, and the VLC client looks like it could with a few fixes.

To be more specific: VLC network stream playback on IPv4: sends OPTIONS sends DESCRIBE sends SETUP with a media url from the SDP for video (server returns session id) sends SETUP with media url for audio sends PLAY with the base url and the session returned from SETUP All good. VLC on IPv6: no OPTIO...

Old thread I know, but what exactly is incompatible with RTSP over IPv6? I have it working just fine with my own client, but VLC (Windows 3.0.14) chokes when trying to playback from an RTSP server on an IPv6 address. Doesn't even bother to do a DESCRIBE to get the SDP, just sends a SETUP with a bad ...