Inconsistent Interfaces

[prev] [thread] [next] [lurker] [Date index for 2003/12/10]

From: Phil!Gregory
Subject: Inconsistent Interfaces
Date: 17:46 on 10 Dec 2003
I'm setting things in the firmware of a wireless device that was basically
dropped in my lap.  It's a BreezeNET AP-10, with firmware revision 4.4.1.
Let's take a look at my commands and its responses (paraphrased for
effect).

me: Please use 0x00DEADBEEF in WEP key slot #1 (out of four)
it: Sure thing!
me: Okay, now use WEP #1 as your default.
it: Done!
me: Good, good.  Since the configuration's done, activate WEP.
it: No, I don't support that!  Ha, ha!
<sound of me going off to find a sledgehammer>

If a particular feature of your program is unavailable (especially if it
will never be available for a given software version[0]), would it be too
much work to *not have configuration options for that feature*?

And a minor annoyance is that I can enable SNMP traps from the console
setup, but I have to set the destination host for them through SNMP
management, which is annoying due to the topology of out network.


[0] Apparently, WEP must be purchased separately for this device and
    whoever bought it originally didn't go for it.  (Tangentially, I'm
    aware of WEP's weaknesses, but it keeps the casual browser out.
    (IPSec routers bordering the wireless connection keep everyone else
    out.))

-- 
...computer contrarian of the first order... / http://aperiodic.net/phil/
PGP: 026A27F2  print: D200 5BDB FC4B B24A 9248  9F7A 4322 2D22 026A 27F2
--- --
  "Who do you think you are, Zaphod Beebelbrox?"
  "Count the heads."
---- --- --

Generated at 14:02 on 01 Jul 2004 by mariachi 0.52