Frazer Jolly Goodfellow <no-(E-Mail Removed)> hath wroth:
>>>> Get one, you will need it to configure the router. You simply
>>>> cannot do it over the wireless link.
>>>Nonsense, it's dead easy.
>> Really?
>Yes.
I beg to slightly differ.
>I've never encountered such a crappily designed beast.
Welcome to the wonderful world of bottom of the line routers.
Fast, cheap, reliable; pick two.
The industry and customers seem to have selected the first two.
>Every
>router/access point I've configured has a two-stage process: set
>the configuration changes you intend to make then click a single
>Save Settings or similar button to actually implement the changes.
You must be used to the real Cisco routers and IOS.
Tweak the settings from the command line of upload a page full of
commands and settings. When it's all working, run:
copy running-config startup-config
Well, that's the way I also like to do it. Same with flash upgrades,
where the router has twice the flash memory as required and can switch
between the old and new flash images with a single command.
>3 Tell the router to implement the changes, which will drop the and
>restart wireless link.
That's where the problem starts. The client sends the settings to the
router (via wireless) as a very long URL. It doesn't just send the
item that was changed. It sends the entire page.
The problem is that that router parses the long list of settings in
the order in which they are received. If the change in SSID or
WEP/WPA key is early in the setup string, the router may disconnect
the wireless link or even initiate a soft reboot before it is done
parsing the subsequent settings. A properly designed system would
store the entire line before executing any changes, but that's not
what seems to be happening. I've been meaning to dive into the WRT54G
source code and see if that's really the way it works.
>[this assumes the router has wireless switched on by default, with
>no encryption or a default encryption key]
See one of my assorted previous rants on the idiocy of routers being
shipped insecure and wide open by default. Your proceedure should
work with what I guess to be perhaps 90% of the routers, firmware
mutations, and situations, and is probably safe. I do it something
like that myself when I feel brave (or lazy). However, when I can't
afford to make a mistake (i.e. wireless access point is sitting on a
rooftop or a tower), I do it via ethernet only.
--
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