On Friday 10 April 2009 00:28:48 Francesco Gringoli wrote:
> You mean that it misses to transmit some frames? Do you have  
> hypotheses on why AP mode should complete change the behavior of the  
> board from "good enough" to "not working correctly"?

Practice shows this. It's as simple as that.
Try it, if you don't trust me.

> >
> > Of course, there always are exceptions to these rules, because there  
> > are about
> > a million completely different 4318 and and 4306 cards out there.
> > So you might be lucky to pick one of the few 4318 that works well in  
> > AP mode, or
> > you might pick one of the few 4306 that don't work too well.
> Ok, that could be. I have only 4318 branded as Asus, they are all  
> equal. Probably the fact the linksys does not work in AP mode confirm  
> what you say.

I mostly use linksys products for testing.
But I think I could give the asus card a try, if you say it works better in AP 
mode.

> I have noticed, however a strange fact with these 4318 based linksys:  
> when I set one of them in AP mode, beaconing is perfect and I can join  
> it from other stations. When I ping the AP from stations I get echo  
> reply. If, instead, I ping stations from the AP, no packet is sent! at  
> all; if I telnet from stations to the AP, e.g., to port 22, 3whs ends  
> but then the TCP session dies. The strange fact is that it seems that  
> there are problems for all the frames whose generation involves a  
> contest switching from userspace to kernel, in other words a complete  
> cross of the mac80211+b43 layers. If instead, on the AP, I completely  
> bypass the network stack and directly ask b43 to transmit a frame  
> (with a modified b43) the frame is transmitted, at every rate I choose  
> (I choose the rate inside the kernel code, I'm not referring to the  
> rate set by iwconfig).
> 
> Do you have some of these flawed 4318?

I don't think the type of device influences whether packets are dropped
inside of some random kernel subsystem.

-- 
Greetings, Michael.
_______________________________________________
Bcm43xx-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Reply via email to