RE: Problem with WEP in one direction!?

> How did you put the enterasys into this mode, by
> 	iwconfig eth2 mode managed

No, I actually have it configured for master mode.  I have an entry in
/etc/pcmcia/wireless.opts which defines the parameters:

  # Enterasys/Cabletron RoamAbout
  *,*,*,*)
        INFO="Roamabout"
        MODE="Master"
        ESSID="rebel-it"
        NWID="donut"
        CHANNEL=10
        KEY="s:SomeStringHere"
        ;;

But if I try to set it manually, with "iwconfig eth2 mode managed" it fails
with:

  Error for wireless request "Set Mode" (8B06) :
    SET failed on device eth2 ; Invalid argument.

So it's probably just set to managed by default, or possibly from
/etc/sysconfig/network-scripts/ifcfg-eth2 which contains 'MODE=managed'.

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?

> > So again, everything seems OK to this point.
>
> Except that the bssid in the syslog (02:00:c1:91:d0:40) does not match the
> one iwconfig reports later (02:00:03:75:76:17).

It's quite possible that some mode changes took place between capturing the
iwconfig output and the syslog.  Trying this again now, I see the output of
iwconfig and the syslog show matching bssids.

> Try with the arping:
> - switch off encryption on the Atmel side only

Yup, that allows me to ping.  So it's as if the enterasys side is not
encrypting. :-0

> - set Atmel side to restricted encryption ("iwconfig wlan0 encr on restr"
>   (?)). With your "open" setting you allow the device to process
>   received unencrypted data. But it will always transmit encrypted.

With this setting (restr), the arp entry doesn't appear on the atmel side
when I try to ping from the enterasys side.  Again, this suggests that the
enterasys is not encrypting, and in this case the atmel is rejecting.

> Maybe the enterasys does not encrypt/decrypt ? Are you sure, that a simple
> "iwconfig encr on" does turn WEP on for the enterasys (it does for the
> Atmel driver, which restarts the device after that cmd)?

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.

I'm flabbergasted that this is the case.  Unbelievable that I've been
operating for some time under the misapprehension that the link was using
WEP encryption.  Fortunately I haven't been relying on this, and have only
allowed ssh or IPSec traffic to pass over the link.  But I'm a bit confused
that the two enterasys cards can only talk to each other when the key is the
same on both.

I'll have to track down the issues with the wavelan2_cs driver.  Thanks very
much for your help (and patience).

Cheers
Jeremy