Linksys WRT54G v 5, firmware 1.0.1.0

For whatever reason. the new firmware (1.0.1.0) for the Linksys WRT54G v 5
and v 6 has a problem with it's DHCP server connecting to Macs and
computers using OS/2 or eComStation. The computer can't find the router.
Workaround is either to set the computer to use a static address, or
reload the prior firmware (1.0.0.9.)


Alan

--

----------------------------------------------------------------------
** Please use address alanh77[at]comcast.net to reply via e-mail. **

Posted using registered MR/2 ICE Newsreader #564 and eComStation 1.21

BBS - The Nerve Center Telnet FidoNet 261/1000 tncbbs.no-ip.com
----------------------------------------------------------------------

On Fri, 17 Nov 2006 18:11:32 -0500, (E-Mail Removed) wrote:

>For whatever reason. the new firmware (1.0.1.0) for the Linksys WRT54G v 5
>and v 6 has a problem with it's DHCP server connecting to Macs and
>computers using OS/2 or eComStation. The computer can't find the router.
>Workaround is either to set the computer to use a static address, or
>reload the prior firmware (1.0.0.9.)

You have it backwards. The computers connect to the DHCP server, not
the other way around.

If it works with a static IP address, my guess(tm) is that you're
using WEP and are trying to use the ASCII text version of the WEP key.
Don't. Use the Hex WEP key and it will work. However, I would
strongly advise you to abandon WEP and switch to WPA or WPA2.


--
# Jeff Liebermann 150 Felker St #D Santa Cruz CA 95060
# 831-336-2558 (E-Mail Removed)
# http://802.11junk.com (E-Mail Removed)
# http://www.LearnByDestroying.com AE6KS

Jeff Liebermann wrote:
> On Fri, 17 Nov 2006 18:11:32 -0500, (E-Mail Removed) wrote:
>
>> For whatever reason. the new firmware (1.0.1.0) for the Linksys WRT54G v 5
>> and v 6 has a problem with it's DHCP server connecting to Macs and
>> computers using OS/2 or eComStation. The computer can't find the router.
>> Workaround is either to set the computer to use a static address, or
>> reload the prior firmware (1.0.0.9.)
>
> You have it backwards. The computers connect to the DHCP server, not
> the other way around.
>
> If it works with a static IP address, my guess(tm) is that you're
> using WEP and are trying to use the ASCII text version of the WEP key.
> Don't. Use the Hex WEP key and it will work. However, I would
> strongly advise you to abandon WEP and switch to WPA or WPA2.

There is a some kind of bug in the DHCP server in firmware 1.0.1.0. When I upgraded(?) from 1.0.0.9,
my Linux wireless systems stopped being able to get an IP address from the AP. Windows still works,
as do the wired computers (both Windows and Linux). So far, I have not had time to debug it, nor
have I found a place to download a copy of 1.0.0.9 for restoring the previous behavior. I had
deleted the old one courtesy of a disk failure. I assigned static addresses for the affected computers.

Larry


Larry

Larry Finger <(E-Mail Removed)> hath wroth:

>There is a some kind of bug in the DHCP server in firmware 1.0.1.0. When I upgraded(?) from 1.0.0.9,
>my Linux wireless systems stopped being able to get an IP address from the AP. Windows still works,
>as do the wired computers (both Windows and Linux). So far, I have not had time to debug it, nor
>have I found a place to download a copy of 1.0.0.9 for restoring the previous behavior. I had
>deleted the old one courtesy of a disk failure. I assigned static addresses for the affected computers.

ftp://ftp.linksys.com/pub/network/wr....9_US_code.zip

For Windoze DHCP (and BOOTP) query tool, see:
| http://www.weirdsolutions.com/weirdS...ytool_free.exe

Linux version of the same:
| http://www.weirdsolutions.com/weirdS...ytool.i586.rpm

--
Jeff Liebermann (E-Mail Removed)
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558

Jeff Liebermann wrote:
> Larry Finger <(E-Mail Removed)> hath wroth:
>
>> There is a some kind of bug in the DHCP server in firmware 1.0.1.0. When I upgraded(?) from 1.0.0.9,
>> my Linux wireless systems stopped being able to get an IP address from the AP. Windows still works,
>> as do the wired computers (both Windows and Linux). So far, I have not had time to debug it, nor
>> have I found a place to download a copy of 1.0.0.9 for restoring the previous behavior. I had
>> deleted the old one courtesy of a disk failure. I assigned static addresses for the affected computers.
>
> ftp://ftp.linksys.com/pub/network/wr....9_US_code.zip
>
> For Windoze DHCP (and BOOTP) query tool, see:
> | http://www.weirdsolutions.com/weirdS...ytool_free.exe
>
> Linux version of the same:
> | http://www.weirdsolutions.com/weirdS...ytool.i586.rpm
>

Thanks for the URL's.

Larry Finger wrote:
>> Larry Finger <(E-Mail Removed)> hath wroth:
>>
>>> There is a some kind of bug in the DHCP server in firmware 1.0.1.0.
>>> When I upgraded(?) from 1.0.0.9, my Linux wireless systems stopped
>>> being able to get an IP address from the AP. Windows still works, as
>>> do the wired computers (both Windows and Linux). So far, I have not

I was wrong here. Wired Linux computers also fail. I reported it to Linksys and "their engineers are
working on the problem."

Larry

Larry Finger wrote:
> Larry Finger wrote:
>>> Larry Finger <(E-Mail Removed)> hath wroth:
>>>
>>>> There is a some kind of bug in the DHCP server in firmware 1.0.1.0.
>>>> When I upgraded(?) from 1.0.0.9, my Linux wireless systems stopped
>>>> being able to get an IP address from the AP. Windows still works, as
>>>> do the wired computers (both Windows and Linux). So far, I have not
>
> I was wrong here. Wired Linux computers also fail. I reported it to
> Linksys and "their engineers are working on the problem."

Linksys has released firmware version 1.0.1.1 for WRT54G V5 and V6 wireless routers. The new version
corrects the problem of using DHCP with Linux. It is likely that it also works with OS X, but I
cannot test that.

Larry