Fri Dec 20, 2013 2:19 am
Workaround: Multicast issues with serviio under KVM
Hi all,
I am a long time Serviio user and I am here to document a quick fix that has solved a problem for me. I recently changed my setup at home to run serviio from a VM (under CentOS KVM) and started having some issues. After starting Serviio, my TV's could find the server without issue. However after a while, if the TV were turned back on again - Serviio could not be found, until Serviio re-advertised. Problem was obviously a multicast issue. I made sure I put in multicast routes but this didn't help.
I dug deeper and found a setting that needs to be change on the KVM host. Apparently after a while, the KVM host stops recognising that there is a multicast server on the guest and no longer forwards multicast traffic to it.
Where <br> is the name of your bridged interface for the VM. Setting this to 0 means that all multicast traffic will hit all adaptors and turn off the host's ability to manage the multicast traffic. There is probably a more elegant way to keep the snooping and fix the problem better - but I just wanted it to work. And with the setting above, it does.
Now, whenever I turn on my TV's they send a broadcast looking for sources and Serviio responds - no matter how long the TV has been switched off for.
M.
I am a long time Serviio user and I am here to document a quick fix that has solved a problem for me. I recently changed my setup at home to run serviio from a VM (under CentOS KVM) and started having some issues. After starting Serviio, my TV's could find the server without issue. However after a while, if the TV were turned back on again - Serviio could not be found, until Serviio re-advertised. Problem was obviously a multicast issue. I made sure I put in multicast routes but this didn't help.
I dug deeper and found a setting that needs to be change on the KVM host. Apparently after a while, the KVM host stops recognising that there is a multicast server on the guest and no longer forwards multicast traffic to it.
Where <br> is the name of your bridged interface for the VM. Setting this to 0 means that all multicast traffic will hit all adaptors and turn off the host's ability to manage the multicast traffic. There is probably a more elegant way to keep the snooping and fix the problem better - but I just wanted it to work. And with the setting above, it does.
Now, whenever I turn on my TV's they send a broadcast looking for sources and Serviio responds - no matter how long the TV has been switched off for.
M.