From: Juliusz Chroboczek <jch@irif.fr>
To: pabr2749409@pabr.org
Cc: Dirk-Willem van Gulik <dirkx@webweaving.org>, galene@lists.galene.org
Subject: [Galene] Re: udp-port range and subsequent "turn" use of ports outside that range (Fix: use RelayAddressGeneratorPortRange ?)
Date: Fri, 18 Jul 2025 18:36:46 +0200 [thread overview]
Message-ID: <877c051mn5.wl-jch@irif.fr> (raw)
In-Reply-To: <i8xms91yfrg.fsf@pabr.org>
> I had to patch galene/turnserver/turnserver.go to use
> RelayAddressGeneratorPortRange (from
> pion/turn/relay_address_generator_range.go) instead of
> RelayAddressGeneratorStatic.
Ah, I see. So Galene should customise the TURN address generation
when -udp-range is a range.
What should we do with the TURN server when -udp-range is a single port?
I don't know whether we can multiplex TURN traffic on a single port.
> Not sure I fully understand the problem nor the intent of -udp-range,
Currently, it controls the UDP range for native UDP traffic. In
principle, if the range given by -udp-range is accessible, TURN should not
be necessary, but strange things happen in the Real Internet.
-- Juliusz
next prev parent reply other threads:[~2025-07-18 16:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-11 14:39 [Galene] udp-port range and subsequent "turn" use of ports outside that range Dirk-Willem van Gulik
2024-02-11 17:56 ` [Galene] " Juliusz Chroboczek
2024-02-11 20:53 ` Dirk-Willem van Gulik
2024-02-11 22:14 ` Juliusz Chroboczek
2024-02-15 15:02 ` Dirk-Willem van Gulik
2024-02-15 18:09 ` Juliusz Chroboczek
2024-02-15 18:12 ` Dirk-Willem van Gulik
2024-02-22 22:38 ` Juliusz Chroboczek
2025-07-18 10:06 ` [Galene] Re: udp-port range and subsequent "turn" use of ports outside that range (Fix: use RelayAddressGeneratorPortRange ?) pabr2749409
2025-07-18 16:36 ` Juliusz Chroboczek [this message]
2025-07-18 17:46 ` pabr2749409
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=877c051mn5.wl-jch@irif.fr \
--to=jch@irif.fr \
--cc=dirkx@webweaving.org \
--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