Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

wifi-radar(1) [debian man page]

wifi-radar(1)						      General Commands Manual						     wifi-radar(1)

NAME

       WiFi Radar - utility for managing WiFi profiles

SYNOPSIS

       wifi-radar [OPTION]...

DESCRIPTION

       WiFi Radar is a PyGTK2 utility for managing WiFi profiles.

       It will look for the config file in /etc/wifi-radar/wifi-radar.conf.  You can change that in wifi-radar.

       If the configuration file does not exist, it will create it, so you must always run it within a correctly permitted account (as root or use
       sudo or pam).

       Recent versions partially implement WPA-TKIP with wpa_supplicant. You need a running wpa_supplicant installation  with  a  /etc/wpa_suppli-
       cant/wpa_supplicant.conf  file.	 Then by setting in your /etc/wifi-radar/wifi-radar.conf file the "use_wpa = yes" option and "wpa_driver =
       ipw" for example, wpa_supplicant will be launched when you connect using this profile.

       But currently you can't set your wpa_supplicant options like the psk, proto, key_mgmt etc. using wifi-radar.  Your wpa_supplicant  configu-
       ration  file  should  be set and tested already. If you have different networks set in wpa_supplicant.conf, then you can switch using wifi-
       radar.

       The wifi-radar script accepts the following command-line options:

OPTIONS

       -v, --version for printing the version.

FILES

       /etc/wifi-radar/wifi-radar.conf
	       See for more information.

BUGS

       Probably lots!

       Because of repeated scanning, WiFi Radar is very power consuming.

       Please report bugs to the mailing list <https://lists.anl.gov/mailman/listinfo/wifi-radar>

MORE INFORMATION

       The GIT repository is available at https://git.berlios.de/cgi-bin/gitweb.cgi?p=wifi-radar;a=summary

       If you have questions, visit http://wifi-radar.berlios.de

AUTHOR

       This Python program was originally written by Ahmad Baitaimal <ahmad@bitbuilder.com>.  It has been maintained at  various  times  by  Brian
       Elliott Finley <brian@thefinleys.com> and Sean Robinson <seankrobinson@gmail.com>.  Contributions have been provided by:

       o   Douglas Breault <genkreton@comcast.net>

       o   Nicolas Brouard <nicolas.brouard@libertysurf.fr>

       o   Gary Case <gcase@redhat.com>

       o   Jon Collette <jonc@etelos.com>

       o   David Decotigny <com.d2@free.fr>

       o   Simon Gerber <gesimu@gmail.com>

       o   Joey Hurst <jhurst@lucubrate.org>

       o   Ante Karamatic <ivoks@ubuntu.com>

       o   Richard Monk <rmonk@redhat.com>

       o   Kevin Otte <kotte@redhat.com>

       o   Nathanael Rebsch <nathanael@dihedral.de>

       o   Andrea Scarpino <andrea@archlinux.org>

       o   Patrick Winnertz <winnie@debian.org>

SEE ALSO

       wifi-radar.conf(5) wpa_supplicant(8)

WiFi Radar 2.0							     July 2009							     wifi-radar(1)

Check Out this Related Man Page

netlog(1)						    BSD General Commands Manual 						 netlog(1)

NAME

     netlog -- Log summary of every UDP and TCP socket when the socket is closed.

SYNOPSIS

     netlog [-v] [-i interval] [-I iterations] [-t type] [-p process-name|pid] [-c] [-z]

DESCRIPTION

     The netlog program logs a summary for each TCP and UDP socket when the socket is closed. A header is printed once. The row items are sepa-
     rated by spaces.  Address to hostname lookups are not performed. Sockets that do not send or receive any data are not listed unless the -z
     option is specified.

OPTIONS

     A list of flags and their descriptions:

     -v       Verbose output

     -i interval
	      Report socket statistics periodically

     -I iterations
	      Used in combination with -i, will make netlog exit after the specified number of iterations.

     -t type  Specify the type of interface. By default, all interfaces will be monitored.  Multiple interface types may be specified.	The fol-
	      lowing types are supported:

	      wifi     WiFi interfaces

	      wired    Wired interfaces

	      loopback
		       Loopback interfaces

	      awdl     Apple Wireless Direct Link interfaces

	      expensive
		       Interfaces marked as "expensive", for example via hotspot

	      undefined
		       Cases where the underlying socket is not associated with an interface

	      external
		       The combination of all defined non-loopback interfaces.

     -p process-name|pid
	      Select a process for display.  A numeric argument identifies a process by its pid.  Alternatively a process name may be given, in
	      which case all processes with that name will be displayed.  The name must be an exact match for the name displayed by netlog, which
	      may require that the name be truncated, for example launchd.develop instead of launchd.development.  This option may be repeated to
	      select multiple processes.

     -c       Print details in comma-separated values (CSV) form.

     -z       Print details even if there was no data transfer on the socket

Darwin								   May 31, 2019 							    Darwin
Man Page