Closed roymelzer closed 1 year ago
Can you check if the igmpproxy is running?
systemctl status igmpproxy
Please disable it as follows:
systemctl disable --now igmpproxy
If that doesn’t work, try to switch to improxy as IGMP Proxy implementation.
Hi @fabianishere,
Thank you for the fast response.
Then the output of the diagnose is:
Please share the following output with the developers:
=== Configuration ===
WAN Interface: eth8
WAN VLAN: 4 (dev iptv)
WAN DHCP: true (options "-O staticroutes -V IPTV_RG")
WAN Ranges: 213.75.0.0/16 217.166.0.0/16
LAN Interfaces: br0
IGMP Proxy quickleave disabled: true
IGMP Proxy debug: false
=== IP Link and Route ===
36: iptv@eth8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
inet 10.23.137.4/22 brd 10.23.139.255 scope global iptv
valid_lft forever preferred_lft forever
10.23.136.0/22 proto kernel scope link src 10.23.137.4
213.75.112.0/21 via 10.23.136.1 metric 236
=== Service Logs ===
Feb 18 18:15:40 xxx udm-iptvd[22288]: Obtaining IP address for VLAN interface
Feb 18 18:15:40 xxx udm-iptvd[22288]: udhcpc (v1.22.1) started
Feb 18 18:15:40 xxx udm-iptvd[22288]: Sending discover...
Feb 18 18:15:40 xxx udm-iptvd[22288]: Sending select for 10.23.137.4...
Feb 18 18:15:40 xxx udm-iptvd[22288]: Lease of 10.23.137.4 obtained, lease time 3600
Feb 18 18:15:40 xxx udm-iptvd[22288]: NATing IPTV network ranges (if necessary)
Feb 18 18:15:40 xxx udm-iptvd[22288]: Creating static routes (if necessary)
Feb 18 18:15:40 xxx udm-iptvd[22288]: Setting up IGMP Proxy
Feb 18 18:15:40 xxx udm-iptvd[22288]: Using igmpproxy...
Feb 18 18:15:40 xxx udm-iptvd[22288]: Starting IGMP Proxy
This is similar as it was before rebooting my UDM-Pro but still no connection from the tv modules which repeat in the F301 error
And when changing to improxy (v3)
Please share the following output with the developers:
=== Configuration ===
WAN Interface: eth8
WAN VLAN: 4 (dev iptv)
WAN DHCP: true (options "-O staticroutes -V IPTV_RG")
WAN Ranges: 213.75.0.0/16 217.166.0.0/16
LAN Interfaces: br0
IGMP Proxy quickleave disabled: true
IGMP Proxy debug: false
=== IP Link and Route ===
39: iptv@eth8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
inet 10.23.137.46/22 brd 10.23.139.255 scope global iptv
valid_lft forever preferred_lft forever
10.23.136.0/22 proto kernel scope link src 10.23.137.46
213.75.112.0/21 via 10.23.136.1 metric 239
=== Service Logs ===
Feb 18 18:36:12 xxx udm-iptvd[29851]: Obtaining IP address for VLAN interface
Feb 18 18:36:12 xxx udm-iptvd[29851]: udhcpc (v1.22.1) started
Feb 18 18:36:12 xxx udm-iptvd[29851]: Sending discover...
Feb 18 18:36:12 xxx udm-iptvd[29851]: Sending select for 10.23.137.46...
Feb 18 18:36:12 xxx udm-iptvd[29851]: Lease of 10.23.137.46 obtained, lease time 3600
Feb 18 18:36:13 xxx udm-iptvd[29851]: NATing IPTV network ranges (if necessary)
Feb 18 18:36:13 xxx udm-iptvd[29851]: Creating static routes (if necessary)
Feb 18 18:36:13 xxx udm-iptvd[29851]: Setting up IGMP Proxy
Feb 18 18:36:13 xxx udm-iptvd[29851]: Using improxy...
Feb 18 18:36:13 xxx udm-iptvd[29851]: Starting IGMP Proxy
but still no connection from the tv modules which repeat in the F301 error
and improxy v2:
Please share the following output with the developers:
=== Configuration ===
WAN Interface: eth8
WAN VLAN: 4 (dev iptv)
WAN DHCP: true (options "-O staticroutes -V IPTV_RG")
WAN Ranges: 213.75.0.0/16 217.166.0.0/16
LAN Interfaces: br0
IGMP Proxy quickleave disabled: true
IGMP Proxy debug: false
=== IP Link and Route ===
41: iptv@eth8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
inet 10.23.137.46/22 brd 10.23.139.255 scope global iptv
valid_lft forever preferred_lft forever
10.23.136.0/22 proto kernel scope link src 10.23.137.46
213.75.112.0/21 via 10.23.136.1 metric 241
=== Service Logs ===
Feb 18 18:38:33 xxx udm-iptvd[2297]: Obtaining IP address for VLAN interface
Feb 18 18:38:33 xxx udm-iptvd[2297]: udhcpc (v1.22.1) started
Feb 18 18:38:33 xxx udm-iptvd[2297]: Sending discover...
Feb 18 18:38:34 xxx udm-iptvd[2297]: Sending select for 10.23.137.46...
Feb 18 18:38:34 xxx udm-iptvd[2297]: Lease of 10.23.137.46 obtained, lease time 3600
Feb 18 18:38:34 xxx udm-iptvd[2297]: NATing IPTV network ranges (if necessary)
Feb 18 18:38:34 xxx udm-iptvd[2297]: Creating static routes (if necessary)
Feb 18 18:38:34 xxx udm-iptvd[2297]: Setting up IGMP Proxy
Feb 18 18:38:34 xxx udm-iptvd[2297]: Using improxy...
Feb 18 18:38:34 xxx udm-iptvd[2297]: Starting IGMP Proxy
but still no connection from the tv modules which repeat in the F301 error
Not sure what is wrong at this moment :/
Settings from the VLAN:
If the tv modules are on the iptv vlan4 than you should also put this in the config. You have br0 configured for the lan. This should be br4.
If the tv modules are on the iptv vlan4 than you should also put this in the config. You have br0 configured for the lan. This should be br4.
Not sure about that point if it also should be 4... I used the configure script and selected the right VLAN during setup (multiple times) which always ended up as br0. How to evaluate which brX should be used manually?
BrX is numbered after the vlan id. You created a vlan called iptv with id4 so br4 Why the script didn’t work I cannot tell you. You could edit the config file yourself.
@reinierjh is right. If your STBs are on VLAN 4, br4 must be enabled in your config.
Thank you very much @reinierjh and @fabianishere for the quick help. Fixing the brX to the right number and just turning it back to default igmpproxy made it to work 👍
Hi,
Since last week my UDM-Pro was updated to 2.4.27. As suggested; I re-installed the packages via:
sh -c "$(curl https://raw.githubusercontent.com/fabianishere/udm-iptv/master/install.sh -sSf)"
Also re-configured the settings:start logging (output of diagnose command)
Before rebooting, it wasn't working either but I did not get the
can't join group 239.255.255.253 on interface iptv; Errno(98): Address already in use
andNo interfaces found for source 0.0.0.0
messages.Could anyone please help out here?
Ps. Before upgrade it worked for over a year as a charm (even the intermediate updates went without issues) Please let me know if I should provide any aditional information