Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    IGMP Proxy Stopping under 2.5.0-RELEASE

    Scheduled Pinned Locked Moved Cache/Proxy
    2 Posts 1 Posters 895 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      StuartSharp
      last edited by StuartSharp

      Hi,

      I'm having a new issue with IGMP Proxy since upgrading from pfSense 2.4.5 to 2.5.0 yesterday.

      I use IGMP Proxy for IPTV channels received through a STB (it's a UK based service provided by BT). The STB is connected directly to a dedicated physical interface on my pfSense box.

      When the STB goes to sleep, the link goes down. This was OK prior to 2.5.0, but now it causes IGMP Proxy to stop and it can't be restarted until the link on the downstream interface is established again. I'm having to work around this by putting a switch in the middle to keep the link to the pfSense interface alive, otherwise I need to login to pfSense and manually start IGMP proxy every time the STB comes out of sleep.

      I don't whether the service kept running or restarted automatically under 2.4.5, but it would be nice to get back to a setup that can cope with the link going down. I thought about using the Service Watchdog package, but that would mean continuous failed restart attempts for the whole time my STB is asleep.

      Edit: IGMP Proxy version is 0.3.1. I never checked what I had before the upgrade.

      1 Reply Last reply Reply Quote 0
      • S
        StuartSharp
        last edited by

        Further info:

        I dug through the package repo and found that IGMP proxy has indeed updated with 2.5.0. But when I tried reverting back to the 2.4.5 version, it didn't fix my issue, so I guess the problem is not IGMP proxy itself but the fact that pfSense fails to restart it.

        I checked the system log events when the interface goes down and found that the script /etc/rc.newwanip runs automatically when it comes back up. Looking in this script, there's a function near the end to restart the IGMP proxy: services_igmpproxy_configure()

        Trouble is, that function only executes when a change in IP address is found, which is never going to happen because the interfaces on both sides of the proxy have static IPs.

        I've edited my script and added a couple of lines at the end to make it go ahead and do the restart whenever the interface coming up is one that's used by IPTV (opt1 is my LAN side and opt3 is the WAN side):

        /* reload igmpproxy for IPTV interface */
        if ($interface == "opt1" || $interface == "opt3") {
        services_igmpproxy_configure();
        }

        This seems to be doing the job for me, but I guess it will get wiped out by a future update, and I still don't know what changed to make this workaround necessary.

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.