ipw2100 - timesout/failure on DHCP request on boot

[Arul]

Since turning on WPA on my router, my ipw2100 based network interface, appears to be failing OR timing out on DHCP request. I had to manually restart networking to get it to work after boot. I have never had this issue before I switched to WPA on my home network. Anyone noticed the issue or have any solution?.

Here are details.
Version: Ubuntu 2.6.24-19.36-generic, Ubuntu 8.04.1

ifconfig after boot:
----------------------
eth1 Link encap:Ethernet HWaddr xxxxxxxxxxxxxxx
          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
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
          Interrupt:5 Base address:0xa000 Memory:fafee000-fafeefff

eth1:avahi Link encap:Ethernet HWaddr xxxxxxxxxxxxx
          inet addr:169.254.9.24 Bcast:169.254.255.255 Mask:255.255.0.0
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          Interrupt:5 Base address:0xa000 Memory:fafee000-fafeefff

Restart networking:
----------------------
xxx@panther:~$ sudo /etc/init.d/networking restart
 * Reconfiguring network interfaces... There is already a pid file /var/run/dhclient.eth1.pid with pid 5478
killed old client process, removed PID file
... <snip>
bound to 192.168.1.102 -- renewal in 930400594 seconds.

ifconfig after network restart:
----------------------------------
eth1 Link encap:Ethernet HWaddr xxxxxxxxxxxx
          inet addr:192.168.1.102 Bcast:192.168.1.255 Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:41 errors:1 dropped:1 overruns:0 frame:0
          TX packets:39 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:5721 (5.5 KB) TX bytes:3571 (3.4 KB)
          Interrupt:5 Memory:fafee000-fafeefff

[Arul (aselvan)]

Update: I figured out the reason... the wpa_supplicant is not ready/up at the time udev tries to activate the network on boot. The simple solution is to disabled the udev ACTION=add rule in /etc/udv/rules.d/85-ifupdown.rules and let the network manager activate the interface instead which works just fine.