Author Topic: failed to connect  (Read 3060 times)

Offline phantom16

  • Full Member
  • ***
  • Posts: 75
failed to connect
« on: February 24, 2012, 04:17:44 PM »
so i just got to a new house with an existing wpa2 encrypted network. i logged in on pclos (the same one ive been using forever, updated just a couple weeks ago and everything) and tried connecting with the password, but every time, over and over (i have like 10x checked to maker sure it's the right password) it just keeps saying connection failed. i have restarted multiple times, and I havent changed any setting in the past couple days since i was connected at my old house no problem. i know its the right password, because when i log in on my windows 7 partition it works fine with the password, and this is how i am now on the internet.

I dont know why i can't connect. im running standard pclos 2011 with kde 4. this new internet is nothing funky, no static ip address or anything, just the name and a password, which works fine on windows, just not pclos O.o

Offline Just17

  • PCLinuxOS Tester
  • Super Villain
  • *******
  • Posts: 10622
  • MLUs Forever!
Re: failed to connect
« Reply #1 on: February 24, 2012, 04:41:25 PM »
I would delete the NIC connection in PCC and then recreate it to see if there is any change ....
MLUs rule the roost!

Linux XPS 3.2.18-pclos2.pae.bfs  32 bit
Intel Core2 Quad CPU Q9450 @ 2.66GHz
4 GB RAM
MCP51 High Def Audio
GeForce GTX 550 Ti
PHILIPS  ‎DVD+-RW DVD8701
‎Logitech ‎BT Mini-Receiver
Afatech DTT

Offline AS

  • Hero Member
  • *****
  • Posts: 4111
  • Have a nice ... night!
Re: failed to connect
« Reply #2 on: February 24, 2012, 06:45:46 PM »
I would delete the NIC connection in PCC and then recreate it to see if there is any change ....

+1

additionally check dmesg for possible hints ...

run
Code: [Select]
iwlist scanning may be near you there is another router broadcasting on the same channel of your router ...  and at least you can see if your adapter see your wireless network ... ;)

AS

Offline phantom16

  • Full Member
  • ***
  • Posts: 75
Re: failed to connect
« Reply #3 on: February 24, 2012, 08:03:31 PM »
ok, so im hoping by "delete and recreate the NIC connection" you mean, go into PCC, click on the network and internet button on the left, and then click "remove a connection". then click the wlan0 device and remove it. then i clicked "set up a new network interface (LAN, ISDN, ASDL,...)" and go thorugh that. because thats what i did, but still to no avail...

i ran "dmesg", and skimmed through it, but i have no idea how to make any sense out of all that, and the output is more than twice as long as the maximum amount of characters allowed in a forum post, would it help if i posted all that?


regardless,  running iwlist scanning returns this:
lo        Interface doesn't support scanning.

eth0      Interface doesn't support scanning.

wlan0     Scan completed :
          Cell 01 - Address: 84:A8:E4:D4:A7:F4
                    Channel:6
                    Frequency:2.437 GHz (Channel 6)
                    Quality=28/70  Signal level=-82 dBm 
                    Encryption key:on
                    ESSID:"Villa Gr�nspecht"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
                              24 Mb/s; 36 Mb/s; 54 Mb/s
                    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
                    Mode:Master
                    Extra:tsf=0000014921594183
                    Extra: Last beacon: 2039ms ago
                    IE: Unknown: 001056696C6C61204772FC6E737065636874
                    IE: Unknown: 010882848B962430486C
                    IE: Unknown: 030106
                    IE: Unknown: 2A0100
                    IE: Unknown: 2F0100
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (2) : CCMP TKIP
                        Authentication Suites (1) : PSK
                    IE: Unknown: 32040C121860
                    IE: Unknown: 2D1AFC181BFFFF000001000000000000000000000000000000000000
                    IE: Unknown: 3D1606001100000000000000000000000000000000000000
                    IE: Unknown: 4A0E14000A002C01C800140005001900
                    IE: Unknown: 7F0101
                    IE: Unknown: DD7B0050F204104A00011010440001021041000100103B00010310470010F56FC656077BB9359D4880E34A656E051021000842726F6164636F6D1023000842726F6164636F6D1024000631323334353610420004313233341054000800060050F20400011011000A42726F6164636F6D4150100800020084103C000103
                    IE: Unknown: DD090010180200F0050000
                    IE: WPA Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (2) : CCMP TKIP
                        Authentication Suites (1) : PSK
                    IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00



