IPTV configuration with init7

billybob · December 2, 2023, 8:00pm

Hello,

I am trying to setup IPTV from my ISP (init7), which provides several IPTV streams https://www.init7.net/de/support/faq/TV-andere-Geraete/
I am using a netgear R7800 on OpenWrt 23.05.0
The R7800 router connects to a TP-LINK MC 220L media converter which is connected to the OTO. There is only this router, no double NAT, bridging or more complex setup.wiki
I have installed igmpproxy and done the configs as per the docs https://openwrt.org/docs/guide-user/network/wan/udp_multicast
However, using a desktop connected by cable to the LAN, I don't get any IPTV stream using VLC. I see log entries which correspond to the requested stream, but nothing happens. From here, I'm not sure what to check in order to identify the problem.
I've put the relevant config and log output below. If anything else is needed to identify the issue, let me know.
Thanks for any help.

/etc/config/network

config interface 'loopback'
	option device 'lo'
	option proto 'static'
	option ipaddr '127.0.0.1'
	option netmask '255.0.0.0'

config globals 'globals'
	option ula_prefix 'fdfc:a61a:6142::/48'

config device
	option name 'br-lan'
	option type 'bridge'
	list ports 'eth1.1'

config interface 'lan'
	option device 'br-lan'
	option proto 'static'
	option netmask '255.255.255.0'
	option ip6assign '60'
	option ipaddr '10.0.0.1'
	option igmp_snooping '1'

config interface 'wan'
	option device 'eth0.2'
	option proto 'dhcp'

config interface 'wan6'
	option device 'eth0.2'
	option proto 'dhcpv6'

config switch
	option name 'switch0'
	option reset '1'
	option enable_vlan '1'

config switch_vlan
	option device 'switch0'
	option vlan '1'
	option ports '1 2 3 4 6t'

config switch_vlan
	option device 'switch0'
	option vlan '2'
	option ports '5 0t'

/etc/config/igmpproxy

config igmpproxy
	option quickleave '0'
	option verbose '2'

config phyint 'wan'
	option network 'wan'
	option zone 'wan'
	option direction 'upstream'
	option altnet '0.0.0.0/0'

config phyint 'lan'
	option network 'lan'
	option zone 'lan'
	option direction 'downstream'

Log output from igmpproxy

