what do i need to make a private murmur server

Please edit this page if you find a feature or footstep you recall should be included; information technology'south a wiki for a reason! Note you lot must annals and expect about 3 days in order to be able to edit.

Contents

• 1 Setting Up a Murmur Server
  • one.1 Preparations
    • 1.1.one Configure OS
      • 1.one.1.one Windows
      • one.1.1.2 Linux
    • 1.1.2 Configure Network
    • i.1.3 Install Murmur
      • 1.1.3.1 Windows
      • ane.1.3.2 Linux
  • ane.ii Fix Up Server
    • i.2.1 Configuring ini File
    • 1.two.2 Regular Expressions
    • ane.2.3 Starting Murmur
      • ane.ii.3.ane Windows
        • i.ii.iii.1.1 Running as a Windows Service
      • i.ii.3.2 Linux
    • i.2.4 Setting SuperUser Password
      • one.ii.4.i Windows
      • one.2.iv.two Linux
    • i.2.5 Connecting to Murmur Server
    • 1.2.half dozen Becoming Administrator and Registering a User
    • ane.2.7 Permissions
      • one.2.seven.1 ACLs
      • 1.2.7.two Access Tokens
  • 1.3 Server Configuration Methods
    • 1.three.1 Remote Controlling the Server

Setting Up a Murmur Server

Note that the instructions of this guide are Windows based, but all of the instructions should exist adjustable to Linux. Once your IP is fabricated static, and you get Murmur started, its ini configured, and its port is cleared through any firewalls are present, the setup is mostly client-side.

Always remember that there are professional Grumble server hosters. Simply Googling "grumble server hosting" volition come up with many fantabulous, reliable hosts that offer servers at a very cheap price. We also have a list of hosters here.

If y'all have any questions, that y'all cannot find answers to on this folio, check the FAQ.

Preparations

Configure OS

Windows

Before you tin can take Murmur completely working, you demand to brand a few changes to your network on Windows.

First, make your IP static. Unless you're only going to run this server a few times, or it is a LAN server but to exist establish via Bonjour, you lot need to brand your IP static then that a person exterior of your network can dependably connect to your Murmur server. If you have no idea how to brand your IP static, read this guide for doing in on Windows XP, and this guide for doing it on Windows Vista.

Linux

Generally, the config file for setting a static IP involves either using your distro's GUI network tool or editing configuration files (for example, /etc/network/interfaces). Information technology is recommended that you lot Google for instructions to set a static IP for your specific distribution. By and large something like "Ubuntu static IP" volition become what yous need.

Configure Network

Now you need to open a port on your figurer and/or networking equipment. This port volition exist the port that Murmur runs on, and the default is 64738 (using the TCP and UDP protocols). If you wish to utilise a port different than this one, utilize information technology instead of port 64738 used in this example. If you are just using Windows' built-in firewall then when y'all starting time Murmur information technology should ask whether or non to allow it. If you are using a third-party software firewall yous will need to find the instructions for opening a port on it on your own. To larn how to open up the port on your network equipment, nosotros recommend you go to Portforward and select your specific devices from the list. Though Murmur is not currently on the Portforward website, just use another program in place of it (for case read the instructions for opening the ports for Call of Duty) but only open the port you want to utilize for Murmur , ensuring that you are using both TCP and UDP for the port. Call up that Whatever device with a firewall between y'all and the cyberspace must allow the port yous are going to use for Murmur on both the TCP and UDP protocols. That means your [wireless] router, Cable or DSL modem, and annihilation else that has a firewall.

Later you have forwarded the port, you tin can cheque to make sure it is open up by going to http://world wide web.canyouseeme.org/ from the computer that has the port forwarded.

Notation that if your network seems to have the port forwarded completely, and you still cannot connect, you may still have some subconscious software firewall blocking the port on your server. Check very carefully to make certain you practise not.

Install Murmur

Windows

