| View previous topic :: View next topic |
| Author |
Message |
Skuromis
n00b
Joined: 02 Feb 2005
Posts: 40
Location: Lausanne
|
 Posted: Tue Mar 25, 2008 12:46 pm Post subject: wlan0 scan works, no conncetion to wep AP |
 |
|
Hi!
I'd need some help on my wireless lan.
It looks like the device itself works, as I can scan for networks (iwlist wlan0 scanning).
However, I can't connect to an 64bit wep access point and after reading so many threads I have no further clue, what to do.
cut from demsg:
| Quote: |
iwl4965: Intel(R) Wireless WiFi Link 4965AGN driver for Linux, 1.2.23ds
iwl4965: Copyright(c) 2003-2007 Intel Corporation
ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:03:00.0 to 64
iwl4965: Detected Intel Wireless WiFi Link 4965AGN
wmaster0: Selected rate control algorithm 'simple'
(...)
iwl4965: Tunable channels: 13 802.11bg, 19 802.11a channels
ADDRCONF(NETDEV_UP): wlan0: link is not ready
|
ifconfig
| Quote: |
eth0 Protokoll:Ethernet Hardware Adresse 00:13:77:3B:41:FE
inet Adresse:192.168.2.21 Bcast:192.168.2.255 Maske:255.255.255.0
inet6 Adresse: fe80::213:77ff:fe3b:41fe/64 Gültigkeitsbereich:Verbindung
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2695 errors:0 dropped:0 overruns:0 frame:0
TX packets:2544 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:1000
RX bytes:2829151 (2.6 Mb) TX bytes:491358 (479.8 Kb)
Interrupt:18
lo Protokoll:Lokale Schleife
inet Adresse:127.0.0.1 Maske:255.0.0.0
inet6 Adresse: ::1/128 Gültigkeitsbereich:Maschine
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
wlan0 Protokoll:Ethernet Hardware Adresse 00:13:E8:76:B9:2B
inet Adresse:169.254.125.233 Bcast:169.254.255.255 Maske:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
wmaster0 Protokoll:UNSPEC Hardware Adresse 00-13-E8-76-B9-2B-30-4E-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
|
iwconfig wlan0
| Quote: |
wlan0 IEEE 802.11g ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Encryption key:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
|
above surprises me, as I have following in the conf.d/net
| Quote: |
essid_wlan0="name"
config_wlan0=("dhcp")
dhcpcd_wlan0="-t 30"
|
Ok, once again, manually:
| Quote: |
Zwergenland linux # ifconfig wlan0 up
Zwergenland linux # iwconfig wlan0 essid name
Zwergenland linux # iwconfig wlan0 key ####-####-##
Zwergenland linux # dhcpcd wlan0
Error, wlan0: timed out
|
With Kanotix I get it running, but not with gentoo.
Does somehave have an idea?
Thank you,
Marc.
_________________
emerge -v information >> /dev/skuromis |
|
| Back to top |
|
 |
username234
Guru
Joined: 09 May 2007
Posts: 332
|
| Posted: Tue Mar 25, 2008 1:16 pm Post subject: |
|
|
| Skuromis wrote: | | Zwergenland linux # iwconfig wlan0 key ####-####-## |
check your encryption key, you appear to be short 6 hex digits (####-####-####-####).
_________________
Creating usernames when you're
in a creative slump is a bad idea
because if you are when you do
then you end up with uninspiring
alphanumeric cocktails like the
one directly above. |
|
| Back to top |
|
|
Skuromis
n00b
Joined: 02 Feb 2005
Posts: 40
Location: Lausanne
|
| Posted: Tue Mar 25, 2008 2:27 pm Post subject: |
|
|
Well, the key should be ok, as I used the same with kanotix where it worked.
Marc.
_________________
emerge -v information >> /dev/skuromis |
|
| Back to top |
|
|
username234
Guru
Joined: 09 May 2007
Posts: 332
|
| Posted: Wed Mar 26, 2008 3:03 am Post subject: |
|
|
| Skuromis wrote: | Well, the key should be ok, as I used the same with kanotix where it worked.
Marc. |
you're right, I am used to copying and pasting wep keys, so I forgot that part of it is automatically generated
| Code: |
Zwergenland linux # ifconfig wlan0 up
Zwergenland linux # iwconfig wlan0 essid name
Zwergenland linux # iwconfig wlan0 key ####-####-## |
when you perform these steps, can you connect with a static IP address?
_________________
Creating usernames when you're
in a creative slump is a bad idea
because if you are when you do
then you end up with uninspiring
alphanumeric cocktails like the
one directly above. |
|
| Back to top |
|
|
d2_racing
Bodhisattva
Joined: 25 Apr 2005
Posts: 13047
Location: Ste-Foy,Canada
|
| Posted: Wed Mar 26, 2008 3:35 am Post subject: |
|
|
| What kernel version are you using ? |
|
| Back to top |
|
|
Skuromis
n00b
Joined: 02 Feb 2005
Posts: 40
Location: Lausanne
|
| Posted: Wed Mar 26, 2008 9:07 am Post subject: |
|
|
Hi,
thanks for your replies!
I cannot connect with a static IP as I cannot change anything in the setup for the accespoint.
My kernel is 2.6.22-gentoo-r5.
Marc.
_________________
emerge -v information >> /dev/skuromis |
|
| Back to top |
|
|
d2_racing
Bodhisattva
Joined: 25 Apr 2005
Posts: 13047
Location: Ste-Foy,Canada
|
| Posted: Wed Mar 26, 2008 6:49 pm Post subject: |
|
|
| What wifi driver are you using ? Ipw3945 or the iwlwifi ? |
|
| Back to top |
|
|
Skuromis
n00b
Joined: 02 Feb 2005
Posts: 40
Location: Lausanne
|
| Posted: Fri Mar 28, 2008 9:25 pm Post subject: |
|
|
Hi!
I use the iwl4965
Marc.
_________________
emerge -v information >> /dev/skuromis |
|
| Back to top |
|
|
d2_racing
Bodhisattva
Joined: 25 Apr 2005
Posts: 13047
Location: Ste-Foy,Canada
|
| Posted: Sat Mar 29, 2008 1:28 am Post subject: |
|
|
| Maybe you should try the latest kernel : 2.6.24-Gentoo-r3 and use the driver iwl4965 inside the kernel. |
|
| Back to top |
|
|
|
Networking & Security