20:54:41 2023 user.notice igmpproxy[6824]: RECV V2 member report   from MY.PUBLIC.IPv4  to 239.255.255.250
20:54:41 2023 user.notice igmpproxy[6824]: The IGMP message was from myself. Ignoring.
20:54:41 2023 user.notice igmpproxy[6824]: Route activation request from MY.PUBLIC.IPv4 for 239.255.255.250 is from myself. Ignoring.
20:54:41 2023 user.notice igmpproxy[6824]: RECV V3 member report   from 10.0.0.140      to 224.0.0.22
20:54:41 2023 user.info igmpproxy[6824]: Inserted route table entry for 239.77.0.77 on VIF #0
20:54:41 2023 user.notice igmpproxy[6824]: Joining group 239.77.0.77 on interface eth0.2
20:54:41 2023 user.notice igmpproxy[6824]: RECV V2 member report   from MY.PUBLIC.IPv4  to 239.77.0.77
20:54:41 2023 user.notice igmpproxy[6824]: The IGMP message was from myself. Ignoring.
20:54:41 2023 user.notice igmpproxy[6824]: Route activation request from MY.PUBLIC.IPv4 for 239.77.0.77 is from myself. Ignoring.
20:54:42 2023 user.notice igmpproxy[6824]: Adding MFC: 77.109.129.16 -> 239.77.0.77, InpVIf: 1
20:54:42 2023 user.notice igmpproxy[6824]: RECV V3 member report   from 10.0.0.140      to 224.0.0.22
20:54:42 2023 user.info igmpproxy[6824]: Updated route entry for 239.77.0.77 on VIF #0
20:54:42 2023 user.notice igmpproxy[6824]: Adding MFC: 77.109.129.16 -> 239.77.0.77, InpVIf: 1
20:54:43 2023 user.notice igmpproxy[6824]: RECV V2 member report   from MY.PUBLIC.IPv4  to 239.77.0.77
20:54:43 2023 user.notice igmpproxy[6824]: The IGMP message was from myself. Ignoring.
20:54:46 2023 user.notice igmpproxy[6824]: RECV V2 member report   from MY.PUBLIC.IPv4  to 239.255.255.251
20:54:46 2023 user.notice igmpproxy[6824]: The IGMP message was from myself. Ignoring.
20:54:46 2023 user.notice igmpproxy[6824]: Route activation request from MY.PUBLIC.IPv4 for 239.255.255.251 is from myself. Ignoring.
20:54:49 2023 user.notice igmpproxy[6824]: RECV Membership query   from 10.0.0.1        to 224.0.0.1
20:54:49 2023 user.notice igmpproxy[6824]: RECV V2 member report   from 10.0.0.1        to 224.0.0.22
20:54:49 2023 user.notice igmpproxy[6824]: The IGMP message was from myself. Ignoring.
20:54:52 2023 user.notice igmpproxy[6824]: Removing MFC: 10.0.0.122 -> 239.255.255.251, InpVIf: 1
20:54:52 2023 user.notice igmpproxy[6824]: Leaving group 239.255.255.251 on interface eth0.2
20:54:53 2023 user.notice igmpproxy[6824]: RECV V2 member report   from 10.0.0.122      to 239.255.255.251
20:54:53 2023 user.info igmpproxy[6824]: Inserted route table entry for 239.255.255.251 on VIF #0
20:54:53 2023 user.notice igmpproxy[6824]: Joining group 239.255.255.251 on interface eth0.2
20:54:53 2023 user.notice igmpproxy[6824]: RECV V2 member report   from MY.PUBLIC.IPv4  to 239.255.255.251
20:54:53 2023 user.notice igmpproxy[6824]: The IGMP message was from myself. Ignoring.
20:54:56 2023 user.notice igmpproxy[6824]: RECV Membership query   from 10.0.0.1        to 224.0.0.1
20:54:56 2023 user.notice igmpproxy[6824]: RECV V2 member report   from 10.0.0.1        to 224.0.0.22
20:54:56 2023 user.notice igmpproxy[6824]: The IGMP message was from myself. Ignoring.
20:54:56 2023 user.notice igmpproxy[6824]: RECV V2 member report   from 10.0.0.122      to 239.255.255.250
20:54:56 2023 user.info igmpproxy[6824]: Updated route entry for 239.255.255.250 on VIF #0
20:54:56 2023 user.notice igmpproxy[6824]: Adding MFC: 10.0.0.134 -> 239.255.255.250, InpVIf: 1
20:54:56 2023 user.notice igmpproxy[6824]: Adding MFC: 10.0.0.229 -> 239.255.255.250, InpVIf: 1
20:54:57 2023 user.notice igmpproxy[6824]: RECV V2 member report   from 10.0.0.1        to 224.0.0.2
20:54:57 2023 user.notice igmpproxy[6824]: The IGMP message was from myself. Ignoring.
20:54:59 2023 user.notice igmpproxy[6824]: Adding MFC: 10.0.0.122 -> 239.255.255.251, InpVIf: 1
20:55:01 2023 user.notice igmpproxy[6824]: RECV V2 member report   from 10.0.0.134      to 239.255.255.250
20:55:01 2023 user.info igmpproxy[6824]: Updated route entry for 239.255.255.250 on VIF #0
20:55:01 2023 user.notice igmpproxy[6824]: Adding MFC: 10.0.0.134 -> 239.255.255.250, InpVIf: 1
20:55:01 2023 user.notice igmpproxy[6824]: Adding MFC: 10.0.0.229 -> 239.255.255.250, InpVIf: 1
20:55:01 2023 user.notice igmpproxy[6824]: RECV V2 member report   from MY.PUBLIC.IPv4  to 239.255.255.251
20:55:01 2023 user.notice igmpproxy[6824]: The IGMP message was from myself. Ignoring.
20:55:01 2023 user.notice igmpproxy[6824]: Route activation request from MY.PUBLIC.IPv4 for 239.255.255.251 is from myself. Ignoring.
20:55:07 2023 user.notice igmpproxy[6824]: RECV Membership query   from 10.0.0.1        to 224.0.0.1
20:55:10 2023 user.notice igmpproxy[6824]: Removing MFC: 77.109.129.16 -> 239.77.0.77, InpVIf: 1
20:55:10 2023 user.notice igmpproxy[6824]: Leaving group 239.77.0.77 on interface eth0.2
20:55:10 2023 user.notice igmpproxy[6824]: Removing MFC: 10.0.0.122 -> 239.255.255.251, InpVIf: 1
20:55:10 2023 user.notice igmpproxy[6824]: Leaving group 239.255.255.251 on interface eth0.2
20:55:10 2023 user.notice igmpproxy[6824]: RECV Membership query   from 85.195.215.129  to 239.77.0.77
20:55:11 2023 user.notice igmpproxy[6824]: RECV Membership query   from 85.195.215.129  to 239.77.0.77
20:55:13 2023 user.notice igmpproxy[6824]: RECV V2 member report   from 10.0.0.1        to 224.0.0.2
20:55:13 2023 user.notice igmpproxy[6824]: The IGMP message was from myself. Ignoring.
20:55:16 2023 user.notice igmpproxy[6824]: RECV Membership query   from 10.0.0.1        to 224.0.0.1
20:55:16 2023 user.notice igmpproxy[6824]: RECV V2 member report   from 10.0.0.1        to 224.0.0.22
20:55:16 2023 user.notice igmpproxy[6824]: The IGMP message was from myself. Ignoring.
20:55:16 2023 user.notice igmpproxy[6824]: RECV V2 member report   from 10.0.0.182      to 239.255.255.250
20:55:16 2023 user.info igmpproxy[6824]: Updated route entry for 239.255.255.250 on VIF #0
20:55:16 2023 user.notice igmpproxy[6824]: Adding MFC: 10.0.0.134 -> 239.255.255.250, InpVIf: 1
20:55:16 2023 user.notice igmpproxy[6824]: Adding MFC: 10.0.0.229 -> 239.255.255.250, InpVIf: 1
20:55:19 2023 user.notice igmpproxy[6824]: RECV V2 member report   from 10.0.0.122      to 239.255.255.251
20:55:19 2023 user.info igmpproxy[6824]: Inserted route table entry for 239.255.255.251 on VIF #0
20:55:19 2023 user.notice igmpproxy[6824]: Joining group 239.255.255.251 on interface eth0.2
20:55:19 2023 user.notice igmpproxy[6824]: RECV V2 member report   from MY.PUBLIC.IPv4  to 239.255.255.251
20:55:19 2023 user.notice igmpproxy[6824]: The IGMP message was from myself. Ignoring.
20:55:19 2023 user.notice igmpproxy[6824]: Route activation request from MY.PUBLIC.IPv4 for 239.255.255.251 is from myself. Ignoring.
20:55:21 2023 user.notice igmpproxy[6824]: RECV V2 member report   from 10.0.0.122      to 239.255.255.250
20:55:21 2023 user.info igmpproxy[6824]: Updated route entry for 239.255.255.250 on VIF #0
20:55:21 2023 user.notice igmpproxy[6824]: Adding MFC: 10.0.0.134 -> 239.255.255.250, InpVIf: 1
20:55:21 2023 user.notice igmpproxy[6824]: Adding MFC: 10.0.0.229 -> 239.255.255.250, InpVIf: 1
20:55:24 2023 user.notice igmpproxy[6824]: RECV V2 member report   from MY.PUBLIC.IPv4  to 239.255.255.251
20:55:24 2023 user.notice igmpproxy[6824]: The IGMP message was from myself. Ignoring.
20:55:25 2023 user.notice igmpproxy[6824]: RECV V2 member report   from 10.0.0.1        to 224.0.0.2
20:55:25 2023 user.notice igmpproxy[6824]: The IGMP message was from myself. Ignoring.
20:55:28 2023 user.notice igmpproxy[6824]: RECV Membership query   from 10.0.0.1        to 224.0.0.1
20:55:31 2023 user.notice igmpproxy[6824]: Leaving group 239.255.255.251 on interface eth0.2
20:55:32 2023 user.notice igmpproxy[6824]: RECV V2 member report   from 10.0.0.1        to 224.0.0.22
20:55:32 2023 user.notice igmpproxy[6824]: The IGMP message was from myself. Ignoring.
20:55:33 2023 user.notice igmpproxy[6824]: RECV V2 member report   from 10.0.0.134      to 239.255.255.250
20:55:33 2023 user.info igmpproxy[6824]: Updated route entry for 239.255.255.250 on VIF #0
20:55:33 2023 user.notice igmpproxy[6824]: Adding MFC: 10.0.0.134 -> 239.255.255.250, InpVIf: 1
20:55:33 2023 user.notice igmpproxy[6824]: Adding MFC: 10.0.0.229 -> 239.255.255.250, InpVIf: 1
20:55:35 2023 user.notice igmpproxy[6824]: RECV V2 member report   from 10.0.0.122      to 239.255.255.251
20:55:35 2023 user.info igmpproxy[6824]: Inserted route table entry for 239.255.255.251 on VIF #0
20:55:35 2023 user.notice igmpproxy[6824]: Joining group 239.255.255.251 on interface eth0.2
20:55:35 2023 user.notice igmpproxy[6824]: RECV V2 member report   from MY.PUBLIC.IPv4  to 239.255.255.251
20:55:35 2023 user.notice igmpproxy[6824]: The IGMP message was from myself. Ignoring.
20:55:35 2023 user.notice igmpproxy[6824]: Route activation request from MY.PUBLIC.IPv4 for 239.255.255.251 is from myself. Ignoring.
20:55:35 2023 user.notice igmpproxy[6824]: RECV V2 member report   from 10.0.0.182      to 239.255.255.250
20:55:35 2023 user.info igmpproxy[6824]: Updated route entry for 239.255.255.250 on VIF #0
20:55:35 2023 user.notice igmpproxy[6824]: Adding MFC: 10.0.0.134 -> 239.255.255.250, InpVIf: 1
20:55:35 2023 user.notice igmpproxy[6824]: Adding MFC: 10.0.0.229 -> 239.255.255.250, InpVIf: 1
20:55:36 2023 user.notice igmpproxy[6824]: RECV Leave message      from 10.0.0.177      to 224.0.0.2
20:55:37 2023 user.notice igmpproxy[6824]: RECV V2 member report   from 10.0.0.1        to 224.0.0.2
20:55:37 2023 user.notice igmpproxy[6824]: The IGMP message was from myself. Ignoring.
20:55:38 2023 user.notice igmpproxy[6824]: RECV Leave message      from 10.0.0.177      to 224.0.0.2
20:55:39 2023 user.notice igmpproxy[6824]: RECV Membership query   from 85.195.215.129  to 224.0.0.1
20:55:40 2023 user.notice igmpproxy[6824]: RECV Leave message      from 10.0.0.177      to 224.0.0.2
20:55:40 2023 user.notice igmpproxy[6824]: RECV V2 member report   from MY.PUBLIC.IPv4  to 239.255.255.251
20:55:40 2023 user.notice igmpproxy[6824]: The IGMP message was from myself. Ignoring.
20:55:41 2023 user.notice igmpproxy[6824]: RECV V2 member report   from MY.PUBLIC.IPv4  to 239.255.255.250
20:55:41 2023 user.notice igmpproxy[6824]: The IGMP message was from myself. Ignoring.
20:55:41 2023 user.notice igmpproxy[6824]: Route activation request from MY.PUBLIC.IPv4 for 239.255.255.250 is from myself. Ignoring.

lleachii · December 3, 2023, 1:07pm

Have you tried:

option quickleave '1'

?

billybob · December 3, 2023, 1:46pm

Yes, I tried both quickleave '0' and quickleave '1' without success. Based on this thread [SOLVED] Init7 iptv / Configuration - #5 by slackito

I wonder if it has something to do with the eth0.2 interface? In the log it says Joining group 239.77.0.77 on interface eth0.2 which is the WAN interface. But the LAN interface is eth1.1 I don't know whether that is an issue or not

slackito · December 3, 2023, 10:08pm

i gave up using igmpproxy and went with udpxy, which works like a charm. maybe consider using that too?
its a small change that needs to be done
but yeah, the .2 is usually the interface for init7 which is not required

config interface 'wan'
        option _orig_ifname 'eth2.132'
        option _orig_bridge 'false'
        option peerdns '0'
        option proto 'dhcp'
        option macaddr '24:A4:xx:xx:xx:xx'
        option device 'eth2'

xize · December 3, 2023, 10:30pm

Hmm do you maybe use a switch between the router and the tv box?, im just going to make a wild guess here but could it be that the switch is running its own igmp stack and manages to sent packets back with the routers source mac?

I once managed to do that myself since then i decided to avoid setting up igmp on managed switches

slackito · December 4, 2023, 11:47am

