IPv4 support

[barbe...@gmail.com]

Hi,

I want to use KMS in a company Network and it only support ipv4 atm.

KMS only start on tcp6 :::8888 .

But I need it on tcp.

Is there any configuration option (in kms or on system level) that force kms to bind 0.0.0.0 or a specified ipv4 ?

Greetings

[Jose Antonio Santos Cadenas]

It should be working on ipv4 out of the box. Have you tested it?

--
You received this message because you are subscribed to the Google Groups "kurento" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kurento+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[barbe...@gmail.com]

Yes I tested it.

netstat:

tcp6       0      0 :::8433                 :::*                    LISTEN      1000       836382350   540/kurento-media-s

tcp6       0      0 :::8888                 :::*                    LISTEN      1000       836382313   540/kurento-media-s

{

  "mediaServer" : {

    "resources": {

    //  //Resources usage limit for raising an exception when an object creation is attempted

    //  "exceptionLimit": "0.8",

    //  // Resources usage limit for restarting the server when no objects are alive

    //  "killLimit": "0.7",

        // Garbage collector period in seconds

        "garbageCollectorPeriod": 240

    },

    "net" : {

      "websocket": {

        "port": 8888,

        "secure": {

          "port": 8433,

          "certificate": "default.pem",

          "password": ""

        },

        //"registrar": {

        //  "address": "ws://localhost:9090",

        //  "localAddress": "localhost"

        //},

        "path": "kurento",

        "threads": 10

      }

    }

  }

}

[Ivan Gracia]

It should also bind to IPv4 address 0.0.0.0, that's weird. 

Ivan Gracia

--

[Jose Antonio Santos Cadenas]

It is binded, but the OS does show it that way  http://unix.stackexchange.com/questions/152612/netstat-why-are-ipv4-daemons-listening-to-ports-listed-only-in-a-inet6. Pleas check that you can do a telnet to that port using ipv4 is possible. I know that, because I normally use IPv4 not IPv6. Please, check things correctly before reporting errors.

Cheers.

[barbe...@gmail.com]

I got it.
My certificate for kms was broken ...

In the kms log was a certificate error and with a New one it works.
The Problem is that netstat show 8443 and 8888 AS open, but 8443 didn't respond to telnet(8888 dies respond).
With WS it didn't works in chrome with a remote server. You need wss .

Maybe someone could change the reaktion from kms it possible so that it didn't shiw open the secure port in netstat if the SSL cert got issues.

The current hello world JS example also referes to wss in port 8443,but kms didn't serve 8433 by default.
I need to enable it in the config and generate a certificate.
It would be nice if someone could at a note for starters like me that the example didn't works with default config.

[Radu Burlacu]

Any update on this? Is it possible to set kurento to start on ipv4?

[Yas]

We've disabled IPV6 in GRUB as follows:

GRUB_CMDLINE_LINUX="ipv6.disable=1"

Now, Kurento is not starting and gives this error message:

WebSocketTransport()  Error starting listen for websocket transport on port 8888: Underlying Transport Error

[Andrey K]

Confirming this weird behavior on Ubuntu 16.04, kurento binds only to tcp6

[Andrey K]

Made clean Ubuntu 16.04 VM, now it works. netstat shows the same tcp6 binding, but telnet ip 8888 works.

понедельник, 16 апреля 2018 г., 23:36:46 UTC+3 пользователь Andrey K написал: