Starting mcproxy over openwrt

shar...@t-online.de

unread,

Jun 25, 2016, 1:15:27 PM6/25/16

to Multicast Proxy

Hi,

when I start the mcproxy I get the following error
ERROR: failed to parse line 12 unknown token TT_RANGE with value , expected ":" or "upstream" or "downstream"

The following information has the line 12
pinstance Entertain-IPTV: "eth2.7" ==> "eth0.50"

The folling information has the "mcproxy -c"

heck the currently available kernel features.
 - root privileges: Ok!

 - ipv4 multicast: Ok!
 - ipv4 multiple routing tables: Ok!
 - ipv4 routing tables: Ok!

 - ipv4 mcproxy was able to join 40+ groups successfully (no limit found)
 - ipv4 mcproxy was able to set 40+ filters successfully (no limit found)

 - ipv6 multicast: Ok!
 - ipv6 multiple routing tables: Ok!
 - ipv6 routing tables: Ok!

 - ipv6 mcproxy was able to join 40+ groups successfully (no limit found)
 - ipv6 mcproxy was able to set 40+ filters successfully (no limit found)

The following information has the "ifconfig"
eth0      Link encap:Ethernet  HWaddr 00:0D:B9:3A:38:44  
          inet6 addr: fe80::20d:b9ff:fe3a:3844/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:14997 errors:0 dropped:0 overruns:0 frame:0
          TX packets:13381 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1868688 (1.7 MiB)  TX bytes:4723992 (4.5 MiB)

eth0.1    Link encap:Ethernet  HWaddr 00:0D:B9:3A:38:44  
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::20d:b9ff:fe3a:3844/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:417 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1115 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:29002 (28.3 KiB)  TX bytes:93754 (91.5 KiB)

eth0.100  Link encap:Ethernet  HWaddr 00:0D:B9:3A:38:44  
          inet addr:192.168.20.1  Bcast:192.168.20.255  Mask:255.255.255.0
          inet6 addr: fe80::20d:b9ff:fe3a:3844/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5139 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2058 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:392900 (383.6 KiB)  TX bytes:260859 (254.7 KiB)

eth0.50   Link encap:Ethernet  HWaddr 00:0D:B9:3A:38:44  
          inet addr:192.168.10.1  Bcast:192.168.10.255  Mask:255.255.255.0
          inet6 addr: fe80::20d:b9ff:fe3a:3844/64 Scope:Link
          inet6 addr: fd1c:3e94:43b::1/60 Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:9424 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10204 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:1173840 (1.1 MiB)  TX bytes:4368931 (4.1 MiB)

eth2      Link encap:Ethernet  HWaddr 00:0D:B9:3A:38:46  
          inet6 addr: fe80::20d:b9ff:fe3a:3846/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:10263 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8513 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:4622154 (4.4 MiB)  TX bytes:1267283 (1.2 MiB)

