Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Downstream disconnects related to packet loss #50

Open
GoogleCodeExporter opened this issue Mar 16, 2015 · 0 comments
Open

Downstream disconnects related to packet loss #50

GoogleCodeExporter opened this issue Mar 16, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

Hi!
1. Run uMurmur (2.14-polarssl) on an OpenWRT system (12.09)
2. Connect with a regular 1.2.8 windows client, use it for a while with a lossy 
connection (e.g. through a VPN), the higher the package loss the faster the 
problem will occur
3. Notice how everybody still hears you although you can't hear anyone
The connection stays active, upload (voice input) works fine, but there is no 
voice coming back from the server

System log shortly before the problem occurs:
[...]
Jan 23 22:45:57 OpenWrt daemon.info uMurmurd[2853]: New UDP connection port 
51618 - [5] [email protected]:65193
Jan 23 22:47:44 OpenWrt daemon.info uMurmurd[2853]: New UDP connection port 
17488 - [5] [email protected]:65193
Jan 23 22:48:39 OpenWrt daemon.info uMurmurd[2853]: New UDP connection port 
60693 - [5] [email protected]:65193
Jan 23 22:49:24 OpenWrt daemon.info uMurmurd[2853]: New UDP connection port 
22627 - [5] [email protected]:65193
Jan 23 22:50:24 OpenWrt daemon.info uMurmurd[2853]: New UDP connection port 
57918 - [5] [email protected]:65193
Jan 23 22:51:29 OpenWrt daemon.info uMurmurd[2853]: New UDP connection port 
55055 - [5] [email protected]:65193

Note that the user's connection with the server stays active the whole time (no 
timeouts, no noticeable lags, etc.). This message shows up almost every minute 
while the user is connected.

The client log shows nothing but regular reconnects (after the problem occured, 
not unless the user actually reconnected).

The issue does not happen on a regular Murmur server (Debian wheezy system), 
running behind the same router/firewall with the same client and connection.
Have fun!

Original issue reported on code.google.com by [email protected] on 23 Jan 2015 at 11:43

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant