IGMPv3 (SSM)

Started by k0ns0l3, May 19, 2019, 06:13:00 PM

Previous topic - Next topic
Quote from: skywalker007 on June 06, 2019, 09:14:39 PM
So for now, in short: it works!
I haven't expectet that it would work  :o

I'm afraid for some screenshots  :)


Hello Skywalker. Your link does not work ;-)

Sorry, will fix that when I get back to my desk
System1: Qotom Q310G4
System2: APU2C4

System1: Qotom Q310G4
System2: APU2C4

June 10, 2019, 12:33:14 PM #35 Last Edit: June 12, 2019, 01:39:57 PM by k0ns0l3
does not work  :(

224.0.0.1   igmp   Block private networks from WAN

Firewall log:
192.168.178.1 > 224.0.0.1: igmp query v3
"The quieter you become, the more you are able to hear...."

- OS:Debian GNU/Linux sid
- IPU662 System

@k0ns0l3: Do you like to share your settings with us? I am sure we can make it work for you as well.

June 12, 2019, 06:00:47 AM #37 Last Edit: June 13, 2019, 07:48:30 PM by k0ns0l3
@gliddie: attitude of apu2 and opnsense or home network ,

Regards k0ns0l3  8)

"The quieter you become, the more you are able to hear...."

- OS:Debian GNU/Linux sid
- IPU662 System

I also tried skywalker007's setup and it doesn't work. While I do get an image it will stutter after a few seconds. I have the 401 receiver connected directly to opnsense. The same result happends if I connect the 401 with a igmpv3 ready zyxel switch. The switch works fine if I use my draytek as a normal router and use it's built in igmp.

My setup is draytek 165 -> opnsense pppoe login with vlan7 -> 401 receiver
Intel Xeon 1225v5
Supermicro X11SSM-F
16GB DDR4 ECC UDIMM
Mellanox ConnectX-3

June 17, 2019, 05:10:12 AM #39 Last Edit: June 17, 2019, 05:17:24 AM by DoomSalamander
OK after some searching I finally found the logs and I get the following messages:

igmpproxy[53407]: select() failure; Errno(4): Interrupted system call

and

igmpproxy[14849]: There must be at least 1 Vif as upstream.

Never mind. Just saw the timestamps and those errors were when I tried out to put the vlan tag on the modem itself. When I restart the igmp proxy it doesn't produce any errors in the log.
Intel Xeon 1225v5
Supermicro X11SSM-F
16GB DDR4 ECC UDIMM
Mellanox ConnectX-3

Quote from: DoomSalamander on June 17, 2019, 05:10:12 AM
OK after some searching I finally found the logs and I get the following messages:

igmpproxy[53407]: select() failure; Errno(4): Interrupted system call

and

igmpproxy[14849]: There must be at least 1 Vif as upstream.

Never mind. Just saw the timestamps and those errors were when I tried out to put the vlan tag on the modem itself. When I restart the igmp proxy it doesn't produce any errors in the log.
Would you share your config and some setup details? Maybe we can find some hint why it doesn't work as expected.


Gesendet von iPad mit Tapatalk
System1: Qotom Q310G4
System2: APU2C4

At first I tried your exact setup and was sure I did everything exactly right and currently it looks like this:

IGMP Proxy


WAN rules with IGMP rule with ip option enabled




I noticed that I get the exact same stutter result even if I haven't the IGMP proxy enabled. Should I not even get a picture if it isn't enabled? I used this post as a baseline https://steffenschiffel.de/telekom-entertain-hinter-pfsense-firewall/

I also tried many other solutions that I have found online somewhere or here on the forum or other pfsense solutions.


Intel Xeon 1225v5
Supermicro X11SSM-F
16GB DDR4 ECC UDIMM
Mellanox ConnectX-3

My understanding is that the streams switch from unicast to multicast within the first 30 sec or so. That explains why initially it works.
Can you please check your firewall log for blocked packets while you start the stream?
System1: Qotom Q310G4
System2: APU2C4

June 17, 2019, 02:41:44 PM #43 Last Edit: June 17, 2019, 02:47:27 PM by DoomSalamander
I wish I could... The thing is that I can't even start the igmp proxy anymore. It now always states " There must be at least 1 Vif as upstream." in the logs.

OK I fixed that somehow now. So never mind.
Intel Xeon 1225v5
Supermicro X11SSM-F
16GB DDR4 ECC UDIMM
Mellanox ConnectX-3

I had struggles with the UI based setup initially as well and ended up with editing the conf file on the command line. Not sure if that's the same problem. You can also run the daemon interactively with verbose output. I can shoot over the exact syntax when I am at my desk.
System1: Qotom Q310G4
System2: APU2C4