![]() ![]() There must be some obscure thing happening if UMS is initialized in IPv6 mode before switching to IPv4 that influences the connection with the PS4. There must be something else going on, as UMS will enable it again. It's still impossible to ignore that so many of you have reported that turning off IPv4 for Java has helped with the issue. ![]() ![]() That will result in UMS not being able to "see" the renderers and vice versa. The reason for this is very simple: as UMS only supports UPnP on IPv4 and so does most UPnP/DLNA devices, we don't want Java to only use IPv6 if both IP stacks are available. What is a mystery to me is how this can make any difference, as I'm very sure that I remember that UMS sets this to "true" during initialization anyway, overriding the value you might set at launch. IPv6 support was added to the DLNA specification in the 2016 revision, and our UPnP library doesn't support IPv6 either. UMS doesn't support IPv6, neither do most of the renderers out there. "ist" is an OS X specific file, so it doesn't exist on other platforms. This setting can be be to either "true" or "false" when launching Java (from the command line) or from a script. To clear up some confusion, "4Stack=true" is a Java setting that tells the Java Virtual Machine (which runs UMS) to prefer IPv4 over IPv6 if both are available. I've just read through this thread, and my conclusion (I don't have a PS4 for testing) is that this is most likely a network configuration issue.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |