91
21.1 Legacy Series / Re: IGMP proxy not started
« on: May 20, 2021, 06:20:46 am »
I beg to differ a bit with you on that point. The MAN page for igmpproxy and also igmpproxy.conf (man igmpproxy and man igmpproxy.conf) are pretty well written and clear about what igmpproxy does and how it is configured and the igmpproxy.conf MAN page describes quite well what should be present and why in the config file. Even the example in the igmpproxy.conf MAN page, actually works if you use it as is with many IPTV providers.
Maybe what is misunderstood by many is what is igmp and multicast is and how it works, which could be more complicated if you think about all it requires to properly pass multicast and IGMP through a firewall (rules, subnets, etc...) which is not in any way the problem of igmpproxy but the firewall's responsibility/problem to allow this traffic to reach igmpproxy properly and allow it to be passed between the networks.
If you don't do firewalling and only routing, you don't need to understand all the 239/x, 224/x networks, igmp, udp, etc... for your IPTV to work. You just need to start igmp proxy with the 2 interfaces I gave above and you're done. But if you run a firewall (like most of us), what is usually the though part is not igmp proxy itself, it's having the right rules so that udp traffic pass, igmp traffic pass, multicast networks and igmp protocol is accepted on both interfaces to reach igmp proxy, some weird routes because of the providers special networks and dns etc... Again none of that is the responsibility of igmp proxy. It's a matter of undertanding multicast, igmp, IPTV, networking, etc...
igmproxy is basically this (from the MAN page):
This "means" it takes the multicast packets on one interface and forwards them (route them) on another interface to the clients that is all it does and nothing else.
If you check the wikis for Multicast and also for IGMP, you'll see why it gets complicated through a firewall.
Maybe what is misunderstood by many is what is igmp and multicast is and how it works, which could be more complicated if you think about all it requires to properly pass multicast and IGMP through a firewall (rules, subnets, etc...) which is not in any way the problem of igmpproxy but the firewall's responsibility/problem to allow this traffic to reach igmpproxy properly and allow it to be passed between the networks.
If you don't do firewalling and only routing, you don't need to understand all the 239/x, 224/x networks, igmp, udp, etc... for your IPTV to work. You just need to start igmp proxy with the 2 interfaces I gave above and you're done. But if you run a firewall (like most of us), what is usually the though part is not igmp proxy itself, it's having the right rules so that udp traffic pass, igmp traffic pass, multicast networks and igmp protocol is accepted on both interfaces to reach igmp proxy, some weird routes because of the providers special networks and dns etc... Again none of that is the responsibility of igmp proxy. It's a matter of undertanding multicast, igmp, IPTV, networking, etc...
igmproxy is basically this (from the MAN page):
Quote
igmpproxy is a simple multicast routing daemon which uses IGMP
forwarding to dynamically route multicast traffic. Routing is done by
defining an "upstream" interface on which the daemon act as a normal
Multicast client, and one or more "downstream" interfaces that serves
clients on the destination networks.
This "means" it takes the multicast packets on one interface and forwards them (route them) on another interface to the clients that is all it does and nothing else.
If you check the wikis for Multicast and also for IGMP, you'll see why it gets complicated through a firewall.