IGMP proxy no longer works reliably after 2.7.1 update

Remie2000

@mistergefahrensucher Thanks a lot for your feedback.

You can also find the log @ Status > System Logs > Routing

ninin06

@Remie2000
Your ticket has been added to mine and the target version has been set to 2.8.0 and 24.03.
https://redmine.pfsense.org/issues/15043

I now hope that these versions will be released as soon as possible.

vjizzle

Release 24.03…wow. So the fix is targeted to be here somewhere in the next 6 months orso?

Is it possible to run the igmp proxy package from 2.6 on 2.7? That would be a workaround perhaps for the time being.

michmoor

@vjizzle
Release fixes are estimations not hard deadlines. It could theoretically be pushed back for months or years so ive seen.
My advice, If possible, downgrade back to a working pfsense version. Not great advice i grant you but i dont know another solution.

Also i advice people on the following
https://www.netgate.com/supported-pfsense-plus-packages

vjizzle

@michmoor

Thanks. I already downgraded tot pfsense 2.6 where everything is working fine. Now I will play the waiting game yes.

UlfMerbold

My Workaround is far more simple

Just set an cronjob for a time in the morning hours and stay at the CE2.7.1

	/usr/local/sbin/pfSsh.php playback svc restart igmpproxy

This fixes it for the day in my setup

mistergefahrensucher

@UlfMerbold

i have done this but in my case it's doesn't help.
These reason is if you change to often between 2 chanals in short time the proxy get messed up.
I will try to install the older working igmproxy

mistergefahrensucher

@vjizzle

can you help me please how to install the older package ?

vjizzle

@UlfMerbold said in IGMP proxy no longer works reliably after 2.7.1 update:

My Workaround is far more simple

Just set an cronjob for a time in the morning hours and stay at the CE2.7.1
	/usr/local/sbin/pfSsh.php playback svc restart igmpproxy
This fixes it for the day in my setup

Restarting the igmp proxy works temporarily, but it happens again when changing channels a few times so not really a workable solution here.

vjizzle

@mistergefahrensucher said in IGMP proxy no longer works reliably after 2.7.1 update:

@vjizzle

can you help me please how to install the older package ?

I have not installed the older package, I just downgraded to pfsense 2.6 where igmp works fine. I also would like to know if it is possible to install the igmp package from 2.6 on 2.7.

UlfMerbold

Since we are now at FreeBSD 14 i do'nt know if an install from an different Kernelversion works :/

There must be a "newer" Version of igmpproxy (4.1.1), we should be on 4.1 originally on pfsense

But since the versioning is a bit unloved by the maintainer, i dont know it fixes something from our mess...i'm not an programmer and while looking at the changes last two years, i've no clue what the problem is exactly

Link Text Freshports says there is an new version

Link Text FreeBSD Org too..

But dont see any link to the package?

the "normal" way to install would be

pkg add -f "link to the repo"file.txz

But as i sayed, i did'nt find any FreeBSD 14 Repo from

Rai80

@UlfMerbold I tried 4.1.1 and also older versions 3.x.x. None of them work. So it seems its not the IGMPproxy software but something in the kernel/freebsd release.

If you want to try you can enable the FreeBSD repositories by changing the value from no to yes in /usr/local/etc/pkg/repos/pfSense.conf and /usr/local/etc/pkg/repos/FreeBSD.conf

pkg update
pkg search igmpproxy
pkg install igmpproxy......

mistergefahrensucher

@Rai80

thanks for testing.
At the moment i have another workaround (somthing from the past as IGMPProxy also not worked)
I configured a servicewathdog. Last 2 Days have seen 2 restarts in the morningtime.
This worked for me so far.
But indeed there must be somthing wrong the combination new Kernel and Proxy.
If you said 0.31 ist also not working. i noticed 0.31 is the former version working with Kernel 14 from PF+ 23.05.
So the Kernelnumber is matching. Look like someting is wrong with checksum and lost IGMP memberships. And when you heavy switch betreen 2 chanels there is a memory leak or what else. (i'm not an expert on that level)
Someting has changed in the new 14 Kernel.

If i find the time i will also tryout 0.31. and 0.4.1

or i will wait for a solution

mistergefahrensucher

@Rai80 said in IGMP proxy no longer works reliably after 2.7.1 update:

pkg update

gives error:

pkg: Error extracting the archive: 'Write error'
pkg: No signature found
Unable to update repository FreeBSD

what i'm doing wrong?

vjizzle

I just saw the new releases for CE and pf+ but sadly no igmp proxy fix in the release notes.

mistergefahrensucher

@vjizzle

yes but maybe a kernel fix ?
I think igmpproxy is not the problem because the same version igmpproxy is working fine with older 14er Kernel.
i see this:
Installed packages to be UPGRADED:
pfSense: 23.09 -> 23.09.1 [pfSense]
pfSense-base: 23.09 -> 23.09.1 [pfSense-core]
pfSense-boot: 23.09 -> 23.09.1 [pfSense-core]
pfSense-default-config: 23.09 -> 23.09.1 [pfSense]
pfSense-kernel-pfSense: 23.09 -> 23.09.1 [pfSense-core]
pfSense-repo: 23.09 -> 23.09.1 [pfSense]

ninin06

Has anyone already installed 2.7.2?
Does the problem still exist?
Or are there new problems?

Rai80

@ninin06 Just did the upgrade and tested. Unfortunately the issue doesn't seem te be resolved:

mistergefahrensucher

@Rai80
Yes this is because Kernel version and igmp version is the same as in 2.7.2
Kernel 1400094

long time ago as far as i remember pfsense 2.3... or 2.4 the same disaster with igmpproxy and the workaround was very crazy.
copy back an older version back. (but will give it a try again)

cheers

btw. i'm looking forwrd to a change to pimd. But ther is no understandble information for human to configure it right in a simple IPTV enviroment.
My knowledge and time to experiment is to less.

jimp

Kristof requested some information from users hitting this bug. See https://redmine.pfsense.org/issues/15043 for the full details. If anyone hitting this can check into what he's asking for it would help. Here is the text describing what to gather:

MRT_DEL_MFC; Errno(49) is interesting. error 49 is EADDRNOTAVAIL, which can only be returned (for MRT_DEL_MFC at least) if the membership igmpproxy attempted to remove does not exist.
So as far as the kernel is concerned we're not joined to that group.
(Do note that the membership lookup takes both origin and group address into account, so it's possible that the group is correct but the membership address is not for example.)

We're going to need a bit more information to track this down.
Let's start with a debug log, because igmpproxy can log the relevant information before it attempts MRT_DEL_MFC. That does require it to run with debug verbosity, which can't be set through the webui. Terminate the running process and restart it as /usr/local/sbin/igmpproxy -v -v /var/etc/igmpproxy.conf (or /usr/local/sbin/igmpproxy -d -v -v /var/etc/igmpproxy.conf to run it in the foreground and send all output to stdout).

Once the error occurs (and igmpproxy is still running!) also export the kernel's view of the multicast state with netstat -i -a -n and netstat -g.