linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Farina <sidhayn@gmail.com>
To: Tim Schneider <schneid5@cs.uni-bonn.de>,
	wireless <linux-wireless@vger.kernel.org>
Subject: Re: Reading the RSSI from a Kernel Module
Date: Mon, 13 Jul 2009 07:57:17 -0400	[thread overview]
Message-ID: <4A5B211D.3040905@gmail.com> (raw)
In-Reply-To: <2E605895-C629-47C5-8DF8-DF012A3749EB@cs.uni-bonn.de>

Tim Schneider wrote:
>
> Am 13.07.2009 um 08:59 schrieb Richard Farina:
>> I don't mean to make this a flame so please do not take it that way.  
>> How exactly do you expect to get the RECEIVED Signal Strength 
>> indication for a packet which you are SENDING? If you send it, you 
>> don't receive it...
>>
>> Just my 0.02
>>
>> -Rick Farina
>
> Hi Rick,
>
> as far, as I understood, the RSSI-Mechanism also displays the signal 
> strength of the just sent package. I figured there was some way the 
> MAC-Layer transported that information, but you're right, I could be 
> mistaken. Anyways, since I'm trying to implement a TCP Algorithm, i 
> definitely have a  two-way connection. Assuming, that the route back 
> is going to be the same as it was on the way there (which basically 
> should be true, based on the Routing algorithms we're using in our 
> wireless mesh network), I could just use the RSSI Value of the 
> received ACK.
>
Any RSSI on a sent packet will be a calculated number not an observed 
number and as such it will be completely pointless for any kind of rate 
control algorithm.  Assuming that the card could actually receive the 
packets it is sending (which it can't) then you would be observing a 
24dBm signal (for instance) with 0 patch loss and your RSSI would be at 
or above max.  Realistically you can assume that every packet you sent 
has a max RSSI on your end because you are the one transmitting it.  
Now, if you want to know what the RSSI on the receiver side is that is a 
completely different question, one which you cannot answer at all. When 
you send a packet you do not have the good fortune to know what RSSI the 
receiver got.  You can roughly assume based on your RSSI when you get an 
ACK, but honestly that isn't even close to correct because every packet 
has a very unique experience in the air and you cannot assume things 
like the same tx power and rx sensitivity will be the same on both 
ends.  There is some 802.11 protocol (the letter eludes me at present) 
which is in draft form which adds information to packets so that both 
ends know each other's RSSI, but I have never seen it implemented 
anywhere yet.

I advise you keep the discussion on list as I am by no means an expert 
and many people much better at this than I may respond.

-Rick Farina
> Regards,
>
> Tim Schneider
>
>


  parent reply	other threads:[~2009-07-13 11:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-13  6:32 Reading the RSSI from a Kernel Module Tim Schneider
2009-07-13  6:59 ` Richard Farina
     [not found]   ` <2E605895-C629-47C5-8DF8-DF012A3749EB@cs.uni-bonn.de>
2009-07-13 11:57     ` Richard Farina [this message]
2009-07-17  6:37       ` Tim Schneider

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A5B211D.3040905@gmail.com \
    --to=sidhayn@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=schneid5@cs.uni-bonn.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).