In the previous version (380.57), I was having trouble achieving anything close to maximum throughput on downloads on my gigabit fiber connection. I would get about 350Mbps down and 850Mbps up. After updating to 380.58, I'm getting about 900Mbps in both directions. I presume there was some sort of problem with cut-through forwarding or flow acceleration that has now been fixed. But the Changelog only mentions CTF fixes in the context of the VPN, which I've never used. So in case anybody else has been having this same throughput issue, I thought you might want to know that there appears to be a fix in this release.
I have the same issue on an RT-AC68P. The manufactures coming back are mostly wrong or just garbage text. I have three iPads and only one reports as Apple. It thinks my security cameras are HP Printers.Works for me. What router model?
N66 here, works. I have a N10+ as a bridge that appears in the map twice, once correctly identified as Asus, the other showing loading manufacturer data. But all the others showing up fine.RT-AC66U
I did a factory reset after flashing the update. It only shows the mac adress, device list shows 'loading manufacturer data' only.
I will check again in a few hours after work. Maybe the lookup service was down or smthg.
I'm also watching for feedback on the N66 users out there as I'm going to flash my sisters router this weekend with the most stable version available.
Thanks Kal, she lives up in Barrie so I want to set and forget. I can remote into any PC but flashing and clearing NVRAM is a different matter.The N66 works MUCH better with John's fork then any of these new releases hands down. Just saying flash what you will..
In the previous version (380.57), I was having trouble achieving anything close to maximum throughput on downloads on my gigabit fiber connection. I would get about 350Mbps down and 850Mbps up. After updating to 380.58, I'm getting about 900Mbps in both directions. I presume there was some sort of problem with cut-through forwarding or flow acceleration that has now been fixed. But the Changelog only mentions CTF fixes in the context of the VPN, which I've never used. So in case anybody else has been having this same throughput issue, I thought you might want to know that there appears to be a fix in this release.
192.168.1.1:8443 uses an invalid security certificate. The certificate is not trusted because it is self-signed. Error code: SEC_ERROR_UNKNOWN_ISSUER
I don't believe that I got that error from 380.57, at least Firefox doesn't have a record of my adding an exception was overwritten when I added the 380.58 exception.
There is no VLAN ID under IPTV when choosing "manual setting". The only way you can set VLAN ID is to use the internet connection wizard and choose "special requirements from isp". Can this be fixed?
There was VLAN ID on 380.57. In my case I need it to access the internet. Although the internet works, I would prefer to see this setting there.
I didn't know you could login by router name, I've only used the IP address all these years. I'll screenshot the next time it happens.Using router name to acces? tr
If using router name to access, try by ip 192.168.1.1
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!