IGMP proxy no longer works reliably after 2.7.1 update

ninin06 · Nov 27, 2023, 9:20 PM

Hello,
I updated my pfSense from 2.7 to 2.7.1 a week ago. Now I have the problem that one channel always does not work. If I then restart the IGMP proxy, another one does not work. In addition, the stream is not stopped when the old channels are changed and in the end up to 100MBit/s are needed just to download all the channels, which I no longer watch.

My routing log is full of such messages:

Nov 26 13:25:41	igmpproxy	81833	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 26 13:25:41	igmpproxy	81833	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 26 13:25:41	igmpproxy	81833	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 26 13:24:34	igmpproxy	81833	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 26 13:24:34	igmpproxy	81833	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 26 13:24:34	igmpproxy	81833	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 26 13:24:34	igmpproxy	81833	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 26 13:23:50	igmpproxy	81833	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 26 13:23:50	igmpproxy	81833	MRT_DEL_MFC; Errno(49): Can't assign requested address

Here is the traffic when I simply switch through a few channels:

🔒 Log in to view

Does anyone have the same problem and know how to fix it?

Cornel · Nov 27, 2023, 9:20 PM

@ninin06 Yup I seem to have the same. I am on 23.09. This was not happening previously. I have still to figure out what has is going on here. My IPTV is on a separate VLAN. Verbose logging did not provide a clue either.

Nov 27 22:12:59 igmpproxy 41826 MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 27 22:12:59 igmpproxy 41826 MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 27 22:12:59 igmpproxy 41826 MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 27 22:12:59 igmpproxy 41826 MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 27 22:12:59 igmpproxy 41826 MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 27 22:12:59 igmpproxy 41826 MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 27 22:12:59 igmpproxy 41826 MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 27 22:13:07 igmpproxy 41826 MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 27 22:13:07 igmpproxy 41826 MRT_DEL_MFC; Errno(49): Can't assign requested address

vjizzle · Nov 27, 2023, 11:43 PM

Same problem here. Restarting igmp service fixes it temporarily.

UlfMerbold · Nov 28, 2023, 5:17 PM

same here :(

Remie2000 · Nov 30, 2023, 6:05 PM

I encounter the same problems with IGMP proxy.
This happens since 23.09 and no configuration change has been done for months except the upgrade to 23.09.

Seems IGMP proxy package has some problems

Nov 30 17:37:53	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 30 08:01:41	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 30 06:52:27	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 30 06:51:55	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 30 06:09:22	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 29 20:13:24	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 29 20:12:44	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 29 12:16:30	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 29 12:16:30	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 29 06:36:26	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 29 06:35:52	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 28 19:48:36	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 28 19:31:57	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 28 18:37:00	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 28 18:22:51	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 28 18:22:11	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 28 18:11:43	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 28 18:11:43	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 28 18:10:50	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 28 18:10:50	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 28 10:34:55	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 28 08:33:22	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 28 08:32:48	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 28 08:18:17	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address
Nov 28 07:14:32	igmpproxy	78906	MRT_DEL_MFC; Errno(49): Can't assign requested address

I also see the same behavious when switching channels.

Rai80 · Dec 2, 2023, 10:24 PM

@Remie2000 Same problem here. Seems igmpproxy quickleave is not working anymore.

Remie2000 · Dec 3, 2023, 9:22 AM

There is a bug report here: https://redmine.pfsense.org/issues/15043

I think it's best to report it there aswell

vjizzle · Dec 3, 2023, 11:25 AM

I know it takes time to solve this, in the meantime watching tv is nearly impossible. If I go back to version 2.6, will I still get the igmp proxy version which was working then and there or will it just pull the current igmp proxy version?

Remie2000 · Dec 3, 2023, 3:19 PM

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

I know it takes time to solve this, in the meantime watching tv is nearly impossible. If I go back to version 2.6, will I still get the igmp proxy version which was working then and there or will it just pull the current igmp proxy version?

If you export your current configuration in Diagnostics > Backup & Restore (with extra data, and without skip RRD data) you can clean install 2.6.x on your box and import the 2.7.x config on it.

It will run as usual again. Perhaps it is wise to set your DHCP back to ISC DHCP (Deprecated) before exporting to prevent possible errors because the new Kea DHCP is in your config. You can find this on System > Advanced > Networking

Hope this helps you

vjizzle · Dec 3, 2023, 3:19 PM

@Remie2000
I downgraded to pfsense 2.6, made sure the dhcp server was the ISC again. But importing an 2.7 config on 2.6 version of pfsense messed up the firewall config. Luckily I had backups from when I was running 23.05 plus and I was able to import that succesfully. IGMP works as expected again. I will wait for a proper fix for IGMP in version 2.7. Thank you.

ninin06 · Dec 3, 2023, 4:13 PM

@vjizzle
Do you think I can also downgrade to version 2.7.0?
Because in this version I thought the IGMP proxy still worked without any problems.
Or were there already problems and I really have to go to 2.6 until this bug is fixed?

Remie2000 · Dec 3, 2023, 4:14 PM

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

@vjizzle
Do you think I can also downgrade to version 2.7.0?
Because in this version I thought the IGMP proxy still worked without any problems.
Or were there already problems and I really have to go to 2.6 until this bug is fixed?

I didn't have any problems prior latest update. But I'm on PF+ instead of CE

vjizzle · Dec 3, 2023, 4:19 PM

The previous version for me was pf+ 23.05.01 and igmp was functioning fine. With all the changes to the license model I decided to go back to pf CE 2.7. And now back to 2.6 because of igmp bug. If pf+ get's the igmp fix before 2.7 I am jumping the wagon to pf+ again :)

mistergefahrensucher · Dec 5, 2023, 5:02 PM

Same here in PF+

will give a try to extract the working version from 2.7.0

mistergefahrensucher · Dec 5, 2023, 5:06 PM

@mistergefahrensucher sorry i meen PF+ 23.05

Remie2000 · Dec 5, 2023, 5:53 PM

@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

Remie2000 · Dec 5, 2023, 6:07 PM

@mistergefahrensucher

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.

mistergefahrensucher · Dec 5, 2023, 6:21 PM

@Remie2000

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

mistergefahrensucher · Dec 5, 2023, 6:32 PM

@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/4

phyint ix0 downstream ratelimit 0 threshold 1
altnet 192.168.3.5/32

phyint igb0 downstream ratelimit 0 threshold 1
altnet 192.168.4.3/32

phyint igb1 disabled
phyint ix0.30 disabled
phyint ix1 disabled
phyint ix0.20 disabled

mistergefahrensucher · Dec 5, 2023, 6:42 PM

@Remie2000

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....