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=1611056839; bh=FFxR/72wlVkNajLYIEmyUQyX/8X5DwTpLe2VH1yXB8s=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=L2HMgGk130j+0vYjx7HCBIaWehH0Q291M8bJGb67lOPCHTF6mbTY/CkKxDGAOiDw4 MXw7e7HnBcMYViq09iVL3BtM0uN0qBbIxDEMsvWJxxDDW7J7oQvPZBFyQdX0ZrQtxY pqjKoVm3Qx0ejY1Qm+7pB8b88WisFWVq+AaLdIw3ShapuKckCZwHb3dKc0OQlMqALe 1no1dRL1L56ozqxx/DqJnjR3KKOLt9NwtFXxoo841wMrUKFF/W+dYhJTf8ACg9Ptkv Iha4B15AbZdpOkByI3tEkV5BbhebHhuKn0d79EonWd3Qufd2SRYpBaLS61L2NRq2wZ 8B7uEln297H/w== To: Juliusz Chroboczek In-Reply-To: <877do9ydvi.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> <87o8hlridf.fsf@toke.dk> <87eeihyipm.wl-jch@irif.fr> <87lfcprgl4.fsf@toke.dk> <877do9ydvi.wl-jch@irif.fr> Date: Tue, 19 Jan 2021 12:47:17 +0100 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <875z3tqhbu.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain Message-ID-Hash: 24E37O5O3YGNXXGJXWXCG3HDOBIA6YAS X-Message-ID-Hash: 24E37O5O3YGNXXGJXWXCG3HDOBIA6YAS 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: > Ok, I disagree with you guys, but I've done as you say. > > The built-in TURN server will be disabled by default if there's an > ice-servers.json file (even if it's empty or otherwise malformed). This > won't happen if the -turn option has been explicitly specified on the > command-line. That sounds reasonable, thanks :) > The server should be started if the ice-servers.json file disappears, but > I haven't actually tested that it works, and haven't written any unit > tests. It does appear to, once someone enters a conference: root@video:/var/lib/galene# ss -ntpl | grep galene LISTEN 0 128 *:443 *:* users:(("galene",pid=793998,fd=6)) root@video:/var/lib/galene# ss -nupl | grep galene root@video:/var/lib/galene# mv data/ice-servers.json . root@video:/var/lib/galene# ss -ntpl | grep galene LISTEN 0 128 *:443 *:* users:(("galene",pid=793998,fd=6)) root@video:/var/lib/galene# ss -nupl | grep galene So nothing, but after entering a conference and turning on video it does appear to enable itself: root@video:/var/lib/galene# ss -nupl | grep galene UNCONN 0 0 45.145.95.8:1194 0.0.0.0:* users:(("galene",pid=794316,fd=9)) It even turns itself off again if I restore the file: root@video:/var/lib/galene# mv ice-servers.json data/ (enter conference) root@video:/var/lib/galene# ss -nupl | grep galene > That's way more magic than I like, but perhaps you guys are right. > I sincerely don't know. I like it - "sufficiently advanced technology being indistinguishable from magic" and all that :) -Toke