Hi, I've been messing around with running a few of the alternative firmware for my linksys 54g router. First I tried to run the Satori branch, which failed miserably and wouldn't allow me to go online. My second try I went with the DD-WRT branch, which seems to run pretty nicely. I've got his rFlow Collector running, and i love it. The main reason why I started doing all this, is we have 3 or 4 various airports at my house, my dad just keeps getting more extreme airports or the express. So I wanted to hook everything up with WDS to have one nasty coverage area. This all was pretty simple to setup, and I even got the WDS working over ethernet to my linksys, however when I'm walking around my house and it switches APs I get any open downloads dropped and my RDP connection closes. Is there any way around this? When I'm pinging something it usually doesn't loose any pings when it hops to a new AP, but other open connections close.

Is anyone also messing around with this?

I'm just about to install dd-wrt on my 54g. Or maybe an alchemy derivative. Not sure yet.

I'm still on Alchemy-pre7a. I haven't looked into what DD-WRT adds or why I should upgrade lately, but my Alchemy version has worked well for me. Haven't noticed anything like dropping connections or anything, been using it with 3 WDS nodes for quite a while now.

A friend of mine was going on about how nice OpenWRT was.

I just picked up a WRT54G. What's a good alternative firmware that includes good QoS support for VOIP (I'm using SunRocket) and has a caching nameserver?

Reason I ask is because my old solution was a 2wire gateway from SBC DSL, and it would automatically cache it's local DHCP addresses and serve them up via a local caching name server. That's really the only thing I miss about my old (SLOW) dsl setup, heh.

-- Gary F.

If you're buying now then get a WRT54GS. It's slightly more expensive but has more flash than the other models/revisions. It has generally better specs than any of the WRT54G's. Firmware should be the same for all of them.

There is one model/version you want to stay away from. It has a buggy ethernet chip. It reliably, after X number of megabytes, goes strange and drops wireless connections.

At first they thought it was the driver. An updated driver was released. Them that are smart, figured out that what it did was overclock the cpu. As far as I can tell it didn't help. If you dig around in the Sevasoft forum there is much better info.

BTW: My GS is in the bin with all the other electronic bits I can't stand to toss, but should. It was replaced with a D-link part.

Already bought, and got the G.

-- Gary F.

What revision is it? The newer ones run faster, have more RAM and flash than the old ones. You lose the miniPCI slot however since it become integrated.

What version?

Here are some links to posts in the sevasoft forum.

http://www.sveasoft.com/modules/phpBB2/viewtopic.php?t=11133&highlight=bug

http://www.sveasoft.com/modules/phpBB2/viewtopic.php?t=11427&highlight=bug

http://www.sveasoft.com/modules/phpBB2/viewtopic.php?t=11988&highlight=bug

I had some serious problems with the alchemy and satori versions, like almost a completely dead router. It would never come online correctly, or if it did the DHCP service was really buggy.

DD-WRT seems to run excellent, besides the connection hiccups when I'm roaming between various APs in my house. I wish I could figure out what it was, maybe it's just my old 54g, I think I might just purchase a GS and see if that fixes my problem, if it doesn't it's another access point I can use to expand my hotspot

It's revision 2.2

I'm checking out the various firmwares now, thanks for the links!

-- Foz

Ok, just for completeness I thought I'd post what I went with.

I decided to try the latest DD-WRT firmware (which seems to be based upon a fork of the sveasoft stuff but I could be mistaken). It pretty much does everything I want it to do (DNS masq, QoS, etc). The port forwarding interface is clunkier than I'm used to, and at one point I had to manually clear out some forwarding instructions out of the nvram when the interface got out of sync with it, but it does seem to be working via uPnP and manually.

It also includes the xlink kai daemon (a free implementation of Xbox live) and I'll be testing it out soon. I haven't fiddled with the QoS much yet, but I'll be spending some time this weekend tweaking it with my SunRocket VOIP gizmo (yeah, they really call it a "gizmo") to see how well it works. Knowing the twiddler in me I'll probably wait until I have it working perfectly, then I'll wipe it and rebuild it with something else though

-- Foz