Page 1 of 2 12 LastLast
Results 1 to 10 of 14

Thread: Can't connect to my WPA2 network

  1. #1
    Join Date
    Jun 2008
    Location
    Tromsø, Norway
    Posts
    28

    Default Can't connect to my WPA2 network

    Hi. I have a Lenovo 3000 N200 and I can't connect to my homenetwork. I am using OpenSUSE 11 with KDE 3.5.

    The network at school works allright and I can see it on the list, I just can't connect. The gear-thingy down right goes to about half and then hangs up.

    I have WPA2 AES on it but I tried WPA1 and I tried a different passkey (this one has lots of symbols in it) but didn't help.

    I am not sure what to do next. It worked fine when I tested it with Fedora 9 live CD and it works on Vista.

    I also tried to use YaST but I'm not sure I did it correctly. I couldn't tell if it even tried to connect.
    If it's not broken, take it apart and then fix it!

  2. #2
    Join Date
    Jan 2008
    Location
    U.K East Anglia
    Posts
    2,581

    Default Re: Can't connect to my WPA2 network

    have you read this My wireless doesn't work - a primer on what I should do next - openSUSE Forums has some good info & might help

    Andy
    To be is to do = Immanuel Kant
    To do is to be = Descartes.
    Do be do be do = Frank Sinatra

    SuSE user since 7.0,Linux user since 1994

  3. #3
    Join Date
    Jun 2008
    Location
    Tromsø, Norway
    Posts
    28

    Default Re: Can't connect to my WPA2 network

    04:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection (rev 61)
    04:00.0 0280: 8086:4230 (rev 61)

    wlan0 IEEE 802.11g ESSID:"linksys"
    Mode:Managed Frequency:2.427 GHz Access Point: 00:18:39:29:83:D2
    Bit Rate=54 Mb/s Tx-Power=27 dBm
    Retry min limit:7 RTS thr:off Fragment thr=2352 B
    Link Quality=50/100 Signal level=-68 dBm Noise level=-88 dBm
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:0 Invalid misc:0 Missed beacon:0

    lo Interface doesn't support scanning.

    eth0 Interface doesn't support scanning.

    wmaster0 Interface doesn't support scanning.

    wlan0 No scan results

    pan0 Interface doesn't support scanning.



    Here's the results from that.
    If it's not broken, take it apart and then fix it!

  4. #4
    Join Date
    Jun 2008
    Location
    Tromsø, Norway
    Posts
    28

    Default Re: Can't connect to my WPA2 network

    I tried to look through the knetworkmanager log but I couldn't really make anything out of it.

    Code:
    Aug 31 21:03:01 linux-317c NetworkManager: <info>  Activation (wlan0) failed.
    Aug 31 21:03:01 linux-317c NetworkManager: <info>  (wlan0): device state change: 9 -> 3
    Aug 31 21:03:01 linux-317c NetworkManager: <info>  (wlan0): deactivating device.
    Aug 31 21:03:01 linux-317c NetworkManager: <info>  Activation (wlan0) starting connection 'Verknett'
    Aug 31 21:03:01 linux-317c NetworkManager: <info>  (wlan0): device state change: 3 -> 4
    Aug 31 21:03:01 linux-317c NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
    Aug 31 21:03:01 linux-317c NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
    Aug 31 21:03:01 linux-317c NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
    Aug 31 21:03:01 linux-317c NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
    Aug 31 21:03:01 linux-317c NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
    Aug 31 21:03:01 linux-317c NetworkManager: <info>  (wlan0): device state change: 4 -> 5
    Aug 31 21:03:01 linux-317c NetworkManager: <info>  Activation (wlan0/wireless): access point 'Verknett' has security, but secrets are required.
    Aug 31 21:03:01 linux-317c NetworkManager: <info>  (wlan0): device state change: 5 -> 6
    Aug 31 21:03:01 linux-317c NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
    Aug 31 21:03:01 linux-317c NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
    Aug 31 21:03:01 linux-317c NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
    Aug 31 21:03:01 linux-317c NetworkManager: <info>  (wlan0): device state change: 6 -> 4
    Aug 31 21:03:01 linux-317c NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
    Aug 31 21:03:01 linux-317c NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
    Aug 31 21:03:01 linux-317c NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
    Aug 31 21:03:01 linux-317c NetworkManager: <info>  (wlan0): device state change: 4 -> 5
    Aug 31 21:03:01 linux-317c NetworkManager: <info>  Activation (wlan0/wireless): connection 'Verknett' has security, and secrets exist.  No new secrets needed.
    Aug 31 21:03:01 linux-317c NetworkManager: <info>  Config: added 'ssid' value 'Verknett'
    Aug 31 21:03:01 linux-317c NetworkManager: <info>  Config: added 'scan_ssid' value '1'
    Aug 31 21:03:01 linux-317c NetworkManager: <info>  Config: added 'key_mgmt' value 'WPA-PSK'
    Aug 31 21:03:01 linux-317c NetworkManager: <info>  Config: added 'psk' value '<omitted>'
    Aug 31 21:03:01 linux-317c NetworkManager: <info>  Config: added 'pairwise' value 'TKIP CCMP'
    Aug 31 21:03:01 linux-317c NetworkManager: <info>  Config: added 'group' value 'TKIP CCMP'
    Aug 31 21:03:01 linux-317c NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
    Aug 31 21:03:01 linux-317c NetworkManager: <info>  Config: set interface ap_scan to 1
    Aug 31 21:03:01 linux-317c NetworkManager: <info>  (wlan0): supplicant connection state change: 0 -> 2
    Aug 31 21:03:09 linux-317c NetworkManager: <info>  (wlan0): supplicant connection state change: 2 -> 4
    Aug 31 21:03:09 linux-317c NetworkManager: <info>  (wlan0): supplicant connection state change: 4 -> 0
    Aug 31 21:03:14 linux-317c NetworkManager: <info>  (wlan0): supplicant connection state change: 0 -> 2
    Aug 31 21:03:26 linux-317c NetworkManager: <info>  Activation (wlan0/wireless): association took too long.
    Aug 31 21:03:26 linux-317c NetworkManager: <info>  (wlan0): device state change: 5 -> 6
    Aug 31 21:03:26 linux-317c NetworkManager: <info>  Activation (wlan0/wireless): asking for new secrets
    Aug 31 21:03:26 linux-317c NetworkManager: <info>  (wlan0): supplicant connection state change: 2 -> 0
    Aug 31 21:03:26 linux-317c NetworkManager: <WARN>  get_secrets_cb(): Couldn't get connection secrets: Requested setting is empty.
    Aug 31 21:03:26 linux-317c NetworkManager: <info>  (wlan0): device state change: 6 -> 9
    Aug 31 21:03:26 linux-317c NetworkManager: <info>  Activation (wlan0) failed for access point (Verknett)
    Aug 31 21:03:26 linux-317c NetworkManager: <info>  Marking connection 'Verknett' invalid.
    Aug 31 21:03:26 linux-317c NetworkManager: <info>  Activation (wlan0) failed.
    Aug 31 21:03:26 linux-317c NetworkManager: <info>  (wlan0): device state change: 9 -> 3
    Aug 31 21:03:26 linux-317c NetworkManager: <info>  (wlan0): deactivating device.
    Aug 31 21:04:09 linux-317c NetworkManager: <info>  Activation (wlan0) starting connection 'Verknett'
    Aug 31 21:04:09 linux-317c NetworkManager: <info>  (wlan0): device state change: 3 -> 4
    Aug 31 21:04:09 linux-317c NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
    Aug 31 21:04:09 linux-317c NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
    Aug 31 21:04:09 linux-317c NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
    Aug 31 21:04:09 linux-317c NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
    Aug 31 21:04:09 linux-317c NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
    Aug 31 21:04:09 linux-317c NetworkManager: <info>  (wlan0): device state change: 4 -> 5
    Aug 31 21:04:09 linux-317c NetworkManager: <info>  Activation (wlan0/wireless): access point 'Verknett' has security, but secrets are required.
    Aug 31 21:04:09 linux-317c NetworkManager: <info>  (wlan0): device state change: 5 -> 6
    Aug 31 21:04:09 linux-317c NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
    Aug 31 21:04:09 linux-317c NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
    Aug 31 21:04:09 linux-317c NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
    Aug 31 21:04:09 linux-317c NetworkManager: <info>  (wlan0): device state change: 6 -> 4
    Aug 31 21:04:09 linux-317c NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
    Aug 31 21:04:09 linux-317c NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
    Aug 31 21:04:09 linux-317c NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
    Aug 31 21:04:09 linux-317c NetworkManager: <info>  (wlan0): device state change: 4 -> 5
    Aug 31 21:04:09 linux-317c NetworkManager: <info>  Activation (wlan0/wireless): connection 'Verknett' has security, and secrets exist.  No new secrets needed.
    Aug 31 21:04:09 linux-317c NetworkManager: <info>  Config: added 'ssid' value 'Verknett'
    Aug 31 21:04:09 linux-317c NetworkManager: <info>  Config: added 'scan_ssid' value '1'
    Aug 31 21:04:09 linux-317c NetworkManager: <info>  Config: added 'key_mgmt' value 'WPA-PSK'
    Aug 31 21:04:09 linux-317c NetworkManager: <info>  Config: added 'psk' value '<omitted>'
    Aug 31 21:04:09 linux-317c NetworkManager: <info>  Config: added 'pairwise' value 'TKIP CCMP'
    Aug 31 21:04:09 linux-317c NetworkManager: <info>  Config: added 'group' value 'TKIP CCMP'
    Aug 31 21:04:09 linux-317c NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
    Aug 31 21:04:09 linux-317c NetworkManager: <info>  (wlan0): supplicant connection state change: 2 -> 0
    Aug 31 21:04:09 linux-317c NetworkManager: <info>  Config: set interface ap_scan to 1
    Aug 31 21:04:09 linux-317c NetworkManager: <info>  (wlan0): supplicant connection state change: 0 -> 2
    Aug 31 21:04:16 linux-317c NetworkManager: <info>  (wlan0): supplicant connection state change: 2 -> 0
    Aug 31 21:04:16 linux-317c NetworkManager: <info>  (wlan0): supplicant connection state change: 0 -> 4
    Aug 31 21:04:16 linux-317c NetworkManager: <info>  (wlan0): supplicant connection state change: 4 -> 0
    Aug 31 21:04:21 linux-317c NetworkManager: <info>  (wlan0): supplicant connection state change: 0 -> 2
    Aug 31 21:04:34 linux-317c NetworkManager: <info>  Activation (wlan0/wireless): association took too long.
    
    
    Aug 31 21:04:34 linux-317c NetworkManager: <info>  (wlan0): device state change: 5 -> 6
    Aug 31 21:04:34 linux-317c NetworkManager: <info>  Activation (wlan0/wireless): asking for new secrets
    Aug 31 21:04:34 linux-317c NetworkManager: <info>  (wlan0): supplicant connection state change: 2 -> 0
    Aug 31 21:04:34 linux-317c NetworkManager: <WARN>  get_secrets_cb(): Couldn't get connection secrets: Requested setting is empty.
    Aug 31 21:04:34 linux-317c NetworkManager: <info>  (wlan0): device state change: 6 -> 9
    Aug 31 21:04:34 linux-317c NetworkManager: <info>  Activation (wlan0) failed for access point (Verknett)
    Aug 31 21:04:34 linux-317c NetworkManager: <info>  Marking connection 'Verknett' invalid.
    Aug 31 21:04:34 linux-317c NetworkManager: <info>  Activation (wlan0) failed.
    Aug 31 21:04:34 linux-317c NetworkManager: <info>  (wlan0): device state change: 9 -> 3
    Aug 31 21:04:34 linux-317c NetworkManager: <info>  (wlan0): deactivating device.
    Aug 31 21:04:34 linux-317c NetworkManager: <WARN> get_secrets_cb(): Couldn't get connection secrets: Requested setting is empty.

    seems interesing though.
    If it's not broken, take it apart and then fix it!

  5. #5
    Join Date
    Jun 2008
    Location
    Tromsø, Norway
    Posts
    28

    Default Re: Can't connect to my WPA2 network

    Please help. I really want to use OpenSUSE and having network at home is critical for me.
    If it's not broken, take it apart and then fix it!

  6. #6
    Join Date
    Jan 2008
    Location
    U.K East Anglia
    Posts
    2,581

    Default Re: Can't connect to my WPA2 network

    Have you checked what encryption the school is using ?

    Andy
    To be is to do = Immanuel Kant
    To do is to be = Descartes.
    Do be do be do = Frank Sinatra

    SuSE user since 7.0,Linux user since 1994

  7. #7
    Join Date
    Jun 2008
    Location
    Tromsø, Norway
    Posts
    28

    Default Re: Can't connect to my WPA2 network

    None. They have an open network, but you're redirected to a page where you have to log in
    If it's not broken, take it apart and then fix it!

  8. #8
    Join Date
    Jan 2008
    Location
    U.K East Anglia
    Posts
    2,581

    Default Re: Can't connect to my WPA2 network

    so, the problem is, you can connect,but not sign on ? or you cannot connect,therefore no sign on ? are you using traditional ifup ? network manager ?


    Andy
    To be is to do = Immanuel Kant
    To do is to be = Descartes.
    Do be do be do = Frank Sinatra

    SuSE user since 7.0,Linux user since 1994

  9. #9
    Join Date
    Jun 2008
    Location
    Sarasota
    Posts
    301

    Default Re: Can't connect to my WPA2 network

    another with exact same device solved it here:
    can't enable wireless - openSUSE Forums
    Box1: MEPIS-8.5/sidux/openSUSE-11.3M6(broken-wifi/hiddenSSIDs)/XP(32-bit), nvidia 5200
    Lap1: antiX-8.5(KDE4.4.3)/MEPIS-8.5/Vista, Intel 945GM, builtin-wifi->Broadcom-4311(drv=wl)

  10. #10
    Join Date
    Jun 2008
    Location
    Tromsø, Norway
    Posts
    28

    Default Re: Can't connect to my WPA2 network

    Quote Originally Posted by deltaflyer44 View Post
    so, the problem is, you can connect,but not sign on ? or you cannot connect,therefore no sign on ? are you using traditional ifup ? network manager ?


    Andy
    Network manager, and I'm talking about the network at home which is WPA2. Everything works fine at school. At home I cannot connect. It sort of gets halfway and then stops. I've checked that the code is correct several times and are fairly sure that it is.

    I've tried, when nobody else used the network, to put the encryption to WPA1 and to a passcode which is not a 14 characters long phrase from Strong Password Generator but that didn't help either.

    I've tried to set it up through YAST a few times but then it didn't even try to connect. Not sure how to see if it's connected or not, but I couldn't surf so obviously it didn't work.
    If it's not broken, take it apart and then fix it!

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •