i do use wpa2 personal, too ,( aes ) without any issues. try another wireless computer.
I've tired an iPhone 5, iPad 4, iPhone 4S, MacBook 2009, MacBook Pro 2013 and a 2012 iMac 27"
Don't actually have any windows machines on with wifi to test with.
I've gone back to Merlin's firmware and it works perfectly. Ill just wait for the next build or try kongs firmware, but I'm sure I had a show stopper issue with that too, probably optware.
i do use wpa2 personal, too ,( aes ) without any issues. try another wireless computer.
I've tired an iPhone 5, iPad 4, iPhone 4S, MacBook 2009, MacBook Pro 2013 and a 2012 iMac 27"
Don't actually have any windows machines on with wifi to test with.
I've gone back to Merlin's firmware and it works perfectly. Ill just wait for the next build or try kongs firmware, but I'm sure I had a show stopper issue with that too, probably optware.
Optware is a big catch 22 with RT-N66U at the moment. USB is currently broken in K26 and doesn't look it will be fixed for the 2.6 kernel either by the devs. Its been fixed in the newer kernel, but Optware isn't exactly ready for 3.x kernel (yet). A lot of work is required for it, so its a big job.
Catch 22 right? Kong will be likely compiling 3.x kernel firmware once its gone through testing, see more here:
I have ntp client enabled, time zone and DST set correctly. Use north-america.pool.ntp.org so far no issue with time. I even have cron scheduled wol commands to wake up systems on my network at night for backups. They have so far worked flawlessly at the correct time. _________________ Asus RT-N66U / DD-WRT v24-sp2 (Build 23598)
Ordered the RT-N66U just now and planning on flashing the K3.x version on it straight away. From what I can gather I can straight away flash it on the stock firmware via the web ui. But what happens if the stock version has the newer CFE with 64k NVRAM? Can I still use the same build or am I forced to find out if it has the newer CFE? Thanks a lot.
Ordered the RT-N66U just now and planning on flashing the K3.x version on it straight away. From what I can gather I can straight away flash it on the stock firmware via the web ui. But what happens if the stock version has the newer CFE with 64k NVRAM? Can I still use the same build or am I forced to find out if it has the newer CFE? Thanks a lot.
Not if you jump straight from stock to DD-WRT 3.xx kernel
Ordered the RT-N66U just now and planning on flashing the K3.x version on it straight away. From what I can gather I can straight away flash it on the stock firmware via the web ui. But what happens if the stock version has the newer CFE with 64k NVRAM? Can I still use the same build or am I forced to find out if it has the newer CFE? Thanks a lot.
Not if you jump straight from stock to DD-WRT 3.xx kernel
Ordered the RT-N66U just now and planning on flashing the K3.x version on it straight away. From what I can gather I can straight away flash it on the stock firmware via the web ui. But what happens if the stock version has the newer CFE with 64k NVRAM? Can I still use the same build or am I forced to find out if it has the newer CFE? Thanks a lot.
Not if you jump straight from stock to DD-WRT 3.xx kernel
The 3.xx builds detect the CFE and NVRAM space setup and adjust accordingly.
Alright thanks, I was confused as there are the "-nv64k" builds of 3.xx. But I guess they only apply to the dd-wrt builds with nv64k.
Again from the wiki:
Quote:
If you are already on a custom 64K Build like Fractals or Kongs with a CFE 1.0.1.3 you need to flash dd-wrt.v24-21676_NEWD-2_K3.x_mega-nv64k.bin. Since K2.6 Builds have an embedded check, you need to use those special nvXXk trailed images. On K3.X this check has been removed and you can simply upgrade from a previous K3.X to newer svn using dd-wrt.v24-YYYYY_NEWD-2_K3.x_mega.bin. You can find all files in the folder named above.
For anyone on K26 using n64k builds (i.e. Fractal or Kong), you'd need to use a build with n64k in the name for the correct header. Once your on the 3.xx kernel, you can flash the generic mega build there after I believe. _________________ James
Main router:
Netgear R7000 overclocked to 1.2GHz - DD-WRT v3.0-r35965M kongac
IPv6 6in4 (HE.net), OpenVPN (with PBR and split tunnelling), Entware, dnsmasq with ipset
Non-authoritative answer:
72.2.123.204.in-addr.arpa name = usno.pa-x.dec.com.
Authoritative answers can be found from:
root@DD-WRT:~#
204.123.2.72 is a local stratum 1 time server close to my home.
Windows 7 time taken short while later
Code:
C:\>time
The current time is: 21:18:46:22
Enter the new time:
C:\>
These same values work fine on my production router running DD-WRT v24-sp2 (04/07/12) big - build 18946M NEWD-2 K2.6 Eko on an RT-N66U
-- Mache
Honestly, without knowing your setup I don't know why NTP doesn't work. I don't believe any recent builds have been reported with NTP functionality being broken, I would have to say something with your setup maybe is causing it.
Reflash another build maybe or 30/30/30 reset it and try again. _________________ James
Main router:
Netgear R7000 overclocked to 1.2GHz - DD-WRT v3.0-r35965M kongac
IPv6 6in4 (HE.net), OpenVPN (with PBR and split tunnelling), Entware, dnsmasq with ipset
Posted: Thu Jun 27, 2013 9:49 Post subject: Newbie troubles
Hi,
I just got an RT-N66U this morning
I flashed from stock firmware so I used dd-wrt.v24-21676_NEWD-2_K3.x_mega_RT-N66U.trx and everything seemed to go well.
When I reset the lights came back on but it wasn't giving out addresses over Ethernet. I did however finally manage to get in using Wi-Fi as dd-wrt was available as an SSID.
I don't know if anyone else has experienced this but I thought I'd put it here for future reference.