OTT Services
Closed this issue · 5 comments
Veldkornet commented
Are the OTT services (Netflix channel 200, terugkijken) supposed to be working with this config?
On Netflix for example, I just get a black screen.
slootjes commented
Yes, it should work just fine.
Veldkornet commented
Hmm, strange. For me it’s not working on the USG-4-Pro (Firmware 4.4.46, controller 5.12.22), although IPTV is working fine.
Veldkornet commented
I don’t really see anything wrong with the config.... (eth0 = LAN, eth2 = WAN, decoders on eth0.4)
{
"interfaces": {
"bridge": {
"br0": {
"aging": "300",
"bridged-conntrack": "disable",
"hello-time": "2",
"max-age": "20",
"priority": "32768",
"promiscuous": "disable",
"stp": "false"
}
},
"ethernet": {
"eth2": {
"description": "eth2 - FTTH",
"duplex": "auto",
"speed": "auto",
"vif": {
"4": {
"address": [
"dhcp"
],
"description": "eth2.4 - IPTV",
"dhcp-options": {
"client-option": [
"send vendor-class-identifier "IPTV_RG";",
"request subnet-mask, routers, rfc3442-classless-static-routes;"
],
"default-route": "no-update",
"default-route-distance": "210",
"name-server": "update"
},
"ip": {
"source-validation": "loose"
}
},
"6": {
"description": "eth2.6 - Internet",
"firewall": {
"in": {
"name": "WAN_IN"
},
"local": {
"name": "WAN_LOCAL"
},
"out": {
"name": "WAN_OUT"
}
},
"pppoe": {
"2": {
"default-route": "auto",
"firewall": {
"in": {
"name": "WAN_IN"
},
"local": {
"name": "WAN_LOCAL"
},
"out": {
"name": "WAN_OUT"
}
},
"mtu": "1492",
"name-server": "none",
"password": "kpn",
"user-id": "xx-xx-xx-xx-xx-xx@internet"
}
}
},
"7": {
"bridge-group": {
"bridge": "br0"
},
"description": "eth2.7 - VOIP",
"mtu": "1500"
}
}
},
"eth0": {
"description": "eth0 - LAN",
"address": [
"192.168.1.1/24"
],
"duplex": "auto",
"firewall": {
"in": {
"name": "LAN_IN"
},
"local": {
"name": "LAN_LOCAL"
},
"out": {
"name": "LAN_OUT"
}
},
"speed": "auto"
},
"eth3": {
"description": "eth3 - ExperiaBox",
"duplex": "auto",
"speed": "auto",
"vif": {
"7": {
"bridge-group": {
"bridge": "br0"
},
"description": "eth3.7 - ExperiaBox VOIP",
"mtu": "1500"
}
}
}
},
"loopback": {
"lo": "''"
}
},
"protocols": {
"igmp-proxy": {
"disable-quickleave": "''",
"interface": {
"eth2": {
"role": "disabled",
"threshold": "1"
},
"eth2.4": {
"alt-subnet": [
"0.0.0.0/0"
],
"role": "upstream",
"threshold": "1"
},
"eth0": {
"role": "disabled",
"threshold": "1"
},
"eth0.4": {
"alt-subnet": [
"0.0.0.0/0"
],
"role": "downstream",
"threshold": "1"
},
"pppoe2": {
"role": "disabled",
"threshold": "1"
}
}
},
"static": {
"interface-route": {
"0.0.0.0/0": {
"next-hop-interface": {
"pppoe2": {
"distance": "1"
}
}
}
},
"route": {
"213.75.112.0/21": {
"next-hop": {
"10.213.96.1": "''"
}
}
}
}
},
"port-forward": {
"auto-firewall": "enable",
"hairpin-nat": "enable",
"lan-interface": [
"eth0"
],
"wan-interface": "pppoe2"
},
"system": {
"task-scheduler": {
"task": {
"iptv": {
"executable": {
"path": "/config/scripts/post-config.d/update_iptv_route.sh"
},
"interval": "15m"
}
}
}
},
"service": {
"nat": {
"rule": {
"5000": {
"description": "MASQ corporate_network to IPTV network",
"destination": {
"address": "213.75.112.0/21"
},
"log": "disable",
"outbound-interface": "eth2.4",
"protocol": "all",
"type": "masquerade"
},
"5001": {
"description": "MASQ corporate_network to IPTV network",
"destination": {
"address": "10.16.0.0/16"
},
"log": "disable",
"outbound-interface": "eth2.4",
"protocol": "all",
"type": "masquerade"
},
"6001": {
"description": "MASQ corporate_network to WAN",
"log": "disable",
"outbound-interface": "pppoe2",
"protocol": "all",
"source": {
"group": {
"network-group": "corporate_network"
}
},
"type": "masquerade"
},
"6002": {
"description": "MASQ remote_user_vpn_network to WAN",
"log": "disable",
"outbound-interface": "pppoe2",
"protocol": "all",
"source": {
"group": {
"network-group": "remote_user_vpn_network"
}
},
"type": "masquerade"
},
"6003": {
"description": "MASQ guest_network to WAN",
"log": "disable",
"outbound-interface": "pppoe2",
"protocol": "all",
"source": {
"group": {
"network-group": "guest_network"
}
},
"type": "masquerade"
}
}
}
}
}
tensink commented
Same issue here.
Veldkornet commented
I think I’ve found the problem. It seems as though the route script is not running...
I ran the script manually and now all is working fine. Any ideas?