FEATURE REQUEST: [PLM] Add mapping functionality to replace string with another in m3u(s)

[babsonnexus]

slampman, post:194, topic:39684, full:true
@babsonnexus Having a weird issue. My setup is I have a standalone linux Channels server @192.168.12.30. My Linux Docker server is @192.168.12.42 and has a couple of Channels servers, Frndly, ESPN+, etc.

I do have a "shim" interface that allows a loopback so that containers can communicate to the host (put in place for macvlan containers but works for all networking in docker).

When I setup SLM Playlists I have to use the internal IP of the Channels server (docker container) when communicating with slm. This works fine, slm picks up the m3u with no issue.

The problem:
When I look at the slm generated m3u, it contains the internal private docker IP's

(http://172.18.0.109:8089/devices/M3U-BBC/channels/9002/stream.mpg?format=ts)

The issue is that my main Channels server (192.168.12.30) cannot talk to (172.18.0.109). So I changed the playlist IP for the Docker Channels server in slm to http://192.168.12.42:8093. With my "shim" in place it should be fine except... The docker channels server is throwing a 403 error because of the networking change in Channels a while back.

[DEBUG | 2024-11-02 19:12:11,893] - Starting new HTTP connection (1): 192.168.12.42:8093
[DEBUG | 2024-11-02 19:12:11,896] - http://192.168.12.42:8093 "GET /devices/M3U-BBC/channels.m3u?format=ts HTTP/11" 403 707

So I'm kind of in a rock and a hard place. I dont know if this is possible but if there was a way to override the source address in the slm generated m3u it would allow this to work.

In the example below if there were an override field in the playlist manager, I would substitute 192.168.12.42:8093 for 172.18.0.109:8089. Then when my main channels server tunes to the m3u it will be able to communicate with the source.

#EXTINF:-1 tvc-guide-title="BBC Four" channel-id="plm_0003" tvg-id="9002" tvg-name="BBC4" tvg-logo="https://tmsimg.fancybits.co/assets/s20684_ll_h15_ab.png?w=360&h=270" tvg-chno="10003" channel-number="10003" tvg-description="No description available..." tvc-guide-description="No description available..." group-title="HD" tvc-guide-stationid="20684" tvc-guide-art="" tvc-guide-tags="" tvc-guide-genres="" tvc-guide-categories="" tvc-guide-placeholders="" tvc-stream-vcodec="" tvc-stream-acodec="",BBC Four
http://172.18.0.109:8089/devices/M3U-BBC/channels/9002/stream.mpg?format=ts

babsonnexus, post:213, topic:39684
It might be if I add a mapping functionality like for SLM, but before going down that path, I'm curious about something. It looks like you are using Channels as an intermediary for some other m3u source? Have you tried putting the m3u source directly into PLM? This is what I discussed here:

slampman, post:218, topic:39684"
I have to use specific dns servers for those Channels servers so i cant use the m3u source directly. But... Even if I use other sources directly I have the same issue.

I did think of a workaround, i can put all of my docker vms on my macvlan which gives them valid ips on the local network. That will work for me but macvlan is only available for Linux. If someone has my same use case where docker is on a seperate server than their Channels server, they will have the same issue.

Still sounds pretty edge-case to me, but I'll put it in as a request for now: