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

NetworkManager[2094]: <info> NetworkManager (version 0.8.1) is starting...
NetworkManager[2094]: <info> Read config file 
/etc/NetworkManager/NetworkManager.conf
NetworkManager[2094]: <info> modem-manager is now available
NetworkManager[2094]:    SCPlugin-Ifupdown: init!
NetworkManager[2094]:    SCPlugin-Ifupdown: update_system_hostname
NetworkManager[2094]:    SCPluginIfupdown: guessed connection type (wlan0) = 
802-11-wireless
NetworkManager[2094]:    SCPlugin-Ifupdown: 
update_connection_setting_from_if_block: name:wlan0, type:802-11-wireless, 
id:Ifupdown (wlan0), uuid: 5391eba4-6426-faca-338e-5828034ff9d1
NetworkManager[2094]:    SCPlugin-Ifupdown: update wireless settings (wlan0).
NetworkManager[2094]:    SCPlugin-Ifupdown: wireless setting key: 
(null)='managed'
NetworkManager[2094]:    SCPlugin-Ifupdown: wireless setting key: 
(null)='Custards'
NetworkManager[2094]:    SCPlugin-Ifupdown: wireless setting key: 
(null)='d0a72f1dad'
NetworkManager[2094]:    SCPlugin-Ifupdown: update wireless security settings 
(wlan0).
NetworkManager[2094]: no (wireless) mapping found for key: wireless-mode
NetworkManager[2094]: no (wireless) mapping found for key: wireless-essid
NetworkManager[2094]: no (wireless) mapping found for key: wireless-key1
NetworkManager[2094]: nm-ifupdown-connection.c.119 - invalid connection read 
from /etc/network/interfaces: (2) ssid
NetworkManager[2094]:    SCPlugin-Ifupdown: adding iface wlan0 to 
well_known_interfaces
NetworkManager[2094]:    SCPluginIfupdown: management mode: unmanaged
NetworkManager[2094]:    SCPlugin-Ifupdown: devices added (path: 
/sys/devices/pci0000:00/0000:00:08.0/0000:02:00.0/net/wlan0, iface: wlan0)
NetworkManager[2094]:    SCPlugin-Ifupdown: devices added (path: 
/sys/devices/virtual/net/lo, iface: lo)
NetworkManager[2094]:    SCPlugin-Ifupdown: device added (path: 
/sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found.
NetworkManager[2094]:    SCPlugin-Ifupdown: devices added (path: 
/sys/devices/virtual/net/pan0, iface: pan0)
NetworkManager[2094]:    SCPlugin-Ifupdown: device added (path: 
/sys/devices/virtual/net/pan0, iface: pan0): no ifupdown configuration found.
NetworkManager[2094]:    SCPlugin-Ifupdown: end _init.
NetworkManager[2094]: <info> Loaded plugin ifupdown: (C) 2008 Canonical Ltd.  
To report bugs please use the NetworkManager mailing list.
NetworkManager[2094]: <info> Loaded plugin keyfile: (c) 2007 - 2008 Red Hat, 
Inc.  To report bugs please use the NetworkManager mailing list.
NetworkManager[2094]:    Ifupdown: get unmanaged devices count: 1
NetworkManager[2094]:    SCPlugin-Ifupdown: (149589280) ... get_connections.
NetworkManager[2094]:    SCPlugin-Ifupdown: (149589280) ... get_connections 
(managed=false): return empty list.
NetworkManager[2094]:    Ifupdown: get unmanaged devices count: 1
NetworkManager[2094]: <info> found WiFi radio killswitch rfkill0 (at 
/sys/devices/pci0000:00/0000:00:08.0/0000:02:00.0/ieee80211/phy0/rfkill0) 
(driver <unknown>)
NetworkManager[2094]: <info> WiFi enabled by radio killswitch; enabled by state 
file
NetworkManager[2094]: <info> WWAN enabled by radio killswitch; enabled by state 
file
NetworkManager[2094]: <info> WiMAX enabled by radio killswitch; enabled by 
state file
NetworkManager[2094]: <info> Networking is enabled by state file
NetworkManager[2094]: <info> (wlan0): driver supports SSID scans (scan_capa 
0x01).
NetworkManager[2094]: <info> (wlan0): new 802.11 WiFi device (driver: 'p54pci' 
ifindex: 2)
NetworkManager[2094]: <info> (wlan0): exported as 
/org/freedesktop/NetworkManager/Devices/0
NetworkManager[2094]: <warn> /sys/devices/virtual/net/pan0: couldn't determine 
device driver; ignoring...
/sbin/ifup: interface lo already configured
NetworkManager[2094]: <warn> bluez error getting default adapter: No such 
adapter
NetworkManager[2094]: <info> caught signal 2, shutting down normally.
NetworkManager[2094]: <info> caught signal 2, shutting down normally.
NetworkManager[2094]: <info> exiting (success)

Reply via email to