16 Apr
2020
16 Apr
'20
8:41 a.m.
Dear sudo-sys,
I set up a Mumble server for Sudo Room. It is running uMurmur on Sudo Room's saros
machine, and is reachable at address room.sudorom.org.
Relevant files:
- /usr/local/etc/umurmur.conf - Server config file
- /usr/local/src/umurmur - Server source directory
- /usr/local/etc/systemd/system/umurmur.service - Systemd service file
- /etc/iptables/rules.v[46] - Firewalls updated to allow incoming connections on port
64738
Relevant commands:
- systemctl status umurmur - Check the server status
- sudo systemctl restart umurmur - Restart the server
- sudo journalctl -u umurmur -f - Follow the server log
uMurmur is a lightweight Mumble server implementation. I first learned of it from browsing
OpenWRT package repos. If you check e.g. htop, you can see it uses very little RAM or CPU.
Bandwidth usage should also be low, and is limited by some config settings.
More info on this Wiki page:
https://sudoroom.org/wiki/Mumble
I also published a private message about it on Secure Scuttlebutt (SSB):
%6wUU2x+wrO4vJbhebX+p9iYlNuS8EnNlPyGT5o4ogaU=.sha256
I hope this can be useful for Sudo Room people and groups wanting to have high-quality
low-latency voice chats, or who like Mumble and could use a server that is more
geographically close to them and not in a corporate cloud. Does sudo-sys have any feedback
before I share it to sudo-discuss?
Regards,
Charles (cel)
18 Apr
18 Apr
3:34 p.m.
On Thu, Apr 16, 2020 at 8:42 AM Charles E. Lehner <cel(a)celehner.com> wrote:
Dear sudo-sys,
I set up a Mumble server for Sudo Room. It is running uMurmur on Sudo Room's saros
machine, and is reachable at address room.sudorom.org.
That's cool but why does it have to be on our router, vs one of the
other machines?
5:08 p.m.
On Sat, 18 Apr 2020 15:34:03 -0700
Yardena Cohen <yardenack(a)gmail.com> wrote:
On Thu, Apr 16, 2020 at 8:42 AM Charles E. Lehner
<cel(a)celehner.com>
wrote:
The router has IPv6. room.sudoroom.org has both an A record and AAAA record. If the router
forwards the port to another machine for IPv4 only, clients may connect unsuccessfully to
the IPv6 address first before connecting to the IPv4 address. This adds a significant
delay during connection since Mumble seems to not connect to both addresses simultaneously
but waits for one to time out before connecting to the other.
Dear sudo-sys,
I set up a Mumble server for Sudo Room. It is running uMurmur on
Sudo Room's saros machine, and is reachable at address
room.sudorom.org.
That's cool but why does it have to be on our router, vs one of the
other machines?
24 Apr
24 Apr
8:05 a.m.
Hi Yar,
On Sat, 18 Apr 2020 20:08:42 -0400
"Charles E. Lehner" <cel(a)celehner.com> wrote:
On Sat, 18 Apr 2020 15:34:03 -0700
Yardena Cohen <yardenack(a)gmail.com> wrote:
Should umurmur not be on the router? Or do you have concerns about it that I could
address? Originally I was going to put Murmur on space.local, but then I discovered the
IPv6 connection timeout issue. To go back to that way, I see two options:
1. space gets an IPv6 address routed by saros. Then saros can forward the mumble port to
it over both IPv4 and IPv6. Or,
2. a new subdomain is added with just the A record, no AAAA record. Then connections to it
will not fail because of the missing IPv6.
Or a third combo option:
- space gets an IPv6 address routed by saros. Add a new subdomain with A record same as
room.sudoroom.org but AAAA record is to space. Then IPv6 DNAT is not needed.
Using IPv6 is a plus I think. I actually get slightly lower ping times to
room.sudoroom.org over IPv6 than IPv4 from New York - probably because I am using a HE.net
tunnel too. But being fully remote, I'm not sure I want to set up IPv6 routing and
risk messing things up without being physically there to fix it.
Regards,
Charles
On Thu, Apr 16, 2020 at 8:42 AM Charles E. Lehner
<cel(a)celehner.com>
wrote:
[...]
That's cool but why does it have to be on our router, vs one of the
other machines?
The router has IPv6. room.sudoroom.org has both an A record and AAAA
record. If the router forwards the port to another machine for IPv4
only, clients may connect unsuccessfully to the IPv6 address first
before connecting to the IPv4 address. This adds a significant delay
during connection since Mumble seems to not connect to both addresses
simultaneously but waits for one to time out before connecting to the
other.
30 Apr
30 Apr
11:08 p.m.
On Fri, Apr 24, 2020 at 8:05 AM Charles E. Lehner <cel(a)celehner.com> wrote:
- space gets an IPv6 address routed by saros. Add a
new subdomain with A record same as room.sudoroom.org but AAAA record is to space. Then
IPv6 DNAT is not needed.
This seems like the most correct option - a unique subdomain for a
unique machine, that routes directly with v6 and by NAT with v4.
I think as long as you're just messing with ipv6 on space, you won't
kill anything mission critical. It probably won't affect the router,
or the v4 traffic on space. And if it does, I live a mile from Omni
and I'm happy to put on a mask and gloves and go fix it :)
Let me know what you decide. I can invite you to digitalocean team to
add a subdomain.
4 May
4 May
11:36 a.m.
On Thu, 30 Apr 2020 23:08:04 -0700
Yardena Cohen <yardenack(a)gmail.com> wrote:
This seems like the most correct option - a unique
subdomain for a
unique machine, that routes directly with v6 and by NAT with v4.
What do you think about a subdomain for the application, e.g.
mumble.sudoroom.org, instead of or in addition to the machine subdomain?
I think as long as you're just messing with ipv6
on space, you won't
kill anything mission critical. It probably won't affect the router,
or the v4 traffic on space.
Hopefully not. But I think I will need to enable DHCP for v6 on the router.
And if it does, I live a mile from Omni and I'm
happy to put on a
mask and gloves and go fix it :)
I appreciate it.
Let me know what you decide. I can invite you to
digitalocean team to
add a subdomain.
Yes, I would like to try doing this.
8 May
8 May
10:33 p.m.
What do you think about a subdomain for the
application, e.g.
mumble.sudoroom.org, instead of or in addition to the machine subdomain?
Sure, that's fine.
I think as
long as you're just messing with ipv6 on space, you won't
kill anything mission critical. It probably won't affect the router,
or the v4 traffic on space.
Hopefully not. But I think I will need to enable DHCP for v6 on the router. 
19 Apr
19 Apr
6:04 p.m.
Hey nice thanks for setting this up!
On 4/16/20, Charles E. Lehner <cel(a)celehner.com> wrote:
Dear sudo-sys,
I set up a Mumble server for Sudo Room. It is running uMurmur on Sudo Room's
saros machine, and is reachable at address room.sudorom.org.
Relevant files:
- /usr/local/etc/umurmur.conf - Server config file
- /usr/local/src/umurmur - Server source directory
- /usr/local/etc/systemd/system/umurmur.service - Systemd service file
- /etc/iptables/rules.v[46] - Firewalls updated to allow incoming
connections on port 64738
Relevant commands:
- systemctl status umurmur - Check the server status
- sudo systemctl restart umurmur - Restart the server
- sudo journalctl -u umurmur -f - Follow the server log
uMurmur is a lightweight Mumble server implementation. I first learned of it
from browsing OpenWRT package repos. If you check e.g. htop, you can see it
uses very little RAM or CPU. Bandwidth usage should also be low, and is
limited by some config settings.
More info on this Wiki page:
https://sudoroom.org/wiki/Mumble
I also published a private message about it on Secure Scuttlebutt (SSB):
%6wUU2x+wrO4vJbhebX+p9iYlNuS8EnNlPyGT5o4ogaU=.sha256
I hope this can be useful for Sudo Room people and groups wanting to have
high-quality low-latency voice chats, or who like Mumble and could use a
server that is more geographically close to them and not in a corporate
cloud. Does sudo-sys have any feedback before I share it to sudo-discuss?
Regards,
Charles (cel)
1687
days inactive
1710
days old
7 comments
3 participants
participants (3)
-
Charles E. Lehner -
Marc Juul -
Yardena Cohen