[Prism54-users] setBeaconPeriod doesn't work

[Jeff Bobzin]

Tim,

I agree that setBeaconPeriod does not seem to affect getBeaconPeriod. =
The 100 value indicates a 100 millisecond interval. This is standard =
rate (10 per second).

But this has nothing to do with the 10 second period packet losses.=20

My research indicates this loss is a 'feature' of Intersil AP firmware.  =
I have been able to detect the 10 second losses on a production AP from =
SMC (but briefer)

See my post on 11/21 entitled "Field report - performance at a distance" =
for links. Published data confirms the losses.

It certainly is a problem for performance. If it blocked the packets =
that would be OK. But it throws them away.=20


---Jeff

 -----Original Message-----
From: 	Tim Dijkstra [mailto:newsuser@famdijkstra.org]=20
Sent:	Wednesday, November 26, 2003 3:30 PM
To:	prism54-users@prism54.org
Subject:	[Prism54-users] setBeaconPeriod doesn't work

Hi,

It seems the ioctl setBeaconPeriod doesn't do anything, well if I use
it to change the period and then getBeaconPeriod it keeps saying 100. I
must confess I do not really know what I'm doing ;) I was trying to
figure out if this number would have any influence on the period packet
loss I'm seeing (every aprox 10s all packets from client to AP get
lost).

grts Tim

Ps. If anybody has a nice link where a can learn more about wireless,
802.11g, etc; that would be nice.
_______________________________________________
Prism54-users mailing list
Prism54-users@prism54.org
http://prism54.org/mailman/listinfo/prism54-users