NYTimmy wrote:
Your pompous attitude is not very helpful to the hundreds of people on this thread that are clearly having an issue related to their upgrade to Lion. Did you ever consider that the way Lion handles wireless protocol negotiation might be locking up the router.
Guess what - if that happens, it's a firmware bug in the router.
How many times do I have to reiterate that if a client can cause a router to "lock up" or otherwise stop working, it's the fault of the router?
That doesn't meant Mac OS X doesn't have bugs, that doesn't mean it may not be doing things it shouldn't, but if the router locks up, it's a buggy router, period.
That's not pompous, arrogant or anything other than truthful.
So perhaps, just perhaps, this is a bug in DD-WRT and you should try a different router.
For example, if you happen to have a revision 2.2 WRT-54GS:
Apparently there is a bug in the WRT54GS v2.2. The bug involves a fatal memory access error due to a difference in the CPU clock speed and the clock speed on the memory bus. This bug causes connections to be dropped when transferring large files. New versions of the Linksys firmware overclock the CPU to 216 MHz. This can be fixed by logging into the router via SSH or Telnet and executing the following commands:
nvram set clkfreq=216
nvram commit
reboot
When running DD-WRT micro v23sp2 on a WRT54G v5 the clock speed can be adjusted by logging into the router via SSH or Telnet and executing the following commands:
nvram set overclocking=216
nvram commit
reboot
After rebooting the router you can confirm that the new clock speed has applied by checking the Status page of the DD-WRT GUI or by logging in via Telnet and executing the following:
nvram get clkfreq
DD-WRT Router Slowdown Wiki