Arch Linux

zhuk_av

Member

Registered: 2009-11-02

Posts: 36

[solved] Wicd is unable to run disconnet scripts

Since last update to 1.7.0 wicd is unable to run any of *disconnect scripts. Moreover, it hangs while connecting to ANY network if there are such fields filled in at least in one profile! Is it arch-specific bug or should it be reported to upstream?

Last edited by zhuk_av (2010-07-14 12:00:47)

Fynean

Member

Registered: 2010-01-28

Posts: 1

Re: [solved] Wicd is unable to run disconnet scripts

I found your message, because I have exactly the same Problem with wicd 1.7 and was looking for a solution.
I'm using Debian (squeeze), therefore it is not an arch-specific problem.

EDIT: I just found this Bugreport: https://bugs.launchpad.net/wicd/+bug/513540

Last edited by Fynean (2010-01-28 12:19:20)

zhuk_av

Member

Registered: 2009-11-02

Posts: 36

Re: [solved] Wicd is unable to run disconnet scripts

So, the bug was reported. Good, but I had stuck into another one. I'm not sure, is it wicd-related, since I had got something similar with NetworkManager (http://bbs.archlinux.org/viewtopic.php?id=89234). The difference with wicd is that it's able to connect after boot, but any next attempt to connect via wireless fails. Going into standby mode helps - first attempt after it is successful.

Here's dmesg after unsuccessful try:

ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlan0: direct probe to AP 00:1e:58:e5:8c:aa (try 1)
wlan0: direct probe responded
wlan0: authenticate with AP 00:1e:58:e5:8c:aa (try 1)
wlan0: authenticated
wlan0: associate with AP 00:1e:58:e5:8c:aa (try 1)
wlan0: RX ReassocResp from 00:1e:58:e5:8c:aa (capab=0x431 status=0 aid=1)
wlan0: associated
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
wlan0: deauthenticating from 00:1e:58:e5:8c:aa by local choice (reason=3)
wlan0: deauthenticating from 00:1e:58:e5:8c:aa by local choice (reason=3)
wlan0: direct probe to AP 00:1e:58:e5:8c:aa (try 1)
ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlan0: direct probe responded
wlan0: authenticate with AP 00:1e:58:e5:8c:aa (try 1)
wlan0: authenticated
wlan0: associate with AP 00:1e:58:e5:8c:aa (try 1)
wlan0: RX ReassocResp from 00:1e:58:e5:8c:aa (capab=0x431 status=0 aid=1)
wlan0: associated
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
wlan0: deauthenticating from 00:1e:58:e5:8c:aa by local choice (reason=3)
wlan0: direct probe to AP 00:1e:58:e5:8c:aa (try 1)
ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlan0: direct probe responded
wlan0: authenticate with AP 00:1e:58:e5:8c:aa (try 1)
wlan0: authenticated
wlan0: associate with AP 00:1e:58:e5:8c:aa (try 1)
wlan0: RX ReassocResp from 00:1e:58:e5:8c:aa (capab=0x431 status=0 aid=1)
wlan0: associated
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
r8169: eth0: link down
ADDRCONF(NETDEV_UP): eth0: link is not ready
wlan0: deauthenticating from 00:1e:58:e5:8c:aa by local choice (reason=3)
wlan0: direct probe to AP 00:1e:58:e5:8c:aa (try 1)
ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlan0: direct probe to AP 00:1e:58:e5:8c:aa (try 2)
wlan0: direct probe responded
wlan0: authenticate with AP 00:1e:58:e5:8c:aa (try 1)
wlan0: authenticated
wlan0: associate with AP 00:1e:58:e5:8c:aa (try 1)
wlan0: RX ReassocResp from 00:1e:58:e5:8c:aa (capab=0x431 status=0 aid=1)
wlan0: associated
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
wlan0: deauthenticating from 00:1e:58:e5:8c:aa by local choice (reason=3)
wlan0: direct probe to AP 00:1e:58:e5:8c:aa (try 1)
wlan0: direct probe responded
wlan0: authenticate with AP 00:1e:58:e5:8c:aa (try 1)
wlan0: authenticated
wlan0: associate with AP 00:1e:58:e5:8c:aa (try 1)
wlan0: RX ReassocResp from 00:1e:58:e5:8c:aa (capab=0x431 status=0 aid=1)
wlan0: associated
wlan0: no IPv6 routers present
wlan0: deauthenticating from 00:1e:58:e5:8c:aa by local choice (reason=3)
wlan0: deauthenticating from 00:1e:58:e5:8c:aa by local choice (reason=3)
ADDRCONF(NETDEV_UP): wlan0: link is not ready
ADDRCONF(NETDEV_UP): wlan0: link is not ready
r8169: eth0: link down
ADDRCONF(NETDEV_UP): eth0: link is not ready

And here's dmesg after successful one:

ADDRCONF(NETDEV_UP): wlan0: link is not ready
ADDRCONF(NETDEV_UP): wlan0: link is not ready
r8169: eth0: link down
ADDRCONF(NETDEV_UP): eth0: link is not ready
ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlan0: direct probe to AP 00:1e:58:e5:8c:aa (try 1)
wlan0: direct probe responded
wlan0: authenticate with AP 00:1e:58:e5:8c:aa (try 1)
wlan0: authenticated
wlan0: associate with AP 00:1e:58:e5:8c:aa (try 1)
wlan0: RX AssocResp from 00:1e:58:e5:8c:aa (capab=0x431 status=0 aid=1)
wlan0: associated
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
wlan0: no IPv6 routers present

Has anyone any suggestions about reasons of all this stuff? And how can it be solved?

pyther

Member

Registered: 2008-01-21

Posts: 1,395

Website

Re: [solved] Wicd is unable to run disconnet scripts

Let me guess you are using an aetheros wireless card, right? If this is the case people have been having problems with such cards for the past two or three kernel releases. :-/

---

Website - Blog - arch-home
Arch User since March 2005

zhuk_av

Member

Registered: 2009-11-02

Posts: 36

Re: [solved] Wicd is unable to run disconnet scripts

You are right. I'm using Acer Aspire One 150 with "Atheros Communications Inc. AR5001 Wireless Network Adapter (rev 01)". But if it is a hardware issue, why then netcfg is able to connect (from second attempt, but it is stable)?

zhuk_av

Member

Registered: 2009-11-02

Posts: 36

Re: [solved] Wicd is unable to run disconnet scripts

Just have tried a simple trick right now. With auto-connection turned off, I've made

ifconfig wlan0 down

in terminal.
And wicd succeeded in connecting after that.

P.S. After some testing it looks like it was an accident - after reboot such effect of ifconfig had disappeared.

Last edited by zhuk_av (2010-02-04 10:52:49)

zhuk_av

Member

Registered: 2009-11-02

Posts: 36

Re: [solved] Wicd is unable to run disconnet scripts

At least, i have found the working solution. I'm not sure, does is work only for my particular case, but driver reload helps to fix problems with reconnections. To automate process the next simple script should be used as pre-connection script in wicd:

modprobe -r ath5k
modprobe ath5k

And there we've came back to the post theme. Probably, the driver reload should be placed to "post-disconnect", when the initial bug should be fixed.

zhuk_av

Member

Registered: 2009-11-02

Posts: 36

Re: [solved] Wicd is unable to run disconnet scripts

I was experimenting with older versions of wicd in the case of this post. Although 1.6.2.2 does not hangs during connection with *disconnect scripts fields filled in, it does not run them at all.

pinterd

Member

Registered: 2010-04-07

Posts: 1

Re: [solved] Wicd is unable to run disconnet scripts

@zhuk_av: excellent solution. i've had the exact same problem, and that one line helped.

Code:

ifconfig wlan0 down

i own an AAO D150, and in case anybody else have the same problem, i'm pasting my rc.conf here. it works after reboot.

Code:

#
# /etc/rc.conf - Main Configuration for Arch Linux
#

# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_US.utf8"
HARDWARECLOCK="UTC"
USEDIRECTISA="no"
TIMEZONE="Asia/Taipei"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
#
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
#
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(ath5k)

# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="myhost"

# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
#   - prefix an entry in INTERFACES with a ! to disable it
#   - no hyphens in your interface names - Bash doesn't like it
#
# DHCP:     Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#

#Static IP example
#eth0="eth0 192.168.x.x netmask 255.255.255.0 broadcast 192.168.0.255"
#eth0="dhcp"
#wlan0="dhcp"
INTERFACES=(!eth0 !wlan0)

# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
#   - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.x.x"
ROUTES=(gateway)

# Enable these network profiles at boot-up.  These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up (dialog package required)
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This now requires the netcfg package
#
#NETWORKS=(main)

# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng dbus hal !iptables networkmanager !network !adsl !netfs alsa crond)

Last edited by pinterd (2010-04-07 12:41:33)

zhuk_av

Member

Registered: 2009-11-02

Posts: 36

Re: [solved] Wicd is unable to run disconnet scripts

From last wicd and wpa_supplicant upgrade no kernel module reload is required for successfull reconnections. And *disconnect scripts are working fine.