Okay, ipw2100 and ipw2200 stopped working after a recent update. I traced it back to baselayout-1.12.4-r6, I downgraded to -r5 and that didn't fix it, so I downgraded to -r2 and now it works. Somewhere in baselayout you seem to set the ap mac address and hold onto it like it is made of gold. Not sure why, but here are the symptoms. System boots. ipw2x00 connects to fix ap it sees set your ssid "iwconfig eth1 essid myssid" will not associate ifconfig shows eth1 is no longer "RUNNING" Please look into this. If someone can ask me for specific information I'm more than willing to help troubleshoot this, I just don't know what you need. -Rick Farina
Please set RC_VERBOSE="yes" in /etc/conf.d/rc and attach the output of it working and output of it failing. Also, please attach your /etc/conf.d/net.
I actually never start net.eth1 (or any other net.* besides lo), I just configure everything manually. I upgraded, then downgraded, and I left net.lo as the baselayout-1.12.4-r6 version but baselayout is actually 1.12.4-r2 and it works if I "iwconfig eth1 essid myssid" and "iwconfig eth1 ap any" Doing those two commands on -r6 still leaves the card on the original channel (6 in this case) and it does not scan. My /etc/conf.d/net only has a few config_intX( "null ") statements where intX is every interface on my system except lo, so the bug is not in my configuration.
if I remove the config_eth1( "null" ) and rm /etc/init.d/net.eth1 then everything works perfectly just as it always should. despite the fact that I don't use gentoo to start net.eth1, it seems to somehow start it anyway (rc-update show doesn't even show net.eth1) and even though I have config_eth1( "null" ) gentoo seems to deciede that it should control the device anyway. Removing anything telling gentoo that the device exists solves my problem in -r2 I upgrade to -r6 and my problem is still solved. This is, however, still an issue, as gentoo is doing something I didn't ask it to do. If you can tell me what to do, I'll be glad to help track it down. Also, I am not the only one who recently encounted this problem, the #ipw2100 chatroom on freenode also has a few other users with this issue. Thanks for your prompt response, I look forward to helping resolve this issue.
Created attachment 94755 [details, diff] Relase AP mac address on stop OK, what's happening is that our scripts are scanning and finding an unencrypted AP. We then connect to it. In baselayout-1.12 this includes forcing the channel/frequency and the AP MAC address to solve issues with other device drivers such as rt2x00 or any driver that uses the dscape stack. This patch to /lib/rcscripts/net/iwconfig.sh releases the AP MAC address when the interface is stopped.
fixed in 1.12.5
