[Pkg-utopia-maintainers] Bug#609072: Processed: Re: Bug#609072: Trials over WLAN: Installation (The Process) Now Successful but Installation (The Result) Not Satisfactory
Paul Bryan Roberts
pbronline-debian at yahoo.co.uk
Fri Jan 7 21:00:13 UTC 2011
Michael Biebl wrote:
> What's the content of /etc/network/interfaces?
>
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug wlan0
iface wlan0 inet dhcp
# wireless-* options are implemented by the wireless-tools
package
wireless-mode managed
wireless-essid Custards
wireless-key1 a7d02f1dad
> Is this how it was created by the installer?
>
Yes
> Please paste the output of nm-tool.
>
NetworkManager Tool
State: disconnected
- Device: wlan0
----------------------------------------------------------------
Type: 802.11 WiFi
Driver: p54pci
State: unmanaged
Default: no
HW Address: 00:09:5B:EE:E5:0E
Capabilities:
Wireless Properties
WEP Encryption: yes
WPA Encryption: yes
WPA2 Encryption: yes
Wireless Access Points
> Please stop the running network-manager (/etc/init.d/network-manager stop) and
> run it manually (as root) NetworkManager --no-daemon and attach the output.
>
See attachment.
> Do you maybe start wpa_supplicant via /etc/network/interfaces (ifupdown) and you
> have two wpa_supplicant instances fighting against each other?
>
>
No. ps -ef | grep wpa reports only one wpa_supplicant.
> Why do you think there is a bug in network-manager?
>
I don't particularly. Something has changed. Perhaps it is something
I did.
I submitted an Installation Report in response to the request that
folks 'test' squeeze
installation and upgrade. It seemed pointless to go to all that
trouble and then not
submit my findings even though I have little expectation of being
taken seriously.
> Please explain the problem in more detail.
>
I have two laptops available for testing (the newer runs KDE, the
older one LXDE).
These ran lenny and what I perceived to be the Network Manager worked
fine.
I could click on the task bar icon and see all wireless access points
nearby.
I could configure a connection for my wireless access point.
Subsequently I was connected automatically each login.
All I needed to do was enter the password for Kwallet on the laptop
running KDE.
I upgraded both laptops to squeeze beta 2 mid December (2010).
The Network Manager appeared fine.
The p54pci driver on the older laptop crashed periodically until I
upgraded the firmware blob.
I did a wired install on KDE laptop and again, the Network Manager
worked fine.
Early January (2011) I attempted a wireless install on both laptops.
The Network Manager (the GUI applet end of it) does not suggest
anything is wrong
but the scan shows no wireless access points at all in the neighbourhood !
My attempts to configure a connection to my WAP have been unsuccessful.
I hypothesise what I did differently this time was the wireless install.
I conjecture /etc/network/interfaces has definitions for wlan0 instead
of (wired) eth0
(I've never looked before - no need - it worked).
This has upset the Network Manager.
OK, so perhaps it can't connect to my WAP but it should say so.
At least I still ought to able to be scan the neighbourhood and see
the other WAPs.
If the contents of /etc/network/interfaces are causing the Network
Manager problems
then perhaps the issue to be reassigned back to the Debian Installer.
It seems paradoxical that the squeeze network manager
works (allows naive user to configuration wireless)
'out of the box' (no other configuration necessary)
*** provided *** you don't use the wireless interface to install squeeze.
> Michael
>
Paul
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: larch.man.txt
URL: <http://lists.alioth.debian.org/pipermail/pkg-utopia-maintainers/attachments/20110107/d55deb27/attachment.txt>
More information about the Pkg-utopia-maintainers
mailing list