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

Re: Wireless issues -- Lenovo R61 ThinkPad -- success BUT ...



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thanks to Guiseppe Marinelli and Lee Glidewell for their responses,
which put me on to the right track.

I did not turn on the R61 yesterday (Sunday 21 Sept) but turned it on
this morning, Monday 22 Sept but also before I read the two responses to
my plea for help.  I decided to try to activate the 3945 wireless card,
and so to connect to the local network where I am presently located  --
usually Toronto Canada but until 12 October Berlin Germany.

After booting I ran as root "cat /etc/network/interfaces", which
returned the following:

# The loopback network interface
auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0

# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp

iface wlan0 inet dhcp
wireless-essid FRITZ!Box Fon WLAN 7050
wireless-key 47656973626572677374723137

So the essential information with respect the network I want is there
and available for use.

Next, I ran "ifup wlan0", which returned the following:

Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:1f:3c:28:09:1e
Sending on   LPF/wlan0/00:1f:3c:28:09:1e
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPOFFER from 192.168.178.1
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPACK from 192.168.178.1
bound to 192.168.178.28 -- renewal in 388595 seconds.

I don't understand the first, second and fifth lines of this message,
BUT I am now connected.

Now, iwconfig shows the address of the access point.  As mentioned in
the initial message of this thread, for "Access Point" iwconfig had
returned "Not Associated", meaning really no connection.

I am now convinced that my troubles stemmed from trying to use KDE's
wireless management system.  I remember now I had trouble with it a few
years ago when I was trying to use it with older laptops and various
PCMCIA wireless cards, both WEP and WPA.  I ended up using the commands
in the ifupdown package to find and establish a connection.

I would consequently not recommend use of network-manager-kde, which
appears to me to be KDE's flawed gui front end for network-manager.  The
latter depends on ifupdown, which I think is the really important
package for wireless connectivity management -- nothing like the good
old command line.

I also find confusing the fact that KDE's control centre has two
configuration modules for wireless connections, both in the "Internet &
Network" group.  One, "Network Settings", shows the enabled interfaces
and allows their enabling, disabling and configuration.  The other,
"Wireless Network", ostensibly allows configuration of multiple
connections.  I am not of a mind to trust either of them.

I would like however to be able to have the wireless connection enabled
on boot-up.  I would appreciate it if someone could tell me how to do so.

Regards,

Ken Heard
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkjXStsACgkQlNlJzOkJmTeomQCfQIEEORXQddcDZajVSuCTbuvs
7xQAoIGkMALLek4TrtrJibUpze7JuaZC
=CdyL
-----END PGP SIGNATURE-----


Reply to: