Gentoo Archives: gentoo-user

From: Joshua Murphy <poisonbl@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Which tool to diagnose wireless connection problem?
Date: Thu, 11 Oct 2012 21:08:09
Message-Id: CAOTuDKq8UcsRRe3dfw1Sf-QY3A2vB9KYmjWaNgKrW2ZB1CAikw@mail.gmail.com
In Reply to: [gentoo-user] Which tool to diagnose wireless connection problem? by Chris Stankevitz
1 On Thu, Oct 11, 2012 at 1:20 PM, Chris Stankevitz
2 <chrisstankevitz@×××××.com> wrote:
3 > Hello,
4 >
5 > I never really understood wireless in linux, it has always "just
6 > worked". I use wicd although I don't really even know what that
7 > means. I have no clue what is a wpa supplicant, ndis, etc.
8 >
9 > I now have a problem. Please point me toward the tools I should use
10 > to diagnose and fix the problem. I tried to fix this problem by
11 > running wicd-client from the command line hoping to see some stderr
12 > messages to help diagnose, but no luck. Also dmesg is not helpful.
13 >
14 > Problem:
15 >
16 > I used a linksys router for years. It appeared as a single SSID that
17 > I connected to. Configured with wicd-client. Everything worked great
18 > under gentoo.
19 >
20 > I throw away the linksys and purchase a new "apple airport express".
21 > This router works fine with my apple machines. On gentoo, wicd-client
22 > shows two SSIDs with identical names for this one router! One is on
23 > "channel 11" and one is on "channel 157". Not sure this matters. I
24 > specify my password for both of them and specify one of them to
25 > "connect automatically". The connection with one (or both?) of the
26 > SSIDs stays live for 5-10 minutes, then disconnects. I can get it to
27 > reconnect by simply opening wicd-client, highlighting one of the two
28 > SSIDs, and clicking connect. Repeat every 5-10 minutes.
29 >
30 > Question: What tools or logs can I use to understand why my wireless
31 > connection disconnects every 5-10 minutes?
32 >
33 > FYI this is what dmesg says during one of these disconnect/reconnect cycles:
34 >
35 > [55519.603007] cfg80211: Calling CRDA to update world regulatory domain
36 > [55520.041137] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
37 > [55520.041381] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
38 > [55520.195568] ADDRCONF(NETDEV_UP): wlan0: link is not ready
39 > [55520.494633] e1000e 0000:00:19.0: irq 44 for MSI/MSI-X
40 > [55520.595455] e1000e 0000:00:19.0: irq 44 for MSI/MSI-X
41 > [55520.598916] ADDRCONF(NETDEV_UP): eth0: link is not ready
42 > [55550.414298] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
43 > [55550.414523] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
44 > [55550.551957] ADDRCONF(NETDEV_UP): wlan0: link is not ready
45 > [55966.719991] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
46 > [55966.720250] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
47 > [55966.863374] ADDRCONF(NETDEV_UP): wlan0: link is not ready
48 > [55967.147380] e1000e 0000:00:19.0: irq 44 for MSI/MSI-X
49 > [55967.248317] e1000e 0000:00:19.0: irq 44 for MSI/MSI-X
50 > [55967.251736] ADDRCONF(NETDEV_UP): eth0: link is not ready
51 > [55967.301004] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
52 > [55967.301252] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
53 > [55967.452333] ADDRCONF(NETDEV_UP): wlan0: link is not ready
54 > [55969.637135] wlan0: authenticate with 7c:d1:c3:cd:b9:be
55 > [55969.641690] wlan0: send auth to 7c:d1:c3:cd:b9:be (try 1/3)
56 > [55969.643564] wlan0: authenticated
57 > [55969.643873] wlan0: associate with 7c:d1:c3:cd:b9:be (try 1/3)
58 > [55969.647304] wlan0: RX AssocResp from 7c:d1:c3:cd:b9:be (capab=0x431
59 > status=0 aid=1)
60 > [55969.654396] wlan0: associated
61 > [55969.657270] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
62 >
63 > Thank you,
64 >
65 > Chris
66
67 Check the log in /var/log/wicd for errors. Also, inside of wicd's
68 configuration there's a "debug" option... enabling that increases the
69 messages dumped into the log(s) there quite a bit, if what's already
70 there doesn't say anything useful.
71
72 --
73 Poison [BLX]
74 Joshua M. Murphy