Synology 212j installation and configuration

3,064 views
Skip to first unread message

Gordon Tyler

unread,
Aug 25, 2012, 11:52:15 AM8/25/12
to umurmur...@googlegroups.com
First, let me say that uMurmur is exactly what I have been looking for.
I didn't think I could run a voice chat server on my entry level NAS.

I want to outline some of the steps I have taken in case it saves some time for others.
My Synology model is the 212j and it is currently running DSM 4.0.2233

First, you should install the Mumble client on at least one machine.
I recommend getting the installation files from http://mumble.sourceforge.net

Next, log into the admin console of your Synology NAS: http://192.168.1.xx:5000
Start the Package Center, click 'Settings' button then 'Package Sources' tab
Click the 'Add' button and enter http://packages.synocommunity.com into the Location field for a new source.
Now, click on the 'Other Sources' tab and you will be able to install 'uMurmur'

Here's the first area where I think an improvement can be made.
I had expected to click on the uMurmur icon off the home menu and configure uMurmur.
Unfortunately, that is a hyperlink to start the client.

Here's how I was able to reconfigure the server:
First, I had to install the 'Configuration File Editor' package.
I downloaded the package from this guys website: http://www.mertymade.com/syno/
Save it to your local machine and then use the 'Install / Update' button from Package Center to install the package
Once installed, click on the 'Config File Editor' icon from the home menu.
Select 'Config File Editor' from the drop down menu and add this line to the bottom of that list:
   /volume1/@appstore/umurmur/var/umurmur.conf,uMurmur
Click the Save button and then close the editor and re-open it.
Now you will see 'uMurmur' on the drop down list - when you select it, you will be able to edit the uMurmur configuration file

The first thing I tried was to add a password.
When I use the Mumble client and the SuperUser account, I enter that password and I am connect as an administrator.
The problem is, I can't for the life of me figure out what the admin can do that everyone else can't do.

After you save configuration changes, just restart the service from the Package Center.
Going to be setting up our channel list next.

Can anyone explain what the SuperUser is supposed to be able to do?
I understand we can't make permanent channels from the client.

I have also experienced disconnects where the client says the remote server disconnected.
The client tries to reconnect and then I get a message that the account is already in use.
This even happens on the LAN side. Any hints on that problem?

My last question is- how do I prevent just anybody from using my server?
I see a bunch of certificate security stuff, but no ACL or alternative way to authorize clients.

Martin Johansson

unread,
Aug 26, 2012, 5:09:21 PM8/26/12
to Gordon Tyler, umurmur...@googlegroups.com
Hi!

See below for responses.

2012/8/25 Gordon Tyler <gordon....@gmail.com>

First, let me say that uMurmur is exactly what I have been looking for.
I didn't think I could run a voice chat server on my entry level NAS.

That's great!
 
The first thing I tried was to add a password.
When I use the Mumble client and the SuperUser account, I enter that password and I am connect as an administrator.
The problem is, I can't for the life of me figure out what the admin can do that everyone else can't do.

After you save configuration changes, just restart the service from the Package Center.
Going to be setting up our channel list next.

Can anyone explain what the SuperUser is supposed to be able to do?
I understand we can't make permanent channels from the client.

 

I have also experienced disconnects where the client says the remote server disconnected.
The client tries to reconnect and then I get a message that the account is already in use.
This even happens on the LAN side. Any hints on that problem?
 
Hard to tell. If your harddrives are set to spin down after a while and you have logging to file enabled, this could cause these kind of issues. 


My last question is- how do I prevent just anybody from using my server?
I see a bunch of certificate security stuff, but no ACL or alternative way to authorize clients.


/Martin

Gordon J. Tyler

unread,
Aug 27, 2012, 3:11:24 PM8/27/12
to Martin Johansson, umurmur...@googlegroups.com
Thanks for the pointers.
The server seems to be a lot more stable when I set the binding IP to my NAS LAN IP.
I also turned off the HDD Hibernation.
I ended up changing the port and adding a password to secure the server.
It seems that once I set that parameter, the admin_password parameter stops working
It works with SuperUser login only if I don't have a password set.

The other thing that doesn't appear to work is the channel_links features.
I have one enter in the list and it just doesn't transmit the audio to the destination.
I tried with a destination as a sub channel as well as a sibling channel.

Are there log files that I can look at to see what is happening?

None of these are very big deals, but I thought you might want to know.
It's really nice to be able to shut down the PCs and migrate off of TS3.

Martin Johansson

unread,
Aug 27, 2012, 5:45:30 PM8/27/12
to Gordon J. Tyler, umurmur...@googlegroups.com
Hi!

2012/8/27 Gordon J. Tyler <gordon....@gmail.com>

Thanks for the pointers.
The server seems to be a lot more stable when I set the binding IP to my NAS LAN IP.
I also turned off the HDD Hibernation.
I ended up changing the port and adding a password to secure the server.
It seems that once I set that parameter, the admin_password parameter stops working
It works with SuperUser login only if I don't have a password set.
Are you sure about this? I have it working fine here. You need to add the token again in Mumble if you change the server port.

The other thing that doesn't appear to work is the channel_links features.
I have one enter in the list and it just doesn't transmit the audio to the destination.
I tried with a destination as a sub channel as well as a sibling channel.
 
The audio is transmitted only if you whisper to the source channel. 


Are there log files that I can look at to see what is happening?

Yes. I don't know the location on Synology though.
 

--
Det här meddelandet skickas till dig eftersom du prenumererar på gruppen umurmur-general i Google Groups.
Om du vill göra ett inlägg i den här gruppen skickar du e-post till umurmur...@googlegroups.com.
Om du vill sluta prenumerera på den här gruppen skickar du e-post till umurmur-gener...@googlegroups.com.
För fler alternativ, besök gruppen på http://groups.google.com/group/umurmur-general?hl=sv.

Reply all
Reply to author
Forward
0 new messages