On Tue, 2009-04-07 at 16:11 +0300, Maxim Levitsky wrote: > On Tue, 2009-04-07 at 12:25 +0300, Rami Rosen wrote: > > Hi, > > > Why iwl3945 still doesn't support AP mode? > > see also this patch, titled: "wlwifi: disable AP mode" > > > > http://www.spinics.net/lists/linux-wireless/msg24688.html > > > > Regards, > > Rami Rosen > > > Quoiting this patch: > > > > iwlwifi does not support AP mode in any way. For one, it doesn't even > > buffer multicast/broadcast frames properly. We didn't allow zd1211rw AP > > mode to be enabled without this, so iwlwifi shouldn't be allowed to > > advertise AP mode either. > This is interesting, this means it doesn't save frames when client is in power save mode? > IBSS doesn't have this? > > > > > > > > > > > It also doesn't work at all, it doesn't even answer to probe requests, > > I'm guessing the packet injection code was disabled again. > Packet injection (even fragmentation) works fine here. > Also, now hostapd responds to probes isn't it? > (I was said that now hostapd sends/recieves all managment frames) > > > > > > > > [ 471.524478] iwlagn: ERROR: APs don't scan > > > > this is a long-standing bug, of course APs scan to know their > > surroundings, not sure why this is there, it's also very pointless since > > I can remove it by enabling software scan... > Here, software scan fixes it, besides many device don't have hardware scan > > > > > > > > [ 487.507346] iwlagn: Microcode SW error detected. Restarting 0x2000000. > This probably was fixed now, there were many reports about microcode errors. > > > > > I just feel, that AP mode can be done, and it isn't that hard to enable it. > I am thinking, currently iwl3945 is ported to iwlagn. When porting is it could fix AP problems in it too? Best regards Maxim Levitsky -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
