From mboxrd@z Thu Jan 1 00:00:00 1970 From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1611008828; bh=7zEQQXKBZFDhy8o5ZPkY/K2hyB17o+cy0GckKkm8yMQ=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=j9wqn2gkMBPu8ZcCryakZ4seUJvKgOIYLIO5pP4H6ZU7EIR2eH1JjZbdzPsV2Un4F 3Ce0WGe0DhPsoeQb9LejRfs0gE+RMerPkwAx9oLi9Ax7VWMq6pixCHN9FozuuLQjlP NR2LhobBfn0DIJN0NggFWs+04fYMmahUhjqcbWsumiBhOdjliX8eGbTH5OQGR7zsgI 9grNvAO1i1XPcR2ojRG6+tUZecKr3i4Pkk+cd33anle1wM9fK4l40jCW2UCbcOCRle +sD3yZt8weM+VnfCCoMYO23UqzDnQbPZPLwoRNSTlnEosX1Sxfv4h+DeHJ2V0NwvTA I0nqBAUhM7R9w== To: Juliusz Chroboczek In-Reply-To: <87mtx5yk96.wl-jch@irif.fr> References: <87sg6yx7gy.wl-jch@irif.fr> <87zh16q61v.fsf@toke.dk> <87pn21yl6t.wl-jch@irif.fr> <87wnw9rjw7.fsf@toke.dk> <87mtx5yk96.wl-jch@irif.fr> Date: Mon, 18 Jan 2021 23:27:08 +0100 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87o8hlridf.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Message-ID-Hash: 665YQKCOEKWRMQLJGBUJ3VSPHO3N3TN4 X-Message-ID-Hash: 665YQKCOEKWRMQLJGBUJ3VSPHO3N3TN4 X-MailFrom: toke@toke.dk X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header CC: galene@lists.galene.org X-Mailman-Version: 3.3.2 Precedence: list Subject: [Galene] Re: Heads-up: built-in TURN server List-Id: =?utf-8?q?Gal=C3=A8ne_videoconferencing_server_discussion_list?= Archived-At: List-Archive: List-Help: List-Post: List-Subscribe: List-Unsubscribe: Juliusz Chroboczek writes: >>>> Is there any benefit to switching to the built-in one if I already have >>>> a working setup with an external TURN server? > >>> None at all, and you'd lose IPv6 support. > >> In that case, would it not be better to only start up the built-in TURN >> server if no explicit turn server config is present, instead of >> requiring a command-line option to turn it off? > > If the built-in server is enabled, it will be injected at the end of the > ICE configuration, your external server will be used first, with fallback > to the built-in server if connectivity cannot be established through the > external server. > > If the built-in server is enabled and uses the same port as your external > server, then the bind() call will fail (EADDRINUSE), you'll get a friendly > log message, and the built-in server will be disabled. > > The only troublesome case is if the ports are the same, and Gal=C3=A8ne is > started before the external TURN server, in which case the external TURN > server won't be able to bind its ports. > > I find the current behaviour simpler to explain than what you suggest, and > I'm trying to optimise for simplicity. I'm open to different opinions, > though, especially if you find any catastrophic failure modes with the > current defaults. What about when the external TURN server is on a different IP, so Galene has no problem starting up the internal one, but it's firewalled off to clients can't connect to it? In that case presumably it'll just be another TURN candidate offered to clients which will fail? Isn't that bad for latency (I think Firefox emits a warning recommending a max of two candidates)? -Toke