Intel4965 | Association/DHCP | Status Issue

Sjoden · 2008-07-02 22:05:10

I can't reliably connect to any network. I have tried just iwconfig, wpa_supplicant, and netcfg with archassistant, and I can't figure out what the problem is.

Generally, to connect I have to run these commands, and this will "usually", but NOT always get me connected to a WEP network.

iwconfig wlan0 essid APNAME
iwconfig wlan0 key 1234567890
dhcpcd wlan0 <times out everytime>
iwlist wlan0 scan <always shows results, although for 2 kernel revisions it didn't>
rm /var/run/dhcpcd-wlan0.pid
dhcpcd wlan0<finally works>

Information/things I have tried.
The 4965 module is in my modules array.

ifconfig wlan0 up

doesn't help.
Putting 'wlan0' in the interfaces array in rc.conf doesn't help.

I was able to connect with wpa_supplicant a few minutes ago. I still had to do that dhcpcd and iwlist stuff, but it worked.
Then I put

wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -B

in my rc.local(command I used to get it working the first time, except the -B) and restarted. Starting up wpa_gui showed that I was associated, but I could not get an IP address. I disconnected, reconnected, did the dhcpcd stuff, and nothing

Netcfg also didn't work. On launching archassistant, and then trying to connect to one of the profiles I set up through archassistant, I get this;

wireless device set in config :   

wireless device used :  wlan0 

profile started : npnwap 1 

error issuing netcfg command.

Double clicking the archassistant icon in the tray, or trying to scan in archassistant, I get this error;

error ifconfigUpProcess

Dmesg;

[zack@boxxy ~]$ dmesg | grep 4965
iwl4965: Intel(R) Wireless WiFi Link 4965AGN driver for Linux, 1.2.23k
iwl4965: Copyright(c) 2003-2007 Intel Corporation
iwl4965: Detected Intel Wireless WiFi Link 4965AGN
iwl4965: Tunable channels: 11 802.11bg, 13 802.11a channels
phy0: Selected rate control algorithm 'iwl-4965-rs'

I appreciate any suggestions.
Zack

Last edited by Sjoden (2008-07-07 21:03:21)

iphitus · 2008-07-03 10:44:11

Try netcfg in [testing]..

Mess about with the quirks here and see which works for your device. Might need prescan and preessid. Try with/without both and work out what seems to work best.

http://wiki.archlinux.org/index.php/Net … evelopment

SiB · 2008-07-03 19:19:45

I have the same card on my laptop. Im using wicd and it's working flawlessly. Maybe it's worth a try .

Last edited by SiB (2008-07-03 19:20:00)

smartcat99s · 2008-07-04 19:04:06

I have my 4965 working with WEP and netcfg2 (both in testing and not, and without any quirks), and it always requires me to try at least twice to connect, sometimes more.

I just ended up doing something like this in my .zshrc

function connect() { sudo netcfg2 home-wireless || connect }

Last edited by smartcat99s (2008-07-04 19:04:22)

iphitus · 2008-07-05 00:55:49

See if theres any changes or anything I can add to netcfg to try and make it work, i could add a quirk if you can track down what's needed.

Did you mess around trying combinations of the prescan and preessid quirks in netcfg2 from [testing]?

Last edited by iphitus (2008-07-05 00:56:43)

Sjoden · 2008-07-05 02:54:46

Sorry iphitus, I didn't try netcfg2 in testing. I did get it working with wicd though. First try. I am quite pleased to not have to unroll a cable through our new living room each time I get online at home .

Zack

Sjoden · 2008-07-06 00:39:23

Now I'm just wondering what wicd does that is different. I can't think of what its doing to make it work everytime now.

iphitus · 2008-07-06 12:57:06

Could you please try my suggestions regarding netcfg2?

Kane · 2008-07-06 15:52:40

i think the difference is that wicd keeps trying to autoconnect,

i've also experienced the same problem using netcfg2 and only been able to use wicd as a work around to solve it.

Last edited by Kane (2008-07-06 15:53:54)

Sjoden · 2008-07-06 22:43:06

iphitus wrote:

Could you please try my suggestions regarding netcfg2?

Sure, I'll give it a try tonight. I'll probably post back in 3+ hours since were heading out now.

Sjoden · 2008-07-07 21:13:15

Sorry I didn't post last night, we went to my sister in laws house.

I started up my laptop at work today. Wicd took two tries to connect to my works WAP(s, we have 3 of them, all the same name, for roaming). I do a 'pacman -Syu'. It runs smoothly, only warning I get is about a font-config change. I only have 1 extra font pkg installed so I didn't worry about it.

I reboot, and wicd fails. I can associate, but I can't get an IP address. I try all 3 WAPs, none work. I try different things for about 30 minutes, rebooting, retyping key, restarting the service and the tray.py for wicd, nothing.

Plug in my network cable, Add the testing repo, re sync, and 'pacman -S testing/netcfg'. All runs fine. I make a profile from the default wep.example;

[zack@boxxy ~]$ cat /etc/network.d/???wap 
CONNECTION="wireless"
DESCRIPTION="???'s external wireless network."
INTERFACE=wlan0
SCAN="yes"
SECURITY="wep"
ESSID="???WAP"
KEY="1234567890"
IP="dhcp"

I run 'netcfg2 ???wap'. It fails. I run it again, it finishes. I unplug the networking cable. No go. I remove the pid for dhcpcd on eth0, nothing. I kill dhcpcd and dhclient. Retry, nothing. I reboot, retry netcfg2, nothing again. I'm about to try and figure out how to use the quirks.

From /var/log/messages.log;

Jul  7 15:12:16 boxxy dhclient: Internet Systems Consortium DHCP Client V3.0.6
Jul  7 15:12:16 boxxy dhclient: Copyright 2004-2007 Internet Systems Consortium.
Jul  7 15:12:16 boxxy dhclient: All rights reserved.
Jul  7 15:12:16 boxxy dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Jul  7 15:12:16 boxxy dhclient: 
Jul  7 15:12:17 boxxy dhclient: Listening on LPF/wlan0/00:13:e8:2e:83:15
Jul  7 15:12:17 boxxy dhclient: Sending on   LPF/wlan0/00:13:e8:2e:83:15
Jul  7 15:12:17 boxxy dhclient: Sending on   Socket/fallback
Jul  7 15:12:19 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul  7 15:12:27 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul  7 15:12:47 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
Jul  7 15:12:51 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
Jul  7 15:13:00 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
Jul  7 15:13:12 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Jul  7 15:13:20 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
Jul  7 15:13:35 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
Jul  7 15:13:48 boxxy dhclient: No DHCPOFFERS received.
Jul  7 15:13:48 boxxy dhclient: Trying recorded lease 192.168.5.24
Jul  7 15:13:51 boxxy dhclient: Trying recorded lease 192.168.2.196
Jul  7 15:13:54 boxxy dhclient: No working leases in persistent database - sleeping.
Jul  7 15:14:26 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
Jul  7 15:14:26 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Jul  7 15:14:29 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
Jul  7 15:14:29 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Jul  7 15:14:29 boxxy dhclient: There is already a pid file /var/run/dhclient.pid with pid 3963
Jul  7 15:14:29 boxxy dhclient: removed stale PID file
Jul  7 15:14:29 boxxy dhclient: Internet Systems Consortium DHCP Client V3.0.6
Jul  7 15:14:29 boxxy dhclient: Copyright 2004-2007 Internet Systems Consortium.
Jul  7 15:14:29 boxxy dhclient: All rights reserved.
Jul  7 15:14:29 boxxy dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Jul  7 15:14:29 boxxy dhclient: 
Jul  7 15:14:30 boxxy dhclient: Listening on LPF/wlan0/00:13:e8:2e:83:15
Jul  7 15:14:30 boxxy dhclient: Sending on   LPF/wlan0/00:13:e8:2e:83:15
Jul  7 15:14:30 boxxy dhclient: Sending on   Socket/fallback
Jul  7 15:14:31 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul  7 15:14:39 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul  7 15:14:55 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
Jul  7 15:15:02 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
Jul  7 15:15:15 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
Jul  7 15:15:25 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19
Jul  7 15:15:44 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
Jul  7 15:15:56 boxxy dhclient: No DHCPOFFERS received.
Jul  7 15:15:56 boxxy dhclient: Trying recorded lease 192.168.5.24
Jul  7 15:15:59 boxxy dhclient: Trying recorded lease 192.168.2.196
Jul  7 15:16:02 boxxy dhclient: No working leases in persistent database - sleeping.
Jul  7 15:17:31 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
Jul  7 15:17:31 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Jul  7 15:17:33 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
Jul  7 15:17:33 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Jul  7 15:17:33 boxxy dhclient: There is already a pid file /var/run/dhclient.pid with pid 5007
Jul  7 15:17:33 boxxy dhclient: removed stale PID file
Jul  7 15:17:33 boxxy dhclient: Internet Systems Consortium DHCP Client V3.0.6
Jul  7 15:17:33 boxxy dhclient: Copyright 2004-2007 Internet Systems Consortium.
Jul  7 15:17:33 boxxy dhclient: All rights reserved.
Jul  7 15:17:33 boxxy dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Jul  7 15:17:33 boxxy dhclient: 
Jul  7 15:17:34 boxxy dhclient: Listening on LPF/wlan0/00:13:e8:2e:83:15
Jul  7 15:17:34 boxxy dhclient: Sending on   LPF/wlan0/00:13:e8:2e:83:15
Jul  7 15:17:34 boxxy dhclient: Sending on   Socket/fallback
Jul  7 15:17:35 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul  7 15:17:40 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul  7 15:17:47 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
Jul  7 15:17:52 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Jul  7 15:18:00 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
Jul  7 15:18:14 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
Jul  7 15:18:30 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
Jul  7 15:18:48 boxxy dhclient: No DHCPOFFERS received.
Jul  7 15:18:48 boxxy dhclient: Trying recorded lease 192.168.5.24
Jul  7 15:18:51 boxxy dhclient: Trying recorded lease 192.168.2.196
Jul  7 15:18:54 boxxy dhclient: No working leases in persistent database - sleeping.
Jul  7 15:21:39 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
Jul  7 15:21:40 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Jul  7 15:21:59 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
Jul  7 15:21:59 boxxy r8169: eth0: link down
Jul  7 15:21:59 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Jul  7 15:22:01 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
Jul  7 15:22:01 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Jul  7 15:22:02 boxxy dhclient: There is already a pid file /var/run/dhclient.pid with pid 6427
Jul  7 15:22:02 boxxy dhclient: removed stale PID file
Jul  7 15:22:02 boxxy dhclient: Internet Systems Consortium DHCP Client V3.0.6
Jul  7 15:22:02 boxxy dhclient: Copyright 2004-2007 Internet Systems Consortium.
Jul  7 15:22:02 boxxy dhclient: All rights reserved.
Jul  7 15:22:02 boxxy dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Jul  7 15:22:02 boxxy dhclient: 
Jul  7 15:22:03 boxxy dhclient: Listening on LPF/wlan0/00:13:e8:2e:83:15
Jul  7 15:22:03 boxxy dhclient: Sending on   LPF/wlan0/00:13:e8:2e:83:15
Jul  7 15:22:03 boxxy dhclient: Sending on   Socket/fallback
Jul  7 15:22:04 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul  7 15:22:12 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul  7 15:22:31 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
Jul  7 15:22:37 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
Jul  7 15:22:48 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 21
Jul  7 15:23:09 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
Jul  7 15:23:27 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
Jul  7 15:23:32 boxxy dhclient: No DHCPOFFERS received.
Jul  7 15:23:32 boxxy dhclient: Trying recorded lease 192.168.5.24
Jul  7 15:23:35 boxxy dhclient: Trying recorded lease 192.168.2.196
Jul  7 15:23:38 boxxy dhclient: No working leases in persistent database - sleeping.
Jul  7 15:24:58 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
Jul  7 15:24:58 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Jul  7 15:25:00 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
Jul  7 15:25:00 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Jul  7 15:25:01 boxxy dhclient: There is already a pid file /var/run/dhclient.pid with pid 8688
Jul  7 15:25:01 boxxy dhclient: removed stale PID file
Jul  7 15:25:01 boxxy dhclient: Internet Systems Consortium DHCP Client V3.0.6
Jul  7 15:25:01 boxxy dhclient: Copyright 2004-2007 Internet Systems Consortium.
Jul  7 15:25:01 boxxy dhclient: All rights reserved.
Jul  7 15:25:01 boxxy dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Jul  7 15:25:01 boxxy dhclient: 
Jul  7 15:25:02 boxxy dhclient: Listening on LPF/wlan0/00:13:e8:2e:83:15
Jul  7 15:25:02 boxxy dhclient: Sending on   LPF/wlan0/00:13:e8:2e:83:15
Jul  7 15:25:02 boxxy dhclient: Sending on   Socket/fallback
Jul  7 15:25:03 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul  7 15:25:11 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul  7 15:25:20 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
Jul  7 15:25:26 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
Jul  7 15:25:37 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
Jul  7 15:25:47 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
Jul  7 15:25:54 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
Jul  7 15:26:01 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
Jul  7 15:26:14 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
Jul  7 15:26:21 boxxy dhclient: No DHCPOFFERS received.
Jul  7 15:26:21 boxxy dhclient: Trying recorded lease 192.168.5.24
Jul  7 15:26:24 boxxy dhclient: Trying recorded lease 192.168.2.196
Jul  7 15:26:27 boxxy dhclient: No working leases in persistent database - sleeping.
Jul  7 15:29:35 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
Jul  7 15:29:35 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Jul  7 15:29:37 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
Jul  7 15:29:37 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Jul  7 15:29:38 boxxy dhclient: There is already a pid file /var/run/dhclient.pid with pid 9688
Jul  7 15:29:38 boxxy dhclient: removed stale PID file
Jul  7 15:29:38 boxxy dhclient: Internet Systems Consortium DHCP Client V3.0.6
Jul  7 15:29:38 boxxy dhclient: Copyright 2004-2007 Internet Systems Consortium.
Jul  7 15:29:38 boxxy dhclient: All rights reserved.
Jul  7 15:29:38 boxxy dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Jul  7 15:29:38 boxxy dhclient: 
Jul  7 15:29:39 boxxy dhclient: Listening on LPF/wlan0/00:13:e8:2e:83:15
Jul  7 15:29:39 boxxy dhclient: Sending on   LPF/wlan0/00:13:e8:2e:83:15
Jul  7 15:29:39 boxxy dhclient: Sending on   Socket/fallback
Jul  7 15:29:42 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul  7 15:29:49 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul  7 15:30:03 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
Jul  7 15:30:10 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
Jul  7 15:30:28 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
Jul  7 15:30:38 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
Jul  7 15:30:49 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
Jul  7 15:31:04 boxxy dhclient: No DHCPOFFERS received.
Jul  7 15:31:04 boxxy dhclient: Trying recorded lease 192.168.5.24
Jul  7 15:31:07 boxxy dhclient: Trying recorded lease 192.168.2.196
Jul  7 15:31:10 boxxy dhclient: No working leases in persistent database - sleeping.
Jul  7 15:31:55 boxxy r8169: eth0: link up
Jul  7 15:31:56 boxxy r8169: eth0: link down
Jul  7 15:31:57 boxxy r8169: eth0: link up
Jul  7 15:32:00 boxxy r8169: eth0: link down
Jul  7 15:32:02 boxxy r8169: eth0: link up
Jul  7 15:32:32 boxxy NET: Registered protocol family 10
Jul  7 15:32:32 boxxy lo: Disabled Privacy Extensions
Jul  7 15:32:38 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
Jul  7 15:33:27 boxxy dhcpcd[12617]: eth0: dhcpcd 3.2.1 starting
Jul  7 15:33:27 boxxy dhcpcd[12617]: eth0: hardware address = 00:13:a9:f1:a0:b7
Jul  7 15:33:27 boxxy dhcpcd[12617]: eth0: broadcasting for a lease
Jul  7 15:33:30 boxxy dhcpcd[12617]: eth0: offered 10.0.1.106 from 10.0.1.200
Jul  7 15:33:30 boxxy dhcpcd[12617]: eth0: checking 10.0.1.106 is available on attached networks
Jul  7 15:33:31 boxxy dhcpcd[12617]: eth0: leased 10.0.1.106 for 86400 seconds
Jul  7 15:33:31 boxxy dhcpcd[12617]: eth0: adding IP address 10.0.1.106/16
Jul  7 15:33:31 boxxy dhcpcd[12617]: eth0: adding default route via 10.0.1.1 metric 0
Jul  7 15:33:31 boxxy dhcpcd[12617]: eth0: adding route to 169.254.0.0/16 metric 0
Jul  7 15:33:31 boxxy dhcpcd[12617]: eth0: exiting
Jul  7 15:54:29 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Jul  7 15:54:29 boxxy ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jul  7 15:55:39 boxxy ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Jul  7 15:55:42 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul  7 15:55:42 boxxy dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
Jul  7 15:55:42 boxxy dhclient: DHCPOFFER from 10.0.1.200
Jul  7 15:55:42 boxxy dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jul  7 15:55:42 boxxy dhclient: DHCPACK from 10.0.1.200
Jul  7 15:55:42 boxxy dhclient: bound to 10.0.1.106 -- renewal in 32528 seconds.
Jul  7 15:55:43 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 5
Jul  7 15:55:45 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul  7 15:55:48 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 5
Jul  7 15:55:50 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul  7 15:55:53 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 6
Jul  7 15:55:59 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 7
Jul  7 15:56:00 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
Jul  7 15:56:00 boxxy r8169: eth0: link down
Jul  7 15:56:06 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 13
Jul  7 15:56:07 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 20
Jul  7 15:56:19 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 10
Jul  7 15:56:27 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 21
Jul  7 15:56:29 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 10
Jul  7 15:56:39 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 5
Jul  7 15:56:44 boxxy dhclient: No DHCPOFFERS received.
Jul  7 15:56:44 boxxy dhclient: No working leases in persistent database - sleeping.
Jul  7 15:56:48 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
Jul  7 15:57:01 boxxy dhclient: No DHCPOFFERS received.
Jul  7 15:57:01 boxxy dhclient: Trying recorded lease 192.168.5.24
Jul  7 15:57:05 boxxy dhcpcd[12618]: eth0: received SIGTERM, stopping
Jul  7 15:57:05 boxxy dhcpcd[12618]: eth0: removing default route via 10.0.1.1 metric 0
Jul  7 15:57:05 boxxy dhcpcd[12618]: eth0: removing route to 169.254.0.0/16 metric 0
Jul  7 15:57:05 boxxy dhcpcd[12618]: eth0: removing IP address 10.0.1.106/16
Jul  7 15:57:05 boxxy dhcpcd[12618]: eth0: exiting
Jul  7 15:57:19 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul  7 15:57:19 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 6
Jul  7 15:57:20 boxxy dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jul  7 15:57:23 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul  7 15:57:24 boxxy dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jul  7 15:57:25 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 15
Jul  7 15:57:27 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul  7 15:57:30 boxxy dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jul  7 15:57:35 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
Jul  7 15:57:38 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
Jul  7 15:57:40 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 21
Jul  7 15:57:41 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Jul  7 15:57:42 boxxy dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
Jul  7 15:57:45 boxxy dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
Jul  7 15:57:48 boxxy dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
Jul  7 15:57:49 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
Jul  7 15:57:53 boxxy dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
Jul  7 15:58:01 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 16
Jul  7 15:58:01 boxxy dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 21
Jul  7 15:58:07 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Jul  7 15:58:15 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
Jul  7 15:58:17 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 3
Jul  7 15:58:20 boxxy dhclient: No DHCPOFFERS received.
Jul  7 15:58:20 boxxy dhclient: No working leases in persistent database - sleeping.
Jul  7 15:58:22 boxxy dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16
Jul  7 15:58:26 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Jul  7 15:58:34 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 2
Jul  7 15:58:36 boxxy dhclient: No DHCPOFFERS received.
Jul  7 15:58:36 boxxy dhclient: Trying recorded lease 192.168.5.24
Jul  7 15:58:39 boxxy dhclient: Trying recorded lease 192.168.2.196
Jul  7 15:58:42 boxxy dhclient: No working leases in persistent database - sleeping.
Jul  7 15:58:42 boxxy dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 1
Jul  7 15:58:43 boxxy dhclient: No DHCPOFFERS received.
Jul  7 15:58:43 boxxy dhclient: Trying recorded lease 10.0.1.106
Jul  7 15:58:46 boxxy dhclient: No working leases in persistent database - sleeping.
[root@boxxy examples]#

