Dan Williams wrote:
Could be because your wifi adapter is a recent one, and thus uses the
preferred upstream nl80211 kernel configuration API.
It's an Intel PRO/Wireless 2200bg, so not exactly recent.
In addition, the wext api of operation 1, then operation 2, then
operation 3 simply doesn't
On Tue, 2012-11-06 at 23:16 +0100, Björn Persson wrote:
Dan Williams wrote:
On Tue, 2012-11-06 at 21:47 +0100, Björn Persson wrote:
I have a Wifi card that is supposed to be managed by the network
service. The interface's IP addresses, prefixes, routes and all that
get assigned
I have a Wifi card that is supposed to be managed by the network
service. The interface's IP addresses, prefixes, routes and all that get
assigned correctly on boot, but the wireless parameters – mode, ESSID
and channel – do not get assigned. I have to set those manually with the
iwconfig
On Tue, 2012-11-06 at 21:47 +0100, Björn Persson wrote:
I have a Wifi card that is supposed to be managed by the network
service. The interface's IP addresses, prefixes, routes and all that get
assigned correctly on boot, but the wireless parameters – mode, ESSID
and channel – do not get
Dan Williams wrote:
On Tue, 2012-11-06 at 21:47 +0100, Björn Persson wrote:
I have a Wifi card that is supposed to be managed by the network
service. The interface's IP addresses, prefixes, routes and all that
get assigned correctly on boot, but the wireless parameters – mode,
ESSID and
