[maemo-developers] WLAN connectivity using only wireless-tools

From: Kalle Vahlman kalle.vahlman at gmail.com
Date: Mon Oct 1 21:19:53 EEST 2007
2007/9/26, Kalle Valo <Kalle.Valo at nokia.com>:
> "ext Kalle Vahlman" <kalle.vahlman at gmail.com> writes:
>
> >> > ifconfig wlan0 up
> >> > iwlist wlan0 scanning > /wlan-list
> >> > iwconfig wlan0 mode managed
> >> > iwconfig wlan0 ap auto
> >> > iwconfig wlan0 essid "xxx"
> >>
> >> I don't use the ap command at all, try without it first.
> >
> > I don't remember if I ever tried without it, but at least now it works
> > when I removed all but the essid command. Go figure :)
>
> Yeah, basically scan, mode and ap commands are not needed because the
> defaults are the same as you set here.
>
> But it might that you were just lucky this time. If only two channels
> are scanned, most of the time the driver won't be able to associate
> because it can't find the AP. How many channels did it scan?

On boot, it says two channels was scanned. Association hasn't failed
on me yet, so perhaps I'm a very lucky guy :P

Running iwlist scanning by hand reports 13 channels afterwards though.
And shows one result with zeroed values (I think I've seen discussion
on this bug though).

On a related matter, I tried to build the modules from garage sources
and although it seemingly worked, replacing the modules on board left
me with non-functional wlan. Being a smart guy (not just lucky), I had
a way to go back to the original drivers of course.

I didn't yet dig deeper and gather logs (IIRC the firmware or driver
was resetting the chip after any commands to the interface), since I
wanted to know first if they are known to be compatible with the
current ITOS2007 release (initfs) or was it just me?

-- 
Kalle Vahlman, zuh at iki.fi
Powered by http://movial.fi
Interesting stuff at http://syslog.movial.fi

More information about the maemo-developers mailing list