WRT54G Firmware Upgrade

mimi hath wroth:

Yet another way. Right click on the "My Computah" on the desktop. Select Properties -> Hardware -> Device Manager -> etc. I think you're working under the "advanced" tab.

Fastest way: Start -> Run -> cmd devmgmt.msc

Extra credit: To go directly to various control panel and admin appletes, first make a list with: Start -> Run -> cmd cd \\windows\\system32 (or winnt for w2K) dir *.msc You can kinda guess what they do by decoding the file names. For example, gpedit.msc is the Group Policy Editor.

That will not work. The "properties" for your unspecified wireless device is usually a rather extensive list. There are several places where it lists the wireless channel. One is for ad-hoc networking only and will change the channel. The other is for infrstructure type networking and will change as soon as you connect to an access point. I guess(tm) that the setting is there for a starting channel when the client scans for a suitable access point to connect. In infrastructure mode, the channel is controlled by the access point, not the client.

You're mixing two questions here. Encryption has nothing to do with channel. You can mangle the encryption any way you want, and you still be able to connect. That's because the access point controls the channel, not the client computah. If you tweak the registry or device properties to claim that the client is on channel 1, but the access point is on channel 11, you're going to end up on channel 11 (in infrastructure mode). Ad-hoc is a different story.

No clue why you can't connect (or what you're trying to accomplish). Since you're into tweaking, it's likely that you have changed something that shouldn't have been changed. Hard to tell from here, especially since you didn't disclose what device you're tweaking. In another part of this thread, you seem to have solve the encryption key problem, so I guess it's fixed.

Incidentally, if you're a masochist, try enabling the Windoze Wireless diagnostic output using: netsh ras set tracing * en net stop wzcsvc net start wzcsvc Look for log files in: c:\\windoze\\tracing\\ directory. There's quite a bit of output, but something should show up in wzctrace.log.

I usually save a trace file collection for a normal connection. Then, when something goes awry, I can compare it with the current version.

mimi hath wroth:

I have no idea what he was doing. Channel 6 is the most commonly used channel. That's because it's dead center in the middle of the band, which puts it in the middle of the bandpass filter pass band, the middle of the antenna VSWR curve, and generally at the performance peak. The bad news is that everyone else does the same thing thus creating the maximum potential for interference. For example, at this time, I can see 6 networks on Channel 6, and a total of 4 on all the other channels.

Nope. That's because I have only a bad clue what you're using for hardware. You've also added your question on the tail end of someone else's problem thus creating a muddle. The subject line says "WRT54G Firmware Upgrade". I think you have a WRT54G but I'm not sure.

For a marginal site survey under Windoze, see Netstumbler:

or Wi-Fi Hopper:

The problem is that Netstumbler and Hopper do NOT show wireless clients. For that you need a promiscuous or monitor mode driver for your unspecified hardware. That means either spending money for one, or switching to Linux using Kismet.

It's not as bad as it might sound as there are "Live CD's" that boot Linux and offer Kismet on a simulated Windoze desktop. I suggest:

Be sure your wireless device is supported before blundering onwards. There are quite a few other hacker tools that might be worth trying. (Welcome to the dark side).

Then you don't need "802.11b compatibility" in the router. Turn it off in the router.

"NotMe" hath wroth:

Can I pass on this? I don't want to post a "Jeff's Favorites" list. Too much work and too easy to misinterpret. Basically, I like Cisco, Sonicwall, 3com, and various wireless switch vendors.

It's not a "wireless router". It's a "wireless client ethernet bridge" (or something like that). List of suitable candidates at:

Note that not all of those listed have a wireless client mode. Some are point to point bridges only, and are rather clumsy to use for a roving RV. Check the data sheet first.

I'm jealous. However, I prefer Radio Mobile:

Acutally, you can just type devmgmt.msc in the run line. You don't need the CMD. Start > Run > devmgmt.msc. You can even create a shortcut on the desktop pointing directly to devmgmt.msc.

Gordon Montgomery Living Scriptures, Inc snipped-for-privacy@lsi.com (anti spam - replace lsi with livingscriptures) (801) 627-2000

Is there any significant difference between Buffalo WHR-HP-G54 and WHR-G54S? The "HP" model seems to be not available in Australia

Kind regards Mark