Im having this annoying issue right now with AC86U. What is the feasible workaround?

So yesterday i configured for auto reboot scheduler, which will run at 5am everyday. This morning i noticed the router unable to boot up, all led were off. Luckily after i reconnect the power adapter the router able to boot up successfully.

i only managed to reduce to 70-71, from over 90ish
fan direction - blow in

try again some other times, maybe due to server overloaded.

Have you selected the correct ISP? Go to LAN-IPTV and select unifi-home if you're using unifi. With this setting, LAN4 will be used for IPTV.

This post has been edited by neuromancerx: Jan 2 2019, 11:07 PM

Anyone tested?

This post has been edited by neuromancerx: Jan 9 2019, 09:35 PM

Less heat? My AC86U recorded 91 degree, and after installed additional fan managed to hover around 71 degree.

Well known issue, search for "hypptv" or "iptv" keywords in this thread.

Here

Make sure R/W access is enabled on the shared folder

This post has been edited by neuromancerx: Feb 10 2019, 01:52 AM


Attached thumbnail(s)

today, after rebooting the router it refuse to boot up. no led at all. have to manually reconnect the power plug. haihz, frustrated la

you can block it based on dns. if you have installed diversion (dns ad blocker), you can easily add netflix.com in the blocklist. you can also try modify the router's /etc/hosts and point netflix.com to any blackhole address.

i fully agreed with all the negative feedback above. HW spec wise it's very good, plenty of RAM and good CPU horse power.

Experienced these issues:
1. IGMP proxy disabled, causing hypptv to disconnect once the router changed WAN ip or rebooted.
2. Sometime the router did not survive reboot. It just stucked at power on mode, have to manually cut the power and reconnect it. Whenever i rebooted the router remotely or reboot after apply new firmware, i just crossed my finger.
3. Poor heat dissipation.

Will not recommend.

is snmp removed from the latest asuswrt merlin? couldn't find the snmp option

Personally I'm ok with TP-Link, most of their routers are supported by Openwrt. I'm still keeping few TP-Link routers for spare and labbing/research.

Replaced with WS880 and then currently using AC-86U. Reason is because 512MB RAM and asuswrt.

In the event this 86U died, i will use back my WS880. All my asuswrt were installed with optware-ng, so only in the event the features or software i that needed not ported in optware-ng, i will use tplink with openwrt.

make sure your next router is supporting wifi-6.

that little dinosaur is easier to handle compared to this 86U, i mean in term of stability and robustness. the only drawback is we will stuck with older firmware.

no. but let's wait for apple device support for it, other will follow. personally, i'm still okay with my current setup (AC86U). I know exactly my requirement and limitation that i can live with.

384.14 (14-Dec-2019)
- NEW: Implement option to prevent Firefox's automatic usage of DoH.
By default, this will only apply if you have DNSPrivacy
enabled, or if you have DNSFilter enabled with a global
filter, to ensure that Firefox will not bypass either of
these. You can also have this override applied all the
time, or completely disable it.
- NEW: Added "split" busybox applet.
- NEW: Added IPv6 support to Network Analysis webui
- NOTE: You might need to reconfigure your device hostname on the
LAN -> LAN IP page due to a GPL-level change (exclusing
the RT-AX88U)
- UPDATED: RT-AX88U to GPL 384_6436 (with Let's Encrypt fixes
backported from 384_81351)
- UPDATED: RT-AC68U, RT-AC86U to GPL 384_81351
- UPDATED: RT-AC88U, RT-AC3100 to GPL 384_81351 and binary
blobs from 384_81116
- UPDATED: RT-AC5300 to GPL 384_81351 and binary blobs from
384_81219.

- UPDATED: miniupnpd 20190824
- UPDATED: dnsmasq 2.80-95-g1aef66b (themiron)
- UPDATED: OpenSSL 1.0.2 to 1.0.2t (themiron)
- UPDATED: OpenSSL 1.1.1 to 1.1.1d (themiron)
- UPDATED: Curl 7.66.0
- UPDATED: nano 4.4
- UPDATED: OpenVPN 2.4.8
- UPDATED: OUI database to 2018-08-17 version
- UPDATED: CA root certificates to October 9th 2019
- CHANGED: Made webui SSL certificate generation compliant with
IOS 13 and MacOS 10.15 new requirements.
- CHANGED: Rewrote the faketc script used to inject Codel into
Adaptive QoS as a C program for improved performance.
- CHANGED: Moved /usr/bin/ip to /usr/sbin/ip on the RT-AC86U and
RT-AX88U to match other models.
- CHANGED: IPv6 firewall now accepts empty values for local IP
(which means any local IP).
- FIXED: Webui wouldn't notify when running dangerously low on
free nvram (feature was lost at some point in the past)
- FIXED: Non-working link to YandexDNS on the webui for
Russian models.
- FIXED: Backported various httpd fixes to RT-AX88 from other
models.
- FIXED: Custom clientlist would be wiped if stopping an
OpenVPN server instance.
- FIXED: Incorrect detection of EUI64 addresses on the IPv6
firewall (would prevent using ::/0 for instance).
- FIXED: EUI64 support missing while in Load Balancing or
using Multicast IPTV.
- FIXED: Asus DDNS failing to update due to an invalid
certificate on Asus's server.
- FIXED: Let's Encrypt support would sometime fail when using
Asus DDNS (fixed DNS publishing of validation record)
(in addition to general failure fixed by GPL 81351)
- FIXED: IPv6 neighbour solicitation drop toggle not working
for some models
- FIXED: openvpn-event scripts would be executed even if custom
scripts were globally disabled

This is a well known drawback from wireless mesh. The bandwidth will be reduced half for every hop count.
As for the powerline, the only bottleneck will be the bandwidth available/supported between the homeplug.
Extending the wireless coverage using traditional copper cable or homeplug is more preferred than relying on wireless mesh.

Readings:
https://commotionwireless.net/docs/cck/netw...lines-for-mesh/
https://www.smallnetbuilder.com/wireless/wi...e-wireless-mesh