Recent content by rromeroa

Thank you but no fixed the issue to me. It seems similar as in the past but not the same. Trying to starting service I obtain the error: symbol lookup error: /opt/lib/libdht.so: undefined symbol: dht_random_bytes

great and simple solution to solve it. thanks

Sorry again @RMerlin, spanish users of your firmware suspects this fix has broken the iptv movistar profile in ac68u, ac88.... seems to be correct only on ac86 and ac88 (even though udpxy is bad parametrized) maybe, you should undo the fix until asus fixed. thanks

Sorry @RMerlin , now with 384.11 final release (AC86u), udpxy is starting at boot time but the spicified multicast interface is wrong. I don't know if it's closed source or not. in iptv movistar profile, the correct video vlan interface must be vlan2 instead vlan6 (data interface) thanks...

udpxy works fine when starts manually. Movistar iptv profile is new in AC86U, recently added in the 384_45713... I think they have simply forgotten. Thanks

Thanks @RMerlin, this is the output commands: # nvram get udpxy_enable_x 4022 # nvram get switch_stb_x 8 # nvram get iptv_ifname eth0.v1

Hi, in this release, udpxy is not starting at boot time in my AC86U. I have Movistar IPTV profile with udpxy at 4022 port but udpxy daemon is not starting.

yes, port 4022.

In this beta, in my AC86u, udpxy is not autostarting. I have Movistar iptv profile but I had to add udpxy call at services-start script.

Movistar's IPTV service is working now in my AC68U. Thank you very much for the quickly resolution.

Hi Merlin, RT-AC68U here. I would be happy to test it.. thanks

this workaround does not work.:(

Movistar working well at 384.9, but when I stopped the quagga service, then I have same issues as 384.10

I have only detected issues with iptv, other services works correctly (internet and openvpn client/server). My router is an AC68U.

Same issue here... and same solution (back to 384.9_0) :(