Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: Dirk-Willem van Gulik <dirkx@webweaving.org>
To: Juliusz Chroboczek <jch@irif.fr>
Cc: galene@lists.galene.org
Subject: [Galene] Re: Turn binding to the ANY Address - even when specified
Date: Wed, 15 Jan 2025 16:56:26 +0100	[thread overview]
Message-ID: <255B813A-A1F3-48A5-B4C8-4A340919BDCC@webweaving.org> (raw)
In-Reply-To: <87o708uqb4.wl-jch@irif.fr>

[-- Attachment #1: Type: text/plain, Size: 2053 bytes --]



> On 15 Jan 2025, at 15:03, Juliusz Chroboczek <jch@irif.fr> wrote:
> 
>> When starting galene with an explcit IP Address on a machine with multiple Ip addresses; e.g. with:
>> 
>> 	./galene  -turn 11.123.4.123:1194 ....
>> 
>> netstat/lsof shows that it is still bound to the ANY address:
>> 
>> 	  # lsof -n | grep LISTEN
>> 	   ....
>> 	   galene    49935 galene    7u     IPv4 0xfffff80019daf000        0     TCP *:1194->*:* (LISTEN)
>> 
>> Is this the expected behaviour (i.e. intentional and for a reason) - or
>> a blemish/thing that I should try to fix ?
> 
> Only the address you specified is advertised to clients, but the server
> listens on the wildcard address.  This allows us to change the server's
> address without tearing down the socket when running with "-turn auto".

So I think below is a fairly simple change - where the 'auto' case is kept as is - and the listener is ONLY bound to a specific IP if it is specified. Otherwise it becomes *:1234 or a found public IP address.

So now [-turn [ip|fqdn]:<port>] behaves exactly like -http.

> So let me know if it's important for you.


So being able to bind it is convenient on a machine with multiple IPs or a machine that straddles networks. As otherwise the galene starting `second' looses the race for 0.0.0.0. . Or a machine with an anal firewall/ACL system - the listen() gets a permission error.

With kind regards,

Dw.


diff --git a/turnserver/turnserver.go b/turnserver/turnserver.go
index 1dcebe0..2210801 100644
--- a/turnserver/turnserver.go
+++ b/turnserver/turnserver.go
@@ -132,7 +132,7 @@ func Start() error {
                if a == nil {
                        return errors.New("couldn't parse address")
                }
-               pcc, lc := listener(net.IP{0, 0, 0, 0}, addr.Port, a)
+               pcc, lc := listener(a, addr.Port, a)
                if pcc != nil {
                        pccs = append(pccs, *pcc)
                        server.addresses = append(server.addresses, &net.UDPAddr{


[-- Attachment #2: Type: text/html, Size: 11924 bytes --]

      reply	other threads:[~2025-01-15 16:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-15 11:30 [Galene] " Dirk-Willem van Gulik
2025-01-15 14:03 ` [Galene] " Juliusz Chroboczek
2025-01-15 15:56   ` Dirk-Willem van Gulik [this message]

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=255B813A-A1F3-48A5-B4C8-4A340919BDCC@webweaving.org \
    --to=dirkx@webweaving.org \
    --cc=galene@lists.galene.org \
    --cc=jch@irif.fr \
    /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