Solved IPTV - Movistar Triple VLAN

[Mathieu]

Good afternoon all

I am running into a -mild- issue with the IPTV settings on my router (please do not yawn).
As Googling away yielded no meaningful result, and my new AI best buddy showed serious limitations, I thought I'd raised the issue with this learned community.

'Movistar Triple VLAN' is one of the preset configurations available under the LAN/IPTV tab of the GUI.
Since the name closely matches that of my ISP, it has been my setting of choice, and I am grateful it has served me well (Internet and TV, I do not use VoIP).
Still, one little bit of the IPTV service is failing me: accessing the replay of programs I have previously recorded.

Additional information:
-It appears the recordings live in a different place (cloud) than the live broadcasts, and that in order to reach them the set-top box needs to access the wider internet. Since it is plugged in a LAN port specifically tagged by the IPTV configurator, could it be prevented to do so?
-I could, with previous FW releases, access recordings seamlessly. However, I do not remember when: was it with a previous Asus router, or was it when the three VLANs had to be configured manually, without the drop down ISP menu?
-It seems (I wouldn't bet the router on it) that IGMP proxy must be enabled in my case, for proper IPTV configuration. But as I have elsewhere on the forum, that there may be an 'architecture' limitation of the router preventing IGMP to 'coexist' with IPTV. If that were the case, could this be overcome with a couple of judicious script(s)?

I appreciate my use case is very particular (and my annoyance limited) but on the off-chance a reader had experienced the same issue, and managed to solve it, I would be keen to hear from them.

Thank you, as always.

 

[Mathieu]

After some more head scratching and Claude prompting, I seem to have solved the issue.
As it appears, the router was not loading the following services (or 'kernel modules' as apparently they are called):
nf_conntrack_rtsp
nf_nat_rtsp
It failed to work when I tried to load them from 'services-start' and 'init-start' scripts. Not sure if was a question of the order with which these scripts are called in the boot process, or more likely because I wrote the scripts from the terminal (using 'cat...' and/or copy-pasting from other source which may have introduced non unix-like characters).
Anyways, on my third attempt, I pulled out vi and typed a lovely, if short, 'wan-start' script with the required commands.
It seems to be holding up well, and has survived already a couple of reboots.
If that's of any help, the content of wan-start looks like the following (don't copy-paste, just in case):

#!/bin/sh
logger -t "wan-start" "Script is running"
modprobe nf_conntrack_rtsp
modprobe nf_nat_rtsp
logger -t "wan-start" "modprobe commands executed"

Cheers guys!

 

[ColinTaylor]

After some more head scratching and Claude prompting, I seem to have solved the issue.
As it appears, the router was not loading the following services (or 'kernel modules' as apparently they are called):
nf_conntrack_rtsp
nf_nat_rtsp
It failed to work when I tried to load them from 'services-start' and 'init-start' scripts. Not sure if was a question of the order with which these scripts are called in the boot process, or more likely because I wrote the scripts from the terminal (using 'cat...' and/or copy-pasting from other source which may have introduced non unix-like characters).
Anyways, on my third attempt, I pulled out vi and typed a lovely, if short, 'wan-start' script with the required commands.
It seems to be holding up well, and has survived already a couple of reboots.
If that's of any help, the content of wan-start looks like the following (don't copy-paste, just in case):

#!/bin/sh
logger -t "wan-start" "Script is running"
modprobe nf_conntrack_rtsp
modprobe nf_nat_rtsp
logger -t "wan-start" "modprobe commands executed"

Cheers guys!

Theoretically, going to WAN - NAT Passthrough and setting RTSP Passthrough = Enable should do exactly the same thing.