Results 1 to 6 of 6

Thread: Problem connecting to password-protected network

  1. #1
    lindners NNTP User

    Default Problem connecting to password-protected network

    Dear all,

    I have tried to connect to a password-protected network, with no success. I could connect to the network before we switched to password-protection, so ther must be something wrong in how I set up the encryption via yast. It would be great if you could help me! Hope the information below are sufficient.

    -- Stephan

    Distribution SuSe Linux 10.0
    Network Card: Netgear
    Network: Netgear WPA-PSK, Mode 11b, passphrase

    In yast:

    Operating Mode: Managed
    Network Name: thenetwork
    Authentication Mode: open [also tried shared key / WPA-PSK]
    password: ...


    $ ifconfig

    eth0 Link encap:Ethernet HWaddr 00:02:3F:8E:EE:00
    inet6 addr: fe80::202:3fff:fe8e:ee00/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:5 errors:0 dropped:0 overruns:0 frame:0
    TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:348 (348.0 b) TX bytes:378 (378.0 b)
    Interrupt:10 Base address:0x4000

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:27 errors:0 dropped:0 overruns:0 frame:0
    TX packets:27 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:2369 (2.3 Kb) TX bytes:2369 (2.3 Kb)

    wlan0 Link encap:Ethernet HWaddr 00:09:5B:8B:14:64
    inet6 addr: fe80::209:5bff:fe8b:1464/64 Scope:Link
    UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:54 errors:0 dropped:15 overruns:0 frame:0
    TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:2907 (2.8 Kb) TX bytes:4944 (4.8 Kb)
    Interrupt:11 Memory:cff8e000-cff8e100


    $ iwconfig

    wlan0 IEEE 802.11b ESSID:"thenetwork"
    Mode:Managed Frequency:2.437 GHz Access Point: 00:14:6C: DE:29:EE
    Bit Rate=11 Mb/s Sensitivity=80/85
    Retry: on Fragment thr: off
    Encryption key:528C-7D5D-9482-1BE1-BEA3-ACE2-B7 Security mode:restri
    cted
    Link Quality=97/100 Signal level=-37 dBm Noise level=-253 dBm
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:0 Invalid misc:0 Missed beacon:0

    eth1 IEEE 802.11b ESSID:"" Nickname:"HERMES I"
    Mode:Managed Frequency:2.457 GHz Access Point: 00:00:00:00:00:00
    Bit Rate:11 Mb/s Sensitivity:1/3
    Retry limit:4 RTS thr: off Fragment thr: off
    Encryption key: off
    Power Management: off
    Link Quality=0/92 Signal level=134/153 Noise level=134/153
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:0 Invalid misc:0 Missed beacon:0

  2. #2
    ab@novell.com NNTP User

    Default Re: Problem connecting to password-protected network

    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA1

    Have you tried using Network Manager to see if that will connect? I've
    had an easier time using that to connect to various wireless network
    especially since switching networks is really easy and Yast (via 'root')
    isn't required.

    Good luck.





    lindners wrote:
    | Dear all,
    |
    | I have tried to connect to a password-protected network, with no
    | success. I could connect to the network before we switched to
    | password-protection, so ther must be something wrong in how I set up
    | the encryption via yast. It would be great if you could help me! Hope
    | the information below are sufficient.
    |
    | -- Stephan
    |
    | Distribution SuSe Linux 10.0
    | Network Card: Netgear
    | Network: Netgear WPA-PSK, Mode 11b, passphrase
    |
    | In yast:
    |
    | Operating Mode: Managed
    | Network Name: thenetwork
    | Authentication Mode: open [also tried shared key / WPA-PSK]
    | password: ...
    |
    |
    | $ ifconfig
    |
    | eth0 Link encap:Ethernet HWaddr 00:02:3F:8E:EE:00
    | inet6 addr: fe80::202:3fff:fe8e:ee00/64 Scope:Link
    | UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    | RX packets:5 errors:0 dropped:0 overruns:0 frame:0
    | TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
    | collisions:0 txqueuelen:1000
    | RX bytes:348 (348.0 b) TX bytes:378 (378.0 b)
    | Interrupt:10 Base address:0x4000
    |
    | lo Link encap:Local Loopback
    | inet addr:127.0.0.1 Mask:255.0.0.0
    | inet6 addr: ::1/128 Scope:Host
    | UP LOOPBACK RUNNING MTU:16436 Metric:1
    | RX packets:27 errors:0 dropped:0 overruns:0 frame:0
    | TX packets:27 errors:0 dropped:0 overruns:0 carrier:0
    | collisions:0 txqueuelen:0
    | RX bytes:2369 (2.3 Kb) TX bytes:2369 (2.3 Kb)
    |
    | wlan0 Link encap:Ethernet HWaddr 00:09:5B:8B:14:64
    | inet6 addr: fe80::209:5bff:fe8b:1464/64 Scope:Link
    | UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
    | RX packets:54 errors:0 dropped:15 overruns:0 frame:0
    | TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
    | collisions:0 txqueuelen:1000
    | RX bytes:2907 (2.8 Kb) TX bytes:4944 (4.8 Kb)
    | Interrupt:11 Memory:cff8e000-cff8e100
    |
    |
    | $ iwconfig
    |
    | wlan0 IEEE 802.11b ESSID:"thenetwork"
    | Mode:Managed Frequency:2.437 GHz Access Point: 00:14:6C:
    | DE:29:EE
    | Bit Rate=11 Mb/s Sensitivity=80/85
    | Retry: on Fragment thr: off
    | Encryption key:528C-7D5D-9482-1BE1-BEA3-ACE2-B7 Security
    | mode:restri
    | cted
    | Link Quality=97/100 Signal level=-37 dBm Noise level=-253
    | dBm
    | Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    | Tx excessive retries:0 Invalid misc:0 Missed beacon:0
    |
    | eth1 IEEE 802.11b ESSID:"" Nickname:"HERMES I"
    | Mode:Managed Frequency:2.457 GHz Access Point:
    | 00:00:00:00:00:00
    | Bit Rate:11 Mb/s Sensitivity:1/3
    | Retry limit:4 RTS thr: off Fragment thr: off
    | Encryption key: off
    | Power Management: off
    | Link Quality=0/92 Signal level=134/153 Noise level=134/153
    | Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    | Tx excessive retries:0 Invalid misc:0 Missed beacon:0
    |
    |
    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.2 (GNU/Linux)
    Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

    iD8DBQFIVDhr3s42bA80+9kRAsVuAJ0UP6yci1V6T5RChq4DsxXdyhw3DgCgitgI
    V/pNjFemiELsUgNBdyW0TJA=
    =HL3v
    -----END PGP SIGNATURE-----

  3. #3
    lindners NNTP User

    Default Re: Problem connecting to password-protected network

    I'll try networkmanager -- thanks!

    Stephan

  4. #4
    gieka NNTP User

    Default Re: Problem connecting to password-protected network

    Hi,

    I have almost the same problem:
    can't connect to WPA2 Personal ... I'm using NetworkManager to connect to AP but I'm always getting the windows asking for password... I know that I entering the correct pass but it does not working...
    System:
    OpenSuse 11 +Gnome, Netgear wg311v3 + Ndiswrapper

    I can see other AP near me and I know that card and drivers working (tested on ubuntu and win xp/vista)...

    Any ideas?

    Thanks!

  5. #5
    brig0803 NNTP User

    Default Re: Problem connecting to password-protected network

    Dear all,

    I have a problem similar to the user's one originally in this post.
    I have a MSI Wind with Opensuse 10.
    Please take note that I'm not used to Linux at all since it is the first time I use it.
    Wifi was working ok on it. I use to connect in some hotel to wireless network with and without password.
    Now, I've bought a wireless access point (Netgear WG602 v4) and I had no problem to connect at the beginning.
    Then, I decided to activate the WEP password protection and since then, there no way to connect to the wireless network again. The computer finds the network, prompts for the password but never gets to connect to it.
    Thank you so much for your advises.

  6. #6
    Join Date
    Jun 2008
    Location
    Kansas City Area, Missouri, USA
    Posts
    7,236

    Default Re: Problem connecting to password-protected network

    How are you putting in your WEP key. You must use the Hex key. For
    WEP, there are several ways to convert a passphrase to the key. If the
    Access point and the computer use different methods, authentication
    will fail.

    Does your AP support WPA? If so, use it. WPA has only a single method
    to go from phrase to key. In addition, it is much more secure. WEP can
    be broken in 5 minutes or less.

    Larry

Posting Permissions

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