Ipw2200 / dhcp

Question

Hello Arch-Community.
I today tried out Arch Linux, and wow, i have to say i was quite impressed. Easy to install, easy to use - till now. Well, it still is.
It is the first distribution where i got the ipw driver working "out of the box". Thumbs up for this ...
Anyway, there is one problem left:
If i receive the IP-Address of my WLAN with DHCP, starting the network and the interface during bootup, i have the following problem:
- The Network goes up (i'm using AcerHK to activate the sw-radio switch).
- I get an IP-Address
- I can ping, i can surf
- Just for some secs / about a minute. After this, my wireless network disappears of "ifconfig", well, as if it never received an Address.wlan_eth1=lly, the interface has already been working.
If i boot up normally, activating the drivers (acerhk, ipw), and getting the IP manually with DHCP, it works very fine.
What could this be? I'm using 0.7 (current).
Following additional information:
- AcerHK as sw-switch
- ipw2200 (Intel Centrino 2200BG)
- arch 0.7 (current)
the /etc/conf.d/wireless
wlan_eth1="eth1 mode managed essid LocalGNet"
WLAN_INTERFACES=(eth1)
I added the following information to /etc/rc.conf
eth1="dhcp"
INTERFACES=(lo eth1)
Of course, i made a script loading AcerHK on boot
#!/bin/bash
. /etc/rc.conf
. /etc/rc.d/functions
case "$1" in
start)
stat_busy "Starting AcerHK driver"
if [ ! -f /proc/driver/acerhk/wirelessled ]; then
modprobe acerhk
else
echo "AcerHK driver seems to be already running"
fi
if [ -f /proc/driver/acerhk/wirelessled ]; then
echo 1 > /proc/driver/acerhk/wirelessled
stat_done
else
stat_fail
fi
stop)
stat_busy "Stopping AcerHK driver"
if [ -f /proc/driver/acerhk/wirelessled ]; then
echo 0 > /proc/driver/acerhk/wirelessled
rmmod acerhk
stat_done
else
echo "AcerHK driver seems not to be running"
stat_fail
fi
restart)
$0 stop
sleep 1
$0 start
echo "usage: $0 {start|stop|restart}"
esac
exit 0
Any idea what could cause this? Any suggestions?
STiAT

Answer 1

Okay, i gave it a shot right now, since i arrived at home.
Compiled 0.19, put the new firmware in the right place.
Still the same.
I think there's nothing wrong with it at all...
The behaviour is like when he wouldn't receive the IP via DHCP, it also drops the interface back to inactive. As if there is no status returend by the dhcpcd at startup time to ifconfig... and so ifconfig drops the interface within 30 secs (dhcp timeout?). i dont know anything of the internals of Arch (yet), since i'm very new to the distribution.
STiAT