[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#288522: debian-installer: WLAN config settings become lost (perhaps misplaced) upon first boot



Michael Gilbert wrote:
> i'm using the i386 debian-installer RC2
> (http://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/i386/rc2/sarge-i386-netinst.iso)
> on a dell inspiron 8200 laptop with a dell truemobile 1150 wlan card
> on a TI PCI-1410 cardbus.  i use a non-standard SSID and a secure WEP
> key on my wireless network.  during the debian-installer

Hope you realize that "secure WEP" is an oxymoron.

Anyway, what kind of interface does your wireless card have? Is it a
pcmcia device?

> if i do "iwconfig," i see that eth1 has "no wireless extensions" and
> that instead eth2 appears to have settings relating to a wireless
> interface, but the SSID and WEP key are not configured (eth0 is my
> wired lan connection which also says "no wireless extensions").  
> now, if i do "ifconfig," i get lo which appears to do it's thing
> correctly (i can ping localhost) and only get an eth1 which says
> "UP BROADCAST RUNNING MULTICAST" as if it's attempting to contact the
> dhcp server, but is just unable to.  there is no eth2 when i do
> "ifconfig."  if i look in "/etc/network/interfaces," the eth1 section
> does have the SSID and WEP key settings that i had set up earlier at the
> beginning of the install.  as an aside, my secure WEP key is stored
> as plain-text in this file (potentially part of the problem and maybe
> a security issue?).

This could happen if the installer for some reason brought up the
interfaces in a different order than the installed system. So wireless
was eth1 during the installation process, and your wired ethernet was
either eth2 or was not detected. Then when booting the installed system
it loads the driver for wired and then wireless. To track this down it
would help to know what bus (pcmcia, pci, usb, whatever) is used
for both your wireless and wired interfaces, and also what kernel
modules are loaded to drive them (lsmod) and probably your PCI bus
information (lspci; lspci-n).

-- 
see shy jo

Attachment: signature.asc
Description: Digital signature


Reply to: