23.01.b.20230106.0600 IGMP proxy stops TV stream

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!

jrueger

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

pkg upgrade igmpproxy

All is now well here too on a new 2100 box in Canada with Telus OptikTV. Many thanks to those who worked on the resolution!!

@thebear - Yes this is a very welcome change for me - a long-time faithful Ubiquiti customer - and I just love both the service here in the forums as well as the ability to actually see what is going on with the innards of pfSense and the ability to tinker at a pretty granular level (unlike the now very opaque Ubiquiti systems).

tedquade

@thebear Thanks to all here and elsewhere for tracking this down and posting the fix. Today I was able to fully enjoy some streamed TV.

Ted Quade

michiel

@stephenw10 Hi Stephen; I am using the Netgate 4100 in combination with Dutch TV provider KPN.
Everything is working fine, except for pausing live TV and pausing recorded programs.
After some tweaking and rebooting pausing live TV is working fine now. But pausing recorded programma not.
Some local guys from a GitHub "Using your own router" advised me to go back to IGMP igmpproxy-0.3_1.pkg in stead off 0.3_1,1.

Can I do that via SSH? Or will I break anything? What is your advise?

stephenw10

To do that you would need to reinstall back to 22.05 where the igmpproxy pkg was 0.3.1. There's no easy way to just downgrade the pkg by itself.

haraldinho

Hi @michiel , I am also using a Netgate (6100) together with KPN IPTV. I assume that the problem that you face is that when you pause the recorded stream for a while, it won't properly restart. The box controls show the stream is running again, but the image hangs. Is this right?

I have this issue too, but I can assure you it is not linked to the latest version of igmpproxy. It has always been there in my setup, also in previous releases of pfSense. If you go back to igmpproxy-0.3_1.pkg you will get other, much worse issues, so I do not recommend that.

If I remember correctly from when I was digging into the pausing issue when I started using KPN IPTV, it is also reported by 'regular' users of the KPN supplied modem/router.

What did you tweak to get pausing live TV working? I am curious. That worked for me straight away.

The pausing issue is quite annoying, would love to get rid of it.

michiel

@stephenw10 OK, thank you!

michiel

@haraldinho Pausing live TV started working after several reboots. That was all :). I followed the instruction of Github "Eigen router":

https://github.com/Eigenrouter/eigenrouter/blob/main/guides/pfsense/KPN/pfSense-with-vlan.md

I recently learned that 0.0.0.0/0 for upstream IGMP suffices; I changed that after live pausing was working. Pausing recorded programs still not working. The player counts the time backwards, picture freezes, and that's it!

I guess I have to live with it?

michiel

@michiel But please see comment of Haraldinho... seems that there is still a bug with pfsenseplus on Netgate and pausing recorded programs. I just got confirmation of other KPN customers - with self build routers with pfsense - they do not have that problem. So, can you please look into this and come up with a solution?

thebear

@michiel there is no bug in the IGMP proxy. That proces is just stupid forwarding MC traffic.

Do you provide KPN DNS servers to your STB?

It could be the cause we are missing some configuration parts? The TV config is somehow reversed engineered over the years.

I’m also a KPN customer could you explain me in Dutch what you experience? I don’t have the recording subscription. Is the behavior different when you use the provider modem? Could you test that for us and report back?

If I know what you see I can try to rebuild it over here an capture the network traffic.

VIP5202 or KPN+ STB?

michiel

@thebear Hi, dank voor je hulp alvast. Ik heb de VIP5202 en heb IPTV opgezet via VLAN. Bij de DHCP settings van de de VLAN heb ik DNS 195.121.1.34 en 195.121.1.66 opgenomen.

De Fritzbox heb ik losgekoppeld, het probleem had ik daarmee niet.

thebear

@michiel and only with recorded programs? Not the paused programs?

michiel

@thebear Ja, dat klopt. In eerste instantie ook met live TV, maar nu alleen met opgenomen programma's... Kan ik een log raadplegen en hier posten?

thebear

@michiel nee dat is te complex als je niet zelf de TV beidend. Ik wil wel 1 poging doen, dan moet je een packetcapture maken op de VLAN interface waar je TV op kijkt. Full aanvinken en Count op 0 en dan de juiste TV interface selecteren.

Daarna kan je die file delen met mij, niet te lang wachten met zappen want het wordt dan een (te) groot bestand.

Net getest en als ik live tv pauzeer dan druk ik op play, en dan start hij na een seconden of 6 foutloos.

Je kan ook nog in je firewall logs kijken of daar iets wordt geblokkeerd vanuit de source interface van je TV interface.

haraldinho

@michiel I dove into the issue and I think I might have found a solution.

These are my adjusted mappings under NAT --> Outbound based on the blogpost I found from the travelling tech guy, where his NAT rules were different than mine.

https://travellingtechguy.blog/using-your-own-pfsense-router-with-kpn-fiber-and-kpn-itv/

Initially I had only the bottom mapping. I disabled it, and replaced them with the three topmost rules based on the blog post. Until now this seems to have fixed the issue for me, but I need some more testing. Can't do too much testing now as the Misses is also watching tv with me .

Obviously you should replace 192.168.70.0/24 with your specific subnet.

thebear

@haraldinho indeed the NAT is wrong in the first guide, that's what I mentioned with reversed engineered...everyone is making a guide for the clickbait with good intentions.

Still the second guide is not 100% correct, in that guide are the commonly used proxy upstream address used in the NAT config. The correct configuration for the proxy is the one from the first guide (in fact 0.0.0.0/0 splitter over two subnets).

The correct NAT rule is the one below, you only need to NAT the traffic to the route you receive from the DHCP advertisement from KPN. And that's a single subnet.

With these both configuration parts you are more persistent to future changes from the ISP side.