[SOLVED] IPTV broken since a couple of days

slackito · October 13, 2019, 6:39pm

Hi, i use init7 as ISP and they provide a free TV stream for their customers.
I have no idea what i did but, since a couple of days or maybe weeks, it does not work anymore.
I am pretty lost as i have no idea about igmp/multicast resp. i have no idea how to debug that to get to the source of the problem.

1. Sun Oct 13 20:02:31 2019 user.notice igmpproxy[4817]: RECV Membership query   from 192.168.1.1     to 224.0.0.1
2. Sun Oct 13 20:02:31 2019 user.notice igmpproxy[4817]: RECV V2 member report   from 192.168.1.1     to 224.0.0.22
3. Sun Oct 13 20:02:31 2019 user.notice igmpproxy[4817]: The IGMP message was from myself. Ignoring.
4. Sun Oct 13 20:02:36 2019 user.notice igmpproxy[4817]: RECV V2 member report   from 192.168.1.1     to 224.0.0.2
5. Sun Oct 13 20:02:36 2019 user.notice igmpproxy[4817]: The IGMP message was from myself. Ignoring.
6. Sun Oct 13 20:02:39 2019 user.notice igmpproxy[4817]: The IGMP message was local multicast. Ignoring.
7. Sun Oct 13 20:02:42 2019 user.notice igmpproxy[4817]: RECV Membership query   from 192.168.1.1     to 224.0.0.1
8. Sun Oct 13 20:02:44 2019 user.notice igmpproxy[4817]: RECV V2 member report   from 192.168.1.1     to 224.0.0.2
9. Sun Oct 13 20:02:44 2019 user.notice igmpproxy[4817]: The IGMP message was from myself. Ignoring.
10. Sun Oct 13 20:02:48 2019 user.notice igmpproxy[4817]: RECV V2 member report   from 192.168.1.1     to 224.0.0.22
11. Sun Oct 13 20:02:48 2019 user.notice igmpproxy[4817]: The IGMP message was from myself. Ignoring.
12. Sun Oct 13 20:02:49 2019 user.notice igmpproxy[4817]: The IGMP message was local multicast. Ignoring.
13. Sun Oct 13 20:02:50 2019 user.notice igmpproxy[4817]: RECV V2 member report   from 192.168.1.227   to 239.77.5.149
14. Sun Oct 13 20:02:50 2019 user.info igmpproxy[4817]: Inserted route table entry for 239.77.5.149 on VIF #1
15. Sun Oct 13 20:02:50 2019 user.notice igmpproxy[4817]: joinMcGroup: 239.77.5.149 on eth2
16. Sun Oct 13 20:02:50 2019 user.notice igmpproxy[4817]: RECV V2 member report   from 81.15.252.28   to 239.77.5.149
17. Sun Oct 13 20:02:50 2019 user.notice igmpproxy[4817]: The IGMP message was from myself. Ignoring.
18. Sun Oct 13 20:02:50 2019 user.notice igmpproxy[4817]: Route activation request from 81.15.252.28 for 239.77.5.149 is from myself. Ignoring.
19. Sun Oct 13 20:02:50 2019 user.notice igmpproxy[4817]: RECV V2 member report   from 192.168.1.227   to 239.77.5.149
20. Sun Oct 13 20:02:50 2019 user.info igmpproxy[4817]: Updated route entry for 239.77.5.149 on VIF #1
21. Sun Oct 13 20:02:53 2019 user.notice igmpproxy[4817]: RECV Membership query   from 192.168.1.1     to 224.0.0.1
22. Sun Oct 13 20:02:54 2019 user.notice igmpproxy[4817]: RECV V2 member report   from 192.168.1.227   to 239.77.5.149
23. Sun Oct 13 20:02:54 2019 user.info igmpproxy[4817]: Updated route entry for 239.77.5.149 on VIF #1
24. Sun Oct 13 20:02:55 2019 user.notice igmpproxy[4817]: RECV V2 member report   from 81.15.252.28   to 239.77.5.149
25. Sun Oct 13 20:02:55 2019 user.notice igmpproxy[4817]: The IGMP message was from myself. Ignoring.
26. Sun Oct 13 20:02:55 2019 user.notice igmpproxy[4817]: RECV Leave message      from 192.168.1.227   to 224.0.0.2
27. Sun Oct 13 20:02:55 2019 user.notice igmpproxy[4817]: RECV Membership query   from 192.168.1.1     to 239.77.5.149
28. Sun Oct 13 20:02:55 2019 user.notice igmpproxy[4817]: RECV V2 member report   from 192.168.1.227   to 239.77.5.18
29. Sun Oct 13 20:02:55 2019 user.info igmpproxy[4817]: Inserted route table entry for 239.77.5.18 on VIF #1
30. Sun Oct 13 20:02:55 2019 user.notice igmpproxy[4817]: joinMcGroup: 239.77.5.18 on eth2
31. Sun Oct 13 20:02:55 2019 user.notice igmpproxy[4817]: RECV V2 member report   from 81.15.252.28   to 239.77.5.18
32. Sun Oct 13 20:02:55 2019 user.notice igmpproxy[4817]: The IGMP message was from myself. Ignoring.
33. Sun Oct 13 20:02:55 2019 user.notice igmpproxy[4817]: Route activation request from 81.15.252.28 for 239.77.5.18 is from myself. Ignoring.
34. Sun Oct 13 20:02:55 2019 user.notice igmpproxy[4817]: RECV V2 member report   from 192.168.1.227   to 239.77.5.18
35. Sun Oct 13 20:02:55 2019 user.info igmpproxy[4817]: Updated route entry for 239.77.5.18 on VIF #1
36. Sun Oct 13 20:02:56 2019 user.notice igmpproxy[4817]: The IGMP message was local multicast. Ignoring.
37. Sun Oct 13 20:02:56 2019 user.notice igmpproxy[4817]: RECV V2 member report   from 192.168.1.1     to 224.0.0.22
38. Sun Oct 13 20:02:56 2019 user.notice igmpproxy[4817]: The IGMP message was from myself. Ignoring.
39. Sun Oct 13 20:02:58 2019 user.notice igmpproxy[4817]: RECV Leave message      from 192.168.1.227   to 224.0.0.2
40. Sun Oct 13 20:02:58 2019 user.notice igmpproxy[4817]: RECV Membership query   from 192.168.1.1     to 239.77.5.18

