Make sure you disable beamforming, as this relies on antenna diversity to do its job.
it runs but when exit and reload with amtm you get a jffs/scripts/amtm not foundcurl -Os https://diversion.ch/amtm/amtm && sh amtm
Log out and back in from your ssh terminal. I cannot make the current session to forget the old alias.did a dirty flash fr9m alpha1
only with amtm it says not found but when executing this
it runs but when exit and reload with amtm you get a jffs/scripts/amtm not found
I just fixed it with the profile.add alias removed and then unalias amtm in ssh. It works now.Log out and back in from your ssh terminal. I cannot make the current session to forget the old alias.
Yes, I was told in the amtm thread. No issues to report with all the new packages. Just make sure you have the new pixelserv -tls certificates from 2.3.0 or newer active.upgraded from alpha2 to beta1. no issues.
amtm is showing a lot of entware packages updates. should i update them?
thanks
hugo
Log out and back in from your ssh terminal. I cannot make the current session to forget the old alias.
Did you just update all the Entware packages with the big release today? You need to go into Diversion, ep, and purge certs, then restart pixelserv-tls new version. That causes failure with old certs.Does anyone know what this entry in my log means, and if there's a fix needed?
Feb 1 20:07:39 pixelserv-tls[911]: generate_cert: failed to open file for write: /opt/var/cache/pixelserv/_.go-mpulse.net
Anton
Thank you!Did you just update all the Entware packages with the big release today? You need to go into Diversion, ep, and purge certs, then restart pixelserv-tls new version. That causes failure with old certs.
I just fixed this by removing the /jffs/addons/amtm and rerunning amtm.
All is well now.
For those seeing errors in amtm after upgrading 384.15 firmware from alpha to beta, please run uu in amtm to get the updated amtm files.
amtm has a built in reset function r which resets the built-in version, while in the standard amtm it removes amtm.
AC86U upgraded from 384.15_alpha2. I tried uu and r in amtm, logged out and I was still getting errors.Log out and back in from your ssh terminal. I cannot make the current session to forget the old alias.
@AntonK Thanks for that link. I had not come across it.Upgraded to Beta1, and all is working perfectly. Used this gem of a guide for the process: Rebootin Router with USB
Thanks RMerlin & L&LD!
Anton
I am having trouble updating from alpha 2 to beta 1 on my rt ac 5300, I have unmounted drive and turned off jffs and still will not flash from alpha 2 to beta 1384.15 beta 1 running well on my plain jane AC 5300 , smooth upgrade as usual
@kernol I don't think amtm + scripts + Entware can be run off of an AiMesh node? Did this work before in Alpha 2?
Worked a treat in Alpha2 with amtm FW version - but clearly few scripts except scMerlin would be useful.
I had never thought of deploying amtm to an Aimesh node before - but given that it was now part of the 384.15 firmware - decided to give it a whirl - and it worked fine in Alpah2 - but broke in Beta1.
I'm not at the level of L&LD, however, I have seen some posts that can minimize the difficulties some have, and some I feel are reckless, they work, but I cringe. Here is my method, some taken from L&LD and others. plus the times I had issues and had to troubleshoot and solve.Since I'm a beginner with using scripts and USB drives I was wondering how exactly I'd go about updating firmware.
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!