You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi
We have observed some random UDP port is getting started along with Janus Server. Have already checked the code but not able to locate any such code who is opening this port.
We are testing with janus 3.8.7-6878f19
[fedora@robs-2018 APIGateway]$ ./janus_linux-amd64 version
janus 3.8.7-6878f19
with a sample janus.toml as
################################################################
Global configuration
################################################################
port = 8080
[log]
level = "debug"
format = "text"
################################################################
API configuration backend
################################################################
[web]
port = 8081
[web.credentials]
The algorithm that you want to use to create your JWT
algorithm = "HS256"
This is the secret that you will use to encrypt your JWT
[fedora@robs-2018 RCP2.0]$ netstat -lanp | grep 30930
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp6 0 0 :::8081 :::* LISTEN 30930/./janus_linux
tcp6 0 0 :::8080 :::* LISTEN 30930/./janus_linux udp6 0 0 :::42106 ::: 30930/./janus_linux*
Q: Who is opening this UDP socket and Why and how can we close it . I assume it is still in RC and not yet released one.
Q: The other questions is we are planning to use Janus in our project but not sure how widely it is used and also as the project is moved to maintenance mode how about critical BUG support ?
I appreciate currently how it is developed and all features it supports currently but e.g TLS mode does not take the port mentioned in [TLS] field but from Global Config as listener seems to be created before this check, like this one.
Thanks in Advance
Swanand
The text was updated successfully, but these errors were encountered:
Hi
We have observed some random UDP port is getting started along with Janus Server. Have already checked the code but not able to locate any such code who is opening this port.
We are testing with janus 3.8.7-6878f19
[fedora@robs-2018 APIGateway]$ ./janus_linux-amd64 version
janus 3.8.7-6878f19
with a sample janus.toml as
################################################################
Global configuration
################################################################
port = 8080
[log]
level = "debug"
format = "text"
################################################################
API configuration backend
################################################################
[web]
port = 8081
[web.credentials]
The algorithm that you want to use to create your JWT
algorithm = "HS256"
This is the secret that you will use to encrypt your JWT
secret = "secret key"
[web.credentials.basic]
A dictionary with the user and password
users = [{admin = "admin"}]
[database]
dsn = "file:///etc/janus"
Reproduction Steps:
./janus_linux-amd64 start -c janus.toml
[fedora@robs-2018 RCP2.0]$ ps -eaf | grep janus
fedora 30930 25242 0 09:59 pts/4 00:00:00 ./janus_linux-amd64 start -c janus.toml
[fedora@robs-2018 RCP2.0]$ netstat -lanp | grep 30930
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp6 0 0 :::8081 :::* LISTEN 30930/./janus_linux
tcp6 0 0 :::8080 :::* LISTEN 30930/./janus_linux
udp6 0 0 :::42106 ::: 30930/./janus_linux*
Q: Who is opening this UDP socket and Why and how can we close it . I assume it is still in RC and not yet released one.
Q: The other questions is we are planning to use Janus in our project but not sure how widely it is used and also as the project is moved to maintenance mode how about critical BUG support ?
I appreciate currently how it is developed and all features it supports currently but e.g TLS mode does not take the port mentioned in [TLS] field but from Global Config as listener seems to be created before this check, like this one.
Thanks in Advance
Swanand
The text was updated successfully, but these errors were encountered: