Not to worry...
DD-WRT caught my eye because it was Sveasoft Talisman and the purpose of
them doing this variation sounded just like the thinking of a good
sysadmin. The other stuff was just a red flag but like you say not
critical to function.
I am quite pleased with how things are working so far. I am trying to
find info on a safe level to turn up the wireless radio. EWRTv0.2 (on my
old WRT54Gv2 HW) recommends no more than @60-65 on a scale that tops out
at 84mW for any length of time but I notice the Sveasoft variations
start at the Linksys default of 28mW and scale to 251mW. That is a big
difference given 84mW supposedly can fry the wireless radio if set that
high over time.
If you hear of any fry level details lemme know... Thanks.
RBW
Tom Gal wrote:
I won't lie. I get the version from the site, and it's always worked
perfectly (except in cases where there was documentation otherwise).
Personally I like to evaluate things on functionality, ease of use,
and of course cost, rather than what license it runs under or who
wrote it. This software works great for $20. That's enough for me.
T
On 8/25/05, RBW <[EMAIL PROTECTED]> wrote:
RBW wrote:
Tom Gal wrote:
The sveasoft firmware is the best thing to hit linksys routers I've
found. All the functionality, gives you security, ssh/shell access to
the device, and let's you jack the power way up along with just about
everything else you can imagine. I install it for someone almost every
week, and I've been running it on various linksys routers in my purvey
for some time now.
-T.
On 8/23/05, RBW <[EMAIL PROTECTED]> wrote:
Has anyone put "alchemy" from Sveasoft on their WRT54G? How is that
working?
Has anyone put "Alchemy" from this alternative onto their WRT54G?
http://wrt54g.thermoman.de/
I was using EWRTv0.2 for some endusers (I'm saving the fun of OpenWRT
for myself and my next WRT54G/GS for later) but the EWRTv0.3beta lacks
non-CLI WDS and "client" mode (which was in v0.2) for the wireless
radio. It appears that this Freeman Basic/The "Individual" method may
work fine in setting up a WDS config and/or a "client" wireless bridge
that will also accept connections as a WAP while bridging...
I'm looking around the different options and how a 3rd party firmware
with a GUI interface like the original Linksys might work for someone
who will eventually need to be told to do this or that in a non-CLI
manner.
TIA for any tips,
RBW
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
Is that the pay (the bastards) $20 method or the do you use one of the
offerings from this "Individual" person and could you post back the
file name of a recent firmware you've had success with?
Sorry to mention the GPL warfare but it does cloud the process of
making a proper useful decision.
RBW
This 3rd party firmware worked...
http://wrt-wiki.bsr-clan.de/index.php?title=DD-WRT_Docu_%28EN%29#What_is_Needed.3F
Following this procedure (with appropriate modifications for the
particular circumstances)...
http://www.linksysinfo.org/modules.php?name=Content&pa=showpage&pid=7
So I have an older WRT54Gv2 hardware running an older different 3rd
party firmware (WDS capable) connected via cat5 on the WAN side to the
DSL modem and I have a WRT54Gv3 hardware running DD-WRT and connecting
to the first unit on the LAN side wirelessly while also accepting
connections from the wireless card on the laptop.
This is good because previously I had a very old wireless AP/switch
connected via cat5 to a wireless bridge connecting to the first WRT54Gv2
unit to reach all parts of the lot. Now the bridge is not necessary with
WDS working.
RBW
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