From /var/log/pacman.log;

[2008-07-07 13:25] synchronizing package lists
[2008-07-07 13:26] starting full system upgrade
[2008-07-07 14:42] upgraded freetype2 (2.3.6-1 -> 2.3.7-1)
[2008-07-07 14:42] Symlinking new configuration files... done.
[2008-07-07 14:42] 
[2008-07-07 14:42] ===> Important Fontconfig configuration change <===
[2008-07-07 14:42] 
[2008-07-07 14:42]   The way fontconfig is configured has been changed. 
[2008-07-07 14:42]   Configuration is done via /etc/fonts/conf.avail and conf.d.
[2008-07-07 14:42]   Read /etc/fonts/conf.avail/README for more information.
[2008-07-07 14:42] 
[2008-07-07 14:42]   Configuration via /etc/fonts/local.conf is still possible,
[2008-07-07 14:42]   but is no longer recommended for options available in conf.avail.
[2008-07-07 14:42] 
[2008-07-07 14:42] Adding missing configuration files... done.
[2008-07-07 14:42] Removing outdated configuration files... done.
[2008-07-07 14:43] updating font cache... done.
[2008-07-07 14:43] upgraded fontconfig (2.5.0-1 -> 2.6.0-2)
[2008-07-07 14:43] upgraded gcc-libs (4.3.1-1 -> 4.3.1-2)
[2008-07-07 14:43] upgraded gcc (4.3.1-1 -> 4.3.1-2)
[2008-07-07 14:43] upgraded glibmm (2.16.2-1 -> 2.16.4-1)
[2008-07-07 14:43] >>> Updating module dependencies. Please wait ...
[2008-07-07 14:43] >>> MKINITCPIO SETUP
[2008-07-07 14:43] >>> ----------------
[2008-07-07 14:43] >>> If you use LVM2, Encrypted root or software RAID,
[2008-07-07 14:43] >>> Ensure you enable support in /etc/mkinitcpio.conf .
[2008-07-07 14:43] >>> More information about mkinitcpio setup can be found here:
[2008-07-07 14:43] >>> http://wiki.archlinux.org/index.php/Mkinitcpio
[2008-07-07 14:43] 
[2008-07-07 14:43] >>> Generating initial ramdisk, using mkinitcpio.  Please wait...
[2008-07-07 14:43] ==> Building image "default"
[2008-07-07 14:43] ==> Running command: /sbin/mkinitcpio -k 2.6.25-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
[2008-07-07 14:43] :: Begin build
[2008-07-07 14:43] :: Parsing hook [base]
[2008-07-07 14:43] :: Parsing hook [udev]
[2008-07-07 14:43] :: Parsing hook [autodetect]
[2008-07-07 14:43] :: Parsing hook [pata]
[2008-07-07 14:43] :: Parsing hook [scsi]
[2008-07-07 14:43] :: Parsing hook [sata]
[2008-07-07 14:43] :: Parsing hook [keymap]
[2008-07-07 14:43] :: Parsing hook [filesystems]
[2008-07-07 14:43] :: Generating module dependencies
[2008-07-07 14:43] :: Generating image '/boot/kernel26.img'...SUCCESS
[2008-07-07 14:43] ==> SUCCESS
[2008-07-07 14:43] ==> Building image "fallback"
[2008-07-07 14:43] ==> Running command: /sbin/mkinitcpio -k 2.6.25-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26-fallback.img -S autodetect
[2008-07-07 14:43] :: Begin build
[2008-07-07 14:43] :: Parsing hook [base]
[2008-07-07 14:43] :: Parsing hook [udev]
[2008-07-07 14:43] :: Parsing hook [pata]
[2008-07-07 14:43] :: Parsing hook [scsi]
[2008-07-07 14:43] :: Parsing hook [sata]
[2008-07-07 14:44] :: Parsing hook [keymap]
[2008-07-07 14:44] :: Parsing hook [filesystems]
[2008-07-07 14:44] :: Generating module dependencies
[2008-07-07 14:44] :: Generating image '/boot/kernel26-fallback.img'...SUCCESS
[2008-07-07 14:44] ==> SUCCESS
[2008-07-07 14:44] upgraded kernel26 (2.6.25.6-1 -> 2.6.25.10-1)
[2008-07-07 14:44] upgraded lame (3.97-1 -> 3.98-1)
[2008-07-07 14:44] upgraded libpng (1.2.28-1 -> 1.2.29-1)
[2008-07-07 14:44] upgraded libsm (1.0.3-1 -> 1.1.0-1)
[2008-07-07 14:44] upgraded libxfont (1.3.2-1 -> 1.3.3-1)
[2008-07-07 14:44] upgraded libxft (2.1.12-1 -> 2.1.13-1)
[2008-07-07 14:44] upgraded libxp (1.0.0-1 -> 1.0.0-2)
[2008-07-07 14:44] upgraded randrproto (1.2.1-1 -> 1.2.2-1)
[2008-07-07 14:44] upgraded libxrandr (1.2.2-1 -> 1.2.3-1)
[2008-07-07 14:44] upgraded libxtrap (1.0.0-1 -> 1.0.0-2)
[2008-07-07 14:44] upgraded libxxf86vm (1.0.1-1 -> 1.0.2-1)
[2008-07-07 14:44] upgraded nss (3.12rc4-1 -> 3.12-1)
[2008-07-07 14:44] upgraded xf86-input-mouse (1.2.3-1 -> 1.3.0-1)
[2008-07-07 14:44] upgraded xorg-xauth (1.0.2-1 -> 1.0.3-1)
[2008-07-07 14:44] upgraded xorg-xkb-utils (1.0.2-2 -> 7.3-1)
[2008-07-07 14:44] upgraded xtrans (1.2-1 -> 1.2.1-1)
[2008-07-07 15:33] synchronizing package lists
[2008-07-07 15:33] starting full system upgrade
[2008-07-07 15:34] upgraded pcre (7.7-1 -> 7.7-2)
[2008-07-07 15:35] synchronizing package lists
[2008-07-07 15:47] installed netcfg (2.1.0_B2-1)

