Messages

It's also worth noting this:

If you have more than one interface in a subnet, then BOTH of those interfaces have to be downstream interfaces in igmpproxy for it to not say "Membership report was recieved on a disabled interface. Ignoring." and "The found if for XXX.XXX.XXX.XXX was not downstream. Ignoring leave request."  I don't know if that is intentional but it seems to only check the first match, not all matches.  Interesting behaviour worth knowing about anyway.  In my case I had a dedicated management interface on the same subnet as my LAN, I just moved this to its own subnet and that cured that issue.

Still solved. I just want to give as much detail as possible for anyone else.

Hi Mech,

We didn't bump the port revision. An option was added instead:

# pkg info igmpproxy | grep VLANFIX


Cheers,
Franco

Thanks for that Franco,

It turns out my issue was not that IGMP proxy wasn't working, but that it was ignoring the IGMP packets because they came back on the wrong interface.  The root cause was my switch which is quite old doing IGMP snooping, but instead of returning the IGMP on the VLAN it came from, it was putting it on the bare interface instead.  Incorrect logic, but it is over 10 years old now.

"sudo /usr/local/sbin/igmpproxy -d -v /usr/local/etc/igmpproxy.conf" was very useful in determining this for anyone who may read this thread in the future.  That turns on debugging and verbosity.  Make sure to stop igmpproxy in the WebGUI first.

The patch is in since 17.1, and we haven't heard a complaint since. Sadly no positive feedback as well.


Cheers,
Franco

Hi Franco,

I'm on 17.1 i386 and don't seem to have the new package, if I do "pkg search igmpproxy" all I have available and installed is igmpproxy-0.1_2,1 and v3,1 isn't there?

Can you help?

Thanks