IPW3945 not associating on WEP network *

ms.fellag · 2009-03-24 12:59:08

hello , after doing a "pacman -Syu" , wireless dont work , after configuring my wifi card it's not passible to retrieve IP with dhcpcd

the out put of : dhcpcd -d wlan0

# dhcpcd -d wlan0
info, wlan0: dhcpcd 3.2.1 starting
info, wlan0: hardware address = 00:18:de:cb:3e:01
info, wlan0: broadcasting for a lease
debug, wlan0: sending DHCP_DISCOVER with xid 0x176c4956
debug, wlan0: waiting on select for 20 seconds
debug, wlan0: sending DHCP_DISCOVER with xid 0x176c4956
debug, wlan0: sending DHCP_DISCOVER with xid 0x176c4956
debug, wlan0: sending DHCP_DISCOVER with xid 0x176c4956
debug, wlan0: sending DHCP_DISCOVER with xid 0x176c4956
debug, wlan0: sending DHCP_DISCOVER with xid 0x176c4956
debug, wlan0: sending DHCP_DISCOVER with xid 0x176c4956
err, wlan0: timed out
info, wlan0: trying to use old lease in `/var/lib/dhcpcd/dhcpcd-wlan0.info'

and this is what i do to run the wifi :

killall dhcpcd

ifconfig wlan0 up

iwlist wlan0 scan

iwconfig wlan0 mode managed channel 1 key off essid my_essid

some out put :

lshwd :

03:00.0 Class 0280: Intel Corporation|PRO/Wireless 3945ABG (ipw3945)

ifconfig :

wlan0     
Link encap:Ethernet  HWaddr 00:18:DE:CB:3E:01
UP BROADCAST MULTICAST  MTU:1500  Metric:1RX
packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

iwconfig :

lwlan0     IEEE 802.11abg  ESSID:"my_essid"
Mode:Managed  Frequency:2.412 GHz  Access Point:     Not-Associated
Tx-Power=15 dBmRetry min limit:7   RTS thr:off   Fragment thr=2352 B
Encryption key:off
Power Management: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

can you help me please ?

Ps1 : i have a hide essid
ps2: sorry about my "very" bad english

broch · 2009-03-25 02:50:46

I went back to the previous version of dhcpcd

.:B:. · 2009-03-25 16:11:45

Did it work before? Hidden SSIDs are generally problematic on Linux.

I am changing your topic btw - no need to put tags in, there is no ambiguity in iwl3945 - no other hardware besides wireless adapters using that driver .

ms.fellag · 2009-03-27 12:15:51

broch wrote:

I went back to the previous version of dhcpcd

i test : dhcpcd-3.2.3 , dhcpcd-4.99.15 , dhcpcd-4.0.12 , and dhcpcd-4.99.15 always the same problem

@B : thinks , i will try with out hide essid

ms.fellag · 2009-04-22 18:59:49

@B : I try it with out hide SSID but always the same problem

but when i use an old Arch version the wifi are correctly working with ipw3945 module but not before -Syu ( iwl3945 ) can i use ipw3945 with an 2.6.29 kernel ?

zenlord · 2009-04-23 12:04:33

ipw3945 is obsolete now that iwl3945 is part of the kernel (since .26 IIRC). Have you tried blacklisting the ipw-driver to see if iwl3945 is loaded automatically?

Zl.

.:B:. · 2009-04-23 12:29:19

iwl3945 uses the new wireless stack (formerly known as the Dscape/Devicescape stack), ipw3945 is the driver developed for the historical wireless stack. Both stacks are afaik still in the kernel, so if you want, you could use ipw3945 - but you'd need to rebuild the kernel (and probably build the driver against it afterwards).

ms.fellag · 2009-04-23 15:28:43

@B : thanks for explications , i found this : http://www.ubuntugeek.com/using-ipw3945 … hardy.html
but it's for ubuntu

zenlord wrote:

ipw3945 is obsolete now that iwl3945 is part of the kernel (since .26 IIRC). Have you tried blacklisting the ipw-driver to see if iwl3945 is loaded automatically?
Zl.

/etc/rc.conf

MODULES=(8139cp 8139too mii  iwl3945 snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore)

iwl3945 is loaded , but always the same probléme dhcpcd time out .

.:B:. · 2009-04-23 15:42:10

I just checked the stock Arch kernel config and the old stack is still enabled. So it would be enough to build the IPW3945 driver and the regulatory daemon and install those .

zenlord · 2009-04-23 16:16:06

OK, next suggestions:
1. Increase the timeout-length dhcpcd has to wait to get an IP-address (some DHCP-servers need more time than others)
2. Use dhclient instead of dhcpcd.

Both suggestions are really easy to setup/edit with netcfg (see the wiki for net-profiles)

Zl.

ms.fellag · 2009-04-23 17:15:29

zenlord wrote:

OK, next suggestions:
1. Increase the timeout-length dhcpcd has to wait to get an IP-address (some DHCP-servers need more time than others)
2. Use dhclient instead of dhcpcd.
Both suggestions are really easy to setup/edit with netcfg (see the wiki for net-profiles)
Zl.

i
- visit this page http://wiki.archlinux.org/index.php/Network_Profiles
- install : netcg + netcfgGUI + netcfg-auto
- desable the network daemon and remplace it with netcfg-auto
- run netcfgGUI
- New -> make a scan ( Hide mode desabled it's now an unhide SSID ) & configure dhcpcd time to 50 sec

and i have this ::Wlan0 up [Busy] DHCP IP lease attempt failed [Fail]

( it works correctly with eth0 )

@B : thanks for your help , i will need to read some doc after dowing this , because i have some probléms when i try to make the ipw driver ( ipw3945-1.2.2 :http://sourceforge.net/project/showfiles.php?group_id=158253&package_id=177235 )

make[2]: *** [/home/fellag/Download/ipw3945-1.2.2/ipw3945.o] Error 1
make[1]: *** [_module_/home/fellag/Download/ipw3945-1.2.2] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.29-ARCH'
make: *** [modules] Error 2

--edit

euh when i choose the dhcp time 50sec i have an error :" An error occured while connecting with netcfg and profile: wlan0 " and after ::Wlan0 up [Busy] DHCP IP lease attempt failed [Fail]

but when i keep it 10 sec i have just ::Wlan0 up [Busy] DHCP IP lease attempt failed [Fail]

Last edited by ms.fellag (2009-04-23 17:23:15)

PinkFloydYoshi · 2009-04-23 17:39:21

Just slightly OT, but isn't WEP incredibly unsecure? Heard of quite a few horror stories. WPA/TKIP with RADIUS is a nice option though but chances are you don't want to have to bother with RADIUS auth servers and whatnot. Arch with an Intel PRO/WIRELESS wlan card works a charm with WPA/TKIP as I've gone that direction, but due to go up to WPA/TKIP/RADIUS eventually as WPA has a few pitfalls too, but none anywhere near as bad as WEP.

Last edited by PinkFloydYoshi (2009-04-23 17:39:36)

ms.fellag · 2009-04-23 17:49:26

PinkFloydYoshi wrote:

Just slightly OT, but isn't WEP incredibly unsecure? Heard of quite a few horror stories. WPA/TKIP with RADIUS is a nice option though but chances are you don't want to have to bother with RADIUS auth servers and whatnot. Arch with an Intel PRO/WIRELESS wlan card works a charm with WPA/TKIP as I've gone that direction, but due to go up to WPA/TKIP/RADIUS eventually as WPA has a few pitfalls too, but none anywhere near as bad as WEP.

WEP ? i can't have an IP adresse .sorry but security is not really a problem now ( sorry if i am not understending 100% )

Last edited by ms.fellag (2009-04-23 18:05:19)

.:B:. · 2009-04-23 18:21:09

Just quoting those make errors doesn't help us, sorry. Throw all the output from make into a pastebin link (make sure you set the time to 'forever' or something reasonable for archiving purposes) and link to it here.

ms.fellag · 2009-04-23 18:50:46

B wrote:

Just quoting those make errors doesn't help us, sorry. Throw all the output from make into a pastebin link (make sure you set the time to 'forever' or something reasonable for archiving purposes) and link to it here.

http://pastebin.com/f5dac9ddd

.:B:. · 2009-04-24 08:07:31

By the way - did you see this topic?

I don't know if it will work (I have an IPW4965 card and never had to install crda to keep the wireless working with the newer kernels), but it's worth a shot - although the problem of the topic starter is not completely the same it's similar.

ms.fellag · 2009-08-10 01:52:58

/etc/rc.conf

# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)

just put out the "!" of "ROUTES=(!gateway)"

thanks for all
B : ty

iphitus · 2009-08-10 04:52:38

B might be on to something with the 'crda' requirement. Ensure you have that installed and configured, I'm sure its documented on the wiki.

It doesnt matter how much you mess about with routes, dhcp, dns, gateways, ponies - unless you have associated first, they won't work. Get the association right first.

broch · 2009-08-13 04:19:30

iwl3495 fails to keep WEP connection for longer than few seconds, WPA/WPA2 works though
another "popular" issue is AP configuration which is also buggy under linux (not Arch only)

It seems that there is not much you can do about WEP and iwl3945. CRDA is not related to this problem

Arch Linux

#1 2009-03-24 12:59:08

IPW3945 not associating on WEP network *

#2 2009-03-25 02:50:46

Re: IPW3945 not associating on WEP network *

#3 2009-03-25 16:11:45

Re: IPW3945 not associating on WEP network *

#4 2009-03-27 12:15:51

Re: IPW3945 not associating on WEP network *

#5 2009-04-22 18:59:49

Re: IPW3945 not associating on WEP network *

#6 2009-04-23 12:04:33

Re: IPW3945 not associating on WEP network *

#7 2009-04-23 12:29:19

Re: IPW3945 not associating on WEP network *

#8 2009-04-23 15:28:43

Re: IPW3945 not associating on WEP network *

#9 2009-04-23 15:42:10

Re: IPW3945 not associating on WEP network *

#10 2009-04-23 16:16:06

Re: IPW3945 not associating on WEP network *

#11 2009-04-23 17:15:29

Re: IPW3945 not associating on WEP network *

#12 2009-04-23 17:39:21

Re: IPW3945 not associating on WEP network *

#13 2009-04-23 17:49:26

Re: IPW3945 not associating on WEP network *

#14 2009-04-23 18:21:09

Re: IPW3945 not associating on WEP network *

#15 2009-04-23 18:50:46

Re: IPW3945 not associating on WEP network *

#16 2009-04-24 08:07:31

Re: IPW3945 not associating on WEP network *

#17 2009-08-10 01:52:58

Re: IPW3945 not associating on WEP network *

#18 2009-08-10 04:52:38

Re: IPW3945 not associating on WEP network *

#19 2009-08-13 04:19:30

Re: IPW3945 not associating on WEP network *

Board footer