Villa Gr_nspecht is the network i'm trying to connect to. there are a couple other networks that show up when i refresh my wlan0. one of them starts with "FRITZ" and the other isnt showing up currently (but it was a few hours ago, maybe the turned it off or something) but "villa..." is in the iwlist, so it seems my computer can see the network? it just wont connect for some reason...

Offline AS

  • Hero Member
  • *****
  • Posts: 4111
  • Have a nice ... night!
Re: failed to connect
« Reply #4 on: February 24, 2012, 08:28:43 PM »
ok, so im hoping by "delete and recreate the NIC connection" you mean, go into PCC, click on the network and internet button on the left, and then click "remove a connection". then click the wlan0 device and remove it. then i clicked "set up a new network interface (LAN, ISDN, ASDL,...)" and go thorugh that. because thats what i did, but still to no avail...

i ran "dmesg", and skimmed through it, but i have no idea how to make any sense out of all that, and the output is more than twice as long as the maximum amount of characters allowed in a forum post, would it help if i posted all that?

try:
Code: [Select]
dmesg  |  grep wlan0
Quote
Villa Gr_nspecht is the network i'm trying to connect to. there are a couple other networks that show up when i refresh my wlan0. one of them starts with "FRITZ" and the other isnt showing up currently (but it was a few hours ago, maybe the turned it off or something) but "villa..." is in the iwlist, so it seems my computer can see the network? it just wont connect for some reason...

Yes, the network is visible, it is using Channel 6, and reach your adapter. If the other routers in your area are using Channel 6 I would suggest to use a different Channel ...

Any info about your wifi adapter ? brand/model ? extract info from:
Code: [Select]
lspci -nn -k

Offline phantom16

  • Full Member
  • ***
  • Posts: 75
Re: failed to connect
« Reply #5 on: February 25, 2012, 07:46:30 AM »
ok so i ran dmesg  |  grep wlan0, im just not one to make sense of that, but this is what i got:
Quote
ADDRCONF(NETDEV_UP): wlan0: link is not ready
ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlan0: direct probe to 84:a8:e4:d4:a7:f4 (try 1/3)
wlan0: direct probe responded
wlan0: authenticate with 84:a8:e4:d4:a7:f4 (try 1)
wlan0: authenticated
wlan0: associate with 84:a8:e4:d4:a7:f4 (try 1)
wlan0: RX AssocResp from 84:a8:e4:d4:a7:f4 (capab=0x411 status=0 aid=2)
wlan0: associated
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
wlan0: deauthenticated from 84:a8:e4:d4:a7:f4 (Reason: 7)
wlan0: authenticate with 84:a8:e4:d4:a7:f4 (try 1)
wlan0: authenticated
wlan0: associate with 84:a8:e4:d4:a7:f4 (try 1)
wlan0: RX AssocResp from 84:a8:e4:d4:a7:f4 (capab=0x411 status=0 aid=2)
wlan0: associated
wlan0: no IPv6 routers present
wlan0: deauthenticated from 84:a8:e4:d4:a7:f4 (Reason: 15)
wlan0: direct probe to 00:1c:4a:00:97:6e (try 1/3)
wlan0: direct probe to 00:1c:4a:00:97:6e (try 2/3)
wlan0: direct probe to 00:1c:4a:00:97:6e (try 3/3)
wlan0: direct probe to 00:1c:4a:00:97:6e timed out
wlan0: authenticate with 84:a8:e4:d4:a7:f4 (try 1)
wlan0: authenticated
wlan0: associate with 84:a8:e4:d4:a7:f4 (try 1)
wlan0: RX AssocResp from 84:a8:e4:d4:a7:f4 (capab=0x411 status=0 aid=2)
wlan0: associated
wlan0: deauthenticating from 84:a8:e4:d4:a7:f4 by local choice (reason=3)
wlan0: authenticate with 84:a8:e4:d4:a7:f4 (try 1)
wlan0: authenticated
wlan0: associate with 84:a8:e4:d4:a7:f4 (try 1)
wlan0: RX AssocResp from 84:a8:e4:d4:a7:f4 (capab=0x411 status=0 aid=2)
wlan0: associated
wlan0: deauthenticated from 84:a8:e4:d4:a7:f4 (Reason: 15)
wlan0: authenticate with 00:1c:4a:00:97:6e (try 1)
wlan0: authenticated
wlan0: associate with 00:1c:4a:00:97:6e (try 1)
wlan0: RX AssocResp from 00:1c:4a:00:97:6e (capab=0x411 status=0 aid=4)
wlan0: associated
wlan0: deauthenticated from 00:1c:4a:00:97:6e (Reason: 1)
wlan0: authenticate with 00:1c:4a:00:97:6e (try 1)
wlan0: authenticate with 00:1c:4a:00:97:6e (try 2)
wlan0: authenticate with 00:1c:4a:00:97:6e (try 3)
wlan0: authentication with 00:1c:4a:00:97:6e timed out
wlan0: authenticate with 84:a8:e4:d4:a7:f4 (try 1)
wlan0: authenticated
wlan0: associate with 84:a8:e4:d4:a7:f4 (try 1)
wlan0: RX AssocResp from 84:a8:e4:d4:a7:f4 (capab=0x411 status=0 aid=2)
wlan0: associated
wlan0: deauthenticated from 84:a8:e4:d4:a7:f4 (Reason: 7)
device wlan0 entered promiscuous mode
wlan0: direct probe to 30:46:9a:44:71:ba (try 1/3)
wlan0: direct probe to 30:46:9a:44:71:ba (try 2/3)
wlan0: direct probe to 30:46:9a:44:71:ba (try 3/3)
wlan0: direct probe to 30:46:9a:44:71:ba timed out
device wlan0 left promiscuous mode
wlan0: authenticate with 84:a8:e4:d4:a7:f4 (try 1)
wlan0: authenticated
wlan0: associate with 84:a8:e4:d4:a7:f4 (try 1)
wlan0: RX AssocResp from 84:a8:e4:d4:a7:f4 (capab=0x411 status=0 aid=2)
wlan0: associated
wlan0: deauthenticating from 84:a8:e4:d4:a7:f4 by local choice (reason=3)
wlan0: direct probe to 00:1c:4a:00:97:6e (try 1/3)
wlan0: direct probe to 00:1c:4a:00:97:6e (try 2/3)
wlan0: direct probe to 00:1c:4a:00:97:6e (try 3/3)
wlan0: direct probe to 00:1c:4a:00:97:6e timed out
ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlan0: direct probe to 00:1c:4a:00:97:6e (try 1/3)
wlan0: direct probe to 00:1c:4a:00:97:6e (try 2/3)
wlan0: direct probe to 00:1c:4a:00:97:6e (try 3/3)
wlan0: direct probe to 00:1c:4a:00:97:6e timed out
wlan0: authenticate with 84:a8:e4:d4:a7:f4 (try 1)
wlan0: authenticated
wlan0: associate with 84:a8:e4:d4:a7:f4 (try 1)
wlan0: RX AssocResp from 84:a8:e4:d4:a7:f4 (capab=0x411 status=0 aid=2)
wlan0: associated
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
wlan0: deauthenticated from 84:a8:e4:d4:a7:f4 (Reason: 15)
wlan0: direct probe to 00:1c:4a:00:97:6e (try 1/3)
wlan0: direct probe to 00:1c:4a:00:97:6e (try 2/3)
wlan0: direct probe to 00:1c:4a:00:97:6e (try 3/3)
wlan0: direct probe to 00:1c:4a:00:97:6e timed out
wlan0: no IPv6 routers present
wlan0: authenticate with 84:a8:e4:d4:a7:f4 (try 1)
wlan0: authenticated
wlan0: associate with 84:a8:e4:d4:a7:f4 (try 1)
wlan0: RX AssocResp from 84:a8:e4:d4:a7:f4 (capab=0x411 status=0 aid=2)
wlan0: associated
wlan0: deauthenticating from 84:a8:e4:d4:a7:f4 by local choice (reason=3)
wlan0: authenticate with 84:a8:e4:d4:a7:f4 (try 1)
wlan0: authenticate with 84:a8:e4:d4:a7:f4 (try 2)
wlan0: authenticate with 84:a8:e4:d4:a7:f4 (try 3)
wlan0: authentication with 84:a8:e4:d4:a7:f4 timed out
ADDRCONF(NETDEV_UP): wlan0: link is not ready
ADDRCONF(NETDEV_UP): wlan0: link is not ready
ADDRCONF(NETDEV_UP): wlan0: link is not ready

and running lspci -nn -k yields:
Quote
00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor Family DRAM Controller [8086:0104] (rev 09)
        Subsystem: Acer Incorporated [ALI] Device [1025:0504]
        Kernel driver in use: agpgart-intel
00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port [8086:0101] (rev 09)
        Kernel driver in use: pcieport
        Kernel modules: shpchp
00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09)
        Subsystem: Acer Incorporated [ALI] Device [1025:0504]
        Kernel driver in use: i915
        Kernel modules: i915
00:16.0 Communication controller [0780]: Intel Corporation 6 Series Chipset Family MEI Controller #1 [8086:1c3a] (rev 04)
        Subsystem: Acer Incorporated [ALI] Device [1025:0504]
00:1a.0 USB Controller [0c03]: Intel Corporation 6 Series Chipset Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 04)
        Subsystem: Acer Incorporated [ALI] Device [1025:0504]
        Kernel driver in use: ehci_hcd
        Kernel modules: ehci-hcd
00:1b.0 Audio device [0403]: Intel Corporation 6 Series Chipset Family High Definition Audio Controller [8086:1c20] (rev 04)
        Subsystem: Acer Incorporated [ALI] Device [1025:0504]
        Kernel driver in use: HDA Intel
        Kernel modules: snd-hda-intel
00:1c.0 PCI bridge [0604]: Intel Corporation 6 Series Chipset Family PCI Express Root Port 1 [8086:1c10] (rev b4)
        Kernel driver in use: pcieport
        Kernel modules: shpchp
00:1c.1 PCI bridge [0604]: Intel Corporation 6 Series Chipset Family PCI Express Root Port 2 [8086:1c12] (rev b4)
        Kernel driver in use: pcieport
        Kernel modules: shpchp
00:1c.3 PCI bridge [0604]: Intel Corporation 6 Series Chipset Family PCI Express Root Port 4 [8086:1c16] (rev b4)
        Kernel driver in use: pcieport
        Kernel modules: shpchp
00:1d.0 USB Controller [0c03]: Intel Corporation 6 Series Chipset Family USB Enhanced Host Controller #1 [8086:1c26] (rev 04)
        Subsystem: Acer Incorporated [ALI] Device [1025:0504]
        Kernel driver in use: ehci_hcd
        Kernel modules: ehci-hcd
00:1f.0 ISA bridge [0601]: Intel Corporation HM65 Express Chipset Family LPC Controller [8086:1c49] (rev 04)
        Subsystem: Acer Incorporated [ALI] Device [1025:0504]
        Kernel modules: iTCO_wdt
00:1f.2 SATA controller [0106]: Intel Corporation 6 Series Chipset Family 6 port SATA AHCI Controller [8086:1c03] (rev 04)
        Subsystem: Acer Incorporated [ALI] Device [1025:0504]
        Kernel driver in use: ahci
        Kernel modules: ahci
00:1f.3 SMBus [0c05]: Intel Corporation 6 Series Chipset Family SMBus Controller [8086:1c22] (rev 04)
        Subsystem: Acer Incorporated [ALI] Device [1025:0504]
        Kernel modules: i2c-i801
01:00.0 VGA compatible controller [0300]: nVidia Corporation Device [10de:0df4] (rev a1)
        Subsystem: Acer Incorporated [ALI] Device [1025:0505]
        Kernel modules: nvidia-current, nvidia173, nouveau, nvidiafb
02:00.0 Ethernet controller [0200]: Broadcom Corporation NetLink BCM57785 Gigabit Ethernet PCIe [14e4:16b5] (rev 10)
        Subsystem: Acer Incorporated [ALI] Device [1025:0504]
        Kernel driver in use: tg3
        Kernel modules: tg3
02:00.1 SD Host controller [0805]: Broadcom Corporation NetXtreme BCM57765 Memory Card Reader [14e4:16bc] (rev 10)
        Subsystem: Acer Incorporated [ALI] Device [1025:0504]
        Kernel driver in use: sdhci-pci
        Kernel modules: sdhci-pci
