Nothing!!! Still unable to use ethernet backhaul!!!!
someone can help me?
View attachment 27651View attachment 27652View attachment 27653View attachment 27654
Same for me with my two RT-AC88U. Ethernet backhaul is not working with all possible options.
Just installed latest beta in AX88U today 11/14/2020. Unfortunately, it knocked my Brother MFC l2750DW offline. It is connected to the network, but neither pc nor airprint clients can see it anymore. Anyone have any ideas? It is showing as connected in the GUI. Everything else is working fine, from PCs to Idevices, to IOT devices. Just the printer...that I really need
Nothing!!! Still unable to use ethernet backhaul!!!!
someone can help me?
View attachment 27651View attachment 27652View attachment 27653View attachment 27654
Yes but is only for a test, is not his usual place...Is that a router sitting on a subwoofer magnet?
OE
Nothing!!! Still unable to use ethernet backhaul!!!!
someone can help me?
View attachment 27651View attachment 27652View attachment 27653View attachment 27654
However he has an AC88U, not an 86U. I am 1000% convinced there is a bug specific to the AC88U in the 386 beta firmware. If you scroll through the archives there's 3-4-5 of us, myself included, that have been screaming they can't get the system working with the 88U for some time. To my knowledge not one beta tester has said they have a working system when an 88U is involved. Initially I was just "oh well, I'll wait until the next build comes out", but now I'm getting more cynical that ASUS is even testing that model.Hopefully Ethernet backhaul is now recognized. It worked for me on an AC68U that I recently upgraded to the newest firmware, where I also got stuck in WiFi backhaul.
However he has an AC88U, not an 86U. I am 1000% convinced there is a bug specific to the AC88U in the 386 beta firmware. If you scroll through the archives there's 3-4-5 of us, myself included, that have been screaming they can't get the system working with the 88U for some time. To my knowledge not one beta tester has said they have a working system when an 88U is involved. Initially I was just "oh well, I'll wait until the next build comes out", but now I'm getting more cynical that ASUS is even testing that model.
Tested both RC7 and RC8 on a RT-AC5300 (on Verizon FIOS network). Got WAN IP address and internet connection, but the connection only maintained for a short period of time (like a minute). The network map showed Internet Status: Disconnected.
Tried:
- removed RT-AC68U node;- set DHCP query frequency to Normal and Continuous mode;- restored to factory default without custom setting changes (except SSIDs and WPA2).No stable internet connection.
Restored to 384_82072, got stable internet connection.
These beta's are not applying DST correction properly.
I can confirm this behaviour - I’m also in GMT +10 Canberra, Melbourne, Sydney.
I have xt8 and was getting kernel stack traces in RC2-7 - stopped happening in rc2-8I'm currently on RC2-7, and for me it has been very solid. No random reboots at all, which was my biggest aggravation with the stock fw on my three XT8's. Now, I every so often experience some slowdowns. It feels as if datatransfer suddenly halts for some time and starts up again. I started looking at the systemlogs (again), and see this recurring:
Nov 14 07:18:47 kernel: CPU: 1 PID: 4378 Comm: dcd Tainted: P O 4.1.52 #2
Nov 14 07:18:47 kernel: Hardware name: Generic DT based system
Nov 14 07:18:47 kernel: [<c0026e60>] (unwind_backtrace) from [<c0022c38>] (show_stack+0x10/0x14)
Nov 14 07:18:47 kernel: [<c0022c38>] (show_stack) from [<c04b9f5c>] (dump_stack+0x8c/0xa0)
Nov 14 07:18:47 kernel: [<c04b9f5c>] (dump_stack) from [<c003aaec>] (get_signal+0x490/0x558)
Nov 14 07:18:47 kernel: [<c003aaec>] (get_signal) from [<c00221d0>] (do_signal+0xc8/0x3ac)
Nov 14 07:18:47 kernel: [<c00221d0>] (do_signal) from [<c0022658>] (do_work_pending+0x94/0xa4)
Nov 14 07:18:47 kernel: [<c0022658>] (do_work_pending) from [<c001f4cc>] (work_pending+0xc/0x20)
Nov 14 07:26:44 kernel: CPU: 1 PID: 11763 Comm: dcd Tainted: P O 4.1.52 #2
Nov 14 07:26:44 kernel: Hardware name: Generic DT based system
Nov 14 07:26:44 kernel: task: d5516400 ti: ce1c8000 task.ti: ce1c8000
Nov 14 07:26:44 kernel: PC is at 0xb6c7e39c
Nov 14 07:26:44 kernel: LR is at 0x1dd14
Nov 14 07:26:44 kernel: pc : [<b6c7e39c>] lr : [<0001dd14>] psr: 600f0010
Nov 14 07:26:44 kernel: sp : bee7d9e8 ip : 000a2050 fp : b5fff024
Nov 14 07:26:44 kernel: r10: 000a23c4 r9 : b5fffca8 r8 : 000a287c
Nov 14 07:26:44 kernel: r7 : b5fffce0 r6 : 000a2876 r5 : 00000000 r4 : b5fffc8c
Nov 14 07:26:44 kernel: r3 : 00000000 r2 : 00000000 r1 : 0007d612 r0 : 00000000
This was the kind of logs that was present during the time of random reboots. I have this sneaking suspicion that they (Asus) have somehow patched the FW to not trigger a reboot when this occurs, rather than fix the underlying problem. Maybe i'm paranoid - or just have three faulty XT8's
Checked again today and still no RC8 firmware for the RT-AC86U, what's going on?
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!