FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Ubuntu > Ubuntu User

 
 
LinkBack Thread Tools
 
Old 11-08-2009, 06:26 PM
Frank Lorenz
 
Default Wireless: network detected, but no connection

Hello Ubuntu Gurus

Before posting this message, I already tried to troubleshoot,
unfortunately without any result. :-(
I spent hours on Google and found no solution. You guys, are my last
chance! :-)

Here the situation:

- two PCs with a fresh and up-to-date install of Ubuntu 9.10 -
2.6.31-15-generic

- two different wireless networks without any restriction (no MAC
filtering, no WEP, no WPA, just an open network)

- two WLAN USB-sticks from Zyxel, mod B-220 (zd1201)

When starting Ubuntu, or clicking on the NetworkManager Applet (ver.
0.7.996), all networks are correctly detected and listed. NetworkManager
tries to connect the network for about a minute, and then fails.

I tried to replace NM with wicd. Wicd connects to the network and a
fraction of a second later disconnects.

- other PCs with Ubuntu 9.10 and 9.04, with integrated WLAN card, have
no problem to connect to the same networks.

- both Zyxel B-220 have no problem to connect the same networks on a Win
XP laptop.

- both Zyxel B-220 USB-sticks have worked well on Ubuntu 8.04

Yes, that's weird! Any ideas?

Many thanks in advance for your help!

Frank

PS: Sorry for my bad English


Output of iwconfig:

wlan1 IEEE 802.11b ESSID:"OpenNetwork" Nickname:"zd1201"
Mode:Managed Channel:0 Access Point: 00:A0:C5:5D:36:CE
Bit Rate:11 Mb/s
Retry RTS thrff Fragment thrff
Power Managementff
Link Quality:0/128 Signal level=24/128 Noise level:0/128
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

Output of ifconfig:

wlan1 Link encap:Ethernet HWaddr 00:a0:c5:62:7e:d9
inet6 addr: fe80::2a0:c5ff:fe62:7ed9/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:513 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:28066 (28.0 KB) TX bytes:320 (320.0 B)


Output of iwlist wlan1 scan:

wlan1 Scan completed :
Cell 01 - Address: 00:A0:C5:5D:36:CE
ESSID:"OpenNetwork"
Mode:Master
Channel:9
Bit Rates:1 Mb/s
Bit Rates:2 Mb/s
Bit Rates:5.5 Mb/s
Bit Rates:11 Mb/s
Encryption keyff
Quality=24/128 Signal level=-90 dBm Noise
level=-96 dBm


And here an excerpt from the daemon.log:

Nov 8 20:03:16 office NetworkManager: <info> Activation (wlan1)
starting connection 'Auto OpenNetwork'
Nov 8 20:03:16 office NetworkManager: <info> (wlan1): device state
change: 3 -> 4 (reason 0)
Nov 8 20:03:16 office NetworkManager: <info> Activation (wlan1) Stage
1 of 5 (Device Prepare) scheduled...
Nov 8 20:03:16 office NetworkManager: <info> Activation (wlan1) Stage
1 of 5 (Device Prepare) started...
Nov 8 20:03:16 office NetworkManager: <info> Activation (wlan1) Stage
2 of 5 (Device Configure) scheduled...
Nov 8 20:03:16 office NetworkManager: <info> Activation (wlan1) Stage
1 of 5 (Device Prepare) complete.
Nov 8 20:03:16 office NetworkManager: <info> Activation (wlan1) Stage
2 of 5 (Device Configure) starting...
Nov 8 20:03:16 office NetworkManager: <info> (wlan1): device state
change: 4 -> 5 (reason 0)
Nov 8 20:03:16 office NetworkManager: <info> Activation
(wlan1/wireless): connection 'Auto OpenNetwork' requires no security.
No secrets needed.
Nov 8 20:03:16 office NetworkManager: <info> Config: added 'ssid'
value 'OpenNetwork'
Nov 8 20:03:16 office NetworkManager: <info> Config: added 'scan_ssid'
value '1'
Nov 8 20:03:16 office NetworkManager: <info> Config: added 'key_mgmt'
value 'NONE'
Nov 8 20:03:16 office NetworkManager: <info> Activation (wlan1) Stage
2 of 5 (Device Configure) complete.
Nov 8 20:03:16 office NetworkManager: <info> Config: set interface
ap_scan to 1
Nov 8 20:03:16 office NetworkManager: <info> (wlan1): supplicant
connection state: scanning -> disconnected
Nov 8 20:03:16 office NetworkManager: <info> (wlan1): supplicant
connection state: disconnected -> scanning
Nov 8 20:03:22 office wpa_supplicant[1491]: CTRL-EVENT-SCAN-RESULTS
Nov 8 20:03:22 office wpa_supplicant[1491]: Trying to associate with
00:a0:c5:5d:36:ce (SSID='OpenNetwork' freq=2452 MHz)
Nov 8 20:03:22 office NetworkManager: <info> (wlan1): supplicant
connection state: scanning -> associating
Nov 8 20:03:23 office wpa_supplicant[1491]: Association request to the
driver failed
Nov 8 20:03:28 office wpa_supplicant[1491]: Authentication with
00:a0:c5:5d:36:ce timed out.
Nov 8 20:03:28 office NetworkManager: <info> (wlan1): supplicant
connection state: associating -> disconnected
Nov 8 20:03:28 office NetworkManager: <info> (wlan1): supplicant
connection state: disconnected -> scanning
Nov 8 20:03:32 office NetworkManager: <info> wlan1: link timed out.
Nov 8 20:03:34 office wpa_supplicant[1491]: CTRL-EVENT-SCAN-RESULTS
Nov 8 20:03:34 office wpa_supplicant[1491]: Trying to associate with
00:a0:c5:5d:36:ce (SSID='OpenNetwork' freq=2452 MHz)
Nov 8 20:03:34 office NetworkManager: <info> (wlan1): supplicant
connection state: scanning -> associating
Nov 8 20:03:34 office wpa_supplicant[1491]: Association request to the
driver failed
Nov 8 20:03:39 office wpa_supplicant[1491]: Authentication with
00:a0:c5:5d:36:ce timed out.
Nov 8 20:03:39 office NetworkManager: <info> (wlan1): supplicant
connection state: associating -> disconnected
Nov 8 20:03:39 office NetworkManager: <info> (wlan1): supplicant
connection state: disconnected -> scanning
Nov 8 20:03:45 office wpa_supplicant[1491]: CTRL-EVENT-SCAN-RESULTS
Nov 8 20:03:45 office wpa_supplicant[1491]: Trying to associate with
00:a0:c5:5d:36:ce (SSID='OpenNetwork' freq=2452 MHz)
Nov 8 20:03:45 office NetworkManager: <info> (wlan1): supplicant
connection state: scanning -> associating
Nov 8 20:03:46 office wpa_supplicant[1491]: Association request to the
driver failed
Nov 8 20:03:51 office wpa_supplicant[1491]: Authentication with
00:a0:c5:5d:36:ce timed out.
Nov 8 20:03:51 office NetworkManager: <info> (wlan1): supplicant
connection state: associating -> disconnected
Nov 8 20:03:51 office NetworkManager: <info> (wlan1): supplicant
connection state: disconnected -> scanning
Nov 8 20:03:57 office wpa_supplicant[1491]: CTRL-EVENT-SCAN-RESULTS
Nov 8 20:03:57 office wpa_supplicant[1491]: Trying to associate with
00:a0:c5:5d:36:ce (SSID='OpenNetwork' freq=2452 MHz)
Nov 8 20:03:57 office NetworkManager: <info> (wlan1): supplicant
connection state: scanning -> associating
Nov 8 20:03:57 office wpa_supplicant[1491]: Association request to the
driver failed
Nov 8 20:04:02 office wpa_supplicant[1491]: Authentication with
00:a0:c5:5d:36:ce timed out.
Nov 8 20:04:02 office NetworkManager: <info> (wlan1): supplicant
connection state: associating -> disconnected
Nov 8 20:04:03 office wpa_supplicant[1491]: CTRL-EVENT-SCAN-RESULTS
Nov 8 20:04:03 office wpa_supplicant[1491]: Trying to associate with
00:a0:c5:5d:36:ce (SSID='OpenNetwork' freq=2452 MHz)
Nov 8 20:04:03 office NetworkManager: <info> (wlan1): supplicant
connection state: disconnected -> associating
Nov 8 20:04:04 office wpa_supplicant[1491]: Association request to the
driver failed
Nov 8 20:04:09 office wpa_supplicant[1491]: Authentication with
00:a0:c5:5d:36:ce timed out.
Nov 8 20:04:09 office NetworkManager: <info> (wlan1): supplicant
connection state: associating -> disconnected
Nov 8 20:04:09 office NetworkManager: <info> (wlan1): supplicant
connection state: disconnected -> scanning
Nov 8 20:04:10 office NetworkManager: <info> wlan1: link timed out.
Nov 8 20:04:15 office wpa_supplicant[1491]: CTRL-EVENT-SCAN-RESULTS
Nov 8 20:04:15 office wpa_supplicant[1491]: Trying to associate with
00:a0:c5:5d:36:ce (SSID='OpenNetwork' freq=2452 MHz)
Nov 8 20:04:15 office NetworkManager: <info> (wlan1): supplicant
connection state: scanning -> associating
Nov 8 20:04:15 office wpa_supplicant[1491]: Association request to the
driver failed
Nov 8 20:04:17 office NetworkManager: <info> Activation
(wlan1/wireless): association took too long, failing activation.
Nov 8 20:04:17 office NetworkManager: <info> (wlan1): device state
change: 5 -> 9 (reason 11)
Nov 8 20:04:17 office NetworkManager: <info> Activation (wlan1) failed
for access point (OpenNetwork)
Nov 8 20:04:17 office NetworkManager: <info> Marking connection 'Auto
OpenNetwork' invalid.
Nov 8 20:04:17 office NetworkManager: <info> Activation (wlan1)
failed.
Nov 8 20:04:17 office NetworkManager: <info> (wlan1): device state
change: 9 -> 3 (reason 0)
Nov 8 20:04:17 office NetworkManager: <info> (wlan1): deactivating
device (reason: 0).
Nov 8 20:04:17 office NetworkManager: <info> Policy set 'Auto
eth0' (eth0) as default for routing and DNS.
Nov 8 20:04:20 office wpa_supplicant[1491]: Authentication with
00:00:00:00:00:00 timed out.











--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 
Old 11-08-2009, 09:00 PM
NoOp
 
Default Wireless: network detected, but no connection

On 11/08/2009 11:26 AM, Frank Lorenz wrote:
> Nov 8 20:04:20 office wpa_supplicant[1491]: Authentication with
> 00:00:00:00:00:00 timed out.

Looks like it's trying to do wpa authentication. What does
/var/log/wicd.log show?
(Note: *don't post* and information here from the log that may contain
sensitive info) - to view:

$ sudo su
# cd /var/log/widc/
# cat wicd.log
(or 'gedit wicd.log')
# exit
$





--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 
Old 11-08-2009, 10:24 PM
Frank Lorenz
 
Default Wireless: network detected, but no connection

Hi!

> Looks like it's trying to do wpa authentication.

OK, the previous log is from the PC running NetworkManager. I noticed
the WPA authentication attempt and I wonder about that. The networks ?im
trying to connect do not require WPA auth.

> What does
> /var/log/wicd.log show?

Here the log from the machine that is running wicd instead of NM.
wlan2 (00:a0:c5:62:7e:e4) is the Zyxel B-220 usb-stick.
It looks like the wlan2 obtains an IP (192.168.10.32), then it
disconnects for some reason and reconnects... in an endless loop.


2009/11/09 00:09:49 :: ---------------------------
2009/11/09 00:09:49 :: wicd initializing...
2009/11/09 00:09:49 :: ---------------------------
2009/11/09 00:09:49 :: wicd is version 1.6.1 426
2009/11/09 00:09:49 :: setting backend to external
2009/11/09 00:09:49 :: trying to load backend external
2009/11/09 00:09:49 :: successfully loaded backend external
2009/11/09 00:09:49 :: trying to load backend external
2009/11/09 00:09:49 :: successfully loaded backend external
2009/11/09 00:09:49 :: Automatically detected wireless interface wlan2
2009/11/09 00:09:49 :: setting wireless interface wlan2
2009/11/09 00:09:49 :: automatically detected wired interface eth0
2009/11/09 00:09:49 :: setting wired interface eth0
2009/11/09 00:09:49 :: setting wpa driver wext
2009/11/09 00:09:49 :: setting use global dns to False
2009/11/09 00:09:49 :: setting global dns
2009/11/09 00:09:49 :: global dns servers are None None None
2009/11/09 00:09:49 :: domain is None
2009/11/09 00:09:49 :: search domain is None
2009/11/09 00:09:49 :: setting automatically reconnect when connection
drops True
2009/11/09 00:09:49 :: Setting dhcp client to 1
2009/11/09 00:09:49 :: Wireless configuration file found...
2009/11/09 00:09:49 :: Wired configuration file found...
2009/11/09 00:09:49 :: chmoding configuration files 0600...
2009/11/09 00:09:49 :: chowning configuration files root:root...
2009/11/09 00:09:49 :: Using wireless interface...wlan2
2009/11/09 00:09:49 :: Using wired interface...eth0
2009/11/09 00:09:55 :: Autoconnecting...
2009/11/09 00:09:55 :: No wired connection present, attempting to
autoconnect to wireless network
2009/11/09 00:09:56 :: trying to automatically connect to...OpenNetwork
2009/11/09 00:09:56 :: Connecting to wireless network OpenNetwork
2009/11/09 00:09:56 :: Putting interface down
2009/11/09 00:09:56 :: Releasing DHCP leases...
2009/11/09 00:09:56 :: Setting false IP...
2009/11/09 00:09:56 :: Stopping wpa_supplicant
2009/11/09 00:09:56 :: Flushing the routing table...
2009/11/09 00:09:56 :: Putting interface up...
2009/11/09 00:09:57 :: Running DHCP
2009/11/09 00:09:57 :: Internet Systems Consortium DHCP Client V3.1.2
2009/11/09 00:09:57 :: Copyright 2004-2008 Internet Systems Consortium.
2009/11/09 00:09:57 :: All rights reserved.
2009/11/09 00:09:57 :: For info, please visit
http://www.isc.org/sw/dhcp/
2009/11/09 00:09:57 ::
2009/11/09 00:09:58 :: Listening on LPF/wlan2/00:a0:c5:62:7e:e4
2009/11/09 00:09:58 :: Sending on LPF/wlan2/00:a0:c5:62:7e:e4
2009/11/09 00:09:58 :: Sending on Socket/fallback
2009/11/09 00:09:58 :: DHCPDISCOVER on wlan2 to 255.255.255.255 port 67
interval 3
2009/11/09 00:09:58 :: DHCPOFFER of 192.168.10.32 from 192.168.10.1
2009/11/09 00:09:58 :: DHCPREQUEST of 192.168.10.32 on wlan2 to
255.255.255.255 port 67
2009/11/09 00:09:58 :: DHCPACK of 192.168.10.32 from 192.168.10.1
2009/11/09 00:09:58 :: * Stopping NTP server ntpd
2009/11/09 00:09:58 :: ...done.
2009/11/09 00:10:00 :: * Starting NTP server ntpd
2009/11/09 00:10:00 :: ...done.
2009/11/09 00:10:00 :: bound to 192.168.10.32 -- renewal in 43002
seconds.
2009/11/09 00:10:00 :: DHCP connection successful
2009/11/09 00:10:00 :: Connecting thread exiting.
2009/11/09 00:10:00 :: Sending connection attempt result Success
2009/11/09 00:10:07 :: Connecting to wireless network OpenNetwork
2009/11/09 00:10:07 :: Putting interface down
2009/11/09 00:10:07 :: Releasing DHCP leases...
2009/11/09 00:10:07 :: Setting false IP...
2009/11/09 00:10:07 :: Stopping wpa_supplicant
2009/11/09 00:10:07 :: Flushing the routing table...
2009/11/09 00:10:07 :: Putting interface up...
2009/11/09 00:10:07 :: Running DHCP
2009/11/09 00:10:07 :: Internet Systems Consortium DHCP Client V3.1.2
2009/11/09 00:10:07 :: Copyright 2004-2008 Internet Systems Consortium.
2009/11/09 00:10:07 :: All rights reserved.
2009/11/09 00:10:07 :: For info, please visit
http://www.isc.org/sw/dhcp/
2009/11/09 00:10:07 ::
2009/11/09 00:10:08 :: Listening on LPF/wlan2/00:a0:c5:62:7e:e4
2009/11/09 00:10:08 :: Sending on LPF/wlan2/00:a0:c5:62:7e:e4
2009/11/09 00:10:08 :: Sending on Socket/fallback
2009/11/09 00:10:11 :: DHCPDISCOVER on wlan2 to 255.255.255.255 port 67
interval 4
2009/11/09 00:10:11 :: DHCPOFFER of 192.168.10.32 from 192.168.10.1
2009/11/09 00:10:11 :: DHCPREQUEST of 192.168.10.32 on wlan2 to
255.255.255.255 port 67
2009/11/09 00:10:11 :: DHCPACK of 192.168.10.32 from 192.168.10.1
2009/11/09 00:10:11 :: * Stopping NTP server ntpd
2009/11/09 00:10:11 :: ...done.
2009/11/09 00:10:13 :: * Starting NTP server ntpd
2009/11/09 00:10:13 :: ...done.
2009/11/09 00:10:13 :: bound to 192.168.10.32 -- renewal in 37251
seconds.
2009/11/09 00:10:13 :: DHCP connection successful
2009/11/09 00:10:13 :: Connecting thread exiting.
2009/11/09 00:10:13 :: Sending connection attempt result Success
2009/11/09 00:10:16 :: Autoconnecting...
2009/11/09 00:10:16 :: No wired connection present, attempting to
autoconnect to wireless network
2009/11/09 00:10:17 :: trying to automatically connect to...OpenNetwork
2009/11/09 00:10:17 :: Connecting to wireless network OpenNetwork
2009/11/09 00:10:17 :: Putting interface down
2009/11/09 00:10:17 :: Releasing DHCP leases...
2009/11/09 00:10:17 :: Setting false IP...
2009/11/09 00:10:17 :: Stopping wpa_supplicant
2009/11/09 00:10:17 :: Flushing the routing table...
2009/11/09 00:10:17 :: Putting interface up...
2009/11/09 00:10:17 :: Running DHCP
2009/11/09 00:10:18 :: Internet Systems Consortium DHCP Client V3.1.2
2009/11/09 00:10:18 :: Copyright 2004-2008 Internet Systems Consortium.
2009/11/09 00:10:18 :: All rights reserved.
2009/11/09 00:10:18 :: For info, please visit
http://www.isc.org/sw/dhcp/
2009/11/09 00:10:18 ::
2009/11/09 00:10:19 :: Listening on LPF/wlan2/00:a0:c5:62:7e:e4
2009/11/09 00:10:19 :: Sending on LPF/wlan2/00:a0:c5:62:7e:e4
2009/11/09 00:10:19 :: Sending on Socket/fallback
2009/11/09 00:10:21 :: DHCPDISCOVER on wlan2 to 255.255.255.255 port 67
interval 5
2009/11/09 00:10:21 :: DHCPOFFER of 192.168.10.32 from 192.168.10.1
2009/11/09 00:10:21 :: DHCPREQUEST of 192.168.10.32 on wlan2 to
255.255.255.255 port 67
2009/11/09 00:10:21 :: DHCPACK of 192.168.10.32 from 192.168.10.1
2009/11/09 00:10:21 :: * Stopping NTP server ntpd
2009/11/09 00:10:21 :: ...done.
2009/11/09 00:10:23 :: * Starting NTP server ntpd
2009/11/09 00:10:23 :: ...done.
2009/11/09 00:10:23 :: bound to 192.168.10.32 -- renewal in 34352
seconds.
2009/11/09 00:10:23 :: DHCP connection successful
2009/11/09 00:10:23 :: Connecting thread exiting.
2009/11/09 00:10:24 :: Sending connection attempt result Success
2009/11/09 00:10:29 :: Autoconnecting...
2009/11/09 00:10:29 :: No wired connection present, attempting to
autoconnect to wireless network
2009/11/09 00:10:30 :: trying to automatically connect to...OpenNetwork
2009/11/09 00:10:30 :: Connecting to wireless network OpenNetwork
2009/11/09 00:10:30 :: Putting interface down
2009/11/09 00:10:30 :: Releasing DHCP leases...
2009/11/09 00:10:30 :: Setting false IP...
2009/11/09 00:10:30 :: Stopping wpa_supplicant
2009/11/09 00:10:30 :: Flushing the routing table...
2009/11/09 00:10:30 :: Putting interface up...
2009/11/09 00:10:31 :: Running DHCP
2009/11/09 00:10:31 :: Internet Systems Consortium DHCP Client V3.1.2
2009/11/09 00:10:31 :: Copyright 2004-2008 Internet Systems Consortium.
2009/11/09 00:10:31 :: All rights reserved.
2009/11/09 00:10:31 :: For info, please visit
http://www.isc.org/sw/dhcp/
2009/11/09 00:10:31 ::
2009/11/09 00:10:32 :: Listening on LPF/wlan2/00:a0:c5:62:7e:e4
2009/11/09 00:10:32 :: Sending on LPF/wlan2/00:a0:c5:62:7e:e4
2009/11/09 00:10:32 :: Sending on Socket/fallback
2009/11/09 00:10:35 :: DHCPDISCOVER on wlan2 to 255.255.255.255 port 67
interval 5
2009/11/09 00:10:35 :: DHCPOFFER of 192.168.10.32 from 192.168.10.1
2009/11/09 00:10:35 :: DHCPREQUEST of 192.168.10.32 on wlan2 to
255.255.255.255 port 67
2009/11/09 00:10:35 :: DHCPACK of 192.168.10.32 from 192.168.10.1
2009/11/09 00:10:35 :: * Stopping NTP server ntpd
2009/11/09 00:10:35 :: ...done.
2009/11/09 00:10:37 :: * Starting NTP server ntpd
2009/11/09 00:10:37 :: ...done.