02:00.2 System peripheral [0880]: Broadcom Corporation Device [14e4:16be] (rev 10)
        Subsystem: Acer Incorporated [ALI] Device [1025:0504]
02:00.3 System peripheral [0880]: Broadcom Corporation Device [14e4:16bf] (rev 10)
        Subsystem: Acer Incorporated [ALI] Device [1025:0504]
03:00.0 Network controller [0280]: Atheros Communications Inc. AR9287 Wireless Network Adapter (PCI-Express) [168c:002e] (rev 01)
        Subsystem: Foxconn International, Inc. Device [105b:e034]
        Kernel driver in use: ath9k
        Kernel modules: ath9k
05:00.0 USB Controller [0c03]: NEC Corporation uPD720200 USB 3.0 Host Controller [1033:0194] (rev 04)
        Subsystem: Acer Incorporated [ALI] Device [1025:0504]
        Kernel driver in use: xhci_hcd
        Kernel modules: xhci-hcd

i also went and tried iwlist scanning again, and it got all 3 networks this time:
Quote
lo        Interface doesn't support scanning.

eth0      Interface doesn't support scanning.

wlan0     Scan completed :
          Cell 01 - Address: 84:A8:E4:D4:A7:F4
                    Channel:6
                    Frequency:2.437 GHz (Channel 6)
                    Quality=43/70  Signal level=-67 dBm 
                    Encryption key:on
                    ESSID:"Villa Gr�nspecht"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
                              24 Mb/s; 36 Mb/s; 54 Mb/s
                    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
                    Mode:Master
                    Extra:tsf=00000153432a7186
                    Extra: Last beacon: 4261ms ago
                    IE: Unknown: 001056696C6C61204772FC6E737065636874
                    IE: Unknown: 010882848B962430486C
                    IE: Unknown: 030106
                    IE: Unknown: 2A0100
                    IE: Unknown: 2F0100
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (2) : CCMP TKIP
                        Authentication Suites (1) : PSK
                    IE: Unknown: 32040C121860
                    IE: Unknown: 2D1AFC181BFFFF000001000000000000000000000000000000000000
                    IE: Unknown: 3D1606001500000000000000000000000000000000000000
                    IE: Unknown: 4A0E14000A002C01C800140005001900
                    IE: Unknown: 7F0101
                    IE: Unknown: DD7B0050F204104A00011010440001021041000100103B00010310470010F56FC656077BB9359D4880E34A656E051021000842726F6164636F6D1023000842726F6164636F6D1024000631323334353610420004313233341054000800060050F20400011011000A42726F6164636F6D4150100800020084103C000103
                    IE: Unknown: DD090010180201F0050000
                    IE: WPA Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (2) : CCMP TKIP
                        Authentication Suites (1) : PSK
                    IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00
          Cell 02 - Address: 00:1C:4A:00:97:6E
                    Channel:6
                    Frequency:2.437 GHz (Channel 6)
                    Quality=29/70  Signal level=-81 dBm 
                    Encryption key:on
                    ESSID:"FRITZ!Box Fon WLAN 7170"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
                    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
                              36 Mb/s; 48 Mb/s; 54 Mb/s
                    Mode:Master
                    Extra:tsf=000002f5e3ccc233
                    Extra: Last beacon: 4707ms ago
                    IE: Unknown: 0017465249545A21426F7820466F6E20574C414E2037313730
                    IE: Unknown: 010482848B96
                    IE: Unknown: 030106
                    IE: Unknown: 050C000300000000000000000000
                    IE: Unknown: 2A0107
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (1) : CCMP
                        Authentication Suites (1) : PSK
                    IE: Unknown: 32080C1218243048606C
                    IE: WPA Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (1) : TKIP
                        Authentication Suites (1) : PSK
                    IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00
          Cell 03 - Address: 30:46:9A:44:71:BA
                    Channel:6
                    Frequency:2.437 GHz (Channel 6)
                    Quality=35/70  Signal level=-75 dBm 
                    Encryption key:on
                    ESSID:"Wiedmann-Wireless"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
                              24 Mb/s; 36 Mb/s; 54 Mb/s
                    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
                    Mode:Master
                    Extra:tsf=00000024052ac183
                    Extra: Last beacon: 4310ms ago
                    IE: Unknown: 0011576965646D616E6E2D576972656C657373
                    IE: Unknown: 010882840B162430486C
                    IE: Unknown: 030106
                    IE: Unknown: 050400020000
                    IE: Unknown: 2A0100
                    IE: Unknown: 2F0100
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : CCMP
                        Pairwise Ciphers (1) : CCMP
                        Authentication Suites (1) : PSK
                    IE: Unknown: 32040C121860
                    IE: Unknown: DD0E0050F204104A0001101044000102
                    IE: Unknown: DD090010180200F0050000
                    IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00

So it seems to me that they are all running on channel 6? do you think that might be the problem? and if thjat is, the problem with that lies in the fact, that again this isn't my house, im just renting a room, and the landlord has it set up, and i don't think they want me changing anything...
but if that is the problem, is there something else we can do to fix it? because it works fine in windows, maybe using the windows driver might be the next step? i dunno... :/

Online muungwana

  • Hero Member
  • *****
  • Posts: 6216
Re: failed to connect
« Reply #6 on: February 25, 2012, 08:18:00 AM »

wireless network connecting and disconnecting a few seconds later is a problem i have and i have yet to find a reliable solution for.

do you know the module used to control your wireless card? What i do when i get this problem is deleting a file i am going to mention and then reload the module and it connects and stay up.

Try first to run the below command and then try to connect and see if it will stay up

rm   -rf    /var/run/wpa_supplicant/wlan0
.. 3 things are certain in life : death, taxes and software bloat ..
.. tell me something i don't know, something i can use as i struggle to reason with the world around me ..

Offline AS

  • Hero Member
  • *****
  • Posts: 4111
  • Have a nice ... night!
Re: failed to connect
« Reply #7 on: February 25, 2012, 08:28:24 AM »
@muungwana,

03:00.0 Network controller [0280]: Atheros Communications Inc. AR9287 Wireless Network Adapter (PCI-Express) [168c:002e] (rev 01)
        Subsystem: Foxconn International, Inc. Device [105b:e034]
        Kernel driver in use: ath9k
        Kernel modules: ath9k


Online muungwana

  • Hero Member
  • *****
  • Posts: 6216
Re: failed to connect
« Reply #8 on: February 25, 2012, 08:54:39 AM »

Thanks AS,

OP, now try these commands(combined now)

rm   -rf    /var/run/wpa_supplicant/wlan0

modprobe -r ath9k
modprobe ath9k

Now try to connect and report your result

The last command shouldnt be necessary because the module get automatically loaded when i unload it(thats the behavior i am seeing there).
.. 3 things are certain in life : death, taxes and software bloat ..
.. tell me something i don't know, something i can use as i struggle to reason with the world around me ..

Offline phantom16

  • Full Member
  • ***
  • Posts: 75
Re: failed to connect
« Reply #9 on: February 25, 2012, 09:44:06 AM »
ok, so after i do "modprobe -r ath9k" it does automatically connectt correctly, but them after a minute or 2 it disconnects again, and then if i try to reconnect it says connection failed, i have to do that command again, and then i will be reconnected for a couple minutes. any idea how to keep it from dropping the connection?

Online muungwana

  • Hero Member
  • *****
  • Posts: 6216
Re: failed to connect
« Reply #10 on: February 25, 2012, 09:55:53 AM »

just looked at one of your above posts and it says the connection quality is 28/70. The signal strength is too weak. Maybe the connection holds in windows because windows driver can sustain weaker connection than pclinuxos.

Try to move closer to the access point and see if you  can connect and hold a connection.

If you can, you can try moving the wireless network to another channel( start with 12 ).

A less crowded space could help with the weak signal.
.. 3 things are certain in life : death, taxes and software bloat ..
.. tell me something i don't know, something i can use as i struggle to reason with the world around me ..

Offline phantom16

  • Full Member
  • ***
  • Posts: 75
