EDIT: PROBLEM SOLVED. TOASTMAN CLUED ME IN TO THE CULPRIT. THANKS, TOASTMAN! Hello everybody. Last week, I got my RT-N16 and I've been struggling with an issue that I've been trying my best to figure out become making a thread. The problem: all of a sudden, without any heavy network traffic, just normal browsing, my router will "lock up". The N16 will continue to show up in list of available networks and all my clients can connect to it, but that's pretty much they can do. They cannot access the internet, nor access the Tomato GUI. When I received this router, I played with the original firmware for a bit but an hour later, I successfully flashed the latest 7486 version of Toastman's mod. I made sure to clear the NVRAM after flashing it, turned on DHCP, and connected it to my modem. It worked great for a few days, but then it locked up. This lockup can ONLY be remedied by turning off the router and then clearing the NVRAM by pressing the WPS button when plugging it in and setting it up again as I did when I first bought it. I fixed the first lockup, and 24 hours later, the same lockup occurred. The only settings I've changed from the default are my security settings (WPA-PSK AES), my location which is the US, and I've been keeping it at 20mhz as per the advice on this forum. I had considered raising the transmit power from what I've read in a thread here but I've always kept it at 17MW. I then decided to try Shibby's mod, build5x-079V-EN, hoping the problem would go away, but within 48 hours, the exact same lockup occurred. I cleared the NVRAM twice to make sure I had a clean Shibby install, but no, the same thing happened, with the same settings I had when using Toastman, which were almost entirely default values. I'm currently using my RT-N16 as I type this, and I'm using the latest official Asus firmware released a few days ago, beta 220.127.116.11, which I just flashed before I came to this forum to post this thread waiting to see if the same lockup occurs tonight or tomorrow. I'd also like to mention that I've been running Toastman's latest 2.4 build on my old WRT4GL, and I've never had this lockup before, obviously because it's different hardware and firmware, but for some reason my clients don't seem to have a problem with it. Over the years, I've had original Tomato, TomatoUSB builds, Victek's mod, and finally, Toastman's mod on my WRT54GL, and it has never locked up like this. Not once. I had to use it again for a while this week because I didn't realize I needed to clear NVRAM to make my RT-N16 work well again. Here's my current clients if you guys need clues. -Desktop running W7 32bit, connected to Lan1 via Cat5 on my desk. -Laptop running W7 32bit, connected wirelessly via a built-in Atheros AR928X card. -iPhone 3GS -Canon Mp620 printer, connected wirelessly. Also, I use an older modem. A DCM-202 by Dlink. Could that be the issue? Keep in mind that I've been running this exact group of clients WRT54GL for over 2 years now with a variety of Tomato firmwares and I've never had this problem. The WRT54GL has been rock solid. Hope you guys can figure this one out for me, because this has been driving me nuts this week. I've posted a poll out of curiosity as well.