Currently, Mumble only listens to IPv4.
When you ping on the connect interface, that means 50% of packets lost, as client seems to have the strange and queer idea to distribute packets evenly between the two IPv4 and IPv6 addresses.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Wontfix | dereckson | T381 Validate Mumble server installation | |||
| Resolved | dereckson | T384 Mumble server should listen to clients on the IPv6 interface too. |
Event Timeline
Comment Actions
As the canonical server address is 2001:470:1f13:9e1:0:c0ff:ee:1.
/usr/local/etc/murmur.ini has been edited:
-host=212.83.187.132 +host=212.83.187.132 2001:470:1f13:9e1:0:c0ff:ee:1
Comment Actions
$ /usr/local/etc/rc.d/murmur restart Stopping murmur. Waiting for PIDS: 923. Starting murmur. Unable to load library icui18n "Cannot load library icui18n: (Shared object "icui18n" not found, required by "murmurd")". $ /usr/local/etc/rc.d/murmur status murmur is running as pid 70661. $ sockstat | grep 70661 [...] murmur murmurd 70661 13 tcp4 212.83.187.132:64738 *:* murmur murmurd 70661 14 tcp6 2001:470:1f13:9e1:0:c0ff:ee:1:64738 *:* murmur murmurd 70661 15 udp4 212.83.187.132:64738 *:* murmur murmurd 70661 16 udp6 2001:470:1f13:9e1:0:c0ff:ee:1:64738 *:* [...] murmur murmurd 70661 21 tcp6 2001:470:1f13:9e1:0:c0ff:ee:1:64738 2001:470:1f13:d91:4dac:ccfe:50f0:fd3b:50472
Warning about icui18n as start time were expected, per T380. We're currently recompiling Qt against the new version of icu to solve this issue (see T386).