Now y'all need to install Murmur. Download the latest stable Win32 release here. Start the installation, and when y'all come up to the installation choice, select at least the Murmur server. You can choose to install Mumble and Bonjour if y'all want, but it is not a requirement. Once you take it installed, it is recommended that you lot brand a shortcut to it in gild to hands start information technology. Go to C:\Programme Files\Mumble (or wherever you installed Murmur to), right click on murmur.exe and click "Create Shortcut." Observe the shortcut (it will be in the same folder as murmur.exe), right click it, and click "Rename." Blazon "Murmur" (without the quotes) and press enter. Now drag the Murmur icon onto your desktop.

Windows Server users note: you may have an old murmur.sqlite database if you are upgrading to 1.ii.10. Mumble may not remove this database on installation, and so unless y'all want to keep it, y'all can delete it at C:\Users\<username>\murmur.sqlite.

Linux

For near all Linux distributions, y'all tin simply use the static binary. However, if your specific distribution supports Murmur (such as Ubuntu), you should look into using the specific packages for information technology. These are listed on the Linux section of the Installing Mumble folio.

Ready Server

Configuring ini File

First, you lot need to locate the path of your Murmur.ini. This file contains all the basic settings for Murmur.

• Windows: In C:\Program Files\Mumble (or wherever yous installed Grumble to) at that place is a file called murmur.ini.
• Linux: If you are running the command murmurd equally root (e.g. when running Murmur every bit a system service) /etc/grumble-server.ini is used, when run as a normal user ~/.murmurd/murmur.ini is sourced. On some distributions you can also employ the easy wrapper control murmur-user-wrapper, per default it will look at ~/murmur/murmur.ini. To generate a sample configuration file at this location, run murmur-user-wrapper -i.

If you modify any of the settings in this ini file, you have to restart Murmur for the changes to use. Information technology is suggested that you look over and/or configure the lines that start with the following:

welcometext= port= serverpassword= bandwidth= users= registerName=        

Y'all do non need to change whatsoever of these fields for your server to piece of work, but you should change them if you need to. For example if you lot practise non want your server to be public (that is, any user of Grumble has the potential to enter information technology) you should set

serverpassword=        

to

serverpassword=Password_of_your_choice        

(Password_of_your_choice being whatever yous want your server password to exist.) Uncomment

#registerName=        

(change it to)

registerName=        

and set information technology. This line sets the name of the Root channel of your Murmur server. It is the top aqueduct of the server and if you lot practice not prepare it, it will take a proper noun of "Root." For instance if you lot wanted to name the server "FPS Fun" y'all would set the line to

registerName=FPS Fun        

Do not fill up out the other

#register*        

fields or uncomment them if yous are going to take a server countersign set. If you desire it to be public yous must go out

serverpassword=        

blank and you must ready the following lines with the proper information and remove the # from them. (# at the first of a line comments the unabridged line, telling the program that reads it to completely ingore the line.) The lines below register the server with the central Grumble server list and make it and then that ane who browses the servers on the "Server Browser" tab of the connect window can come across your server. Read the commented lines in the ini for specific data about these three lines.

#registerName= #registerPassword= #registerUrl=        

The

#registerHostname=        

line is optional and only fix it if you take an external static IP. If you lot are on a home-based DSL or Cable network, yous probably should not set this field.

Carefully read the commented text in the ini file for explanations of each of the ini settings you wish to modify or fix.

Regular Expressions

If you want to utilise a grapheme that the server does non allow, you lot need to utilize regular expressions - specifically, Qt regular expressions. These are, in themselves, rather complex, but for Mumble, you don't need to acquire them. Here's a quick guide to regular expressions:

If you desire to use the character "%" in a aqueduct proper noun, so uncomment this line in Murmur.ini:

#channelname=[ \\-=\\w\\#\\[\\]\\{\\}\\(\\)\\@\\|]+        

so that information technology is

channelname=[ \\-=\\westward\\#\\[\\]\\{\\}\\(\\)\\@\\|]+        

then add the character, which volition brand it look like this:

channelname=[ \\-=\\westward\\#\\[\\]\\{\\}\\(\\)\\@\\|\\%]+        

See? It's piece of cake. Yous just add together each character that you desire, putting \\ between each character.

If y'all want to add the ability for users to utilise spaces in their username, then uncomment this line

#username=[-=\\w\\[\\]\\{\\}\\(\\)\\@\\|\\.]+        

so that information technology is

username=[-=\\w\\[\\]\\{\\}\\(\\)\\@\\|\\.]+        

and so brand it look similar this:

username=[ \\-=\\w\\[\\]\\{\\}\\(\\)\\@\\|\\.]+        

(Encounter the space at the very beginning, right after the [ ?)

Starting Murmur

In server versions upward to ane.2.ii, the server must have been run normally at least once, to generate the database properly. Also, if you are using a custom config file location, yous must call up to specify it on the command line using the -ini <path> flag while setting the password.

Windows

In one case you accept configured the .ini file to your liking and are ready to start Murmur, showtime it by double clicking the Murmur icon y'all put on your desktop. The server should start and you should see a little icon like to Mumble's in your organization tray (the trivial icons in the bottom right corner of your screen). You can correct click this icon and select either "Evidence Log" to view the log that Murmur generates (users that connect, settings initialized, etc.) or "Quit Murmur" to shut downwards the Murmur server.

If you want Murmur to automatically starting time with Windows, select the Murmur icon, right click it, and click "Re-create." Now right click on your beginning button, select "Open All Users" and open "Programs\Startup." Right click in an empty space and select "Paste." Now Murmur should starting time with Windows.

Running as a Windows Service

Download latest version of NSSM from https://nssm.cc/download , extract the files, in a command prompt navigate to the NSSM folder then navigate to the win32 or win64 folder depending on your arrangement. Run the following command "nssm install <servicename>" without quotes and NSSM volition display a prompt for yous to navigate to the murmur folder to select the murmur.exe, click Install service subsequently selecting murmur.exe. You volition need to go and manually start the service as NSSM doesnt start it after creation. Working on Server 2012 R2 as of 3/18/2016.

https://sourceforge.internet/p/grumble/characteristic-requests/650/

Linux

If you are using the static binary, simply CD to wherever yous extracted it, chmod information technology, then do

./murmur.x86 [-ini <path>]        

If you lot are using a package for your distribution, the command is commonly

murmurd        

This command will exist run if you employ Murmur as a system service on Linux. As described in Running_Murmur#Distribution-Specific_Murmur on some distributions y'all tin also utilise the following wrapper-control if you intend to run Murmur from a normal user environment:

murmur-user-wrapper        

Refer to the respective manual pages for options etc.

Near packages will automatically offset from init.d; you should cheque to make sure yours does not before manually starting information technology. For Installation, expect at the installation department. For the path of the configuration file at this section.

Setting SuperUser Password

Now you volition need to set the SuperUser Password. The server should be running at this point.

Windows

To set the SuperUser password, press the Windows key and agree it down (information technology's the key typically located between the left CTRL and left Alt buttons) and then press the R key.

In the input box of the window that pops upwardly, type cmd and press Enter.

Now blazon

cd %ProgramFiles%\Mumble        

and printing Enter. If that does non piece of work endeavour "cd %ProgramFiles(x86)%\Mumble". If you installed Murmur to a dissimilar binder than those, you need to cd to the correct install directory.

After you lot take done that, type

murmur.exe -supw Password_of_your_choice        

(Password_of_your_choice existence whatsoever password you want to give SuperUser) and press Enter. If you are not using the murmur.ini located in the install binder you can pass your ain using "-ini <full path to ini>".

Note: This does not commencement the Murmur server, information technology only sets the SuperUser password. A window should popular upwards that displays the electric current engagement and time followed by "Superuser password prepare on server1."

Linux

If you're using the static binary, CD to where you extracted information technology, and run

./murmur.x86 [-ini <path>] -supw Password_of_your_choice        

If you're using Murmur every bit a system service or with murmurd, run

murmurd -supw Password_of_your_choice        

If yous're using the wrapper command murmur-user-wrapper, then run

murmur-user-wrapper -p Password_of_your_choice        

Password_of_your_choice being your chosen SuperUser password, of course.

Connecting to Murmur Server

Now that Murmur is started, start Mumble. When it is started, click the Add New... button. And then make full the fields with your servers data.

The Servername field contains the proper noun that will be displayed in your server listing.

The Address field is the external IP of your server; if you practise not know the external IP, go here (from the computer hosting Murmur): http://whatismyipaddress.com/ ; or your servers bonjour proper name (prefixed with @). Your external IP is never 192.168.x.ten

The Username field takes your users Name. Be aware that names are case sensitive. If you lot desire to connect as SuperUser mind the capitalization. Since yous are going to want to add your user every bit an admin, put in that username for at present.

Annotation that in contrast to 1.i.8 there is no password field. This is considering 1.2.ten relies on certificate hallmark. If for some reason a countersign is needed the client volition present you with a prompt.

Becoming Administrator and Registering a User

In 1.2.x you lot don't need any third party scripts, servers, or programs to add a user. First, you probably want to become a member of the ambassador group.

Note that as an administrator, you tin can manage the registered users by going to Server -> Registered Users.

Becoming an admin:

1. Start the Mumble client.
2. Go through the Document Wizard and either import or create a document. You can skip the Audio Wizard if you want, although you will need to run through it in order to set upward your mic properly, then you might want to exercise that anyhow.
3. Open up Configure -> Settings and check "Advanced" at the bottom left.
4. Join your server following the previous pace
5. When you are continued to the server, correct click on your username, and so click "Register" - if you practice not see this pick, ensure that you have an @all ACL that has "Register Self" set to Allow, Applies to sub-channels unchecked.
6. Reconnect every bit the SuperUser - Get dorsum to your server list, and on the main Mumble window click Server -> Connect. You lot volition see the server you added in the previous footstep. Right click it and select "Edit..." Change Username to SuperUser, click OK, and so click Connect.
7. Right click the "Root" Channel (information technology volition be to a higher place your username; it volition exist any yous named information technology if yous set the registerName in Murmur.ini) and click Edit.
8. Become to the Groups tab
9. In the drop-downwardly box at the height select the "admin" group
10. In the "Members" drib-downwardly box at the bottom left, type your username and press enter
11. Click OK
12. Follow step three to alter your username back to the user yous added with SuperUser
13. Connect back to the server
14. Test your administration ability by right clicking the root channel, clicking Add together, and adding a new channel

The default settings allow users to register themselves. This can be disabled inside the ACLs. Members of the admin group can always right click->Register a user to annals them manually. Note that this simply works if the user provided a certificate (pregnant that they have completed the certificate sorcerer).

Brand sure that you instruct everyone on your server to back up their certificate. The certificate sorcerer forces you to do this, just you should always back it up to a secure storage medium like a wink drive, your email inbox, or any external storage medium. If you ever lose your certificate, you will have to re-register and be manually added back into all your various ACLs!

If you lot want to learn more about ACLs see this guide.

For a quick overview of what a certificate is, and how they are used to place people, encounter this folio.

Permissions

Annotation that you must have Advanced config checked at Configure -> Settings in order to see the ACL tab for a channel.

ACLs

Many people have complained about the complexity of ACLs - that they are complicated, difficult, and cumbersome. They are none of these if used correctly. Yous see, the ACLs can exist as complicated every bit you desire. It is basically a full permissions suite similar to what you would bargain with on an Apache server. But information technology doesn't have to exist that complicated!

Do you know what ACL means? Access Control Listing. That is all. An ACL simply defines where and what a "Group" can practice. A Group is simply a bunch of users defined by a proper name. That is all.

Here is a bones guide that you can use to create the most essential permissions for your server:

Ok. You take made one admin so far. If y'all want to add together another admin, the other person you lot know must register themselves. After that, you tin can open the ACL editor and add them in the same style that you used SuperUser to add yourself.

But now you lot want to make a channel that but certain people can go far. Very simple.

1. Make sure that anybody you want to add together is registered with the server
2. Brand the channel for the people who want it (for this example, make an MMO channel)
3. Correct click on the root channel, click "Edit", and then go to the Groups tab
4. Click, in the empty box at the top, and type the proper name of the group you want to add together. For case, if you wanted to make a channel for MMO players, you might proper noun your grouping "MMOplayers." Type that into the box and printing enter. A new group has been made.
5. At present you lot need to add members to this group. In the box at the bottom left, type a member proper name and press enter later each proper name. The names that you add should appear in the box above the input box.

Finally, yous need to create an ACL for the aqueduct. Close the electric current window, and and so right click on the MMO aqueduct and select Edit. Click the ACL tab.

1. Here is where it appears to get complicated, when in fact it is not at all. What y'all start see is inherited ACLs. All inherited means is that the permissions of the in a higher place aqueduct are automatically practical to this one. Since we don't want that, uncheck "Inherit ACLs."
2. Now if you lot just left it like it is now, so the @all permissions would be in effect for this channel. Anyone who went into this channel (except for those in the admin group; they override this) would have the permissions you run into at the right.
3. But we desire to make some ACLs. Start off by calculation an "@all." Just click "Add together" and it will be created. Past default, the Grouping will be all. All the @ means is "apply to." For this group, you probably just want to ready "Deny" for all the permissions. However, you don't take to manually click "Deny" on everything. The group that is divers before it, the "@all" in italics, already has set permissions. For instance, it defaults to deny "Write ACL." So, in the "@all" ACL below information technology, if yous don't bank check either "Deny" or "Allow" and it will default to "Deny." Also note that lower ACLs have priority over ones to a higher place them. For instance, you tin can make an @all that denies permissions for everything, and make an @all below that one, that allows permissions for everything, and everyone in the server will exist given administrator-level access to the server.
4. At present click "Add" over again. Nonetheless, this time you need to click the "Group" box at the bottom left. Delete the "all" text from in that location and type MMOplayers, and so press enter.
5. Now you need to ascertain what exactly MMOPlayers can do. The recommended settings would probably be "Allow" on all the permissions except for "Write ACL" and "Brand channel"; those ii permissions should be fix to "Deny".
6. Now but people in the MMOplayers grouping should exist able to join the aqueduct (and those in the admin grouping, of grade).

Access Tokens

Another dainty characteristic of Mumble 1.2.ten is Access Tokens. These are what you could call passwords; basically, if you have a token that is the same name as the aqueduct'southward ACL Access Token grouping, y'all tin enter the channel. Remember of Access Tokens as groups where you tin can add yourself to the group if you know the "password" (token).

1. Go to Server -> Access Tokens and add a token.
2. Add together an ACL for a aqueduct y'all desire to give permissions to. Do exactly the same as you would with a normal ACL, but when you lot assign a group for the ACL, type #TOKEN_NAME (TOKEN_NAME being the name of the token that you added in the above step).
3. At present each individual user can click themselves, click Server -> Access Tokens, and add together the tokens for the channels they want to enter. Remember, channel owners should only give out the token proper noun to those they want to enter their channel, and it is best to selection a unique, hard-to-guess name for your token.

Server Configuration Methods

As of Mumble ane.2.x, nigh all administration tasks can be handled directly through the customer. However, if you are a dedicated server hoster, you will probably want to start virtual servers, and have some way of configuring and applying the murmur.ini parameters without having to shut down Murmur. Meet below for more information.

Remote Controlling the Server

For a tertiary party application there are two methods, Ice and DBus, to interact with the server. These tin be used from a variety of programming languages and give you low-level access to a lot of functionality.

The easiest way to set a remote interface is to employ Mumble-Django or MumPI.

If you are using a Debian-based distribution, y'all can install Mumble-Django with

sudo apt-get install mumble-django        

and follow the included documentation.

Y'all can observe a list of all the various web-interfaces 3rd_Party_Applications.

This is not a required footstep in this guide.

geanneselleept.blogspot.com

Source: https://wiki.mumble.info/wiki/Murmurguide

Bagikan Artikel ini