[ale] Lost wireless on laptop

[James Moore]

Finally got it up again.  Had also posted the problem on the Debian 
forum and a reader there gave me a link to an  Ubuntu how to.  Upon 
examining the set-up suggested and looking at my /etc/network/interfaces 
I saw that in changing from  DHCP to static addressing I had left out 
the wlan info on my eth2 entries.  Once replaced and the system 
restarted all was well again.   Duh.  It was really a learning 
experience.  It always seems that way.  The greater the foul-up the more 
learned from the recovery.
Thanks for you reply
Jim Moore

Jim Kinney wrote:
> Sounds like a key format issue. Sometimes the key is ascii, others 
> hex, others unknown. Start by digging into the key type on the desktop 
> and compare with the laptop. Also check the WAP device to see if it 
> was "upgraded".
>
> On Tue, Apr 29, 2008 at 11:42 AM, Jim Moore <d2ove4deb at bellsouth.net 
> <mailto:d2ove4deb at bellsouth.net>> wrote:
>
>     First how I got here.  Changed from dhcp to static; i.e; reset router
>     assigning addresses to desktop and laptop. It worked fine on
>     desktop but
>     could never get laptop to connect.  So have gone back and reset router
>     to dhcp, again desktop connects no problem, but laptop can't.
>     If I go to Administration>Network and check eth2 (which is where my
>     wireless is set up) it shows the device is working.
>     Looking at /etc/network/interfaces  I see:
>     #The loopback network interface
>     auto lo
>     iface lo init loopback
>
>     #The primary network interface
>     iface eth2 init dhcp
>     wireless-essid  "My wireless network"
>     wireless - key s: "My tkip key"
>
>     auto eth2
>
>     This is what happens when I boot up and it gets down to loading
>     the network:
>
>     "DHCP Discover on eth2 255.255.255.255 <http://255.255.255.255>
>     port 67"  This is repeated 4
>     times, then a pause and again repeats four times.
>
>     Then the message "eth2:NetDev_Tx_BUSY returned
>     No working leases in persistent database"
>
>     Another abnormality which occurs just before it begins the DHCP
>     Discover
>     routine is a message appears that it doesn't recognize the tkip
>     key but
>     it only gives the last ten characters of the key not the first three
>     digits.  My key is 3 digits and then 10 characters.
>
>     Any suggestions as to where to start to set all of this straight
>     again?
>
>     Jim
>
>
>
>     _______________________________________________
>     Ale mailing list
>     Ale at ale.org <mailto:Ale at ale.org>
>     http://mail.ale.org/mailman/listinfo/ale
>
>
>
>
> -- 
> -- 
> James P. Kinney III
> ------------------------------------------------------------------------
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://mail.ale.org/mailman/listinfo/ale
>