Random mutes for 1 person (myself)

[GoogleCodeExporter]

What steps will reproduce the problem?
1. installed latest umurmur on latest openwrt (rc4)
2. config set as default with password to login
3. run voice/sound wizard

What is the expected output? What do you see instead?
* I should hear others clearly and others should clearly hear me.

What version of the product are you using? On what operating system?
* Openwrt rc4 - Backfire (r24038)
* umurmur-openssl 0.2.4-1 (installed with epkg)
* Mumble client (windows) 1.2.2 (all users)

Please provide any additional information below.
Problem I'm having is- the others can hear me... then all of the sudden, they 
cant anymore (other voip apps work without a problem! -vent, ts, skype). As I 
would randomly mute myself. I also tried all config changes from TCP only to 
QOS disabling and Server Loopback (i hear myself great!)

Others hear each other clearly. It has to do something with the idea I'm behind 
the OpenWRT on the same Subnet? I can provide you with any data I can, but I 
dont know what else to post. 

I'll gladly help you help me solve this issue!

thank you!

Original issue reported on code.google.com by gregorp on 30 Dec 2010 at 1:02

[GoogleCodeExporter]

Hi!

This problem, or at least similar, was reported by a person on the mail-list as 
well. Haven't got any additional info though. I don't think that you being 
behind the router matters. I'm using it in the same setup without problems.

More info that might lead to some clues:
o Version of client OS you are using?
o Have you tried tcpdump or equivalent network sniffer when the problem occurs?
o Any pattern when the problem occurs? Directly after connecting or after a 
while?
o OpenSSL or PolarSSL?
o What architecture are you running in on? (which router)

You could try installing uMurmur version 0.2.5. Should be available in the 
snapshots directory on openwrt.org. That will give some info regarding good/bad 
packets and stuff under the 'Information' menu item (right click on user in 
UI). Could give a clue.

Original comment by fatbob.s...@gmail.com on 1 Jan 2011 at 5:22

• Changed state: Accepted

[GoogleCodeExporter]

Hi!

Same problem here. I hope I can give you some info that helps fixing this. :-)

- Netgear WNDR3700 router. Atheros AR7161 CPU
- Firmware: DD-WRT v24-sp2 (11/21/10)
- opkg: downloads.openwrt.org/backfire/10.03.1-rc3/ar71xx/packages 
        but used snapshot/trunk to get umurmur 2.5 and polarssl.

The problem was noticed on a umurmur 0.2.4 but still persists after update to 
0.2.5.

It seems that I (behind the router) can hear the person AS LONG as I myself 
talk. If the person continues talking after I have stopped it stays ok. If both 
stop (mouth in client goes black :-), the other talker can not open 
communication again. If I start talking, he can immediatly be heard again, 
often mid sentence.

Tested with tcpdump and it is obvious the packages arrive ok but nothing can be 
heard.

Thanks and good luck

Original comment by hopperue...@gmail.com on 10 Jan 2011 at 9:47

[GoogleCodeExporter]

Hi both and thank you for your replies. I found a solution to my problem. Here 
was the brainstorm and problems again I had:

* the server was on my local subnet, the same subnet I'm in.
* it was running on openwrt backfire rc4, murmur was version 2.4
* openwrt also had enabled firewall (logically!)
* everyone could connect, because of nature of openwrt it didnt show any 
ping/latency since you cannot ping router from the outside either (fair enough)
* i could connect, tried server echo, it did work. server replied proper result.
* everyone from the outside (connecting to server from internet) could talk to 
each other, just not to me.
* tcpdump was giving the proper results (or did i miss something?)

What solved it?
First, just for the sake of it, I disabled firewall in total, as service. 
Magically, everyone could hear anyone!

It was the default port Murmur/Mumble clients are using! I had to forward it TO 
THE OUSIDE!!! (I had port opened routing connections from outside, not vice 
versa!).

And noone on the net is that mentioned, nor I was almost 100% sure openwrt 
doesnt block any port to the outside. Guess it does.

Thank you again for your help.

Original comment by gregorp on 11 Jan 2011 at 5:29

[GoogleCodeExporter]

@Gregorp: I don't really understand the description of your network setup, but 
packets was dropped in the firewall somehow, so no error on umurmur's part if I 
understand it correctly?
@hopperuediger: I can't see any way that a bug in umurmur would cause the 
symptoms you describe. It sounds much more like a failure with soundcard/mic or 
Mumble, or maybe even with UDP connection tracking with a very small timeout in 
either your or the other person's router. The tcpdump test you mentioned; do 
you mean that the packets arrive to your computer or to the router and then 
don't get sent to your computer?

Original comment by fatbob.s...@gmail.com on 17 Jan 2011 at 8:08

[GoogleCodeExporter]

@martin: exactly. packets were dropped while going out. firewall was blocking 
the port going outside from local intranet to internet and not vice versa.

Original comment by gregorp on 17 Jan 2011 at 8:11

[GoogleCodeExporter]

No new info regarding this for a number of months. Closing.

Original comment by fatbob.s...@gmail.com on 7 Oct 2011 at 12:12

• Changed state: Invalid

[GoogleCodeExporter]

I have this issue at the moment. I've got no idea why it occurs, but I'll look 
into the network setup.

Original comment by SteelS...@gmail.com on 14 Dec 2011 at 8:31

[GoogleCodeExporter]

I just fixed the issue on my side. At least I think I did. I will test it with 
a few friends over the next few days.

I am running uMurmur on a QNAP TS-419P II.
uMurmur version 0.2.8 protocol version 1.2.3

Ports were forwarded on my router and everything worked fine for users from the 
outside, but I (from the same network) could only hear people talking when I 
was talking e.g. sending data. I noticed that I couldn't establish an UDP 
connection and that I had 100% packet loss when hovering over the server name 
to get more info.

I probably fixed the issue by explicitly setting the "bindaddr" in the config 
file to the IP of the QNAP NAS in my home network. Now I can establish an UDP 
connetion and I have no more "packet loss".

Original comment by christop...@gmail.com on 28 Jan 2012 at 12:06

[GoogleCodeExporter]

I had the same issue also.  As stated previously the issue was resolved by 
setting the bindaddr to my wan ip address.  Thanks for the  info!

Original comment by jquinn...@gmail.com on 4 Aug 2012 at 1:06