From: "Lars Ericsson" <Lars_Ericsson@telia.com>
To: "'Ivo van Doorn'" <ivdoorn@gmail.com>
Cc: <rt2400-devel@lists.sourceforge.net>,
<linux-wireless@vger.kernel.org>, <hostap@lists.shmoo.com>
Subject: RE: [Rt2400-devel] mac80211 / rt2x00 / rt61 and adhoc status
Date: Sun, 17 Aug 2008 12:25:09 +0200 [thread overview]
Message-ID: <059301c90053$86f182f0$0b3ca8c0@gotws1589> (raw)
In-Reply-To: <200808171158.25501.IvDoorn@gmail.com>
> On Sunday 17 August 2008, Lars Ericsson wrote:
> > > >
> > > > Have tried using the wpa_supplicant and got the -EBUSY from
> > > > ieee80211_ioctl_siwmode().
> > >
> > > As usual: The interface must be down when changing working mode.
> > >
> >
> > The initial mode is 2. I do not know the source of that
> mode, might be a
> > default.
> > <7>[ 85.713782] LaE: ieee80211_ioctl_siwmode: type=2,
> sdata->vif.type=2
>
> that is managed mode.
>
> > Between 85.713698 and 85.821832 device is opened
> (1=netif_running(dev))
> > <7>[ 85.713698] LaE: ieee80211_ioctl_siwmode: 0=netif_running(dev)
> > <7>[ 85.713752] LaE: ieee80211_ioctl_siwmode: mode=2
> > <7>[ 85.713782] LaE: ieee80211_ioctl_siwmode: type=2,
> sdata->vif.type=2
> > <6>[ 85.713938] phy0 -> rt2x00lib_request_firmware: Info - Loading
> > firmware file 'rt2561s.bin'.
> > <6>[ 85.724265] firmware: requesting rt2561s.bin
> > <6>[ 85.779042] phy0 -> rt2x00lib_request_firmware: Info
> - Firmware
> > detected - version: 0.8.
> > <7>[ 85.821654] LaE: ieee80211_ioctl_giwrange: enter;
> > <7>[ 85.821832] LaE: ieee80211_ioctl_giwrange:
> 1=netif_running(dev)
> >
> > When wpa supplicant set the adhoc mode=1/type=3 the device
> is running and
> > fails
>
> to quota myself: "The interface must be down when changing
> working mode."
OK, I got that ;)
>
> > <7>[ 85.947991] LaE: ieee80211_ioctl_siwmode: mode=1
> > <7>[ 85.948134] LaE: ieee80211_ioctl_siwmode: type=3,
> sdata->vif.type=2
> > <7>[ 85.948433] LaE: ieee80211_ioctl_siwmode: type=3
> >
> > My work around was to ignore this situation and continue
> the mode change.
>
> that is not correct, as I've stated already: The interface
> must be down when changing working mode.
>
I have to check if it is the mac80211 or the wpa_supplicant that is doing
wrong.
> > > > Two tests cases, but same behaviour:
> > > > 1) Linx.git: 2.6.26 and wpa_supplicant 0.5.9
> > > > 2) rt2x00.git: Version 2.2.0 and wpa_supplicant 0.5.9
> > >
> > > Are any beacons going out? Is there anything in the logs which
> > > indicates what is happening?
> > >
> >
> > As you can se in the trace below, the configuration
> proceeds and the adhoc
> > is created.
> > The warnon might give some clues.
>
> So how about those beacons? are they getting out?
>
I will check that and come back as soon as the first issue is sorted out.
I might broke some logic when I was trying to change mode for an open
interface.
/Lars
next prev parent reply other threads:[~2008-08-17 10:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-17 5:36 mac80211 / rt2x00 / rt61 and adhoc status Lars Ericsson
2008-08-17 9:05 ` [Rt2400-devel] " Ivo van Doorn
2008-08-17 9:54 ` Lars Ericsson
2008-08-17 9:58 ` Ivo van Doorn
2008-08-17 10:25 ` Lars Ericsson [this message]
2008-08-17 14:02 ` Lars Ericsson
2008-08-17 20:42 ` Lars Ericsson
2008-08-18 14:34 ` Dan Williams
2008-08-18 19:27 ` Lars Ericsson
2008-08-18 19:35 ` Dan Williams
2008-08-19 17:38 ` Jouni Malinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='059301c90053$86f182f0$0b3ca8c0@gotws1589' \
--to=lars_ericsson@telia.com \
--cc=hostap@lists.shmoo.com \
--cc=ivdoorn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rt2400-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox