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=1610113941; bh=YB/z3DuhwLT+PKgeK9jr6HG7BqGrcr02YyiJlVNPFnQ=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=L0BV7lpi3S5H9F/cIl7THtTv6nqA0DC+2gEGZyNL15QsS2At1JhsiFHrNUcCh2IRa WCBV8DivW1cIwSMcSHJIXSFI2CG3k4S06+zPHmxE6YMg1V06y0yByXfYctEuTc+Ko1 YXIOhdEfJfp/4XbhLPL7MOnu2jkeL6q2yj030OByvQx6lhFC2JjKUdsVf5Dx3fYMwo 430MQIIZ93kEvfDk9VWnj5FbqkKynHZaKXgxfmsSYvnltrH2qXo03SklkbDppPfn1g k2JISU1XPpKPkuz44bsjq+ADNYRgmMYUoeNT47kxKpyAxdJUarMaoirxR84fnGvclI +XsGMhlNERONw== To: Juliusz Chroboczek In-Reply-To: <87v9c77e20.wl-jch@irif.fr> References: <875z485swt.wl-jch@irif.fr> <87wnwnha9w.fsf@toke.dk> <87v9c77e20.wl-jch@irif.fr> Date: Fri, 08 Jan 2021 14:52:21 +0100 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87turrh6y2.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Message-ID-Hash: C2M6BNPU6SYGHMSJFH3YNM6TSPVYISQM X-Message-ID-Hash: C2M6BNPU6SYGHMSJFH3YNM6TSPVYISQM 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: Logging 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: >> Which doesn't really tell me much. What's happening here, is the Turn >> server working? > > The direct connection was successful, so the TURN server was never > contacted. Right, I see. What are the conditions where a direct connection fails? Is it just when the client is behind a NAT? >> What's with the remote candidates being ignored? > > They're active TCP candidates, and I've disabled support for ICE-TCP in G= al=C3=A8ne: > > https://github.com/pion/webrtc/issues/1356 > > ICE-TCP has the potential to make TURN redundant, so it would greatly > simplify the deployment of Gal=C3=A8ne. Unfortunately, I've found it to = be > unreliable in Pion, so I've disabled it until I can find the time to work > out what the issue is. Right, gotcha. >> What would be most useful in terms of checking configuration is if >> Galene would *on startup* emit something like: > >> Checking Turn server candidate turn.example.com:443?transport=3Dtcp: suc= cess! > > Ah. What you want is not logging, but active monitoring. Well, both, ideally :) As for just logging, Galene does propagate JSON parsing errors from the Go JSON parser, but because the files are not read on startup you can start up the daemon and everything looks fine until someone tries to connect... > Could you please file an issue? Sure: https://github.com/jech/galene/issues/30 -Toke