Richard wrote:
> The RTS/CTS protocol in 802.11 handles the hidden transmitter problem.
> A network node wishing to send data through the central station (the
> access point) sends an RTS packet that contains the originating stations
> id, the acces point then replies with a CTS with the same id, other
> stations that did not hear the RTS will hear the CTS and thus know that
> the access point is busy.
Sounds good, I hadn't thought about that - sorry. At least it's good
if link turnaround times are small. But how will it know for how long
the receiver will be busy? Does it wait for that station to send
an ack or do the RTS and the CTS transmissions contain the length of
the data that is to be transmitted?
> There is a lot in 802.11 and as I am not actually directly interested
> currently in the local link I have not yet fully read the spec. I have
> only read the Harris application note that G8OTA put me on to.
Yes, all I found when I searched today was rather short summaries.
Is the original document available anywhere on the net or is it one
of the many standards that should never become a standard because the
information is not free?
> When idle the access point advertises that fact
> at intervals.
Ok, all this works for bidirectional communication, but what about
a low power station that receives another very well but is unable
to reply directly? Connected mode ax25 doesn't provide for this
either, but it's possible and it would be fun...
Kai
