Wireless doesn't like my router anymore.(SOLVED)

[gemini91]

This problem has been going on for over a month, but it is getting worse.
When I bring up the machine, it insists on trying to connect to my
neighbors routers. Once I get it up I run
"/init.d/net.eth0 restart" and maybe after 6 or 7 times it will connect
to my router. Example follows

don don # /etc/init.d/net.eth0 restart
* Starting eth0
* Configuring wireless network for eth0
* WEP key is not set for "araku" - not connecting
Error for wireless request "Set Frequency" (8B04) :
SET failed on device eth0 ; Device or resource busy.
* eth0 connected to ESSID "Belkin_G_Plus_MIMO_785000" at 00:17:3F:B5:8D:88
* in managed mode on channel 1 (WEP disabled)
* Configuration not set for eth0 - assuming DHCP
* Bringing up eth0
* dhcp
* Running dhcpcd ... [ ok ]
* eth0 received address 192.168.2.2/24

don don # /etc/init.d/net.eth0 restart
* Stopping eth0
* Bringing down eth0
* Stopping dhcpcd on eth0 ... [ ok ]
* Shutting down eth0 ... [ ok ]
* Starting eth0
* Configuring wireless network for eth0
Error for wireless request "Set Frequency" (8B04) :
SET failed on device eth0 ; Device or resource busy.
* eth0 connected to ESSID "miloulan" at 00:06:25:F6:35:34
* in managed mode on channel 6 (WEP enabled - open)
* Configuration not set for eth0 - assuming DHCP
* Bringing up eth0
* dhcp
* Running dhcpcd ... [ ok ]
* eth0 received address 192.168.1.101/24

Here is my net file

# /etc/conf.d/net:
# Global wireless config file for net.* rc-scripts
modules=( "iwconfig" )
key_miloulan="e9e61d5f99 enc open"
preferred_aps=("miloulan")

Wireless tools is at wireless-tools-29_pre22, but has failed since at least pre10
LSPCI = 02:02.0 Network controller: Intersil Corporation Prism 2.5 Wavelan chipset (rev
DRIVER = orinoco_pci

The machine has 3 other systems on it. Windows 2000, an old Gentoo system, and Ununtu
Gutsty Gibbon All 3 connect with no problems.

[massimo]

Try setting the associate_order variable appropriately [1].

[1] http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=4&chap=4#doc_chap3
_________________
Hello 911? How are you?

[gemini91]

massimo, thanks very much. It appears that it needed

associate_order="forcepreferred"

It has booted twice and connected both times, hasn't done that in over a month.
Again, thanks very much. I will give it a few more times and then mark as Solved.