From: Juliusz Chroboczek <jch@irif.fr>
To: Franck Routier <alci@mecadu.org>
Cc: galene@lists.galene.org
Subject: [Galene] Re: Help needed on network settings
Date: Mon, 28 Oct 2024 17:36:05 +0100 [thread overview]
Message-ID: <874j4wuqve.wl-jch@irif.fr> (raw)
In-Reply-To: <172966575797.1024.4787511935673740367@gauss.local>
Hello, and sorry for the delay.
> * on this server, incus (https://linuxcontainers.org/incus/docs/main/) is used
> to handle different containers: galene is in one of this containers (running
> Ubuntu)n
As you've noticed, containers introduce a lot of extra complexity as soon
as you use an interesting network protocol: they force you to do port
forwardings and other weird things. What I do is to run Galene on the
bare hardware, but run it as its own user. If you insist on running
Galene in a container, then you should give it access to the physical
network, not a virtualised one.
> Oct 22 11:57:07 galene galene[535]: 2024/10/22 11:57:07 Relay test successful
> in 12.038506ms, RTT = 162.921µs
Okay, so Galene can speak to itself.
> Oct 22 14:54:17 galene galene[535]: turn ERROR: 2024/10/22 14:54:17 Failed to
> handle datagram: failed to create stun message from packet: unexpected EOF: not
> enough bytes to read header
That looks like port 1194 is receiving messages that are not destined to
the TURN server. Please double-check your forwarding configuration, and
make sure that you're not forwarding some other port to 1194.
On a machine that's *not* your server, please do the following:
git clone https://github.com/pion/stun
cd cmd/stun-nat-behaviour
go run main.go -server your-server.example.org:1194
and post the output here.
-- Juliusz
next parent reply other threads:[~2024-10-28 16:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <172966575797.1024.4787511935673740367@gauss.local>
2024-10-28 16:36 ` Juliusz Chroboczek [this message]
2024-10-23 6:42 [Galene] " Franck Routier
2024-10-24 8:11 ` [Galene] " Franck Routier
[not found] ` <172975749182.1024.2812222916835422030@gauss.local>
2024-10-24 8:18 ` Franck Routier
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=874j4wuqve.wl-jch@irif.fr \
--to=jch@irif.fr \
--cc=alci@mecadu.org \
--cc=galene@lists.galene.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