Linksys WET54G v3 Annoyances

In Adhoc mode, two WET’s cannot use wpa security and connect to each other.
WPA only works in Infrastructure mode.
2 WET’s can only connect in ad-hoc mode.

Linksys refuses to post this information on their website.

Linksys refuses to give out the release notes for v1.08 of the firmware for the WET.

Awesome.

Part 2.

A WET54G v3 v1.08 firmware and a WRT54G v2 v4.20.7 firmware can only we connected using WPA1 TKIP for security (if you want WPA.)
This must be done in infrastructure mode.

I know this. Not one goddam stupid son of a bitch at Linksys tech support has access to this information. (until they read this blog.)

Awesome. I love Linksys. Cisco did a fucking great job transforming them from a shoddy company that makes half ass products with lousy support and terrible documentation. Keep it up!

One more note, there is a problem with using my domain’s dns suffix across the bridge. We don’t use netbios, just dns in the environment.

nslookup mycomputer.domainname.local fails
nslookup mycomputer succeeds.

Not sure why. Have to remap some drives b/c they had the suffix in their name. But it looks like this will work.

One Response to “Linksys WET54G v3 Annoyances”

  1. jake c Says:

    Your post is quite interesting, I have had a different situation

    I have a WRT54GX firmware 1.02.19 with the WET54 v 3 firmware 1.08
    and with TKIP security it will only stay connected a few minutes.

    I have had to use AES security in order to maintain connection.

Leave a Reply