Ran into a weird little bug while switching my routers over to Tomato. When I had ddWRT v23 on both of my routers I was getting about 17-21 Mbps (iperf results) between my two WRT54GLs and it wasn't sufficient for HD streaming so I was trying to squeeze every last drop I could out of the wireless link. One thing I tried was Afterburner, and to my absolute amazement, my throughput dropped to about 3-5 Mbps with Afterburner set to enabled on both devices. I thought maybe there was something wrong in ddWRT, so I gave it a try again once I got Tomato loaded on both of the boxes. On my AP/gateway box I set it to enabled, it saved and restarted some services, and went on it's merry way. On my wireless bridge box, an identical WRT54GL, when I set Afterburner to enabled or auto, I lost all connectivity to the box. I wondered downstairs to power cycle it, and I noticed it was rebooting over and over and over and over and over. I power cycled it, and it did the same ... flashing light while booting, solid light for about 2 seconds, then reboot and flashing light again. I reset to factory defaults, went back in, turned it on again, and again, the exact same thing, non-stop rebooting. I reset to factory defaults again and didn't bother trying Afterburner anymore. I wouldn't hesitate to call this a bug, as even if there is something wrong with the router, constant rebooting is not a desirable result of changing something in the configuration ... but I am a little confused about the potential trigger as well ... I thought Afterburner was not a hardware thing, but a software thing? If it's working (well, not causing reboots) on the one WRT54GL I'm not quite getting why it's causing issues on the other box. Any insight or advice would be greatly appreciated.