This is rediculous.
Zack

/edit
I was able to load the google homepage after adding the preessid quirk, and using the 'netcfg' command instead of 'netcfg2'. I restarted, and it doesn't work(I'm pretty sure my eth cable was unplugged when loaded, could be wrong);

[root@boxxy zack]# netcfg npnwap
:: npnwap up  - Wireless association failed.                             [FAIL] 
[root@boxxy zack]# netcfg npnwap
:: npnwap up  - Network unavailable                                      [FAIL] 
[root@boxxy zack]# netcfg npnwap
:: npnwap up  - Network unavailable                                      [FAIL] 
[root@boxxy zack]# netcfg2 npnwap
:: npnwap up  - Network unavailable                                      [FAIL] 
[root@boxxy zack]# netcfg npnwap
:: npnwap up  - Network unavailable                                      [FAIL] 
[root@boxxy zack]# killall wicd
wicd: no process killed
[root@boxxy zack]# /etc/rc.d/wicd stop
:: Stopping wicd Daemon                                                  [DONE] 
[root@boxxy zack]# killall dhcpcd
dhcpcd: no process killed
[root@boxxy zack]# killall dhclient
dhclient: no process killed
[root@boxxy zack]# netcfg npnwap
:: npnwap up  - Network unavailable                                      [FAIL] 
[root@boxxy zack]# netcfg2 npnwap
:: npnwap up  - Network unavailable                                      [FAIL] 
[root@boxxy zack]# nano /etc/network.d/npnwap 
[root@boxxy zack]# netcfg npnwap
:: npnwap up                                                             [DONE] 
[root@boxxy zack]# nano /etc/network.d/npnwap 
[root@boxxy zack]# /etc/rc.d/wicd stop
:: Stopping wicd Daemon                                                  [DONE] 
[root@boxxy zack]# netcfg npnwap
 > npnwap already connected 
[root@boxxy zack]#

Last edited by Sjoden (2008-07-07 21:36:17)

Sjoden · 2008-07-07 21:53:38

I just updated my whole system to testing, I don't like doing that. It was actually an accident. I did an -Syu, forgetting that I had it enabled to get the latest netcfg. It updated kernel headers and the 4965 firmware, among other things.

As of now, wicd and netcfg both work.

Wicd just works, and netcfg works with the following;

netcfg profilename

and the profile looks like;

CONNECTION="wireless"
DESCRIPTION="???'s extgernal wireless network."
INTERFACE=wlan0
QUIRKS=(prescan preessid)
SCAN="yes"
SECURITY="wep"
ESSID="???WAP"
KEY="1234567890"
IP="dhcp"

/edit

Not all is well. I have to try and connect twice now with wicd. Verified this twice, after a restart. Netcfg failed 3 times in a row. I haven't troubleshooted it more than that, although I know it does work sometimes. This is very frustrating. I'm going to grab a snack. I'm sorry If I sound rude. I don't mean any harm. Its just that I have had this problem for over a year, I reported it to bug tracker, I was told to do ifconfig wlan0 up, and it was closed. And of course, It still didn't work. The forums didn't help much then either. This time has been a more pleasant experience.

I do have to give a thumbs up to iphitus on netcfg. It is pretty nice and straight forward. The profile syntax is clean and easy to understand.

