JoaoBR wrote:
> when running a wi device in AP mode all connected clients ar showing up with
> 1
> Mbit/s connection but are connected with 11Mbit
>
> Is this a bug?
>
> João
>
>
> ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS ERP
> 00:40:f4:c5:13:b2 4 1 1M 46 150 155 37104 EP 0
> 00:e0:7d:c8:c9:89 5 1 1M 57 150 240 4240 EPB 0
> 00:0e:2e:75:f3:7a 6 1 1M 51 165 137 4624 EP 0
> 00:40:f4:c3:c9:48 8 1 1M 49 150 140 62176 EP 0
>
>
> wi0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
> ether 00:02:6f:37:4e:46
> media: IEEE 802.11 Wireless Ethernet DS/11Mbps mode 11b <hostap>
> (DS/2Mbps <hostap>)
> status: associated
> ssid frutalnet_1 channel 1 (2412) bssid 00:02:6f:37:4e:46
> stationname AP1
> authmode OPEN privacy MIXED deftxkey 1
> wepkey 1:40-bit
> wepkey 2:40-bit
> wepkey 3:40-bit
> wepkey 4:40-bit powersavemode OFF powersavesleep 100 txpowmax 100
> rtsthreshold 2347 mcastrate 1 fragthreshold 2346 -pureg protmode CTS
> -wme -burst ssid HIDE -apbridge dtimperiod 1 bintval 100
> bridge0: flags=8043<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
> ether ac:de:48:db:e2:15
> priority 32768 hellotime 2 fwddelay 15 maxage 20
> member: wi0 flags=7<LEARNING,DISCOVER,STP>
> port 3 priority 128 path cost 55 forwarding
> member: re0 flags=3<LEARNING,DISCOVER>
If I recall correctly the wi driver leaves rate control decisions to the
firmware and has no way of knowing what the current tx rate is for each
client.
There have been patches floating around for a while to do tx rate
control in the driver instead (in which case this info would be
available) but they were never committed because of reported bugs. It
might be time to just commit the code anyway (to HEAD) in order to force
the bug(s) to be resolved.
Sam
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
