LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Wicd has stopped finding wireless access point. (https://www.linuxquestions.org/questions/slackware-14/wicd-has-stopped-finding-wireless-access-point-930932/)

daz__ 02-23-2012 03:07 PM

Wicd has stopped finding wireless access point.
 
Hello LQ,

Been running Slackware a year or more and last week Wicd suddenly started dropping the wireless connection and is then unable to find wireless access point thereafter. After a cold boot it seem to find the access point and then runs for a while and then drops.

Last night tried to connect upstairs and it wouldn't connect but this morning on waking it had connected itself and ran for a good while but then on coming downstairs it failed to connect. The router is downstairs.

On a connect failure I have tried restarting Wicd daemon but that has no effect. A cold boot seems to be the only way to get it up and running and this is only good for a while and there doesn't seem to be a pattern except that it drops the connection.

Following is iwconfig with wireless working and connected..

Code:

bash-4.1# iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

wlan0    IEEE 802.11bg  ESSID:"Thomson3DB104" 
          Mode:Managed  Frequency:2.412 GHz  Access Point: 00:26:44:3D:B1:04 
          Bit Rate=1 Mb/s  Tx-Power=20 dBm 
          Retry  long limit:7  RTS thr:off  Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=56/70  Signal level=-54 dBm 
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:7  Missed beacon:0


Following is iwconfig with no access point scanned and when Wicd seems to be in err.

Code:

bash-4.1# iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

wlan0    IEEE 802.11bg  ESSID:off/any 
          Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated 
          Tx-Power=20 dBm 
          Retry  long limit:7  RTS thr:off  Fragment thr:off
          Encryption key:off
          Power Management:off


Following is a snippet form /var/log/messages that I think is relevent to the network issue.

Code:

Feb 23 14:09:14 dazedproductions kernel: \[  485.438727\] ADDRCONF(NETDEV_UP): eth0: link is not ready
Feb 23 14:09:14 dazedproductions kernel: \[  485.484814\] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb 23 14:09:15 dazedproductions kernel: \[  487.009692\] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Feb 23 14:09:16 dazedproductions dhcpcd\[2256\]: version 5.2.11 starting
Feb 23 14:09:16 dazedproductions dhcpcd\[2256\]: wlan0: broadcasting for a lease
Feb 23 14:09:21 dazedproductions dhcpcd\[2256\]: wlan0: offered 192.168.15.2 from 192.168.15.1
Feb 23 14:09:21 dazedproductions dhcpcd\[2256\]: wlan0: acknowledged 192.168.15.2 from 192.168.15.1
Feb 23 14:09:21 dazedproductions dhcpcd\[2256\]: wlan0: checking for 192.168.15.2
Feb 23 14:09:26 dazedproductions dhcpcd\[2256\]: wlan0: leased 192.168.15.2 for 3600 seconds
Feb 23 14:09:26 dazedproductions dhcpcd: wlan0: MTU set to 1500
Feb 23 14:09:26 dazedproductions dhcpcd\[2256\]: forked to background, child pid 2299
Feb 23 14:11:49 dazedproductions ntpd\[1638\]: Listen normally on 4 wlan0 192.168.15.2 UDP 123
Feb 23 14:11:49 dazedproductions ntpd\[1638\]: Listen normally on 5 wlan0 fe80::21f:3aff:feb5:5098 UDP 123
Feb 23 14:11:49 dazedproductions ntpd\[1638\]: peers refreshed
Feb 23 14:20:08 dazedproductions dhcpcd\[2299\]: wlan0: carrier lost
Feb 23 14:20:08 dazedproductions kernel: \[ 1139.532075\] cfg80211: Calling CRDA to update world regulatory domain
Feb 23 14:20:08 dazedproductions kernel: \[ 1139.537776\] cfg80211: World regulatory domain updated:
Feb 23 14:20:08 dazedproductions kernel: \[ 1139.537782\]    (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Feb 23 14:20:08 dazedproductions kernel: \[ 1139.537788\]    (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Feb 23 14:20:08 dazedproductions kernel: \[ 1139.537794\]    (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Feb 23 14:20:08 dazedproductions kernel: \[ 1139.537800\]    (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Feb 23 14:20:08 dazedproductions kernel: \[ 1139.537805\]    (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Feb 23 14:20:08 dazedproductions kernel: \[ 1139.537810\]    (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Feb 23 14:20:08 dazedproductions dhcpcd: wlan0: MTU restored to 1500
Feb 23 14:21:49 dazedproductions ntpd\[1638\]: Deleting interface #4 wlan0, 192.168.15.2#123, interface stats: received=0, sent=0, dropped=0, active_time=600 secs
Feb 23 14:21:49 dazedproductions ntpd\[1638\]: peers refreshed
Feb 23 14:26:58 dazedproductions kernel: \[ 1549.182616\] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
Feb 23 14:26:58 dazedproductions kernel: \[ 1549.182949\] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Feb 23 14:27:10 dazedproductions dhcpcd\[2944\]: sending signal 1 to pid 2299
Feb 23 14:27:10 dazedproductions dhcpcd\[2944\]: waiting for pid 2299 to exit
Feb 23 14:27:10 dazedproductions dhcpcd\[2299\]: received SIGHUP, releasing
Feb 23 14:27:10 dazedproductions dhcpcd\[2299\]: wlan0: removing interface
Feb 23 14:27:10 dazedproductions kernel: \[ 1562.002107\] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
Feb 23 14:27:10 dazedproductions dhcpcd\[2965\]: version 5.2.11 starting
Feb 23 14:27:11 dazedproductions dhcpcd\[2965\]: eth0: broadcasting for a lease
Feb 23 14:27:12 dazedproductions dhcpcd\[2965\]: eth0: offered 192.168.15.3 from 192.168.15.1
Feb 23 14:27:12 dazedproductions dhcpcd\[2965\]: eth0: acknowledged 192.168.15.3 from 192.168.15.1
Feb 23 14:27:12 dazedproductions dhcpcd\[2965\]: eth0: checking for 192.168.15.3
Feb 23 14:27:16 dazedproductions dhcpcd\[2965\]: eth0: leased 192.168.15.3 for 3600 seconds
Feb 23 14:27:16 dazedproductions dhcpcd: eth0: MTU set to 1500
Feb 23 14:27:16 dazedproductions dhcpcd\[2965\]: forked to background, child pid 2997
Feb 23 14:31:49 dazedproductions ntpd\[1638\]: Listen normally on 6 eth0 192.168.15.3 UDP 123
Feb 23 14:31:49 dazedproductions ntpd\[1638\]: Listen normally on 7 eth0 fe80::240:d0ff:fe97:601e UDP 123
Feb 23 14:31:49 dazedproductions ntpd\[1638\]: Deleting interface #5 wlan0, fe80::21f:3aff:feb5:5098#123, interface stats: received=0, sent=0, dropped=0, active_time=1200 secs
Feb 23 14:31:49 dazedproductions ntpd\[1638\]: peers refreshed
Feb 23 14:33:48 dazedproductions dhclient: isc-dhclient-4.2.1-P1
Feb 23 14:33:48 dazedproductions dhclient: isc-dhclient-4.2.1-P1


The following is an excerpt from a few hours of the /var/log/wicd/wicd.log

I have noticed in the middle of the following log that it is trying to use a network address that does not seem to add up. Address ranges it should be trying to lease are 192.168.15.* but I will insert a section of the log following I think may be relevent.

Code:

2012/02/22 15:55:44 :: Connecting to wireless network Thomson3DB104
2012/02/22 15:55:45 :: Putting interface down
2012/02/22 15:55:45 :: Releasing DHCP leases...
2012/02/22 15:55:45 :: Setting false IP...
2012/02/22 15:55:45 :: Stopping wpa_supplicant
2012/02/22 15:55:45 :: Flushing the routing table...
2012/02/22 15:55:45 :: Putting interface up...
2012/02/22 15:55:45 :: Generating psk...
2012/02/22 15:55:45 :: Attempting to authenticate...
2012/02/22 15:55:47 :: Running DHCP
2012/02/22 15:55:47 :: dhcpcd\[2766\]: version 5.2.11 starting
2012/02/22 15:55:47 ::
2012/02/22 15:55:47 :: dhcpcd\[2766\]: wlan0: checking for 169.254.79.86
2012/02/22 15:55:47 ::
2012/02/22 15:55:51 :: dhcpcd\[2766\]: wlan0: using IPv4LL address 169.254.79.86
2012/02/22 15:55:51 ::
2012/02/22 15:55:51 :: dhcpcd\[2766\]: forked to background, child pid 2788
2012/02/22 15:55:51 ::
2012/02/22 15:55:51 ::
2012/02/22 15:55:51 :: DHCP connection successful

Following is the larger section of the wicd.log

Code:

/var/log/wicd/wicd.log

2012/02/22 15:22:47 :: wicd initializing...
2012/02/22 15:22:47 :: ---------------------------
2012/02/22 15:22:47 :: wicd is version 1.6.2.2 463
2012/02/22 15:22:47 :: setting backend to external
2012/02/22 15:22:47 :: trying to load backend external
2012/02/22 15:22:47 :: successfully loaded backend external
2012/02/22 15:22:47 :: trying to load backend external
2012/02/22 15:22:47 :: successfully loaded backend external
2012/02/22 15:22:47 :: Automatically detected wireless interface wlan0
2012/02/22 15:22:47 :: setting wireless interface wlan0
2012/02/22 15:22:47 :: automatically detected wired interface eth0
2012/02/22 15:22:47 :: setting wired interface eth0
2012/02/22 15:22:47 :: setting wpa driver wext
2012/02/22 15:22:48 :: setting use global dns to False
2012/02/22 15:22:48 :: setting global dns
2012/02/22 15:22:48 :: global dns servers are None None None
2012/02/22 15:22:48 :: domain is None
2012/02/22 15:22:48 :: search domain is None
2012/02/22 15:22:48 :: setting automatically reconnect when connection drops True
2012/02/22 15:22:48 :: Setting dhcp client to 0
2012/02/22 15:22:49 :: Wireless configuration file found...
2012/02/22 15:22:49 :: Wired configuration file found...
2012/02/22 15:22:49 :: chmoding configuration files 0600...
2012/02/22 15:22:49 :: chowning configuration files root:root...
2012/02/22 15:22:49 :: Using wireless interface...wlan0
2012/02/22 15:22:49 :: Using wired interface...eth0
2012/02/22 15:55:41 :: hidden
2012/02/22 15:55:44 :: Connecting to wireless network Thomson3DB104
2012/02/22 15:55:45 :: Putting interface down
2012/02/22 15:55:45 :: Releasing DHCP leases...
2012/02/22 15:55:45 :: Setting false IP...
2012/02/22 15:55:45 :: Stopping wpa_supplicant
2012/02/22 15:55:45 :: Flushing the routing table...
2012/02/22 15:55:45 :: Putting interface up...
2012/02/22 15:55:45 :: Generating psk...
2012/02/22 15:55:45 :: Attempting to authenticate...
2012/02/22 15:55:47 :: Running DHCP
2012/02/22 15:55:47 :: dhcpcd\[2766\]: version 5.2.11 starting
2012/02/22 15:55:47 ::
2012/02/22 15:55:47 :: dhcpcd\[2766\]: wlan0: checking for 169.254.79.86
2012/02/22 15:55:47 ::
2012/02/22 15:55:51 :: dhcpcd\[2766\]: wlan0: using IPv4LL address 169.254.79.86
2012/02/22 15:55:51 ::
2012/02/22 15:55:51 :: dhcpcd\[2766\]: forked to background, child pid 2788
2012/02/22 15:55:51 ::
2012/02/22 15:55:51 ::
2012/02/22 15:55:51 :: DHCP connection successful
2012/02/22 15:55:51 :: Connecting thread exiting.
2012/02/22 15:55:52 :: Sending connection attempt result Success
2012/02/22 16:03:14 :: hidden
2012/02/22 17:09:26 :: hidden
2012/02/22 19:07:22 :: hidden
2012/02/22 19:29:42 :: hidden
2012/02/22 19:32:32 :: hidden
2012/02/22 19:32:58 :: hidden
2012/02/22 19:33:40 :: hidden
2012/02/22 19:35:39 :: hidden
2012/02/22 19:38:25 :: hidden
2012/02/22 19:41:41 :: hidden
2012/02/22 19:42:57 :: hidden
2012/02/22 19:50:31 :: hidden
2012/02/22 19:56:21 :: hidden
2012/02/22 20:05:11 :: hidden
2012/02/22 20:27:50 :: hidden
2012/02/22 20:33:34 :: hidden
2012/02/22 20:59:38 :: hidden
2012/02/22 21:02:14 :: hidden
2012/02/22 21:40:23 :: hidden
2012/02/22 21:43:16 :: hidden
2012/02/22 22:04:17 :: hidden
2012/02/22 22:47:26 :: hidden
2012/02/23 00:27:38 :: hidden
2012/02/23 06:12:19 :: hidden
2012/02/23 06:18:42 :: ---------------------------
2012/02/23 06:18:42 :: wicd initializing...
2012/02/23 06:18:42 :: ---------------------------
2012/02/23 06:18:42 :: wicd is version 1.6.2.2 463
2012/02/23 06:18:43 :: setting backend to external
2012/02/23 06:18:43 :: trying to load backend external
2012/02/23 06:18:43 :: successfully loaded backend external
2012/02/23 06:18:43 :: trying to load backend external
2012/02/23 06:18:43 :: successfully loaded backend external
2012/02/23 06:18:43 :: Automatically detected wireless interface wlan0
2012/02/23 06:18:43 :: setting wireless interface wlan0
2012/02/23 06:18:43 :: automatically detected wired interface eth0
2012/02/23 06:18:43 :: setting wired interface eth0
2012/02/23 06:18:44 :: setting wpa driver wext
2012/02/23 06:18:44 :: setting use global dns to False
2012/02/23 06:18:44 :: setting global dns
2012/02/23 06:18:44 :: global dns servers are None None None
2012/02/23 06:18:44 :: domain is None
2012/02/23 06:18:44 :: search domain is None
2012/02/23 06:18:44 :: setting automatically reconnect when connection drops True
2012/02/23 06:18:45 :: Setting dhcp client to 0
2012/02/23 06:18:46 :: Wireless configuration file found...
2012/02/23 06:18:46 :: Wired configuration file found...
2012/02/23 06:18:46 :: chmoding configuration files 0600...
2012/02/23 06:18:46 :: chowning configuration files root:root...
2012/02/23 06:18:46 :: Using wireless interface...wlan0
2012/02/23 06:18:46 :: Using wired interface...eth0
2012/02/23 06:18:51 :: Autoconnecting...
2012/02/23 06:18:51 :: No wired connection present, attempting to autoconnect to wireless network
2012/02/23 06:18:52 :: Unable to autoconnect, you'll have to manually connect
2012/02/23 06:18:56 :: Autoconnecting...
2012/02/23 06:18:56 :: No wired connection present, attempting to autoconnect to wireless network
2012/02/23 06:18:57 :: Unable to autoconnect, you'll have to manually connect
2012/02/23 06:19:01 :: Autoconnecting...
2012/02/23 06:19:01 :: No wired connection present, attempting to autoconnect to wireless network
2012/02/23 06:19:02 :: Unable to autoconnect, you'll have to manually connect
2012/02/23 06:19:06 :: Autoconnecting...
2012/02/23 06:19:06 :: No wired connection present, attempting to autoconnect to wireless network
2012/02/23 06:19:07 :: Unable to autoconnect, you'll have to manually connect
2012/02/23 06:22:31 :: Autoconnecting...
2012/02/23 06:22:31 :: No wired connection present, attempting to autoconnect to wireless network
2012/02/23 06:22:32 :: Unable to autoconnect, you'll have to manually connect
2012/02/23 06:22:44 :: hidden
2012/02/23 06:22:47 :: Connecting to wireless network Thomson3DB104
2012/02/23 06:22:47 :: Putting interface down
2012/02/23 06:22:47 :: Releasing DHCP leases...
2012/02/23 06:22:47 :: Setting false IP...
2012/02/23 06:22:47 :: Stopping wpa_supplicant
2012/02/23 06:22:47 :: Flushing the routing table...
2012/02/23 06:22:47 :: Putting interface up...
2012/02/23 06:22:47 :: Generating psk...
2012/02/23 06:22:47 :: Attempting to authenticate...
2012/02/23 06:22:51 :: wpa_supplicant rescan forced...
2012/02/23 06:23:28 :: wpa_supplicant authentication may have failed.
2012/02/23 06:23:28 :: Running DHCP
2012/02/23 06:23:28 :: dhcpcd\[2235\]: version 5.2.11 starting
2012/02/23 06:23:28 ::
2012/02/23 06:23:28 :: dhcpcd\[2235\]: wlan0: waiting for carrier
2012/02/23 06:23:28 ::
2012/02/23 06:23:58 :: dhcpcd\[2235\]: timed out
2012/02/23 06:23:58 ::
2012/02/23 06:23:58 :: DHCP connection failed
2012/02/23 06:23:58 :: exiting connection thread
2012/02/23 06:23:58 :: Sending connection attempt result dhcp_failed
2012/02/23 06:24:03 :: Connecting to wireless network Thomson3DB104
2012/02/23 06:24:03 :: Putting interface down
2012/02/23 06:24:03 :: Releasing DHCP leases...
2012/02/23 06:24:04 :: Setting false IP...
2012/02/23 06:24:04 :: Stopping wpa_supplicant
2012/02/23 06:24:04 :: Flushing the routing table...
2012/02/23 06:24:04 :: Putting interface up...
2012/02/23 06:24:04 :: Generating psk...
2012/02/23 06:24:04 :: Attempting to authenticate...
2012/02/23 06:24:07 :: wpa_supplicant rescan forced...
2012/02/23 06:24:44 :: wpa_supplicant authentication may have failed.
2012/02/23 06:24:44 :: Running DHCP
2012/02/23 06:24:44 :: dhcpcd\[2375\]: version 5.2.11 starting
2012/02/23 06:24:44 ::
2012/02/23 06:24:44 :: dhcpcd\[2375\]: wlan0: waiting for carrier
2012/02/23 06:24:44 ::
2012/02/23 06:25:14 :: dhcpcd\[2375\]: timed out
2012/02/23 06:25:14 ::
2012/02/23 06:25:14 :: DHCP connection failed
2012/02/23 06:25:14 :: exiting connection thread
2012/02/23 06:25:16 :: Sending connection attempt result dhcp_failed
2012/02/23 06:26:29 :: Connecting to wireless network Thomson3DB104
2012/02/23 06:26:29 :: Putting interface down
2012/02/23 06:26:29 :: Releasing DHCP leases...
2012/02/23 06:26:29 :: Setting false IP...
2012/02/23 06:26:29 :: Stopping wpa_supplicant
2012/02/23 06:26:29 :: Flushing the routing table...
2012/02/23 06:26:29 :: Putting interface up...
2012/02/23 06:26:29 :: Generating psk...
2012/02/23 06:26:29 :: Attempting to authenticate...
2012/02/23 06:26:30 :: Running DHCP
2012/02/23 06:26:30 :: dhcpcd\[2490\]: version 5.2.11 starting
2012/02/23 06:26:30 ::
2012/02/23 06:26:30 :: dhcpcd\[2490\]: wlan0: broadcasting for a lease
2012/02/23 06:26:30 ::
2012/02/23 06:26:33 :: dhcpcd\[2490\]: wlan0: offered 192.168.15.2 from 192.168.15.1
2012/02/23 06:26:33 ::
2012/02/23 06:26:33 :: dhcpcd\[2490\]: wlan0: acknowledged 192.168.15.2 from 192.168.15.1
2012/02/23 06:26:33 ::
2012/02/23 06:26:33 :: dhcpcd\[2490\]: wlan0: checking for 192.168.15.2
2012/02/23 06:26:33 ::
2012/02/23 06:26:38 :: dhcpcd\[2490\]: wlan0: leased 192.168.15.2 for 3600 seconds
2012/02/23 06:26:38 ::
2012/02/23 06:26:38 :: dhcpcd: wlan0: MTU set to 1500
2012/02/23 06:26:38 ::
2012/02/23 06:26:38 :: dhcpcd\[2490\]: forked to background, child pid 2526
2012/02/23 06:26:38 ::
2012/02/23 06:26:38 ::
2012/02/23 06:26:38 :: DHCP connection successful
2012/02/23 06:26:38 :: Connecting thread exiting.
2012/02/23 06:26:39 :: Sending connection attempt result Success
2012/02/23 14:01:59 :: ---------------------------
2012/02/23 14:01:59 :: wicd initializing...
2012/02/23 14:01:59 :: ---------------------------
2012/02/23 14:01:59 :: wicd is version 1.6.2.2 463
2012/02/23 14:01:59 :: setting backend to external
2012/02/23 14:01:59 :: trying to load backend external
2012/02/23 14:01:59 :: successfully loaded backend external
2012/02/23 14:01:59 :: trying to load backend external
2012/02/23 14:01:59 :: successfully loaded backend external
2012/02/23 14:01:59 :: Automatically detected wireless interface wlan0
2012/02/23 14:01:59 :: setting wireless interface wlan0
2012/02/23 14:02:00 :: automatically detected wired interface eth0
2012/02/23 14:02:00 :: setting wired interface eth0
2012/02/23 14:02:00 :: setting wpa driver wext
2012/02/23 14:02:00 :: setting use global dns to False
2012/02/23 14:02:00 :: setting global dns
2012/02/23 14:02:00 :: global dns servers are None None None
2012/02/23 14:02:00 :: domain is None
2012/02/23 14:02:00 :: search domain is None
2012/02/23 14:02:00 :: setting automatically reconnect when connection drops True
2012/02/23 14:02:01 :: Setting dhcp client to 0
2012/02/23 14:02:02 :: Wireless configuration file found...
2012/02/23 14:02:02 :: Wired configuration file found...
2012/02/23 14:02:02 :: chmoding configuration files 0600...
2012/02/23 14:02:02 :: chowning configuration files root:root...
2012/02/23 14:02:02 :: Using wireless interface...wlan0
2012/02/23 14:02:02 :: Using wired interface...eth0
2012/02/23 14:02:08 :: Autoconnecting...
2012/02/23 14:02:08 :: No wired connection present, attempting to autoconnect to wireless network
2012/02/23 14:02:09 :: Unable to autoconnect, you'll have to manually connect
2012/02/23 14:02:13 :: Autoconnecting...
2012/02/23 14:02:13 :: No wired connection present, attempting to autoconnect to wireless network
2012/02/23 14:02:14 :: Unable to autoconnect, you'll have to manually connect
2012/02/23 14:02:18 :: Autoconnecting...
2012/02/23 14:02:18 :: No wired connection present, attempting to autoconnect to wireless network
2012/02/23 14:02:19 :: Unable to autoconnect, you'll have to manually connect
2012/02/23 14:02:23 :: Autoconnecting...
2012/02/23 14:02:23 :: No wired connection present, attempting to autoconnect to wireless network
2012/02/23 14:02:24 :: Unable to autoconnect, you'll have to manually connect
2012/02/23 14:05:48 :: Autoconnecting...
2012/02/23 14:05:48 :: No wired connection present, attempting to autoconnect to wireless network
2012/02/23 14:05:49 :: Unable to autoconnect, you'll have to manually connect
2012/02/23 14:09:13 :: Autoconnecting...
2012/02/23 14:09:13 :: No wired connection present, attempting to autoconnect to wireless network
2012/02/23 14:09:14 :: hidden
2012/02/23 14:09:14 :: trying to automatically connect to...Thomson3DB104
2012/02/23 14:09:14 :: Connecting to wireless network Thomson3DB104
2012/02/23 14:09:14 :: Putting interface down
2012/02/23 14:09:14 :: Releasing DHCP leases...
2012/02/23 14:09:14 :: Setting false IP...
2012/02/23 14:09:14 :: Stopping wpa_supplicant
2012/02/23 14:09:14 :: Flushing the routing table...
2012/02/23 14:09:14 :: Putting interface up...
2012/02/23 14:09:14 :: Generating psk...
2012/02/23 14:09:14 :: Attempting to authenticate...
2012/02/23 14:09:16 :: Running DHCP
2012/02/23 14:09:16 :: dhcpcd\[2256\]: version 5.2.11 starting
2012/02/23 14:09:16 ::
2012/02/23 14:09:16 :: dhcpcd\[2256\]: wlan0: broadcasting for a lease
2012/02/23 14:09:16 ::
2012/02/23 14:09:21 :: dhcpcd\[2256\]: wlan0: offered 192.168.15.2 from 192.168.15.1
2012/02/23 14:09:21 ::
2012/02/23 14:09:21 :: dhcpcd\[2256\]: wlan0: acknowledged 192.168.15.2 from 192.168.15.1
2012/02/23 14:09:21 ::
2012/02/23 14:09:21 :: dhcpcd\[2256\]: wlan0: checking for 192.168.15.2
2012/02/23 14:09:21 ::
2012/02/23 14:09:26 :: dhcpcd\[2256\]: wlan0: leased 192.168.15.2 for 3600 seconds
2012/02/23 14:09:26 ::
2012/02/23 14:09:26 :: dhcpcd: wlan0: MTU set to 1500
2012/02/23 14:09:26 ::
2012/02/23 14:09:26 :: dhcpcd\[2256\]: forked to background, child pid 2299
2012/02/23 14:09:26 ::
2012/02/23 14:09:26 ::
2012/02/23 14:09:26 :: DHCP connection successful
2012/02/23 14:09:26 :: Connecting thread exiting.
2012/02/23 14:09:30 :: Sending connection attempt result Success
2012/02/23 14:20:16 :: Autoconnecting...
2012/02/23 14:20:16 :: No wired connection present, attempting to autoconnect to wireless network
2012/02/23 14:20:17 :: Unable to autoconnect, you'll have to manually connect
2012/02/23 14:20:21 :: Autoconnecting...
2012/02/23 14:20:21 :: No wired connection present, attempting to autoconnect to wireless network
2012/02/23 14:20:22 :: Unable to autoconnect, you'll have to manually connect
2012/02/23 14:20:26 :: Autoconnecting...
2012/02/23 14:20:26 :: No wired connection present, attempting to autoconnect to wireless network
2012/02/23 14:20:27 :: Unable to autoconnect, you'll have to manually connect
2012/02/23 14:20:31 :: Autoconnecting...
2012/02/23 14:20:31 :: No wired connection present, attempting to autoconnect to wireless network
2012/02/23 14:20:32 :: Unable to autoconnect, you'll have to manually connect
2012/02/23 14:23:56 :: Autoconnecting...
2012/02/23 14:23:56 :: No wired connection present, attempting to autoconnect to wireless network
2012/02/23 14:23:57 :: Unable to autoconnect, you'll have to manually connect
2012/02/23 14:27:10 :: Putting interface down
2012/02/23 14:27:10 :: Releasing DHCP leases...
2012/02/23 14:27:10 :: Setting false IP...
2012/02/23 14:27:10 :: Flushing the routing table...
2012/02/23 14:27:10 :: Putting interface up...
2012/02/23 14:27:10 :: Running DHCP
2012/02/23 14:27:10 :: dhcpcd\[2965\]: version 5.2.11 starting
2012/02/23 14:27:10 ::
2012/02/23 14:27:11 :: dhcpcd\[2965\]: eth0: broadcasting for a lease
2012/02/23 14:27:11 ::
2012/02/23 14:27:12 :: dhcpcd\[2965\]: eth0: offered 192.168.15.3 from 192.168.15.1
2012/02/23 14:27:12 ::
2012/02/23 14:27:12 :: dhcpcd\[2965\]: eth0: acknowledged 192.168.15.3 from 192.168.15.1
2012/02/23 14:27:12 ::
2012/02/23 14:27:12 :: dhcpcd\[2965\]: eth0: checking for 192.168.15.3
2012/02/23 14:27:12 ::
2012/02/23 14:27:16 :: dhcpcd\[2965\]: eth0: leased 192.168.15.3 for 3600 seconds
2012/02/23 14:27:16 ::
2012/02/23 14:27:16 :: dhcpcd: eth0: MTU set to 1500
2012/02/23 14:27:16 ::
2012/02/23 14:27:16 :: dhcpcd\[2965\]: forked to background, child pid 2997
2012/02/23 14:27:16 ::
2012/02/23 14:27:16 ::
2012/02/23 14:27:16 :: DHCP connection successful
2012/02/23 14:27:16 :: Connecting thread exiting.
2012/02/23 14:27:19 :: Sending connection attempt result Success
2012/02/23 14:33:47 :: Daemon going down, killing wicd-monitor...
2012/02/23 14:33:47 :: Removing PID file...
2012/02/23 14:33:47 :: Error in atexit._run_exitfuncs:
2012/02/23 14:33:47 :: Traceback (most recent call last):
2012/02/23 14:33:47 ::  File "/usr/lib/python2.6/atexit.py", line 24, in _run_exitfuncs
2012/02/23 14:33:47 ::    func(*targs, **kargs)
2012/02/23 14:33:47 ::  File "/usr/lib/wicd/wicd-daemon.py", line 1739, in on_exit
2012/02/23 14:33:47 ::    os.remove(wpath.pidfile)
2012/02/23 14:33:47 :: OSError: \[Errno 2\] No such file or directory: '/var/run/wicd/wicd.pid'
2012/02/23 14:33:47 :: Error in sys.exitfunc:
2012/02/23 14:33:47 :: Traceback (most recent call last):
2012/02/23 14:33:47 ::  File "/usr/lib/python2.6/atexit.py", line 24, in _run_exitfuncs
2012/02/23 14:33:47 ::    func(*targs, **kargs)
2012/02/23 14:33:47 ::  File "/usr/lib/wicd/wicd-daemon.py", line 1739, in on_exit
2012/02/23 14:33:47 ::    os.remove(wpath.pidfile)
2012/02/23 14:33:47 :: OSError: \[Errno 2\] No such file or directory: '/var/run/wicd/wicd.pid'
2012/02/23 14:33:48 :: ---------------------------
2012/02/23 14:33:48 :: wicd initializing...
2012/02/23 14:33:48 :: ---------------------------
2012/02/23 14:33:48 :: wicd is version 1.6.2.2 463
2012/02/23 14:33:48 :: setting backend to external
2012/02/23 14:33:48 :: trying to load backend external
2012/02/23 14:33:48 :: successfully loaded backend external
2012/02/23 14:33:48 :: trying to load backend external
2012/02/23 14:33:48 :: successfully loaded backend external
2012/02/23 14:33:48 :: Automatically detected wireless interface wlan0
2012/02/23 14:33:48 :: setting wireless interface wlan0
2012/02/23 14:33:48 :: automatically detected wired interface eth0
2012/02/23 14:33:48 :: setting wired interface eth0
2012/02/23 14:33:48 :: setting wpa driver wext
2012/02/23 14:33:48 :: setting use global dns to False
2012/02/23 14:33:48 :: setting global dns
2012/02/23 14:33:48 :: global dns servers are None None None
2012/02/23 14:33:48 :: domain is None
2012/02/23 14:33:48 :: search domain is None
2012/02/23 14:33:48 :: setting automatically reconnect when connection drops True
2012/02/23 14:33:48 :: Setting dhcp client to 0
2012/02/23 14:33:48 :: Wireless configuration file found...
2012/02/23 14:33:48 :: Wired configuration file found...
2012/02/23 14:33:48 :: chmoding configuration files 0600...
2012/02/23 14:33:48 :: chowning configuration files root:root...
2012/02/23 14:33:48 :: Using wireless interface...wlan0
2012/02/23 14:33:48 :: Using wired interface...eth0

So I hope this is enough nfo for someone to help me out here and try figure out what is the issue. I have considerd that it may be a hardware issue or perhaps like was suggested in another thread that the router may need a firmware update or perhaps the crack in the magnetosphere last week may have damaged some hardware. I am unsure and will try to keep an open mind for the now until I hear more.

liberalchrist 02-23-2012 04:17 PM

I'm no network whiz, but this line from your third snippet of code makes me think signal loss instead of wicd/software problem:

Feb 23 14:20:08 dazedproductions dhcpcd\[2299\]: wlan0: carrier lost

daz__ 02-23-2012 04:32 PM

Quote:

Originally Posted by liberalchrist (Post 4610461)
I'm no network whiz, but this line from your third snippet of code makes me think signal loss instead of wicd/software problem:

Feb 23 14:20:08 dazedproductions dhcpcd\[2299\]: wlan0: carrier lost

Thanks for your response liberal. Yes noticed that too. I am thinking also there is a problem with the router. Reserving judgement for a a bit though.

i find it strange wicd is requesting a lease from 169.254.79.86 when I would have expected it to try lease an address from a 192.168.15.* quad.

So is the router broadcasting an incorrect address some times. and if so why is eth0 not affected.

or

is there a file getting rewritten which wicd reads from to request an address from a paticular quad.

any way

appreciate your response

daz

Alien Bob 02-23-2012 05:12 PM

A bit of knowledge building (won't help you with your wireless issue but it will clear up things conceptually anyway):

Any address which starts with "169.254." means that the DHCP client was unable to talk to a DHCP server. The result being that the DHCP client randomly assigns the network interface a so-called "link-local" address in the range 169.254.0.0/255.255.0.0. Since all DHCP clients should know about and apply this link-local fall-back in the absense of a DHCP server, the result will be that all your computers in the local LAN will still be able to talk to each other since they all get assigned a random IP address in the same IP network range.

Eric

daz__ 02-23-2012 05:32 PM

Quote:

Originally Posted by Alien Bob (Post 4610494)
A bit of knowledge building (won't help you with your wireless issue but it will clear up things conceptually anyway):

Any address which starts with "169.254." means that the DHCP client was unable to talk to a DHCP server. The result being that the DHCP client randomly assigns the network interface a so-called "link-local" address in the range 169.254.0.0/255.255.0.0. Since all DHCP clients should know about and apply this link-local fall-back in the absense of a DHCP server, the result will be that all your computers in the local LAN will still be able to talk to each other since they all get assigned a random IP address in the same IP network range.

Eric

Wow Alien Bob,
Nice to meet you, been to your site many times.
Thank you for that bit of information. I like to think I know a little bit about networking but never knew that. thank you for the food for thought. Hmmmmm what gives then...

daz

liberalchrist 02-23-2012 05:49 PM

A question that comes to mind -- Do you have anything hardwired to the router that uses DHCP. If not, you might try plugging in directly for a while to see what happens. The lack of a carrier signal still makes me think of a weak or intermittent signal. The obvious is try to move closer, but if the hardware is failing it probably won't help.

daz__ 02-23-2012 06:08 PM

Quote:

Originally Posted by liberalchrist (Post 4610508)
A question that comes to mind -- Do you have anything hardwired to the router that uses DHCP. If not, you might try plugging in directly for a while to see what happens. The lack of a carrier signal still makes me think of a weak or intermittent signal. The obvious is try to move closer, but if the hardware is failing it probably won't help.

Hi again liberal.

I am unsure what you mean by hardwired to the router using DHCP. May I assume you mean connected via cable. At the moment there is nothing else connected to router only this laptop and that is usually the case except for one other computer which is a wired connection also using slackware. This computer is very seldom on.The laptop is wired in and there is no proplem with that connection at all. The wireless has been up and running for a couple of hours now with no problems. But that may not be for long. As I said earlier there is no patter except for the fact the it will drop the connection. This I am sure of as it has been happening for a week now. Eveything appears to work? except for the dropped connections which have no pattern and an inability to scan for the wireless access point without a cold boot.

again I appreciate your participitation


edit: Wireless dropped while posting this response.
daz

liberalchrist 02-23-2012 06:21 PM

Both wired and wireless connections are granted ip addresses by the router using DHCP. DHCP problems can be eliminated from the equation if, for the last week, wired connections have not experienced the same problem. This is a difficult proposition to test if the other computer has not been on. Another way would be to use static ip's, but that would require you to access the router configuration. Most people shouldn't toy with their router, particularly if it comes from the cable company.

daz__ 02-23-2012 06:35 PM

Quote:

Originally Posted by liberalchrist (Post 4610533)
Both wired and wireless connections are granted ip addresses by the router using DHCP. DHCP problems can be eliminated from the equation if, for the last week, wired connections have not experienced the same problem. This is a difficult proposition to test if the other computer has not been on. Another way would be to use static ip's, but that would require you to access the router configuration. Most people shouldn't toy with their router, particularly if it comes from the cable company.

Hi again liberal,

I do realize the concept of DHCP and that wireless and wired connections are granted access via the DHCP server. As I have said a few time now there is no problem with the wired connection. It has been flawless which leads me to believe there is no problem with the DHCP server. Using static IP's would achieve nothing as I would not be using the DHCP server anymore for my addressing so I fail to see what I would learn from doing that.

I will take on board what you say about using a static address but If like you pointed out earlier concerning carrier signal loss is the problem. I am unsure what static IP will do to alleviate this issue.

Again you'r input much appreciated

daz

liberalchrist 02-23-2012 07:08 PM

Wavemon (or some similar program) might help you troubleshoot the signal issue. It is available from SlackBuilds in the 13.1 repository. If you want to see what it does, here is a brief explanation: http://www.techspikes.com/2009/12/wavemon-wifi-signal-monitor/ and here is their website: http://eden-feed.erg.abdn.ac.uk/wavemon/http://eden-feed.erg.abdn.ac.uk/wavemon/.

If you can monitor the signal while you work, it may help. I don't have much more to offer, but my gut still tells me hardware problem.

daz__ 02-23-2012 07:34 PM

Quote:

Originally Posted by liberalchrist (Post 4610555)
Wavemon (or some similar program) might help you troubleshoot the signal issue. It is available from SlackBuilds in the 13.1 repository. If you want to see what it does, here is a brief explanation: http://www.techspikes.com/2009/12/wavemon-wifi-signal-monitor/ and here is their website: http://eden-feed.erg.abdn.ac.uk/wavemon/http://eden-feed.erg.abdn.ac.uk/wavemon/.

If you can monitor the signal while you work, it may help. I don't have much more to offer, but my gut still tells me hardware problem.

Nice one liberal,
You have been helping realize or not. I will give that monitor a go a see what it is trying to tell me. My gut also says hardware in some form or another.

again really appreciate your input
I will set it up tomorrow and let you know the result if any.
gone a little late here for troubleshooting so good night.

daz

daz__ 02-24-2012 09:40 AM

Quote:

Originally Posted by liberalchrist (Post 4610555)
Wavemon (or some similar program) might help you troubleshoot the signal issue. It is available from SlackBuilds in the 13.1 repository. If you want to see what it does, here is a brief explanation: http://www.techspikes.com/2009/12/wavemon-wifi-signal-monitor/ and here is their website: http://eden-feed.erg.abdn.ac.uk/wavemon/http://eden-feed.erg.abdn.ac.uk/wavemon/.

If you can monitor the signal while you work, it may help. I don't have much more to offer, but my gut still tells me hardware problem.

Right I have been running wavemon for few hours now. The wireless link has stayed up for the entire time. The link quality is reading between 51-61/70. I would guess that seems ok to me.

The signal quality is about -60 dBm. This I would class as normal for this wireless adapter. It never seemed to be that much of an issue before.

The bitrate is the one that seems a bit extreme. One minute it is reading 54Mbits/s and all of a sudden it will drop to 1Mbit/s and then back up to 54. I am fairley sure It should be reading a steady 54Mbits/s. It still doesn't tell me much about whether the problem is router or card.

Thank you again for your help and links.

If anyone has any information on software for troubleshooting routers or wireless cards I would be very grateful.

daz

trademark91 02-24-2012 12:43 PM

Which card do you have? And which kernel version are you running? There were a bunch of issues with ath9k drivers in the latest kernel, idk if that might be your problem or not, but if you have an Atheros card, you might want to look into it.

whats the output of
Code:

lspci | grep -i wireless
and
Code:

uname -r

daz__ 02-24-2012 02:33 PM

Quote:

Originally Posted by trademark91 (Post 4611176)
Which card do you have? And which kernel version are you running? There were a bunch of issues with ath9k drivers in the latest kernel, idk if that might be your problem or not, but if you have an Atheros card, you might want to look into it.

whats the output of
Code:

lspci | grep -i wireless
and
Code:

uname -r

Nice one trademark,
Thanks for joining in.

I was over on an ubuntu site earlier and some dude managed to sort a similar type of problem out by boosting the antenna signal on his router. I am not ready to go there just yet since the problem only started happening out of the blue I would like to understand the issue better. I am running a second hand achter which I am really impressed with. Ex army laptop. Impressive in design. The signal level was never the best but it was very functunionl even upstairs away form the router.

Code:

bash-4.1# lspci | grep -i wireless
03:00.0 Ethernet controller: Atheros Communications Inc. AR5001 Wireless Network Adapter

Code:

bash-4.1# uname -r
2.6.37.6-smp

I am going to upload a screencapture of wavemon as it runs in a little bit.
Never know some one may be able to make some sense of it.

Thank you again trademark for joining in

daz

daz__ 02-25-2012 02:19 AM

Hi again,

I have that screencapture of wavemon up now If someone would like to take a look and explain what I am seeing.

If you get as far as the 2 minute mark you can see where the bitrate drops to 1Mbits/s.

http://www.youtube.com/watch?v=SLoTR...1&feature=plcp

Thanks in advance

daz


All times are GMT -5. The time now is 05:08 AM.