Run: At a ssh prompt.
Code:opkg update opkg install tcpdump
yea my issues the exact opposite, what was your solution, my temperatures are never this low.
i usually rock it in the high 80's low 90's any advice, what was you solution for dealing with high temps, maybe i need to do the opposite to bring my high temps back...
yes, sorry I did not notice your disposition, I was merely wondering if something was wrong with mine , as I am use to seeing it in the high 80's and low 90's as stated.You can't be serious! Making fun of the new guy, I see. Why would anyone want their temps to run extremely high--100c or over). Seems you risk over the intermediate term (at minimum) a failure of the PCB, desoldering, errors, reboots, system instability etc etc.....
My apologies. I thought you were teasing me. Not offended. (should have left off the exclamation point) I can now see that, from your perspective, any change in "operating parameters" <--fancy phrase should beg the question why did that change, even if it changed for the better.yes, sorry I did not notice your disposition, I was merely wondering if something was wrong with mine , as I am use to seeing it in the high 80's and low 90's as stated.
Should be in the LAN 1 port.I just can't get the AC87U to work in AP mode anymore. Same thing with 384.12. After factory reset it works just fine, but when enabling AP mode it looks like WAN port won't wakeup and the router doesn't get an IP address. And neither does any device connected to access point. Is there anything you can do Merlin about this issue? 384.11.2 is the last working version.
Thank you. That helps clarify. Looks like all I need to do is add a check for the nvram variable "model" in the code. If it is an HND model, parse the hostnames from /jffs/nvram/dhcp_hostnames rather than the nvram variable dhcp_hostnames for the non-HND models.Asus has some major enhancements for some AiMesh models coming, probably sometime during Q4. That's all I can say for now.
That's coming from AiMesh nodes.
/jffs/nvram/dhcp_hostnames (it's in the same folder where Asus stores their own larger nvrams).
dhcp_staticlist now has the same format as stock firmware:
Code:<MAC>IP
As for dhcp_hostnames:
Code:<MAC>Hostname
It's exactly the same format as the dhcp_hostname nvram on pre-HND models, just that it gets read/written through jffs_nvram_get() and jffs_nvram_set() for HND models. Unfortunately the userspace nvram tool cannot automatically handle it, since the list of large nvrams is hardcoded by Asus, so I cannot make my own additions to it.
downloaded and installed the latest firmware 384.13. While going through all the settings, I see in <Tools > Sysinfo> that my CPU temperature had bumped up over 30 degrees C.
One CPU temp reads 61C, the other 101C. Both used to read in the 70's when NOT being actively cooled. I doubt the two are really running with a 40 degree C temperature difference while sitting side by side.
After investigating all my processes are running correctly with no issues, so I am under the impression something must have been broken that got fixed with the update----(I use to have to have mine on a cooler like yours). I hope your issue gets resolved though. keep us updated if you come up with "internal" solutions.My apologies. I thought you were teasing me. Not offended. (should have left off the exclamation point) I can now see that, from your perspective, any change in "operating parameters" <--fancy phrase should beg the question why did that change, even if it changed for the better.
If the changelog should indicate that this was an expected improvement then great, but if it didn't, why did it change/improve?
BTW you asked what was my solution. I don't have one. Both my routers are sitting on a small desktop HEPA air cleaner with fairly high (clean) airflow. One CPU temp reads 61C, the other 101C. Both used to read in the 70's when NOT being actively cooled. I doubt the two are really running with a 40 degree C temperature difference while sitting side by side. If you really want to raise the operating temperature, maybe put it on heater? :O
They may be trying to fix no boot issue after soft reboot on some RT-AC86U and RT-AX88U. Let's see...
When I go the the DDNS page (under WAN) I get a pop up stating "Invalid Character". I have entered my email address for No-IP.org with the corresponding password. The username is changed to the username of the router.
Thank you. That helps clarify. Looks like all I need to do is add a check for the nvram variable "model" in the code. If it is an HND model, parse the hostnames from /jffs/nvram/dhcp_hostnames rather than the nvram variable dhcp_hostnames for the non-HND models.
Edit: 86U running at 73 deg. Can I check the mesh node temp? I can't log into it as a mesh (at least it's not letting me).
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!