You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the existing issues, open and closed, and I'm convinced that mine is new.
When the request is meant for an existing plugin, I've added its name to the title.
Is your feature request related to a problem? Please describe.
A TURN server is required for several self-hosted video conferencing solutions (Nextcloud Talk, Jitsi Meet, BigBlueButton, Matrix, etc.). This service is pretty light-weight, but usually requires an excessive number of open ports. Besides that, running a TURN server behind NAT is not recommended.
Describe the solution you'd like
I plan to build a small plugin for net/turnserver. It consists of the net/turnserver port and a small GUI to adjust some options.
Describe alternatives you've considered
Running the TURN server elsewhere and using NAT, but this is not recommended.
Additional context
I've found a few requests on the forum regarding TURN servers behind a OPNsense firewall (NAT) and one request to run a TURN server directly on OPNsense. So I'm not the only one interested in this. :)
The text was updated successfully, but these errors were encountered:
@fichtner The port is tiny and builds very fast, so the additional load on build servers and mirrors would be very low. Are there any objections from the core team regarding the addition of net/turnserver? Otherwise I would continue and create PRs for the new port/plugin (without database support, of course, to keep the number of dependencies low).
fraenki
added a commit
to fraenki/tools
that referenced
this issue
Jan 20, 2025
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
Is your feature request related to a problem? Please describe.
A TURN server is required for several self-hosted video conferencing solutions (Nextcloud Talk, Jitsi Meet, BigBlueButton, Matrix, etc.). This service is pretty light-weight, but usually requires an excessive number of open ports. Besides that, running a TURN server behind NAT is not recommended.
Describe the solution you'd like
I plan to build a small plugin for net/turnserver. It consists of the net/turnserver port and a small GUI to adjust some options.
Describe alternatives you've considered
Running the TURN server elsewhere and using NAT, but this is not recommended.
Additional context
I've found a few requests on the forum regarding TURN servers behind a OPNsense firewall (NAT) and one request to run a TURN server directly on OPNsense. So I'm not the only one interested in this. :)
The text was updated successfully, but these errors were encountered: