NetBSD Problem Report #18520
Received: (qmail 15130 invoked by uid 605); 3 Oct 2002 15:11:21 -0000
Message-Id: <200210031443.g93Ehb700341@night-revel.duskware.de>
Date: Thu, 3 Oct 2002 16:43:37 +0200 (CEST)
From: Martin Husemann <martin@duskware.de>
Sender: gnats-bugs-owner@netbsd.org
Reply-To: martin@duskware.de
To: gnats-bugs@gnats.netbsd.org
Subject: wi driver stopped working
X-Send-Pr-Version: 3.95
>Number: 18520
>Category: kern
>Synopsis: wi driver stopped working
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: onoe
>State: closed
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu Oct 03 15:12:01 +0000 2002
>Closed-Date: Tue Oct 08 20:58:19 +0000 2002
>Last-Modified: Sat Apr 29 08:49:38 +0000 2006
>Originator: Martin Husemann
>Release: NetBSD 1.6I
>Organization:
>Environment:
System: NetBSD night-revel.duskware.de 1.6I NetBSD 1.6I (REVEL) #2: Thu Oct 3 12:19:38 MEST 2002 martin@night-porter.duskware.de:/usr/src/sys/arch/i386/compile/REVEL i386
Architecture: i386
Machine: i386
>Description:
After a kernel update to -current as of a few hours ago, the wi driver stopped
working completely.
I use this card:
wi0 at pcmcia0 function 0: Lucent Technologies, WaveLAN/IEEE, Version 01.01
wi0: 802.11 address 00:02:2d:21:0f:64
wi0: using Lucent Technologies, WaveLAN/IEEE
wi0: Lucent Firmware: Station (8.10.1)
wi0: supported rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
and this /etc/ifconfig.wi0:
192.168.XXX.X down
nwid "MartinAtHome" nwkey 1:XXXXX,XXXXX,XXXXX,XXXXX mediaopt adhoc
up
Peer is a system running a few days older -current and using the same kind of
card.
At boot time, the card is initialized, but the blinkenlights do not turn on.
Ifconfig shows UP and RUNNING, but that's not true ;-)
When I ifconfig down/up the card, the lights start blinking, but the card is
not able to communicate with the peer (driven by a slightly older version
of the wi driver).
Oh well, back to ethernet.
>How-To-Repeat:
Use a lucent silver card.
>Fix:
n/a
>Release-Note:
>Audit-Trail:
From: Atsushi Onoe <onoe@netbsd.org>
To: gnats-bugs@gnats.netbsd.org
Cc:
Subject: pr/18520 CVS commit: syssrc/sys/dev/ic
Date: Fri, 4 Oct 2002 01:32:39 +0300 (EEST)
Module Name: syssrc
Committed By: onoe
Date: Thu Oct 3 22:32:39 UTC 2002
Modified Files:
syssrc/sys/dev/ic: wi.c
Log Message:
Set IEEE80211_F_IBSSON before test in wi_init() to set CREATE_IBSS
correctly for Lucent firmware to work with IBSS mode.
PR 18520
To generate a diff of this commit:
cvs rdiff -r1.96 -r1.97 syssrc/sys/dev/ic/wi.c
Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.
From: Atsushi Onoe <onoe@sm.sony.co.jp>
To: martin@duskware.de
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: pr/18520 CVS commit: syssrc/sys/dev/ic
Date: Fri, 4 Oct 2002 11:09:53 +0900 (JST)
> Cool, this solves part of the problem (blinkenlights work right away).
>
> The cards still don't communicate though. Strangely ifconfig shows adhoc mode,
> while wiconfig shows port type = 1 (BSS). Shouldn't that be 3 (adhoc)?
No. The port type 3 is another mode which is lucent proprietary adhoc demo
mode.
> An explicit "wiconfig wi0 -p 3" fixes it - comunication works again.
> Shouldn't that be implied by "ifconfig ... mediaopt adhoc" ?
It looks strange. It configures different mode and cannot communicate
normal IBSS mode.
Perhaps your peer system is running older kernel? There is another
HEADS UP message I've sent on Auguest, which shows the meaning of 'adhoc'
is changed for wi driver.
old behavior: mediaopt adhoc lucent proprietary demo mode
wiconfig -c 1, without mediaopt
standard IBSS mode
new behavior: mediaopt adhoc standard IBSS mode
mediaopt adhoc,flag0 lucent proprietary demo mode
So, if you can communicate by "wiconfig wi0 -p 3", then I guess your
peer is running in lucent proprietary demo mode. If so, you could
configure by
ifconfig wi0 mediaopt adhoc,flag0
It is documented in wi(4) and ifmedia(4)
Atsushi Onoe
Responsible-Changed-From-To: kern-bug-people->onoe
Responsible-Changed-By: onoe
Responsible-Changed-When: Fri Oct 4 01:02:21 PDT 2002
Responsible-Changed-Why:
I'll take care of it.
From: Atsushi Onoe <onoe@sm.sony.co.jp>
To: martin@duskware.de
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: pr/18520 CVS commit: syssrc/sys/dev/ic
Date: Fri, 4 Oct 2002 17:13:44 +0900 (JST)
Thanks for update.
Could you please confirm your revision of wi.c is at least 1.97, and
send the output of 'wiconfig' when it is NOT working?
And please Cc: gnats-bugs@gnats.netbsd.org so that we can trace your
report later.
Atsushi Onoe
> On Fri, Oct 04, 2002 at 11:09:53AM +0900, Atsushi Onoe wrote:
>
> > Perhaps your peer system is running older kernel? There is another
> > HEADS UP message I've sent on Auguest, which shows the meaning of 'adhoc'
> > is changed for wi driver.
>
> No, I updated it's kernel with the same source.
>
> The config on the peer has (forgot to replace that with ifconfig)
> still a wiconfig based /etc/ifocnfig.wi0 - but a mediaopt adhoc later, so
> that overrides the -p 3:
>
> ---8<---
> 192.168.XXX.X down
> ! /usr/sbin/wiconfig wi0 -p 3 -c 1 -n "XXXXXX" -q "XXXXXX" -s "XXXXX"
> mediaopt adhoc
> nwkey 1:XXXXX,XXXXX,XXXXX,XXXXX
> up
> --->8---
>
> > So, if you can communicate by "wiconfig wi0 -p 3", then I guess your
> > peer is running in lucent proprietary demo mode.
>
> No, I could only communicate after I did "wiconfig wi0 -p 3" on *both*
> machines. I just tested the -p 1 mode again. I started with a working setup,
> both machines using port type 3. I then did "wiconfig wi0 -p 1" on both and
> it stopped working. Switching back to 3 on both made it working again.
>
> The output of wiconfig now (after it's working again) on the peer is:
>
> NIC serial number: [ 01UT12444645 ]
> Station name: [ XXXXXXXXXXXX ]
> SSID for IBSS creation: [ XXXXXXXXXXXX ]
> Current netname (SSID): [ XXXXXXXXXXXX ]
> Desired netname (SSID): [ XXXXXXXXXXXX ]
> Current BSSID: [ 00:00:00:00:00:00 ]
> Channel list: [ 1 2 3 4 5 6 7 8 9 10 11 12 13 ]
> IBSS channel: [ 3 ]
> Current channel: [ 3 ]
> Comms quality/signal/noise: [ 0 27 27 ]
> Promiscuous mode: [ Off ]
> Port type (1=BSS, 3=ad-hoc): [ 3 ]
> MAC address: [ 00:02:2d:21:10:7b ]
> TX rate (selection): [ 11 ]
> TX rate (actual speed): [ 2 ]
> Beacon Interval (current) [msec]: [ 100 ]
> Maximum data length: [ 2304 ]
> RTS/CTS handshake threshold: [ 2347 ]
> Create IBSS: [ Off ]
> Microwave oven robustness: [ 0 ]
> Roaming mode(1:firm,3:disable): [ 1 ]
> Access point density: [ 1 ]
> Power Mgmt (1=on, 0=off): [ 0 ]
> Max sleep time (msec): [ 100 ]
> WEP encryption: [ On ]
> Authentication type
> (1=OpenSys, 2=Shared Key): [ ]
> TX encryption key: [ 1 ]
> Encryption keys: [ XXXXX ][ XXXXX ][ XXXXX ][ XXXXX ]
>
> when switching to -p 1 the output differs only in the following:
>
> +Current BSSID: [ 44:44:44:44:44:44 ]
> +Current channel: [ 2 ]
> +Port type (1=BSS, 3=ad-hoc): [ 1 ]
>
> So this boils down to : mediaopt adhoc,flag0 works, but mediaopt adhoc does
> not work at all.
>
> Martin
>
From: Martin Husemann <martin@duskware.de>
To: Atsushi Onoe <onoe@sm.sony.co.jp>
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: pr/18520 CVS commit: syssrc/sys/dev/ic
Date: Fri, 4 Oct 2002 11:34:29 +0200
Ok, I did "ifconfig wi0 mediaopt adhoc" on both machines and it stopped
working.
ident /netbsd | fgrep wi.c says:
$NetBSD: wi.c,v 1.97 2002/10/03 22:32:37 onoe Exp $
wiconfig wi0 says:
NIC serial number: [ 01UT12444645 ]
Station name: [ XXXXXXXXXXXX ]
SSID for IBSS creation: [ XXXXXXXXXXXX ]
Current netname (SSID): [ XXXXXXXXXXXX ]
Desired netname (SSID): [ XXXXXXXXXXXX ]
Current BSSID: [ 00:00:00:00:00:00 ]
Channel list: [ 1 2 3 4 5 6 7 8 9 10 11 12 13 ]
IBSS channel: [ 3 ]
Current channel: [ 3 ]
Comms quality/signal/noise: [ 0 27 27 ]
Promiscuous mode: [ Off ]
Port type (1=BSS, 3=ad-hoc): [ 3 ]
MAC address: [ 00:02:2d:21:10:7b ]
TX rate (selection): [ 11 ]
TX rate (actual speed): [ 2 ]
Beacon Interval (current) [msec]: [ 100 ]
Maximum data length: [ 2304 ]
RTS/CTS handshake threshold: [ 2347 ]
Create IBSS: [ Off ]
Microwave oven robustness: [ 0 ]
Roaming mode(1:firm,3:disable): [ 1 ]
Access point density: [ 1 ]
Power Mgmt (1=on, 0=off): [ 0 ]
Max sleep time (msec): [ 100 ]
WEP encryption: [ On ]
Authentication type
(1=OpenSys, 2=Shared Key): [ ]
TX encryption key: [ 1 ]
Encryption keys: [ XXXXX ][ XXXXX ][ XXXXX ][ XXXXX ]
On the other machine I get basically the same, but "port type" is 1 - duh.
(I did "ifconfig wi0 mediaopt adhoc" on both machines, so expected the same
result on both - maybe the "wiconfig wi0 -p 3" I used before on one machine
for testing is sticky?)
Forcing it to port type 1 does not help (still does not work). This is
what ifconfig and wiconfig say in this mode:
wi0: flags=88e3<UP,BROADCAST,NOTRAILERS,RUNNING,NOARP,SIMPLEX,MULTICAST> mtu 1500
nwid XXXXXXXXXXXX nwkey 1:XXXXX,XXXXX,XXXXX,XXXXX
powersave off
bssid 00:00:00:00:00:00 chan 65535
address: 00:02:2d:21:10:7b
media: IEEE802.11 DS11 adhoc (DS11)
status: no network
inet 192.168.XXX.X netmask 0xffffff00 broadcast 192.168.XXX.255
NIC serial number: [ 01UT12444645 ]
Station name: [ XXXXXXXXXXXX ]
SSID for IBSS creation: [ XXXXXXXXXXXX ]
Current netname (SSID): [ XXXXXXXXXXXX ]
Desired netname (SSID): [ XXXXXXXXXXXX ]
Current BSSID: [ 44:44:44:44:44:44 ]
Channel list: [ 1 2 3 4 5 6 7 8 9 10 11 12 13 ]
IBSS channel: [ 3 ]
Current channel: [ 3 ]
Comms quality/signal/noise: [ 0 27 27 ]
Promiscuous mode: [ Off ]
Port type (1=BSS, 3=ad-hoc): [ 1 ]
MAC address: [ 00:02:2d:21:10:7b ]
TX rate (selection): [ 11 ]
TX rate (actual speed): [ 2 ]
Beacon Interval (current) [msec]: [ 100 ]
Maximum data length: [ 2304 ]
RTS/CTS handshake threshold: [ 2347 ]
Create IBSS: [ Off ]
Microwave oven robustness: [ 0 ]
Roaming mode(1:firm,3:disable): [ 1 ]
Access point density: [ 1 ]
Power Mgmt (1=on, 0=off): [ 0 ]
Max sleep time (msec): [ 100 ]
WEP encryption: [ On ]
Authentication type
(1=OpenSys, 2=Shared Key): [ ]
TX encryption key: [ 1 ]
Encryption keys: [ XXXXX ][ XXXXX ][ XXXXX ][ XXXXX ]
From: Atsushi Onoe <onoe@sm.sony.co.jp>
To: martin@duskware.de
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: pr/18520 CVS commit: syssrc/sys/dev/ic
Date: Sun, 6 Oct 2002 10:49:19 +0900 (JST)
I've updated the firmware of my Orinoco card to 8.10.1, which is the
exact same version of yours, but still cannot reproduce your problem,
i.e. it works fine.
What I did are,
1. Insert the card, it is attached to wi1, since my PC has a wi0 inside.
wi1 at pcmcia0 function 0: Lucent Technologies, WaveLAN/IEEE, Version 01.01
wi1: 802.11 address 00:02:2d:05:70:4c
wi1: using Lucent Technologies, WaveLAN/IEEE
wi1: Lucent Firmware: Station (8.10.1)
wi1: supported rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
2. ifconfig wi1 192.168.1.1 down
wiconfig wi1 -p 3 -c 1 -n NWID -q NWID -s STA1
ifconfig wi1 mediaopt adhoc
ifconfig wi1 nwkey 1:aaaaa,aaaaa,aaaaa,aaaaa
ifconfig wi1 up
wiconfig wi1 says:
NIC serial number: [ 00UT43330376 ]
Station name: [ STA1 ]
SSID for IBSS creation: [ NWID ]
Current netname (SSID): [ NWID ]
Desired netname (SSID): [ NWID ]
Current BSSID: [ 02:f0:6f:f7:32:be ]
Channel list: [ 1 2 3 4 5 6 7 8 9 10 11 ]
IBSS channel: [ 10 ]
Current channel: [ 10 ]
Comms quality/signal/noise: [ 0 27 27 ]
Promiscuous mode: [ Off ]
Port type (1=BSS, 3=ad-hoc): [ 1 ]
MAC address: [ 00:02:2d:05:70:4c ]
TX rate (selection): [ 3 ]
TX rate (actual speed): [ 2 ]
Beacon Interval (current) [msec]: [ 100 ]
Maximum data length: [ 2304 ]
RTS/CTS handshake threshold: [ 2347 ]
Create IBSS: [ On ]
Microwave oven robustness: [ 0 ]
Roaming mode(1:firm,3:disable): [ 1 ]
Access point density: [ 1 ]
Power Mgmt (1=on, 0=off): [ 0 ]
Max sleep time (msec): [ 100 ]
WEP encryption: [ On ]
Authentication type
(1=OpenSys, 2=Shared Key): [ ]
TX encryption key: [ 1 ]
Encryption keys: [ aaaaa ][ aaaaa ][ aaaaa ][ aaaaa ]
The differences from your output are:
Port type: It should be 1 for Lucent firmware.
Create IBSS: It should be On for Lucent firmware.
IBSS channel: it doesn't matter, the default value is changed
to 10 for recent card.
TX rate (selection): It doesn't matter for communication,
But unless specified, it should be 3 (auto)
for all the card I know.
And the output of ifconfig shows you have another configuration to
configure TX rate, and the configuration is force changed by
wiconfig *after* ifconfig mediaopt adhoc.
> wi0: flags=88e3<UP,BROADCAST,NOTRAILERS,RUNNING,NOARP,SIMPLEX,MULTICAST> mtu 1500
> nwid XXXXXXXXXXXX nwkey 1:XXXXX,XXXXX,XXXXX,XXXXX
> powersave off
> bssid 00:00:00:00:00:00 chan 65535
> address: 00:02:2d:21:10:7b
> media: IEEE802.11 DS11 adhoc (DS11)
> status: no network
> inet 192.168.XXX.X netmask 0xffffff00 broadcast 192.168.XXX.255
So I guess you have another configuration anywhere, at least to specify
TX rate to 11Mbps, conjunction with wiconfig -p 1 line.
Note that wiconfig -p 1 after ifconfig mediaopt adhoc will change the
operation mode of lucent card back to normal infrastructure mode, not
a IBSS mode. So this will be the reason why you cannot operate in
IBSS mode. Please confirm there is another configuration using wiconfig.
The incompatibility of wiconfig would be matter, since the detail such as
configuration value and the order of the option is vary among the firmware
revision and type.
Instead of emulating all the revision of firmware, we may deprecate the
use of wiconfig...
Atsushi Onoe
From: Martin Husemann <martin@duskware.de>
To: Atsushi Onoe <onoe@sm.sony.co.jp>
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: pr/18520 CVS commit: syssrc/sys/dev/ic
Date: Sun, 6 Oct 2002 11:13:34 +0200
On Sun, Oct 06, 2002 at 10:49:19AM +0900, Atsushi Onoe wrote:
> What I did are,
> 2. ifconfig wi1 192.168.1.1 down
> wiconfig wi1 -p 3 -c 1 -n NWID -q NWID -s STA1
> ifconfig wi1 mediaopt adhoc
> ifconfig wi1 nwkey 1:aaaaa,aaaaa,aaaaa,aaaaa
> ifconfig wi1 up
That's pretty much what my /etc/ifconfig.wi0 has (only the order of -c and
-p on are exchanged, but I hope that does not matter). The output I send
you was after lots of experiments with various settings, that's where the
locked TX rate came from.
I've just updated that machine completely to -current (including userland) and
rebooted, the settings now (without any manual fidling with the wi0) are:
NIC serial number: [ 01UT12444645 ]
Station name: [ STATIONID ]
SSID for IBSS creation: [ NWID ]
Current netname (SSID): [ NWID ]
Desired netname (SSID): [ NWID ]
Current BSSID: [ 02:33:30:10:0d:4a ]
Channel list: [ 1 2 3 4 5 6 7 8 9 10 11 12 13 ]
IBSS channel: [ 3 ]
Current channel: [ 3 ]
Comms quality/signal/noise: [ 0 27 27 ]
Promiscuous mode: [ Off ]
Port type (1=BSS, 3=ad-hoc): [ 1 ]
MAC address: [ 00:02:2d:21:10:7b ]
TX rate (selection): [ 3 ]
TX rate (actual speed): [ 2 ]
Beacon Interval (current) [msec]: [ 100 ]
Maximum data length: [ 2304 ]
RTS/CTS handshake threshold: [ 2347 ]
Create IBSS: [ On ]
Microwave oven robustness: [ 0 ]
Roaming mode(1:firm,3:disable): [ 1 ]
Access point density: [ 1 ]
Power Mgmt (1=on, 0=off): [ 0 ]
Max sleep time (msec): [ 100 ]
WEP encryption: [ On ]
Authentication type
(1=OpenSys, 2=Shared Key): [ ]
TX encryption key: [ 1 ]
Encryption keys: [ XXXXX ][ XXXXX ][ XXXXX ][ XXXXX ]
and
wi0: flags=88e3<UP,BROADCAST,NOTRAILERS,RUNNING,NOARP,SIMPLEX,MULTICAST> mtu 1500
nwid NWID nwkey 1:XXXXX,XXXXX,XXXXX,XXXXX
powersave off
bssid 02:74:5c:57:61:0d chan 3
address: 00:02:2d:21:10:7b
media: IEEE802.11 autoselect adhoc
status: active
inet 192.168.XXX.X netmask 0xffffff00 broadcast 192.168.XXX.255
And (just to be sure to mention it) it still does not work.
> Instead of emulating all the revision of firmware, we may deprecate the
> use of wiconfig...
How do I get the settings above with only ifconfig? Just set nwid and nwkey?
How do I set the station name? (Or don't I just do that? It's shown in the
windows monitoring software and looked pretty usefull to me)
Martin
From: Atsushi Onoe <onoe@sm.sony.co.jp>
To: martin@duskware.de
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: pr/18520 CVS commit: syssrc/sys/dev/ic
Date: Mon, 7 Oct 2002 08:26:33 +0900 (JST)
Thanks a lot!
I've finally got the problem. I'll fix the problem later today.
> That's pretty much what my /etc/ifconfig.wi0 has (only the order of -c and
> -p on are exchanged, but I hope that does not matter). The output I send
> you was after lots of experiments with various settings, that's where the
> locked TX rate came from.
Because of insufficient emulation of the firmware, the order of option of
wiconfig DOES matter. But the next 'mediaopt adhoc' should override
-p and -c option, for this case.
> I've just updated that machine completely to -current (including userland) and
> rebooted, the settings now (without any manual fidling with the wi0) are:
OK, it is just what I got and seems running, except
> Current BSSID: [ 02:33:30:10:0d:4a ]
> wi0: flags=88e3<UP,BROADCAST,NOTRAILERS,RUNNING,NOARP,SIMPLEX,MULTICAST> mtu 1500
> bssid 02:74:5c:57:61:0d chan 3
These BSSID information must match, otherwise the communication fails,
which is just you got. It seems that the recent lucent firmware (8.10.1
and may be later) generates random BSSID and keep changing it every 10
seconds. So if there is no IBSS created yet, and a next station doesn't
join the IBSS within 10 seconds, there is mis-match the bssid between
driver (for normal data packet) and firmware (for beacon). That is the
reason for communication failure.
> How do I get the settings above with only ifconfig? Just set nwid and nwkey?
Exactly.
> How do I set the station name? (Or don't I just do that? It's shown in the
> windows monitoring software and looked pretty usefull to me)
Hmm, it is proprietary feature of wi related cards. You will continue to
use wiconfig just for the purpose, i.e. the option which cannot do via
ifconfig.
Atsushi Onoe
From: Atsushi Onoe <onoe@netbsd.org>
To: gnats-bugs@gnats.netbsd.org
Cc:
Subject: pr/18520 CVS commit: syssrc/sys/dev/ic
Date: Mon, 7 Oct 2002 14:01:54 +0300 (EEST)
Module Name: syssrc
Committed By: onoe
Date: Mon Oct 7 11:01:53 UTC 2002
Modified Files:
syssrc/sys/dev/ic: wi.c
Log Message:
Update BSSID at every CONNECTED LINK_STAT notification in IBSS mode,
since it can be updated by IBSS merge. Also the lucent firmware 8.10.1
changes random generated bssid every 10 seconds in IBSS creation enable.
PR 18520
To generate a diff of this commit:
cvs rdiff -r1.98 -r1.99 syssrc/sys/dev/ic/wi.c
Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.
From: Atsushi Onoe <onoe@sm.sony.co.jp>
To: martin@duskware.de
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: pr/18520 CVS commit: syssrc/sys/dev/ic
Date: Mon, 7 Oct 2002 20:59:38 +0900 (JST)
> I've finally got the problem. I'll fix the problem later today.
Could you please try the following?
sys/dev/ic/wi.c rev 1.99
Atsushi Onoe
From: Martin Husemann <martin@duskware.de>
To: Atsushi Onoe <onoe@sm.sony.co.jp>
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: pr/18520 CVS commit: syssrc/sys/dev/ic
Date: Mon, 7 Oct 2002 15:23:56 +0200
On Mon, Oct 07, 2002 at 08:59:38PM +0900, Atsushi Onoe wrote:
> Could you please try the following?
> sys/dev/ic/wi.c rev 1.99
Sorry, does not work (wiconfig output is the same as before).
I rearanged /etc/ifconfig.wi0 to get rid of wiconfig as much as possible,
it now looks like this:
192.168.XXX.X down
! /usr/sbin/wiconfig wi0 -s XXXXXXXXXX
mediaopt adhoc
nwid XXXXXXXXXXXX nwkey 1:XXXXX,XXXXX,XXXXX,XXXXX
up
but that does not help.
Martin
From: Atsushi Onoe <onoe@sm.sony.co.jp>
To: martin@duskware.de
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: pr/18520 CVS commit: syssrc/sys/dev/ic
Date: Tue, 8 Oct 2002 07:54:14 +0900 (JST)
> Sorry, does not work (wiconfig output is the same as before).
> I rearanged /etc/ifconfig.wi0 to get rid of wiconfig as much as possible,
Fine,
> but that does not help.
Hmm, I've confirmed it works on the exact same revision of the firmware.
Could you confirm again 'Current BSSID' from wiconfig and 'bssid' from
ifconfig matches, on both stations? Also, 'Current channel' from wiconfig
and 'chan' from ifconfig matches, on both stations?
If all the parameters above match, and 'Port type' is 1 and 'Create IBSS'
is On, I have no idea why it doesn't work..
Atsushi Onoe
From: Martin Husemann <martin@duskware.de>
To: Atsushi Onoe <onoe@sm.sony.co.jp>
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: pr/18520 CVS commit: syssrc/sys/dev/ic
Date: Tue, 8 Oct 2002 22:56:42 +0200
On Tue, Oct 08, 2002 at 07:54:14AM +0900, Atsushi Onoe wrote:
> Hmm, I've confirmed it works on the exact same revision of the firmware.
STUPID ME!
Of course it works, once you make sure ot not have one machine use "NWID"
instead of NWID. Probably a mistake when converting from wiconfig to ifconfig.
Thanks a lot!
Martin
State-Changed-From-To: open->closed
State-Changed-By: martin
State-Changed-When: Tue Oct 8 13:57:13 PDT 2002
State-Changed-Why:
Fixed with sys/dev/ic/wi.c rev 1.99
>Unformatted:
(Contact us)
$NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.