fwiw: i had the same messages without any switch, directly ftth->router->tv

xize · December 4, 2023, 1:25pm

hmm and there is also not a switch somewhere else in your network advertising as igmp stack?

the thing I'm also looking at is this here:

20:55:32 2023 user.notice igmpproxy[6824]: RECV V2 member report   from 10.0.0.1        to 224.0.0.22
20:55:32 2023 user.notice igmpproxy[6824]: The IGMP message was from myself. Ignoring.
20:55:33 2023 user.notice igmpproxy[6824]: RECV V2 member report   from 10.0.0.134      to 239.255.255.250
20:55:33 2023 user.info igmpproxy[6824]: Updated route entry for 239.255.255.250 on VIF #0
20:55:33 2023 user.notice igmpproxy[6824]: Adding MFC: 10.0.0.134 -> 239.255.255.250, InpVIf: 1
20:55:33 2023 user.notice igmpproxy[6824]: Adding MFC: 10.0.0.229 -> 239.255.255.250, InpVIf: 1

I see 224.0.0.0 range this is often OpenWrt's one, but I also see 239.255.255.250 sometimes I see these type of addresses multicasted from switches beginning with 239, though it looks like the end so probably a broadcast address but can you verify?

also do you run a instance like avahi/samba ?, this might be also causing issues if it does you could make avahis rules more strict to where it listens to.

slackito · December 4, 2023, 1:58pm

i did not ask here, my problem was solved by switching from igmpproxy to udpxy. billybob has its own problems now with this.
i had the same logs, see in the first thread. and no, i have NO switch whatsoever. my network-stack is: ftth provider -> router -> end-devices
nothing else. no avahi, no samba, nothing.
https://extreme-networks.my.site.com/ExtrArticleDetail?an=000091058
239.x multicasts are part of igmp

xize · December 4, 2023, 2:47pm

oh I see I confused you with OP excuse.

billybob · December 6, 2023, 8:55pm

Thanks for the answers both of you. And nice to see you on this thread @slackito
So I tried udpxy, and disabled igmpproxy, but without any luck.
Here's my udpxy config

config udpxy
	option disabled '0'
	option respawn '1'
	option verbose '1'
	option status '1'
	option bind '10.0.0.1'
	option port '4022'
	# option source '0.0.0.0'
	# option max_clients '3'
	option log_file '/var/log/udpxy'
	# option buffer_size '4096'
	# option buffer_messages '-1'
	# option buffer_time '-1'
	# option nice_increment '0'
	# option mcsub_renew '0'

I've tried streaming using VLC or jellyfin with for example http://10.0.0.1:4022/rtp/239.77.0.77:5000 and http://10.0.0.1:4022/udp/239.77.0.77:5000 where 10.0.0.1 is the LAN ip of the router. It looks as if the requests are going through to the udpxy daemon on the openWRT router. I can see the IP and user-agent of the client in the logs. But no success in opening the stream.

