For the WRT54GL, there are some things to try:
- inital versions of the WRT54G hardware (now called the GL) would reboot under load. The fix is to
overclock the broadcomm chip to 216MHz. New firmware should do this automagically. [The resaon
for the name change was that the new WRT54G runs different (non-Linux) firmware and can't use
firmware for the older HW design. Linksys continues to sell the old 45g design as the 54gl because it's a
popular router for the embedded crowd).
- Other than the above, I've had good luck with the WRT54G/GL hardware after I reflashed the frimware
with straight Linux. If you're not a Unix type, the dd-wrt firmware looks most like the original linksys
stuff:
http://www.dd-wrt.com Personally, I've used openwrt for a couple years. Much less "point and clicky" -- In fact, I don't even
run the web interface, configuration is done by SSHing to the hub and editing files. If you're unix literate
you'll be right at home.
http://openwrt.org/ [This is basically the same as misconfigurations suggestion, execpt that the linksys HW is cheaper and
more power efficient that an old PC. But of course you won't be using hacked linksys for any heavy
duty tasks.]
- YMMV, but I've usually found port-triggering to be more of a problem than a solution. I just run
vanilla NAT rules on the linksys (or other firewall/hub/ap) and then run Software firewalls on the
linux/windows/mac systems in the lan and nothing special on PS/2 and Xbox360. So two sets of
firewalls, but no funky triggering. In this config the windows firewall seems better (read: less of
a headache) than nort/ice/etc. Most games seem to run fine without port triggering, including
stuff like SOCOM and BF2. [Plus, I do unix security as a job, so port-triggering scares me.
]
Good luck,
Dale