RE: Problem with WEP in one direction!?
Joerg Albert <[email protected]>
| Newsgroups | gmane.linux.drivers.at76c503a.user |
|---|---|
| Message-ID | <Pine.LNX.4.56.0402270049390.675@invb> |
Hi,
On Thu, 26 Feb 2004, Jeremy Laidman wrote:
> > 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'.
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.
> 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.
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)
> > 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.
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.
/Jörg