[07:55:22]
<lautre> May be you can look at `arno-iptables-firewall`
But you will need to learn hox to use it a few
[08:22:27]
<tcfx> Ok, I managed to fix the internet connectivity issue from the other day, back in my nginx approach conf. Probably because I hadn't enabled packet forwarding in the first time (and done it as part of following the forum guide).
[09:24:13]
<12b> The `active (exited)` status is normal. This is not a long running service. It just setups wireguard and exits when done.
[09:26:24]
<12b> To check if wireguard is propely setup, run `ip a`, which should display your wireguard interface and `wg show`, which should display the peer(s) you have configured
[09:27:13]
<12b> and some send/receive stats with non 0 numbers if communication is OK
[09:31:40]
<12b> What is used on your VPS? Netplan?
[09:33:03]
<12b> Anyway, you don't have to replicate this part of the howto of the forum. Network interface configuration is specific to your VPS provider. As long as internet connectivity is working, you should not have to change anything in this part
[09:35:00]
<12b> There are several ways to configure network interface on Debian (you VPS is using debian, right?). /etc/network/interface is not deprecated. It is just that it is not the way things are configured by default on your VPS.
[09:35:30]
<12b> yes I could do that
[09:47:47]
<12b> But my config is quite complex compared to the forum because my VPS is the wireguard server for several machines. One is a server that is exposed on the internet by forwarding port from the main IPv4 address of the VPS, like on the forum, but also some that are non servers machines, not exposed on the internet, some that are servers with IPv6 only connectivity, some that are exposed on the internet with dedicated IPv4 and some that are routers that are used to route traffix between the LAN of several sites. I guess you only need the setup for one server using ports forwarded from the IPv4 of the VPS, right?
[09:47:55]
<12b> But my config is quite complex compared to the forum because my VPS is the wireguard server for several machines. One is a server that is exposed on the internet by forwarding port from the main IPv4 address of the VPS, like on the forum, but also some that are non servers machines, not exposed on the internet, some that are servers with IPv6 only connectivity, some that are exposed on the internet with dedicated IPv4 and some that are routers that are used to route traffic between the LAN of several sites. I guess you only need the setup for one server using ports forwarded from the IPv4 of the VPS, right?
[11:36:18]
<12b> There are several ways to configure network interface on Debian (your VPS is using debian, right?). /etc/network/interface is not deprecated. It is just that it is not the way things are configured by default on your VPS.
[11:37:05]
<12b> tcfx: some sample files from my setup with private info redacted, and some comments added :
- wireguard config file of the wireguard server : https://paste.yunohost.org/amixezamiy.coffeescript
- post-up script of the wireguard server : https://paste.yunohost.org/adeqapefid.apache
- wireguard config of yunohosts server : https://paste.yunohost.org/isolavuder.ini
[13:57:38]
<tcfx> > Anyway, you don't have to replicate this part of the howto of the forum. Network interface configuration is specific to your VPS provider. As long as internet connectivity is working, you should not have to change anything in this part
Makes sense
(Also yes it's Debian. I initially tried installing ifupdown to be able to use the network interfaces file like in the forum, though I guess now it would not be needed)
[13:59:36]
<tcfx> > But my config is quite complex compared to the forum because my VPS is the wireguard server for several machines. One is a server that is exposed on the internet by forwarding port from the main IPv4 address of the VPS, like on the forum, but also some that are non servers machines, not exposed on the internet, some that are servers with IPv6 only connectivity, some that are exposed on the internet with dedicated IPv4 and some that are routers that are used to route traffic between the LAN of several sites. I guess you only need the setup for one server using ports forwarded from the IPv4 of the VPS, right?
I also tried to do that for IPv6 because according to diagnostics I need it for email. But besides that, yeah pretty much, though I might in different contexts use it with other clients eventually.
[14:00:15]
<tcfx> > tcfx: some sample files from my setup with private info redacted, and some comments added :
>
> - wireguard config file of the wireguard server : https://paste.yunohost.org/amixezamiy.coffeescript
> - post-up script of the wireguard server : https://paste.yunohost.org/adeqapefid.apache
> - wireguard config of yunohosts server : https://paste.yunohost.org/isolavuder.ini
Thanks, I'll look into it later
[15:20:57]
<12b> Note that I have not included the post-down script of the wireguard server. However I do have one. However I do not have any post up/down script on the yunohost server side. I just feed the wireguard config file to the wireguard client ynh app and it just works.
[15:21:07]
<12b> Note that I have not included the post-down script of the wireguard server. But I do have one. However I do not have any post up/down script on the yunohost server side. I just feed the wireguard config file to the wireguard client ynh app and it just works.
[15:21:23]
<12b> Note that I have not included the post-down script of the wireguard server. But I do have one. However I do not have any post-up/down script on the yunohost server side. I just feed the wireguard config file to the wireguard client ynh app and it just works.
[15:22:14]
<12b> Note that I have not included the post-down script of the wireguard server. But I do have one. However I do not have any post-up/down script on the yunohost server side. I just feed the wireguard config file to the wireguard client ynh app and it works.
[20:25:23]
<sa> I have Prosody installed and it works great.
Now I would like to be able to do XMPP voice calls.
What are the steps to have XMPP voice calls?
I think I have to install Coturn. But could anyone tell me in detail the steps?
Can I install Coturn in a different subdomain?
What ports should I open?
Do I have to configure anything? If so, what and where?
Thank you
[20:35:57]
<Markus Delbrouck> Ask the Yunohost Forum. Detailed Description is there to find.