RE: Problem with WEP in one direction!?

> > But if I try to set it manually, with "iwconfig eth2 mode
> managed" it fails
....
> This is confusing, if it really is in master mode, it should display it.
> If it is in managed mode, it should accept the mode parameter.

Sorry, I meant "iwconfig eth2 mode master" fails.  Managed seems to work
fine.

> > I think from what you're saying, I should be setting both sides
> to "ad-hoc",
> > because neither support "master".  Is that correct?  If I try this, it
> > doesn't work.  If I want 3 nodes to be able to talk to each other, am I
> > supposed to have them all ad-hoc or should only one (eg one
> that's always
> > on) be set to ad-hoc and the others set to managed?
>
> adhoc + managed won't work. Either set all into adhoc mode or the
> Enterasys into master mode (if it is working correctly) and the others in
> managed mode. The Atmel device doesn't support master mode due to it's
> limited firmware.

I don't think the standard enterasys firmware supports master mode.  Google
shows me some references to HermesAP, but needs a firmware change to do it.
I doubt what I'm using supports this.

Assuming enterasys doesn't support master mode, ad-hoc all around is my only
choice.  However, I've never been able to get the 2 enterasys cards to talk
to each other when the linux one was in ad-hoc mode.  When it's in managed
mode, all is fine.  In this case, the other end was a win2k box running in
ad-hoc mode.  Perhaps the wavelan2_cs driver is acting strangely?  Or
perhaps there's an AP around that I don't know about?

> managed  = connect to an AP
> master = act as an AP
> adhoc = build your own IBSS, can be joined by other clients in adhoc mode
>         (not in managed)

Thanks for this concise summary of how it works.  I've been looking for
simple documentation on all these modes, and haven't been able to find
anything useful AND concise.  It's all becoming clear to me now though...

> > I've rebooted the enterasys, then done "iwconfig eth2" and it shows
> > encryption key.  Immediately after this I see the same
> symptoms.  That is, I
> > can ping from the atmel with enc=off and with an encryption key on the
> > enterasys.
>
> As I said before, some cards need a "ifconfig .. down; ifconfig .. up"
> _after_ the WEP key is set to activate the settings from iwconfig.
> iwconfig sometimes displays driver internal parameter, not the current
> state of the device.

Ah, I see.  So:
  1) reboot
  2) set key (during boot process)
isn't enough, I also need
  3) down/up the device

I'll try that.

Cheers
Jeremy