On Wed, May 17, 2006 at 04:28:27PM +0200, Reinhard Tartler wrote: > On Wed, May 17, 2006 at 03:46:10PM +0200, Christoph Haas wrote: > > It appears like the ESSID is not set properly when the interface comes up. > > [...] > > Still when running "iwconfig" I can see that the ESSID is not set to > > "foobar". > > Perhaps the wpa_cli just sets a bunch of parameter for a WLAN with the > > ESSID "foobar" - but doesn't actually assign that ESSID to the interface. > > > > My current workaround: adding a "wireless-essid foobar" to the interface > > definition > > The difference between wpa-essid and wireless-ssid is that the later is > set by iwconfig and the first one by wpasupplicant via Wireless > Extension IO-Calls. I suspect that your driver modules doesn't implement > WE correctly. Could you please tell us what hardware and what driver do > you use? Please tell us the exact version as well.
Thanks for your attention. The kernel module I use is the 'ipw2200' (version 2.4) I got from http://ipw2200.sourceforge.net/firmware.php So the /etc/network/interfaces reads "wpa-driver wext". The hardware is listed (by lspci) as: "Intel Corporation PRO/Wireless 2200BG (rev 05)". It's built into a Fujitsu-SIEMENS Lifebook laptop. Christoph -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
