Posted: Fri Mar 06, 2015 5:42 Post subject: Re: Add Wifi LED
dechronic wrote:
...
This now reduces the script overhead. There is still a little overhead, like ~6% to ~10% increase.
Hi
Thanks for the fix and now the cpu usage is down.
Firmware:K2.6 03-05-15 mega 26446.
EDIT(2015/03/08):
It seems that K3X version is unstable for RT-N12 D1, my router just rebooted unexpectedly so I will give it up for now and back to K26 version.
Posted: Mon Mar 09, 2015 13:22 Post subject: Re: Add Wifi LED
BurtJ wrote:
EDIT(2015/03/0:
It seems that K3X version is unstable for RT-N12 D1, my router just rebooted unexpectedly so I will give it up for now and back to K26 version.
I can confirm that as well. When you told me about how you were trying it, I tried K3X version as well and it boots the first time but as I was configuring it and made my changes on the Wireless page and saved it then the router went into some sort of reboot loop and wouldn't boot up. I had to use the CFE firmware upload to upload and use the K2.6 firmware again.
I had happily configured my own custom DDNS script to sync with my domain, OpenVPN and one to turn on the WI-Fi light.
However, the only thing which caused me trouble after about a week of running it was that a power shortage made it start - and it started and turned on the Wi-Fi light except that it wouldn't open up 192.168.1.1 and neither turn on the Wi-FI network.
I know it starts due to the light script that is supposed to run at start-up but it appears that its stuck there. When I do a regular shutdown through the back button and turn it back on I can also get this issue.
Furthermore it works to just hold the WPS and then it would reboot and show up with the regular DD-WRT Wi-Fi, except that this would wipe all my configuration such as the publickey, encryption, wi-fi name and so on and so forth.
Anyone else who have experienced something similar to me? / may it be related to what I'm running on it? It was k26 dd-wrt.v24-26424_NEWD-2_K2.6_mega for information.
It might be that only the reboot function (which I was using for the most part) is safe and turning off the device is now. But I strongly believe that it might be some settings involved I change involved.
Posted: Sat Mar 21, 2015 7:58 Post subject: Using K3X
Hi
I finally maybe found a way to run latest K3X on RT-N12 D1. I write it here for anyone who interesting to test K3X.
If all you need is simply daily working router not for testing, do not touch this and stick at K26.
And sorry my English is not good and maybe weird.
Before we start
(EDIT:After one day testing,I got an unexpected reboot issue,dunno why.)
There are something you may want to know:
1.You must know how to unbrick the router whatever something is going wrong.
2.I will only suggest the one who interesting to test this version.If not do not touch it.
3.For the one who just need a daily working router,please stick on K2.6, it is stable so far as I know.
4.In K26,Firmware Restoration tool is enough to do installation on N12 D1 and very easy. But K3X needs special way to go, so read the guide carefully and make sure you step by step.
5.It is really a difficult time to use K3X for now, even you follow this guide I still can't guarantee it works for you.You maybe still brick the router.
6.It maybe unstable or bricked after few days,I am not sure.I just test it a few hours while this guide was written.
What's new in K3X?
0.Kernel 3.x
1.Wifi LED works.
2.Regulatory Domain options in Wireless Basic Settings.
3.No afterburner option in Wireless Advanced Settings.
4.It seems that K3X dd-wrt extends NVRAM size,by mirror it to another partition other than default 32K NVRAM.(I wonder, not sure.)
In this picture shows nvram is 32K from command line:
But it is 256K in WEB GUI(latest 26490M):
Some bad news?
1.In K3X WIFI only max 11 channels can be used while K26 WIFI has max 14 channels.
2.I did not really test this but maybe longer booting time than K26.(you need to wait till wifi led starting to flash)
Upgrade Guide
Remember step by step or you have high chance to brick the router.
You may noticed some steps ask you to reset the router in web GUI but not command or 30/30/30 and doubt that why can't simply reset the router with erase nvram. But it is the way,or you will just brick the router like me.
The main issue is base on NVRAM's size/partition for now I wonder.And even you use erase nvram, when go to K3X ,you may found that the nvram is still there while you think it is erased.And in K3X,use erase nvram will just brick the router instead of reset.
0.If possible use IE for dd-wrt web access. Other browsers may have unexpected issue on dd-wrt's web UI.
1.You must already have a K26 mega installed on your router. Any version seems ok.
It is easy to use ASUS Firmware Restoration tool to do this with this firmware if you do not flash it yet: dd-wrt.v24-26490_NEWD-2_K2.6_mini.bin
Now to go:
1.Make sure the router is reset to default settings.
But do not use "erase nvram" command.In this guide we are not using this command.
Go to K26 firmware web GUI >> Administration>>Factory Defaults ,reset the router or use WPS button to do this.
In RT-N12 D1, it seems do not need 30/30/30.
a.Power down the router >> Hold the WPS button >> power up the router while holding the WPS button for 3~5 sec.
b.Then release the button , the router will just reboot automatic.
2.Setting your admin info
Go to K26's web GUI by 192.168.1.1 and setup your admin info and password.
PS.While upgrade from K26 to latest K3X will brick the route,21605 works so 21605 first.
We need this build to do a 64K nvram reset in WEB GUI.
If you see Wifi LED is starting to flash, it should mean your upgrading is success and now we can go to 192.168.1.1 web UI.
4.21605
Check around and make sure 21605 works by 192.168.1.1.
You will now noticed that NVRAM is 64K now, it is ok.
After checked base info,go to 21605's WEB GUI >> Administration >> Factory Defaults, reset 21605 to default setting again.
Please Remember : Do not use command "erase nvram",and do not use WPS button.
5.Upgrade to 21676
After we reset 21605,now go to 21605's web GUI and upgrade to dd-wrt.v24-21676_NEWD-2_K3.x_mega.bin.
Remember to choose "Don't reset".
If you want to,skip this and go to latest K3X version,but I am not sure it works or not.
6.Finally Upgrade to latest K3X or whatever you want
This time we no need to reset, just go to 21676's web GUI and upgrade to dd-wrt.v24-26490_NEWD-2_K3.x_mega.bin Remember to choose "Don't reset".
Now all done, you can start to setup your favorite setting.But remember do not use nvrambak.bin from old version, setup from scratch.
If something is going wrong and router bricked
Use ASUS Firmware Restoration tool or follow This guide to flash router back to K26.
Remember do not try to flash to K3X with this tool ,it will brick again.Go back K26 first.
P.S About Local DNS
If you has need to use Local DNS like me,you may want to know this too.
In DHCP setting:
Some guides on internet will tell you to set static DNS1 as your router's local IP(192.168.x.x).
Do not do it, just use normal DNS is fine.
Make sure Use DNSMasq for DNS is checked.
And make sure DNSMasq's Loca DNS is on:
In K26 it works to set static DNS1 to local router IP(router self) but it seems not in K3X and will broken the connection.
For now this is all the things I have done.And this is not so call the only way, I just write down what I have found.
Hope it helps anyone who wants to try K3X on N12 D1.
EDIT:
It seems that K3X's WAN/LAN rule on RT-N12 D1 is the same as K26 so it still need to be switched by following command if needed:
nvram set vlan0ports="0 1 2 3 5*"
nvram set vlan1ports="4 5"
nvram commit
reboot
EDIT:
Anyway the router did not bricked anymore by using this way to upgrade firmware to K3X.
But after one day testing, I found that there is an unexpected reboot issue in K3X on RT-N12 D1.I don't why but just connection suddenly lost and router reboot.So I think it is not the time to go K3X yet.
But anyway, if anyone want to try K3X, this guide works.
EDIT:
K3X version after 26622(dd-wrt.v24-26622_NEWD-2_K3.x_mega.bin) is not working anymore,all bricked.
K3X 26622 is the last version that worked for this guide.
Last edited by BurtJ on Thu Apr 09, 2015 23:21; edited 1 time in total
Posted: Thu Apr 02, 2015 15:06 Post subject: Re: Add Wifi LED
dechronic wrote:
Here is a little script
Hi
I modified this WiFi LED script to fix issue 1.This script should be always working whatever only Save/or Apply the wifi settings or not.It detects status of WiFi radio on or off in real time.
Also,it only detects status of "RX bytes" because I found that whatever WiFi client/frame packages exists or not ,"TX bytes" always keeps changing on this router.
As for the LED flash rate sync issue, it seems very hard to implement by bash script.I wonder it can only be implement on hardware-driver level.
Code:
WIFI_LED=5
while sleep 1; do
WIFI=`wl radio`
if [ "$WIFI" != "0x0000" ]; then
gpio disable $WIFI_LED
else
gpio enable $WIFI_LED
wlaninterface=`nvram get wl0_ifname`
XFER=`ifconfig $wlaninterface | grep bytes`
XFER=${XFER%TX*}
if [ "$XFER" != "$PXFER" ]; then
gpio disable $WIFI_LED ; usleep 100000 ; gpio enable $WIFI_LED ; usleep 100000 ; gpio disable $WIFI_LED ; usleep 100000 ; gpio enable $WIFI_LED
PXFER=$XFER
fi
fi
done
If this script has any issue please tell me.
EDIT:
Add "gpio enable $WIFI_LED" to fix an issue that when radio is on but no RX packages WiFi LED is still off.
while sleep 1; do
WIFI=`wl radio`
if [ "$WIFI" != "0x0000" ]; then
gpio disable $WIFI_LED
else
gpio enable $WIFI_LED
wlaninterface=`nvram get wl0_ifname`
XFER=`ifconfig $wlaninterface | grep bytes`
XFER=${XFER%TX*}
if [ "$XFER" != "$PXFER" ]; then
flash
PXFER=$XFER
fi
fi
done
EDIT:
Well
After several testing,I think the script which to enable wifi LED eats too much load performance,Load average always shows 12%~20%~30% usage, while not using it only 2%~usage.
I will suggest not to use it unless you really need that.
Posted: Thu Jun 18, 2015 20:06 Post subject: Client Bridge
Hello,
I want to use the router as a client. But I don't get it working with ddwrt. I tried different firmware versions. I'm running dd-wrt.v24-26490_NEWD-2_K3.x_mega.bin now.
Hello,
I want to use the router as a client. But I don't get it working with ddwrt. I tried different firmware versions. I'm running dd-wrt.v24-26490_NEWD-2_K3.x_mega.bin now.
I want to use them in a WDS-Mesh / OLSR. But i have no luck.
I also tried different builds.
Finally i "roll-back" to the Asus-Firmware which is included in the .zip (Post by 80sguitartist, FW_RT_N12_D1_3004374813.trx, 3.0.0.4.374_813-gf2791af) where WDS works almost GOOD. Also in combination with WPA2/AES and 2 other WRT54GL with WDS (If it run´s - it run´s! After making changes, i often need to reboot everything. The "Connection-Procedure" is a bit tricky - somebody described somewhere that the order of powering is necessary. Maybe a script which turns the radio off and on if nobody is connectet, can also work?)...
The newer official Asus-Firmware(Beta) dosen´t work for me with WDS + WRT54Gl, but i did not test it enough.
Quote:
Any suggestions how to fix this issue?
Maybe it is possible, to extract the drivers and some settings from a Asus-Source [where Wlan works better], and include it into a [new] RT-N12-D1-ddwrt-build. (if there are any drivers available, and if it isn´t allready done this way)
Currently i use the Asus-FW, and I try my best with it.
[Maybe the "Client- or Repeater-Mode" works (currently) better there for U, too?]
Did somebody know a "really WDS-Ready" ddwrt-build for RT-N12?
____
I have a question about the Asus-Firmware:
I use directional antennas, and I'm not allowed to transmit with 100mW, so i need to reduce the power:
Shell:
Code:
ASUSWRT RT-N12D1_3.0.0.4 Sun Sep 22 08:16:09 UTC 2013
admin@RT-N12D1:/# nvram show | grep txp
wl_txpower=100
wl0_txpower=100
wl1_txpower=0
Can i simply edit the Nvram-option here?
Code:
admin@RT-N12D1:/# nvram set wl_txpower=10
admin@RT-N12D1:/# nvram set wl0_txpower=10
admin@RT-N12D1:/# nvram commit
After a reboot, i see that the options have changed, but I can't really measure the power on it, so i need to rely on this. Maybe someone can give me a ACK for this option! Sorry for my bad english.
tsx.
fkng.png
Description:
I often recive this f***ing Page, if i access a device, which is behind a RT-N12.
Can i simply edit the Nvram-option here?
Code:
admin@RT-N12D1:/# nvram set wl_txpower=10
admin@RT-N12D1:/# nvram set wl0_txpower=10
admin@RT-N12D1:/# nvram commit
Oh okay it worked, but i have set the wrong values! (Case sensitive!)
Did somebody else have tested a WDS-connection between two RT-N12, or with RT-N12 <--> WRT54GL? (with ddwrt on both sides??)
Posted: Wed Aug 05, 2015 14:57 Post subject: RT-N12 and Tomato works.
I got a working WDS between RT-N12 / WRT54 GL mixed..
I installed "Tomato Firmware 1.28.0000 MIPSR2-130 K26 Max" on RT-N12.
Linux kernel 2.6.22.19 and Broadcom Wireless Driver 5.110.27.20012
After Reset the Routers and Reconfigure it, the WDS Works good and FAST between all nodes. After Reboot of some Nodes, the WDS connect successfully between nodes aggain, but there is no communication possible.
Just for fun - and as last try- i play with the Broadcom-Specific Values, like Afterburner / Frameburst / CTS - and set them all enabled... AND NOW it worked.
Set on both sides, if available:
Security Mode WPA2 Personal
Security Algo. TKIP+AES
Channel Width 40 Mhz
Control Sideband Upper
Afterburner En
AP Isolation Dis
Authentication Type Auto
Basic Rate Default
Beacon Interval 100
CTS Protection Mode Auto
Regulatory Mode Off
Bluetooth Coexistence Dis
Frame Burst En
Multicast Rate Auto
Preamble Long
802.11n Preamble Mixed
Transmission Rate Auto
Interference Mitigation None
WMM En
No ACK Dis
APSD Mode En
Wireless Multicast Forwarding Dis
On WRT54GL / DDWRT, i have WMM disabled... I don´t think it really matters.
Also a WDS-KeepAlive (60s) is enabled. (Ping to next-Hop / Gateway)
This allows to Reboot / Reconnect / Disable & Enable any Node in any order - and it reconnect´s and allows traffic after a while...
On Asus RT-N12, WMM it is enabled - i read, its required for 40Mhz and 300Mbit.
The Wifi-LED tells me absolutely nothing (No Rx/Tx blinking)!
Is there a other GPIO used?
I try to write a script, for a KeepAlive on Tomato, to restart the Wlan-Interface if the next hop/Node is down/lost.
___________
Now I have a question about those two Antennas, used for MIMO:
On RT-N12, i currently use Channel 8 with 40 Mhz...
The WRT54GL find´s my SSID on Channel 6, but I also set / connect with Channel 8!
Is there a possible way on RT-N12, to can set a specific Channel to a specific Antenna?
Are both Antennas (HF-Field´s) required for a connection?
I want to use 2 directional Antennas (in different directions), and i really don´t know how to deal the 40 Mhz.
Can a Wrt54GL/Node/Client connect to this single lower Channel 6? (I Can not test this setup/setting currently...)
Posted: Sat Oct 10, 2015 19:40 Post subject: Asus RT-N12 D1
I have finally managed to install DD WRT on my Asus RT-N12 D1. It was a painful long process. However and when I setup my VPN on DD WRT and specifically while configuring the wireless security, every time I change the security mode to WPA2 or any other option my router goes to local network or limited connectivity. Unless I keep the security mode "disabled" I can't browse the Internet using my vpn. I am not sure what is the solution for this ,but I appreciate if anyone can give some tips.
I badly bricked my asus rt-n12d1 using the cfe miniweb to reset to default... (but resetting to default in dd wrt or doing a 303030 work normally) so I recommend you to avoid doing that...
I've already a thread about that so I don't want to pollute this one with my problem.
But I suggest you backup your cfe before it's too late.
Also
Please someone with a working asus rt-n12d1, please do a cfe backup and send me the file.
Just go http://192.168.1.1/backup/cfe.bin and send me the file.
Thx for saving my router.
:
