From: Kail <kaildio@gmail.com>
To: Maciej Soltysiak <maciej@soltysiak.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Multicast forwarding
Date: Mon, 29 Sep 2014 20:47:18 +0200 [thread overview]
Message-ID: <CAFjk_J8GxV2sJm=iJ4QDeWf6-FyZgukQFeivfcvYx+W8aEaaDg@mail.gmail.com> (raw)
In-Reply-To: <CAMZR1YBQ7OqQ7aiysZdhe6jNH+--8qs7VfNz6bK38WqLE+fCXw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]
Hi Maciej
On Mon, Sep 29, 2014 at 8:11 PM, Maciej Soltysiak <maciej@soltysiak.com>
wrote:
> > On Sep 28, 2014 1:23 AM, "Kail" <kaildio@gmail.com> wrote:
> >> I'm trying to enable DLNA across wifi and wired on 3.10.
> >>
> >> PIM is already there is seems to be configured correctly (but for RP
> >> address, but should not need this).
> Ever since this stopped working for me I just gave up and thought it
> must be my devices and/or software. ENOTIME.
>
>
It could, maybe are devices that multicast dlna but they serve only on the
same network, for some unknown reason. But I don't know how to debug that.
I'd be happy enough to see the multicast ping work or some other test that
validate the network config before moving into devices.
Anything I can try comes to your mind. I've some time for this atm, don't
know how long it will last.
> >> I've 3 devices that serves as media servers but only those on sw00 see
> >> each others.
> Interesting... Although it doesn't work for me atm, I think I've seen
> the exact behavior in the past.
>
> Are you on 3.10.50-1?
>
Yes.
>
> Regards,
> Maciej
>
Regards,
Kail
[-- Attachment #2: Type: text/html, Size: 2042 bytes --]
prev parent reply other threads:[~2014-09-29 18:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFjk_J91RxqtvUQKFQQc0P_udVMWhLGr4Eq4ezSrN7+HU9ZbCw@mail.gmail.com>
2014-09-28 15:01 ` Dave Taht
2014-09-28 16:52 ` Kail
2014-09-29 18:11 ` Maciej Soltysiak
2014-09-29 18:47 ` Kail [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFjk_J8GxV2sJm=iJ4QDeWf6-FyZgukQFeivfcvYx+W8aEaaDg@mail.gmail.com' \
--to=kaildio@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=maciej@soltysiak.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox