Re: Problems with NM initial setup on FC6

["Jonathan Nichols" <jnichols alumni princeton edu>]

Hi Dan,

    Thanks for the response.  After a few more reboots and restoration of the eth1 device in the Network Configuration tool I was able to get it up and running.  

Best Regards,

jon

On Thu, Mar 6, 2008 at 6:49 AM, Dan Williams <dcbw redhat com> wrote:

On Wed, 2008-03-05 at 12:37 -0800, Jonathan Nichols wrote:
> Hello,
>
>     I am trying to set up Network Manager for the first time.  Here is
> a sequence of events I have gone through:

What version of NetworkManager do you have installed?

rpm -qv NetworkManager

should tell you.

> 1)  Enabled Network Manager by starting the service in /etc/init.d
> 2)  Clicked on the icon to see a list of SSIDs
> 3)  Clicked on the desired SSID
> 4)  Entered the WPA key
> 5)  The icon went through its thinking phase, and then it gave me the
> red circle with the line through it
> 6)  I thought that there might be a collision between the eth1 device
> set up with the Network Configuration Manager so i delete the eth1
> entry in the devices list (but did not delete it in the hardware tab)
> 7)  I clicked on the Network Manager icon again, entered the WPA key.
> 8)  I was prompted for a key ring manager password.  I entered a
> password
> 9)  Network Manager told me that was successfully connected to the
> desired SSID
> 10)  However, I couldn't access any websites
> 11)  I rebooted my computer
> 12)  I restarted the Network Manager service
> 13)  I tried to access the desired SSID
> 14)  I am never able to connect.  I just get the red circle with the
> line through it.  Here is my /var/log/messages log:

We might need to try a straight wpa_supplicant run here to ensure that
your driver is working properly.  NetworkManager uses wpa_supplicant
underneath to control the wireless card, so going directly to
wpa_supplicant can tell us whether NM is the problem or not.  To do
that, you'll want to 'service NetworkManager stop' and then construct a
wpa_supplicant config file in /tmp that will look like this:


eapol_version=1
ap_scan=1
fast_reauth=1
network={
       ssid="my-ssid"
       scan_ssid=1
       proto=WPA RSN
       key_mgmt=WPA-PSK
       psk="my passphrase"
}

Of course, replace my-ssid with your SSID and my passphrase with your
actual WPA passphrase.  Then, as root, run wpa_supplicant like so:

/usr/sbin/wpa_supplicant -ddd -i wlan0 -c /tmp/wpa_supplicant.conf -D wext

Let that run for at least a minute or two, and then copy the output and
mail it to me directly as it may have private details about your network
in it.

Dan

