in reply to Re^2: Module to return signal levels on captured packets
in thread Module to return signal levels on captured packets

Also, I've noted that TCPdump will report the signal value between myself and another client when sending echo requests to it. Actually, during the echo request I see the reply directly from the target and also from the AP that is acting as a hub in this instance. I did not think that iwconfig was able to provide signal levels between clients in this fashion. Is there a perl module that can read interface statistics such as TCPdump appears to be doing?

Any direction is greatly appreciated.
  • Comment on Re^3: Module to return signal levels on captured packets

Replies are listed 'Best First'.
Re^4: Module to return signal levels on captured packets
by Khen1950fx (Canon) on Jan 04, 2010 at 21:50 UTC
    If I understand your question correctly, then you want to try ifconfig and Net::Interface. For an example from the source:
    #!/usr/bin/perl use strict; use warnings; use Net::Interface; my @all = Net::Interface->interfaces(); print $all[0]->name,"\n"; my @allnames = "@all"; print @allnames,"\n";

      I apologize for not making myself more clear...While performing frame capture on tcpdump it returns the signal level that each frame was intercepted at. So, if I ping a host on my LAN, tcpdump receives two frames per ping sent. One directly from the pinged host, and the other from the AP which has rebroadcast the ping since it is acting as a wireless hub. The measurement from the AP is different from that of the host since the host is much closer. So, somehow, tcpdump is able to read the signal levels of frames intercepted by other hosts on my LAN, not just the signal level to my AP. Ifconfig and Net::Interface do not seem to grant me access to those frame by frame stats. I would like to use perl to collect the signal levels of other hosts on my LAN in a similar manner to how tcpdump does it.


      Thanks

        porpoise_paul:

        I'm sorry I can't help. But while reading the thread, I thought that it might be helpful if you showed some sample output, and indicate what parts of the output you're specifically interested in. That way, it might clear up some misunderstandings and help you get to the answer more quickly. For example, it took a couple exchanges to find out that there were multiple packets involved, and that the AP is (apparently) reporting the signal level in a separate packet. But we still don't know how other devices are reporting the signal level.

        ...roboticus

        Never attribute to malice that which can be explained by incompetence.