Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 15 Jan 2016 21:36:15 +0100
From:      Guido Falsi <madpilot@FreeBSD.org>
To:        =?UTF-8?Q?Gerrit_K=c3=bchn?= <gerrit.kuehn@aei.mpg.de>
Cc:        freebsd-net@freebsd.org
Subject:   Re: upnp/dlna
Message-ID:  <5699583F.3090203@FreeBSD.org>
In-Reply-To: <20160115204304.a284c92bb8aa72d24cdc26ae@aei.mpg.de>
References:  <20160115145225.e0dbde9632d5122df8acbb41@aei.mpg.de> <5699161C.1010009@FreeBSD.org> <20160115204304.a284c92bb8aa72d24cdc26ae@aei.mpg.de>

next in thread | previous in thread | raw e-mail | index | archive | help
On 01/15/16 20:43, Gerrit Kühn wrote:
> On Fri, 15 Jan 2016 16:54:04 +0100
> Guido Falsi <madpilot@FreeBSD.org> wrote:
> 
> GF> I forget one thing, Are the mindlna and mediatomb installed in a
> GF> jail?
> 
> No jails involved here, they are both running on a plain machine.
> 
> I just tried the patch you referred to. It applied and compiled
> cleanly, but does not change anything regarding this strange behaviour.
> The server is not seen directly by the clients, some do pick up its
> announcements after some time. The multicasts it emits are not seen by
> the second FreeBSD box. I also have a Linux box here, which also does
> not see the announcements minidlna emits. Other devices (printers etc.)
> emitting announcements are seen just fine on all machines.
> Looks like something is wrong here, but I have no idea what it might
> be...
> 

>From your description it looks like a different issue. Looks like some
network issue, maybe some network device (switch or router) is eating up
certain multicasts?

-- 
Guido Falsi <madpilot@FreeBSD.org>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5699583F.3090203>