(....)



--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 
Old 11-08-2009, 11:10 PM
NoOp
 
Default Wireless: network detected, but no connection

On 11/08/2009 03:24 PM, Frank Lorenz wrote:
> Hi!
>
>> Looks like it's trying to do wpa authentication.
>
> OK, the previous log is from the PC running NetworkManager. I noticed
> the WPA authentication attempt and I wonder about that. The networks ?im
> trying to connect do not require WPA auth.
>
>> What does
>> /var/log/wicd.log show?
>
> Here the log from the machine that is running wicd instead of NM.
> wlan2 (00:a0:c5:62:7e:e4) is the Zyxel B-220 usb-stick.
> It looks like the wlan2 obtains an IP (192.168.10.32), then it
> disconnects for some reason and reconnects... in an endless loop.
>

On my wireless laptop (9.10) I've been testing with NM (I normally use
wicd, but thought I'd give NM a try) & only have wpa2 set up. I can test
without a little later & also w/wicd. But I also use a fixed IP as I
seem to recall that I was having DHCP issues as well (I'll try reverting
shortly, but that system is currently in use by another user). Can you
temporarily set to a fixed IP to see if it's a DHCP issue?


--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 
Old 11-08-2009, 11:18 PM
"H.S."
 
Default Wireless: network detected, but no connection

NoOp wrote:
>
> On my wireless laptop (9.10) I've been testing with NM (I normally use
> wicd, but thought I'd give NM a try) & only have wpa2 set up. I can test

I had started to use wicd a while back, but I am now back to nm because
wicd has no feature to deal with vpn connections. (sorry for going OT a
bit).

I recall having switched to wicd because nm couldn't deal with wpa2 at
that time or some such problem. Not sure if it is still the case,
haven't tested it yet in that scenario.




--

Please reply to this list only. I read this list on its corresponding
newsgroup on gmane.org. Replies sent to my email address are just
filtered to a folder in my mailbox and get periodically deleted without
ever having been read.


--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 
Old 11-08-2009, 11:39 PM
NoOp
 
Default Wireless: network detected, but no connection

On 11/08/2009 04:18 PM, H.S. wrote:
> NoOp wrote:
>>
>> On my wireless laptop (9.10) I've been testing with NM (I normally use
>> wicd, but thought I'd give NM a try) & only have wpa2 set up. I can test
>
> I had started to use wicd a while back, but I am now back to nm because
> wicd has no feature to deal with vpn connections. (sorry for going OT a
> bit).
>
> I recall having switched to wicd because nm couldn't deal with wpa2 at
> that time or some such problem. Not sure if it is still the case,
> haven't tested it yet in that scenario.
>

Wicd works just fine with wpa2. NM (9.10 version) is working just fine
with wpa2 also & yes you're detracting from the thread :-)

Note to Frank: just tested w/NM & wpa2 w/DHCP & that seems to be working
fine. Once the other users are off the router (a few hours I'm told)
I'll isolate it & try testing w/no security set.





--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 
Old 11-09-2009, 09:23 AM
Ian Coetzee
 
Default Wireless: network detected, but no connection

On Sun, Nov 8, 2009 at 9:26 PM, Frank Lorenz <mailinglists@lavabit.com> wrote:
<snip>
> wlan1 * * Scan completed :
> * * * * *Cell 01 - Address: 00:A0:C5:5D:36:CE
> * * * * * * * * * *ESSID:"OpenNetwork"
> * * * * * * * * * *Mode:Master
> * * * * * * * * * *Channel:9
> * * * * * * * * * *Bit Rates:1 Mb/s
> * * * * * * * * * *Bit Rates:2 Mb/s
> * * * * * * * * * *Bit Rates:5.5 Mb/s
> * * * * * * * * * *Bit Rates:11 Mb/s
> * * * * * * * * * *Encryption keyff
> * * * * * * * * * *Quality=24/128 *Signal level=-90 dBm *Noise
> level=-96 dBm
<snip>
> Nov *8 20:03:23 office wpa_supplicant[1491]: Association request to the
> driver failed
> Nov *8 20:03:28 office wpa_supplicant[1491]: Authentication with
> 00:a0:c5:5d:36:ce timed out.

Looking at the above extracts it would seem that the wireless signal
you are picking up is a bit low.

-90 is about the connection threshold for 2.4Ghz (it does depend on
the sensitivity of the reciever)

How close are you to the wireless AP

In windows, what does the signal strength look like at the same
location of those machines?

Regards
Ian

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 
Old 11-09-2009, 10:25 AM
Frank Lorenz
 
Default Wireless: network detected, but no connection

wicd & static IP gives the same behavior: connecting and disconnecting a
second later.
Here the log:

2009/11/09 12:00:00 :: Connecting to wireless network OpenNetwork
2009/11/09 12:00:00 :: Putting interface down
2009/11/09 12:00:00 :: Releasing DHCP leases...
2009/11/09 12:00:00 :: Setting false IP...
2009/11/09 12:00:00 :: Stopping wpa_supplicant
2009/11/09 12:00:00 :: Flushing the routing table...
2009/11/09 12:00:00 :: Putting interface up...
2009/11/09 12:00:01 :: Setting static IP : 192.168.10.32
2009/11/09 12:00:01 :: Setting default gateway : 192.168.10.1
2009/11/09 12:00:01 :: Verifying AP association
2009/11/09 12:00:02 :: Connecting thread exiting.
2009/11/09 12:00:02 :: Sending connection attempt result Success


For information, here is the log from a laptop (ubuntu 9.10) that
successfully connects to the same network (using NM):

Nov 9 12:13:00 verde-laptop NetworkManager: <info> (wlan0): device
state change: 8 -> 3 (reason 0)
Nov 9 12:13:00 verde-laptop NetworkManager: <info> (wlan0):
deactivating device (reason: 0).
Nov 9 12:13:00 verde-laptop NetworkManager: <info> (wlan0): canceled
DHCP transaction, dhcp client pid 2090
Nov 9 12:13:00 verde-laptop NetworkManager: <WARN> check_one_route():
(wlan0) error -34 returned from rtnl_route_del(): Sucess#012
Nov 9 12:13:00 verde-laptop NetworkManager: <info> Activation (wlan0)
starting connection 'Auto OpenNetwork'
Nov 9 12:13:00 verde-laptop NetworkManager: <info> (wlan0): device
state change: 3 -> 4 (reason 0)
Nov 9 12:13:00 verde-laptop NetworkManager: <info> Activation (wlan0)
Stage 1 of 5 (Device Prepare) scheduled...
Nov 9 12:13:00 verde-laptop NetworkManager: <info> Activation (wlan0)
Stage 1 of 5 (Device Prepare) started...
Nov 9 12:13:00 verde-laptop NetworkManager: <info> Activation (wlan0)
Stage 2 of 5 (Device Configure) scheduled...
Nov 9 12:13:00 verde-laptop NetworkManager: <info> Activation (wlan0)
Stage 1 of 5 (Device Prepare) complete.
Nov 9 12:13:00 verde-laptop NetworkManager: <info> Activation (wlan0)
Stage 2 of 5 (Device Configure) starting...
Nov 9 12:13:00 verde-laptop NetworkManager: <info> (wlan0): device
state change: 4 -> 5 (reason 0)
Nov 9 12:13:00 verde-laptop NetworkManager: <info> Activation
(wlan0/wireless): connection 'Auto OpenNetwork' requires no security.
No secrets needed.
Nov 9 12:13:00 verde-laptop avahi-daemon[636]: Withdrawing address
record for 192.168.10.12 on wlan0.
Nov 9 12:13:00 verde-laptop wpa_supplicant[693]:
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Nov 9 12:13:00 verde-laptop avahi-daemon[636]: Leaving mDNS multicast
group on interface wlan0.IPv4 with address 192.168.10.12.
Nov 9 12:13:00 verde-laptop avahi-daemon[636]: Interface wlan0.IPv4 no
longer relevant for mDNS.
Nov 9 12:13:00 verde-laptop NetworkManager: <info> Config: added
'ssid' value 'OpenNetwork'
Nov 9 12:13:00 verde-laptop NetworkManager: <info> Config: added
'scan_ssid' value '1'
Nov 9 12:13:00 verde-laptop NetworkManager: <info> Config: added
'key_mgmt' value 'NONE'
Nov 9 12:13:00 verde-laptop NetworkManager: <info> Activation (wlan0)
Stage 2 of 5 (Device Configure) complete.
Nov 9 12:13:00 verde-laptop NetworkManager: <info> (wlan0): supplicant
connection state: completed -> disconnected
Nov 9 12:13:00 verde-laptop NetworkManager: <info> Config: set
interface ap_scan to 1
Nov 9 12:13:00 verde-laptop wpa_supplicant[693]: Failed to initiate AP
scan.
Nov 9 12:13:00 verde-laptop NetworkManager: <info> (wlan0): supplicant
connection state: disconnected -> scanning
Nov 9 12:13:11 verde-laptop wpa_supplicant[693]:
CTRL-EVENT-SCAN-RESULTS
Nov 9 12:13:11 verde-laptop wpa_supplicant[693]: Trying to associate
with 00:a0:c5:5d:36:ce (SSID='OpenNetwork' freq=2452 MHz)
Nov 9 12:13:11 verde-laptop wpa_supplicant[693]: Association request to
the driver failed
Nov 9 12:13:11 verde-laptop NetworkManager: <info> (wlan0): supplicant
connection state: scanning -> associating
Nov 9 12:13:11 verde-laptop wpa_supplicant[693]: Associated with
00:a0:c5:5d:36:ce
Nov 9 12:13:11 verde-laptop wpa_supplicant[693]: CTRL-EVENT-CONNECTED -
Connection to 00:a0:c5:5d:36:ce completed (reauth) [id=0 id_str=]
Nov 9 12:13:11 verde-laptop NetworkManager: <info> (wlan0): supplicant
connection state: associating -> associated
Nov 9 12:13:11 verde-laptop NetworkManager: <info> (wlan0): supplicant
connection state: associated -> completed
Nov 9 12:13:11 verde-laptop NetworkManager: <info> Activation
(wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected
to wireless network 'OpenNetwork'.
Nov 9 12:13:11 verde-laptop NetworkManager: <info> Activation (wlan0)
Stage 3 of 5 (IP Configure Start) scheduled.
Nov 9 12:13:11 verde-laptop NetworkManager: <info> Activation (wlan0)
Stage 3 of 5 (IP Configure Start) started...
Nov 9 12:13:11 verde-laptop NetworkManager: <info> (wlan0): device
state change: 5 -> 7 (reason 0)
Nov 9 12:13:11 verde-laptop NetworkManager: <info> Activation (wlan0)
Beginning DHCP transaction (timeout in 45 seconds)
Nov 9 12:13:11 verde-laptop dhclient: Internet Systems Consortium DHCP
Client V3.1.2
Nov 9 12:13:11 verde-laptop dhclient: Copyright 2004-2008 Internet
Systems Consortium.
Nov 9 12:13:11 verde-laptop dhclient: All rights reserved.
Nov 9 12:13:11 verde-laptop dhclient: For info, please visit
http://www.isc.org/sw/dhcp/
Nov 9 12:13:11 verde-laptop dhclient:
Nov 9 12:13:12 verde-laptop NetworkManager: <info> dhclient started
with pid 2219
Nov 9 12:13:12 verde-laptop NetworkManager: <info> Activation (wlan0)
Stage 4 of 5 (IP6 Configure Get) scheduled...
Nov 9 12:13:12 verde-laptop NetworkManager: <info> Activation (wlan0)
Stage 3 of 5 (IP Configure Start) complete.
Nov 9 12:13:12 verde-laptop NetworkManager: <info> Activation (wlan0)
Stage 4 of 5 (IP6 Configure Get) started...
Nov 9 12:13:12 verde-laptop NetworkManager: <info> Activation (wlan0)
Stage 4 of 5 (IP6 Configure Get) complete.
Nov 9 12:13:12 verde-laptop dhclient: Listening on
LPF/wlan0/00:90:4b:8f:a8:34
Nov 9 12:13:12 verde-laptop dhclient: Sending on
LPF/wlan0/00:90:4b:8f:a8:34
Nov 9 12:13:12 verde-laptop dhclient: Sending on Socket/fallback
Nov 9 12:13:12 verde-laptop NetworkManager: <info> DHCP: device wlan0
state changed normal exit -> preinit
Nov 9 12:13:13 verde-laptop ntpd[2201]: sendto(129.132.2.21) (fd=21):
Invalid argument
Nov 9 12:13:13 verde-laptop wpa_supplicant[693]:
CTRL-EVENT-SCAN-RESULTS
Nov 9 12:13:15 verde-laptop dhclient: DHCPREQUEST of 192.168.10.12 on
wlan0 to 255.255.255.255 port 67
Nov 9 12:13:15 verde-laptop dhclient: DHCPACK of 192.168.10.12 from
192.168.10.1
Nov 9 12:13:15 verde-laptop NetworkManager: <info> DHCP: device wlan0
state changed preinit -> reboot
Nov 9 12:13:15 verde-laptop NetworkManager: <info> Activation (wlan0)
Stage 4 of 5 (IP4 Configure Get) scheduled...
Nov 9 12:13:15 verde-laptop NetworkManager: <info> Activation (wlan0)
Stage 4 of 5 (IP4 Configure Get) started...
Nov 9 12:13:15 verde-laptop NetworkManager: <info> address
192.168.10.12
Nov 9 12:13:15 verde-laptop NetworkManager: <info> prefix 24
(255.255.255.0)
Nov 9 12:13:15 verde-laptop NetworkManager: <info> gateway
192.168.10.1
Nov 9 12:13:15 verde-laptop NetworkManager: <info> nameserver
'192.168.10.1'
Nov 9 12:13:15 verde-laptop NetworkManager: <info> Activation (wlan0)
Stage 5 of 5 (IP Configure Commit) scheduled...
Nov 9 12:13:15 verde-laptop NetworkManager: <info> Activation (wlan0)
Stage 4 of 5 (IP4 Configure Get) complete.
Nov 9 12:13:15 verde-laptop NetworkManager: <info> Activation (wlan0)
Stage 5 of 5 (IP Configure Commit) started...
Nov 9 12:13:15 verde-laptop avahi-daemon[636]: Joining mDNS multicast
group on interface wlan0.IPv4 with address 192.168.10.12.
Nov 9 12:13:15 verde-laptop avahi-daemon[636]: New relevant interface
wlan0.IPv4 for mDNS.
Nov 9 12:13:15 verde-laptop avahi-daemon[636]: Registering new address
record for 192.168.10.12 on wlan0.IPv4.
Nov 9 12:13:15 verde-laptop dhclient: bound to 192.168.10.12 -- renewal
in 41029 seconds.
Nov 9 12:13:15 verde-laptop ntpd[2201]: sendto(91.189.94.4) (fd=21):
Network is unreachable
Nov 9 12:13:16 verde-laptop NetworkManager: <info> (wlan0): device
state change: 7 -> 8 (reason 0)
Nov 9 12:13:16 verde-laptop NetworkManager: <info> Policy set 'Auto
OpenNetwork' (wlan0) as default for routing and DNS.
Nov 9 12:13:16 verde-laptop NetworkManager: <info> Activation (wlan0)
successful, device activated.
Nov 9 12:13:16 verde-laptop NetworkManager: <info> Activation (wlan0)
Stage 5 of 5 (IP Configure Commit) complete.
Nov 9 12:13:16 verde-laptop ntpd[2201]: ntpd exiting on signal 15
Nov 9 12:13:17 verde-laptop ntpdate[2301]: adjust time server
129.132.2.21 offset -0.000258 sec
Nov 9 12:13:17 verde-laptop ntpd[2329]: ntpd 4.2.4p6@1.1549-o Thu Oct
22 21:58:37 UTC 2009 (1)
Nov 9 12:13:17 verde-laptop ntpd[2330]: precision = 1.000 usec
Nov 9 12:13:17 verde-laptop ntpd[2330]: Listening on interface #0
wildcard, 0.0.0.0#123 Disabled
Nov 9 12:13:17 verde-laptop ntpd[2330]: Listening on interface #1
wildcard, ::#123 Disabled
Nov 9 12:13:17 verde-laptop ntpd[2330]: Listening on interface #2
lo, ::1#123 Enabled
Nov 9 12:13:17 verde-laptop ntpd[2330]: Listening on interface #3
wlan0, fe80::290:4bff:fe8f:a834#123 Enabled
Nov 9 12:13:17 verde-laptop ntpd[2330]: Listening on interface #4 lo,
127.0.0.1#123 Enabled
Nov 9 12:13:17 verde-laptop ntpd[2330]: Listening on interface #5
wlan0, 192.168.10.12#123 Enabled
Nov 9 12:13:17 verde-laptop ntpd[2330]: kernel time sync status 2040
Nov 9 12:13:17 verde-laptop ntpd[2330]: frequency initialized -33.295
PPM from /var/lib/ntp/ntp.drift



--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 
Old 11-09-2009, 10:41 AM
Frank Lorenz
 
Default Wireless: network detected, but no connection

On Mon, 2009-11-09 at 12:23 +0200, Ian Coetzee wrote:

> Looking at the above extracts it would seem that the wireless signal
> you are picking up is a bit low.
>
> -90 is about the connection threshold for 2.4Ghz (it does depend on
> the sensitivity of the reciever)

Hmm... interesting observation! The NM indicates almost full-scale
signal level.

> How close are you to the wireless AP

Approximately 4 meters and no obstacles between AP and clients.

> In windows, what does the signal strength look like at the same
> location of those machines?

Signal strenght: Excellent






--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 
Old 11-09-2009, 10:50 AM
Ian Coetzee
 
Default Wireless: network detected, but no connection

On Mon, Nov 9, 2009 at 1:41 PM, Frank Lorenz <mailinglists@lavabit.com> wrote:
> On Mon, 2009-11-09 at 12:23 +0200, Ian Coetzee wrote:
>
>> Looking at the above extracts it would seem that the wireless signal
>> you are picking up is a bit low.
>>
>> -90 is about the connection threshold for 2.4Ghz (it does depend on
>> the sensitivity of the reciever)
>
> Hmm... interesting observation! The NM indicates almost full-scale
> signal level.

yes working for a wireless ISP has its perks (like noticing a low
signal strength )

>
>> How close are you to the wireless AP
>
> Approximately 4 meters and no obstacles between AP and clients.

Hmm... then I am out of ideas...

>
>> In windows, what does the signal strength look like at the same
>> location of those machines?
>
> Signal strenght: Excellent

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 

Thread Tools




All times are GMT. The time now is 12:17 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org