Re: failed to connect
« Reply #11 on: February 25, 2012, 11:19:31 AM »
28/70 thats weird, unless that a different value than the percentage that shows when i just look at the connections in pcc and the bottom right corner? because there it says 52%, and my network at my old house had just about the same connection strength... :/
also, im not far away by any means, in my old house the router was in the basement, and about 5 rooms over, this new place i am directly below the router (its in the same room as me, but 1 floor above me me), of course that could be due to a weaker output signal...
and as it's not my router/internet, but the landlords, and it's locked in the office upstairs, and she doesnt want people to mess with it regardless, so i cant change the channel :/

and lately, i havent been needing to re-input modprobe -r ath9k, it just seems to be connecting and then disconnecting over and over again.... i dont know why the behavior has changed...

kind of a shot in the dark, but could the problem possibly be caused because the SSID doesnt have a normal english character in it (it's: Villa Grünspecht)

lol i have no idea why it's freaking out so much, i am not far away at all, and if it is a channel issue, then it is something that i won't be able to fix because i dont have access to the router :-(

Online muungwana

  • Hero Member
  • *****
  • Posts: 6216
Re: failed to connect
« Reply #12 on: February 25, 2012, 12:06:25 PM »
you are getting 3 different reasons for getting authenticated, 3,7 and 15.

according to mr. google reason 3 means the access point just went offline( or went out of range )

reason 7 means the wireless network tried to send packet before it was properly authenticated

reason 15 has to do with timing out when doing encryption handshaking.

I think the problem primarily comes from the unstable AP going offline temporarily and the difficulty in reconnecting is a secondary problem from a shaky driver and a shaky access point.

what kernel are you using? updating to a more recent kernel could solve the problem.

using window's driver could also be a solution.

I use b43 driver here and it disconnects every time it cant get a response from the access point within 500 ms. Increasing the time the driver wait before disconnecting if possible could also be a solution.

i have looked online to see if the driver can have its setting changed but havent found anything yet.
« Last Edit: February 25, 2012, 12:08:44 PM by muungwana »
.. 3 things are certain in life : death, taxes and software bloat ..
.. tell me something i don't know, something i can use as i struggle to reason with the world around me ..

Offline AS

  • Hero Member
  • *****
  • Posts: 4111
  • Have a nice ... night!
Re: failed to connect
« Reply #13 on: February 25, 2012, 12:39:26 PM »
You may try to use a fixed "data rate", I have found that some adapter (notably my iwl3945), experience lot of difficult to connect in case of weak signals ... things improved for me:

from command line (temporary fix):
Code: [Select]
iwconfig wlan0 rate 9M
you should choose one of the rates available from your router:
Quote
                    ESSID:"Villa Gr�nspecht"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
                              24 Mb/s; 36 Mb/s; 54 Mb/s
                    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s

note that you will loose this settings each time you will reload the kernel module.

To make the changes permanent:
Network Center -> (Select your wireless connection) -> Configure -> (scroll down) > Advanced
add the parameter: rate 9M to the field labeled: "iwconfig command extra argument".






Offline phantom16

  • Full Member
  • ***
  • Posts: 75
Re: failed to connect
« Reply #14 on: February 25, 2012, 01:23:46 PM »
what kernel are you using? updating to a more recent kernel could solve the problem.

Quote
[root@localhost ~]# uname -v
#1 SMP PREEMPT Sat Jun 4 04:13:21 CDT 2011
[root@localhost ~]# uname -r
2.6.38.8-pclos1.bfs
[root@localhost ~]#
i just updated it a few weeks ago, and its proving hard to do it now with the internet jumping in and out :-D

using window's driver could also be a solution.
i tried that briefly, but none of the options that were there said they would work with my device. ill try more on this a little later


You may try to use a fixed "data rate", I have found that some adapter (notably my iwl3945), experience lot of difficult to connect in case of weak signals ... things improved for me:

from command line (temporary fix):
Code: [Select]
iwconfig wlan0 rate 9M
you should choose one of the rates available from your router:
Quote
                    ESSID:"Villa Gr�nspecht"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
                              24 Mb/s; 36 Mb/s; 54 Mb/s
                    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s

note that you will loose this settings each time you will reload the kernel module.

To make the changes permanent:
Network Center -> (Select your wireless connection) -> Configure -> (scroll down) > Advanced
add the parameter: rate 9M to the field labeled: "iwconfig command extra argument".

so i just tried that, replacing the "9m" in iwconfig wlan0 rate 9M with all the speeds, and it still keeps dropping my connection... :/