From: Kail <kaildio@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Multicast forwarding
Date: Sun, 28 Sep 2014 18:52:36 +0200 [thread overview]
Message-ID: <CAFjk_J95nopQJKEA=oq0qE=Wo6cSma8+nR-cAuQnX8pbHq8vTQ@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5MxEdDuTSN0ZrND=cOts0jk+qsG2y9MOVyF=upyPTjbA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1752 bytes --]
Hi Dave,
thanks for forwarding to the right list.
Forgot this line
[1] http://troglobit.com/multicast-howto.html
Thanks,
Kail
On Sun, Sep 28, 2014 at 5:01 PM, Dave Taht <dave.taht@gmail.com> wrote:
> The right list for this question is cerowrt-devel
>
> What guide?
> On Sep 28, 2014 1:23 AM, "Kail" <kaildio@gmail.com> wrote:
>
>> Hi all,
>>
>> 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).
>>
>> I added a rule on mangle PREROUTING for incresing the TTL by one for
>> 224.../4
>>
>> I've 3 devices that serves as media servers but only those on sw00 see
>> each others.
>>
>> root@cerowrt:~# ip mroute show
>> (172.30.42.72, 239.255.255.250) Iif: sw00 Oifs: se00 sw10
>> (172.30.42.21, 239.255.255.250) Iif: se00 Oifs: sw10 sw00
>> (172.30.42.73, 239.255.255.250) Iif: sw00 Oifs: se00 sw10
>>
>> Following hints from the guide [1] I tried pinging 225.1.2.3 from
>> 172.30.42.21. This resulted in
>> (172.30.42.21, 225.1.2.3) Iif: unresolved
>>
>> and 'pimd -r' shows no sign of this group.
>>
>> No icmp or igmp packets are sent on sw+ for this multicast pings.
>>
>> Do you have any suggestion on what and where to look. I don't like the
>> idea of bridging the internal lans.
>>
>> Thanks,
>> Kail
>>
>>
>> _______________________________________________
>> Bloat mailing list
>> Bloat@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/bloat
>>
>>
--
"Our souls that God has given us... our spirit. Is not our body an
existence all too small and weak for our spirits which found a way to swim
through the vast network and live in the infinity of space?"
-= Cowboy Bebop =-
[-- Attachment #2: Type: text/html, Size: 3039 bytes --]
next prev parent reply other threads:[~2014-09-28 16:52 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 [this message]
2014-09-29 18:11 ` Maciej Soltysiak
2014-09-29 18:47 ` Kail
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_J95nopQJKEA=oq0qE=Wo6cSma8+nR-cAuQnX8pbHq8vTQ@mail.gmail.com' \
--to=kaildio@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.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