Yes, I've never quite figured out why sometimes a code load just reboots and others it pops the message to manually reboot (i.e power cycle). But I've noticed enough strange things when it just reboots that I now always power cycle after a code load.
just update to fork v4 on ac56u and i was able to change wireless power to -26,5 db . wow.
root# wl txpwr_target_max
Maximum Tx Power Target (chanspec:0x1001): 26.50 26.50
How about just updating the usb share driver (NTFS) plz
Can these commands be just copied/pasted "as is" via Putty? No reboot command required? If so, what options should then be present in the Tx setting in the GUI options? I'd love to boost my signal a bit but still learning to navigate the AC68U.just update to fork v4 on ac56u and i was able to change wireless power to -26,5 db . wow.
root# wl txpwr_target_max
Maximum Tx Power Target (chanspec:0x1001): 26.50 26.50
This comes up every so often....
As a regular user, I don't have the ability to edit the thread title. In addition, if the thread title were edited, it would break anyone who created a subscription to the thread.
Can these commands be just copied/pasted "as is" via Putty? No reboot command required? If so, what options should then be present in the Tx setting in the GUI options? I'd love to boost my signal a bit but still learning to navigate the AC68U.
Any chance that you can add a facility to restrict dropbear from listening on all interfaces?
TIA
Sent from my Samsung S3 (GT-i9300) on Sammy JB 4.3 (NB6) powered by Boeffla kernel via Tapatalk
It looks like the standard dropbear doesn't have that capability.....but it may be possible be address, like the gui access. Would that give you what you need?
Edit: Or new thought....bet it could be done with iptables.
Yes, that is what I was looking at.....and if it was possible to add to the gui
I have not changed the default CFE on my T-Mobile TM-AC1900, but have updated the firmware to version 4 of FW 374.43 successfully giving me the ability to up output power on both the 2.4GHz and 5.0GHz bands, as verified by inSSIDer.
However, when change channel selection from "Auto" to 64, 104, 108, etc., I cannot get my clients to hold a connection. I've tried this on my iPad, iPhone, and Win7 laptop, and all are immediately disconnected.
Any suggestions?
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!