Hey guys, I just picked up an RT-N66u after having enough with the free router from Optimum.
First thing I did was install Merlin on it as I love to break stuff out of the box apparently.
Just a note, I always use a static IP on my main PC so this isnt an issue as in all cases I can ping the router fine.
I put it in recovery mode, flashed the file, etc. Wouldnt come back up, no power light blinking but the Lan1 light blinks regularly. So I reset holding wps for nvram and it comes up. All appears to be good.
I name the SSIDs, and then typically I like to change the routers lan ip to 192.168.1.2 so I can attach to my current network, compare settings on previous router, port forwards, etc and copy them over.
So I set it to .2, connects to the dlink fine, I can connect to both and ping both. good.
I take a break and play some xbox for an hour.
I come back over, the N66u is off, no power. I check the power adapter, no blue led.
I unplug and try in another socket, nothing. I plug into original outlet, nothing. I unplug it from the router, the led comes on. I plug back into the router now the led is blinking on the adapter. I unplug/replug a few more times and now the router comes back up. I can ping the .2 but I can no longer connect to it.
I reset the nvram, back to 1.1. I then set to 1.2 again. It "applies" it and reports back it is 1.2 but i am still connected via 1.1 and cannot ping 1.2. It didnt automatically change. I click the reboot option in the menu, it hangs for a bit, but still comes back as 1.1. I physically power off and back on, now I cannot connect or ping 1.1. Good, I try to connect to 1.2 on browser, no connection, but I can ping 1.2.
So I read up that I probably didnt give the firmware proper time, since i only waited 5-10 mins, so I figure Ill do a clean install. I kick that off last night and give it 6 hours. I come over, power and lan1 blinking, all is good.
I do the same, name the ssids, set it to .2. Again it does apply this immediately, and doesnt change until a physical reboot. Same as before, I can ping .2 but cannot connect via browser.
So now I check if the ssid's are broadcasting, no.
Ok, so I reset nvram again, back to 1.1 and I can connect to it. So I set up the ssids, which I hadn't actually tried yet. I check on my phone and tablet, nothing is coming up.
So last checked, freshly reset nvram, I am not seeing my ssid's at all. Not broadcasting, nor can I manually connect to them.
I also noticed the core1 was always at 100%.
As of now I just set to recover mode again and applying the stock asus firmware to narrow it down.
Any ideas on what may be going on? It seemed to work fine that first time but for less than an hour. Then the odd power supply behavior. Do I have a faulty unit already? Am I missing something? I dont know why just changing ip to 1.2 to now make me unable to connect to it. It looked like wifi was on for me
First thing I did was install Merlin on it as I love to break stuff out of the box apparently.
Just a note, I always use a static IP on my main PC so this isnt an issue as in all cases I can ping the router fine.
I put it in recovery mode, flashed the file, etc. Wouldnt come back up, no power light blinking but the Lan1 light blinks regularly. So I reset holding wps for nvram and it comes up. All appears to be good.
I name the SSIDs, and then typically I like to change the routers lan ip to 192.168.1.2 so I can attach to my current network, compare settings on previous router, port forwards, etc and copy them over.
So I set it to .2, connects to the dlink fine, I can connect to both and ping both. good.
I take a break and play some xbox for an hour.
I come back over, the N66u is off, no power. I check the power adapter, no blue led.
I unplug and try in another socket, nothing. I plug into original outlet, nothing. I unplug it from the router, the led comes on. I plug back into the router now the led is blinking on the adapter. I unplug/replug a few more times and now the router comes back up. I can ping the .2 but I can no longer connect to it.
I reset the nvram, back to 1.1. I then set to 1.2 again. It "applies" it and reports back it is 1.2 but i am still connected via 1.1 and cannot ping 1.2. It didnt automatically change. I click the reboot option in the menu, it hangs for a bit, but still comes back as 1.1. I physically power off and back on, now I cannot connect or ping 1.1. Good, I try to connect to 1.2 on browser, no connection, but I can ping 1.2.
So I read up that I probably didnt give the firmware proper time, since i only waited 5-10 mins, so I figure Ill do a clean install. I kick that off last night and give it 6 hours. I come over, power and lan1 blinking, all is good.
I do the same, name the ssids, set it to .2. Again it does apply this immediately, and doesnt change until a physical reboot. Same as before, I can ping .2 but cannot connect via browser.
So now I check if the ssid's are broadcasting, no.
Ok, so I reset nvram again, back to 1.1 and I can connect to it. So I set up the ssids, which I hadn't actually tried yet. I check on my phone and tablet, nothing is coming up.
So last checked, freshly reset nvram, I am not seeing my ssid's at all. Not broadcasting, nor can I manually connect to them.
I also noticed the core1 was always at 100%.
As of now I just set to recover mode again and applying the stock asus firmware to narrow it down.
Any ideas on what may be going on? It seemed to work fine that first time but for less than an hour. Then the odd power supply behavior. Do I have a faulty unit already? Am I missing something? I dont know why just changing ip to 1.2 to now make me unable to connect to it. It looked like wifi was on for me