I'm not using WPA but WEP for now, so the wpa_supplicant script figures that out and exits without problems. NetworkManager is running and this is what syslog says about it:
Aug 18 09:41:21 febian NetworkManager: <WARN> nm_signal_handler(): Caught signal 15, shutting down normally. Aug 18 09:41:21 febian NetworkManager: <info> Caught terminiation signal Aug 18 09:41:21 febian NetworkManager: <debug> [1219077681.283986] nm_print_open_socks(): Open Sockets List: Aug 18 09:41:21 febian NetworkManager: <debug> [1219077681.284081] nm_print_open_socks(): Open Sockets List Done. Aug 18 09:41:21 febian NetworkManager: <info> Deactivating device eth1. Aug 18 19:52:46 febian kernel: udev: renamed network interface eth0 to eth1 Aug 18 19:52:51 febian avahi-daemon[5860]: Network interface enumeration completed. Aug 18 19:52:55 febian NetworkManager: <info> starting... Aug 18 19:52:55 febian NetworkManager: <info> New VPN service 'openvpn' (org.freedesktop.NetworkManager.openvpn). Aug 18 19:52:55 febian NetworkManager: <info> New VPN service 'vpnc' (org.freedesktop.NetworkManager.vpnc). Aug 18 19:52:56 febian NetworkManager: <info> eth1: Device is fully-supported using driver 'tg3'. Aug 18 19:52:56 febian NetworkManager: <info> nm_device_init(): waiting for device's worker thread to start Aug 18 19:52:57 febian NetworkManager: <info> nm_device_init(): device's worker thread started, continuing. Aug 18 19:52:57 febian NetworkManager: <info> Now managing wired Ethernet (802.3) device 'eth1'. Aug 18 19:52:57 febian NetworkManager: <info> Deactivating device eth1. Aug 18 19:52:57 febian NetworkManager: <info> Will activate wired connection 'eth1' because it now has a link. Aug 18 19:52:57 febian NetworkManager: <info> SWITCH: no current connection, found better connection 'eth1'. Aug 18 19:52:57 febian NetworkManager: <info> Will activate connection 'eth1'. Aug 18 19:52:57 febian NetworkManager: <info> Device eth1 activation scheduled... Aug 18 19:52:57 febian NetworkManager: <info> Activation (eth1) started... Aug 18 19:52:57 febian NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled... Aug 18 19:52:57 febian NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started... Aug 18 19:52:57 febian NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled... Aug 18 19:52:57 febian NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete. Aug 18 19:52:57 febian NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting... Aug 18 19:52:57 febian NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) successful. Aug 18 19:52:57 febian NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) scheduled. Aug 18 19:52:57 febian NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete. Aug 18 19:52:57 febian NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) started... Aug 18 19:52:58 febian NetworkManager: <info> Activation (eth1) Beginning DHCP transaction. Aug 18 19:52:58 febian NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) complete. Aug 18 19:52:58 febian NetworkManager: <info> DHCP daemon state is now 12 (successfully started) for interface eth1 Aug 18 19:52:59 febian NetworkManager: <info> DHCP daemon state is now 1 (starting) for interface eth1 Aug 18 19:53:00 febian NetworkManager: <info> DHCP daemon state is now 4 (reboot) for interface eth1 Aug 18 19:53:00 febian NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP Configure Get) scheduled... Aug 18 19:53:00 febian NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP Configure Get) started... Aug 18 19:53:00 febian NetworkManager: <info> Retrieved the following IP4 configuration from the DHCP daemon: Aug 18 19:53:00 febian NetworkManager: <info> address 192.168.1.103 Aug 18 19:53:00 febian NetworkManager: <info> netmask 255.255.255.0 Aug 18 19:53:00 febian NetworkManager: <info> broadcast 192.168.1.255 Aug 18 19:53:00 febian NetworkManager: <info> gateway 192.168.1.1 Aug 18 19:53:00 febian NetworkManager: <info> nameserver 64.59.160.13 Aug 18 19:53:00 febian NetworkManager: <info> nameserver 64.59.160.15 Aug 18 19:53:00 febian NetworkManager: <info> domain name 'gv.shawcable.net' Aug 18 19:53:00 febian NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) scheduled... Aug 18 19:53:00 febian NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP Configure Get) complete. Aug 18 19:53:00 febian NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) started... Aug 18 19:53:01 febian NetworkManager: <info> DHCP returned name servers but system has disabled dynamic modification! Aug 18 19:53:01 febian NetworkManager: <info> Activation (eth1) Finish handler scheduled. Aug 18 19:53:01 febian NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) complete. Aug 18 19:53:01 febian NetworkManager: <info> Activation (eth1) successful, device activated. There is no mention of wlan0, even after an ifconfig wlan0 up. On 8/17/08, Larry Finger <[EMAIL PROTECTED]> wrote: > Francesco Marass wrote: >> Thank you for your reply. >> >> There is no iface command: I was not clear enough and just pasted the >> /etc/network/interfaces iface stanza for my wireless. So >> >> iface wlan0 inet dhcp >> wireless-essid XXXX >> wireless-key YYYY >> >> is how my wlan0 interface is configured within /etc/network/interfaces. >> >> I did not really make changes to the system. I did install some >> SELinux packages, but right after I purged for various reasons. >> >> How do I turn on the interface, if after my attempts (with ifup, >> iwconfig, network-manager, ...) I still do not get scan results? (I >> wonder whether I am even able to scan, or just do not find networks) > > It looks as if something is wrong with wpa_supplicant. When using NM, > please check your 'ps ax' listing to see that it is running. In > addition, look at the NetworkManager log in /var/log to see what it says. > > Larry > _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
