ICE authenticator through a container

[Silmerias]

Hey, we originally bundeled the ice authenticator we made in python in the murmur docker, which is to me a bad practice but we had hard time to make it work outside the container as ice on murmur side is opening a random port instead of using the declared one for communication which end up with a timeout.

I am trying to make this work again and separate murmur and the ice auth however the only solution I found is to use the host network instead of the separated one, which I do not really like. Do you guys have any advice to make this work?

[Krzmbrzl]

Iirc there should be a config option to specify what port Ice should bind to 🤔

[Silmerias]

You mean via this murmur config?

ice="tcp -h 10.0.0.1 -p 6502

<W>2023-12-14 18:29:30.921 MumbleServerIce: Endpoint "tcp -h 10.0.0.1 -p 6502 -t 60000" running

The authenticator is configured like this:

[ice]
host = 10.0.0.1
port = 6502

2023-12-14 18:46:57,888 INFO Starting SSO Authenticator
2023-12-14 18:46:57,890 INFO Connecting to Ice server (10.0.0.1:6502)

Basically, when the authenticator connect to murmur via ice it also do this :

<W>2023-12-14 18:39:09.844 Added Ice MetaCallback 06601E01-21BB-42CB-A427-E5060B890009 -o -e 1.0:tcp -h 10.0.0.1 -p 34791 -t 5000
<W>2023-12-14 18:39:09.855 1 => Set Ice Authenticator to 218F2643-C47D-45D2-84C9-788269580009 -t -e 1.0:tcp -h 10.0.0.1 -p 34791 -t 5000
<W>2023-12-14 18:39:09.863 1 => Set Ice UpdatingAuthenticator to 218F2643-C47D-45D2-84C9-788269580009 -t -e 1.0:tcp -h 10.0.0.1 -p 34791 -t 5000

It open random port like 34791 here locally murmur side that can't be reach from ther authenticator as this is not exposed from docker.

[Krzmbrzl]

Ah so the issue is that the authenticator is binding to a random port? The authenticator is an external component and therefore not immediately related to the server, no?
If so, I can't help you with that as I have never used an Ice authenticator. But maybe checking its sources give insights in what it is doing and why it is binding to that port 👀

[Kissaki]

as ice on murmur side is opening a random port instead of using the declared one for communication which end up with a timeout

I don't think that is correct.

Mumble server binds the configured Ice port.

Did you configure the docker container to open and route the port - and do so between your two containers?

See our mumble-docker repository at https://github.com/mumble-voip/mumble-docker with more information.

Mumo docker docs also mentions this use case of two docker containers, and the need to connect the containerized network via docker configuration: https://github.com/mumble-voip/mumo/blob/master/docker.md