Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: Juliusz Chroboczek <>
To: Dirk-Willem van Gulik <>
Subject: [Galene] Re: udp-port range and subsequent "turn" use of ports outside that range
Date: Thu, 15 Feb 2024 19:09:10 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

> The situation is slightly more odd.  With galene ran as:
> 	/usr/local/bin/galene -static /usr/local/share/galene \
> 			.... \
> 			-udp-range 18100-19100

> I would expect to only see UDP traffic going out that originates from

I don't see why.  The above configuration only specifies that the TURN
server is advertised on OUTSIDEIP.  It says nothing about the addresses
that are advertised for direct (non-TURN) traffic.

So in the above configuration, Galene will advertise:

  - all local addresses with ports 18100-19100 ;
  - arbitrary STUN-ed addresses ;
  - TURN addresses on OUTSIDEIP:SRCPORT.

> 1)	I had not expected to see OUTSIDEIP_2 in this list at all.

That's a STUNed address.

> 2) 	I had not expected source UDP ports such as 11247 in below list.

If you seen port 11247 inside the NAT, then it's suprising.  Seeing port
11247 outside the NAT might happen if the NAT remapped a port in udp-range
to a different value.

> With the attempts to reach a case where perhaps some RFC1918
> optimisation can be applied.

That's normal behaviour, the first point in the enumeration above.

Please be patient, I'm up to my ears in other stuff right now, but I'm
really interested in understanding the behaviour you've pointed out.

-- Juliusz

  reply	other threads:[~2024-02-15 18:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-11 14:39 [Galene] " 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 [this message]
2024-02-15 18:12           ` Dirk-Willem van Gulik
2024-02-22 22:38         ` Juliusz Chroboczek

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \
    --subject='[Galene] Re: udp-port range and subsequent "turn" use of ports outside that range' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox