sentinelvdx
Very Senior Member
Sadly I had to reboot the router, but happened a couple of times before. I'll pay attention to next time it happens to run the cmd and post it here. thanks!Run "top" to determine what is using the CPU.
Sadly I had to reboot the router, but happened a couple of times before. I'll pay attention to next time it happens to run the cmd and post it here. thanks!Run "top" to determine what is using the CPU.
hmmm... odd that the ax86 didn't do a sanity check on the image and stop the upload... but there has to be a way to 'fool' the router into taking a firmware upload...Sadly no. No power light no rescue mode.
Firmware images do get validated when being flashed. Both the actual model as well as a CRC32 integrity check to ensure the image isn't corrupted. Anyone who managed to flash an AX86U firmware on an AC86U must have done something really unusual to flash it, like using TFTP...hmmm... odd that the ax86 didn't do a sanity check on the image and stop the upload... but there has to be a way to 'fool' the router into taking a firmware upload...
If you plan to drive with your car on some muddy road (firmware upgrade): Do you wash the car before or after your ride?Just to double-check, if I'm coming from 384_19_0 on my RT-AX88U, I flash 386.1 Beta 5 ... then do a Factory Reset?
of course they get validated - I agree, it doesn't make sense... chcksum and mod#... how the heck did that happen??... in a private message, if you have any cli suggestions for him you'd rather not post up here 'in-the-wild' if he goes ttl serial, it might help him out of brickland... I got nuthin' even if I was sitting at a ttl serial prompt other than forcing a tftp that bypasses the nic hardware...Firmware images do get validated when being flashed. Both the actual model as well as a CRC32 integrity check to ensure the image isn't corrupted. Anyone who managed to flash an AX86U firmware on an AC86U must have done something really unusual to flash it, like using TFTP...
of course they get validated - I agree, it doesn't make sense... chcksum and mod#... how the heck did that happen??... in a private message, if you have any cli suggestions for him you'd rather not post up here 'in-the-wild' if he goes ttl serial, it might help him out of brickland... I got nuthin' even if I was sitting at a ttl serial prompt other than forcing a tftp that bypasses the nic hardware...
hmm - no way to revive the cfe btldr? - ok - I know that's in the weeds - sorry... and before the re-read I thought he'd bricked a new ax86 - not an old ac86 with high-time on it... oops on my part - had it backwards... but still ; ) ...TFTP in recovery mode is the only way to do it. If it fails to enter recovery mode, then it means either he has broken hardware, or somehow he overwrote his bootloader in which case there is nothing he can do.
A throughput around the half of the link speed is also my experience - but already with past firmware and actual ones the same...Fast AC clients that connect at solid 866Mbps, are maxing out at 350.
With 2.4Ghz and 300Mbps connection, it maxes out at 150-180 (tested on 2 fast ThinkPads).
For what it is worth, I have figured out what the problem was. I had a bad Intel AC7260 Client in the PC, When I swapped out the client mini PCIe no more disconnects.Posting this to find out if anyone else is having the same issue with 386.1 releases that I am.
This has been / still is happening with all Merlin 386.1 alpha's & beta's. I have one client, a W10 PC with an Intel AC7260 wireless adapter, that constantly looses it's 5Ghz wireless connection. It takes a while for the drop to happen after initial PC boot up but after that drops gets closer and closer together. No other clients on RT-AC86U or AIMesh node RC-AC68U drop.
This client is very close to the 86U, 6ft. Once dropped I have to reset the client in the PC via running network diagnostics or manually disable / enable wireless client. I have forgotten wireless network connection several times within PC. I have tried disabling both beamforming's in router, it does not make a difference. This client has always been rock solid prior to this release. I believe there was a new driver version for the 86U that came out with the 386.1 release. I've been hoping that newer releases will fix.
I did do a factory reset after flashing to 386.1 alpha as instructed. The drops have gotten so bad I am now using an Ethernet connection. I read the forum often enough to know no that is not an issue that is being encountered by many.
Any help / suggestions will be appreciated.
A throughput around the half of the link speed is also my experience - but already with past firmware and actual ones the same...
So, it does not seem to be an issue in the current beta version, right?
Does that allow you to limit reservations to a specific interface, or are you forcing that client to be assigned that IP no matter what interface they're connected to?
I currently have no plans to merge any newer GPL for 386.1. 41700 is good enough to be used for a formal release.@RMerlin, a few official firmwares higher than 41700 have been released. Do you know what changes these have, and are you considering incorporating the next unified GPL release? I know this can be a never-ending game, but still want to ask since this has been such a long beta period.
I'm reading this like it'll be a "this weekend" thing...I currently have no plans to merge any newer GPL for 386.1. 41700 is good enough to be used for a formal release.
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!