DD-WRT Standard v24 Beta

[SephYuyX]

So finally got around to picking up a WRT54GL, and I installed DD-WRT Standard v24 Beta on it. I just wanted to see if you guys have done any cool stuffs with this thing before I go through about 100 pages of modding discussion.

[Caiyuo]

Nothing comes to mind from a blank slate, but do you have anything in mind regarding your network setup that interested you?

Also if you haven't seen this yet, it might save you some time: http://www.dd-wrt.com/phpBB2/viewtopic.php?t=51486

[Blabj]

Have my Buffalo WZR-HP-G300NH set up to mount a usb drive as a NAS for communal file sharing. Everything else is just some useful traffic shaping for things like prioritising game traffic over bittorrent, etc.

[Kriz]

I always wanted to have my DD-WRT router do that PeerGuardian/IP Blocking thing, and I've read about doing it on the router itself on the forums, but haven't done it yet.

I have mine auto-refresh a dynamic DNS service so a desktop client doesn't need to be run, that's pretty useful.

[octopus]

I use tomato rather than dd-wrt. I'm sure you can do this for dd-wrt, but one thing I do is to do adblocking at the router level, redirecting blocked sites to 0.0.0.0.

[Caiyuo]

I've been hesitant to try tomato because as far as I know there isn't a forum or a source to find answers to little problems. Is that the case? Do you ever have trouble with things like that? I'd love to try it, I've heard the QoS works really, really well.

[octopus]

This is the forum I use for Tomato help:

http://www.linksysinfo.org/forums/fo...play.php?f=160

[Caiyuo]

That'll do, lol.

[SephYuyX]

Actually running in to issues with FFXI. Anyone uisng DDWRT and XI? Do anything to get that working?

Also ran in to issues with utorrent, set up port forward rules that should have worked, but it didnt. Enabled upnp and it worked fine; took a look at the rules upnp set up, and they were the exact sames ones I made.. Unless something other than port forwarding needed to be done.

[Dmitry]

I have DD-WRT on my router set up as a wireless bridge and didn't have issue with PS2 FFXI. Are you getting an error ?

[SephYuyX]

No errors.

It connects fine, and plays fine, but after 5~10mins it disconnects (FFXI autodisconnect is off, havent changed anything game-wise). I followed FFXI on portforward, but that didnt change anything.

Im not using it wirelessly atm, im physically connected to it (but it's set in AP mode).

From the brief time ive tried to figure it out, it seems it stays active for as long as I play the game, but once I idle, it disconnects. But again, I havent played more than just a few minutes at the time, so I havent tested it very much.

[Caiyuo]

Did you pick one of the builds listed in the Peacock thread I linked? Not sure which build you meant in OP but they pretty plainly say the current releases are pretty buggy.

[SephYuyX]

Didnt even see those.
Im using generic standard (non USB) 13491.

All ive seen is his thread is "DONT USE THIS ONE OR THAT ONE"
lol, what is a "recommended" one? Im just looking for semi-advanced basic options, nothing crazy needed.

[SephYuyX]

So his posts mentions ftp://dd-wrt.com/others/eko/BrainSla...4929/broadcom/ as being the best.
But I dont see WRT54GL listed. Would using mini generic (or std generic) work fine, or?

[Caiyuo]

Yeah it's got kind all over the place, but as far as the broadcom forum section is concerned it's the best information collection. I think from reading the WRT54GL also had a specific install issue about starting with a mini build and then installing the standard build in case you didn't see that in the wiki. I haven't had any notable problems with DD-WRT, even with FFXI, but maybe tomato would be a good consideration? I'm thinking about trying it this weekend. As far as your actual problem, if the connection with XI's servers is timing out, I can only think of looking at the TCP and UDP timeout section under Administration to see if they're set excessively low (some torrenting/P2P guides say to do this). If you're losing your internet or network connection altogether when this happens, then I have no idea outside of a build-specific problem.

Here's the part about specific builds:

Spoiler: show

3. Upgrade to a recommended newer build, especially if you are running SP1 or v24 final (05/21/08 ). Newer builds contain fixes for bugs. At the time of writing, the latest official build is v.24 SP1. SP1 has a LOT of issues. It will spontaneously brick the Asus WL500W router. These issues are fixed with some of the later builds. However, sometimes new builds have new bugs. New builds are BETA and not "finished" yet. Although you use them at your own risk these builds have been pretty thoroughly tested and work well, certainly better than SP1. Browse the forums and see what others are saying.

Prior to upgrading, understand how builds work by reading note 4, below, and ALWAYS follow the wiki install for your router when initially flashing it from oem firmware!

These are the recommended builds:
Brainslayer 14929. This build has worked fine in most configurations and should be used in most cases.

Here is a link to the NEWD BS 14929 builds:
K24 builds:
ftp://dd-wrt.com/others/eko/BrainSla...4929/broadcom/

K26 builds (see below to determine if you need k24 or k26...screwing this up will brick your router)

If you have installed 14929 and are having problems, ESPECIALLY IF REPEATER MODE ISN'T WORKING for you, try dropping back to EKO 12548[/b] .

This is a link to these the new EKO builds. Click on the link and open the folder with the same number as the recommended build you wish to use:

EKO:
ftp://dd-wrt.com/others/eko/V24_TNG/

Here is the direct link to the newer BRAINSLAYER builds:

Brainslayer:
ftp://dd-wrt.com/others/eko/BrainSlayer-V24-preSP2/

Be sure to understand whether you need a VINTage driver, NEWD driver OR NEWD2/K26 BEFORE you upgrade. Some newly supported routers can ONLY use K26 builds, but don't use K26 unless you have to.

If you HAVE to use k26 (which you can tell by whether when you originally flashed the router, you were required to use a build with K26 in the name) here is the link to the k26 builds. Putting these on a router that isn't supported WILL brick it.

If you NEED a k26 build, here is the link to the recommended build.
ftp://dd-wrt.com/others/eko/BrainSla.../broadcom_K26/

Use one of the recommended builds mentioned here NOT 14896, 13064 (Build date 10/10/09) or SP1, regardless of what the router database recommends!

Note that if you need VINT for your router, (see note 4 on this) you must use EKO builds since new BS builds do not include the VINT driver. Build 13491 is a recommended VINT build. You can also try 15230 but some are reporting problems with the 15230 build on routers that need VINT. Since build 12548, a decision was made not to overlap BS and Eko builds. So, if BS already creates a generic standard build, for example, EKO will NOT be compiling that build in his build folders. Additional differences between EKO and BS are explained in the thread linked in note 18.

Due to the exploit that is discussed in the following link, if you wish to use older builds, you should modify your startup script according to the instructions. Otherwise, you should use one of the latest builds. See the development announcements here:

http://dd-wrt.com/dd-wrtv3/

If you do not wish to have to patch the firewall script, use one of the above recommended builds.

You should not put SP1 or 13064 (Build date 10/10/09) on your router....use one of the builds recommended here. Although not as bad, it seems that quite a few users are also having some problems with 14896.

You can get Beta Builds at Downloads, Other, Eko, TNG_24, and then go to the folder number that matches the recommended build number. There is a direct link below

Sometimes, a wireless encryption type doesn't work, so you might have to try another one if one is not working. I believe most if not all encryption are working with the later recommended builds. WPA2-AES is secure and working well.

Each build has a thread on the forum. These new builds have worked out well, and have many changes that improve dd-wrt compatibility with Wireless N/Dual Radio setups. If you need wireless N speed, or have a dual radio definitely check out the build threads and see what others are saying.

SECURITY settings often do NOT work properly with v.24SP1. SP1 also does not forward DHCP properly in bridged mode.

Builds that are newer than the recommended ones listed here are not necessarily better. If you see a newer folder and think you will try that, even though it's not one of the builds recommended in this announcement or Redhawk's, be sure you have a jtag cable and a place to attach it.

Some people are jumping ahead to the newer NEWD-2 builds (builds with NEWD-2 in the name) even though they are not recommended builds and without reading the build threads that are available for each new release. Do NOT put NEWD-2 on your router without reading the build threads and knowing what you are doing. Noobs are best advised to stay away from Newd2. We are not seeing any significant benefit from the Newd2 driver. NEWD-2 will brick many routers. See these threads for guidance:
http://www.dd-wrt.com/phpBB2/viewtopic.php?t=54711
http://www.dd-wrt.com/phpBB2/viewtopic.php?t=55625
And this wiki article:
http://www.dd-wrt.com/wiki/index.php...on_some_models

Some newer routers MUST use K2.6 builds. If you originally had to flash a build with k2.6 in the name, you likely will ALWAYS have to flash a k2.6 build. K2.6 builds always use the Newd-2 driver. See note 4, below for further info on this.


Make sure your firewalls and virus protection are disabled prior to upgrading. Some people have had problems accessing their router due to not disabling their computer security.


Remember that newer is not necessarilly better!!!

The router database has recommended some less stable builds, including SP1 and 13064 (10/10/09) build. I suggest using the builds that are recommended here or in Redhawk's announcement above, rather than the ones in the router database. SP1 is full of bugs, and while 13064 is not nearly as bad, some are reporting connection issues fairly regularly. Sometimes the router database also has had the wrong build type. The router database is being worked on improve the recommendations. Do not skip over reading the install wiki for your router just because you got the files from the router database. You need to KNOW what to do with those files. The wiki usually has the right builds for particular routers. READ THE WIKI!

edit: lemme check the wiki re: mini/std

yeah the generic is what you're looking for. The others are just specific builds for hardware that the generic doesn't work with. Here's the wiki page for GL as well if you're interested: http://www.dd-wrt.com/wiki/index.php/Linksys_WRT54GL

[SephYuyX]

I forgot to mention that I did lower the tcp/udp timeouts, and when I changed them back to a higher number, I stopped getting disconnects.. lol whoops.

Looking at his recommended Brainslayer 14929 NEWD K24 link, there isnt wrt54gl listed, but there is a generic build. Im wondering if that will work fine.

I did have to use micro first, then I flashed to "standard".

[Caiyuo]

Sorry edited last post. Yup, that'll work fine, I think specifically you'd want "dd-wrt.v24_std_generic.bin" from that ftp listing. I mean, if it's fixed it might not be worth the trouble of reconfiguring everything since they stress never to use backup for settings anytime you change builds, but it seems worthwhile in general.

[SephYuyX]

Havent done anything but enable upnp, so i'll give that build a go. Thanks.
Tomorrow I should have a chance to mess around with it.