I can confirm this bug for Feisty using ipw2100 in a wpa_roam setup. No network management software involved, just a hand-edited /etc/network/interfaces like so:
auto lo
iface lo inet loopback
allow-hotplug eth0
iface eth0 inet dhcp
auto eth1
iface eth1 inet manual
wpa-driver wext
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
iface default inet dhcp
ifup "thinks" eth1 is up after booting (the kernel interface actually is up), but wpa_supplicant and wpa_cli aren't running. I have to ifdown and ifup eth1 after each boot to connect.
I can confirm this bug for Feisty using ipw2100 in a wpa_roam setup. No network management software involved, just a hand-edited /etc/network/ interfaces like so:
auto lo
iface lo inet loopback
allow-hotplug eth0
iface eth0 inet dhcp
auto eth1 supplicant/ wpa_supplicant. conf
iface eth1 inet manual
wpa-driver wext
wpa-roam /etc/wpa_
iface default inet dhcp
ifup "thinks" eth1 is up after booting (the kernel interface actually is up), but wpa_supplicant and wpa_cli aren't running. I have to ifdown and ifup eth1 after each boot to connect.