From: Mikael Abrahamsson <swmike@swm.pp.se>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Multicast
Date: Wed, 24 Apr 2013 13:42:42 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.00.1304241337280.26743@uplift.swm.pp.se> (raw)
In-Reply-To: <CAA93jw4_c8jMzDiVtUwu=V5Dm-OeooiDzzfm0zYFN-LH06UYsQ@mail.gmail.com>
On Wed, 24 Apr 2013, Dave Taht wrote:
>> I can't find any mention of IGMP proxying in the pimd manual I found.
>> ISPs generally do not allow residential customers to talk PIM with the
>> network, they expect an IGMP join, which is what an IGMP proxy would
>> do.
>
> Sample application?
IPTV. IGMP join is sent from customer device to network which starts
sending the multicast stream afterwards.
This either requires the IPTV box to have direct L2 connectivity to the
ISP network, or it requires whatever home device connects the home to the
ISP network to do IGMP proxying from LAN port to WAN port. It then also of
course needs to create forwarding entries so the multicast received is
forwarded to the LAN.
PIM is used within the ISP / enterprise for multicast routing. IGMP is
used for end devices who would like to subscribe to a multicast group. A
NAT router in a home environment needs to act like a hybrid device, it
needs to use IGMP join to get the IPTV stream, but it then needs to
forward it as if it was a router.
For instance:
<http://sourceforge.net/projects/igmpproxy/>
--
Mikael Abrahamsson email: swmike@swm.pp.se
next prev parent reply other threads:[~2013-04-24 11:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 15:07 William Katsak
2013-04-23 18:40 ` Dave Taht
2013-04-24 7:25 ` Mikael Abrahamsson
2013-04-24 9:30 ` Dave Taht
2013-04-24 11:42 ` Mikael Abrahamsson [this message]
2013-04-24 12:06 ` William Katsak
2013-04-24 17:16 ` Dave Taht
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=alpine.DEB.2.00.1304241337280.26743@uplift.swm.pp.se \
--to=swmike@swm.pp.se \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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