23.01.b.20230106.0600 IGMP proxy stops TV stream

stephenw10

Yes, it should be available for all architectures. Including on the 1100.

jrueger

Does that mean that it will be available as a System Patch in Patch Manager? Sorry for the dumb questions as I'm learning how to administer a pfsense box.

stephenw10

No it's not a runtime patch it requires a new binary so it will appear as an updatable pkg from the command line. That's not a usual way to upgrade/patch in pfSense but otherwise it would only be in the next release.

Dobby_

@stephenw10 said in 23.01.b.20230106.0600 IGMP proxy stops TV stream:

No it's not a runtime patch it requires a new binary so it will appear as an updatable pkg from the command line. That's not a usual way to upgrade/patch in pfSense but otherwise it would only be in the next release.

fetch https://redmine.pfsense.org/attachments/download/4714/igmpproxy-0.3_1.pkg
pkg add -f igmpproxy-0.3_1.pkg

and after this a...

pkg install igmpproxy-0.3_1.pkg

Y = for YES

And then all is done?

stephenw10

Yes, you only need to upgrade the pkg. Everything else will start using that.

jrueger

@stephenw10 but this is still only for amd64?

stephenw10

Yes, the pkg file attached to the redmine is amd64.
pkgs for all architectures should be available when the repo builds update.

jrueger

@stephenw10 ok then I'm lost and confused ... where is the "repo builds update" located? On github/pfsense or somewhere else?

stephenw10

Sorry I typo'd that.

When our pkg builders next run I expect to see an updated package available in our repos.

So running pkg upgrade igmpproxy at the command line will show it.

jrueger

@stephenw10 Ah I get it now ... thanks for explaining things to a newbie.

Remie2000

I can confirm that this package fixes the IGMP problems!

Thanks a lot!

Dobby_

@stephenw10 said in 23.01.b.20230106.0600 IGMP proxy stops TV stream:

Yes, you only need to upgrade the pkg. Everything else will start using that.

Thank you very much for that information.

I installed like above shown with the commands and then
I was setting up another one on top, like;

pkg upgrade

It shows me then there will be an upgrade named:
igmpproxy-0.3,1.pkg
It upgraded the first loaded from "outside" packed named
igmpproxy-0.3-1, was this a failure was it now reinstalling the older version or another one or was it only a typo?

stephenw10

No if you look back in this thread that was explained. 0.3,1 is the original version from 23.01, the pkg system sees that as numerically newer than 0.3_1 allows you to "upgrade" to it. If you check pkg info igmpproxy you will see the build date for 0.3,1 is in Jan.

Steve

mxt3rs

i have updated bug tracker with arm pkg if someone wants to try

https://redmine.pfsense.org/attachments/download/4733/igmpproxy-aarch64-0.3,1.pkg

Fretboard36

@mxt3rs Great job! I've installed the arm package on my Netgate 2100 and the IP-TV streams are working flawless again.

cmcdonald

Thanks to everyone who provided feedback.

Thanks @mxt3rs for tracking down the issue.

The patch has been pushed to 23.01 repos. Soon you should be able to update via pkg upgrade igmpproxy

stephenw10

You should be able to see that now:

[23.01-RELEASE][admin@m470.stevew.lan]/root: pkg upgrade igmpproxy
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
	igmpproxy: 0.3,1 -> 0.3_1,1 [pfSense]

Number of packages to be upgraded: 1

24 KiB to be downloaded.

Proceed with this action? [y/N]:

Available for all architectures.

thebear

@stephenw10 said in 23.01.b.20230106.0600 IGMP proxy stops TV stream:

You should be able to see that now:

[23.01-RELEASE][admin@m470.stevew.lan]/root: pkg upgrade igmpproxy
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
	igmpproxy: 0.3,1 -> 0.3_1,1 [pfSense]

Number of packages to be upgraded: 1

24 KiB to be downloaded.

Proceed with this action? [y/N]:

Available for all architectures.

Thanks for the great and fast support, it make me remember the good old days on the Ubiquity UniFi forum. When the interaction was between the dev and the technical enduser. Love that, keep up the good NetGate work!

Dobby_

[23.01-RELEASE][root@Dockmaster.Heimnetz]/root: pkg info igmpproxy
igmpproxy-0.3,1
Name           : igmpproxy
Version        : 0.3,1
Installed on   : Mon Feb 20 23:00:28 2023 CET
Origin         : net/igmpproxy
Architecture   : FreeBSD:14:amd64
Prefix         : /usr/local
Categories     : net
Licenses       : GPLv2+
Maintainer     : franco@opnsense.org
WWW            : https://github.com/pali/igmpproxy
Comment        : Multicast forwarding IGMP proxy
Annotations    :
        FreeBSD_version: 1400073
        build_timestamp: 2023-01-07T20:09:23+0000

and then

[23.01-RELEASE][root@Dockmaster.Heimnetz]/root: pkg upgrade igmpproxy
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
        igmpproxy: 0.3,1 -> 0.3_1,1 [pfSense]

Number of packages to be upgraded: 1

24 KiB to be downloaded.

Proceed with this action? [y/N]: y
[1/1] Fetching igmpproxy-0.3_1,1.pkg: 100%   24 KiB  24.4kB/s    00:01
Checking integrity... done (0 conflicting)
[1/1] Upgrading igmpproxy from 0.3,1 to 0.3_1,1...
[1/1] Extracting igmpproxy-0.3_1,1: 100%

All is fine here now again like the other user reported,
German Telekom Magenta TV

Dobby_

This post is deleted!