Here's a log from udpxy:

2023-12-06 20:36:46.382350 UTC	S(28860)	No children exited since last check
2023-12-06 20:36:46.382521 UTC	S(28860)	Got 1 requests
2023-12-06 20:36:46.382626 UTC	S(28860)	Accepting new connection
2023-12-06 20:36:46.382750 UTC	S(28860)	Accepted socket=[9] from 10.0.0.140:46564 n=1/nmax=16
2023-12-06 20:36:46.382850 UTC	S(28860)	Accepting new connection
2023-12-06 20:36:46.382959 UTC	S(28860)	Nothing more to accept
2023-12-06 20:36:46.383049 UTC	S(28860)	accept_requests: Sockets accepted: [1]
2023-12-06 20:36:46.383139 UTC	S(28860)	Waiting for input from [3] fd's, with timeout
2023-12-06 20:36:46.383245 UTC	S(28860)	No children exited since last check
2023-12-06 20:36:46.383334 UTC	S(28860)	Got 1 requests
pre-process sockets [1]: 9
2023-12-06 20:36:46.383439 UTC	S(28860)	acting on accepted socket [9] (1/1)
2023-12-06 20:36:46.383531 UTC	S(28860)	Reading command from socket [9]
2023-12-06 20:36:46.383635 UTC	S(28860)	HTTP buffer [152 bytes] received
GET /udp/239.77.0.77:5000/ HTTP/1.1
Host: 10.0.0.1:4022
Accept: */*
Accept-Language: en_US
User-Agent: VLC/3.0.20 LibVLC/3.0.20
Range: bytes=0-

2023-12-06 20:36:46.383739 UTC	S(28860)	Request=[udp/239.77.0.77:5000/], length=[21]
2023-12-06 20:36:46.383831 UTC	S(28860)	Command [udp] with params [239.77.0.77:5000/], tail [] read from socket=[9]
2023-12-06 20:36:46.383925 UTC	S(28860)	udp_relay : new_socket=[9] param=[239.77.0.77:5000/]
2023-12-06 20:36:46.384194 UTC	S(28860)	Added client: pid=[30198], maddr=[239.77.0.77], mport=[5000], saddr=[10.0.0.140], sport=[46564]
2023-12-06 20:36:46.384332 UTC	S(28860)	process_requests: closing accepted socket [9]
2023-12-06 20:36:46.384455 UTC	S(28860)	Processed [1/1] accepted sockets
newly-accepted sockets [1]: -1
2023-12-06 20:36:46.384412 UTC	S(28860)	Client process=[30198] started for socket=[9]
2023-12-06 20:36:46.384562 UTC	S(28860)	All accepted sockets processed
2023-12-06 20:36:46.384627 UTC	c(30198)	min socket buffer = [65536], max space to use = [1500], Rmsgs = [1]
2023-12-06 20:36:46.384655 UTC	S(28860)	Waiting for input from [2] fd's, NO timeout
2023-12-06 20:36:46.384730 UTC	c(30198)	Setting up multicast listener
2023-12-06 20:36:46.384844 UTC	c(30198)	current receive buffer size is [180224] bytes for socket [6]
2023-12-06 20:36:46.384989 UTC	c(30198)	multicast-group [ADD]
2023-12-06 20:36:46.385089 UTC	c(30198)	Mcast listener socket=[6] set up
2023-12-06 20:36:46.385186 UTC	c(30198)	min socket buffer = [65536], max space to use = [1500], Rmsgs = [1]
2023-12-06 20:36:46.385281 UTC	c(30198)	Data buffer will hold up to [1] messages
2023-12-06 20:36:46.385372 UTC	c(30198)	UDP stream, RTP check enabled
2023-12-06 20:36:46.385681 UTC	c(30198)	socket 6: RCV timeout set to 138064 sec, 5 usec
2023-12-06 20:36:46.385796 UTC	c(30198)	socket 6: SEND timeout set to 138064 sec, 5 usec
2023-12-06 20:36:46.385892 UTC	c(30198)	current send buffer size is [44800] bytes for socket [9]
2023-12-06 20:36:46.385987 UTC	c(30198)	current receive buffer size is [180224] bytes for socket [6]
2023-12-06 20:36:46.386083 UTC	c(30198)	send buffer size set to [180224] bytes for socket [9]
2023-12-06 20:36:46.386251 UTC	c(30198)	Sent HTTP response code=[200], reason=[OK] to socket=[9]
HTTP/1.1 200 OK
Server: udpxy 1.0-25.1 (prod) standard [Linux 5.15.134 armv7l]
Content-Type:application/octet-stream


2023-12-06 20:36:46.386394 UTC	c(30198)	Relaying traffic from socket[6] to socket[9], buffer size=[2048], Rmsgs=[1], pauses=[0]
2023-12-06 20:36:51.419636 UTC	c(30198)	read_buf: socket time-out on read2023-12-06 20:36:51.419805 UTC	c(30198)	read_data - EOF
2023-12-06 20:36:51.419912 UTC	c(30198)	Exited relay loop: received=[-1], sent=[0], quit=[0]
2023-12-06 20:36:51.420090 UTC	c(30198)	multicast-group [DROP]
2023-12-06 20:36:51.420211 UTC	c(30198)	Mcast listener socket=[6] closed
2023-12-06 20:36:51.420382 UTC	c(30198)	Child process=[30198] exits with rc=[0]
2023-12-06 20:36:51.420758 UTC	S(28860)	*** Caught SIGCHLD (17) ***
2023-12-06 20:36:51.420894 UTC	S(28860)	Waiting on exited children
2023-12-06 20:36:51.421008 UTC	S(28860)	Client [30198] has exited.
2023-12-06 20:36:51.421112 UTC	S(28860)	Deleted client: pid=[30198]
2023-12-06 20:36:51.421205 UTC	S(28860)	Cleaned up 1 children, 0 still running
2023-12-06 20:36:51.421296 UTC	S(28860)	INTERRUPTED, yet will continue.
2023-12-06 20:36:51.421385 UTC	S(28860)	Waiting for input from [2] fd's, NO timeout

It seems to not be able to open the stream, getting an EOF instead, as on this line of the log: read_buf: socket time-out on read2023-12-06 20:36:51.419805 UTC c(30198) read_data - EOF

As for having a switch on the network @xize, I do. I've tried removing it so there is only the openWRT router, without success. But per @slackito it seems 239.x are linked to igmp multicast anyways.

billybob · December 6, 2023, 9:09pm

Success!
A firewall rule accepting input on port 5000 was required. I guess this is so that the incoming stream can actually get past the firewall.
I wonder if this was the same reason igmpproxy was not working, will investigate.
Thanks for the help!

slackito · December 6, 2023, 10:20pm

igmp is enabled by default in openwrt's firewall, whereas udpxy (which uses tcp) is not. so i dont think any modification to the firewall will fix your igmpproxy problem. in any way, udpxy is probably a better choice. you can use wifi devices and watch TV without flooding the network

billybob · December 8, 2023, 10:10pm

After some more testing, it appears the firewall rule in the docs (https://openwrt.org/docs/guide-user/network/wan/udp_multicast#firewall_configuration_for_udpxy) with dest_ip 224.0.0.0/4 is needed for either igmpproxy or udpxy. I guess the automatic rule insertion only works for iptables and not nftables.

I don't really mind not being able to have iptv on the wifi clients, as all the iptv streaming will pass through a jellyfin server that has a wired connection.

Igmpproxy had the advantage of being able to directly use the .m3u file provided by init7. With udpxy, you need to prefix the udp adress with something like http://192.168.1.1:4022/rtp/224.0.1.2:345/. But igmpproxy required an additional firewall on the iptv client. And the iptv stream seemed to drop after 20-30 seconds. Disabling the firewall seemed to fix the stream dropping, but isn't a proper solution.

So I went with udpxy in the end, which gives a stable iptv stream and doesn't need a firewall config on the client.

Thanks again for the help!

system · December 18, 2023, 10:12pm

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.