eth2.7    Link encap:Ethernet  HWaddr 00:0D:B9:3A:38:46  
          inet6 addr: fe80::20d:b9ff:fe3a:3846/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:10052 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8509 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:4408440 (4.2 MiB)  TX bytes:1266835 (1.2 MiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:589 errors:0 dropped:0 overruns:0 frame:0
          TX packets:589 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:61461 (60.0 KiB)  TX bytes:61461 (60.0 KiB)

pppoe-wan Link encap:Point-to-Point Protocol  
          inet addr:ww.xxx.yyy.z  P-t-P:ww.xxx.yyy.zzz  Mask:255.255.255.255
          inet6 addr: fe80::5c14:6d0:8417:f5d1/10 Scope:Link
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1492  Metric:1
          RX packets:9569 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8022 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3 
          RX bytes:4311483 (4.1 MiB)  TX bytes:1075364 (1.0 MiB)

wlan0     Link encap:Ethernet  HWaddr 04:F0:21:14:C8:36  
          inet addr:192.168.30.1  Bcast:192.168.30.255  Mask:255.255.255.0
          inet6 addr: fe80::6f0:21ff:fe14:c836/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2735 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2798 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:503653 (491.8 KiB)  TX bytes:652174 (636.8 KiB)


The multicast channels can be found online . The receiver is in VLAN eth0.50.
Where should I look for the problem?

Thank for helping.

Stefan Harbich

shar...@t-online.de

unread,

Jun 25, 2016, 4:55:23 PM6/25/16

to Multicast Proxy

Hi,

I do not understand is that all interfaces in mc_forwarding set 0
net.ipv4.conf.all.mc_forwarding = 0
net.ipv4.conf.default.mc_forwarding = 0
net.ipv4.conf.eth0.mc_forwarding = 0
net.ipv4.conf.eth0.1.mc_forwarding = 0
net.ipv4.conf.eth0.100.mc_forwarding = 0
net.ipv4.conf.eth0.50.mc_forwarding = 0
net.ipv4.conf.eth1.mc_forwarding = 0
net.ipv4.conf.eth2.mc_forwarding = 0
net.ipv4.conf.eth2.7.mc_forwarding = 0
net.ipv4.conf.ifb0.mc_forwarding = 0
net.ipv4.conf.ifb1.mc_forwarding = 0
net.ipv4.conf.lo.mc_forwarding = 0
net.ipv4.conf.pppoe-wan.mc_forwarding = 0
net.ipv4.conf.wlan0.mc_forwarding = 0

Message has been deleted

shar...@t-online.de

unread,

Jun 27, 2016, 5:59:48 AM6/27/16

to Multicast Proxy

Hi,
supported mcproxy the pppoe protocol on the wan site?

Thanks for helping.

Stefan Harbich

nutel...@gmail.com

unread,

Jun 27, 2016, 6:12:11 AM6/27/16

to Multicast Proxy

Hello Stefan Harbich,

if you use the proxy instance "Entertain_IPTV" instead of "Entertain-IPTV", then it should work.
Or I think you could put Entertain-IPTV within quotation marks.
Unfortunately, the token "-" is not allowed by the parser in names, it is used to indicate ranges (e. g. from 1 to 10).

Kind Regards,
Sebastian

Am Samstag, 25. Juni 2016 19:15:27 UTC+2 schrieb shar...@t-online.de:

shar...@t-online.de

unread,

Jun 27, 2016, 11:21:06 AM6/27/16

to Multicast Proxy, nutel...@gmail.com

Hello Sebastin,
the next error information is "failed to add interface", when i change the mcproxy.con via
pinstance Entertain_IPTV: "pppoe-wan" ==> "eth0.50";
i see the next error

root@rome01:~# mcproxy -d -f /etc/mcproxy.conf 
BusyBox v1.22.1 (2016-06-23 17:51:14 CEST)BusyBox v1.22.1 (2016-06-23 17:51:14 CEST) multi-call binary.

Usage: ip [OPTIONS] {address | route | link | tunnel | rule} {COMMAND}

ip [OPTIONS] OBJECT {COMMAND}
where OBJECT := {address | route | link | tunnel | rule}
OPTIONS := { -f[amily] { inet | inet6 | link } | -o[neline] }

ERROR: failed to bind vif to table! Error on cmd: ip mrule add iif eth0.100 lookup 2
 multi-call binary.

Usage: ip [OPTIONS] {address | route | link | tunnel | rule} {COMMAND}

ip [OPTIONS] OBJECT {COMMAND}
where OBJECT := {address | route | link | tunnel | rule}
OPTIONS := { -f[amily] { inet | inet6 | link } | -o[neline] }

ERROR: failed to bind vif to table! Error on cmd: ip mrule add iif pppoe-wan lookup 1
BusyBox v1.22.1 (2016-06-23 17:51:14 CEST)BusyBox v1.22.1 (2016-06-23 17:51:14 CEST) multi-call binary.

Usage: ip [OPTIONS] {address | route | link | tunnel | rule} {COMMAND}

ip [OPTIONS] OBJECT {COMMAND}
where OBJECT := {address | route | link | tunnel | rule}
OPTIONS := { -f[amily] { inet | inet6 | link } | -o[neline] }

ERROR: failed to bind vif to table! Error on cmd: ip mrule add iif eth0.50 lookup 2
 multi-call binary.

Usage: ip [OPTIONS] {address | route | link | tunnel | rule} {COMMAND}

ip [OPTIONS] OBJECT {COMMAND}
where OBJECT := {address | route | link | tunnel | rule}
OPTIONS := { -f[amily] { inet | inet6 | link } | -o[neline] }

ERROR: failed to bind vif to table! Error on cmd: ip mrule add iif eth0.50 lookup 1
BusyBox v1.22.1 (2016-06-23 17:51:14 CEST) multi-call binary.

Usage: ip [OPTIONS] {address | route | link | tunnel | rule} {COMMAND}

ip [OPTIONS] OBJECT {COMMAND}
where OBJECT := {address | route | link | tunnel | rule}
OPTIONS := { -f[amily] { inet | inet6 | link } | -o[neline] }

ERROR: failed to bind vif to table! Error on cmd: ip mrule add iif wlan0 lookup 2

Whout i can do for the erro information?

Thanks for helping.

Stefan Harbich

nutel...@gmail.com

unread,

Jun 27, 2016, 12:00:20 PM6/27/16

to Multicast Proxy, nutel...@gmail.com

Hello Stefan Harbich,

Mcproxy cannot add the interfaces (vif = virtual interface) to the multicast routing table, which is managed by your operating system.
It looks like these errors are specific to your operating system.
I cannot help you here.

Kind Regards,
Sebastian

shar...@t-online.de

unread,

Jun 27, 2016, 3:47:19 PM6/27/16

to Multicast Proxy, nutel...@gmail.com

Hallo Sebastian,
pity, many ISP in Germany provide a login via pppoe in the internet and then offer IPTV via multicast. Okay over the igmpproxy is the routing possible. But in the igmpproxy i can configure one upstream interface. But i have in the DMZ the secount multicast server. Okay for my situation there as no solution (igmpproxy, pimd, mrouted, mcproxy, smcroute are not give my a solution), Any Idea?

Pity, pity, pity

Thanks for helping.

Stefan Harbich

Reply all

Reply to author

Forward