Can someone tell me if there is something wierd in that log? Thats the igmpproxy on my clearfog pro with debug=2.
The error i get in kodi with debug enabled is: DEBUG: Error, could not open file udp://239.77.0.78:5000/

root@OpenWrt:/etc# cat /sys/devices/virtual/net/br-lan/bridge/multicast_igmp_version
2
root@OpenWrt:/etc# cat /sys/devices/virtual/net/br-lan/bridge/multicast_snooping
0
root@OpenWrt:/etc# cat /sys/devices/virtual/net/br-lan/bridge/multicast_router
1

root@OpenWrt:/etc# cat /etc/igmpproxy.conf

phyint eth2 upstream ratelimit 0 threshold 1
        altnet 0.0.0.0/0

phyint br-lan downstream ratelimit 0 threshold 1

I would really really really appreciate if someone could help me!

lleachii · October 13, 2019, 7:01pm

Can you show us /etc/config/igmpproxy too?

Did you do anything at all?

slackito · October 13, 2019, 7:57pm

root@OpenWrt:~# cat /etc/config/igmpproxy
config igmpproxy
    option quickleave 0
    option verbose 2
#    option verbose [0-2]

config phyint
    option network wan
    option zone wan
    option direction upstream
#    list altnet 192.168.1.0/24 - hier bin ich mir nicht sicher ob das eingeschraenkt werden kann, werde das noch testen
    list altnet 0.0.0.0/0

config phyint
    option network lan
    option zone lan
    option direction downstream

I just turned on some debug stuff. And i disabled some firewall stuff (some things where on rejected, i changed to accept, etc.), but i reverted everything.

Maybe i did an update or changed something, did not notice any change (because the services were not restarted) and so it got forgot

I am wondering if it could be that first drop line with igmp (zone lan dest DROP)

slackito · October 16, 2019, 3:36pm

Ok so, now it gets strange. I changed nothing and suddenly, i can play videos again.
I guess there was something wrong with my ISPs IPTV offer which they fixed now.
I did not yet get a response. i wrote them about a week ago.
Usually, they answer very fast. Guess they are still trying to figure out what happened. Or so...

Anyway, thanks for your effort!

edit: unfortunately, i see no way to edit the title to something like "[SOLVED] ..." so i just marked my answer as solution. Hope thats ok!

lleachii · October 16, 2019, 3:49pm

Step1 -
Screenshot%20from%202019-10-16%2011-48-53

Step 2-

See: How to mark a topic as [Solved]

tmomas · October 16, 2019, 4:22pm

As a user with trustlevel 1 (TL1), you can edit your postings only 24h.
Luckily there are other users with higher TL that can help

system · October 26, 2019, 4:22pm

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.