All,

I am new to Linux, and have switched from ubuntu 10.04 to Fedora 17. I was only running a mumble server (aka Murmur) and an FTP server. I switched for Linux college courses I am taking.

I spent a good amount of time figuring out how to do it in Fedora.

Finally, after all the time spent yesterday, it was working.
Not sure what has changed from then to now, but I am sure I may (or may not) have dinked something up.

Here is my problem, it seems as if the box is blocking connections on the port that hosts need to connect with. I have verified port forwarding is active on my router, and for grins I even reset the router back to defaults and configured the server and the router to use a different port.

I can see the server operating when I have the client up on my machine, but I cannot even connect to it on the local IP address from within the network!!

I am confused because the service is running, and appears to be listening. Howver I cannot connect to the server at all!

Here is what the mumble-server.log file shows:

<W>2012-08-21 23:50:32.960 Initializing settings from /etc/mumble-server.ini (basepath /etc)
<W>2012-08-21 23:50:32.960 Binding to address 192.168.100.102
<W>2012-08-21 23:50:32.962 OpenSSL: OpenSSL 1.0.0j-fips 10 May 2012
<W>2012-08-21 23:50:32.990 SSL: Adding recommended CA UTN-USERFirst-Client Authentication and Email
<C>2012-08-21 23:50:32.990 Successfully switched to uid 995
<W>2012-08-21 23:50:33.050 ServerDB: Openend SQLite database /var/lib/mumble-server/mumble-server.sqlite
<W>2012-08-21 23:50:33.095 Resource limits were 0 0
<W>2012-08-21 23:50:33.103 Successfully dropped capabilities
<W>2012-08-21 23:50:33.116 DBus registration succeeded
<W>2012-08-21 23:50:33.125 MurmurIce: Endpoint "tcp -h 127.0.0.1 -p 6502" running
<W>2012-08-21 23:50:33.129 OSInfo: Failed to execute lsb_release
<W>2012-08-21 23:50:33.130 Murmur 1.2.3 (1.2.3) running on X11: Linux 3.5.2-1.fc17.x86_64: Booting servers
<W>2012-08-21 23:50:33.289 1 => Server listening on 192.168.100.102:64738
<W>2012-08-21 23:50:33.399 1 => Announcing server via bonjour
<W>2012-08-21 23:50:33.525 1 => Registration needs nonempty 'registername', 'registerpassword' and 'registerurl',
must have an empty 'password' and allowed pings.


Doing a netstat -l shows that it is listening on the host named "featherhat"
tcp 0 0 FeatherHat:64738 *:* LISTEN
tcp 0 0 localhost:boks_servm *:* LISTEN
tcp 0 0 *:sunrpc *:* LISTEN
tcp 0 0 *:51665 *:* LISTEN
tcp 0 0 *:ssh *:* LISTEN
tcp 0 0 localhost:smtp *:* LISTEN
tcp6 0 0 [::]:sunrpc [::]:* LISTEN
tcp6 0 0 [::]:53749 [::]:* LISTEN
tcp6 0 0 [::]:ssh [::]:* LISTEN
udp 0 0 *:54703 *:*
udp 0 0 FeatherHat:64738 *:*


[root@FeatherHat ~]# service murmur status
murmur.service - SYSV: murmur is the server for the Mumble
Loaded: loaded (/etc/rc.d/init.d/murmur)
Active: active (running) since Wed, 22 Aug 2012 00:07:52 -0700; 2min 15s ago
Process: 1455 ExecStop=/etc/rc.d/init.d/murmur stop (code=exited, status=0/SUCCESS)
Process: 1461 ExecStart=/etc/rc.d/init.d/murmur start (code=exited, status=0/SUCCESS)
Main PID: 1469 (murmurd)
CGroup: name=systemd:/system/murmur.service
└ 1469 murmurd -ini /etc/mumble-server.ini

Aug 22 00:07:52 FeatherHat murmur[1461]: [34B blob data]



Can anyone shed some light on this? Going through a reinstall of the OS isnt that much out of the question, but I cannot for the life of me figure out why this has changed. Furthermore, I believe it to be a networking problem on the box its self, because if I cannot even get it to connect within the same lan, we know there is a problem.

Your help is appreciated!!!