I had a similar problem with multicast addresses. I talked with bertl about it, too. I have two vservers needing multicast on the same host. One uses mt-daapd+avahi and the other is a UPNP server running mediatomb. I was able to sniff the traffic of these applications and determine which mutlicast addresses I needed to assign to each vserver to get the applications working. I can't guarantee this will work for you though. For mt-daapd/avahi I created the following: interfaces/1/ip : 224.0.0.251 interfaces/1/prefix: 24 interfaces/1/nodev For UPNP/mediatomb I created: interfaces/1/ip: 239.255.255.250 interfaces/1/prefix: 24 interfaces/1/nodev Hope this helps you, or someone else! Eric On 08/30/10 16:19, Herbert Poetzl wrote: > On Mon, Aug 30, 2010 at 10:43:40PM +0200, Benedikt B�hm wrote: > >> On Mon, Aug 30, 2010 at 7:08 PM, Ed W<lists@wildgooses.com> wrote: >> >>> �Hi, I'm trying to get avahi working within a guest. �So far it seems like >>> because it wants to do multicast, I might need to run something like the >>> following in the host: >>> > >>> � �naddress --nid xxx --add --mask 224.0.0.0/4 >>> > >> i failed with this approach and wrote the patch available at >> http://paste.linux-vserver.org/16406 >> > >> Bertl told me he might add this patch to the official vserver >> patch, no idea what's the ETA though ... >> > testing and reporting success will definitely speed > things up when it comes to patch inclusion ... > > best, > Herbert > > >>> Now, how might I adjust the config files so that this is applied >>> automatically when I start the guest? �Can't figure it out? >>> > >>> Version: 2.6.32.8-grsec2.1.14-vs2.3.0.36.29.1 >>> > >>> (Any other problems/pointers others have running avahi in a guest I'm all >>> ears?) >>> > >>> Thanks >>> Ed W >>> >>>