> Mar  5 12:31:27 localhost NetworkManager: <information> User
> Switch: /org/freedesktop/NetworkManager/Devices/_5f__5f_tmp342535111 /
> bengi
> Mar  5 12:31:27 localhost NetworkManager: <information> Deactivating
> device __tmp342535111.
> Mar  5 12:31:27 localhost NetworkManager: <information> Device
> __tmp342535111 activation scheduled...
> Mar  5 12:31:27 localhost NetworkManager: <information> Activation
> (__tmp342535111) started...
> Mar  5 12:31:27 localhost NetworkManager: <information> Activation
> (__tmp342535111) Stage 1 of 5 (Device Prepare) scheduled...
> Mar  5 12:31:27 localhost NetworkManager: <information> Activation
> (__tmp342535111) Stage 1 of 5 (Device Prepare) started...
> Mar  5 12:31:27 localhost NetworkManager: <information> Activation
> (__tmp342535111) Stage 2 of 5 (Device Configure) scheduled...
> Mar  5 12:31:27 localhost NetworkManager: <information> Activation
> (__tmp342535111) Stage 1 of 5 (Device Prepare) complete.
> Mar  5 12:31:27 localhost NetworkManager: <information> Activation
> (__tmp342535111) Stage 2 of 5 (Device Configure) starting...
> Mar  5 12:31:27 localhost NetworkManager: <information> Activation
> (__tmp342535111/wireless): access point 'bengi' is encrypted, but NO
> valid key exists.  New key needed.
> Mar  5 12:31:27 localhost NetworkManager: <information> Activation
> (__tmp342535111) New wireless user key requested for network 'bengi'.
> Mar  5 12:31:27 localhost NetworkManager: <information> Activation
> (__tmp342535111) Stage 2 of 5 (Device Configure) complete.
> Mar  5 12:31:27 localhost NetworkManager: <information> Activation
> (__tmp342535111) New wireless user key for network 'bengi' received.
> Mar  5 12:31:27 localhost NetworkManager: <information> Activation
> (__tmp342535111) Stage 1 of 5 (Device Prepare) scheduled...
> Mar  5 12:31:27 localhost NetworkManager: <information> Activation
> (__tmp342535111) Stage 1 of 5 (Device Prepare) started...
> Mar  5 12:31:27 localhost NetworkManager: <information> Activation
> (__tmp342535111) Stage 2 of 5 (Device Configure) scheduled...
> Mar  5 12:31:27 localhost NetworkManager: <information> Activation
> (__tmp342535111) Stage 1 of 5 (Device Prepare) complete.
> Mar  5 12:31:27 localhost NetworkManager: <information> Activation
> (__tmp342535111) Stage 2 of 5 (Device Configure) starting...
> Mar  5 12:31:27 localhost NetworkManager: <information> Activation
> (__tmp342535111/wireless): access point 'bengi' is encrypted, and a
> key exists.  No new key needed.
> Mar  5 12:31:27 localhost NetworkManager: <information> SUP: sending
> command 'INTERFACE_ADD __tmp342535111
> wext    /var/run/wpa_supplicant '
> Mar  5 12:31:27 localhost NetworkManager: <information> SUP: response
> was 'OK'
> Mar  5 12:31:27 localhost NetworkManager: <information> SUP: sending
> command 'AP_SCAN 1'
> Mar  5 12:31:27 localhost NetworkManager: <information> SUP: response
> was 'OK'
> Mar  5 12:31:27 localhost NetworkManager: <information> SUP: sending
> command 'ADD_NETWORK'
> Mar  5 12:31:27 localhost NetworkManager: <information> SUP: response
> was '0'
> Mar  5 12:31:27 localhost NetworkManager: <information> SUP: sending
> command 'SET_NETWORK 0 ssid 62656e6769'
> Mar  5 12:31:27 localhost NetworkManager: <information> SUP: response
> was 'OK'
> Mar  5 12:31:27 localhost NetworkManager: <information> SUP: sending
> command 'SET_NETWORK 0 proto WPA'
> Mar  5 12:31:27 localhost NetworkManager: <information> SUP: response
> was 'OK'
> Mar  5 12:31:27 localhost NetworkManager: <information> SUP: sending
> command 'SET_NETWORK 0 key_mgmt WPA-PSK'
> Mar  5 12:31:27 localhost NetworkManager: <information> SUP: response
> was 'OK'
> Mar  5 12:31:27 localhost NetworkManager: <information> SUP: sending
> command 'SET_NETWORK 0 psk <key>'
> Mar  5 12:31:27 localhost NetworkManager: <information> SUP: response
> was 'OK'
> Mar  5 12:31:27 localhost NetworkManager: <information> SUP: sending
> command 'ENABLE_NETWORK 0'
> Mar  5 12:31:27 localhost NetworkManager: <information> SUP: response
> was 'OK'
> Mar  5 12:31:27 localhost NetworkManager: <information> Activation
> (__tmp342535111) Stage 2 of 5 (Device Configure) complete.
> Mar  5 12:31:27 localhost kernel: ADDRCONF(NETDEV_CHANGE):
> __tmp342535111: link becomes ready
> Mar  5 12:31:27 localhost NetworkManager: <information> Activation
> (__tmp342535111/wireless) Stage 2 of 5 (Device Configure) successful.
> Connected to access point 'bengi'.
> Mar  5 12:31:27 localhost NetworkManager: <information> Activation
> (__tmp342535111) Stage 3 of 5 (IP Configure Start) scheduled.
> Mar  5 12:31:27 localhost NetworkManager: <information> Activation
> (__tmp342535111) Stage 3 of 5 (IP Configure Start) started...
> Mar  5 12:31:29 localhost avahi-daemon[3012]: New relevant interface
> __tmp342535111.IPv6 for mDNS.
> Mar  5 12:31:29 localhost avahi-daemon[3012]: Joining mDNS multicast
> group on interface __tmp342535111.IPv6 with address
> fe80::213:ceff:fe8e:32b7.
> Mar  5 12:31:29 localhost avahi-daemon[3012]: Registering new address
> record for fe80::213:ceff:fe8e:32b7 on __tmp342535111.
> Mar  5 12:31:29 localhost NetworkManager: <information> Activation
> (__tmp342535111) Beginning DHCP transaction.
> Mar  5 12:31:29 localhost NetworkManager: <information> Activation
> (__tmp342535111) Stage 3 of 5 (IP Configure Start) complete.
> Mar  5 12:31:29 localhost NetworkManager: <information> DHCP daemon
> state is now 12 (successfully started) for interface __tmp342535111
> Mar  5 12:31:29 localhost NetworkManager: <information> DHCP daemon
> state is now 1 (starting) for interface __tmp342535111
> Mar  5 12:31:29 localhost dhclient: DHCPDISCOVER on __tmp342535111 to
> 255.255.255.255 port 67 interval 6
> Mar  5 12:31:29 localhost dhclient: send_packet: No such device
> Mar  5 12:31:35 localhost dhclient: DHCPDISCOVER on __tmp342535111 to
> 255.255.255.255 port 67 interval 12
> Mar  5 12:31:35 localhost dhclient: send_packet: No such device
> Mar  5 12:31:47 localhost dhclient: DHCPDISCOVER on __tmp342535111 to
> 255.255.255.255 port 67 interval 11
> Mar  5 12:31:47 localhost dhclient: send_packet: No such device
> Mar  5 12:31:58 localhost dhclient: DHCPDISCOVER on __tmp342535111 to
> 255.255.255.255 port 67 interval 20
> Mar  5 12:31:58 localhost dhclient: send_packet: No such device
> Mar  5 12:32:14 localhost NetworkManager: <information> Device
> '__tmp342535111' DHCP transaction took too long (>45s), stopping it.
> Mar  5 12:32:15 localhost NetworkManager: <information> Activation
> (__tmp342535111) Stage 4 of 5 (IP Configure Timeout) scheduled...
> Mar  5 12:32:15 localhost NetworkManager: <information> DHCP daemon
> state is now 14 (normal exit) for interface __tmp342535111
> Mar  5 12:32:15 localhost NetworkManager: <information> DHCP daemon
> state is now 14 (normal exit) for interface __tmp342535111
> Mar  5 12:32:15 localhost NetworkManager: <information> Activation
> (__tmp342535111) Stage 4 of 5 (IP Configure Timeout) started...
> Mar  5 12:32:15 localhost NetworkManager: <information> Activation
> (__tmp342535111) failure scheduled...
> Mar  5 12:32:15 localhost NetworkManager: <information> Activation
> (__tmp342535111) Stage 4 of 5 (IP Configure Timeout) complete.
> Mar  5 12:32:15 localhost NetworkManager: <information> Activation
> (__tmp342535111) failed for access point (bengi)
> Mar  5 12:32:15 localhost NetworkManager: <information> Activation
> (__tmp342535111) failed.
> Mar  5 12:32:15 localhost NetworkManager: <information> Deactivating
> device __tmp342535111.
> Mar  5 12:32:15 localhost avahi-daemon[3012]: Withdrawing address
> record for fe80::213:ceff:fe8e:32b7 on __tmp342535111.
> Mar  5 12:32:15 localhost avahi-daemon[3012]: Leaving mDNS multicast
> group on interface __tmp342535111.IPv6 with address
> fe80::213:ceff:fe8e:32b7.
> Mar  5 12:32:15 localhost avahi-daemon[3012]: iface.c:
> interface_mdns_mcast_join() called but no local address available.
> Mar  5 12:32:15 localhost avahi-daemon[3012]: Interface
> __tmp342535111.IPv6 no longer relevant for mDNS.
>
>
> I'm thinking that the "no such device" is the key here but I haven't
> made any more progress.  I tried adding a device to the network
> configuration device manager but that hasn't worked.
>
> Any ideas?
>
> -jon
>

> _______________________________________________
> NetworkManager-list mailing list
> NetworkManager-list gnome org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list