23.01.b.20230106.0600 IGMP proxy stops TV stream
-
Not at this point, at least not in the release build. There is no fix yet as I understand it and the release is imminent. If it's something that can be patched at runtime it can be added to the system patches package later.
-
This is not good news...
Then I have to skip this update. :( -
J jimp moved this topic from Plus 23.01 Development Snapshots (Retired) on
-
I agree it's unfortunate but we couldn't hold the release for this. As soon as we pin down the issue we'll know more.
-
@stephenw10 is this issue affecting all IGMP proxy setups? Not just particullar driver or configuration. Combinations?
-
I haven't been able to replicate it here yet so I can't say for sure. However I would expect it to be something that affects all NICs/drivers. Other multicast traffic, like CARP, does not appear affected so it looks like something in igmpproxy or the libraries it uses.
Steve
-
I faced the same issue when upgraded to 23.01, Disable hardware checksum offload didnt help, bad checksum was in the packet capture
after reverting to BE 22.05 no bad checksum and ip tv works,
my interface is I226-V -
It would be nice if this issue was included in the release notes for 23.01. I read through all the documentation for 23.01 and then proceeded with the upgrade only to find that igmp-proxy did not work. Several hours of troubleshooting lead me to this forum post where it appears that the issue was known for some time before the release of 23.01. This is not the introduction to Netgate and pfSense that I wanted, having just migrated to Netgate products from Ubiquiti Unifi products specifically for the igmp-proxy functionality.
Oh well, now I'll get an early introduction to the process for rolling back upgrades. -
@jrueger said in 23.01.b.20230106.0600 IGMP proxy stops TV stream:
Oh well, now I'll get an early introduction to the process for rolling back upgrades.
Well that's not new to UniFi users right ;-) but yes I think the dev's underestimate the impact of this bug for home deployments. The list get longer and longer when users hit the update button.
At least it could be documented under know issues.
-
@thebear - no kidding with the Unifi gateways ... I finally abandoned Ubiquiti because of the opaqueness of their processes and capabilities. They did finally introduce igmp-proxy functionality in the latest release but with no documentation ... only a checkbox in the GUI and no explanation of just what exactly was enabled when checking the box. So far I am enjoying pfSense immensely so I can live with the igmp-proxy issue since I get to tinker more with things. My wife wasn't happy that her television show was interrupted!
-
Yes, I apologise, it should have been in the notes. The issue was undefined, and still is to some extent. Hopefully we can pin it down shortly.
Steve
-
@stephenw10
issue seems to be from upstream FreeBSD-14 , I was able reproduce checksum errors on FreeBSD-14.0-CURRENT-amd64-20230216-2894c8c96b9b-260969 while freeBSD 13.1-Release doesn't have the issue, pcap attached
13.pcap
14.pcap -
I think i found the issue updated bugtracker, I am attaching patch + binary , it is working for me now, if someone else can confirm that would be great
-
@mxt3rs said in 23.01.b.20230106.0600 IGMP proxy stops TV stream:
I think i found the issue updated bugtracker, I am attaching patch + binary , it is working for me now, if someone else can confirm that would be great
Sure happy to test, TV is currently in use so need to wait until tomorrow. File is loaded and ready for testing.
-
-
@thebear Thanks for the report! I've got the patch staged up and ready to bring into the tree. Until then, for anyone who wants a pkg that can be installed, I have bundled up the patched igmpproxy and attached it to the redmine issue:
https://redmine.pfsense.org/issues/13929#note-14
-
And then feeling brave and daring I went and managed to install the pkg on my 2100, not paying attention to the note that the pkg was for amd64 ... and now igmpproxy is borked and won't start (nice red x under Status - Services). Such is the life of a newbie to pfSense (if only I actually had some sense
). -
You should be able to reinstall the default pkg using
pkg install. You may need to force it.I'm surprised it allowed you to install that on aarch64 though.
-
I've managed to recover and am back to the original 23.01 version of igmp-proxy. Thanks for the help and now I'll be a good boy and wait until a version is available for aarch64.
-
@mxt3rs Installed 23.01 yesterday, had the same issue with igmpproxy. Patch works perfectly so far! Thx!
-
Upgraded on APU2. Fix works. Thank you
