IGMP proxy no longer works reliably after 2.7.1 update
-
Same here in PF+
will give a try to extract the working version from 2.7.0
-
@mistergefahrensucher sorry i meen PF+ 23.05
-
@mistergefahrensucher said in IGMP proxy no longer works reliably after 2.7.1 update:
@mistergefahrensucher sorry i meen PF+ 23.05
Please keep us posted, I'm craving for a solution. I even tought my wife to log into the firewall to reset igmp herself
-
I've also created a separate bug report for the PF+ version to get it on the bug tracker of PFsense+.
You can find it here (https://redmine.pfsense.org/issues/15065) , there is a big chance it will be merged with the 2.7.1 bug report.
It would really help to also share your logs and other findings there to help the developers fix this issue.
-
i will do my best. But i can't find the log. My knowledge is to small.
I have enabled verbose logging in IGMPProxy but i don't know where i can find the results.
Are they normally came in system Log -> general ?
Just right now i noticed the:
/usr/local/etc/igmpproxy.conf
is empty (looks like a copy from default). Is this right ?
I expected to see the things i have configured on the web GUI -
@Remie2000
ok i found my /var/etc/igmpproxy.conf
this was working with 23.05 and now after some time it stops on one chanal.
Not always the same but when i restart the igmpproxy it work for some time.##------------------------------------------------------
Enable Quickleave mode (Sends Leave instantly)
##------------------------------------------------------
quickleave
phyint pppoe0 upstream ratelimit 0 threshold 1
altnet 87.141.215.251/32
altnet 224.0.0.0/4phyint ix0 downstream ratelimit 0 threshold 1
altnet 192.168.3.5/32phyint igb0 downstream ratelimit 0 threshold 1
altnet 192.168.4.3/32phyint igb1 disabled
phyint ix0.30 disabled
phyint ix1 disabled
phyint ix0.20 disabled -
yeeehaaa i found the LOG:
Dec 5 17:55:28 raumgitter igmpproxy[15567]: The IGMP message was from myself. Ignoring.
Dec 5 17:55:33 raumgitter igmpproxy[15567]: RECV Membership query from 192.168.4.1 to 224.0.0.1
Dec 5 17:55:33 raumgitter igmpproxy[15567]: RECV Membership query from 192.168.3.1 to 224.0.0.1
Dec 5 17:55:33 raumgitter igmpproxy[15567]: RECV Membership query from 192.168.0.66 to 224.0.0.1
Dec 5 17:55:33 raumgitter igmpproxy[15567]: RECV Membership query from 192.168.99.8 to 224.0.0.1
Dec 5 17:55:33 raumgitter igmpproxy[15567]: RECV V2 member report from 192.168.3.16 to 224.0.0.251
Dec 5 17:55:33 raumgitter igmpproxy[15567]: Updated route entry for 224.0.0.251 on VIF #1
Dec 5 17:55:33 raumgitter igmpproxy[15567]: RECV V2 member report from 192.168.3.16 to 239.255.255.250
Dec 5 17:55:33 raumgitter igmpproxy[15567]: Updated route entry for 239.255.255.250 on VIF #1
Dec 5 17:55:34 raumgitter igmpproxy[15567]: RECV V2 member report from 192.168.3.2 to 239.255.255.250
Dec 5 17:55:34 raumgitter igmpproxy[15567]: Updated route entry for 239.255.255.250 on VIF #1
Dec 5 17:55:34 raumgitter igmpproxy[15567]: RECV V2 member report from 192.168.3.2 to 224.0.0.252
Dec 5 17:55:34 raumgitter igmpproxy[15567]: Updated route entry for 224.0.0.252 on VIF #1
Dec 5 17:55:35 raumgitter igmpproxy[15567]: RECV V2 member report from 192.168.4.1 to 224.0.0.22
Dec 5 17:55:35 raumgitter igmpproxy[15567]: The IGMP message was from myself. Ignoring.
Dec 5 17:55:35 raumgitter igmpproxy[15567]: RECV V2 member report from 192.168.3.1 to 224.0.0.2
Dec 5 17:55:35 raumgitter igmpproxy[15567]: The IGMP message was from myself. Ignoring.
Dec 5 17:55:36 raumgitter igmpproxy[15567]: RECV V2 member report from 192.168.3.1 to 224.0.0.22
Dec 5 17:55:36 raumgitter igmpproxy[15567]: The IGMP message was from myself. Ignoring.
Dec 5 17:55:37 raumgitter igmpproxy[15567]: RECV V2 member report from 192.168.4.3 to 232.0.20.2
Dec 5 17:55:37 raumgitter igmpproxy[15567]: Updated route entry for 232.0.20.2 on VIF #0
Dec 5 17:55:37 raumgitter igmpproxy[15567]: Adding MFC: 87.141.215.251 -> 232.0.20.2, InpVIf: 4
Dec 5 17:55:38 raumgitter igmpproxy[15567]: RECV V2 member report from 192.168.3.5 to 239.255.255.250
Dec 5 17:55:38 raumgitter igmpproxy[15567]: Updated route entry for 239.255.255.250 on VIF #1
Dec 5 17:55:38 raumgitter igmpproxy[15567]: RECV V2 member report from 192.168.4.1 to 224.0.0.2
Dec 5 17:55:38 raumgitter igmpproxy[15567]: The IGMP message was from myself. Ignoring.
Dec 5 17:55:38 raumgitter igmpproxy[15567]: RECV V2 member report from 192.168.3.130 to 239.255.255.250
Dec 5 17:55:38 raumgitter igmpproxy[15567]: Updated route entry for 239.255.255.250 on VIF #1
Dec 5 17:55:40 raumgitter igmpproxy[15567]: RECV V2 member report from 192.168.4.3 to 239.255.255.250
Dec 5 17:55:40 raumgitter igmpproxy[15567]: Updated route entry for 239.255.255.250 on VIF #0
Dec 5 17:55:45 raumgitter igmpproxy[15567]: RECV Leave message from 192.168.4.3 to 224.0.0.2
Dec 5 17:55:45 raumgitter igmpproxy[15567]: Leaving group 232.0.20.2 on interface pppoe0
Dec 5 17:55:45 raumgitter igmpproxy[15567]: RECV Membership query from 192.168.4.1 to 232.0.20.2
Dec 5 17:55:48 raumgitter igmpproxy[15567]: RECV Membership query from 192.168.4.1 to 232.0.20.2
Dec 5 17:55:49 raumgitter igmpproxy[15567]: RECV V2 member report from 192.168.4.3 to 232.0.20.234
Dec 5 17:55:49 raumgitter igmpproxy[15567]: Inserted route table entry for 232.0.20.234 on VIF #0
Dec 5 17:55:49 raumgitter igmpproxy[15567]: Joining group 232.0.20.234 on interface pppoe0
Dec 5 17:55:50 raumgitter igmpproxy[15567]: RECV V3 member report from 84.171.92.84 to 224.0.0.22
Dec 5 17:55:50 raumgitter igmpproxy[15567]: The IGMP message was from myself. Ignoring.
Dec 5 17:55:50 raumgitter igmpproxy[15567]: Adding MFC: 87.141.215.251 -> 232.0.20.234, InpVIf: 4
Dec 5 17:55:52 raumgitter igmpproxy[15567]: RECV V3 member report from 84.171.92.84 to 224.0.0.22
Dec 5 17:55:52 raumgitter igmpproxy[15567]: The IGMP message was from myself. Ignoring.
Dec 5 17:55:55 raumgitter igmpproxy[15567]: Removing MFC: 87.141.215.251 -> 232.0.20.2, InpVIf: 4
Dec 5 17:55:55 raumgitter igmpproxy[15567]: Inserted route table entry for 232.0.20.2 on VIF #-1
Dec 5 17:55:59 raumgitter igmpproxy[15567]: RECV V2 member report from 192.168.4.3 to 232.0.20.234
Dec 5 17:55:59 raumgitter igmpproxy[15567]: Updated route entry for 232.0.20.234 on VIF #0
Dec 5 17:55:59 raumgitter igmpproxy[15567]: Adding MFC: 87.141.215.251 -> 232.0.20.234, InpVIf: 4
Dec 5 17:56:01 raumgitter igmpproxy[15567]: RECV V2 member report from 192.168.4.3 to 232.0.20.234
Dec 5 17:56:01 raumgitter igmpproxy[15567]: Updated route entry for 232.0.20.234 on VIF #0
Dec 5 17:56:01 raumgitter igmpproxy[15567]: Adding MFC: 87.141.215.251 -> 232.0.20.234, InpVIf: 4
Dec 5 17:56:01 raumgitter igmpproxy[15567]: select() failure; Errno(4): Interrupted system call
Dec 5 17:56:01 raumgitter igmpproxy[15567]: Got a interrupt signal. Exiting.
Dec 5 17:56:01 raumgitter igmpproxy[15567]: Removing MFC: 87.141.215.251 -> 232.0.20.2, InpVIf: 4
Dec 5 17:56:01 raumgitter igmpproxy[15567]: MRT_DEL_MFC; Errno(49): Can't assign requested address
Dec 5 17:56:01 raumgitter igmpproxy[15567]: Removing MFC: 87.141.215.251 -> 232.0.20.234, InpVIf: 4
Dec 5 17:56:01 raumgitter igmpproxy[15567]: Leaving group 232.0.20.234 on interface pppoe0
Dec 5 17:56:01 raumgitter igmpproxy[15567]: Leaving group 239.255.255.250 on interface pppoe0
Dec 5 17:56:01 raumgitter igmpproxy[15567]: Leaving group 224.0.0.251 on interface pppoe0
Dec 5 17:56:01 raumgitter igmpproxy[15567]: Leaving group 224.0.0.252 on interface pppoe0
Dec 5 17:56:01 raumgitter igmpproxy[15567]: All routes removed. Routing table is empty.
Dec 5 17:56:01 raumgitter igmpproxy[15567]: Shutdown complete.... -
@mistergefahrensucher Thanks a lot for your feedback.
You can also find the log @ Status > System Logs > Routing
-
@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/15043I now hope that these versions will be released as soon as possible.
-
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.
-
@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 -
Thanks. I already downgraded tot pfsense 2.6 where everything is working fine. Now I will play the waiting game yes.
-
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 igmpproxyThis fixes it for the day in my setup
-
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 -
can you help me please how to install the older package ?
-
@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 igmpproxyThis 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.
-
@mistergefahrensucher said in IGMP proxy no longer works reliably after 2.7.1 update:
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.
-
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.txzBut as i sayed, i did'nt find any FreeBSD 14 Repo from
-
@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...... -
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