Last edited by Sjoden (2008-07-07 22:17:46)

iphitus · 2008-07-07 22:19:44

Cool Thanks a heap!

Last edited by iphitus (2008-07-07 22:19:58)

Sjoden · 2008-07-08 00:09:20

I just restarted. I wasn't able to connect with wicd. I tried netcfg, it failed the 1st two times saying it couldn't authenticate, then the 3rd time it connected and everything is fine...

Does anyone have any ideas?

/edit

I restarted again, and then I couldn't connect with netcfg, but after messing around with wicd I could. This is so rediculous.

Maybe it has to do with this being a WEP network. I'm going home in a few minutes. I'll connect to my WPA net after dinner....

Zack

Last edited by Sjoden (2008-07-08 00:54:28)

Sjoden · 2008-07-08 02:42:28

Just tried it, wicd connected first try. . I'm guessing it has something to do with either wep, but more likely the fact that there is 3 APs with the same name. I'll find out tomorrow.

iphitus · 2008-07-08 03:15:45

Given it's so patchy and unreliable, it's probably a driver issue.

If you want to specify with netcfg [testing], see this:
http://wiki.archlinux.org/index.php/Net … connecting

Last edited by iphitus (2008-07-08 03:15:58)

litemotiv · 2008-12-09 11:15:20

