trackerjacker
=============
Like nmap for mapping wifi networks you’re not connected to. Maps and
tracks wifi networks and devices through raw 802.11 monitoring.
PyPI page: https://pypi.python.org/pypi/trackerjacker
Install
^^^^^^^
::
pip3 install trackerjacker
*Supported platforms*: Linux (tested on Ubuntu, Kali, and RPi) and macOS
(pre-alpha)
.. figure:: https://i.imgur.com/I5NH5KM.jpg
:alt: visual description
visual description
trackerjacker can help with the following:
- I want to know all the nearby wifi networks **and know all the
devices connected to each network.**
- I want to know who’s hogging all the bandwidth.
- I want to run a command when this MAC address sends more than 100000
bytes in a 30 second window (maybe to determine when an IP camera is
uploading a video, which is indicative that it just saw motion).
- I want to deauth anyone who uses more than 100000 bytes in a 10
second window.
- I want to deauth every Dropcam in the area so my Airbnb hosts don’t
spy on me.
- I want to be alerted when any MAC address is seen at a power level
greater than -40dBm that I’ve never seen before.
- I want to see when this particular person is nearby (based on the MAC
of their mobile phone) and run a command to alert me.
- I want to write my own plugin to run some script to do something fun
every time a new Apple device shows up nearby.
Usage
-----
Find detailed usage like this:
::
trackerjacker -h
There are 2 major usage modes for ``trackerjacker``: **map** mode and
**track** mode:
Map mode example
~~~~~~~~~~~~~~~~
Map command:
::
trackerjacker -i wlan1337 --map
By default, this outputs the ``wifi_map.yaml`` YAML file, which is a map
of all the nearby WiFi networks and all of their users. Here’s an
example ``wifi_map.yaml`` file:
::
TEST_SSID:
00:10:18:6b:7a:ea:
bssid: 00:10:18:6b:7a:ea
bytes: 5430
channels:
- 11
devices:
3c:07:71:15:f1:48:
bytes: 798
signal: 1
vendor: Sony Corporation
78:31:c1:7f:25:43:
bytes: 4632
signal: -52
vendor: Apple, Inc.
signal: -86
ssid: TEST_SSID
vendor: Broadcom
BRANSONS_WIFI:
90:48:9a:e3:58:25:
bssid: 90:48:9a:e3:58:25
bytes: 5073
channels:
- 1
devices:
01:00:5e:96:e1:89:
bytes: 476
signal: -62
vendor: ''
30:8c:fb:66:23:91:
bytes: 278
signal: -46
vendor: Dropcam
34:23:ba:1c:ba:e7:
bytes: 548
signal: 4
vendor: SAMSUNG ELECTRO-MECHANICS(THAILAND)
signal: -80
ssid: BRANSONS_WIFI
vendor: Hon Hai Precision Ind. Co.,Ltd.
hacker_network:
80:2a:a8:e5:de:92:
bssid: 80:2a:a8:e5:de:92
bytes: 5895
channels:
- 11
devices:
80:1f:02:e6:44:96:
bytes: 960
signal: -46
vendor: Edimax Technology Co. Ltd.
80:2a:a8:8a:ec:c8:
bytes: 472
signal: 4
vendor: Ubiquiti Networks Inc.
80:2a:a8:be:09:a9:
bytes: 5199
signal: 4
vendor: Ubiquiti Networks Inc.
d8:49:2f:7a:f0:8f:
bytes: 548
signal: 4
vendor: CANON INC.
signal: -46
ssid: hacker
vendor: Ubiquiti Networks Inc.
80:2a:a8:61:aa:2f:
bssid: 80:2a:a8:61:aa:2f
bytes: 5629
channels:
- 44
- 48
devices:
78:88:6d:4e:e2:c9:
bytes: 948
signal: -52
vendor: ''
e4:8b:7f:d4:cb:25:
bytes: 986
signal: -48
vendor: Apple, Inc.
signal: -48
ssid: null
vendor: Ubiquiti Networks Inc.
82:2a:a8:51:32:25:
bssid: 82:2a:a8:51:32:25
bytes: 3902
channels:
- 48
devices:
b8:e8:56:f5:a0:70:
bytes: 1188
signal: -34
vendor: Apple, Inc.
signal: -14
ssid: hacker
vendor: ''
82:2a:a8:fc:33:b6:
bssid: 82:2a:a8:fc:33:b6
bytes: 7805
channels:
- 10
- 11
- 12
devices:
78:31:c1:7f:25:43:
bytes: 4632
signal: -52
vendor: Apple, Inc.
7c:dd:90:fe:b4:87:
bytes: 423223
signal: 4
vendor: Shenzhen Ogemray Technology Co., Ltd.
80:2a:a8:be:09:a9:
bytes: 5199
signal: 4
vendor: Ubiquiti Networks Inc.
signal: -62
ssid: null
vendor: ''
Note that, since this is YAML, you can easily use it as an input for
other scripts of your own devising. I have an example script to parse
this “YAML DB” here:
`parse_trackerjacker_wifi_map.py <https://gist.github.com/calebmadrigal/fdb8855a6d05c87bbb0254a1424ee582>`__.
Example: Track mode with trigger command
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Track mode allows you to specify some number of MAC addresses to watch,
and if any specific devices exceeds the threshold (in bytes), specified
here with the ``--threshold 4000`` (specifying an alert threshold of
4000 bytes) an alert will be triggered.
::
trackerjacker --track -m 3c:2e:ff:31:32:59 --threshold 4000 --trigger-command "./alert.sh" --channels-to-monitor 10,11,12,44
Using monitor mode interface: wlan1337
Monitoring channels: {10, 11, 12, 44}
[@] Device (3c:2e:ff:31:32:59) threshold hit: 4734
[@] Device (3c:2e:ff:31:32:59) threshold hit: 7717
[@] Device (3c:2e:ff:31:32:59) threshold hit: 7124
[@] Device (3c:2e:ff:31:32:59) threshold hit: 8258
[@] Device (3c:2e:ff:31:32:59) threshold hit: 8922
In this particular example, I was watching a security camera to
determine when it was uploading a video (indicating motion was detected)
so that I could turn on my security system sirens (which was the
original genesis of this project).
Example: Track mode with foxhunt plugin
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
::
trackerjacker -i wlan1337 --track --trigger-plugin foxhunt
Displays a curses screen like this:
::
POWER DEVICE ID VENDOR
======= ================= ================================
-82dBm 1c:1b:68:35:c6:5d ARRIS Group, Inc.
-84dBm fc:3f:db:ed:e9:8e Hewlett Packard
-84dBm dc:0b:34:7a:11:63 LG Electronics (Mobile Communications)
-84dBm 94:62:69:af:c3:64 ARRIS Group, Inc.
-84dBm 90:48:9a:34:15:65 Hon Hai Precision Ind. Co.,Ltd.
-84dBm 64:00:6a:07:48:13 Dell Inc.
-84dBm 00:30:44:38:76:c8 CradlePoint, Inc
-86dBm 44:1c:a8:fc:c0:53 Hon Hai Precision Ind. Co.,Ltd.
-86dBm 18:16:c9:c0:3b:75 Samsung Electronics Co.,Ltd
-86dBm 01:80:c2:62:9e:36
-86dBm 01:00:5e:11:90:47
-86dBm 00:24:a1:97:68:83 ARRIS Group, Inc.
-88dBm f8:2c:18:f8:f3:aa 2Wire Inc
-88dBm 84:a1:d1:a6:34:08
- Note that ``foxhunt`` is a builtin plugin, but you can define your
own plugins using the same Plugin API.
Example: Track mode with trigger plugin
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
::
$ trackerjacker --track -m 3c:2e:ff:31:32:59 --threshold 10 --trigger-plugin examples/plugin_example1.py --channels-to-monitor 10,11,12,44 --trigger-cooldown 1
Using monitor mode interface: wlan1337
Monitoring channels: {10, 11, 12, 44}
[@] Device (device 3c:2e:ff:31:32:59) threshold hit: 34 bytes
3c:2e:ff:31:32:59 seen at: [1521926768.756529]
[@] Device (device 3c:2e:ff:31:32:59) threshold hit: 11880 bytes
3c:2e:ff:31:32:59 seen at: [1521926768.756529, 1521926769.758929]
[@] Device (device 3c:2e:ff:31:32:59) threshold hit: 18564 bytes
3c:2e:ff:31:32:59 seen at: [1521926768.756529, 1521926769.758929, 1521926770.7622838]
This runs ``examples/plugin_example1.py`` every time
``3c:2e:ff:31:32:59`` is seen sending/receiving 10 bytes or more.
trackerjacker plugins are simply python files that contain either: \*
``Trigger`` class which defines a ``__call__(**kwargs)`` method
(example: ``examples/plugin_example1.py``) \* ``trigger(**kwargs)``
function (example: ``examples/plugin_example2.py``)
And optionally a ``__apiversion__ = 1`` line (for future backward
compatibility)
Example: Configuring with config file
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
::
trackerjacker.py -c my_config.json
And here’s the example config file called ``my_config.json``:
::
{
"iface": "wlan1337",
"devices_to_watch": {"5f:cb:53:1c:8a:2c": 1000, "32:44:1b:d7:a1:5b": 2000},
"aps_to_watch": {"c6:23:ef:33:cc:a2": 500},
"threshold_window": 10,
"channels_to_monitor": [1, 6, 11, 52],
"channel_switch_scheme": "round_robin"
}
A few notes about this:
- ``threshold_bytes`` is the default threshold of bytes which, if seen,
a causes the alert function to be called
- ``threshold_window`` is the time window in which the
``threshold_bytes`` is analyzed.
- ``devices_to_watch`` is a list which can contain either strings
(representing MACs) or dicts (which allow the specification of a
``name`` and ``threshold``)
- ``name`` is simply what a label you want to be printed when this
device is seen.
- ``threshold`` in the “Security camera” is how many bytes must be
seen
- ``channels_to_monitor`` - list of 802.11 wifi channels to monitor.
The list of channels your wifi card supports is printed when
trackerjacker starts up. By default, all supported channels are
monitored.
- ``channel_switch_scheme`` - either ``default``, ``round_robin``, or
``traffic_based``. ``traffic_based`` determines the channels of most
traffic, and probabilistically monitors them more.
Example: Enable/Disable monitor mode on interface
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Trackerjacker comes with a few other utility functions relevant to WiFi
hacking. One of these is the ability to turn on monitor mode on a
specific interface.
Enable monitor mode:
::
trackerjacker --monitor-mode-on -i wlan0
Disable monitor mode:
::
trackerjacker --monitor-mode-off -i wlan0mon
Note that trackerjacker will automatically enable/disable monitor mode
if necessary. This functionality is just useful if you want to enable
monitor mode on an interface for use with other applications (or for
quicker starup of trackerjacker, if you plan to be starting/exiting to
test stuff).
Example: Set adapter channel
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
::
trackerjacker --set-channel 11 -i wlan0
Note that trackerjacker will automatically switch channels as necessary
during normal map/track actions. This option is just useful if you want
to set the channel on an interface for use with other applications.
Recommended hardware
--------------------
- Panda PAU07 N600 Dual Band (nice, small, 2.4GHz and 5GHz)
- Panda PAU09 N600 Dual Band (higher power, 2.4GHz and 5GHz)
- Alfa AWUS052NH Dual-Band 2x 5dBi (high power, 2.4GHz and 5GHz, large,
ugly)
- TP-Link N150 (works well, but not dual band)
Roadmap
-------
- ☒ Hosted in PyPI
- ☒ Radio signal strength for APs
- ☒ Radio signal strength for individual macs
- ☒ Build map by data exchanged (exclude beacons)
- ☒ Packet count by AP
- ☒ Packet count by MAC
- ☒ Easier way to input per-device tracking thresholds
- ☒ Plugin system
- ☒ Fox hunt mode
- ☒ Tracking by SSID (and not just BSSID)
- ☒ Basic macOS (OS X) support (pre-alpha)
- ☐ macOS support: get signal strength values correct (will be fixed in
https://github.com/secdev/scapy/pull/1381
- ☐ macOS support: reverse airport binary to determine how to set true
monitor mode
- ☐ macOS support: diverse interface support (not just ``en0``)
- ☐ macOS support: get interface supported channels
- ☐ Mapping a specific SSID
- ☐ Performance enhancement: not shelling out for channel switching
- ☐ “Jack” mode - deauth attacks
Raw data
{
"_id": null,
"home_page": "https://github.com/calebmadrigal/trackerjacker",
"name": "trackerjacker",
"maintainer": "",
"docs_url": null,
"requires_python": "",
"maintainer_email": "",
"keywords": "hacking,network,wireless,packets,scapy",
"author": "Caleb Madrigal",
"author_email": "caleb.madrigal@gmail.com",
"download_url": "https://files.pythonhosted.org/packages/a5/85/cd04b4bce2e8f334f8aa560a32a40af17bb1bc03810553668f2b2e26fd66/trackerjacker-2.0.5.tar.gz",
"platform": null,
"description": "trackerjacker\n=============\n\nLike nmap for mapping wifi networks you\u2019re not connected to. Maps and\ntracks wifi networks and devices through raw 802.11 monitoring.\n\nPyPI page: https://pypi.python.org/pypi/trackerjacker\n\nInstall\n^^^^^^^\n\n::\n\n pip3 install trackerjacker\n\n*Supported platforms*: Linux (tested on Ubuntu, Kali, and RPi) and macOS\n(pre-alpha)\n\n.. figure:: https://i.imgur.com/I5NH5KM.jpg\n :alt: visual description\n\n visual description\n\ntrackerjacker can help with the following:\n\n- I want to know all the nearby wifi networks **and know all the\n devices connected to each network.**\n- I want to know who\u2019s hogging all the bandwidth.\n- I want to run a command when this MAC address sends more than 100000\n bytes in a 30 second window (maybe to determine when an IP camera is\n uploading a video, which is indicative that it just saw motion).\n- I want to deauth anyone who uses more than 100000 bytes in a 10\n second window.\n- I want to deauth every Dropcam in the area so my Airbnb hosts don\u2019t\n spy on me.\n- I want to be alerted when any MAC address is seen at a power level\n greater than -40dBm that I\u2019ve never seen before.\n- I want to see when this particular person is nearby (based on the MAC\n of their mobile phone) and run a command to alert me.\n- I want to write my own plugin to run some script to do something fun\n every time a new Apple device shows up nearby.\n\nUsage\n-----\n\nFind detailed usage like this:\n\n::\n\n trackerjacker -h\n\nThere are 2 major usage modes for ``trackerjacker``: **map** mode and\n**track** mode:\n\nMap mode example\n~~~~~~~~~~~~~~~~\n\nMap command:\n\n::\n\n trackerjacker -i wlan1337 --map\n\nBy default, this outputs the ``wifi_map.yaml`` YAML file, which is a map\nof all the nearby WiFi networks and all of their users. Here\u2019s an\nexample ``wifi_map.yaml`` file:\n\n::\n\n TEST_SSID:\n 00:10:18:6b:7a:ea:\n bssid: 00:10:18:6b:7a:ea\n bytes: 5430\n channels:\n - 11\n devices:\n 3c:07:71:15:f1:48:\n bytes: 798\n signal: 1\n vendor: Sony Corporation\n 78:31:c1:7f:25:43:\n bytes: 4632\n signal: -52\n vendor: Apple, Inc.\n signal: -86\n ssid: TEST_SSID\n vendor: Broadcom\n\n BRANSONS_WIFI:\n 90:48:9a:e3:58:25:\n bssid: 90:48:9a:e3:58:25\n bytes: 5073\n channels:\n - 1\n devices:\n 01:00:5e:96:e1:89:\n bytes: 476\n signal: -62\n vendor: ''\n 30:8c:fb:66:23:91:\n bytes: 278\n signal: -46\n vendor: Dropcam\n 34:23:ba:1c:ba:e7:\n bytes: 548\n signal: 4\n vendor: SAMSUNG ELECTRO-MECHANICS(THAILAND)\n signal: -80\n ssid: BRANSONS_WIFI\n vendor: Hon Hai Precision Ind. Co.,Ltd.\n\n hacker_network:\n 80:2a:a8:e5:de:92:\n bssid: 80:2a:a8:e5:de:92\n bytes: 5895\n channels:\n - 11\n devices:\n 80:1f:02:e6:44:96:\n bytes: 960\n signal: -46\n vendor: Edimax Technology Co. Ltd.\n 80:2a:a8:8a:ec:c8:\n bytes: 472\n signal: 4\n vendor: Ubiquiti Networks Inc.\n 80:2a:a8:be:09:a9:\n bytes: 5199\n signal: 4\n vendor: Ubiquiti Networks Inc.\n d8:49:2f:7a:f0:8f:\n bytes: 548\n signal: 4\n vendor: CANON INC.\n signal: -46\n ssid: hacker\n vendor: Ubiquiti Networks Inc.\n 80:2a:a8:61:aa:2f:\n bssid: 80:2a:a8:61:aa:2f\n bytes: 5629\n channels:\n - 44\n - 48\n devices:\n 78:88:6d:4e:e2:c9:\n bytes: 948\n signal: -52\n vendor: ''\n e4:8b:7f:d4:cb:25:\n bytes: 986\n signal: -48\n vendor: Apple, Inc.\n signal: -48\n ssid: null\n vendor: Ubiquiti Networks Inc.\n 82:2a:a8:51:32:25:\n bssid: 82:2a:a8:51:32:25\n bytes: 3902\n channels:\n - 48\n devices:\n b8:e8:56:f5:a0:70:\n bytes: 1188\n signal: -34\n vendor: Apple, Inc.\n signal: -14\n ssid: hacker\n vendor: ''\n 82:2a:a8:fc:33:b6:\n bssid: 82:2a:a8:fc:33:b6\n bytes: 7805\n channels:\n - 10\n - 11\n - 12\n devices:\n 78:31:c1:7f:25:43:\n bytes: 4632\n signal: -52\n vendor: Apple, Inc.\n 7c:dd:90:fe:b4:87:\n bytes: 423223\n signal: 4\n vendor: Shenzhen Ogemray Technology Co., Ltd.\n 80:2a:a8:be:09:a9:\n bytes: 5199\n signal: 4\n vendor: Ubiquiti Networks Inc.\n signal: -62\n ssid: null\n vendor: ''\n\nNote that, since this is YAML, you can easily use it as an input for\nother scripts of your own devising. I have an example script to parse\nthis \u201cYAML DB\u201d here:\n`parse_trackerjacker_wifi_map.py <https://gist.github.com/calebmadrigal/fdb8855a6d05c87bbb0254a1424ee582>`__.\n\nExample: Track mode with trigger command\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\nTrack mode allows you to specify some number of MAC addresses to watch,\nand if any specific devices exceeds the threshold (in bytes), specified\nhere with the ``--threshold 4000`` (specifying an alert threshold of\n4000 bytes) an alert will be triggered.\n\n::\n\n trackerjacker --track -m 3c:2e:ff:31:32:59 --threshold 4000 --trigger-command \"./alert.sh\" --channels-to-monitor 10,11,12,44\n Using monitor mode interface: wlan1337\n Monitoring channels: {10, 11, 12, 44}\n\n [@] Device (3c:2e:ff:31:32:59) threshold hit: 4734\n\n [@] Device (3c:2e:ff:31:32:59) threshold hit: 7717\n\n [@] Device (3c:2e:ff:31:32:59) threshold hit: 7124\n\n [@] Device (3c:2e:ff:31:32:59) threshold hit: 8258\n\n [@] Device (3c:2e:ff:31:32:59) threshold hit: 8922\n\nIn this particular example, I was watching a security camera to\ndetermine when it was uploading a video (indicating motion was detected)\nso that I could turn on my security system sirens (which was the\noriginal genesis of this project).\n\nExample: Track mode with foxhunt plugin\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\n::\n\n trackerjacker -i wlan1337 --track --trigger-plugin foxhunt\n\nDisplays a curses screen like this:\n\n::\n\n POWER DEVICE ID VENDOR\n ======= ================= ================================\n -82dBm 1c:1b:68:35:c6:5d ARRIS Group, Inc.\n -84dBm fc:3f:db:ed:e9:8e Hewlett Packard\n -84dBm dc:0b:34:7a:11:63 LG Electronics (Mobile Communications)\n -84dBm 94:62:69:af:c3:64 ARRIS Group, Inc.\n -84dBm 90:48:9a:34:15:65 Hon Hai Precision Ind. Co.,Ltd.\n -84dBm 64:00:6a:07:48:13 Dell Inc.\n -84dBm 00:30:44:38:76:c8 CradlePoint, Inc\n -86dBm 44:1c:a8:fc:c0:53 Hon Hai Precision Ind. Co.,Ltd.\n -86dBm 18:16:c9:c0:3b:75 Samsung Electronics Co.,Ltd\n -86dBm 01:80:c2:62:9e:36\n -86dBm 01:00:5e:11:90:47\n -86dBm 00:24:a1:97:68:83 ARRIS Group, Inc.\n -88dBm f8:2c:18:f8:f3:aa 2Wire Inc\n -88dBm 84:a1:d1:a6:34:08\n\n- Note that ``foxhunt`` is a builtin plugin, but you can define your\n own plugins using the same Plugin API.\n\nExample: Track mode with trigger plugin\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\n::\n\n $ trackerjacker --track -m 3c:2e:ff:31:32:59 --threshold 10 --trigger-plugin examples/plugin_example1.py --channels-to-monitor 10,11,12,44 --trigger-cooldown 1\n Using monitor mode interface: wlan1337\n Monitoring channels: {10, 11, 12, 44}\n [@] Device (device 3c:2e:ff:31:32:59) threshold hit: 34 bytes\n 3c:2e:ff:31:32:59 seen at: [1521926768.756529]\n [@] Device (device 3c:2e:ff:31:32:59) threshold hit: 11880 bytes\n 3c:2e:ff:31:32:59 seen at: [1521926768.756529, 1521926769.758929]\n [@] Device (device 3c:2e:ff:31:32:59) threshold hit: 18564 bytes\n 3c:2e:ff:31:32:59 seen at: [1521926768.756529, 1521926769.758929, 1521926770.7622838]\n\nThis runs ``examples/plugin_example1.py`` every time\n``3c:2e:ff:31:32:59`` is seen sending/receiving 10 bytes or more.\n\ntrackerjacker plugins are simply python files that contain either: \\*\n``Trigger`` class which defines a ``__call__(**kwargs)`` method\n(example: ``examples/plugin_example1.py``) \\* ``trigger(**kwargs)``\nfunction (example: ``examples/plugin_example2.py``)\n\nAnd optionally a ``__apiversion__ = 1`` line (for future backward\ncompatibility)\n\nExample: Configuring with config file\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\n::\n\n trackerjacker.py -c my_config.json\n\nAnd here\u2019s the example config file called ``my_config.json``:\n\n::\n\n {\n \"iface\": \"wlan1337\",\n \"devices_to_watch\": {\"5f:cb:53:1c:8a:2c\": 1000, \"32:44:1b:d7:a1:5b\": 2000},\n \"aps_to_watch\": {\"c6:23:ef:33:cc:a2\": 500},\n \"threshold_window\": 10,\n \"channels_to_monitor\": [1, 6, 11, 52],\n \"channel_switch_scheme\": \"round_robin\"\n }\n\nA few notes about this:\n\n- ``threshold_bytes`` is the default threshold of bytes which, if seen,\n a causes the alert function to be called\n- ``threshold_window`` is the time window in which the\n ``threshold_bytes`` is analyzed.\n- ``devices_to_watch`` is a list which can contain either strings\n (representing MACs) or dicts (which allow the specification of a\n ``name`` and ``threshold``)\n\n - ``name`` is simply what a label you want to be printed when this\n device is seen.\n - ``threshold`` in the \u201cSecurity camera\u201d is how many bytes must be\n seen\n\n- ``channels_to_monitor`` - list of 802.11 wifi channels to monitor.\n The list of channels your wifi card supports is printed when\n trackerjacker starts up. By default, all supported channels are\n monitored.\n- ``channel_switch_scheme`` - either ``default``, ``round_robin``, or\n ``traffic_based``. ``traffic_based`` determines the channels of most\n traffic, and probabilistically monitors them more.\n\nExample: Enable/Disable monitor mode on interface\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\nTrackerjacker comes with a few other utility functions relevant to WiFi\nhacking. One of these is the ability to turn on monitor mode on a\nspecific interface.\n\nEnable monitor mode:\n\n::\n\n trackerjacker --monitor-mode-on -i wlan0\n\nDisable monitor mode:\n\n::\n\n trackerjacker --monitor-mode-off -i wlan0mon\n\nNote that trackerjacker will automatically enable/disable monitor mode\nif necessary. This functionality is just useful if you want to enable\nmonitor mode on an interface for use with other applications (or for\nquicker starup of trackerjacker, if you plan to be starting/exiting to\ntest stuff).\n\nExample: Set adapter channel\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\n::\n\n trackerjacker --set-channel 11 -i wlan0\n\nNote that trackerjacker will automatically switch channels as necessary\nduring normal map/track actions. This option is just useful if you want\nto set the channel on an interface for use with other applications.\n\nRecommended hardware\n--------------------\n\n- Panda PAU07 N600 Dual Band (nice, small, 2.4GHz and 5GHz)\n- Panda PAU09 N600 Dual Band (higher power, 2.4GHz and 5GHz)\n- Alfa AWUS052NH Dual-Band 2x 5dBi (high power, 2.4GHz and 5GHz, large,\n ugly)\n- TP-Link N150 (works well, but not dual band)\n\nRoadmap\n-------\n\n- \u2612 Hosted in PyPI\n- \u2612 Radio signal strength for APs\n- \u2612 Radio signal strength for individual macs\n- \u2612 Build map by data exchanged (exclude beacons)\n- \u2612 Packet count by AP\n- \u2612 Packet count by MAC\n- \u2612 Easier way to input per-device tracking thresholds\n- \u2612 Plugin system\n- \u2612 Fox hunt mode\n- \u2612 Tracking by SSID (and not just BSSID)\n- \u2612 Basic macOS (OS X) support (pre-alpha)\n- \u2610 macOS support: get signal strength values correct (will be fixed in\n https://github.com/secdev/scapy/pull/1381\n- \u2610 macOS support: reverse airport binary to determine how to set true\n monitor mode\n- \u2610 macOS support: diverse interface support (not just ``en0``)\n- \u2610 macOS support: get interface supported channels\n- \u2610 Mapping a specific SSID\n- \u2610 Performance enhancement: not shelling out for channel switching\n- \u2610 \u201cJack\u201d mode - deauth attacks\n\n\n",
"bugtrack_url": null,
"license": "MIT",
"summary": "Finds and tracks wifi devices through raw 802.11 monitoring",
"version": "2.0.5",
"project_urls": {
"Homepage": "https://github.com/calebmadrigal/trackerjacker"
},
"split_keywords": [
"hacking",
"network",
"wireless",
"packets",
"scapy"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "a585cd04b4bce2e8f334f8aa560a32a40af17bb1bc03810553668f2b2e26fd66",
"md5": "f66f99d6e5aa4a2571246c2f05574409",
"sha256": "f8b2d0b86996ab253cd444ba0aa05aaf945fef53bd7246f991f2870bcb28891b"
},
"downloads": -1,
"filename": "trackerjacker-2.0.5.tar.gz",
"has_sig": false,
"md5_digest": "f66f99d6e5aa4a2571246c2f05574409",
"packagetype": "sdist",
"python_version": "source",
"requires_python": null,
"size": 407105,
"upload_time": "2024-01-16T05:10:39",
"upload_time_iso_8601": "2024-01-16T05:10:39.930792Z",
"url": "https://files.pythonhosted.org/packages/a5/85/cd04b4bce2e8f334f8aa560a32a40af17bb1bc03810553668f2b2e26fd66/trackerjacker-2.0.5.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-01-16 05:10:39",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "calebmadrigal",
"github_project": "trackerjacker",
"travis_ci": false,
"coveralls": false,
"github_actions": false,
"requirements": [],
"lcname": "trackerjacker"
}
JSON
