dhclient conflict between /sbin/devd and /etc/rc.d/netif ?

[Robert Jenssen]

Hi,
Every so often I have trouble connecting rt2560 based PCI wireless network 
card to my wireless router/access point. Typically I get:

# sudo /etc/rc.d/netif restart ral0
Starting wpa_supplicant.
ral0: no link .............. giving up
ral0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether 00:11:50:63:cd:47
        media: IEEE 802.11 Wireless Ethernet autoselect (DS/1Mbps)
        status: no carrier

Even though there seems to be plenty of signal power:

# sudo ifconfig ral0 list scan
SSID            BSSID              CHAN RATE   S:N     INT CAPS
xxxxxxx...      00:xx:xx:xx:xx:xx   10   54M -74:-95  100 EPS  WPA

Recently I noticed that sometimes, after the above "netif restart" fails, the 
ral0 interface "automagically" comes up anyway. Then dhclient is owned 
by /sbin/devd. The default devd.conf starts dhclient for both ethernet and 
PCI-cardbus devices. Is it a good idea for both /sbin/devd 
and /etc/rc.d/netif to start a dhclient on ral0 at about the same time? 
Should I disable dhclient in /etc/devd.conf?

Regards,

Rob Jenssen
 
PS:

"uname -a" shows:
FreeBSD 7.0-PRERELEASE #1: Fri Feb  8 14:36:49 EST 2008

dmesg.today shows:
ral0: <Ralink Technology RT2560> mem 0xf2004000-0xf2005fff irq 22 at device 
6.0 on pci2
ral0: MAC/BBP RT2560 (rev 0x04), RF RT2525
ral0: Ethernet address: 00:11:50:63:cd:47
ral0: [ITHREAD]