I using the 1900acs , in the newest build 5-29 I can mount my drive but I can't access it under file sharing, same settings on the 3/25 build I can. not sure what the problem is. thanks.
I using the 1900acs , in the newest build 5-29 I can mount my drive but I can't access it under file sharing, same settings on the 3/25 build I can. not sure what the problem is. thanks.
I using the 1900acs , in the newest build 5-29 I can mount my drive but I can't access it under file sharing, same settings on the 3/25 build I can. not sure what the problem is. thanks.
Working here as well with user accounts & ntfs filesystem
I using the 1900acs , in the newest build 5-29 I can mount my drive but I can't access it under file sharing, same settings on the 3/25 build I can. not sure what the problem is. thanks.
I using the 1900acs , in the newest build 5-29 I can mount my drive but I can't access it under file sharing, same settings on the 3/25 build I can. not sure what the problem is. thanks.
I noticed the same issue. I have a USB hard drive and a usb flash drive plugged in. Both worked fine until an upgrade to the latest Kong build. After the update, the mounted drives were all messed up. I unplugged both and reboot. I plugged the hard drive back in, it now works. Had to reset the file sharing section. I have not re-plugged the flash drive yet.
I can't seem to get QOS to prioritize traffic by interface. I am trying to limit the overall bandwidth usage on ath1 (on WAN), but no matter what settings I choose, ath1 can still use max bandwidth of the WAN. Anyone else seeing this issue?
EDIT: Nevermind - it suddenly started working after a reboot of the router. All appears to be working well.
There are some more commits, one which may look like it delivers a performance boost.
I can built myself, but my builds don't include Kong secret sauce, and performance is more aligned to standard builds. Keen to see if the latest code drop adds anything useful
If anyone has a couple of WRT1900xxx to test, as mine are going to be in use for the next few days. _________________ Tutorial for flashing WRT series WRT Installation,Upgrade & Basic Setup–Cliff Notes
r52242: WRT3200ACM, WRT1200ACv1 & 1 Velop in bridge mode(IoT subnet), r52242 WRT1900ACv1 AP
Velop:2 WHW0101, RE6500, RE9000(AP)
Spectrum - 1000/50
SysLog Watcher 5, New security Onion box coming soon, Fingboxes, PiHoles, NEMS, Cacti, rpisurv
Posted: Sat Jun 04, 2016 19:02 Post subject: New Kong build....
DD-WRT v3.0-r29825M kongmv (06/04/16)
root@DD-WRT:~# uname -a
Linux DD-WRT 3.18.33 #40 SMP Sat May 21 20:24:26 CEST 2016 armv7l DD-WRT
root@DD-WRT:~# strings /lib/ath9k/mwlwifi.ko | grep 10.3
10.3.0.17-20160603
The changes have been good, useful ones, finally. The main change that concerns me the most is getting rid of the network latencies of a couple of my mobile (wireless) clients. And then getting rid of the log messages that were generated as a result of the latency fixes.
The wireless driver isn't too bad, finally, after 2 years...
The changes have been good, useful ones, finally. The main change that concerns me the most is getting rid of the network latencies of a couple of my mobile (wireless) clients. And then getting rid of the log messages that were generated as a result of the latency fixes.
The wireless driver isn't too bad, finally, after 2 years...
Wow like you said. 2 years and all of a sudden a fire seems lit under their butts.
Not much change in the wireless. The 2.4 is excellent as has been. The 5.0 range is almost non-existent. Tried playing with the settings. The best I can get is with WideHT, Channel 153(5765)MHz.
Wonder what the changes are?