iphitus wrote:

Given it's so patchy and unreliable, it's probably a driver issue.
If you want to specify with netcfg [testing], see this:
http://wiki.archlinux.org/index.php/Net … connecting

not sure if this is also a 4965 driver problem, but i just noticed that on "cold connect" when netcfg (2.1.2-1) usually times out on the first run (with or without QUIRKS), the wrong essid is somehow caught.

for instance, this is right after boot:

wlan0     IEEE 802.11abgn  ESSID:"someoneElsesEssid"  
          Mode:Managed  Frequency:2.462 GHz  Access Point: Not-Associated   
          Tx-Power=15 dBm   
          Retry min limit:7   RTS thr:off   Fragment thr=2352 B   
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0

while my config says:

CONNECTION="wireless"
INTERFACE=wlan0
SCAN="yes"
SECURITY="wpa"
ESSID="myEssid"
KEY="myKey"
QUIRKS=(prescan preessid)
IP="dhcp"
TIMEOUT=30

dmesg, my essid = 00:19:CB:09:35:EE

iwlagn 0000:0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
iwlagn 0000:0c:00.0: restoring config space at offset 0x1 (was 0x100102, writing 0x100106)
firmware: requesting iwlwifi-4965-2.ucode
Registered led device: iwl-phy0:radio
Registered led device: iwl-phy0:assoc
Registered led device: iwl-phy0:RX
Registered led device: iwl-phy0:TX
Clocksource tsc unstable (delta = -352706298 ns)
wlan0: authenticate with AP 00:19:cb:09:35:ee
wlan0: authenticated
wlan0: associate with AP 00:19:cb:09:35:ee
wlan0: RX AssocResp from 00:19:cb:09:35:ee (capab=0x451 status=0 aid=2)
wlan0: associated
wlan0: deauthenticating by local choice (reason=3)
wlan0: authenticate with AP 00:0c:f6:33:e9:08
mac80211-phy0: failed to remove key (0, 00:19:cb:09:35:ee) from hardware (-22)
iwlagn 0000:0c:00.0: PCI INT A disabled
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
iwlagn 0000:0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
iwlagn 0000:0c:00.0: restoring config space at offset 0x1 (was 0x100102, writing 0x100106)
Registered led device: iwl-phy0:radio
Registered led device: iwl-phy0:assoc
Registered led device: iwl-phy0:RX
Registered led device: iwl-phy0:TX
wlan0: authenticate with AP 00:0c:f6:33:e9:08
ADDRCONF(NETDEV_UP): wlan0: link is not ready

