Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not working with Telenor IPTV #155

Open
Nauticno opened this issue Mar 19, 2020 · 1 comment
Open

Not working with Telenor IPTV #155

Nauticno opened this issue Mar 19, 2020 · 1 comment

Comments

@Nauticno
Copy link

Hi!
I have some problems. Perhaps not possible to use this for Telenor IPTV in Norway?
I use igmpproxy proxy now. It does this:

Source | Destination | Protocol|Length|Info
192.168.xx.xxx | 239.255.255.250 | IGMPv2 | 60 | Membership Report group 239.255.255.250
then TV starts to work

pimd does this:

Source | Destination | Protocol | Length | Info
192.168.xx.xxx | 148.123.13.229 | TLSv1.2 |   |  
148.123.13.229 | 192.168.xx.xxx | TCP | 66 |  
192.168.xx.xxx | 239.255.255.250 | IGMPv2 | 60 | Membership Report group 239.255.255.250
and pimd keeps sending TLSv1.2
TV never starts

pimd using TLSv1.2. igmp-proxy does not. Is it possible to turn off TLSv1.2 ?

Nautic

@troglobit
Copy link
Owner

First of all, pimd does not implement any sort of TLS, so it is not the source of those TLSv1.2 messages.

Second, the multicast group 239.255.255.250 is reserved for Microsoft's SSDP (Simple Service Discovery Protocol). It is link-local only, so it has a TTL of 1 and cannot be routed (this is by design). So that you can ignore completely. From what I can understand, the Telenor IPTV multicast groups are in the range 233.184.xxx.yyy, none of which show up in our report above.

Also, as I tried to explain in the other issue you reported, igmpproxy and pimd are very different animals and will therefore behave differently:

  • igmpproxy forwards IGMP join/leave messages from one LAN to another, hence if a client in LAN B sends "IGMP join", igmpproxy creates routing entry for the request group from LAN A to LAN B, and forwards the "IGMP join" to LAN A.
  • pimd listens for IGMP join/leave for each LAN and then talks PIM with its neighboring routers. If it is the only router between two LANs it expects to see all multicast that is to be routed at its "doorstep", so to speak. It does not forward the IGMP traffic, since that's supposed to be link-local.

For your use-case I do not think pimd is the answer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants