2009-07-29 11:11:11

by Holger Schurig

[permalink] [raw]
Subject: BUG: ifdown doesn't notify cfg80211

# iw dev eth1 connect -w MNHS key 0:11111
eth1 (phy #0): connected to 00:13:19:80:da:30
# ifconfig eth1 down
# iw dev eth1 connect -w MNHS key 0:11111
# ifconfig eth1 down
# ifconfig eth1 up
# iw dev eth1 connect -w MNHS key 0:11111
command failed: Operation already in progress (-114)


Only when I do "iw dev eth1 disconnect" can I connect again.
Shouldn't downing the interface clear the "I'm connected" state?

--
http://www.holgerschurig.de


2009-07-29 13:00:16

by Holger Schurig

[permalink] [raw]
Subject: Re: BUG: ifdown doesn't notify cfg80211

> # iw dev eth1 connect -w MNHS key 0:11111
> eth1 (phy #0): connected to 00:13:19:80:da:30
> # ifconfig eth1 down
> # ifconfig eth1 up
> # iw dev eth1 connect -w MNHS key 0:11111
> command failed: Operation already in progress (-114)

As Johannes pointed out on IRC, this happens only if you used

iwconfig eth1 key s:11111
iwconfig eth1 essid MNHS

previously on the device. Seems that the CFG80211-configuration
doesn't delete the WEXT-configuration remnants. And as soon as
you "ifup" the device, it starts associating based on old WEXT
data, resulting in the busy.

--
http://www.holgerschurig.de

2009-07-29 11:26:27

by Holger Schurig

[permalink] [raw]
Subject: Re: BUG: ifdown doesn't notify cfg80211

On Wednesday 29 July 2009 13:10:50 Holger Schurig wrote:
> # iw dev eth1 connect -w MNHS key 0:11111
> eth1 (phy #0): connected to 00:13:19:80:da:30
> # ifconfig eth1 down
> # iw dev eth1 connect -w MNHS key 0:11111
> # ifconfig eth1 down

Oops, a copy'n'paste error. I didn't send those two lines twice
at this point. The correct sequence I did:

# iw dev eth1 connect -w MNHS key 0:11111
eth1 (phy #0): connected to 00:13:19:80:da:30
# ifconfig eth1 down
# ifconfig eth1 up
# iw dev eth1 connect -w MNHS key 0:11111
command failed: Operation already in progress (-114)

--
http://www.holgerschurig.de