From: Juliusz Chroboczek <jch@irif.fr>
To: galene@lists.galene.org
Cc: pabr2749409@pabr.org
Subject: [Galene] Redesigning the TURN functionality
Date: Sat, 26 Jul 2025 00:04:28 +0200 [thread overview]
Message-ID: <87qzy4apw3.wl-jch@irif.fr> (raw)
On 18 July, Pascal wrote the following:
> Enabling TURN is the easiest way I found to manually provide this public
> IP address. Maybe I could have patched the ICE gathering code instead.
> Or added STUN support.
Well, if you have access to a public STUN server, then you can simply
point Galene at the STUN server and be done. Of course, unless the STUN
server also does TURN, you'll lose TURN functionality.
But what this discussion indicates is that the current built-in TURN
server works fine for globally-accessible servers, but doesn't work for
servers behind NAT. So here's the plan:
1. rename -udp-range to -port-range, and have it control all of
- the direct UDP port range;
- the TURN UDP port range;
- the TURN TCP port ragne.
2. add -udp-mux, which takes a single port, and only controls the direct
UDP port being used.
It's a little bit more complicated, but more explicit. Suggestions?
-- Juliusz
reply other threads:[~2025-07-25 22:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.galene.org/postorius/lists/galene.lists.galene.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87qzy4apw3.wl-jch@irif.fr \
--to=jch@irif.fr \
--cc=galene@lists.galene.org \
--cc=pabr2749409@pabr.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox