First, thank all developers for so great work. LEDE is definitely the best firmware I've ever installed on my Netgear WNDR3800 router with flexibility and reliability balanced, though the documentation of guides still need a catch up to OpenWRT.
By FTTH, I have both Internet and IPTV connections via an ONU (Optical Network Unit). With the hardware switch RTL8366S in the router and VLAN binding, I successfully made the change - moving the STB (Set-Top-Box) from LAN port of ONU to the router. It works fine.
The next step, when I try to watch TV from my Windows desktop and Android smart phones with igmpproxy and udpxy packages installed, following the How-to "IPTV / UDP multicast", the problem happens that the "IPTV" interface in DHCP client Protocol could not pass the authentication to get a valid intranet address. Even I manually set the static address Protocol with IP, gateway, DNS, etc. acquired by the STB, the connection will be offline always.
Through packet capturing during STB booting up, I can see DHCP discover/offer/request/ack showing
Option 61 = STB MAC address
Option 12 = STB SN
Option 60, maybe IPTV user name and password.
Following some hints got from searching on Internet, I edited following 2 config files (not accurate info), but nothing changed - only “udhcp 1.25.1” could be found in DHCP discover.
config dhcp 'iptv'
option networkid 'iptv'
list dhcp_option '60,00:00:01:06:35:75:61:71:69:6E:02:0A:48:47:55:34:32:31:4E:20:76:33:03:0A:48:47:55:34:32:31:4E:20:76:33:04:10:32:30:30:2E:55:59:59:2E:30:2E:41:2E:30:2E:53:48:05:04:00:01:00:50'
option fore '1'
If I paste anyway the Hex codes into the LuCI input box throught a web browser, it will turn to plain text not the binary format anymore.
In LEDE documentation, I found the definition and statement as below:
String sent by the client representing the vendor of the client. dnsmasq performs a substring match on the vendor class string using this value."
"These parameters are handled partially by netifd (in interface.c) and partially by a shell script in lib/netifd/proto/dhcp.sh."
Does that mean this moment, LEDE can only handle DHCP Option:vendorclass in ASCII characters?
Hope someone could give me a firm answer and suggest some other way around.
Thanks in advance.