Hi Guys,

My iwi interface works very well if I set it up with
/etc/hostname.iwi0, but if I change access points I can usually not
get onto a new network. For example, consider this scenario:

At location 1 with open AP 'dlink' available:
# echo "dhcp nwid dlink" > /etc/hostname.iwi0
(reboot), and all is well.

I move to a new location without rebooting, and I want to get onto a
new AP, for example 'attwifi', so I try:
# ifconfig nwid attwifi    (However this will almost never result in
'status active', sometimes it does work, randomly.)
# sh /etc/netstart iwi0  (rarely works because it says no link)

I have tried to reset it to defaults with the man page example, but
this doesn't work either.. I'll try something like this:
ifconfig iwi0 -bssid -chan media autoselect nwid "" -nwkey -wpa -wpapsk
ifconfig iwi0 nwid attwifi
ifconfig iwi0 up
sh /etc/netstart iwi0
(However this usually does not work either)

So I am often forced to reboot just to change AP's, and that is rather
annoying. Any thoughts? I am running -current but have had this issue
since 4.5-release

The machine is an IBM T42p

$ pkg_info | grep iwi
iwi-firmware-3.1    Firmware binary image for iwi driver

OpenBSD 4.6-current (GENERIC) #62: Wed Jul 15 17:27:21 MDT 2009
    deraadt@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel(R) Pentium(R) M processor 2.00GHz ("GenuineIntel" 686-class) 599 MHz
cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,SBF,EST,TM2
real mem  = 1072656384 (1022MB)
avail mem = 1028411392 (980MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 06/18/07, BIOS32 rev. 0 @
0xfd750, SMBIOS rev. 2.33 @ 0xe0010 (61 entries)
bios0: vendor IBM version "1RETDRWW (3.23 )" date 06/18/2007
bios0: IBM 2373KUU
apm0 at bios0: Power Management spec V1.2
apm0: battery life expectancy 29%
apm0: AC off, battery charge high, estimated 0:24 hours
acpi at bios0 function 0x0 not configured
pcibios0 at bios0: rev 2.1 @ ...
[ message continues ]

This will reset your nwid to 'dlink', which is what you have in

Again, this resets your nwid to 'dlink'.


[ message continues ]

David,

You are right. The way I laid out the example it would go back to
dlink. For the sake
of argument assume that I have also edited /etc/hostname.iwi0 "dhcp
nwid attwifi", as that doesn't seem to work either.

But, what you are saying to do is to use ifconfig to setup the network
connection
and then dhclient once you can get 'status: active' in ifconfig. The
problem I have is
that I can't reliably get ifconfig to get an active status. It does
work sometimes, but
for some reason it is not consistent.

Jeremy


FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,F

[ message continues ]

Hi Jeremy,

iwi does seem to be a bit picky about changing access points without a
reboot (I've though about replacing it on my laptop with another
card), what usually works for me is the following sequence of
commands:

x41:fred ~> sudo ifconfig iwi0 down
x41:fred ~> sudo ifconfig iwi0 nwid myaccesspoint nwkey mykey
x41:fred ~> sudo ifconfig iwi0 scan
x41:fred ~> sudo /sbin/dhclient iwi0

Doing the scan after changing settings but before issuing a dhclient
seems to get iwi into an active state.

HTH

Fred

[ message continues ]