I have managed to workaround the issue by creating a NetworkManager dispatcher.d script. It basically restarts the mumble-server when it detects that my connection is up.
Put this script into /etc/NetworkManager/dispatcher.d/90mumblerestart
=============================================================
#!/bin/sh -e
IF=$1
STATUS=$2
if [ "$IF" = "em1" ]
then
case "$STATUS" in
up) service mumble-server restart
;;
*)
;;
esac
fi
Of course, replace em1 with whatever network interface you're using. This script works around the problem for me and I am able to connect to the mumble-server whenever I restart. The only downside is that whenever you disconnect/reconnect on your connection, the mumble server will get restarted, but I figured that if you're doing that all clients will be dropped anyways so it really makes no difference.
I have managed to workaround the issue by creating a NetworkManager dispatcher.d script. It basically restarts the mumble-server when it detects that my connection is up.
Put this script into /etc/NetworkMan ager/dispatcher .d/90mumblerest art ======= ======= ======= ======= ======= ======= ======= =====
=======
#!/bin/sh -e
IF=$1
STATUS=$2
if [ "$IF" = "em1" ]
service mumble-server restart
then
case "$STATUS" in
up)
;;
*)
;;
esac
fi
======= ======= ======= ======= ======= ======= ======= ===
Of course, replace em1 with whatever network interface you're using. This script works around the problem for me and I am able to connect to the mumble-server whenever I restart. The only downside is that whenever you disconnect/ reconnect on your connection, the mumble server will get restarted, but I figured that if you're doing that all clients will be dropped anyways so it really makes no difference.