Arch Linux

shnela

Member

Registered: 2012-02-12

Posts: 5

i can't connect with wep encrypted network

Hi,
I'm trying to connect with this accesspoint:

          Cell 03 - Address: 00:14:C1:30:FE:ED
                    Channel:11
                    Frequency:2.462 GHz (Channel 11)
                    Quality=40/70  Signal level=-70 dBm  
                    Encryption key:on
                    ESSID:"Masters"
                    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=000000063d3dc183
                    Extra: Last beacon: 136ms ago
                    IE: Unknown: 00074D617374657273
                    IE: Unknown: 010882848B962430486C
                    IE: Unknown: 03010B
                    IE: Unknown: 2A0100
                    IE: Unknown: 2F0100
                    IE: Unknown: 32040C121860
                    IE: Unknown: DD060010180201F5

Of course i tried:

[root@myhost shnela]# iwconfig wlan0 essid Masters key s:mastuning2000
[root@myhost shnela]# iwconfig 
lo        no wireless extensions.

wlan0     IEEE 802.11bgn  ESSID:"Masters"  
          Mode:Ad-Hoc  Frequency:2.412 GHz  Cell: 66:BA:DC:7E:D2:E5   
          Tx-Power=15 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:6D61-7374-756E-696E-6732-3030-30
          Power Management:off
          
eth0      no wireless extensions.

But I didn't get ip address:

[root@myhost shnela]# dhcpcd wlan0
dhcpcd[1040]: version 5.2.12 starting
dhcpcd[1040]: wlan0: waiting for carrier
dhcpcd[1040]: timed out

or

[root@myhost shnela]# dhcpcd wlan0
dhcpcd[1092]: version 5.2.12 starting
dhcpcd[1092]: wlan0: rebinding lease of 192.168.4.63
dhcpcd[1092]: wlan0: broadcasting for a lease
dhcpcd[1092]: timed out

I tried also netcfg with profle "stancja":

CONNECTION='wireless'
DESCRIPTION='A simple WEP encrypted wireless connection'
INTERFACE='wlan0'
SECURITY='wep'
ESSID='Masters'
KEY='s:mastuning2000'
IP='dhcp'
# Uncomment this if your ssid is hidden
#HIDDEN=yes

But when I use it, it returns:

[root@myhost network.d]# netcfg stancja
:: stancja up                                                                                             [BUSY]
 > WPA Authentication/Association Failed

I don't know what WPA Autenthication do here...

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 19,956

Re: i can't connect with wep encrypted network

You are a bit ahead of yourself trying to run DHCP.  You are not associated with the router yet.  Take a look at the frequencies -- the router is at 2.462 GHz, your card is on 2.412 GHz.  Also, your card is in ad-hoc mode.

Here is my connection:

wlan0     IEEE 802.11bg  ESSID:"Woodlyn"  
          Mode:Managed  Frequency:2.462 GHz  Access Point: C4:3D:C7:5D:EB:8D   
          Bit Rate=24 Mb/s   Tx-Power=20 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=57/70  Signal level=-53 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:398  Invalid misc:21891   Missed beacon:0

Note the access point MAC.  When you are connected, yours will say 00:14:C1:30:FE:ED.  The mode will say "managed"

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

shnela

Member

Registered: 2012-02-12

Posts: 5

Re: i can't connect with wep encrypted network

Oh.. I'm very sorry. I confused my "iwconfig" output...
I've similar problem with this particular ap with debian too ( I can connect onnly with wicd).
I changed frequency and tried change ap addr:

[root@myhost shnela]# iwconfig wlan0 ap 00:14:C1:30:FE:ED
[root@myhost shnela]# iwconfig wlan0 freq 2.462G
[root@myhost shnela]# iwconfig
lo        no wireless extensions.

wlan0     IEEE 802.11bgn  ESSID:"Masters"
          Mode:Managed  Frequency:2.462 GHz  Access Point: Not-Associated
          Tx-Power=15 dBm
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:6D61-7374-756E-696E-6732-3030-30
          Power Management:off

eth0      no wireless extensions.

[root@myhost shnela]# dhcpcd wlan0
dhcpcd[1336]: version 5.2.12 starting
dhcpcd[1336]: wlan0: waiting for carrier
dhcpcd[1336]: timed out

I'm stil Not-Associated.

This is my rc.conf file:

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

# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# DAEMON_LOCALE: If set to 'yes', use $LOCALE as the locale during daemon
# startup and during the boot process. If set to 'no', the C locale is used.
# HARDWARECLOCK: set to "", "UTC" or "localtime", any other value will result
#   in the hardware clock being left untouched (useful for virtualization)
#   Note: Using "localtime" is discouraged, using "" makes hwclock fall back
#   to the value in /var/lib/hwclock/adjfile
# TIMEZONE: timezones are found in /usr/share/zoneinfo
#   Note: if unset, the value in /etc/localtime is used unchanged
# 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.UTF-8"
DAEMON_LOCALE="no"
HARDWARECLOCK="localtime"
TIMEZONE="Europe/Warsaw"
KEYMAP="en"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MODULES: Modules to load at boot-up. Blacklisting is no longer supported.
#   Replace every !module by an entry as on the following line in a file in
#   /etc/modprobe.d:
#     blacklist module
#   See "man modprobe.conf" for details.
#
MODULES=()

# Udev settle timeout (default to 15)
UDEV_TIMEOUT=30

# Scan for FakeRAID (dmraid) Volumes at startup
USEDMRAID="no"

# Scan for BTRFS volumes at startup
USEBTRFS="no"

# 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 'ip addr' or 'ls /sys/class/net/' to see all available interfaces.
#
# Wired network setup
#   - interface: name of device (required)
#   - address: IP address (leave blank for DHCP)
#   - netmask: subnet mask (ignored for DHCP) (optional, defaults to 255.255.255.0)
#   - broadcast: broadcast address (ignored for DHCP) (optional)
#   - gateway: default route (ignored for DHCP)
# 
# Static IP example
# interface=eth0
# address=192.168.0.2
# netmask=255.255.255.0
# broadcast=192.168.0.255
# gateway=192.168.0.1
#
# DHCP example
# interface=eth0
# address=
# netmask=
# gateway=

interface=wlan0
address=
netmask=
broadcast=
gateway=

# Setting this to "yes" will skip network shutdown.
# This is required if your root device is on NFS.
NETWORK_PERSIST="no"

# Enable these netcfg profiles at boot-up. These are useful if you happen to
# need more advanced network features than the simple network service
# supports, such as 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 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
#
# If something other takes care of your hardware clock (ntpd, dual-boot...)
# you should disable 'hwclock' here.
#
DAEMONS=(hwclock syslog-ng network netfs crond alsa sensors)

Last edited by shnela (2012-02-12 20:23:50)

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 19,956

Re: i can't connect with wep encrypted network

Is it your router?  Can you turn of WEP and associate?
What is your wireless chipset?

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

shnela

Member

Registered: 2012-02-12

Posts: 5

Re: i can't connect with wep encrypted network

Unfortunately I can't change anything on router,
My chipset:

shnela@shl:~$ lspci | grep Network
09:00.0 Network controller: Intel Corporation Centrino Wireless-N 1030 (rev 34)

As i said, I can connect only using wicd ( on Debian) or on Windows.

Strike0

Member

From: Germany

Registered: 2011-09-05

Posts: 1,429

Re: i can't connect with wep encrypted network

In your last try posted here #3 you don't activate the link, try

ip link set wlan0 up

before doing the first iwconfig command.

Avant-texte

Member

Registered: 2012-02-13

Posts: 136

Re: i can't connect with wep encrypted network

Have you tried inputing the the WEP key as a hex string rather than using the s: prefix?

shnela

Member

Registered: 2012-02-12

Posts: 5

Re: i can't connect with wep encrypted network

In your last try posted here #3 you don't activate the link, try

ip link set wlan0 up

before doing the first iwconfig command.

Have you tried inputing the the WEP key as a hex string rather than using the s: prefix?

Both doesn't work. I also tried change channel, but still can't associate with my ap.

Strike0

Member

From: Germany

Registered: 2011-09-05

Posts: 1,429

Re: i can't connect with wep encrypted network

In your rc.conf you have configured "wlan0" as interface. That is wrong there; the section is only for wired interfaces. Take it out there. You don't need to specify it anywhere for now.
Then please try again after rebooting according to the manual connection method from the wiki and post output again where it fails.

beretta

Member

Registered: 2008-04-21

Posts: 133

Re: i can't connect with wep encrypted network

I have a brand new laptop (Lenovo u400) that has the same wireless card; I've been having the same problem, though sometimes it does let me connect.  I'll try taking the line out of rc.conf, though I recall the Beginner's Wiki saying it should be there... I may be wrong and went through it too quickly.

If I find anything more, I'll post it of course.

sealclubber

Member

Registered: 2012-04-16

Posts: 34

Re: i can't connect with wep encrypted network

Have you tried doing it manually with wpa_supplicant? I always find that works the best for me.

---

When I  win the lottery, the first thing I will do, before I buy a new car or a house, would be to buy a goddamn Cisco XR 12000 router and enough T3 lines to wire a country.

http://myanimelist.net/profile/sealclubber