OPNsense Forum

English Forums => 26.1, 26,4 Series => Topic started by: FvdAa on June 29, 2026, 09:08:10 PM

Title: [OPNsense v26.1.10] IGMPProxy: MRT_DEL_MFC; Errno(49): Can't assign requested ad
Post by: FvdAa on June 29, 2026, 09:08:10 PM
Hi,

Since I updated OPNsense to v26.1.10 I'm experiencing issues with IGMPProxy and my KPN Interactive TV.

After a while, it seems that certain actions, f.e. starting an earlier recorded video is not possible and return and error (STB-zap-06) and when restarting the STB it hangs at 85% while starting up. When I then restart IGMPProxy, it directly proceeds the startup and I can also play the recorded video again.

Looking at the logs I can see the following warnings:
 - select() failure; Errno(4): Interrupted system call
 - MRT_DEL_MFC; Errno(49): Can't assign requested address

So far, this seems to happen every 3 days (23rd, 26th and 29th of June).

I found an older topic that looks like similar problem, also with IGMPProxy and KPN:
https://forum.opnsense.org/index.php?topic=41719.45

Anything to check the next time I encounter this issue?

Regards,

Frank
Title: Re: [OPNsense v26.1.10] IGMPProxy: MRT_DEL_MFC; Errno(49): Can't assign requested ad
Post by: nero355 on June 30, 2026, 06:06:59 PM
Consider moving IPTV away from OPNsense and offloading it to a dedicated device like this : https://forum.opnsense.org/index.php?topic=51192.msg262139#msg262139 :)
Title: Re: [OPNsense v26.1.10] IGMPProxy: MRT_DEL_MFC; Errno(49): Can't assign requested ad
Post by: staticznld on July 01, 2026, 09:14:02 AM
I have a small script running that restarts IGMPproxy every night at 03:00 to prevent issues. Nobody is affected by it, and if someone happens to be watching TV at that time, it is only interrupted for a second or two.

Also, I personally think adding an extra device for such a small task is a bit overkill.
Title: Re: [OPNsense v26.1.10] IGMPProxy: MRT_DEL_MFC; Errno(49): Can't assign requested ad
Post by: Haxel on July 01, 2026, 03:49:56 PM
Quote from: FvdAa on June 29, 2026, 09:08:10 PMHi,

Since I updated OPNsense to v26.1.10 I'm experiencing issues with IGMPProxy and my KPN Interactive TV.

After a while, it seems that certain actions, f.e. starting an earlier recorded video is not possible and return and error (STB-zap-06) and when restarting the STB it hangs at 85% while starting up. When I then restart IGMPProxy, it directly proceeds the startup and I can also play the recorded video again.

Looking at the logs I can see the following warnings:
 - select() failure; Errno(4): Interrupted system call
 - MRT_DEL_MFC; Errno(49): Can't assign requested address

So far, this seems to happen every 3 days (23rd, 26th and 29th of June).

I found an older topic that looks like similar problem, also with IGMPProxy and KPN:
https://forum.opnsense.org/index.php?topic=41719.45

Anything to check the next time I encounter this issue?

Regards,

Frank
I wasn't after some huge bonus or anything, just a casino that would accept a $10 PayID deposit without drama. Most lists I checked were messy, so I ended up using payiddeposit.com (https://payiddeposit.com/). It gave me a better idea of what to look for and which deposit details matter before creating an account.
The next time a problem occurs, you should check the status of the DHCP address lease on the IPTV WAN interface, the current multicast routing table in the kernel via the CLI, and the status of the Netmap/Zenarmor queues, if they are in use.
Title: Re: [OPNsense v26.1.10] IGMPProxy: MRT_DEL_MFC; Errno(49): Can't assign requested ad
Post by: nero355 on July 02, 2026, 05:43:53 PM
Quote from: staticznld on July 01, 2026, 09:14:02 AMAlso, I personally think adding an extra device for such a small task is a bit overkill.
Small devices are great at small tasks so that's why in the example a Raspberry Pi was used :)

But to each his own ofcourse!
Title: Re: [OPNsense v26.1.10] IGMPProxy: MRT_DEL_MFC; Errno(49): Can't assign requested ad
Post by: FvdAa on July 02, 2026, 09:54:25 PM
Quote from: Haxel on July 01, 2026, 03:49:56 PMThe next time a problem occurs, you should check the status of the DHCP address lease on the IPTV WAN interface, the current multicast routing table in the kernel via the CLI, and the status of the Netmap/Zenarmor queues, if they are in use.

Thanks, will do! Updated to v26.1.11 this evening, so with a bit of luck this issue is not showing up anymore *fingers crossed*