//-> then i do a manual connect from console

wlan0: authenticate with AP 00:19:cb:09:35:ee
wlan0: authenticated
wlan0: associate with AP 00:19:cb:09:35:ee
wlan0: RX AssocResp from 00:19:cb:09:35:ee (capab=0x451 status=0 aid=2)
wlan0: associated
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

litemotiv · 2008-12-13 14:44:57

p.s., this is not solved with the latest intel driver update (228.57.2.23-1). doing a 2nd manual connect with netcfg always works though.

Arch Linux

#1 2008-07-02 22:05:10

Intel4965 | Association/DHCP | Status Issue

#2 2008-07-03 10:44:11

Re: Intel4965 | Association/DHCP | Status Issue

#3 2008-07-03 19:19:45

Re: Intel4965 | Association/DHCP | Status Issue

#4 2008-07-04 19:04:06

Re: Intel4965 | Association/DHCP | Status Issue

#5 2008-07-05 00:55:49

Re: Intel4965 | Association/DHCP | Status Issue

#6 2008-07-05 02:54:46

Re: Intel4965 | Association/DHCP | Status Issue

#7 2008-07-06 00:39:23

Re: Intel4965 | Association/DHCP | Status Issue

#8 2008-07-06 12:57:06

Re: Intel4965 | Association/DHCP | Status Issue

#9 2008-07-06 15:52:40

Re: Intel4965 | Association/DHCP | Status Issue

#10 2008-07-06 22:43:06

Re: Intel4965 | Association/DHCP | Status Issue

#11 2008-07-07 21:13:15

Re: Intel4965 | Association/DHCP | Status Issue

#12 2008-07-07 21:53:38

Re: Intel4965 | Association/DHCP | Status Issue

#13 2008-07-07 22:19:44

Re: Intel4965 | Association/DHCP | Status Issue

#14 2008-07-08 00:09:20

Re: Intel4965 | Association/DHCP | Status Issue

#15 2008-07-08 02:42:28

Re: Intel4965 | Association/DHCP | Status Issue

#16 2008-07-08 03:15:45

Re: Intel4965 | Association/DHCP | Status Issue

#17 2008-12-09 11:15:20

Re: Intel4965 | Association/DHCP | Status Issue

#18 2008-12-13 14:44:57

Re: Intel4965 | Association/DHCP | Status Issue

Board footer